1. Using Siebel Tools
  2. What’s New in This Release

9Managing Repositories

Viewing, Renaming, Comparing, and Configuring Repositories

This topic describes how to view, rename, and compare repositories. It includes the following information:

Overview of Managing Repositories

A Siebel Repository is a set of tables that includes Siebel objects and server scripts. These objects and scripts define a Siebel application, such as Siebel Field Service. This repository provides the metadata that Siebel CRM requires to interact with enterprise data and to interact with the people who use the Siebel application. The Siebel application stores these tables in the Siebel runtime repository, and then reads the repository at run time. You can use Siebel Tools to view and modify the information that this repository contains. For more information, see Configuring Siebel Business Applications.

Siebel CRM includes Incremental Repository Merge, which is a feature that allows you to merge multiple repositories to a single repository during an incremental upgrade. It automatically does some of this upgrade work for you, such as importing SIF files and seed data, applying schema modifications, and deliver. For more information, see Siebel Database Upgrade Guide.

Files That You Use to Manage Repositories

A Siebel ArchIve File (SIF) is a type of file that you can use to import object definitions into or export objects from the Siebel runtime repository. You can use Siebel Tools to create an SIF file, and you can use SIF files to move your modifications from a source environment to a destination environment. Siebel Tools writes SIF files in XML format. A SIF file uses the following hierarchy, and it can include property values and scripts:

  1. Repository

  2. Project

  3. Object

  4. Child Objects

For example, the following code is part of an SIF file that Siebel Tools creates when it adds objects to a hotfix. It includes a definition for the Account Assoc Applet:

<REPOSITORY

  NAME="Siebel Repository"

  ... >

  <PROJECT

     ...

     NAME="Account (SSE)"... >

     <APPLET

        ASSOCIATE_APPLET="Account Assoc Applet"

        BUSINESS_COMPONENT="Account"

        CLASS="CSSFrameListBase"

        ...

        NAME="Account List Applet"

        ... >

        <APPLET_METHOD_MENU_ITEM... >

        </APPLET_METHOD_MENU_ITEM>...

     </APPLET>

     <BUSINESS_COMPONENT

        CACHE_DATA="N"

        CLASS="CSSBusComp"

        ... >

     </BUSINESS_COMPONENT>

     ...

  </PROJECT>

</REPOSITORY>

For more information about:

  • Using Siebel Tools to import or export an SIF file as an archive file, see Archiving Objects

Viewing Information About the Current Repository

In Siebel Tools, only one repository is available for all users working on workspaces in the Siebel environment. Siebel Tools opens this repository, by default.

In some situations, multiple repositories might reside on the Siebel Server (for example, if you upgrade to a new version of Siebel CRM).

To view information about the current repository

  1. In Siebel Tools, click the File menu, and then click Open Repository.

    Siebel Tools displays the Open Repository dialog box. This dialog box lists the repositories in the database that Siebel Tools uses. Siebel Tools highlights the repository that it is currently using.

  2. Click the Help menu, and then click About SRF.

  3. Examine the information that the About Repository File dialog box shows using the information from the following table.

    Field Description

    Internal Version

    Version number that Oracle maintains. Siebel CRM modifies this value only if the internal format of the repository is modified (for example, during an upgrade).

    User Version

    Reserved for use by Oracle’s Siebel Anywhere. It maintains this number when Oracle creates kits that upgrade the repository. Siebel CRM reads this value when it does a version check.

    Full Compile

    Choose this option to display information about the most recent full compile.

    Last Incremental Compile

    Choose this option to display information about the most recent incremental compile. If no incremental compile has occurred since the last full compile, then this option is not available.

    When

    Date of the last compile.

    Machine Name

    Name of the computer that Siebel CRM uses to compile the repository.

    Language

    Language code.

    User Name

    The Microsoft Windows logon name of the user who compiled the repository.

    Repository

    Repository name of the repository that was current when Siebel CRM performed the compile. This value is typically Siebel Repository.

    Tools Version

    The version number and build number of the Siebel Tools software that performed the compile. Global Customer Support can use this information to help you resolve a problem.

    Schema Version

    Database schema version of the Siebel database that Siebel CRM uses to compile the repository.

Renaming Repositories

It is recommended that you use Siebel Repository as the name of the repository that you use in your production environment. If you want to rename the repository, then it is recommended that you use the procedure that this topic describes.

