Extra Step not in Admin Guide for Upgrades

[mkenney]

I wanted to post this to the group because it corrected numerous issues with our upgrade, and other Oracle customers have expressed an interest in doing something similar.

In the first rehearsal of our upgrade there were many integrity constraint errors. We had to disable constraints in the DB throughout the entire upgrade to get data to load. Here is one example:

<TableName>MANAGER_LAYOUT</TableName>
<Exception>ORA-02291: integrity constraint (GLOGOWNER.FK_ML_TRANSLATION_GID) violated - parent key not found

I found hundreds of missing data elements where data from a previous release was missing, and a missing header would cause the detail to fail on a foreign key or other similar circumstance. In our second rehearsal of the upgrade I added extra steps not in the Admin Guide which corrected virtually all of the integrity problems.

The fix was to do a run of update_content to load ALL of the base 5.5 data. After running [dbupdate_55.sql] and before running [update_content for V55] add this extra two step process:

1 - In the [otm\glog\oracle\script8\content_glogowner] folder, copy 'csv_glogowner_tables.txt' to a file called 'BASE_insert_glogowner_data.txt'.

2 - Execute the following command: update_content d:\otm\glog\config BASE

The update_content script will go look for all of the 330 or so tables in the text file, and load using the corresponding txt or xml files. All of our subsequent testing has been favorable, and the system is running without problems.

Similar steps could be taken for 5.0 or other versions.

Enjoy

Matt Kenney

[mkenney]

Re: Extra Step not in Admin Guide for Upgrades

Here is another additional step to try if you see errors from update_content similar to this in the logs:

<Error>Failed to open ext_fname = .\content_glogowner\xml\V55_AGENT_ACTION\accept_te nder.txt</Error>

The resolution is to make copies of 8 folders under 'script8\content_glogowner\xml' with 'V55_' at the beginning of the folder name, because that is what the update_content script is apparently looking for including 'agent_action' from this example. So, the old folder name for this example was 'agent_action' and new folder name is 'V50A_AGENT_ACTION'.

After making this change there are no errors opening the files.

MK

[mkenney]

Re: Extra Step not in Admin Guide for Upgrades

Here are the 8 folders needed:

V55_AGENT_ACTION
V55_FINDER_SET
V55_MANAGER_LAYOUT
V55_NOTIFY_SUBJECT
V55_USER_MENU_LAYOUT
V55_USER_MENU_LAYOUT_DE
V55_USER_MENU_LAYOUT_FR_CA
V55_WORKSPACE

[mkenney]

Re: Extra Step not in Admin Guide for Upgrades

Correction:

... for this example was 'agent_action' and new folder name is 'V55_AGENT_ACTION'.

The same is also true for 5.0LA where 'V50A' needs to be added to the folder names, though there were only 7 folders. GA was fine and did not need the folder names changed.

[sprabhakar]

Re: Extra Step not in Admin Guide for Upgrades

Hi Matt,
This is very useful but could you also provide the OS on which you are encountering these problems as the same issues need not replicate on other OS installations.

Prabhakar

[mkenney]

Re: Extra Step not in Admin Guide for Upgrades

Hi Prabhakar,

The OS is Windows Server 2003 Enterprise Edition. The extra run of update_content should also work with UNIX Shell in theory, but I have only run the DOS version. I also do not know if the folder names are a problem on other OS installations, or just Windows.

MK

[mkenney]

Re: Extra Step not in Admin Guide for Upgrades

Here is a little more background on what lead us towards loading 'BASE' data.

Besides MANAGER_LAYOUT (used as an example in previous post), here are other tables that failed to load due to integrity problems:

ACTION, ACTION_DEF, ACTION_DEF_ARG, ACTION_DEF_STATE, AGENT_ACTION_DETAILS, AGENT_EVENT, AGENT_EVENT_DETAILS, BN_TYPE, DATA_TYPE_ASSOCIATION, FINDER_SET, INT_GLOG_XML_ELEMENT, NOTIFY_SUBJECT, PREFERENCE_VALUE, PLANNING_PARAMETER, ROT_RATE_OPERAND_VISIBILITY, TABLE_SET_DETAIL, reportowner.REPORT_PARAMETER, BN_RULE, DATA_TYPE_ASSOCIATION, ACTION_ARG, AGENT_ACTION, NOTIFY_SUBJECT_STYLESHEET

Loading the BASE data corrected all of this.

[mkenney]

Re: Extra Step not in Admin Guide for Upgrades

Here is a detailed explanation for a few of these tables:

DATA_QUERY_TYPE.csv data was not loaded because it was not listed in [version]_insert_glogowner_data.txt or [version]_update_glogowner_data.txt files. The record with DATA_QUERY_TYPE_GID of 'SHIP UNIT' was not in V55_DATA_QUERY_TYPE.csv or V55P_DATA_QUERY_TYPE.csv files. This caused a constraint problem with DATA_TYPE_ASSOCIATION (FK_DTA_FROM_DATA_QUERY_TYPE_GID) because the child record with the FROM_DATA_QUERY_TYPE_GID of 'SHIP UNIT' could not be inserted due to the missing DATA_QUERY_TYPE data.

ACTION.csv data was not loaded because it was not listed in [version_insert_glogowner_data.txt or [version]_update_glogowner_data.txt files. The record with ACTION_GID of 'SCHEDULE_APPOINTMENT' was not in V55_ACTION.csv or V55P_ACTION.csv files. This caused a constraint problem with ACTION_ARG (FK_AA_ACTION_GID) because the child record with the ACTION_GID of 'SCHEDULE_APPOINTMENT' and ARG_NAME of 'state' could not be updated due to the missing ACTION data.

BN_TYPE.csv data was not loaded because it was not listed in [version]_insert_glogowner_data.txt or [version]_update_glogowner_data.txt files. The records with BN_TYPE_GID of 'JOB_XID_ORDER_MOVEMENT', 'JOB_XID_ORDER_RELEASE', and 'FILE_DOCUMENT_XID' were not in V55_BN_TYPE.csv or V55P_BN_TYPE.csv files. This caused constraint problems with BN_RULE (FK_BN_TYPE_GID) because the child records with the same three BN_TYPE_GID values could not be inserted due to the missing BN_TYPE data.

Again this is all resolved now, but just wanted to provide a little more background in case others are experiencing something similar.

MK