My Oracle Support Banner

Siebel Server service is not starting after application upgrade to Siebel IP2017 due to error "Repository 'Siebel Repository' does not exist in database" (Doc ID 2597101.1)

Last updated on OCTOBER 08, 2019

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.

Symptoms

After upgrading Siebel Application to version IP2017 or later the Siebel Server service is not starting. 

The errors captured in SRProc log are:

Message: GEN-06, Additional Message: Repository 'Siebel Repository' does not exist in database.

Message: GEN-10, Additional Message: Calling Function: DICLoadDict; Called Function: DICGetRepository

(srpdb.cpp (862) err=3006 sys=2) SBL-GEN-03006: Error calling function: DICFindTable m_pReqTbl

 

SvrTblCleanup and SvrTaskPersist are not starting due to below errors:

objdef.cpp (14527)) SBL-DAT-60313: Workspace config does not exist for the given workspace name.

( (0) err=2818155 sys=7728025) SBL-OMS-00107: Object manager error: ([0] Workspace config does not exist for the given workspace name.(SBL-DAT-60313) (0x75eb99))

(ccfom.cpp (568) err=2818150 sys=0) SBL-OMS-00102: Error 7728025 logging in to the application

 

If SRProc, SvrTblCleanup and SvrTaskPersist components are down the Siebel Server service will never start.

Changes

 Upgraded Siebel Application from lower version like 8.1.1.14 to IP2017.

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


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