Siebel DB2 Z/OS Upgrade Fails With SQLCODE = -669, ERROR: THE OBJECT CANNOT BE EXPLICITLY DROPPED. REASON 0001 While Removing Interface Tables
(Doc ID 3021657.1)
Last updated on MAY 14, 2024
Applies to:
Siebel CRM - Version 22.9 and laterIBM z/OS on System z
Symptoms
Siebel with DB2 Z/OS is being upgraded, or IRM, Incremental Repository Merge, is being executed.
When the step Staging Database Environment Setup Menu > Option 8 - Drop Interface Tables is selected in the mainframe, it submits the job DSNHLQ.SIEBEL.INSTALL.JCL (INFDRPJS), which fails as follows:
SQLERROR ON DROP COMMAND, EXECUTE FUNCTION
RESULT OF SQL STATEMENT:
DSNT408I SQLCODE = -669, ERROR: THE OBJECT CANNOT BE EXPLICITLY DROPPED. REASON 0001
DSNT418I SQLSTATE = 42917 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXIDTB SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 35 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000023' X'00000000' X'00000000' X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOST
The following steps can be executed to reproduce the issue:
1. Start the Siebel Database Upgrade, or IRM, for DB2 Z/OS. Read the details in Siebel Database Upgrade Guide for DB2 for z/OS.
2. Run the steps to create the Stage Database in the mainframe. Execute option 8 of Staging Database Environment Setup Menu. See instructions in Siebel Database Upgrade Guide for DB2 for z/OS > Creating the Siebel Staging Database.
3. The job DSNHLQ.SIEBEL.INSTALL.JCL (INFDRPJS) fails with SQLCODE -669 reason 01.
Changes
Upgrade Siebel DB2 Z/OS or run the Incremental Repository Merge to any version starting in 22.9.
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 |