Upgradation of ORACLE 9.2.0.1 to 9.2.07/9.2.08 for AIX 5L Based Systems (64-Bit)

Done By: Rahul Gupta Client Site: L.G.Electronics

---------------------------------------------------------------------------------------------------------------Dear Team,

Kindly find the doc containing the steps followed during the Upgradation of punetest from 9.2.0.5 to 9.2.0.8. Any changes Or suggestion on this will be highly appreciated. ---------------------------------------------------------------------------------------------------------------

Step 1 : Download and extract the p4547809_9208_AIX64-5L.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory. For example, Oracle_patch.

Step 2 : Enter the following commands to unzip and extract the installation files:

$ unzip p4547809_9208_AIX64-5L.zip

Step 3 : Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:

$ ORACLE_HOME=<oracle_home location>$ ORACLE_SID=<sid>$ export ORACLE_HOME ORACLE_SID$ export PATH=$PATH:$ORACLE_HOME/lib:$ORACLE_HOME/bin:<java location>

Step 4 : Delete the statistics on all of the objects in the SYS schema . This will speed the catupgrade.sql (Run later as a part of Upgradation )

SQL> EXECUTE DBMS_STATS.DELETE_SCHEMA_STATS('SYS');

Step 5 : Shutdown the database

SQL>shutdown immediate

Now, check the oraInventory.loc, check the location. If the location is not correct, then change it to the appropriate value

Step 6 : Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.

Step 7: To remove any currently used modules in kernel and library memory, enter the following command as root:

# /usr/sbin/slibclean

Step 8 : Log in as the Oracle software owner (typically oracle).

Step 9 : Set the display

DISPLAY=<local_host>:0.0 ; export DISPLAY

Step 10: Enter following commands to start the Installer where patchset_directory is the directory where you unzipped the patch set software:

$ <patchset_directory>/Disk1 $ ./runInstaller

When the runInstaller start

a.On the Welcome screen, click Nextb. On the Specify File Locations screen, click Browse next to the Path field in

the Source section.c. Select the products.xml file from the stage directory where you unpacked the

patch set files, then click Next. For example:

patchset_directory/Disk1/stage/products.xmld. In the Name field in the Destination section, select the name of the Oracle

home that you want to update from the drop down list, then click Next.e. On the Summary screen, click Install. This screen lists all of the patches

available for installation. f. When prompted, run the $ORACLE_HOME/root.sh script as the root user.g. On the End of Installation screen, click Exit, then click Yes to exit from the

Installer.

Step 11: Start the database:

SQL> STARTUP

Step 12: Determine the current values of these parameters:

A ) Check out the system tablespace size

There should be 10 MB of free space allocated to the SYSTEM tablespace.

B)

SQL> SHOW PARAMETER SHARED_POOL_SIZE SQL> SHOW PARAMETER JAVA_POOL_SIZE

If the system is using a server parameter file:

If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:

SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;

If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:

SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;

Step 13: Shut down the database:

SQL> SHUTDOWN

Step 14: Now startup the database in migrate mode and run the catpatch.sql ( spooled that also)

SQL> STARTUP MIGRATE SQL> SPOOL patch.log SQL> @?/rdbms/admin/catpatch.sql SQL> SPOOL OFF

Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script. This list provides the version and status of each SERVER component in the database. If necessary, rerun the catpatch.sql script after correcting any problems

Step 15: Restart the database:

SQL> SHUTDOWN SQL> STARTUP

Step 16: Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

SQL> @?/rdbms/admin/utlrp.sql OR

exec utl_recomp.recomp_parallel(threads=>5)

Step 17: Recollect the statistics after normal database open, if necessary.

SQL> EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS('SYS',degree=>10);

Optional step :

If you are using the Oracle Recovery Manager catalog, enter the following command:

$ rman catalog username/password@aliasRMAN> UPGRADE CATALOG;

Errors & Troubleshooting

1. While running the runInstaller , We encountered the error “Unable To Find Product Oracle.swd.jre[1.3.1, 1.6]”

Solution:

For this error I refer to the Metalink doc: 468150.1 and for the solution I applied the patch “OUI 2.2.0.18 via Patch 2878462”

(a). Extract the contents of the file oui220180_aix.jar into a newly created directory using: jar -xvf <jarfile>  (  For machines without jar use the unzip utility available in the "Download Notes" section of  the patch download page in Metalink.)

(b). Change permissions on Unix as follows:

       chmod -R +x Disk1  

(c). Change current path to Disk1/install/aix as:

      cd Disk1/install/aix  

Run the Installer from the Disk1/install/aix directory as:  ./runInstaller. This will launch the Install session for installing OUI 2.2.0.18.0 to the current ORACLE_HOME.After the installation completes you should verify that the  OUI version of the ORACLE_HOME is 2.2.0.18.0 by running the runInstaller from ORACLE_HOME/bin and clicking on the "About Oracle Universal Installer" button

------- ---------------------- -------------------------- -------------------------

2. Now , after the successful completion of OUI patch , When we run the runinstaller , we got error

“The target area /u01/app/oracle/product/oraInventory is being used as a source by other session. A write lock cannot be obtained.”

Solution:

1. Use the following command to identify the process locking the file :

   ps -ef | grep jre

2. Use the kill -9 command for the process-id  discovered in point 1.

3. Restart the installation.

---------- ----- ------------- -------------------- -------------------- -----------------

3. ORA-31609: error loading file "kubody.xsl" from file system directory "/u11/app/ilproddb/9.2.0/rdbms/xml/xsl"

Solution :

Change the ORACLE_HOME location in initmeta.sql

[ilerppune:oradev] /u11d/app/ilproddb/9.2.0/rdbms/admin> vi initmeta.sql"initmeta.sql" 1 line, 90 charactersEXECUTE SYS.DBMS_METADATA_UTIL.LOAD_STYLESHEETS('/u11d/app/ilproddb/9.2.0/rdbms/xml/xsl');

SQL> @initmeta.sql

PL/SQL procedure successfully completed.

SQL>