Upgrading to Oracle 12c - Expert Consolidation in Oracle Database 12c - page 422

The all-important information is in the last line: the result of the operation was successful. If you are running
into problems it is useful to raise a Service Request with Oracle Support straight away, in addition to your
own troubleshooting efforts. It might take a little while for Oracle Support to develop new notes similar to the
troubleshooting notes for rootupgrade.sh with version 11.2. In the meantime you should begin your investigation in
the 12.1 Grid Home. You will find a directory name $GRID_HOME/cfgtoollogs/crsconfig/ . Inside this directory you
should have a file named roothas_ timestamp .log. This log file is unusually detailed and useful. Have a look inside to
find out where it went wrong. Additionally you can consult the files in $GRID_HOME/log/hostname/ . Another useful
starting point is the alerthostname.log file, which points you to the correct log file name in most situations.
After you have assured yourself that the installation has been successful close the “execute configuration scripts”
window to proceed with the last remaining tasks. After those have completed and when you see the final screen, click
on the “Close” button to exit Oracle Universal Installer. But how do you know if ASM has been upgraded? The easiest
way is to connect to the ASM instance and query v$version:

SQL> select banner from v$version;

BANNER
--------------------------------------------------------------------------------
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
PL/SQL Release 12.1.0.1.0 - Production
CORE 12.1.0.1.0 Production
TNS for Linux: Version 12.1.0.1.0 - Production
NLSRTL Version 12.1.0.1.0 - Production

But if you carefully checked the output from the rootupgrade script you will have noticed the following:

ASM Configuration upgraded successfully.

This should take away any doubts. If you want more information about the migration process you can check the
roothas- timestamp .log file in $GRID_HOME/cfgtoollogs/crsconfig/ . With the Oracle Restart migration completed
successfully you can either leave it as it is and complete your current change, or alternatively proceed with the
database migration.

Performing additional post-migration validation
Your ASM installation has now been upgraded to version 12c. You should review any customizations you performed
in the $GRID_HOME/network/admin directory, copy any wallets and files modified by you into the new home. At the
same time it might be advisable to check the expiry date for your wallets to avoid them from being a show-stopper
during the migration weekend. Additional things to check for are:

tnsnames.ora file correct? • Are the entries in the

sqlnet.ora file present, and with the correct contents? Are the paths
referenced still valid?

• Is the (optional)

• Are all the static registrations for the listener still correct? Remember the listener will be

started from the 12c Grid Home.

• Have you used any wallets previously which need to be taken care of?

• Are there custom resources that need adapting?