IP2017: After Siebel Migration Is Done, Repository Has Only Few tables.
Last updated on FEBRUARY 09, 2018
Applies to:Siebel CRM - Version 17.3 [IP2017] and later
Information in this document applies to any platform.
Using Siebel Migration functionality, DEV environment was migrated into TEST environment. After the migrated repository name was changed from "Migrated Repository" to "Siebel Repository", web tools could open it. However, only few objects were visible and many were not shown.
repexport_39E2A493B4CB.log, log file for "export repository" showed the following information.
2018-02-06 11:35:35 repimexp /l /app/siebel/siebelfs/migration/88-527N9/log/repexport_39E2A493B4CB.log /p ***** /d SIEBEL /Y SrcWorkspaceName=MAIN;SrcEndVer=2;Lang=ENU /r "Siebel Repository" /f /app/siebel/siebelfs/migration/88-527N9/dat/repexport_39E2A493B4CB.dat /c SBA_82_DSN /A O /u sadmin
2018-02-06 11:42:34 Exporting table S_WS_VERSION ... exported 1 rows
2018-02-06 11:42:34 TOTAL TABLES: 126
2018-02-06 11:42:34 TOTAL ROWS : 822182
2018-02-06 11:42:34 Cleaning up, disconnecting from the database.
2018-02-06 11:42:34 Elapsed time: 6 min 59 sec.
** Total number of exported records was 126. Usually it should be close to 400.
** One of the parameters for repimexp utility was "/A O ". It means "Export Runtime Repository Tables & required base tables during initial full and incremental migration."
Also the screenshot of the history of the Migration Application showed the following information.
Resource Name Operation
Schema Service Export
Schema Service Import
RuntimeRepository Date Service Export
RuntimeRepository Date Service Import
RuntimeRepository Date Service DBCheck
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms