# # WARNING: Failure to carefully read and understand these requirements may # result in your applying a patch that can cause your Oracle Server to # malfunction, including interruption of service and/or loss of data. # # If you do not meet all of the following requirements, please log an # iTAR, so that an Oracle Support Analyst may review your situation. The # Oracle analyst will help you determine if this patch is suitable for you # to apply to your system. We recommend that you avoid applying any # temporary patch unless directed by an Oracle Support Analyst who has # reviewed your system and determined that it is applicable. # # Requirements: # # - You must have located this patch via a Bug Database entry # and have the exact symptoms described in the bug entry. # # - Your system configuration (Oracle Server version and patch # level, OS Version) must exactly match those in the bug # database entry - You must have NO OTHER PATCHES installed on # your Oracle Server since the latest patch set (or base release # x.y.z if you have no patch sets installed). # # - [Oracle 9.2.0.2 & above] You must have Perl 5.00503 (or later) # installed under the ORACLE_HOME, or elsewhere within the host # environment. OPatch is no longer included in patches as of 9.2.0.2. # Refer to the following link for details on Perl and OPatch: # http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=189489.1 # # - [IBM AIX O/S & Java patches for Oracle 9.2] # In order to apply java class updates to IBM AIX based systems using # java_131, you must update your java if you are running a version prior # to Service Refresh build date 20030630a. This is # necessary to fix IBM Defect#60472. # # To identify which java build date you are on, enter the following # command ; # # > $ORACLE_HOME/jdk/bin/java -fullversion # ... example response ... # java full version "J2RE 1.3.1 IBM AIX build ca131-20030630a" # # The string ends in the date format YYYYMMDD or YYYYMMDDa where 'a' # indicates an updated release to the original build. You should always # apply the latest AIX Java SDK 1.3.1 Service Update available from IBM. # As a minimum, the above service refresh can be found under # APAR IY47055. The signature for the updated JVM is ca131-20030630a. # Information on the latest available fixes, as well as how to apply # the APARs to your AIX systems, is available at the IBM Java site. # # If you are running AIX 5L, you can safely ignore any comment against # the APAR that says (AIXV43 only). The APAR is applicable to # both AIX 4.3 and AIX 5L. # # Once you have updated your java installation you need to copy these # updated files to Oracle's copies in $ORACLE_HOME/jdk. # As the Oracle owner, simply issue the following commands; # # > cd /usr/java131 # > cp -fpR * $ORACLE_HOME/jdk # # # If you do NOT meet these requirements, or are not certain that you meet # these requirements, please log an iTAR requesting assistance with this # patch and Support will make a determination about whether you should # apply this patch. # #------------------------------------------------------------------------- # Interim Patch 3836030 #------------------------------------------------------------------------- # # DATE: 27 Aug 2004 # -------------------- # Platform Patch for : Linux x86 # Product Version # : 9.2.0.4.0 # Product Patched : RDBMS # (MODPLSQL VERSION 3.0.9.8.5d ONE-OFF PATCH) # # Bugs Fixed by this patch: # ------------------------- # 3838197 : REPRESENTATIVE BUG # # Patch Installation Instructions: # -------------------------------- # To apply the patch, unzip the PSE container file: # # % unzip p3835963_9204_LINUX.zip # Applying the database portion of the patch # ------------------------------------------ # # Change your current working directory to the directory where the patch was # downloaded. Now do the following steps. # # % cd ./3836030/files/Apache # # Identify the Oracle databases serviced by mod_plsql. You can get this # information by scanning the connect strings defined inside your Database # Access Descriptors (DAD) for mod_plsql # Here are the steps to get this information : # # - Identify the setting for the environment variable WV_GATEWAY_CFG. # For default installs, this value is configured in the file # <ORACLE_HOME>/Apache/Apache/bin/apachectl # and has a value of # <ORACLE_HOME>/Apache/modplsql/cfg/wdbsvr.app # - Open the file as pointed by this environment variable. # - Search for each unique occurrence of 'connect_string' and # use the database connection information to identify which database # instances need to be patched up. # - If a DAD does not explicitly specify a value for 'connect_string', # then identify the default database instance for your configuration. # # For all such database instances, # # Step 1. Verify that you can connect to the database as the sys user # - Issue "sqlplus /nolog" # - At the SQL prompt, issue "conn sys/sys_password@conn_str as sysdba" # # NOTE: # The following Oracle database parameter settings could disallow # remote database connections as sysdba # - O7_DICTIONARY_ACCESSIBILITY = FALSE # - REMOTE_LOGIN_PASSWORDFILE = NONE # If this is the case, either allow remote connections temporarily, or # upload the patch to the database machine and follow Step 2 to # patch up the database. # # For more details on these Oracle database parameters, refer to the # Oracle documentation. # # Step 2. Invoke the following command to patch up the OWA packages in the # SYS schema # # ./patch.csh -m sysobjects -o <ORACLE_HOME> -c <conn_str> -p <sys_password> # # - Once all the database instances are patched up, proceed to the middle-tier # instance to apply the middle-tier portion of the patch. # # # Applying the middle-tier portion of the patch # --------------------------------------------- # # WARNING : The newer version of mod_plsql will not work against a # database which is not patched up as per the previous instructions. # # Stop the Oracle HTTP Server (from EM or DCMCTL) # # Set your current directory to the directory where the patch # is located: # % cd 3836030 # # Ensure that the directory containing the opatch script appears in # your $PATH; then enter the following command: # # % opatch apply # # # Restart Oracle HTTP Server # # # Patch Special Instructions: # --------------------------- # Make sure all instances running under the ORACLE_HOME being patched # are cleanly shutdown before installing this patch. Also ensure that # the tool used to terminate the instance(s) has exited cleanly. # # If the Oracle inventory is not setup correctly this utility will # fail. To check accessibility to the inventory you can use the # command # # % opatch lsinventory # # If you have any problems installing this PSE or are not sure # about inventory setup please call Oracle support. # # Patch Deinstallation Instructions: # ---------------------------------- # Use the following command: # # % cd 3836030 # Stop the Oracle HTTP Server # % opatch rollback -id 3835963 # # Restart Oracle HTTP Server # # End of README.txt file