Update the SDK Table

Importing and Exporting Data Using the Deployment Manager 5-17 table, you must check the schema name in the SDK_SCHEMA column, and if necessary, manually change it to the schema name on the target system where the Oracle Identity Manager database is running. To update the schema name in the SDK_SCHEMA column, run a SQL query similar to the following with SQLPlus on Oracle Database installations or with SQL Query Analyzer on Microsoft SQL Server installations: UPDATE SDK SET SDK_SCHEMA=target system schema name If you do not update the schema name in the SDK_SCHEMA column, an error similar to the following might be generated when you import other XML files that modify user-defined field UDF definitions: CREATE SEQUENCE UGP_SEQ java.sql.SQLException: ORA-00955: name is already used by an existing object

5.5.16 Remove Data Object Fields Before Importing Event Handlers as Dependencies

The Deployment Manager does not import event handlers that include data object fields if the event handlers are imported as dependencies. For this reason, you must remove the data object fields from any event handlers that you want to import as dependencies with the Deployment Manager.

5.6 Best Practices for Using the Horizontal Migration Utility

The following are some of the suggested practices and pitfalls to avoid while by using the horizontal migration utility: ■ Export system objects only when necessary. See Export System Objects Only When Necessary on page 5-13. ■ Export related groups of objects. See Export Related Groups of Objects on page 5-14. ■ Check all listing before importing or exporting. See Check All Warnings Before Importing on page 5-15. ■ Create a backup of the database. Back Up the Database on page 5-16. ■ Provide filter criteria as specific as possible in the Config.xml file. See step 3 in Running the Horizontal Migration Utility on page 5-10. For example, consider the following filter criteria: entityDetails EntityTypeCustomResourceBundlesEntityType FilteringCriteria Attribute NameFileNameName FilterFilter Attribute FilteringCriteria entityDetails Instead of using the asterisk wildcard character as the filter criteria, specify a file name or combine a file name with wildcard characters, such as Filter.propertiesFilter. 5-18 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

5.7 Troubleshooting

Table 5–2 lists the troubleshooting steps that you can perform if you encounter a failure: Table 5–2 Troubleshooting Deployment Manager Problem Solution In Oracle Identity Manager 11g Release 1 11.1.1, scheduled job has a dependency on scheduled task. Therefore, scheduled task must be imported prior to scheduled job. As a result, if a XML file has scheduled job entries prior to scheduled task entries, then importing the XML file using Deployment Manager fails with the following error message: [exec] Caused By: oracle.iam.scheduler.exception.SchedulerExceptio n: Invalid ScheduleTask definition [exec] com.thortech.xl.ddm.exception.DDMException Open the XML file and move all scheduled task entries above the scheduled job entries. Deployment Manager export fails for any object. User is prompted with Export Failed dialog box, and no exception is found in the server log. When you look at the JRE console, you can see the following: java.security.AccessControlException: access denied java.io.FilePermission PATH_AND_NAME_OF_THE_FILE Perform the following steps: 1. Modify your java.policy in the JRE_HOMElibsecurity directory. 2. Replace the existing policy file content with the following: grant{ permission java.security.AllPermission; }; 3. Restart the browser to laod the policy again. You can now export the data. The following error occurs while importing an XML file: Caused by: oracle.iam.reconciliation.exception.ConfigExcept ion: Profile :Xellerate User InvalidAttributes : Perform any one of the following: ■ Remove the attribute on which the error is generated from the XML, and then try importing. ■ Create the missing UDF or other attributes by using configuration service, and then retry the import. ■ Export the UDF shown as missing dependency. Import this UDF first before importing the current XML. Importing approval policy might result in the following error: weblogic.kernel.Default self-tuning] [userId: xelsysadm] [ecid: f9e72ab2a292a346:-188377b2:12f96ae9676:-8000-000 0000000000047,0] [APP: oim11.1.1.3.0] Exception thrown {0}[[ oracle.iam.platform.entitymgr.ProviderException: USER_NOT_FOUND An approval policy rule is invalid if it points to an entity user or organization that does not exist in Oracle Identity Manager. These invalid approval rules must be corrected to point to a valid entity user or organization before the import.