Oracle 11g Deprecated Initialization Parameters

How to Check Deprecated Initialization Parameters:

Run the following command on your SQL Prompt, it will give you the list of Deprecated Initialization Parameters in your installed Oracle Version, Our concern is to check it for Oeacle 11g Release 1 (11.1).

SQL> SELECT name FROM v$parameter WHERE isdeprecated = ‘TRUE’;

Check the List of Deprecated Initialization Parameters

Initialization Parameters Deprecated in Oracle Database 11g Release 1 (11.1):

1. BACKGROUND_DUMP_DEST (replaced by DIAGNOSTIC_DEST)
2. OMMIT_WRITE
3. CORE_DUMP_DEST (replaced by DIAGNOSTIC_DEST)
4. INSTANCE_GROUPS
5. LOG_ARCHIVE_LOCAL_FIRST
6. PLSQL_DEBUG (replaced by PLSQL_OPTIMIZE_LEVEL)
7. PLSQL_V2_COMPATIBILITY
8. REMOTE_OS_AUTHENT
9. STANDBY_ARCHIVE_DEST
10. TRANSACTION_LAG (attribute of the CQ_NOTIFICATION$_REG_INFO object)
11. USER_DUMP_DEST (replaced by DIAGNOSTIC_DEST)

Initialization Parameters Deprecated in Oracle Database 10g Release 2 (10.2) :

LOGMNR_MAX_PERSISTENT_SESSIONS
MAX_COMMIT_PROPAGATION_DELAY
REMOTE_ARCHIVE_ENABLE
SERIAL_REUSE
SQL_TRACE

Compatibility Issues with Initialization Parameters:

The lists of deprecated and obsolete initialization parameters earlier in this page show changes to initialization parameters across Oracle 11g and Oracle 10g Releases of oracle database. However, certain initialization parameter changes require special attention because they might raise compatibility issues for your database. These parameter changes are described in the following sections.

Compatibility Issues Introduced in Oracle Database 11g Release 1 (11.1)

New Default Value for UNDO_MANAGEMENT
Starting with Oracle Database 11g Release 1 (11.1), the default value of the UNDO_MANAGEMENT parameter is AUTO so that automatic undo management is enabled by default. You must set the parameter to MANUAL to turn off automatic undo management, if required. Compatibility Issues Introduced in Oracle Database 10g

Change in Behavior for SESSION_CACHED_CURSORS
Starting with Oracle Database 10g Release 1 (10.1), the number of cached cursors is determined by the SESSION_CACHED_CURSORS initialization parameter. In previous Oracle Database releases, the number of SQL cursors cached by PL/SQL was determined by the OPEN_CURSORS initialization parameter.

New Default Value for DB_BLOCK_SIZE
Starting with Oracle Database 10g Release 1 (10.1), the default value of DB_BLOCK_SIZE is operating system specific, but is typically 8 KB (8192 bytes). In previous Oracle Database releases, the default value was 2 KB (2048 bytes). If DB_BLOCK_SIZE is not specified in the parameter file when upgrading from Oracle Database9i Release 2 (9.2), then you receive an error when attempting to start up your database. Add the following to your parameter file:

DB_BLOCK_SIZE = 2048

If DB_BLOCK_SIZE is specified in the parameter file, then Oracle Database uses this value instead of the default value of 8 KB.