Sadmins,
Repository Export/Import and DDL sync during
migrations can we done in different ways. In windows servers most of us will
use “Database Server Configuration Wizard” and Uxin/Linux we use direct .ucf
files. But in effect all these are invoking some common commands based on the
input values provided. I think it is easy to customize and use this command
during the deployments.
Export Repository,
- repimexp /a E /g ALL /u sadmin /p ****** /c siebel_DSN /d SIEBEL /r "Siebel Repository" /f "<Path to be exported>/siebel.dat" /l "<SIEBEL_ROOT>/log/exprep/output/Siebel_export.log"
Import Repository,
- repimexp /a I /G ALL /c siebel_DSN /u sadmin /p ****** /d SIEBEL /r "Siebel Repository_<Date>" /f "<Repository Path>/siebel.dat" /l "<SIEBEL_ROOT>/log/imprep/output/Siebel_Import.log"
DDL Sync,
- <SIEBEL_ROOT>/bin/ddldict /u sadmin /p ****** /c siebel_DSN /d siebel /f /app/siebel/dbsrvr/oracle/schema.ddl /e y /a y /l <SIEBEL_ROOT>/log/ddlsync/output/expschem.log /n "Siebel Repository" /T DCIR
- <SIEBEL_ROOT>/bin/ddlimp /u siebel /p ******* /c siebel_DSN /g SSE_ROLE /f /app/siebel/dbsrvr/oracle/schema.ddl /e n /B SBL_DATA /X SBL_INDX /R Y /s Y /l <SIEBEL_ROOT>/log/ddlsync/output/ddlsync1.log /9 Y
- <SIEBEL_ROOT>/bin/ddlimp /u siebel /p ****** /c siebel_DSN /g SSE_ROLE /f /app/siebel/dbsrvr/oracle/schema.ddl /e y /B SBL_DATA /X SBL_INDX /R Y /s Y /l <SIEBEL_ROOT>/log/ddlsync/output/ddlsync2.log /9 Y
·
/c – System DNS value for Siebel environment
·
/B – Table space name for data
·
/X – Table space name for Index
Have a Nice deployment... :)