Starting or Stopping a Runtime Instance
2.5 Troubleshooting OPatch in a Fusion Middleware Environment
This section describes common issues you may encounter when running the OPatch utility in a Fusion Middleware environment.2.5.1 Notes About Patching the MDS Repository
For special information about patching the MDS repository, refer to Understanding the MDS Repository in the Oracle Fusion Middleware Administrators Guide.2.5.2 Setting the Machine Name and Listen Address
The machine name of the Administration Server and Managed Servers must be set to a valid value. It cannot be set to blank or None. The listen address of the Administration and Managed Servers must be set to the real physical hosts address hostname, FQDN, or IP address. It cannot be set to blank or localhost. These values need to be properly set only once; you will not need to reset them should you ever need to patch your software. To set the machine name and listed address of the Managed Servers: 1. Open the Administration Console. Patching Oracle Fusion Middleware with Oracle OPatch 2-25 2. In the Domain Structure, navigate to domain_name Environments Machines. 3. If your WebLogic Server is running in Production Mode, click the Lock Edit button on the left hand side. If your WebLogic Server is running in Development Mode, this step is not needed. 4. Click the New button to create a new machine. Specify a name and select the operating system. 5. Select the machine you just created, go to Configuration Node Manager and change the Listen Address to the host on which the Node Manager is listening, then click the Save button. 6. In the Domain Structure, navigate to domain_name Environments Servers. 7. For each Managed Server, assign the machine you just created. In the Listen Address field, specify the name of the host on which the Node Manager is listening. Click Save when you are finished. 8. If your WebLogic Server is running in Production Mode, click the Activate Changes button on the left hand side. If your WebLogic Server is running in Development Mode, this step is not needed. To set the machine name and listen address of the Administration Server: 1. Stop the Administration Server and all Managed Servers. 2. Back up the config.xml file in the domain. The default location of this file is the config directory inside your Domain home. 3. Modify the existing config.xml file as follows: a. Find the following line: nameAdminServername b. Add the following lines: machine host_name machine listen-address host_name listen-address c. Save the file. 4. Restart the Administration Server and all the Managed Servers. If you encounter any problems, revert back to the saved version of the config.xml file and contact Oracle Support. 2-26 Oracle Fusion Middleware Patching GuideParts
» 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