This chapter contains information about manual tasks that should be performed after you have completed patching your existing Oracle Forms and Reports 11g Release 2 (11.1.2). Some of the tasks may not apply to your environment as you may not be using the products in question.
The following section is included in this chapter:
A system component is a manageable process that is not deployed as a Java application. Instead, a system component is managed by Oracle Process Manager and Notification (OPMN). For more information, see "Understanding Key Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide.
Oracle Fusion Middleware system components include the following:
Products included with Oracle Web Tier, including Oracle HTTP Server and Oracle Web Cache.
Products included with Oracle Identity Management, including Oracle Virtual Directory and Oracle Internet Directory.
Products included with Oracle Portal, Forms, Reports and Discoverer.
Products included with Oracle Business Intelligence, including BI Server, BI Scheduler and BI Presentation Services.
Products included with Oracle Data Integrator.
If you have patched one or more of these components, the tasks in this section should be performed. For more information about system components, refer to "Understanding Key Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide.
The following tasks should be performed:
Section 4.1.3, "Resolving JDBC Errors in Oracle Reports and Oracle Portal"
Section 4.1.5, "Generating the BASE64 Encoded Encryption Key for OPSS"
Section 4.1.6, "Enabling Dynamic Audit Metadata Model for OPSS Running in JavaSE Mode"
Section 4.1.7, "Configuring Diagnostic Framework Dump Sampling"
Section 4.1.8, "Adding Batik Library Jar Files to the JRF Template for IBM WebSphere"
This step is required for any system component that is associated with a WebLogic domain. In some cases (for example, Oracle Web Tier and Oracle Internet Directory), you can choose to create standalone system components that are not associated with any domain; in these cases, you do not have to perform this procedure.
After you have patched your system component software that is associated with a WebLogic domain, you must run the ORACLE_HOME/opmn/bin/upgradenonj2eeapp.sh (on UNIX operating systems) or ORACLE_HOME\opmn\bin\upgradenonj2eeapp.bat (on Windows operating systems) script to upgrade your system components.
Before running this script, make sure:
The Administration Server is up and running.
The ORACLE_HOME environment variable has been set to your product's Oracle home directory.
The OPMN instance in the bin directory in the Instance home is up and running.
On UNIX operating systems:
cd INSTANCE_HOME/bin
./opmnctl start
On Windows operating systems:
cd INSTANCE_HOME\bin
opmnctl start
To run the script on UNIX operating systems:
cd ORACLE_HOME/opmn/bin ./upgradenonj2eeapp.sh -oracleInstance Instance_Home_Location -adminHost WebLogic_Server_Host_Name -adminPort administration_server_port_number -adminUsername administration_server_user
On Windows operating systems:
cd ORACLE_HOME\opmn\bin upgradenonj2eeapp.bat -oracleInstance Instance_Home_Location -adminHost WebLogic_Server_Host_Name -adminPort administration_server_port_number -adminUsername administration_server_user
If you encounter the Command failed: NonJ2EEManagement Application deployment failed error while running the upgradenonj2eeapp script, perform the following steps to diagnose and correct the problem:
Review the provisioning.log to determine the root cause of the failure. The log file is located in the following directory:
MW_HOME/instances/myinstance/diagnostics/logs/OPMN/opmn
If the root cause of the failure is a locking issue, continue with the remaining steps.
If the error was not caused by a locking failure, you may need to simply redeploy and register your instance as described in Step 5.
Login to the Oracle WebLogic Server Administration console:
http://localhost:7001/console
Navigate to the Change Center and click Release Configuration.
The lock on the configuration will be removed, but you may also need to deploy re-register your instance.
Restart the upgradenonj2eeapp script as described above and review the provisioning.log.
If you see: "Failed to unregister instance instance1, does not exist on the adminserver", continue to the next step.
Redeploy and register the instance as shown in the following examples. Be sure to use the directory path and instance name for your environment.
./opmnctl redeploy -oracleInstance /Middleware/instances/instance1 -adminHost localhost -adminPort 7001 -adminUsername weblogic
Command requires login to weblogic admin server (localhost):
Username: weblogic
Password:
./opmnctl registerinstance Command requires login to weblogic admin server (localhost): Username: weblogic Password:
Restart the upgradenonj2eeapp script as described above. You should see "Successfully upgraded NonJ2EEManagement.ear and the registration."
If you are patching Oracle Portal, Forms, Reports and Discoverer, you must run some emCCR commands after applying the latest patch set in order for the correct version to appear. emCCR is used by Oracle Configuration Manager, which is used to collect client configuration information and upload it to the Oracle repository:
Go to the ORACLE_HOME\ccr\bin directory.
Set the ORACLE_CONFIG_HOME environment variable to the Instance home that contains Oracle Configuration Manager.
For example, on a Windows operating system:
set ORACLE_CONFIG_HOME=C:\Oracle\Middleware\Instances\asinst_ocmoc
Below is an example on a UNIX operating system:
setenv ORACLE_CONFIG_HOME /home/Oracle/Middleware/asinst_ocmoc
Run the following emCCR commands:
emccr collect emccr status
If you have Oracle Reports or Oracle Portal configured in a domain and you apply the latest patch set, you will see the following error if you try to change the invalidation password:
Error. Check logs for details. [OK].
The following errors are seen in the portal_wls.log and wls_portal.out log files:
<Date and time> <Warning> <RMI> <BEA-080003>
<RuntimeException thrown by rmi server:
javax.management.remote.rmi.RMIConnectionImpl.invoke
(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
javax.management.RuntimeErrorException:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I.javax.management.RuntimeErrorException:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I
at
oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:991)
at
oracle.adf.mbean.share.AdfMBeanInterceptor.internalInvoke(AdfMBeanInterceptor.java:104)
at
oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
....
Caused By: java.lang.UnsatisfiedLinkError:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I
at oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber(Native
Method)
at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:3537)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.jdbc.driver.T2CConnection.loadNativeLibrary
(T2CConnection.java:3532)
....
You must perform the following in order to avoid these JDBC error messages:
Go to the bin directory inside your DOMAIN_HOME (user_projects by default).
Edit the setDomainEnv.sh (on UNIX operating systems) or setDomainEnv.cmd (on Windows operating systems) file and search for EXT_PRE_CLASSPATH.
Change the definition to match the following:
On UNIX operating systems:
EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar export EXT_PRE_CLASSPATH
For example:
if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
if [ "${PRE_CLASSPATH}" != "" ] ; then
EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar // add this line
export EXT_PRE_CLASSPATH // add this line
PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
export PRE_CLASSPATH
else
EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar // add this line
export EXT_PRE_CLASSPATH // add this line
PRE_CLASSPATH="${EXT_PRE_CLASSPATH}"
export PRE_CLASSPATH
fi
fi
On Windows operating systems:
if NOT "%EXT_PRE_CLASSPATH%"=="" (
if NOT "%PRE_CLASSPATH%"=="" (
set EXT_PRE_CLASSPATH=%ORACLE_HOME%\jdbc\lib\ojdbc6.jar // add this line
set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%;%PRE_CLASSPATH%
) else (
set EXT_PRE_CLASSPATH=%ORACLE_HOME%\jdbc\lib\ojdbc6.jar // add this line
set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%
)
)
Restart the Portal Managed Server.
If your Oracle Internet Directory schema was created during installation of a version prior to 11g Release 1 (11.1.1.6.0), you must add datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE tablespaces if you intend to add more than a million entries to Oracle Internet Directory. Perform this step prior to the bulkload or ldapadd operation.
For details, see "Creating Data Files and Adding Data Files to a Tablespace" in Oracle Database Administrator's Guide.
The upgradeOpss() command is used to add a new BASE64 encoded key for each encryption key already in the bootstrap wallet. This key is required when OBI C based code accesses DB credential store. This optional command can be used when starting from version 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0. If this step is not followed, OBI will be unable to access DB-based credential stores in 11.1.1.9.0.
For more information on running OPSS in JSE mode, see "Configuring DB-Based OPSS Security Stores" in Oracle Fusion Middleware Security Guide.
To enable the dynamic audit metadata model in audit service for OPSS running in JavaSE mode, the upgradeOpss() command is used to modify jps-config-jse.xml with the additional audit service properties. This optional command can be used when starting from version 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0. If this step is not followed, 11.1.1.9.0 components registered to audit service with the new metadata model will not have audit service in JSE mode.
For more information on running OPSS in JSE mode, see "Configuring Policy and Credential Stores in Java SE Applications" in Oracle Fusion Middleware Security Guide.
As of Release 11.1.1.7.0 a new dump sampling feature was added to Diagnostic Framework. To enable this optional feature, the following WLST command should be run while connected to the AdminServer:
wlst.sh <ORACLE_HOME>/common/scripts/wlst/upgradeDFWConfig.py --adminuser <admin user name> --password <admin password> --adminurl <admin url>
This optional post-patching step enables you to provide printer-friendly renderings of certain DVT components such as treemap and sunburst by adding the Batik SVG libraries to the ADF View JRF classpath and the Apache JARs to the application classpath.
For more information, see "upgradeADFLibrary" in the Administering Oracle ADF Applications.