To rename repositories

  1. Display the Repository object type.

    For more information, see Displaying Object Types in the Object Explorer.

  2. In the Object Explorer, click Repository.

  3. In the Repositories list, locate the repository that you want to rename.

    For more information, see Locating and Modifying Object Definitions in the Object List Editor.

  4. Enter the new name in the Name property, and then step off the record to save your modifications.

    For more information, see Guidelines for Naming Repositories.

  5. Modify the value of the Siebel Repository enterprise parameter to the new name of the repository.

    For information about how to modify an enterprise parameter, see Siebel System Administration Guide.

  6. Modify the Application Main Repository Name parameter in the Object Manager.

Guidelines for Naming Repositories

If you name a repository, then it is recommended that you use the following guidelines:

  • Use a naming convention for all repositories that your Siebel CRM implementation uses. Siebel Servers reference a repository by name. The procedure that you use to upgrade to a new version of Siebel CRM depends on the repository name. A consistent naming convention promotes successful configuration and testing and minimizes the work required to migrate a new repository or to do an upgrade.

  • Use the default Siebel Repository name, where possible. You can modify this name only if it is absolutely necessary. The default configuration that Siebel CRM uses assumes that the repository name is Siebel Repository.

  • Use the same repository name in your test environment that you use in your production environment.

  • If your development environment uses multiple repositories, then use a unique and descriptive name for each repository. For example, you might use Siebel v8.2 Original as the name of the repository when you install Siebel CRM. You can use another descriptive name for the repository that you use during an upgrade and for a repository from a prior custom configuration.

Configuring Siebel CRM to Read Data from a Single Repository

The example in this topic describes how to configure Siebel CRM to read data from a single repository when the Siebel database contains multiple repositories.

To configure Siebel CRM to read data from a single repository

  1. Log in to the Siebel client with administrative privileges, and complete the following steps:

    1. Navigate to the Administration - Order Management screen, and then the Message Types view.

    2. Navigate to the Payload view, and then create a new record.

    3. In the new record, access the drop-down list for the Response Field.

      If the Response Field drop-down list:

      • Does not display duplicate values. The Siebel database does not contain multiple repositories, and you can exit this task.

      • Displays duplicate values.The Siebel database contains multiple repositories, and you must configure Siebel CRM to read data only from a single repository. Continue to Step 2.

    4. Delete the new record that you created.

  2. Configure Siebel CRM to read data only from a single repository:

    1. Log in to Siebel Tools.

    2. In the Object Explorer, click Pick List.

    3. In the Pick Lists list, query the Name property for the following value:

      UMS PickList Response Field

    4. Modify the Search Specification property using the value from the following table.

      Property Value

      Search Specification

      [Buscomp] = 'UMS Response' and [Repository Id] = RepositoryId()

      Siebel CRM displays the UMS Type Variables List Applet in Step 2. This applet references the UMS Type Variable business component. It displays the Response Field Name field and uses the UMS PickList Response Field picklist for this field. This picklist uses the following search specification when it references the UMS Pick List Field business component: 

      [Buscomp] = 'UMS Response'

      The UMS Pick List Field business component references the S_FIELD table. It does not include a search specification, so Siebel CRM does not filter the records that it gets according to the specifications that the repository contains. If the Siebel database contains multiple repositories, then Siebel CRM gets all the field names from all repositories, and then displays them in the picklist. This configuration might result in Siebel CRM displaying duplicate values that you cannot choose in the picklist. To correct this situation, you create a search specification that configures Siebel CRM to read data only from the current repository.

  3. Deliver your modifications.

  4. Repeat Step 1 to make sure the Response Field drop-down list does not display duplicate values.

Restricting the Objects That Developers Can Modify

In some situations, it might be helpful to restrict the objects that developers can modify, according to a date that you specify. If you enable this feature, then Siebel Tools applies these restrictions when the developer does the following work:

To restrict the objects that developers can modify

  1. Enable the system preferences:

    1. Click the Screens menu, click System Administration, and then click System Preferences.

      Note: In Web Tools, click the Tools menu and then click the System Preferences menu item.

    2. In the System Preferences list, set values for the following system preferences.

      System Preference Name System Preference Value

      EnablePerfFieldModification

      Set the value to TRUE.

      This system preference applies edit and copy restrictions to objects.

      Enable Object Version Control

      Set the value to TRUE.

      ServerEditRecordTimeStamp

      Enter the time when Siebel Tools must start using this configuration. For more information, see Setting the Server Edit Record Time Stamp Parameter.

  2. Log out of Siebel Tools.

