My Oracle Support Banner

Isssue Importing A Repository After Rollback Form IP 2016 To IP 13 (comdb51.sql not found) (Doc ID 2487861.1)

Last updated on DECEMBER 25, 2019

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
Issue importing a repository after rollback form IP 2016 to IP 13

Siebel Server was rolled back from IP2016 to Ip2013. As part of the rollback repimexp was executed to import a latest IP13 repository form our other environment. However, when imprep was run there seems to be an issue with sql referenced not existing in IP13 but only in IP2016. 


repimexp.exe /a I /g FRA,ENU /u SADMIN /p ***** /c XYZ_DSN /D SIEBEL /M y /R "Siebel Repository-8.1" /F D:\sba81\siebsrvr\custrep.dat /l D:\sba81\siebsrvr\log\rep2.log

Connecting to the database...
Connected.
Starting common api.
Unable to open file 'D:\sba81\siebsrvr\sqltempl\comdb51.sql'.
Unable to start Common SQL file api.
Unable to start common api.
Unable to start common api.
Error in initiate function..
Elapsed time: 1 sec.



EXPECTED BEHAVIOR
-----------------------
repimexp should work without accessing 'D:\sba81\siebsrvr\sqltempl\comdb51.sql'.




STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Rolled back Siebel Server from IP2016 to IP2013.
2. On IP2013 environment, repimexp was started.



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


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