Reconfiguring the ODI Standalone Agent

4 Updating Your Schemas with Patch Set Assistant 4-1 4 Updating Your Schemas with Patch Set Assistant The Patch Set Assistant is used in patch set releases only to update the database schema of an Oracle Fusion Middleware component. This tool updates 11g Release 1 schema versions 11.1.1.2.0, 11.1.1.3.0, and in some cases, 11.1.1.4.0 to version 11.1.1.5.0. See Table 4–1 for specific information. If your existing schema version is earlier than 11.1.1.2.0, you must migrate to version 11.1.1.2.0 before you can run the Patch Set Assistant. See Appendix B, Using Patch Assistant to Migrate from 11g Release 1 11.1.1.1.0 to Release 1 11.1.1.2.0 for more information. If you are interested in creating new schemas or dropping existing schemas, you must use the Repository Creation Utility RCU. Information is provided in Oracle Fusion Middleware Repository Creation Utility Users Guide. This chapter contains the following topics: ■ Section 4.1, Which Schemas Need to be Updated with Patch Set Assistant? ■ Section 4.2, Special Instructions for Standalone Oracle Portal Repository Schemas ■ Section 4.3, Special Instructions for Oracle Service Bus Schemas Installed in a Microsoft SQL Server Database ■ Section 4.4, Before You Begin Using the Patch Set Assistant ■ Section 4.5, Running the Patch Set Assistant ■ Section 4.6, Patch Set Assistant Log Files 4.1 Which Schemas Need to be Updated with Patch Set Assistant? The component schemas in Table 4–1 default names shown must be updated with the Patch Set Assistant in order to update them to 11g Release 1 11.1.1.5.0. Remember to also update the dependent schemas in addition to the component schemas for your own product. Note: Some products, such as Oracle Portal, are not released in 11.1.1.5.0. If you run the Patch Set Assistant for those products, you would be updating them to the latest available version, not 11.1.1.5.0. 4-2 Oracle Fusion Middleware Patching Guide Table 4–1 Schemas That Require Updating for the Latest Release Component Schemas Dependencies Required For Common Schemas prefix _IAU None. 11.1.1.2.0 to 11.1.1.5.0 11.1.1.3.0 to 11.1.1.5.0 prefix _MDS None. 11.1.1.2.0 to 11.1.1.5.0 11.1.1.3.0 to 11.1.1.5.0 11.1.1.4.0 to 11.1.1.5.0 Oracle Portal prefix _PORTAL None. 11.1.1.2.0 to 11.1.1.4.0 11.1.1.3.0 to 11.1.1.4.0 Oracle Internet Directory ODS NOTE: The Oracle Internet Directory schema ODS cannot be prepended with a custom prefix. None. 11.1.1.2.0 to 11.1.1.5.0 11.1.1.3.0 to 11.1.1.5.0 11.1.1.4.0 to 11.1.1.5.0 Oracle Identity Management prefix _OIM The prefix _MDS and prefix _SOAINFRA schemas must be updated first. 11.1.1.3.0 to 11.1.1.5.0 Oracle Adaptive Access Manager prefix _OAAM The prefix _MDS schema must be updated first. 11.1.1.3.0 to 11.1.1.5.0 Oracle Adaptive Access Manager Partition Support prefix _OAAM_PARTN The prefix _MDS schema must be updated first. 11.1.1.3.0 to 11.1.1.5.0 Oracle Business Intelligence prefix _BIPLATFORM The prefix _MDS schema must be updated first. 11.1.1.3.0 to 11.1.1.5.0 Oracle Data Integrator Master and Work Repository prefix _ODI_REPO None. 11.1.1.3.0 to 11.1.1.5.0 Oracle SOA Suite prefix _SOAINFRA The prefix _MDS schema must be updated first. 11.1.1.2.0 to 11.1.1.5.0 11.1.1.3.0 to 11.1.1.5.0 Oracle WebCenter Schemas prefix _WEBCENTER The prefix _MDS schema must be updated first. 11.1.1.2.0 to 11.1.1.5.0 11.1.1.3.0 to 11.1.1.5.0 prefix _DISCUSSIONS prefix _DISCUSSIONS_CRAWLER None. 11.1.1.2.0 to 11.1.1.5.0 11.1.1.3.0 to 11.1.1.5.0 Note: The WebCenter schemas must be updated in the following order: MDS first, followed by WEBCENTER, then DISCUSSIONS, then DISCUSSIONS_CRAWLER. If the Discussions Crawler schema has not previously been installed using RCU, then migrating Discussions will automatically install the Discussions Crawler schema, assigning the same password as the Discussions schema. If you then attempt to update the Discussions Crawler schema individually, the Patch Set Assistant will warn that the schema has already been updated.