Problems saving results of Headstart Utilities

Question

I've problems with two utilities concerning journalling:
1. Maintain journal tables HSU_CJNT Revision 6.5.0.4
This package does not want to save the changes made to the journal tables in the repository. The error is CDA-01305: Column: UID 1 uniqueness violation. Version of Repository is 6.5.69.2.0
2. Maintain journalling business rules HSU_JNBR Revision 6.5.0.2
This package also doen't want to save adjustments, in this case to the BR's Errors :
CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_INS): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_INS) in Container (Name MAT)
CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_UPD): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_UPD) in Container (Name MAT)
CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_DEL): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_DEL) in Container (Name MAT)
Anyone any suggestions/patches?

Answer 1

Willem,
Regarding your problems:
1. Maintain journal tables HSU_CJNT Revision 6.5.0.4
This package does not want to save the changes made to the journal tables in the repository.
The error is CDA-01305: Column: UID 1 uniqueness violation. Version of Repository is 6.5.69.2.0This UID requires the column name to be unique within the table.
What could be the case is that your table has two or more columns that have almost identical names, and only differ
after the 26th character. The utility creates column names like OLD_<column name> and NEW_<column name>.
If for example you have 2 columns in the same table that are called VERY_VERY_LONG_COLUMN_NAME1 and
VERY_VERY_LONG_COLUMN_NAME2, the utility applies the algorithm 'OLD_'||substr(r_col.col_name, 1, MAX_IDENTIFIER_LENGTH - 4)
and come up with OLD_VERY_VERY_LONG_COLUMN_NAME, for both of the original columns!
Could you check if this is the reason for the failure? If so, you could try renaming the columns, or changing the algorithm for deriving the journal column names in package hsu_cjnt.
2. Maintain journalling business rules HSU_JNBR Revision 6.5.0.2
This package also doen't want to save adjustments, in this case to the BR's Errors :
CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_INS): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_INS) in Container (Name MAT)
CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_UPD): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_UPD) in Container (Name MAT)
CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_DEL): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_DEL) in Container (Name MAT) It seems like the utility tries to create new database triggers, but they already exist in the Container (=Application System or Folder).
It could be that the database triggers already exist in a different workarea than the one you are running the utility in.
The utility can see only the objects in the context workarea, so it doesn't know about the possible existence of the triggers in another workarea.
You can check this by running the following query while logged in as a Repository user or the Utilities owner:
select name
from ci_database_triggers
where table_definition_reference = 2642375373300319097291377310396885686
If it selects the trigger names BR_ADS_JRN_INS etc, but you cannot see those triggers in your workarea, then they must exist in another workarea.
Try to include them in your workarea or run the utility in the other workarea.
Could you check if this is the case?
kind regards, Sandra