Setting the Server Edit Record Time Stamp Parameter

When you set the ServerEditRecordTimeStamp parameter, you enter the time when Siebel Tools must start using this configuration. Use the following format:

MM/DD/YYYY

You can specify only the month, day, and year. You cannot specify minutes and seconds.

For example, to start using the configuration on October 9, 2014, enter the following value:

10/09/2014

In this example, Siebel Tools does the following:

  • Allows you to modify any object that includes a timestamp that occurs after October 9, 2014.

  • Does not allow you to modify any object that includes a timestamp that occurs before October 9, 2014. Developers can view or copy these objects, but not modify them.

  • Allows you to create new records, and then to modify these new records.

  • Allows you to copy any record, regardless of the timestamp.

Restricting Access to an Object

This topic describes how to restrict access to an object.

To restrict access to an object

  1. Determine the date that Siebel Tools most recently updated the object:

    1. In the Object List Editor, choose the record where you want to restrict access.

    2. Click Help, and then click About Record.

    3. In the Siebel Tools dialog box, in the Updated section, note the date that the On window shows.

  2. Set the value for ServerEditRecordTimeStamp to the date that you noted in Step iii.

Properties That Affect Database Performance

The following table lists the properties that affect database performance.

Table Properties That Affect Database Performance

Object Type Property

business component

The following properties affect database performance:

  • Force Active

field

The following properties affect database performance:

  • Force Active

  • Link Specification
  • Immediate Post Changes

multi value link

The following properties affect database performance:

  • Check No Match

multi value field

The following properties affect database performance:

  • Force Active

  • Link Specification

single value field

The following properties affect database performance:

  • Force Active

  • Link Specification

Overriding Restrictions That Prevent Developers from Modifying Objects

This topic describes how to log in to Siebel Tools so that the developer can modify any object, regardless of the timestamp restrictions that you place in Step1 of Restricting the Objects That Developers Can Modify.

To override restrictions that prevent developers from modifying objects

  1. In Microsoft Windows, click Start, All Programs, and then click the Siebel Tools installation folder.

  2. Right-click the Siebel Tools icon, and then click Properties.

  3. In the Siebel Tools Properties window, click the Shortcut tab, add the EditPerfFields switch to the Target field, and then click OK.

    For example:

    C:\Siebel\8.1\Tools_2\BIN\siebdev.exe /c 
"C:\Siebel\8.1\Tools_2\bin\enu\tools.cfg" /u SADMIN /p SADMIN /d Sample /
EditPerfFields

    Bold font indicates the switch that you add.

  4. Log in to Siebel Tools.

Exporting and Importing Repositories

This topic describes how to export and import repositories. It includes the following information:

Overview of Exporting and Importing Repositories

You can use the Database Configuration Wizard to export or import a repository. You can use this utility to do the following work:

  • Back up or restore a repository.

  • Move all repository objects to another environment that uses the same physical database schema that the source environment uses.

  • Export objects to an archive so that you can export or import only some objects. For more information, see Exporting Objects to an Archive.

For more information about how to use the Database Configuration Wizard, see Siebel Database Upgrade Guide and the Siebel Installation Guide for the operating system you are using.

Guidelines for Exporting and Importing Repositories

If you use the Database Configuration Wizard to import or export a repository, then it is recommended that you use the following guidelines:

  • If you import a custom repository, then the Database Configuration Wizard restores all the languages that are part of the predefined repository when you do the import. For example, if you archive repositories weekly, and if your development repository includes ENU and DEU, then the wizard includes ENU and DEU when it imports one of the archived repositories. For more information, see About Predefined Objects.

  • If you modify the repository, then make sure you perform Full Publish. Make a backup copy of the repository file in case you want to compare it to the contents of the updated repository. If necessary, you can use this comparison to verify that the import is identical to the backup.

  • You can use the database utilities that your RDBMS vendor provides to back up the entire contents of the Siebel database.

  • If you customize the source repository, then you can use the Migrate option of the Database Configuration Wizard. For more information, see Process of Migrating Repositories.

Character Encoding That Siebel CRM Supports to Import or Export Repositories

The following table describes the character encoding that Siebel CRM supports when it imports or exports a repository. These databases must use the same Siebel version.

