Pre-Upgrade Checks On Production

1. Check the Invalid Objects in the existing Production Instance and Spool the output

2. Check the Size of existing SGA in Production

3. Check the Number of Tablespaces along with free space

4. Check the Number of Datafiles/Log/Control files in Production

5. Run Autoconfig on both Both Nodes just to make sure that autoconfig run successful on both nodes…Note: This must be done when users logout from application

6. Relink any Executable eg.FNDLIBR using adadmin or adrelink command on both nodes just to make sure that there is no relink issue for any module

7. Check the Installed or Shared Modules on existing Production Instance along with it Patch Level

8. Turn Off Archive Log mode

Note: Except step 5,6,8 spool the output and store it for further reference

Additional steps:

a. Obtain URL, port of instance

b. Obtain username and password of essential Oracle users (apps, system, sys) and OS users (applmgr, root)

c. Obtain username, password for user with System Administrator responsibility, to test concurrent programs (e.g. Active Users)

d. Determine and note location of database files, log files, control files, archive log files

e. Note location of top directories (APPL_TOP, COMMON_TOP, ORA_TOP, DB_TOP, DATA_TOP)

f. Determine status of archivelog mode (and turn off if necessary)

g. Record PERL location and version

h. Rerun AutoConfig on database, application tiers to ensure it is working

I. Run adrelink on database, application to ensure it is working

j. Source environment and ensure environment variables correct (e.g. APPLCSF)

k. Ensure UNIX commands available (cc, ld, make/gnumake, ar)

Leave a Comment


NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


This site uses Akismet to reduce spam. Learn how your comment data is processed.