What happens when you give "STARTUP UPGRADE"?
What happens when you give "STARTUP UPGRADE"?
===============================================
The UPGRADE keyword enables you to open a database based on an earlier Oracle Database release.
It also restricts logons to AS SYSDBAsessions, disables system triggers, and performs additional
operations that prepare the environment for the upgrade.
You might be required to use the PFILE option to specify the location of your initialization parameter
file.
Once the database is started in upgrade mode, only queries on fixed views execute without errors until
after the catupgrd.sql script is run. Before running catupgrd.sql, queries on any other view or the use
of PL/SQL returns an error.
------>in 11gR2 you can use the "diagcollection.pl"script to collect diagnostic data from root user
rac patching:OPATCH napply -skip_subset -skip_duplicate -local -oh $ORACLE_HOME
OPATCH –v
-Check orainst.loc file pointing to your current ORACLE_HOME
-Opatch napply -skip_subset -skip_duplicate
-Select * from registry$history;
--If you want check the CPU patch is whether rolling support or not,
go to the patch directory
go to –patch directory
opatch util napply <patch_location> -id 9 -skip_subset -skip_duplicate
[oracle@prod1]$ opatch query -all
--$opatch lsinventory -detail -oh $ORACLE_HOME
SQL> @catbundle.sql cpu/psu apply
SQL> @utlrp.sql
The catbundle.sql execution is reflected in the dba_registry_history view by a row
associated with bundle series CPU. Check the following log files for any errors:
===============================================
The UPGRADE keyword enables you to open a database based on an earlier Oracle Database release.
It also restricts logons to AS SYSDBAsessions, disables system triggers, and performs additional
operations that prepare the environment for the upgrade.
You might be required to use the PFILE option to specify the location of your initialization parameter
file.
Once the database is started in upgrade mode, only queries on fixed views execute without errors until
after the catupgrd.sql script is run. Before running catupgrd.sql, queries on any other view or the use
of PL/SQL returns an error.
------>in 11gR2 you can use the "diagcollection.pl"script to collect diagnostic data from root user
rac patching:OPATCH napply -skip_subset -skip_duplicate -local -oh $ORACLE_HOME
OPATCH –v
-Check orainst.loc file pointing to your current ORACLE_HOME
-Opatch napply -skip_subset -skip_duplicate
-Select * from registry$history;
--If you want check the CPU patch is whether rolling support or not,
go to the patch directory
go to –patch directory
opatch util napply <patch_location> -id 9 -skip_subset -skip_duplicate
[oracle@prod1]$ opatch query -all
--$opatch lsinventory -detail -oh $ORACLE_HOME
SQL> @catbundle.sql cpu/psu apply
SQL> @utlrp.sql
The catbundle.sql execution is reflected in the dba_registry_history view by a row
associated with bundle series CPU. Check the following log files for any errors:
Comments
Post a Comment