Table Character Encoding That Siebel CRM Supports to Import or Export a Repository

Source Database Target Database

Code Page

Code Page

Unicode

Unicode

Code Page

Unicode

Where the Database Configuration Wizard Saves Log Files

If you export a repository in a Windows or UNIX environment, and if you use the Export Repository option of the Database Configuration Wizard, then this wizard saves log files in following directories:

  • SIEBSRVR_ROOT\log\exprep\output

  • SIEBSRVR_ROOT\log\exprep\state

Exprep is the default process name for the exprep utility. You can modify this value.

Importing Repositories in Windows Environments

This topic describes how to import repositories in a Windows environment.

To import repositories in Windows environments

  1. Make sure Siebel CRM supports the databases that you intend to use.

    For more information, see Character Encoding That Siebel CRM Supports to Import or Export Repositories.

  2. In Microsoft Windows, navigate to Start Programs menu, Settings, Control Panel, and then click Services.

  3. Stop all Siebel Servers.

    For more information, see Siebel System Administration Guide and the Siebel Installation Guide for the operating system you are using.

  4. Click the Start Programs menu, Programs, Siebel Enterprise Server Configuration 8.0, and then click Database Server Configuration.

  5. In the Database Configuration Wizard, enter information when this wizard prompts you, and then click Next to continue.

  6. Choose Import Repository when the wizard prompts you to specify a database operation.

  7. Specify the following items:

    • To import your custom 8.x repository

    • The location of where the custom CustRep.dat file resides

  8. When the wizard displays the Configuration is Complete window, choose one of the following options, and then click Next:

    • Yes Apply Configuration Changes Now. The wizard saves the configuration information that you entered, and you can open the Siebel Upgrade Wizard in Step 10.

    • No I Will Apply Configuration Changes Later. The wizard saves the configuration information that you entered, but you cannot open the Siebel Upgrade Wizard in Step 10.

  9. In the Configuration Parameter Review window, review the configuration that you entered. To modify a value, click Back to return to the window that includes the parameter you want to modify, modify the parameter, and then click Next.

  10. When the wizard prompts you to run the configuration, click one of the following:

    • No. The wizard does not save the configuration information that you entered. You must enter the database configuration parameters again.

    • Yes. The wizard saves the configuration information that you entered.

  11. Click OK.

    The Database Configuration Wizard does one of the following, depending on the choice that you make in Step 8:

    • Apply now. Opens the Siebel Upgrade Wizard, and then calls the SQL generator to create the SQL scripts.

    • Apply later. Saves the configuration information, but does not open the Siebel Upgrade Wizard. You can restart the configuration, and then run the Upgrade Wizard later. For more information, see Importing or Exporting Repositories at a Later Time.

Importing Repositories in UNIX Environments

This topic describes how to import repositories in a UNIX environment.

To import repositories in UNIX environments

  1. Do Step 1 and Step 3 of Importing Repositories in Windows Environments .

  2. Make sure $SIEBEL_ROOT is the current folder.

  3. Run a script, depending on the following UNIX shell that you are using:

    • Korn shell. Run siebenv.sh.

    • C shell. Run siebenv.csh.

  4. Make sure that the following environment variables use the following values:

    • SIEBEL_ROOT. This path must end in siebsrvr (for example, /usr/siebel/siebsrvr).

    • LANGUAGE. Determines the language that the Database Configuration Wizard uses. The value of this variable is a text string that identifies the language (for example, enu for English).

  5. Run the following command to start the Database Configuration Wizard:

    $install_path/config/config -mode dbsrvr

  6. In the Database Configuration Wizard, do the following:

    • Enter information when the wizard prompts you.

    • Use the Next and Back button to navigate between dialog boxes.

    • Choose Import Repository when the wizard prompts you to choose a database operation.

    • Specify to import your 8.x repository.

    • Identify the location of where the custom CustRep.dat file resides.

  7. After you enter all the requested information, the wizard displays a message that is similar to the following. Click Next to continue:

    Configuration is complete: configuration parameters will be saved to $Masterfile 
