Additional Database Connection Information for Oracle Data Integrator
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.Parts
» Oracle Fusion Middleware Online Documentation Library
» Types of Patches That can be Used with OPatch
» OPatch System Requirements Backup and Recovery Considerations for Patching
» Patching with a Local Middleware Home
» Patching with a Shared Middleware Home
» Patching a Fusion Middleware Product Patching Artifacts Deployed Outside the Oracle Home
» Using the OPatch Property File
» Configuring Node Manager Beginning with OPatch release 11.1.0.8.2, the -auto
» Using the -auto Option with the -domain Option The -auto option should be used
» Sample Output for the apply Command
» Deploying Patched Artifacts to WebLogic Servers
» Listing the Source Oracle Homes
» Listing the Domains Created from the Middleware Home or Oracle Home
» Listing the Applicable Oracle Homes for a Patch
» Listing Patches Applied to an Oracle Home or WebLogic Domain
» Starting or Stopping a Runtime Instance
» Notes About Patching the MDS Repository Setting the Machine Name and Listen Address
» Summary of the Oracle Fusion Middleware Patching Process
» Special Instructions for Patching Oracle WebCenter
» Special Instructions for Patching Oracle Identity and Access Management Release 11.1.1.3.0
» Stop the Servers and Processes
» Back Up Your Middleware Home, Domain Home and Oracle Instances
» Back Up Your Database and Database Schemas
» Back Up Additional Configuration Information
» Patch Oracle WebLogic Server
» Product Installers About the Installers Used for Patching
» Patch Set Installers About the Installers Used for Patching
» Download the Installer Download and Start the Product Installer or Patch Set Installer
» Start the Installer Download and Start the Product Installer or Patch Set Installer
» Patch Set Installer Instructions
» Post-Patching Tasks If Your Starting Point is Release 11.1.1.2.0
» Post-Patching Tasks If Your Starting Point is Release 11.1.1.3.0
» Post-Patching Tasks If Your Starting Point is Release 11.1.1.4.0
» Upgrading System Components Post-Patching Tasks for System Components
» Updating Configuration Properties in Oracle Identity Federation
» Updating Oracle Configuration Manager Windows Only
» Resolving JDBC Errors in Oracle Reports and Oracle Portal
» Updating the Configuration in SSL-Enabled Oracle Portal Instances
» Updating Fusion Middleware Shared Libraries
» Updating Configurations and Stores
» Enabling WS-AtomicTransaction Post-Patching Tasks for Your WebLogic Server Domain
» Removing the tmp Folder for SOA Composer and BPM Workspace
» Updating the soa-infra Application in Warning State
» Run soa-upgrade.py to Update the Policy Store and Deploy a Shared Library
» Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled
» Committing or Reverting Open Edit Sessions in SOA Composer
» Saving and Restoring XEngine Customizations for Oracle B2B
» Updating Oracle IPM in Oracle Enterprise Content Management Suite
» Updating Oracle Application Adapters for Oracle Enterprise Content Management Suite
» Applying Patch 12369706 for Oracle Information Rights Management
» Adding New OWSM Pre-Defined Policies
» Updating an Oracle Service Bus Domain After Applying the Latest Patch Set
» Deleting Oracle WebLogic Server 11g Release 1 10.3.3 You need to create a new
» Updating Oracle Business Intelligence Code Grants
» Updating Oracle Business Intelligence Catalogs
» Update the rtd_ils Resource Type Using WLST Perform the following to add
» Add Permissions to the BIAdministrator Principle Using EM The steps in this
» Finalizing Repository Patching Post-Patching Tasks for Oracle Data Integrator
» Reconfiguring the Java EE Agent
» Reconfiguring the ODI Standalone Agent
» Reconfiguring Oracle Enterprise Manager Properties
» Update Your Schemas with Patch Set Assistant Start the Servers and Processes
» Verify Your Patch Installation
» Which Schemas Need to be Updated with Patch Set Assistant?
» General Information about the Patch Set Assistant
» Starting the Patch Set Assistant
» Command Line Syntax Running the Patch Set Assistant
» Additional Database Connection Information for Oracle Data Integrator
» Sample Commands Verifying the Schema Version Number After Update
» Checking for Invalid Database Objects Loading the Oracle SOA Suite Purge Scripts
» Patch Set Assistant Log Files
» Performing General Oracle Fusion Middleware Pre-Patching Steps
» Saving Your OmniPortlet and WebClipping Customizations
» Purging Old Documents in MDS for WebCenter Spaces
» Upgrading Oracle Universal Content Management 10
» Removing the LD_LIBRARY_PATH Entry from the setDomainEnv Script
» Choosing Your Oracle WebCenter Update Method
» Updating Oracle WebCenter Using WLST Commands
» Configuring Node Manager Updating Oracle WebCenter Using Node Manager and Automated Script
» Verifying Your Node Manager Configuration
» Updating Your Oracle WebCenter Software and Database Schemas
» Example 1: No Optional Parameters Specified If no optional parameters are
» Example 2: Specifying a Properties File and Setting the Value of user.config.file If you
» Example 3: Specifying a Properties File and Administrator Password If you specify a
» Example 4: Specifying a Properties File, Administrator Password, and Node Manager
» Properties That can be Set in the Upgrade Properties File
» Formatting Your Properties File You must make sure you escape values correctly
» Procedure for Migrating Oracle Wiki Pages and Blogs
» Troubleshooting Problems During Wiki Migration
» Restoring Your OmniPortlet and WebClipping Customizations
» Upgrading Oracle WebCenter Custom Portal Managed Servers
» Migrating Content Presenter Custom Templates
» Updating Oracle WebCenter Portal Schemas
» Configuring an Identity Asserter
» Configuring the Credential Store
» Updating Multi Calendar Layouts Extending a Domain to Install Oracle WSM Policy Manager
» Setting the Web Context Root on the UCM Connection
» Configuring Group Space Workflows
» Allowing Group Spaces to Have a Default Template Set
» Updating the Timezone Attribute in WebCenter Spaces
» Updating the Group Spaces Display Mode
» Migrating WebCenter Spaces Custom Library
» Starting Oracle BPM to Login to WebCenter Spaces
» Configuring Web Services Security for Discussions
» Enabling Process Spaces in a Patched Domain
» Extending a WebCenter Domain to Add Oracle WebCenter Analytics Collector
» Upgrading a WebCenter Custom Application to Add Portal Framework Features
» Prerequisites Preparing to Patch
» Before You Begin Preparing to Patch
» Backing Up Oracle Fusion Middleware
» Patching Oracle WebLogic Server 10.3.3. to 10.3.5
» Instructions for Updating Oracle Identity Manager
» Configuring Oracle Identity Manager Design Console
» Setting System Properties for LDAP Sync and Referential Integrity
» Updating Oracle Access Manager 11.1.1.3.0 to 11.1.1.5.0
» Updating Oracle Adaptive Access Manager 11.1.1.3.0 to 11.1.1.5.0
» Updating Oracle Identity Navigator 11.1.1.3.0 to 11.1.1.5.0
Show more