My Oracle Support Banner

Siebel IP2013 Unable to verify login name SIEBEL Error When Regenerating Schema.ddl (Doc ID 2504215.1)

Last updated on DECEMBER 23, 2019

Applies to:

Siebel Public Sector Service - Version [IP2013] and later
Information in this document applies to any platform.


On : [IP2013] version, Upgrade

When attempting to run ddlsync on restored IP2013 environment as standalone utility, ddlsync fails and the following error occurs.

2019-02-01 14:46:44 Unable to verify login name SIEBEL.
2019-02-01 14:46:44 Unable to start common api.
2019-02-01 14:46:44 Error in DDLDictStartApis function..
2019-02-01 14:46:44 (logapi.cpp (184) err=1 sys=0) SBL-GEN-00001: (logapi.cpp: 184) error code = 1, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)

The issue can be reproduced ONLY in customer environment at will with the following steps:
1. Rollback Siebel IP16 to IP2013 and restoring poruduction IP2013 db ino the environment
2. Restore Production IP2013 DB into the environment
3. Run imprep, exprep and ddlsync and check to see if the utilities run.

The issue has the following business impact:
Due to this issue, users cannot finish ddlsync and this was causing a setback.




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

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