PostInstallDBSetup Fails When Updating To 22.10 in SeedSchemaManifest Upgrade Step - ORA-00955 Error Found In create_table.log
(Doc ID 2916184.1)
Last updated on FEBRUARY 13, 2023
Applies to:
Siebel CRM - Version 22.10 to 23.1 [Release V17]Information in this document applies to any platform.
Symptoms
When attempting to install 22.10 Monthly Update on top of 20.12, PostInstallDBsetup fails on SeedSchemaManifest Upgrade step, see below:
WSRanking script has already been run on this environment
Stage 2 of 4 : Running SeedSchemaManifest Upgrade
Error in running SeedSchemaManifest Upgrade
WSRanking Execution is not applicable and SeedSchemaManifest Execution Failed.
The create_table.log file located under $SIEBEL_ROOT/siebsrvr/log/PostInstallDBSetup_YYYY-MM-DD_HH-MM-SS directory contains the following error related to S_APP_VER_HIST table:
SQL DBMS: Oracle version 19.00.0000 Oracle 19.0.0.0.0
ODBC driver: SEor827.so version 07.16.0162 (B0375, U0247)
(login time: 0.15s)
CREATE TABLE SIEBEL.S_APP_VER_HIST
(ROW_ID VARCHAR2(15 CHAR),
CREATED DATE,
CREATED_BY VARCHAR2(15 CHAR),
LAST_UPD DATE,
LAST_UPD_BY VARCHAR2(15 CHAR),
MODIFICATION_NUM NUMBER(10,0) DEFAULT 0,
CONFLICT_ID VARCHAR2(15 CHAR) DEFAULT '0',
PAR_ROW_ID VARCHAR2(15 CHAR),
DB_LAST_UPD DATE,
OVERRIDE_FLG CHAR(1 CHAR),
APP_VER_BASE VARCHAR2(15 CHAR),
DB_LAST_UPD_SRC VARCHAR2(50 CHAR),
START_VER VARCHAR2(15 CHAR),
END_VER VARCHAR2(15 CHAR),
REPOSITORY_NAME VARCHAR2(75 CHAR),
PROCESS_NAME VARCHAR2(30 CHAR),
PROCESS_CMD VARCHAR2(3500 CHAR),
ERROR_DESC VARCHAR2(3500 CHAR),
STATUS_CD VARCHAR2(30 CHAR)
)
ODBC error S0001 in SQLExecDirect: [1076673536][ODBC Oracle driver][Oracle]ORA-00955: name is already used by an existing object (native error 955).
grant select,insert,update,delete on SIEBEL.S_APP_VER_HIST to SSE_ROLE
(execution time: 0.05s, no rows affected)
ODBCSQL: Exit at 12/13/22 18:55 (status 0)
The import_cus_schema.log located under $SIEBEL_ROOT/siebsrvr/log/PostInstallDBSetup_YYYY-MM-DD_HH-MM-SS/SeedSchemaManifest/Common contains the following error:
STEPS
The issue can be reproduced at will with the following steps:
1. Install 22.10 Monthly Update on top of 20.12 installation
2. Observe that PostInstallDBSetup is executed, but fails on the step 2 as mentioned above.
Changes
Installation of 22.10 Monthly Update on top of 20.12 installation
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |