Prerequisites for IRM

Before you begin:

1. Install Enterprise Server (Siebel Gateway Name Server, the Siebel Server, and the Siebel Database Server)
2. Windows only: Install Siebel tools on the same machine as Enterprise Servers,  then the merge process automatically starts Siebel Tools to execute the incremental repository merge.
• If the Siebel Enterprise server is not installed on the same computer as Siebel Tools, then map a network drive from the computer where Siebel Tools is installed to the computer where Siebel Enterprise Server is installed. Use this mapped drive to specify the location of the Siebel Server when you run the Siebel Database Configuration Wizard.
3. Set open_cursors=5000
4. Change Tools ODBC

1.            Use the Siebel Tools default ODBC driver, Siebel Oracle90.

2.            Navigate to HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INI and for your ODBC add

·          

o    ColumnsAsChar=1

o    ColumnSizeAsCharacter=1

3. Test ODBC

5. Update tools.cfg:

1.  
1. In the [Siebel] section Change the ServerDbODBCDataSource parameter from the default value to your custom ODBCname.
2. (For MSSQL and IBM DB2 platforms only) In the [ServerDataSrc] section, change the Connect String parameter from the default value to your custom ODBC name.
3. Change the SymStrPrefix value from the default value of X_ to SBL_ .
4. EnableToolsConstrain=False
5. DockRepositoryName=Prior Customer Repository
6. Test Siebel Tools
7. Navigate to Veiw->Options-Language Settings and select the required language as the primary language, then click Yes.
8. Close Tools

6. Copy Ancestor Repositories

• On My Oracle Support, locate 17329360 (Patch ID) and download it to your folder
• Copy files

Windows: copydat.bat SiebelRoot optional_log_file

UNIX: sh copydat.sh SiebelRoot optional_log_file

7. Delete all repositories except for Siebel Repository

8. Drop functional or bitmap indexes if they exist (they are created if you have CIAI implementation)

9. Run upgrep/Delta merge/upgphys

10. Upgrade test production

11. Replace the original siebel_sia.srf provided as part of the Siebel CRM version 8.1.1.11 or 8.2.2.4 Fix Pack with a new SRF file obtained following one of these methods:

a) Full compiled SRF using Siebel Tools version 8.1.1.11 or 8.2.2.4; Note when 8.1.1.11 is applied on the existing 8.1.1.x including 8.1.1.10, IRM (Incremental Repository Merge) is mandatory. The SRF should be compiled after the IRM (Incremental Repository Merge) process successfully completed, more detail about IRM is available from: Siebel Database Upgrade Guide >Performing the Siebel Incremental Repository Merge

b) SRF obtained from a download of this file for Siebel CRM version 8.1.1.11 (or 8.2.2.4) from Oracle Software Delivery Cloud, also known as eDelivery (https://edelivery.oracle.com/)

12. If you have to restart IRM:

1) Restore the database from backup prior to running IRM
2) Remove UpgRep log folder from SiebSrvrLog directory
3) Restart IRM process.

13. The following KM articles should be reviewed before starting the IRM process as these may contain information or workarounds that should be applied before starting IRM:

•Delta Repository Merge Aborted during Incremental Repository Merge (IRM) on Siebel version 8.1.1.11: (Doc ID 1600333.1)         

•8.1.1.11 Delta Merge exit "Operation aborted due to general error " (Doc ID 1604417.1)     - Oracle RBDMS specific        

•DDLDICT-ERR-1017: Unable To Copy Data From Siebel Dictionary. (Doc ID 1630424.1)    

•If Siebel Order Management is in use on the current release, a known issue may cause Siebel Order Management application data migration issues. The migration scripts should be adjusted before starting IRM. Verify workaround as per Doc ID 1622589.1 in case.

  

Please make a database backup after each IRM phase. Especially before starting the Incremental Repository Merge from the Siebel Tools workstation and after completing this phase, pre and post having reviewed the object conflicts.

Incremental Repository Merge (IRM)

Siebel CRM 8.1.1.10/8.2.2.3 introduces a new tool, Incremental Repository Merge (IRM).

The incremental repository merge process streamlines previous processes such as the ACR import process and repository changes to provide a simple and highly effective way to import and reconcile repository changes.  Only changes since the last installed patch are imported, reducing the impact on customers of adopting both new repository fixes and features.  IRM allows easy identification and resolution of any merge conflicts in workflows and tasks which in turn can help reduce the risk of regressions being introduced.

IRM provides the following capabilities and benefits:

1. IRM simplifies the installation and deployment features of Oracle patches that provide new features in Siebel CRM; a Siebel Innovation Pack consists of products features (formerly known as ACRs). IRM provides an aggregated process of importing all new ACR’s at once 

a. Removes the need to individually import Siebel features released since the base release. 

b. Accelerates availability of Siebel features by removing the need for any additional repository changes one a patch has been put into place

c. Reduces the impact of integration and testing midstream in a deployed Siebel instance by collating and combining manual steps previously required into the core IRM process. 

d. Reduces the number of steps required to complete deployment, the amount of documentation needed to support these steps and the associated learning curve by combing all steps needed to update the repository into a single process.

2. IRM provides repository fixes in Siebel patches that improve quality improvements related to quick fixes that are provided as part of the patch or release.

a. Reduces testing overhead caused by needing to conservatively apply patches that may not apply to the deployed functionality.

b. Increases confidence that all patches related to specific deployed functionality are present.

3. IRM provides a new and formalized approach to generating and consuming specific repository archives; it is now possible to generate an archive of specific targeted object content into Siebel Delta Files (SDF).

a. Promotes Parallel Development of customer solutions, simplifying the integration of work from different sources

       Generated files contain only the changes are smaller and will merge into the target repository faster.Example: archiving a particular Business Component field property change as opposed to archiving the complete object.

b. Reduces integration testing load by highlighting areas of conflict and recommending actions.

4. IRM provides aggregated product features together that are already tested in the same consolidated format by Oracle

a. Removes the task of acceptance testing ACR combinations

b. Allows the testing of customer specific changes related to configuration to take priority, shortening overall time to deploy.

The mandatory IRM process concentrates more on incremental changes, simplifies the adoption of fixes and features, and allows customers to make more agile business decisions based on function rather than being driven by the technical demands of the legacy, more complex, patching effort.