My Oracle Support Banner

After Running PostInstallDBSetup Several Components Fail to Start Due to Invalid SADMIN IS Null Query (Doc ID 2739673.1)

Last updated on MARCH 18, 2021

Applies to:

Siebel CRM - Version 20.3 to 21.2 [Release V17]
Information in this document applies to any platform.

Symptoms

Database Platform: db2 z/OS specific

After the PostInstallDBSetup execution is complete the following unexpected query is found on several components that failed to startup.

SELECT T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
:1
FROM
SIEBEL.S_PARTY T1,
SIEBEL.S_CONTACT T2
WHERE
('SADMIN' IS NULL )
...
ObjMgrSqlLog SqlTag 2 000000035f722074:0 2020-09-28 17:32:00 Begin: Execute SqlObj 'Login User' at e0869e0 with SqlTag=SvrTaskPersist,srvr1,40894466,SADMIN,000000035f722074:0,,Login User,

The query is related to the Login User business component, causing the following two subsequent errors:

ObjMgrSessionLog Error 1 000000035f722074:0 2020-09-28 17:32:00 (dmsessionusercontext.cpp (1171)) SBL-DAT-00254: The username you have entered is invalid.  Please try to log on again or contact your system administrator for assistance.
ObjMgrSessionLog Error 1 000000035f722074:0 2020-09-28 17:32:00 (dmsessionusercontext.cpp (640)) SBL-DAT-00546: The user-context could not be established.  Something is wrong with the assigned primary position or login related repository objects.  See additional error messages for more information.

For interactive application object managers it gives the 'Server is busy...' error as no user authentication can be processed.

It is possible to obtain detailed PostInstallDBSetup log file by setting the SIEBEL_LOG_EVENTS=5 on the OS session used to start PostInstallDBSetup execution.
In the IncrementalTablePublish.log located under the generated PostInstallDBSetup directories in the siebsrvr/log directory, the following update query confirms the corruption on S_RR_STREAMS table contents:

ObjMgrSqlObjLog WriteRecord 5 000000025fd001e4:0 2020-12-09 16:40:59 Begin: WriteRecord for SqlObj 'Runtime Repository Stream' at 6e873a48
ObjMgrSqlLog Detail 4 000000025fd001e4:0 2020-12-09 16:40:59 INSERT/UPDATE statement with ID: Unknown

UPDATE SIEBEL.S_RR_STREAMS SET
  DB_LAST_UPD_SRC = ?,
  DB_LAST_UPD = current timestamp,
  LAST_UPD = ?,
  LAST_UPD_BY = ?,
  MODIFICATION_NUM = ?,
  COMPILED_OBJ_DEFN = ?
  WHERE
  ROW_ID = ? AND MODIFICATION_NUM = ?

ObjMgrSqlLog Detail 4 000000025fd001e4:0 2020-12-09 16:40:59 Bind variable 1: Object Manager - Default
ObjMgrSqlLog Detail 4 000000025fd001e4:0 2020-12-09 16:40:59 Bind variable 2: 2020-12-09 16:40:59
ObjMgrSqlLog Detail 4 000000025fd001e4:0 2020-12-09 16:40:59 Bind variable 3: 1-1YJYWR5T
ObjMgrSqlLog Detail 4 000000025fd001e4:0 2020-12-09 16:40:59 Bind variable 4: 1
ObjMgrSqlLog Detail 4 000000025fd001e4:0 2020-12-09 16:40:59 Bind variable 5: 2#13#1#9#S_EVT_ACT23#1#18#1#13#S_EVT_ACT_LSX
ObjMgrSqlLog Detail 4 000000025fd001e4:0 2020-12-09 16:40:59 Bind variable 6: 1-1YJZ2CHY
ObjMgrSqlLog Detail 4 000000025fd001e4:0 2020-12-09 16:40:59 Bind variable 7: 0

The following query can be used to verify the corruption:

SELECT length(T1.COMPILED_OBJ_DEFN),T1.COMPILED_OBJ_DEFN, T1.ROW_ID
   FROM <TBL_OWNER>.S_RR_STREAMS T1
   WHERE T1.NAME = 'EXTN_STREAM' AND T1.REPOSITORY_ID in
   (select T2.ROW_ID from <TBL_OWNER>.S_REPOSITORY T2 WHERE T2.NAME='Siebel Repository');

In a non-corrupt situation it should return a length that is greater than 5000 characters long while in a corrupt situation it returns 44 characters long.

Changes

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.