Errors Generated in the dbpatch_60 Logs When Migrating to Version 6.2 (Doc ID 1280519.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 6.2.0 and later   [Release: 6.2 and later ]
Information in this document applies to any platform.

Symptoms

As part of the migration to OTM 6.2 the dbpatch_60.sh, or .cmd script is run from the < OTM Home >/glog/oracle/script8 directory to update the database with the structural and data content needed for 6.2. When this script is run several log files are generated which should be reviewed to ensure no errors are generated.

The following are an example of the log files that would be generated during the process.

update_content_<DB SID>_<YYYYMMDD>_<HHMM>.log
csvone_RATE_GEO_COST_OP_OWNER.log
csvone_ACTION_DEF.log
csvone_APP_ACTION.log
csvone_MANAGER_LAYOUT.log
csvone_ACTION.log
csvone_gtm_ACTION_DEF.log
csvone_gtm_APP_ACTION.log
csvone_gtm_MANAGER_LAYOUT.log
csvone_gtm_ACTION.log
migrate_groupmembers_<DB SID>_<YYYYMMDD>_<HHMM>.log
update_password_<DB SID>_<YYYYMMDD>.log
dbpatch_60_<DB SID>_<YYYYMMDDHHMM>.log

Users reviewing the dbpatch_60 log will notice the following errors listed at the end.

The following patches did not apply successfully:

PATCH7256402
PATCH7331920
PATCH7652741
PATCH8475573
PATCH8505623

Changes

These errors have been reported by clients migrating from OTM 6.1.x to 6.2. 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms