Additional Database Connection Information for Oracle Data Integrator

Updating Your Schemas with Patch Set Assistant 4-9 name ; Replace schema_name with the value supplied in the -schemaUserName parameter from the command line. The value UPGRADED flag=Y indicates that schema has been upgraded to 11.1.1.5.0. If the status appears as INVALID then the schema update failed. You should examine the logs files to determine the reason for the failure. For more information, see Section 4.6, Patch Set Assistant Log Files .

4.5.7 Checking for Invalid Database Objects

If you are using an Oracle database, you should recompile database objects after running the Patch Set Assistant by connecting to the database as SYS and running the following from SQLPlus: SQL ?rdbmsadminutlrp.sql This will compile the database objects that were updated by Patch Set Assistant. Then issue to following query to ensure there are no longer any invalid database objects: SELECT owner, object_name FROM all_objects WHERE status=INVALID; None of the database objects for the updated schema should be invalid at this point. If there are any, run the utlrp.sql command again and check again.

4.5.8 Loading the Oracle SOA Suite Purge Scripts

When the amount of data in Oracle Fusion Middleware databases grows very large, maintaining the databases can become difficult and can affect performance. Oracle Fusion Middleware 11g Release 1 11.1.1.4.0 and later provide a set of tools that can help you purge the Oracle Fusion Middleware of unneeded data. When a new Oracle Fusion Middleware user installs the latest Oracle SOA Suite schemas using the Repository Creation Utility RCU, stored procedures required by the Oracle SOA Suite purge scripts are automatically installed in the database. However, if you are running Oracle Fusion Middleware 11g Release 1 11.1.1.2.0 or Release 1 11.1.1.3.0, these stored procedures are not installed automatically. As a result, after you run the Patch Set Assistant to update your Oracle SOA Suite schemas to the latest version, you must manually install the necessary database objects using the following procedure. This procedure is necessary if you want to use the purging capabilities provided by Oracle SOA Suite 11g Release 1 11.1.1.4.0 or later: 1. Locate, download, and unpack the latest Oracle Fusion Middleware 11g Repository Creation Utility RCU software archive. For more information, see Obtaining RCU in the Oracle Fusion Middleware Repository Creation Utility Users Guide. Note: Unlike major releases which use Upgrade Assistant to upgrade one or more schemas at a time, Patch Set Assistant only updates a single schema the one passed by -schemaUserName. In particular, the RUU component Schema Version Registry is not modified by Patch Set Assistant so its version number will remain at 11.1.1.3.0. 4-10 Oracle Fusion Middleware Patching Guide The directory where you unpack the RCU software is referred to as the RCU_HOME directory. 2. Using SQLPlus, connect to the database where the Oracle SOA Suite schemas are installed using the database user that owns the SOAINFRA schema. 3. Run the following script to load the database objects required for purging Oracle SOA Suite data: RCU_HOME rcuintegrationsoainfrasqlsoa_purgesoa_purge_scripts.sql 4. Run the following script to load the database objects required for verifying the Oracle SOA Suite data in the database: RCU_HOME rcuintegrationsoainfrasqlverifysoa_verify_scripts.sql After you load the database objects using the provided SQL scripts, refer to Managing Database Growth in the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite for more information.

4.6 Patch Set Assistant Log Files

The Patch Set Assistant writes log files to the following locations: On UNIX operating systems: ORACLE_HOME upgradelogspsa timestamp .log On Windows operating systems: ORACLE_HOME \upgrade\logs\psa timestamp .log Some components will create a second log file called psa timestamp .out, also in the same location. The timestamp will reflect the actual date and time that Patch Set Assistant was run. Should any failures occur when running Patch Set Assistant, these log files will be needed to help diagnose and correct the problem; do not delete them. You can alter the contents of your log files by specifying a different -logLevel from the command line. Some of the operations performed by the Patch Set Assistant may take longer to complete than others. If you want to see the progress of these long operations, you can see this information in the log file, or you can use the following query: SELECT VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY WHERE OWNER= schema_ name ; In the query results, the STATUS field will be either UPGRADING or UPGRADED during the schema patching operation, and will become VALID when the operating is finished.