Upgrade database from oracle 11202 to 12101
Database Upgrade from 11202 to 12101
Copy two sql files to /tmp location
[oracle@yesbolisetty admin]$ cd /tmp/upgrade/
[oracle@yesbolisetty upgrade]$ ls -lrt
total 396
-rwxr-xr-x 1 oracle oinstall 5231 Nov 9 14:10 preupgrd.sql
-rwxr-xr-x 1 oracle oinstall 381893 Nov 9 14:16 utluppkg.sql
Step 2: connect to 11g database and execute preupgrd.sql script
[oracle@yesbolisetty upgrade]$ dba
SQL*Plus: Release 11.2.0.2.0 Production on Sat Nov 9 14:16:35 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @preupgrd.sql
Loading Pre-Upgrade Package...
Executing Pre-Upgrade Checks...
Pre-Upgrade Checks Complete.
************************************************************
Results of the checks are located at:
/u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade.log
Pre-Upgrade Fixup Script (run in source database environment):
/u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade_fixups.sql
Post-Upgrade Fixup Script (run shortly after upgrade):
/u02/app/oracle/cfgtoollogs/db11202/preupgrade/postupgrade_fixups.sql
************************************************************
Fixup scripts must be reviewed prior to being executed.
************************************************************
************************************************************
====>> USER ACTION REQUIRED <<====
************************************************************
The following are *** ERROR LEVEL CONDITIONS *** that must be addressed
prior to attempting your upgrade.
Failure to do so will result in a failed upgrade.
You MUST resolve the above errors prior to upgrade
************************************************************
SQL>exit
View logfile
[oracle@yesbolisetty upgrade]$ cat /u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade.log
Oracle Database Pre-Upgrade Information Tool 11-09-2013 14:16:54
Script Version: 12.1.0.1.0 Build: 006
**********************************************************************
Database Name: DB11202
Version: 11.2.0.2.0
Compatible: 11.2.0.0.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone file: V14
**********************************************************************
[Renamed Parameters]
[No Renamed Parameters in use]
**********************************************************************
**********************************************************************
[Obsolete/Deprecated Parameters]
[No Obsolete or Desupported Parameters in use]
**********************************************************************
[Component List]
**********************************************************************
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Oracle Workspace Manager [upgrade] VALID
--> OLAP Analytic Workspace [upgrade] VALID
--> Oracle Enterprise Manager Repository [upgrade] VALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [upgrade] VALID
--> Oracle Java Packages [upgrade] VALID
--> Oracle Multimedia [upgrade] VALID
--> Oracle Spatial [upgrade] VALID
--> Expression Filter [upgrade] VALID
--> Rule Manager [upgrade] VALID
--> Oracle Application Express [upgrade] VALID
--> Oracle OLAP API [upgrade] VALID
**********************************************************************
[Tablespaces]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
minimum required size: 1204 MB
--> SYSAUX tablespace is adequate for the upgrade.
minimum required size: 1399 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
minimum required size: 400 MB
--> TEMP tablespace is adequate for the upgrade.
minimum required size: 60 MB
[No adjustments recommended]
**********************************************************************
**********************************************************************
[Pre-Upgrade Checks]
**********************************************************************
WARNING: --> Process Count may be too low
Database has a maximum process count of 150 which is lower than the
default value of 300 for this release.
You should update your processes value prior to the upgrade
to a value of at least 300.
For example:
ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE
or update your init.ora file.
WARNING: --> Enterprise Manager Database Control repository found in the database
In Oracle Database 12c, Database Control is removed during
the upgrade. To save time during the Upgrade, this action
can be done prior to upgrading using the following steps after
copying rdbms/admin/emremove.sql from the new Oracle home
- Stop EM Database Control:
$> emctl stop dbconsole
- Connect to the Database using the SYS account AS SYSDBA:
SET ECHO ON;
SET SERVEROUTPUT ON;
@emremove.sql
Without the set echo and serveroutput commands you will not
be able to follow the progress of the script.
WARNING: --> Existing DBMS_LDAP dependent objects
Database contains schemas with objects dependent on DBMS_LDAP package.
Refer to the Upgrade Guide for instructions to configure Network ACLs.
USER APEX_030200 has dependent objects.
INFORMATION: --> OLAP Catalog(AMD) exists in database
Starting with Oracle Database 12c, OLAP is desupported.
If you are not using the OLAP Catalog component and want
to remove it, then execute the
ORACLE_HOME/oraolap/admin/catnoamd.sql script before or
after the upgrade.
INFORMATION: --> Older Timezone in use
Database is using a time zone file older than version 18.
After the upgrade, it is recommended that DBMS_DST package
be used to upgrade the 11.2.0.2.0 database time zone version
to the latest version which comes with the new release.
Please refer to My Oracle Support note number 977512.1 for details.
**********************************************************************
[Pre-Upgrade Recommendations]
**********************************************************************
*****************************************
********* Dictionary Statistics *********
*****************************************
Please gather dictionary statistics 24 hours prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
EXECUTE dbms_stats.gather_dictionary_stats;
^^^ MANUAL ACTION SUGGESTED ^^^
**********************************************************************
[Post-Upgrade Recommendations]
**********************************************************************
*****************************************
******** Fixed Object Statistics ********
*****************************************
Please create stats on fixed objects two weeks
after the upgrade using the command:
EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;
^^^ MANUAL ACTION SUGGESTED ^^^
**********************************************************************
************ Summary ************
0 ERRORS exist in your database.
3 WARNINGS that Oracle suggests are addressed to improve database performance.
2 INFORMATIONAL messages that should be reviewed prior to your upgrade.
After your database is upgraded and open in normal mode you must run
rdbms/admin/catuppst.sql which executes several required tasks and completes
the upgrade process.
You should follow that with the execution of rdbms/admin/utlrp.sql, and a
comparison of invalid objects before and after the upgrade using
rdbms/admin/utluiobj.sql
If needed you may want to upgrade your timezone data using the process
described in My Oracle Support note 977512.1
***********************************
[oracle@yesbolisetty upgrade]$
Pre-Upgrade Fixup Script (run in source database environment):
/u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade_fixups.sql
SQL>@/u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade_fixups.sql
Pre-Upgrade Fixup Script Generated on 2013-11-09 14:16:51 Version: 12.1.0.1 Build: 006
Beginning Pre-Upgrade Fixups...
**********************************************************************
Check Tag: DEFAULT_PROCESS_COUNT
Check Summary: Verify min process count is not too low
Fix Summary: Review and increase if needed, your PROCESSES value.
**********************************************************************
Fixup Returned Information:
WARNING: --> Process Count may be too low
Database has a maximum process count of 150 which is lower than the
default value of 300 for this release.
You should update your processes value prior to the upgrade
to a value of at least 300.
For example:
ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE
or update your init.ora file.
**********************************************************************
**********************************************************************
Check Tag: EM_PRESENT
Check Summary: Check if Enterprise Manager is present
Fix Summary: Execute emremove.sql prior to upgrade.
**********************************************************************
Fixup Returned Information:
WARNING: --> Enterprise Manager Database Control repository found in the database
In Oracle Database 12c, Database Control is removed during
the upgrade. To save time during the Upgrade, this action
can be done prior to upgrading using the following steps after
copying rdbms/admin/emremove.sql from the new Oracle home
- Stop EM Database Control:
$> emctl stop dbconsole
- Connect to the Database using the SYS account AS SYSDBA:
SET ECHO ON;
SET SERVEROUTPUT ON;
@emremove.sql
Without the set echo and serveroutput commands you will not
be able to follow the progress of the script.
**********************************************************************
**********************************************************************
Check Tag: DBMS_LDAP_DEPENDENCIES_EXIST
Check Summary: Check for dependency on DBMS_LDAP package
Fix Summary: Network Objects must be reviewed manually.
**********************************************************************
Fixup Returned Information:
WARNING: --> Existing DBMS_LDAP dependent objects
Database contains schemas with objects dependent on DBMS_LDAP package.
Refer to the Upgrade Guide for instructions to configure Network ACLs.
USER APEX_030200 has dependent objects.
**********************************************************************
**********************************************************************
Check Tag: AMD_EXISTS
Check Summary: Check to see if AMD is present in the database
Fix Summary: Manually execute ORACLE_HOME/oraolap/admin/catnoamd.sql script to remove OLAP.
**********************************************************************
Fixup Returned Information:
INFORMATION: --> OLAP Catalog(AMD) exists in database
Starting with Oracle Database 12c, OLAP is desupported.
If you are not using the OLAP Catalog component and want
to remove it, then execute the
ORACLE_HOME/oraolap/admin/catnoamd.sql script before or
after the upgrade.
**********************************************************************
**********************************************************************
[Pre-Upgrade Recommendations]
**********************************************************************
*****************************************
********* Dictionary Statistics *********
*****************************************
Please gather dictionary statistics 24 hours prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
EXECUTE dbms_stats.gather_dictionary_stats;
^^^ MANUAL ACTION SUGGESTED ^^^
**************************************************
************* Fixup Summary ************
4 fixup routines generated INFORMATIONAL messages that should be reviewed.
**************** Pre-Upgrade Fixup Script Complete *********************
SQL> exit
Connect to 12C
[root@yesbolisetty ~]# su - oracle
[oracle@yesbolisetty ~]$
[oracle@yesbolisetty ~]$
[oracle@yesbolisetty ~]$
[oracle@yesbolisetty ~]$ cd $ORACLE_HOME/bin
[oracle@yesbolisetty bin]$ ./dbua
Database Upgrade Summary
Source Database
Target Database
Name:
db11202
db11202
Release:
11.2.0.2.0
12.1.0.1.0
Oracle Home:
/u02/app/oracle/product/11.2.0/dbhome_1
/u01/app/oracle/product/12.1.0/dbhome_1
Pre-Upgrade Checks
Warnings Ignored
Database contains schemas with objects dependent on DBMS_LDAP package. Refer to the Oracle Database Upgrade Guide for instructions to configure Network ACLs.
Database is using an old time zone file version. After the upgrade, patch the database time zone file version using DBMS_DST package to record latest time zone file version.
Database Components to be Upgraded
Database Components
Version
Status
Oracle Server
11.2.0.2.0
VALID
JServer JAVA Virtual Machine
11.2.0.2.0
VALID
Oracle XDK for Java
11.2.0.2.0
VALID
OLAP Analytic Workspace
11.2.0.2.0
VALID
Oracle Enterprise Manager Repository
11.2.0.2.0
VALID
Oracle Text
11.2.0.2.0
VALID
Oracle XML Database
11.2.0.2.0
VALID
Oracle Java Packages
11.2.0.2.0
VALID
Oracle Multimedia
11.2.0.2.0
VALID
Oracle Spatial
11.2.0.2.0
VALID
Oracle Workspace Manager
11.2.0.2.0
VALID
Expression Filter
11.2.0.2.0
VALID
Rule Manager
11.2.0.2.0
VALID
Oracle Application Express
3.2.1.00.12
VALID
Oracle OLAP API
11.2.0.2.0
VALID
Initialization Parameter changes
The following changes will be made in the initialization parameters:
Parameters to be added:
Name
Value
local_listener
LISTENER_DB11202
Parameters to be updated:
Name
Old Value
New Value
processes
150
300
audit_file_dest
"/u02/app/oracle/admin/db11202/adump"
/u01/app/oracle/admin/db11202/adump
diagnostic_dest
/u02/app/oracle
/u01/app/oracle
Recovery options
Create a new offline RMAN backup and restore database using that backup in case of upgrade failure.
Backup Location
Available Space (MB)
Required Space (MB)
/u01/app/oracle/admin/db11202/backup
7003
1420
Listener Registration
The following listeners will be registered with the database:
Listener Name
LISTENER
Upgrade Results
Database upgrade has been completed successfully, and the database is ready to use.
Source Database
Target Database
Name:
db11202
db11202
Release:
11.2.0.2.0
12.1.0.1.0
Oracle Home:
/u02/app/oracle/product/11.2.0/dbhome_1
/u01/app/oracle/product/12.1.0/dbhome_1
Pre-Upgrade Checks
Warnings Ignored
Database contains schemas with objects dependent on DBMS_LDAP package. Refer to the Oracle Database Upgrade Guide for instructions to configure Network ACLs.
Database is using an old time zone file version. After the upgrade, patch the database time zone file version using DBMS_DST package to record latest time zone file version.
Upgrade Details
The following summary lists the steps performed during the upgrade process. Log files for all the steps, as well as this summary, are available at "/u01/app/oracle/cfgtoollogs/dbua/db11202/upgrade1".
Step Name
Log File Name
Status
Database Backup
Backup.log
Successful
Pre Upgrade
PreUpgrade.log
Successful
RDBMS Upgrade
Oracle_Server.log
Successful
Post Upgrade
PostUpgrade.log
Successful
Generate Summary
generateSummary.log
Successful
Step Execution Information:
Database Backup
The Database can be restored by running the following script "/u01/app/oracle/admin/db11202/backup/db11202_restore.sh" from the backup location.NOTE: This operation will remove all the upgrade changes made by the Database Upgrade Assistant.
Post Upgrade
A persistent initialization parameter file (spfile) has been created at the following location: /u01/app/oracle/product/12.1.0/dbhome_1/dbs/spfiledb11202.ora.
Initialization Parameter changes
The following changes have been made in the initialization parameters:
Parameters Added:
Name
Value
local_listener
LISTENER_DB11202
Parameters Updated:
Name
Old Value
New Value
processes
150
300
audit_file_dest
"/u02/app/oracle/admin/db11202/adump"
/u01/app/oracle/admin/db11202/adump
diagnostic_dest
/u02/app/oracle
/u01/app/oracle
Database upgrade has been completed successfully, and the database is ready to use.
[oracle@yesbolisetty bin]$
[oracle@yesbolisetty bin]$
[oracle@yesbolisetty bin]$ ps -ef |grep pmon
oracle 15302 1 0 18:43 ? 00:00:00 ora_pmon_db11202
oracle 15615 12943 0 18:59 pts/1 00:00:00 grep pmon
[oracle@yesbolisetty bin]$ export ORACLE_SID=db11202
[oracle@yesbolisetty bin]$ sqlplus / as sysdba
SQL*Plus: Release 12.1.0.1.0 Production on Sat Nov 9 19:00:16 2013
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
SQL> select name from v$database;
NAME
---------
DB11202
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
శ్రీనివాస్ బోలిశెట్టి
Copy two sql files to /tmp location
[oracle@yesbolisetty admin]$ cd /tmp/upgrade/
[oracle@yesbolisetty upgrade]$ ls -lrt
total 396
-rwxr-xr-x 1 oracle oinstall 5231 Nov 9 14:10 preupgrd.sql
-rwxr-xr-x 1 oracle oinstall 381893 Nov 9 14:16 utluppkg.sql
Step 2: connect to 11g database and execute preupgrd.sql script
[oracle@yesbolisetty upgrade]$ dba
SQL*Plus: Release 11.2.0.2.0 Production on Sat Nov 9 14:16:35 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @preupgrd.sql
Loading Pre-Upgrade Package...
Executing Pre-Upgrade Checks...
Pre-Upgrade Checks Complete.
************************************************************
Results of the checks are located at:
/u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade.log
Pre-Upgrade Fixup Script (run in source database environment):
/u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade_fixups.sql
Post-Upgrade Fixup Script (run shortly after upgrade):
/u02/app/oracle/cfgtoollogs/db11202/preupgrade/postupgrade_fixups.sql
************************************************************
Fixup scripts must be reviewed prior to being executed.
************************************************************
************************************************************
====>> USER ACTION REQUIRED <<====
************************************************************
The following are *** ERROR LEVEL CONDITIONS *** that must be addressed
prior to attempting your upgrade.
Failure to do so will result in a failed upgrade.
You MUST resolve the above errors prior to upgrade
************************************************************
SQL>exit
View logfile
[oracle@yesbolisetty upgrade]$ cat /u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade.log
Oracle Database Pre-Upgrade Information Tool 11-09-2013 14:16:54
Script Version: 12.1.0.1.0 Build: 006
**********************************************************************
Database Name: DB11202
Version: 11.2.0.2.0
Compatible: 11.2.0.0.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone file: V14
**********************************************************************
[Renamed Parameters]
[No Renamed Parameters in use]
**********************************************************************
**********************************************************************
[Obsolete/Deprecated Parameters]
[No Obsolete or Desupported Parameters in use]
**********************************************************************
[Component List]
**********************************************************************
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Oracle Workspace Manager [upgrade] VALID
--> OLAP Analytic Workspace [upgrade] VALID
--> Oracle Enterprise Manager Repository [upgrade] VALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [upgrade] VALID
--> Oracle Java Packages [upgrade] VALID
--> Oracle Multimedia [upgrade] VALID
--> Oracle Spatial [upgrade] VALID
--> Expression Filter [upgrade] VALID
--> Rule Manager [upgrade] VALID
--> Oracle Application Express [upgrade] VALID
--> Oracle OLAP API [upgrade] VALID
**********************************************************************
[Tablespaces]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
minimum required size: 1204 MB
--> SYSAUX tablespace is adequate for the upgrade.
minimum required size: 1399 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
minimum required size: 400 MB
--> TEMP tablespace is adequate for the upgrade.
minimum required size: 60 MB
[No adjustments recommended]
**********************************************************************
**********************************************************************
[Pre-Upgrade Checks]
**********************************************************************
WARNING: --> Process Count may be too low
Database has a maximum process count of 150 which is lower than the
default value of 300 for this release.
You should update your processes value prior to the upgrade
to a value of at least 300.
For example:
ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE
or update your init.ora file.
WARNING: --> Enterprise Manager Database Control repository found in the database
In Oracle Database 12c, Database Control is removed during
the upgrade. To save time during the Upgrade, this action
can be done prior to upgrading using the following steps after
copying rdbms/admin/emremove.sql from the new Oracle home
- Stop EM Database Control:
$> emctl stop dbconsole
- Connect to the Database using the SYS account AS SYSDBA:
SET ECHO ON;
SET SERVEROUTPUT ON;
@emremove.sql
Without the set echo and serveroutput commands you will not
be able to follow the progress of the script.
WARNING: --> Existing DBMS_LDAP dependent objects
Database contains schemas with objects dependent on DBMS_LDAP package.
Refer to the Upgrade Guide for instructions to configure Network ACLs.
USER APEX_030200 has dependent objects.
INFORMATION: --> OLAP Catalog(AMD) exists in database
Starting with Oracle Database 12c, OLAP is desupported.
If you are not using the OLAP Catalog component and want
to remove it, then execute the
ORACLE_HOME/oraolap/admin/catnoamd.sql script before or
after the upgrade.
INFORMATION: --> Older Timezone in use
Database is using a time zone file older than version 18.
After the upgrade, it is recommended that DBMS_DST package
be used to upgrade the 11.2.0.2.0 database time zone version
to the latest version which comes with the new release.
Please refer to My Oracle Support note number 977512.1 for details.
**********************************************************************
[Pre-Upgrade Recommendations]
**********************************************************************
*****************************************
********* Dictionary Statistics *********
*****************************************
Please gather dictionary statistics 24 hours prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
EXECUTE dbms_stats.gather_dictionary_stats;
^^^ MANUAL ACTION SUGGESTED ^^^
**********************************************************************
[Post-Upgrade Recommendations]
**********************************************************************
*****************************************
******** Fixed Object Statistics ********
*****************************************
Please create stats on fixed objects two weeks
after the upgrade using the command:
EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;
^^^ MANUAL ACTION SUGGESTED ^^^
**********************************************************************
************ Summary ************
0 ERRORS exist in your database.
3 WARNINGS that Oracle suggests are addressed to improve database performance.
2 INFORMATIONAL messages that should be reviewed prior to your upgrade.
After your database is upgraded and open in normal mode you must run
rdbms/admin/catuppst.sql which executes several required tasks and completes
the upgrade process.
You should follow that with the execution of rdbms/admin/utlrp.sql, and a
comparison of invalid objects before and after the upgrade using
rdbms/admin/utluiobj.sql
If needed you may want to upgrade your timezone data using the process
described in My Oracle Support note 977512.1
***********************************
[oracle@yesbolisetty upgrade]$
Pre-Upgrade Fixup Script (run in source database environment):
/u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade_fixups.sql
SQL>@/u02/app/oracle/cfgtoollogs/db11202/preupgrade/preupgrade_fixups.sql
Pre-Upgrade Fixup Script Generated on 2013-11-09 14:16:51 Version: 12.1.0.1 Build: 006
Beginning Pre-Upgrade Fixups...
**********************************************************************
Check Tag: DEFAULT_PROCESS_COUNT
Check Summary: Verify min process count is not too low
Fix Summary: Review and increase if needed, your PROCESSES value.
**********************************************************************
Fixup Returned Information:
WARNING: --> Process Count may be too low
Database has a maximum process count of 150 which is lower than the
default value of 300 for this release.
You should update your processes value prior to the upgrade
to a value of at least 300.
For example:
ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE
or update your init.ora file.
**********************************************************************
**********************************************************************
Check Tag: EM_PRESENT
Check Summary: Check if Enterprise Manager is present
Fix Summary: Execute emremove.sql prior to upgrade.
**********************************************************************
Fixup Returned Information:
WARNING: --> Enterprise Manager Database Control repository found in the database
In Oracle Database 12c, Database Control is removed during
the upgrade. To save time during the Upgrade, this action
can be done prior to upgrading using the following steps after
copying rdbms/admin/emremove.sql from the new Oracle home
- Stop EM Database Control:
$> emctl stop dbconsole
- Connect to the Database using the SYS account AS SYSDBA:
SET ECHO ON;
SET SERVEROUTPUT ON;
@emremove.sql
Without the set echo and serveroutput commands you will not
be able to follow the progress of the script.
**********************************************************************
**********************************************************************
Check Tag: DBMS_LDAP_DEPENDENCIES_EXIST
Check Summary: Check for dependency on DBMS_LDAP package
Fix Summary: Network Objects must be reviewed manually.
**********************************************************************
Fixup Returned Information:
WARNING: --> Existing DBMS_LDAP dependent objects
Database contains schemas with objects dependent on DBMS_LDAP package.
Refer to the Upgrade Guide for instructions to configure Network ACLs.
USER APEX_030200 has dependent objects.
**********************************************************************
**********************************************************************
Check Tag: AMD_EXISTS
Check Summary: Check to see if AMD is present in the database
Fix Summary: Manually execute ORACLE_HOME/oraolap/admin/catnoamd.sql script to remove OLAP.
**********************************************************************
Fixup Returned Information:
INFORMATION: --> OLAP Catalog(AMD) exists in database
Starting with Oracle Database 12c, OLAP is desupported.
If you are not using the OLAP Catalog component and want
to remove it, then execute the
ORACLE_HOME/oraolap/admin/catnoamd.sql script before or
after the upgrade.
**********************************************************************
**********************************************************************
[Pre-Upgrade Recommendations]
**********************************************************************
*****************************************
********* Dictionary Statistics *********
*****************************************
Please gather dictionary statistics 24 hours prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
EXECUTE dbms_stats.gather_dictionary_stats;
^^^ MANUAL ACTION SUGGESTED ^^^
**************************************************
************* Fixup Summary ************
4 fixup routines generated INFORMATIONAL messages that should be reviewed.
**************** Pre-Upgrade Fixup Script Complete *********************
SQL> exit
Connect to 12C
[root@yesbolisetty ~]# su - oracle
[oracle@yesbolisetty ~]$
[oracle@yesbolisetty ~]$
[oracle@yesbolisetty ~]$
[oracle@yesbolisetty ~]$ cd $ORACLE_HOME/bin
[oracle@yesbolisetty bin]$ ./dbua
Database Upgrade Summary
Source Database
Target Database
Name:
db11202
db11202
Release:
11.2.0.2.0
12.1.0.1.0
Oracle Home:
/u02/app/oracle/product/11.2.0/dbhome_1
/u01/app/oracle/product/12.1.0/dbhome_1
Pre-Upgrade Checks
Warnings Ignored
Database contains schemas with objects dependent on DBMS_LDAP package. Refer to the Oracle Database Upgrade Guide for instructions to configure Network ACLs.
Database is using an old time zone file version. After the upgrade, patch the database time zone file version using DBMS_DST package to record latest time zone file version.
Database Components to be Upgraded
Database Components
Version
Status
Oracle Server
11.2.0.2.0
VALID
JServer JAVA Virtual Machine
11.2.0.2.0
VALID
Oracle XDK for Java
11.2.0.2.0
VALID
OLAP Analytic Workspace
11.2.0.2.0
VALID
Oracle Enterprise Manager Repository
11.2.0.2.0
VALID
Oracle Text
11.2.0.2.0
VALID
Oracle XML Database
11.2.0.2.0
VALID
Oracle Java Packages
11.2.0.2.0
VALID
Oracle Multimedia
11.2.0.2.0
VALID
Oracle Spatial
11.2.0.2.0
VALID
Oracle Workspace Manager
11.2.0.2.0
VALID
Expression Filter
11.2.0.2.0
VALID
Rule Manager
11.2.0.2.0
VALID
Oracle Application Express
3.2.1.00.12
VALID
Oracle OLAP API
11.2.0.2.0
VALID
Initialization Parameter changes
The following changes will be made in the initialization parameters:
Parameters to be added:
Name
Value
local_listener
LISTENER_DB11202
Parameters to be updated:
Name
Old Value
New Value
processes
150
300
audit_file_dest
"/u02/app/oracle/admin/db11202/adump"
/u01/app/oracle/admin/db11202/adump
diagnostic_dest
/u02/app/oracle
/u01/app/oracle
Recovery options
Create a new offline RMAN backup and restore database using that backup in case of upgrade failure.
Backup Location
Available Space (MB)
Required Space (MB)
/u01/app/oracle/admin/db11202/backup
7003
1420
Listener Registration
The following listeners will be registered with the database:
Listener Name
LISTENER
Upgrade Results
Database upgrade has been completed successfully, and the database is ready to use.
Source Database
Target Database
Name:
db11202
db11202
Release:
11.2.0.2.0
12.1.0.1.0
Oracle Home:
/u02/app/oracle/product/11.2.0/dbhome_1
/u01/app/oracle/product/12.1.0/dbhome_1
Pre-Upgrade Checks
Warnings Ignored
Database contains schemas with objects dependent on DBMS_LDAP package. Refer to the Oracle Database Upgrade Guide for instructions to configure Network ACLs.
Database is using an old time zone file version. After the upgrade, patch the database time zone file version using DBMS_DST package to record latest time zone file version.
Upgrade Details
The following summary lists the steps performed during the upgrade process. Log files for all the steps, as well as this summary, are available at "/u01/app/oracle/cfgtoollogs/dbua/db11202/upgrade1".
Step Name
Log File Name
Status
Database Backup
Backup.log
Successful
Pre Upgrade
PreUpgrade.log
Successful
RDBMS Upgrade
Oracle_Server.log
Successful
Post Upgrade
PostUpgrade.log
Successful
Generate Summary
generateSummary.log
Successful
Step Execution Information:
Database Backup
The Database can be restored by running the following script "/u01/app/oracle/admin/db11202/backup/db11202_restore.sh" from the backup location.NOTE: This operation will remove all the upgrade changes made by the Database Upgrade Assistant.
Post Upgrade
A persistent initialization parameter file (spfile) has been created at the following location: /u01/app/oracle/product/12.1.0/dbhome_1/dbs/spfiledb11202.ora.
Initialization Parameter changes
The following changes have been made in the initialization parameters:
Parameters Added:
Name
Value
local_listener
LISTENER_DB11202
Parameters Updated:
Name
Old Value
New Value
processes
150
300
audit_file_dest
"/u02/app/oracle/admin/db11202/adump"
/u01/app/oracle/admin/db11202/adump
diagnostic_dest
/u02/app/oracle
/u01/app/oracle
Database upgrade has been completed successfully, and the database is ready to use.
[oracle@yesbolisetty bin]$
[oracle@yesbolisetty bin]$
[oracle@yesbolisetty bin]$ ps -ef |grep pmon
oracle 15302 1 0 18:43 ? 00:00:00 ora_pmon_db11202
oracle 15615 12943 0 18:59 pts/1 00:00:00 grep pmon
[oracle@yesbolisetty bin]$ export ORACLE_SID=db11202
[oracle@yesbolisetty bin]$ sqlplus / as sysdba
SQL*Plus: Release 12.1.0.1.0 Production on Sat Nov 9 19:00:16 2013
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
SQL> select name from v$database;
NAME
---------
DB11202
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
శ్రీనివాస్ బోలిశెట్టి
annai, please post the instructions for upgrading time zone file ugrade to version 18
ReplyDeletePlease ask procedure oriented questions if any ..what is version 18 ? its not related to oracle
DeleteThis comment has been removed by the author.
ReplyDelete