Repository Import/Export & DDL Sync From Command Line

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... :)

Application Deployment Manager

                       Application Deployment Manager(ADM)

Introduction:

Siebel can automate movement of Repository related data between environments, but it cannot move application related data like,

• List of Values
• View
• Responsibilities
• Business Services
• Runtime Events

and many more things. We have to move them manually. Using ADM provided by Siebel can make admins life easier.

Note: ADM is only recommended if the amount of data that is to be moved is less, otherwise EIM is the preferred option.

Following are the process to execute the UI Session ADM,

• Go to Application Deployment Manager > Deployment Projects,

• Create a Project under Deployment Projects view,

• Add entities and apply appropriate Filter,

• Enable the project
  

• Go to Application Deployment Manager > Deployment Sessions and create new deployment session with new project,
  

• Deploy the project
  

• Provide the path and click the export button,
  

• The exported file will be in the specified folder,
  

• Move the all three files to the destination environment and Go to Application Deployment Manager > Deployment Sessions,
  

• Select “Deploy From File” or “Deploy From Local File” from the “Menu”,
  

• Provide the path and click “Import” button,
  

Some points that need to keep in mind,

• There should be a shared folder that should be accessible from both source and target environments.
• Don’t forget to check the Export to File checkbox
• If your servers are on Unix/Solaris environment then you need to provide path according to that e.g /opt/shared/ and if your Siebel server is on windows then you need to provide path like \\servername\sharedfoldername
• Path provided in Source environment should be only till the shared folder for example if you want that your file should go to /opt/shared/admfolder then you should then path you give is /opt/shared/admfolder/
• In the target environment you will provide complete the path including the filename that you want to import.

Have nice Deployments with ADM.... :)