file when the wizard completes. Please run the following command line after you 
exit from this configuration wizard. This command will deploy the process you 
configured to the database.

    $SIEBEL_ROOT/siebsrvr/bin/srvrupgwiz /m $SIEBEL_ROOT/siebsrvr/bin/$Masterfile

  8. The wizard displays the values that you entered in the Parameter Review window. To modify a value, click Back to return to the appropriate window.

  9. The wizard prompts you to click one of the following values:

    • Yes. The wizard saves the configuration in a master file in the $SIEBEL_ROOT/bin folder. It does not start the Upgrade Wizard. For information about how to start the Upgrade Wizard, see Siebel Database Upgrade Guide.

    • No. The wizard does not save the configuration that you entered.

Exporting Repositories

To export a repository when you use:

Importing or Exporting Repositories at a Later Time

If you use the Database Configuration Wizard to export or import a repository, then it saves the values that you specify to the master_exprep.ucf file in the SIEBSRVR_ROOT\ folder. After the wizard finishes collecting information from you, it prompts you to export or to not export. If you choose not to export or not to import, then you can run the following command to do the export or import at a later time:

siebupg.exe /m master_exprep.ucfs

Upgrading Repositories

The Siebel Application Upgrader is a utility that you can use to get new features from the latest software release while preserving the custom configuration that you created in the current repository. It allows you to do the following:

  • Compare your custom configuration to the modifications that a new Siebel CRM release contains.

  • Receive notifications about conflicts between the customizations that you make and the new release.

  • Merge any differences between objects.

  • Choose the modifications to apply and manually override modifications.

  • Merge objects with versions, including task UI objects and workflow processes. It copies version 1 through version n from the prior custom repository to the new custom repository. It merges version 0 from the prior repository with the new custom repository. This configuration results in version n + 1 in the new custom repository.

  • Reduce the time required to upgrade Siebel CRM.

You can use the Application Upgrader to merge an entire custom repository with another repository. To merge only part of a repository, you must import the repository. For more information, see Exporting and Importing Repositories. For more information about the Application Upgrader, see Siebel Database Upgrade Guide.

To upgrade repositories

  1. Click the Tools menu, Upgrade, and then click Upgrade Application.

  2. In the Merge Repositories dialog box, choose the repositories to merge, and then click Merge.

    Siebel Tools does the following:

    • Starts the upgrade.

    • Displays any differences between objects and properties.

    • Displays any differences between objects and properties for different versions of task UIs and workflow processes.

Identifying Conflicts That Occur During Upgrades

This topic describes how to identify merge conflicts between objects that Siebel Tools added or modified during a repository merge. A merge conflict is a scenario in which a customer changed an object in the current customer repository, and Siebel CRM changed that same object to a different value in a new version of the Siebel repository. Consequently, the attribute for the object is different when the following three repositories are compared: the current customer repository, the current Siebel repository, and the new version of the Siebel repository.

To identify conflicts that occur during upgrades

  1. Make sure you finish upgrading repositories.

    For more information, see Upgrading Repositories.

  2. In Siebel Tools, click the Screens menu, Application Upgrader, and then click Application Upgrade Object List.

  3. In the Application Upgrades list, right-click the record of the merge that you want to analyze, and then click Hierarchy Reports.

    Siebel Tools displays the hierarchy report, which includes the objects that Siebel Tools added or modified during a merge. The report includes the following types of objects:

    • Objects that include a valid value for each field value.Siebel Tools modified these objects during the merge. An N or a Y in a binary field is an example of a valid value.

      For these objects, the Status field designates added objects or objects with modified attributes. For added objects, an N appears in the Attributes field because none of the attributes are modified. For objects with modified attributes, a Y appears in the Attributes field, and the modified attributes appear in the Attributes pane.

    • Objects that include an asterisk (*) for each field value.Siebel Tools modified children of these objects during the merge, or Siebel Tools modified dependent objects of these objects during the merge.

  4. To view information about merge details, complete the following steps:

    1. Expand and navigate through the hierarchical tree in the Object Types pane to select a parent or child object type.

      The starting List of Objects pane shows the objects for the parent object type that you select, and the next List of Objects pane shows the objects for the child object type that you select.

    2. Click an object in a List of Objects pane.

      In the Attributes pane, Siebel Tools displays any merge conflicts for the object.

  5. (Optional) To filter the objects in the report, select one of the following values in the Filter drop-down list, and then click Go:

    • Siebel and Customer Modified. Siebel Tools displays only objects that Oracle or you modified. These objects have a Y in the In Prior Standard, In Prior Customized, and In New Standard fields.

    • Siebel Modified.Siebel Tools displays only objects that Oracle modified or added. These objects have an N in the In Prior Standard and In Prior Customized field and a Y in the In New Standard field.

    • All.Siebel Tools displays all modified or added objects.

  6. (Optional) To filter the merge conflicts in the Attributes pane, select or clear the Critical Only check box as follows, and then click Go:

    • Select the check box to show only critical merge conflicts.

    • Clear the check box to show all merge conflicts.

  7. (Optional) To display the dependencies for an object, complete the following steps:

    1. Click an object in a List of Objects pane.

      If you want to display the dependencies for an additional object, then hold down the CTRL key, and click the additional object in the List of Objects pane.

    2. Click Show Dependencies.

      If the object has no dependencies, then the Show Dependencies button is disabled.

      Siebel Tools displays the dependent objects that it modified and the attributes for these objects.

    3. Click Back to return to the hierarchy report.

