Installation and Upgrade Guides › SiteMinder Upgrade Guide › Upgrade Procedures from 5.x › Step 1: Upgrade the 5.x Policy Server to 6.x › Upgrade a 5.x Policy Store › Upgrade an Oracle Policy Store › Migrate a 5.x Oracle Policy Store

Migrate a 5.x Oracle Policy Store

Important! Before running a SiteMinder utility or executable on Windows Server 2008, open the command line window with Administrator permissions. Open the command line window this way, even if your account has Administrator privileges. For more information, see the release notes for your SiteMinder component.

To migrate a 5.x Oracle policy store

1. Export the 5.x policy store using the 5.x version of smobjexport.

   Consider the following:

   • If your key store resides in the policy store, be sure to use the -k option when exporting the policy store. By default, policy store keys are not included in an export.
   • If the r6.0 SP6 Policy Server uses the same encryption key that is stored in the 5.x policy store, you do not need to export the policy store data in clear–text. Exporting sensitive data in clear–text is necessary only if the 5.x and 6.x Policy Servers use different encryption keys.
2. Configure a new Oracle database as an r6.0 SP6 policy store.

   Note: For more information about configuring an Oracle database as a policy store, see the Policy Server Installation Guide.

3. Import the 5.x policy store data using the r6.0 SP6 version of smobjimport.

   Important! If your 5.x policies defined user directories with the OCI namespace, see Modify the 5.x smdif File With an OCI Namespace User Directory before importing the policy store data.

   Consider the following:

   • If you exported sensitive data in clear–text, be sure to import the policy store data using the -c option.
   • If you exported agent keys, be sure to use the -k option when importing the policy store. By default, policy store keys are not included in an import.

   Note: For more information about using smobjimport, see the Policy Server Installation Guide.

4. (Optional) If the 5.x policy store data you imported contains sensitive data in clear–text, use the smreg utility to encrypt the SiteMinder super user password.

   Note: For more information about using the smreg utility, see the Policy Server Installation Guide.

5. (Optional) Delete the SiteMinder data from the 5.x policy store using the sm_oracle_ps_delete script.

   Note: For more information about using this script, see the 5.x version of the Policy Server Installation Guide.