UPGRADE DATABASE FROM 10.2.0.5 TO 11.2.0.1
This article is intended as a brief guide to upgrade Oracle Database from 10.2.0.5 to 11.2.0.1 on LINUX OS for Self Practice. I explain step by step how to upgrade database from 10g to 11g. The purpose of this article to minimize the downtime while upgrading the database using DBUA.
WHY UPGRADE ?
Several Bugs that are causing outages and/or business impacts?
Upgrade your database because numerous Bugs fixed. Several new features deployed with higher versions.
Improved Performance and Scalability for latest versions rather than previous versions.
Already Thousands of customers upgraded their database from lower versions to recent versions. Extended support fee can be avoided; no bug fixes unless you pay extra fee to get extended support.
Upgrade means the process of changing the data dictionary contents of a database to reflect particular release.
Upgrading from 10.2.X to 11.2.X is a major release upgrade. Ex: 10.2.0.5.0 to 11.2.0.1.0
Upgrading from 10.2.0.X to 10.2.0.X is a patch set upgrade. EX: 10.2.0.1 to 10.2.0.5
IMPORTANT POINTS BEFORE YOU START 11G UPGRADE
1. Read Chapter 1, 2 & 3 of Database Upgrade Guide here
2. Read 11g online documentation INSTALLING & UPGRADING from here DIFFERENT WAYS TO UPGRADE AN ORACLE DATABASE.
Generally peoples are using MANUAL & DBUA method. But I would prefer to use DBUA method.
DBUA – Database Upgrade Assistant – Recommended by Oracle.
MANUAL – Using SQL scripts and utilities.
WHEN TO CHOOSE DBUA ?
Remains same operating system as well as at least 90 mins avg downtime. GUI is preferred rather than command line interface because,
Less manual effort & automatically performs pre-upgrade checks.
CONSIDERATION
Source & Target $ORACLE_HOME should reside in same system. Cannot rerun if any error encountered mid-upgrade.
DBUA automates the upgrade process by performing all of the tasks which are performed manually. Some steps which can be performed when the database is running. If these steps can be done manually before upgrading using DBUA, the downtime can be minimized.
ABOUT DBUA
It provides GUI Mode – Graphical User Interface.
Recommended method to perform Database upgrade (major release). Automates the upgrade process by performing all of the tasks.
DBUA makes appropriate recommendations for configuration options such as tablespaces & redologs.
DBUA PERFORMS FOLLOWING CHECKS BEFORE UPGRADE PROCESS
Stale optimizer statistics. Invalid user accounts or roles.
Invalid data types or invalid objects. Desupported character sets.
Timezone file versions.
Adequate resources, including rollback segments, tablespaces, and free disk space Missing SQL scripts needed for the upgrade.
Listener running (If OEM database control upgrade or configuration is requested). Oracle Database Software linked with Database vault option.
If database vault is enabled, DBUA will ask you to disable Database vault before upgrade.
** DBUA does NOT begin the upgrade until all of the pre-upgrade steps are completed. **
FIX DUPLICATE OBJECTS
Check for duplicate objects in SYS and SYSTEM schemas.
Ensure that you do NOT have duplicate objects in the SYS and SYSTEM schema.
SYS> select OBJECT_NAME, OBJECT_TYPE from DBA_OBJECTS where OBJECT_NAME||OBJECT_TYPE in
(select OBJECT_NAME||OBJECT_TYPE from DBA_OBJECTS where OWNER='SYS') and OWNER='SYSTEM';
OBJECT_NAME OBJECT_TYPE
--- --- AQ$_SCHEDULES TABLE
AQ$_SCHEDULES_PRIMARY INDEX DBMS_REPCAT_AUTH PACKAGE
DBMS_REPCAT_AUTH PACKAGE BODY
Please refer 1030426.6 how to clean up duplicate objects owned by SYS & SYSTEM schema. I would not be clean anything from SYS & SYSTEM schema. IMO, it is safe to leave above items as it is.
INSTALL 11g ORACLE DATABASE SOFTWARE
Download 11g Software from here.
Transfer files to target server and unzip those files.
Install 11g s/w in separate location.
Step by step 11g installation on OEL explained here. UNZIP DOWNLOADED FILES
# First unzip file1 then unzip 2nd file. Do not unzip parallelly both files. $ cd /u04/software
$ unzip linux_11gR2_database_1of2.zip $ unzip linux_11gR2_database_2of2.zip
Once you unzip both files, you will get database directory; then need to change the ownership of that s/w or else set the appropriate permissions to oracle user to install the database s/w.
INSTALL 11g SOFTWARE ON NEW MOUNT POINT
$ mkdir –p /u01/app/oracle/product/11.2.0/db_home # In my case, 11g S/W already installed.
WHY SEPARATE $ORACLE_HOME FOR 11g
We cannot upgrade existing 10g $ORACLE_HOME for 11g database.
11g is NOT a Patchset. We have to install 11g $ORACLE_HOME separately.
To upgrade existing database into 11g, install only Oracle 11g Server software into new location.
$ORACLE_HOME for 10g : /u02/app/oracle/product/10.2.0/db_home $ORACLE_HOME for 11g : /u01/app/oracle/product/11.2.0/db_home
SANITY OPERATONS
# PURGE THE RECYCLEBIN
SYS> purge dba_recyclebin;
# FIX all invalid objects before upgrade process
SYS> select object_name, object_type, owner FROM dba_objects where status='INVALID'; ...
# ANY INVALID OBJECTS, EXECUTE FOLLOWING SCRIPT. SYS> @?/rdbms/admin/utlrp.sql;
...
Should be NO invalid objects from SYS and SYSTEM schema.
Recompile all invalid objects using utlrp.sql before upgrade process
CHECK ANY FILES IN MEDIA RECOVERY
SYS> select * from v$recover_file;
no rows selected.
SYS> select * from v$backup where status != 'NOT ACTIVE';
no rows selected.
Make sure no files need media recovery as well as nothing is in backup mode.
GATHER DICTIONARY STATS
In order to reduce the amount of downtime, you can collect statistics prior to perform actual database upgrade. As of 10g Oracle Database, Oracle recommends to use DBMS_STATS procedure to gather statistics. This procedure gather statistics for dictionary schemas SYS, SYSTEM, etc..
# STATISTICS FOR ALL DICTIONARY OBJECTS
SYS> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS; ...
If you ignore to keep stats up to date on data dictionary, then updating itself time taking process. Oracle recommends collect stats on you dictionary as part of pre-upgrade task prior to downtime.
CHECK ANY CORRUPTION IN THE DICTIONARY
# EXECUTE AS SYS SCHEMA SYS> spool analyze.sql;
SYS> SELECT 'Analyze cluster "'||cluster_name||'" validate structure cascade;' FROM dba_clusters
WHERE owner='SYS' UNION
SELECT 'Analyze table "'||table_name||'" validate structure cascade;' FROM dba_tables
WHERE owner='SYS' AND partitioned='NO'
AND (iot_type='IOT' OR iot_type is NULL) UNION
SELECT 'Analyze table "'||table_name||'" validate structure cascade into invalid_rows;' FROM dba_tables
WHERE owner='SYS' AND partitioned='YES'; SYS> spool off;
# TO FIND ANY LOGICAL CORRUPTION
SYS> @$ORACLE_HOME/rdbms/admin/utlvalid.sql; SYS> spool analyze.log
SYS> @analyze.sql; SYS> spool off;
Should not return any error.
SCRIPT TO TRACK FOR DATABASE LINKS
# DBLINK BACKUP (In case the database has to be downgraded again) $ vi dblink.sql
SELECT 'CREATE '||DECODE(U.NAME,'PUBLIC','public ')||'DATABASE LINK '||CHR(10) ||DECODE(U.NAME,'PUBLIC',Null, 'SYS','',U.NAME||'.')|| L.NAME||chr(10)
||'CONNECT TO ' || L.USERID || ' IDENTIFIED BY "'||L.PASSWORD||'" USING '''||L.HOST||''''
||chr(10)||';' TEXT
FROM SYS.LINK$ L, SYS.USER$ U WHERE L.OWNER# = U.USER#; SYS> spool dblink.log SYS> @dblink.sql; SYS> spool off;
ORACLE DATABASE VAULT
If you have enabled Oracle Database vault option in your current home, you must disable it. If you do not disable it, DBUA will return an error to disable prior to upgrade.
# CHECK ORACLE DATABASE VAULT IS ENABLED OR NOT
SYS> select * from v$option where parameter='Oracle Database Vault'; PARAMETER VALUE
--- ---
Oracle Database Vault FALSE
NOTE 453903.1 – Enabling and Disabling Oracle Database Vault in UNIX.
BACK UP ENTERPRISE MANAGER DATABASE CONTROL DATA
You may ignore this action. After upgraded to 11g, suppose you decide to downgrade from 11g to 10g then direct downgrade of EM is not supported. So it is better to save the EM data and restore it back. The utility emdwgrd can be used to keep a copy of database control files and data before upgrading your database. It resides in $ORACLE_HOME/bin directory. Please refer 870877.1.
RUN PRE-UPGRADE INFORMATION SCRIPT
Copy the Pre-Upgrade information script (utlu112i.sql) from 11g $ORACLE_HOME/rdbms/admin/ into
/tmp directory and start SQL*Plus. Execute the script. This script checks the database (which you
# SET 10G DATABASE ENV $ . ./db10g.env
$ echo $ORACLE_HOME
/u02/app/oracle/product/10.2.0/db_home
# ALREADY 11g S/W INSTALLED AT /u01/app/oracle/product/11.2.0/db_home
# COPY utlu112i.sql SCRIPT TO /tmp FROM 11g $ORACLE_HOME/rdbms/admin LOCATION. $ cd /u01/app/oracle/product/11.2.0/db_home/rdbms/admin
$ cp utlu112i.sql /tmp $ cd /tmp
# EXECUTE utlu112i.sql SCRIPT
SYS> spool pre_upgrade_11201_info.log SYS> @/tmp/utlu112i.sql;
SYS> spool off;
REVIEW PRE UPGRADE SCRIPT OUTPUT
$ cat pre_upgrade_11201_info.log SQL> @/tmp/utlu112i.sql;
Oracle Database 11.2 Pre-Upgrade Information Tool 10-03-2015 23:05:57
. ********************************************************************** Database: ********************************************************************** --> name: DEVDB --> version: 10.2.0.5.0 --> compatible: 10.2.0.1.0 --> blocksize: 8192
--> platform: Linux IA (32-bit) --> timezone file: V4
.
********************************************************************** Tablespaces: [make adjustments in the current environment]
********************************************************************** --> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 747 MB
.... AUTOEXTEND additional space required: 247 MB --> UNDOTBS1 tablespace is adequate for the upgrade. .... minimum required size: 10 MB
--> SYSAUX tablespace is adequate for the upgrade. .... minimum required size: 456 MB
.... AUTOEXTEND additional space required: 216 MB --> TEMP tablespace is adequate for the upgrade. .... minimum required size: 61 MB
.... AUTOEXTEND additional space required: 32 MB
--> EXAMPLE tablespace is adequate for the upgrade. .... minimum required size: 69 MB
.
********************************************************************** Flashback: OFF
********************************************************************** ********************************************************************** Update Parameters: [Update Oracle Database 11.2 init.ora or spfile] ********************************************************************** WARNING: --> "java_pool_size" needs to be increased to at least 64 MB .
********************************************************************** Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile] ********************************************************************** -- No renamed parameters found. No changes are required.
.
********************************************************************** **********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile] **********************************************************************
--> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
--> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
--> core_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
.
**********************************************************************
Components: [The following database components will be upgraded or installed] **********************************************************************
--> 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 --> OLAP Catalog [upgrade] VALID --> EM Repository [upgrade] VALID --> Oracle Text [upgrade] VALID --> Oracle XML Database [upgrade] VALID --> Oracle Java Packages [upgrade] VALID --> Oracle interMedia [upgrade] VALID --> Spatial [upgrade] VALID --> Data Mining [upgrade] VALID --> Expression Filter [upgrade] VALID --> Rule Manager [upgrade] VALID --> Oracle OLAP API [upgrade] VALID .
********************************************************************** Miscellaneous Warnings
********************************************************************** WARNING: --> Database is using a timezone file older than version 11. WARNING: --> Database is using a timezone file older than version 11. .... After the release migration, it is recommended that DBMS_DST package .... be used to upgrade the 10.2.0.5.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Database contains schemas with stale optimizer statistics. .... Refer to the Upgrade Guide for instructions to update
.... schema statistics prior to upgrading the database. .... Component Schemas with stale statistics:
.... SYS .... SYSMAN
WARNING: --> Database contains INVALID objects prior to upgrade. .... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to .... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid .... objects due to the upgrade.
.... USER PUBLIC has 1 INVALID objects. .... USER SYS has 2 INVALID objects.
WARNING: --> Database contains schemas with objects dependent on network packages.
.... Refer to the Upgrade Guide for instructions to configure Network ACLs. .... USER ORACLE_OCM has dependent objects.
WARNING: --> EM Database Control Repository exists in the database.
.... Direct downgrade of EM Database Control is not supported. Refer to the .... Upgrade Guide for instructions to save the EM data prior to upgrade. WARNING:--> recycle bin in use.
.... Your recycle bin is turned on and it contains .... 18 object(s). It is REQUIRED
.... that the recycle bin is empty prior to upgrading .... your database.
.... The command: PURGE DBA_RECYCLEBIN
.... must be executed immediately prior to executing your upgrade. .
PL/SQL procedure successfully completed.
Adjust the warnings reported by the utlu112i.sql script.
I have fixed following warnings prior to upgrade with help of oracle docs.
FIX THE WARNINGS REPORTED BY PRE-UPGRADED TOOL
If the current database contains objects with stale optimizer statistics, then it would be better to collect the statistics before upgrade process. If we ignore upgrade process will be slower depending upon number of objects with stale optimizer statistics.
# STALE OPTIMIZER STATISTICS FOR RDBMS DEFAULT SCHEMAS $ vi statistics_gather.sql;
grant analyze any to SYS;
exec dbms_stats.gather_dictionary_stats;
exec dbms_stats.gather_schema_stats('WMSYS',options=>'GATHER',estimate_percent
=>DBMS_STATS.AUTO_SAMPLE_SIZE,method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE); exec dbms_stats.gather_schema_stats('XDB',options=>'GATHER',estimate_percent =>
DBMS_STATS.AUTO_SAMPLE_SIZE, method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE); exec dbms_stats.gather_schema_stats('OUTLN',options=>'GATHER',estimate_percent =>
DBMS_STATS.AUTO_SAMPLE_SIZE,method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE); exec dbms_stats.gather_schema_stats('DBSNMP',options=>'GATHER',estimate_percent =>
DBMS_STATS.AUTO_SAMPLE_SIZE,method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE); exec dbms_stats.gather_schema_stats('SYSTEM',options=>'GATHER',estimate_percent =>
DBMS_STATS.AUTO_SAMPLE_SIZE,method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE); exec dbms_stats.gather_schema_stats('CTXSYS',options=>'GATHER',estimate_percent =>
DBMS_STATS.AUTO_SAMPLE_SIZE,method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE); exec dbms_stats.gather_schema_stats('SYS',options=>'GATHER',estimate_percent =>
DBMS_STATS.AUTO_SAMPLE_SIZE,method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE);
SYS> spool statistics_gather.log; SYS> @statistics_gather.sql;
SYS> spool off;
# FIX DEPRECATED PARAMETERS FOR 11G DATABASE
SYS> alter system reset background_dump_dest= '*' scope=spfile;
System altered.
SYS> alter system reset core_dump_dest= '*' scope=spfile;
System altered.
SYS> alter system reset user_dump_dest= '*' scope=spfile;
System altered.
# ADJUST JAVA_POOL_SIZE
SYS> alter system set java_pool_size=65m scope=spfile;
System altered.
# PRE-UPGRADED TOOL REPORTED WARNINGS FROM TABLESPACES SECTION
SYS> select tablespace_name from dba_data_files where autoextensible= 'YES';
...
Pre upgraded scrip reported some tablespaces need adequate space for upgrade process; they can
automatically extend by itself, if auto extendable option is enabled for those tablespaces. Using
If auto extend clause is not enabled, you can resize the tablespace at command line. As per warnings, you need to resize required tablespaces to set sufficient space.
# EXAMPLE FOR RESIZING SYSTEM DATAFILE
SYS> alter database datafile '/u02/app/oracle/oradata/devdb/system01.dbf' resize 1000m;
...
MISCELLANEOUS WARINGS
You can see bunch of various warnings about the current database. Even you ignore them, they may make the upgrade to run slower and may effect some of Oracle features that you use. You need to take care some warnings prior to upgrade and some after the upgrade.
CONFIGURE ENV FILE FOR 11G DATABASE
$ vi db11.env
# ENV SETUP FOR 11G DATABASE
export PATH=$ORACLE_HOME/bin:$PATH export ORACLE_BASE=/u01/app/oracle export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_home export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/lib export TNS_ADMIN=$ORACLE_HOME/network/admin export CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib export EDITOR=vi #. oraenv
CREATE PFILE FROM SPFILE
# CREATE PFILE FROM SPFILE
SYS> create pfile from spfile;
File created.
# COPY NEWLY CREATED PFILE FROM 10g $ORACLE_HOME/dbs to 11g $ORACLE_HOME/dbs # COPY ORACLE PASSWORDFILE FROM 10g $ORACLE_HOME/dbs to 11g $ORACLE_HOME/dbs $ echo $ORACLE_HOME
/u02/app/oracle/product/10.2.0/db_home/
$ cd /u02/app/oracle/product/10.2.0/db_home/dbs
$ cp initdevdb.ora /u01/app/oracle/product/11.2.0/db_home/dbs/ $ cp orapwdevdb /u01/app/oracle/product/11.2.0/db_home/dbs/
STOP 10g DATABASE COMPONENTS
# TO STOP ISQLPLUS (if it is running) $ isqlplusctl stop
# TO STOP ENTERPRISE MANAGER DBCONSOLE $ emctl stop dbconsole
...
# TO STOP LISTENER
$ stop listener <listener_name> ...
# SHUTDOWN THE DATABASE SYS> shutdown immediate; ...
# BACKUP 10G $ORACLE_HOME
$ cd /u02/app/oracle/product/10.2.0/
$ tar –czf /u04/bkp/orclhomebkp.tar.gz db_home
I maintain all physical files at /u02/app/oracle/oradata/devdb/ I would prefer to take cold backup because I have downtime.
# BACKUP DATABASE PHYSICAL FILES CONTROLFILES, DATAFILES AND LOGFILES $ cd /u02/app/oracle/oradata
$ tar –czf /u04/bkp/devdb.tar.gz devdb
CREATE NEW LISTENER FOR 11g $ORACLE_HOME
If you wish to take backup, take backup listener.ora, tnsnames.ora, sqlnet.ora file. But I would configure new listener. Step by step details for setting listener for 11g $ORACLE_HOME.
$ . ./db11.env $ netca
2) Select Add and Click on NEXT
3) Enter Listener name and click on NEXT
NOTE: In my case, listener name is LISTENER11g
Please refer following links to get light on Oracle network configuration.
https://www.scribd.com/doc/131516826/Registering-Database-Service-With-Listener https://www.scribd.com/doc/131514434/Oracle-Network-Configuration
4) Select TCP and click on NEXT
5) Choose port number, Default Port number is 1521, but I am using 1598 (Non Default Port).
When you create a listener on a NON DEFAULT PORT, PMON tries to register the database service(s) with this listener. PMON utilizes TNSENTRY naming method for this. PMON will look in tnsnames.ora file for the value it found in LOCAL_LISTENER. If it does not find this entry in the tnsnames.ora file, it will throw error. (Before start DBUA, you must add LOCAL_LISTENER entry in tnsnames.ora.
6) Choose No and click on NEXT
Click on NEXT and close the Screen. START LISTENER
$ lsnrctl start LISTENER11g
...
START DBUA FROM 11g ENVIRONMENT TO UPRGADE. $ . ./db11g.env
$ dbua
Click on NEXT
2) Select the database which you want to upgrade
Click on NEXT
DBUA shows some warnings that were not solved after running Pre-Upgrade (utlu112i.sql) script
Already DEVDB Database has been backed up, so I do not want take back up again.
Whether you want to move the datafiles while upgrade, though the "move datafile" check-box was not highlighted when I upgraded.
Check configuration for EM
Upgrade is complete Click on OK
Check upgrade results.
ENTERPRISE MANAGER FOR DEVDB
CONNECT TO DEVDB
SYS> select * from v$version; BANNER
--- Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production NLSRTL Version 11.2.0.1.0 - Production
SYS> select count(*) from dba_objects where status='INVALID'; COUNT(*)
--- 0
SYS> show parameter compatible;
NAME TYPE VALUE
--- --- --- compatible string 10.2.0.1.0
# SET COMPITIBLE=11.2.0.1.0
SYS> alter system set compatible='11.2.0.1.0' scope=spfile;
System altered.
SYS> shut immediate; ...
SYS> startup; ...
SYS> show parameter compatible;
NAME TYPE VALUE
--- --- --- compatible string 11.2.0.1.0
SYS> show parameter local_listener;
NAME TYPE VALUE
--- --- --- local_listener string LISTENER_DEVDB
POINTS TO NOTE :
When you create a listener on a NON-DEFAULT PORT, PMON will look for the value of LOCAL_LISTENER in tnsnames.ora file. If it does NOT find this entry, it will throw error. Before running DBUA you must add proper entry in 11g $ORACLE_HOME tnsnames.ora – (If you request to configure/upgrade EM).
ORACLE NETWORK CONFIGURAION FILES
$ cd $ORACLE_HOME/network/admin $ vi tnsnames.ora
# tnsnames.ora Network Configuration File:
/u01/app/oracle/product/11.2.0/db_home/network/admin/tnsnames.ora # Generated by Oracle configuration tools.
LISTENER_DEVDB =
(ADDRESS = (PROTOCOL = TCP)(HOST = DEVSERVER)(PORT = 1598))
DEVDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = DEVSERVER)(PORT = 1598)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = devdb) ) ) $ vi listener.ora
# listener.ora Network Configuration File:
/u01/app/oracle/product/11.2.0/db_home/network/admin/listener.ora # Generated by Oracle configuration tools.
LISTENER11G =
(DESCRIPTION_LIST = (DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = DEVSERVER)(PORT = 1598)) ) ) ADR_BASE_LISTENER11G = /u01/app/oracle SID_LIST_LISTENER11G = (SID_LIST = (SID_DESC = (SID_NAME = devdb) (ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_home) ) )
NEWLY CREATED PFILE PARAMETERS AFTER UPGRADE
devdb.__db_cache_size=620756992 devdb.__java_pool_size=67108864 devdb.__large_pool_size=4194304
devdb.__pga_aggregate_target=322961408 devdb.__sga_target=964689920 devdb.__shared_io_pool_size=0 devdb.__shared_pool_size=264241152 devdb.__streams_pool_size=0 *.audit_file_dest='/u02/app/oracle/admin/devdb/adump' *.compatible='11.2.0.1.0' *.control_files='/u02/app/oracle/oradata/devdb/control01.ctl','/u02/app/oracle/oradata/devdb/ control02.ctl','/u02/app/oracle/oradata/devdb/control03.ctl' *.db_block_size=8192 *.db_domain='' *.db_file_multiblock_read_count=16 *.db_name='devdb' *.db_recovery_file_dest_size=5242880000 *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area' *.diagnostic_dest='/u01/app/oracle' *.dispatchers='(PROTOCOL=TCP) (SERVICE=DEVDBXDB)' *.event='' *.java_pool_size=67108864 *.job_queue_processes=10 *.local_listener='LISTENER_DEVDB' *.log_archive_format='%t_%s_%r.dbf' *.open_cursors=300 *.pga_aggregate_target=320864256 *.processes=150 *.remote_login_passwordfile='EXCLUSIVE' *.sga_target=964689920 *.undo_management='AUTO' *.undo_tablespace='UNDOTBS1'
DEPRECATED PARAMETERS FROM 11G
background_dump_dest core_dump_dest
user_dump_dest
Above three parameters are replaced by diagnostic_dest
SYS> show parameter dump_dest;
NAME TYPE VALUE
--- --- ---
background_dump_dest string /u01/app/oracle/diag/rdbms/devdb/devdb/trace core_dump_dest string /u01/app/oracle/diag/rdbms/devdb/devdb/cdump user_dump_dest string /u01/app/oracle/diag/rdbms/devdb/devdb/trace