Process of Migrating Repositories

Configuration and other changes must be migrated from your development environment to your downstream environments, such as test or production. To perform this migration, use the Siebel Migration application. For more information, see Siebel Database Upgrade Guide.

Deleting Repositories

You can delete repositories either using the repimexp utility or the RRCleanup utility. You use the repimexp utility by using the option /a t to delete the existing repository.

You use the RRCleanup utility to delete the existing repository or the orphan records from the Siebel database. Using this utility, you can delete:

  • Orphan records.

    This option does not require you to pass a repository name as an argument to the RRCleanup utility because orphan records do not have the valid repository in the Siebel system and the repository does not exist in the S_REPOSITORY table. The RRCleanup utility deletes the LOVs (S_LST_OF_VAL) as well for orphan workspaces.

  • Repository data.

    This option passes a valid repository as an argument to the RRCleanup utility to delete repository data from all repository tables. The RRCleanup utility deletes the LOVs (S_LST_OF_VAL) as well for this repository.

    Note: A repository can contain multiple integration branches with each branch containing a copy of List of Value. Deletion of repository has a cascading effect on branches and LOVs.

In Siebel Tools, the RRCleanup utility is located at this location:

<Siebel_Home>\BIN\RRCleanup.exe

In the Siebel Server, the RRCleanup utility is located at this location:

<Siebel_Home>\ses\siebsrvr\BIN\RRCleanup.exe

To run the RRCleanup utility

  1. Open the Command Prompt window from your computer by clicking the Start button and then selecting the Run option.

    The Run window appears.

  2. Enter the value CMD in the Open field.

    The Command Prompt window appears.

  3. Change the directory in the Command Prompt window using one of the following commands:

    cd <Siebel_Home>\BIN

    or

    cd <Siebel_Home>\ses\siebsrvr\BIN

  4. Run the RRCleanup.exe utility.

  5. The Command Prompt window opens and displays the following arguments and parameters, which you can use to run the RRCleanup utility:

    • -t Siebel Table Owner (required)

    • -u Username (required)

    • -p Password (required)

    • -o ODBC Data Source (required)

    • -l Log File Name (default: RRCleanup.log)

    • -r Repository Name (delete Runtime Repository data for repository name pass. e.g. “Siebel Repository” )

    • -a Orphan Flag (Pass Y if required to delete only orphan records)

    • -s Siebsrvr/Tools Installation path specified (required)

    • -b Repository Type ((R)unTime, (B)Both (DR and RR)) (required)

  6. Use the following command to delete a particular repository data from repository tables:

    RRCleanup.exe -t "Table Owner" -u "Siebel User Name" -p "Siebel User Name 
Password" -r "Repository Name" -o "ODBC Data Source" -s "Siebsrvr/Tools home location" -b Repository Type
    Note: For the -r argument, you can pass only one repository at a time as a parameter. For the -b argument, you can pass either of the repository types as parameter such as -b R to delete data from runtime repository tables or –b B to delete data from all repository tables.

  7. Use the following command to delete orphan records:

    RRCleanup.exe -t "Table Owner" -u "Siebel User Name" -p "Siebel User Name 
Password" -a Y -o "ODBC Data Source" -s "Siebsrvr/Tools home location" -b Repository Type
    Note: In one command, you can delete either a repository or orphan records but not both. However, if you pass a repository as parameter and the orphan flag is also set to true then the orphan takes precedence.

  8. View the output stages that represent the progress of the tasks performed by the utility to ensure that the RRCleanup utility is run successfully.