A Initialization Parameter and Data Dictionary Changes

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

Initialization Parameters Deprecated in Release 10.1

The following initialization parameters were deprecated in release 10.1:

BUFFER_POOL_KEEP (replaced by DB_KEEP_CACHE_SIZE)
BUFFER_POOL_RECYCLE (replaced by DB_RECYCLE_CACHE_SIZE)
GLOBAL_CONTEXT_POOL_SIZE
LOCK_NAME_SPACE
LOG_ARCHIVE_START
MAX_ENABLED_ROLES
PARALLEL_AUTOMATIC_TUNING
PLSQL_COMPILER_FLAGS (replaced by PLSQL_CODE_TYPE and PLSQL_DEBUG)

Initialization Parameters Deprecated in Release 9.2

The following initialization parameters were deprecated in release 9.2:

DRS_START (replaced by DG_BROKER_START)

Initialization Parameters Deprecated in Release 9.0.1

The following initialization parameters were deprecated in release 9.0.1:

FAST_START_IO_TARGET (replaced by FAST_START_MTTR_TARGET)
MTS_CIRCUITS (replaced by CIRCUITS)
MTS_DISPATCHERS (replaced by DISPATCHERS)
MTS_MAX_DISPATCHERS (replaced by MAX_DISPATCHERS)
MTS_MAX_SERVERS (replaced by MAX_SHARED_SERVERS)
MTS_SERVERS (replaced by SHARED_SERVERS)
MTS_SESSIONS (replaced by SHARED_SERVER_SESSIONS)
PARALLEL_SERVER (replaced by CLUSTER_DATABASE)
PARALLEL_SERVER_INSTANCES (replaced by CLUSTER_DATABASE_INSTANCES)

Initialization Parameters Obsolete in Release 10.1

The following initialization parameters were made obsolete in release 10.1:

DBLINK_ENCRYPT_LOGIN
HASH_JOIN_ENABLED
LOG_PARALLELISM
MAX_ROLLBACK_SEGMENTS
MTS_CIRCUITS
MTS_DISPATCHERS
MTS_LISTENER_ADDRESS
MTS_MAX_DISPATCHERS
MTS_MAX_SERVERS
MTS_MULTIPLE_LISTENERS
MTS_SERVERS
MTS_SERVICE
MTS_SESSIONS
OPTIMIZER_MAX_PERMUTATIONS
ORACLE_TRACE_COLLECTION_NAME
ORACLE_TRACE_COLLECTION_PATH
ORACLE_TRACE_COLLECTION_SIZE
ORACLE_TRACE_ENABLE
ORACLE_TRACE_FACILITY_NAME
ORACLE_TRACE_FACILITY_PATH
PARTITION_VIEW_ENABLED
PLSQL_NATIVE_C_COMPILER
PLSQL_NATIVE_LINKER
PLSQL_NATIVE_MAKE_FILE_NAME
PLSQL_NATIVE_MAKE_UTILITY
ROW_LOCKING
SERIALIZABLE
TRANSACTION_AUDITING
UNDO_SUPPRESS_ERRORS

Initialization Parameters Obsolete in Release 9.2

The following initialization parameters were made obsolete in release 9.2:

DISTRIBUTED_TRANSACTIONS
MAX_TRANSACTION_BRANCHES
PARALLEL_BROADCAST_ENABLED
STANDBY_PRESERVES_NAMES

Initialization Parameters Obsolete in Release 9.0.1

The following initialization parameters were made obsolete in release 9.0.1:

ALWAYS_ANTI_JOIN
ALWAYS_SEMI_JOIN
DB_BLOCK_LRU_LATCHES
DB_BLOCK_MAX_DIRTY_TARGET
DB_FILE_DIRECT_IO_COUNT
GC_DEFER_TIME
GC_RELEASABLE_LOCKS
GC_ROLLBACK_LOCKS
HASH_MULTIBLOCK_IO_COUNT
INSTANCE_NODESET
JOB_QUEUE_INTERVAL
OPS_INTERCONNECTS
OPTIMIZER_PERCENT_PARALLEL
SORT_MULTIBLOCK_READ_COUNT
TEXT_ENABLE

Initialization Parameters Obsolete in Release 8.1

The following initialization parameters were made obsolete in release 8.1:

ALLOW_PARTIAL_SN_RESULTS
ARCH_IO_SLAVES
B_TREE_BITMAP_PLANS
BACKUP_DISK_IO_SLAVES
CACHE_SIZE_THRESHOLD
CLEANUP_ROLLBACK_ENTRIES
CLOSE_CACHED_OPEN_CURSORS
COMPATIBLE_NO_RECOVERY
COMPLEX_VIEW_MERGING
DB_BLOCK_CHECKPOINT_BATCH
DB_BLOCK_LRU_EXTENDED_STATISTICS
DB_BLOCK_LRU_STATISTICS
DB_FILE_SIMULTANEOUS_WRITES
DELAYED_LOGGING_BLOCK_CLEANOUTS
DISCRETE_TRANSACTIONS_ENABLED
DISTRIBUTED_RECOVERY_CONNECTION_HOLD_TIMEFAST_FULL_SCAN_ENABLED
ENT_DOMAIN_NAME
FREEZE_DB_FOR_FAST_INSTANCE_RECOVERY
GC_LATCHES
GC_LCK_PROCS
JOB_QUEUE_KEEP_CONNECTIONS
LARGE_POOL_MIN_ALLOC
LGWR_IO_SLAVES
LM_LOCKS
LM_PROCS
LM_RESS
LOCK_SGA_AREAS
LOG_ARCHIVE_BUFFER_SIZE
LOG_ARCHIVE_BUFFERS
LOG_BLOCK_CHECKSUM
LOG_FILES
LOG_SIMULTANEOUS_COPIES
LOG_SMALL_ENTRY_MAX_SIZE
MTS_RATE_LOG_SIZE
MTS_RATE_SCALE
OGMS_HOME
OPS_ADMIN_GROUP
OPTIMIZER_SEARCH_LIMIT
PARALLEL_DEFAULT_MAX_INSTANCES
PARALLEL_MIN_MESSAGE_POOL
PARALLEL_SERVER_IDLE_TIME
PARALLEL_TRANSACTION_RESOURCE_TIMEOUT
PUSH_JOIN_PREDICATE
REDUCE_ALARM
ROW_CACHE_CURSORS
SEQUENCE_CACHE_ENTRIES
SEQUENCE_CACHE_HASH_BUCKETS
SHARED_POOL_RESERVED_MIN_ALLOC
SNAPSHOT_REFRESH_KEEP_CONNECTIONS
SNAPSHOT_REFRESH_PROCESSES
SORT_DIRECT_WRITES
SORT_READ_FAC
SORT_SPACEMAP_SIZE
SORT_WRITE_BUFFER_SIZE
SORT_WRITE_BUFFERS
SPIN_COUNT
TEMPORARY_TABLE_LOCKS
USE_ISM

New Default Value for DISPATCHERS

Starting with release 10.1, the default for DISPATCHERS is '(PROTOCOL=TCP)'. DISPATCHERS is given this default value if it is not set or if it is set to '' and SHARED_SERVERS is set to 1 or higher.

In previous releases, there was no default value for DISPATCHERS.

New Default Value for SHARED_SERVERS

Starting with release 10.1, if DISPATCHERS is set such that the total number of dispatchers is equal to 0, then SHARED_SERVERS defaults to 0. If DISPATCHERS is set such that the total number of dispatchers is greater than 0, then SHARED_SERVERS defaults to 1 as in previous releases.

In previous releases, if DISPATCHERS was set such that the number of dispatchers is equal to 0, then SHARED_SERVERS defaulted to 1.

New Default Value for MAX_SHARED_SERVERS

Starting with release 10.1, there is no preset default for MAX_SHARED_SERVERS. The maximum number of shared servers varies depending on the number of free process slots. If MAX_SHARED_SERVERS is not set or is set to a value greater than or equal to PROCESSES, then PMON will not spawn any more shared servers if the number of free process slots is either 2 (if PROCESSES is less than 24) or is less than 1 / 8, unless the existing servers are involved in a deadlock situation. If the existing servers are involved in a deadlock situation, then no matter the transaction load, a new server will be spawned if there is a free process slot.

In previous releases, the default for MAX_SHARED_SERVERS is 20, or 2 * SHARED_SERVERS, whichever is greater, subject to the condition that MAX_SHARED_SERVERS does not exceed PROCESSES.

Starting with release 10.1, SHARED_SERVERS can be set higher than MAX_SHARED_SERVERS, in which case the number of servers will remain constant at the level set for SHARED_SERVERS. This is to allow the range SHARED_SERVERS - MAX_SHARED_SERVERS to be changed without having to change these parameters in a specific order.

In previous releases, SHARED_SERVERS cannot be set higher than MAX_SHARED_SERVERS.

New Default Value for SHARED_SERVER_SESSIONS

Starting with release 10.1, there is no preset default for SHARED_SERVER_SESSIONS. That is, if SHARED_SERVER_SESSIONS is not specified, then shared server sessions can be created as needed and as permitted by the session limit.

In previous releases, the default for SHARED_SERVER_SESSIONS was the maximum number of virtual circuits (CIRCUITS), or the maximum number of database sessions (SESSIONS) - 5, whichever is smaller.

New Default Value for CIRCUITS

Starting with release 10.1, there is no preset default for CIRCUITS. That is, if CIRCUITS is not specified, then circuits can be created as needed and as permitted by dispatcher constraints and system resources.

In previous releases, the default for CIRCUITS was the maximum number of database sessions (SESSIONS) if shared server mode was enabled, 0 otherwise.

New Default Value for MAX_DISPATCHERS

Starting with release 10.1, there is no preset default for MAX_DISPATCHERS. MAX_DISPATCHERS no longer limits the number of dispatchers; the user can increase the number of dispatchers via the DISPATCHERS parameter as long as there are free process slots and system resources.

In previous releases, the default for MAX_DISPATCHERS was 5, or the total number of dispatchers specified via the DISPATCHERS parameter, whichever was greater.

Retaining Parameter Settings without Modifications

You do not alter the parameters from their previous settings:

These settings are the most common scenario. In this case, you already have accounted for the space required for parallel execution in the shared pool.

Using PARALLEL_AUTOMATIC_TUNING

You alter the parameters from their previous settings to the following settings:

In this case, parallel execution allocates buffers from the large pool based on the Oracle Database's automatic calculation. Buffer allocation is more efficient, and failures to allocate are isolated from the clients of the shared pool.

Using PARALLEL_AUTOMATIC_TUNING and Setting LARGE_POOL_SIZE

You alter the parameters from their previous settings to the following settings:

In this case, parallel execution allocates buffers from the large pool. After initial testing with LARGE_POOL_SIZE not set, you determined that the default calculation for LARGE_POOL_SIZE did not reflect your requirements for the large pool. Therefore, you decided to manually set LARGE_POOL_SIZE. After you set LARGE_POOL_SIZE properly, buffer allocation is more efficient, and failures to allocate are isolated from the clients of the shared pool.

Using PARALLEL_AUTOMATIC_TUNING without Modifying SHARED_POOL_SIZE

You alter the parameters from their previous settings to the following settings:

In this case, parallel execution allocates buffers from the large pool, but because you did not modify SHARED_POOL_SIZE, it is likely that the SGA will be unnecessarily large, causing performance problems. Therefore, avoid setting PARALLEL_AUTOMATIC_TUNING to true without modifying the settings of SHARED_POOL_SIZE and LARGE_POOL_SIZE appropriately.

Changing to the New Archive Log Destination Parameters

After you determine the new archive destinations, associated states, and options, complete the following steps to change from the old archive log destination parameters to the new ones:

1. Use ALTER SYSTEM to set LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.

2. Use ALTER SYSTEM to set LOG_ARCHIVE_DUPLEX_DEST to null.

3. Use ALTER SYSTEM to set LOG_ARCHIVE_DEST to null.

4. Use ALTER SYSTEM to set any LOG_ARCHIVE_DEST_STATE_n parameters to 'defer' or 'enable' as required. Although enable is the default, Oracle recommends that you explicitly set a state for each destination.

5. Use ALTER SYSTEM to set at least one LOG_ARCHIVE_DEST_n parameter to a value specifying a local destination.

6. Use ALTER SYSTEM to set other LOG_ARCHIVE_DEST_n parameters as required.

7. Use ALTER SYSTEM to set LOG_ARCHIVE_MIN_SUCCEED_DEST to the required value.

For example, assume there are the following two destinations:

• /oracle/dbs/arclog

• /backup/dbs/arclog

Both destinations are mandatory (minimum succeed destination count is 2). The new destinations are the following:

• /oracle/dbs/arclog (local)

• stndby1 (a standby database)

• /backup/dbs/arclog

• /backup2/dbs/arclog

The first destination, the standby destination, and either of the backup destinations are mandatory (minimum succeed destination count is 3).

With these assumptions, issue the following SQL statements to change your old archive log destination parameters to the new ones:

ALTER SYSTEM SET LOG_ARCHIVE_MIN_SUCCEED_DEST = 1;

ALTER SYSTEM SET LOG_ARCHIVE_DUPLEX_DEST = ' ';

ALTER SYSTEM SET LOG_ARCHIVE_DEST = ' ';

ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1 = 'enable';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2 = 'enable';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_3 = 'enable';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_4 = 'enable';

ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 = 'LOCATION=/oracle/dbs/arclog MANDATORY';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_2 = 'SERVICE=stndby1 MANDATORY';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_3 = 'LOCATION=/backup/dbs/arclog OPTIONAL';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_4 = 'LOCATION=/backup2/dbs/arclog OPTIONAL';
ALTER SYSTEM SET LOG_ARCHIVE_MIN_SUCCEED_DEST = 3;

Changing Back to the Old Archive Log Destination Parameters

Complete the following steps to change back to the old archive log destination parameters:

1. Use ALTER SYSTEM to set LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.

2. Use ALTER SYSTEM to set all LOG_ARCHIVE_DEST_n parameters to NULL.

3. Use ALTER SYSTEM to set the LOG_ARCHIVE_DEST parameter to a value specifying a local destination.

4. Use ALTER SYSTEM to set the LOG_ARCHIVE_DUPLEX_DEST parameter as required.

5. Use ALTER SYSTEM to set LOG_ARCHIVE_MIN_SUCCEED_DEST to the required value.

For example, assume there are the following two destinations:

• /oracle/dbs/arclog (LOG_ARCHIVE_DEST_1)

• /backup/dbs/arclog (LOG_ARCHIVE_DEST_4)

Both destinations are mandatory. The new destinations and minimum succeed count are the same.

With these assumptions, issue the following SQL statements to change your new archive log destination parameters to the old ones:

ALTER SYSTEM SET LOG_ARCHIVE_MIN_SUCCEED_DEST = 1;

ALTER SYSTEM SET LOG_ARCHIVE_DEST_4 = ' ';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 = ' ';

ALTER SYSTEM SET LOG_ARCHIVE_DEST = '/oracle/dbs/arclog';

ALTER SYSTEM SET LOG_ARCHIVE_DUPLEX_DEST = '/backup/dbs/arclog';

ALTER SYSTEM SET LOG_ARCHIVE_MIN_SUCCEED_DEST = 2;

Possible Errors During the Transition in Parameters

When you follow the procedures described previously in this section for changing your archive destination parameters, you may encounter the following error messages in your log files if archiving is enabled:

• In the Alert log - "Archiving not possible: No available destinations"

• In the Trace log - "ARCH: INCOMPLETE, no available destinations"

You will not encounter these errors if archiving is disabled. The errors may occur during the procedure when there are no valid archive destinations. However, when the transition in parameters is complete, the errors should cease. You should not disable archiving during the transition to avoid these errors.

Static Data Dictionary Views Deprecated in Release 10.1

The following static data dictionary views were deprecated in release 10.1:

ALL_STORED_SETTINGS (replaced by ALL_PLSQL_OBJECT_SETTINGS)
DBA_STORED_SETTINGS (replaced by DBA_PLSQL_OBJECT_SETTINGS)
USER_STORED_SETTINGS (replaced by USER_PLSQL_OBJECT_SETTINGS)

Static Data Dictionary Views Deprecated in Release 9.2

The following static data dictionary views were deprecated in release 9.2:

ALL_RULESETS (replaced by ALL_RULE_SETS)
DBA_RULESETS (replaced by DBA_RULE_SETS)
USER_RULESETS (replaced by USER_RULE_SETS)

Static Data Dictionary Views Deprecated in Release 9.0.1

The following static data dictionary views were deprecated in release 9.0.1:

ALL_REGISTERED_SNAPSHOTS (replaced by ALL_REGISTERED_MVIEWS)
ALL_SNAPSHOT_LOGS (replaced by ALL_BASE_TABLE_MVIEWS and ALL_MVIEW_LOGS)
ALL_SNAPSHOT_REFRESH_TIMES (replaced by ALL_MVIEW_REFRESH_TIMES)
DBA_REGISTERED_SNAPSHOT_GROUPS (replaced by DBA_REGISTERED_MVIEW_GROUPS)
DBA_REGISTERED_SNAPSHOTS (replaced by DBA_REGISTERED_MVIEWS)
DBA_SNAPSHOT_LOG_FILTER_COLS (replaced by DBA_MVIEW_LOG_FILTER_COLS)
DBA_SNAPSHOT_LOGS (replaced by DBA_BASE_TABLE_MVIEWS and DBA_MVIEW_LOGS)
DBA_SNAPSHOT_REFRESH_TIMES (replaced by DBA_MVIEW_REFRESH_TIMES)
USER_REGISTERED_SNAPSHOTS (replaced by USER_REGISTERED_MVIEWS)
USER_SNAPSHOT_LOGS (replaced by USER_BASE_TABLE_MVIEWS and USER_MVIEW_LOGS)
USER_SNAPSHOT_REFRESH_TIMES (replaced by USER_MVIEW_REFRESH_TIMES)

Static Data Dictionary Views Deprecated in Release 8.1

The following static data dictionary views were deprecated in release 8.1:

ALL_SNAPSHOTS (replaced by ALL_MVIEWS)
ALL_SUMMARIES (replaced by ALL_MVIEW_ANALYSIS)
ALL_SUMMARY_AGGREGATES (replaced by ALL_MVIEW_AGGREGATES)
ALL_SUMMARY_DETAIL_TABLES (replaced by ALL_MVIEW_DETAIL_RELATIONS)
ALL_SUMMARY_JOINS (replaced by ALL_MVIEW_JOINS)
ALL_SUMMARY_KEYS (replaced by ALL_MVIEW_KEYS)
DBA_SNAPSHOTS (replaced by DBA_MVIEWS)
DBA_SUMMARIES (replaced by DBA_MVIEW_ANALYSIS)
DBA_SUMMARY_AGGREGATES (replaced by DBA_MVIEW_AGGREGATES)
DBA_SUMMARY_DETAIL_TABLES (replaced by DBA_MVIEW_DETAIL_RELATIONS)
DBA_SUMMARY_JOINS (replaced by DBA_MVIEW_JOINS)
DBA_SUMMARY_KEYS (replaced by DBA_MVIEW_KEYS)
USER_SNAPSHOTS (replaced by USER_MVIEWS)
USER_SUMMARIES (replaced by USER_MVIEW_ANALYSIS)
USER_SUMMARY_AGGREGATES (replaced by USER_MVIEW_AGGREGATES)
USER_SUMMARY_DETAIL_TABLES (replaced by USER_MVIEW_DETAIL_RELATIONS)
USER_SUMMARY_JOINS (replaced by USER_MVIEW_JOINS)
USER_SUMMARY_KEYS (replaced by USER_MVIEW_KEYS)

Static Data Dictionary Views Obsolete in Release 10.1

The following static data dictionary views were made obsolete in release 10.1:

Static Data Dictionary Views with Renamed Columns in Release 9.0.1

The static data dictionary view columns listed in Table A-5 were renamed in release 9.0.1:

Static Data Dictionary Views with Dropped Columns in Release 9.0.1

The following static data dictionary view columns were dropped in release 9.0.1:

Static Data Dictionary Views with Dropped Columns in Release 8.1

The following static data dictionary view columns were dropped in release 8.1:

Dynamic Performance Views Deprecated in Release 10.1

The following dynamic performance views were deprecated in release 10.1:

GV$CACHE
GV$CACHE_TRANSFER
GV$CLASS_CACHE_TRANSFER (replaced by GV$INSTANCE_CACHE_TRANSFER)
GV$FALSE_PING
GV$FILE_CACHE_TRANSFER (replaced by GV$INSTANCE_CACHE_TRANSFER)
GV$GC_ELEMENTS_WITH_COLLISIONS
GV$LOCK_ACTIVITY
GV$TEMP_CACHE_TRANSFER (replaced by GV$INSTANCE_CACHE_TRANSFER)
V$CACHE
V$CACHE_LOCK
V$CACHE_TRANSFER
V$CLASS_CACHE_TRANSFER (replaced by V$INSTANCE_CACHE_TRANSFER)
V$FALSE_PING
V$FILE_CACHE_TRANSFER (replaced by V$INSTANCE_CACHE_TRANSFER)
V$GC_ELEMENTS_WITH_COLLISIONS
V$LOCK_ACTIVITY
V$TEMP_CACHE_TRANSFER (replaced by V$INSTANCE_CACHE_TRANSFER)

Dynamic Performance Views Deprecated in Release 9.2

The following dynamic performance views were deprecated in release 9.2:

GV$SORT_USAGE (replaced by GV$TEMPSEG_USAGE)
V$SORT_USAGE (replaced by V$TEMPSEG_USAGE)

Dynamic Performance Views Deprecated in Release 9.0.1

The following dynamic performance views were deprecated in release 9.0.1:

GV$BSP (replaced by GV$CR_BLOCK_SERVER)
GV$CLASS_PING (replaced by GV$CLASS_CACHE_TRANSFER)
GV$DLM_ALL_LOCKS (replaced by GV$GES_ENQUEUE)
GV$DLM_CONVERT_LOCAL (replaced by GV$GES_CONVERT_LOCAL)
GV$DLM_CONVERT_REMOTE (replaced by GV$GES_CONVERT_REMOTE)
GV$DLM_LATCH (replaced by GV$GES_LATCH)
GV$DLM_LOCKS (replaced by GV$GES_BLOCKING_ENQUEUE)
GV$DLM_MISC (replaced by GV$GES_STATISTICS)
GV$DLM_RESS (replaced by GV$GES_RESOURCE)
GV$DLM_TRAFFIC_CONTROLLER (replaced by GV$GES_TRAFFIC_CONTROLLER)
GV$FILE_PING (replaced by GV$FILE_CACHE_TRANSFER)
GV$LOCK_ELEMENT (replaced by GV$GC_ELEMENT)
GV$LOCKS_WITH_COLLISIONS (replaced by GV$GC_ELEMENTS_WITH_COLLISIONS)
GV$MAX_ACTIVE_SESS_TARGET_MTH (replaced by GV$ACTIVE_SESS_POOL_MTH)
GV$MTS (replaced by GV$SHARED_SERVER_MONITOR)
GV$PING (replaced by GV$CACHE_TRANSFER)
GV$TEMP_PING (replaced by GV$TEMP_CACHE_TRANSFER)
V$BSP (replaced by V$CR_BLOCK_SERVER)
V$CLASS_PING (replaced by V$CLASS_CACHE_TRANSFER)
V$DLM_ALL_LOCKS (replaced by V$GES_ENQUEUE)
V$DLM_CONVERT_LOCAL (replaced by V$GES_CONVERT_LOCAL)
V$DLM_CONVERT_REMOTE (replaced by V$GES_CONVERT_REMOTE)
V$DLM_LATCH (replaced by V$GES_LATCH)
V$DLM_LOCKS (replaced by V$GES_BLOCKING_ENQUEUE)
V$DLM_MISC (replaced by V$GES_STATISTICS)
V$DLM_RESS (replaced by V$GES_RESOURCE)
V$DLM_TRAFFIC_CONTROLLER (replaced by V$GES_TRAFFIC_CONTROLLER)
V$FILE_PING (replaced by V$FILE_CACHE_TRANSFER)
V$LOCK_ELEMENT (replaced by V$GC_ELEMENT)
V$LOCKS_WITH_COLLISIONS (replaced by V$GC_ELEMENTS_WITH_COLLISIONS)
V$MAX_ACTIVE_SESS_TARGET_MTH (replaced by V$ACTIVE_SESS_POOL_MTH)
V$MTS (replaced by V$SHARED_SERVER_MONITOR)
V$PING (replaced by V$CACHE_TRANSFER)
V$TEMP_PING (replaced by V$TEMP_CACHE_TRANSFER)

Dynamic Performance Views Obsolete in Release 10.1

The following dynamic performance views were made obsolete in release 10.1:

Dynamic Performance Views Obsolete in Release 9.2

The following dynamic performance views were made obsolete in release 9.2:

Dynamic Performance Views Obsolete in Release 9.0.1

The following dynamic performance views were made obsolete in release 9.0.1:

Dynamic Performance Views Obsolete in Release 8.1

The following dynamic performance views were made obsolete in release 8.1:

Dynamic Performance Views with Renamed Columns in Release 9.2

The dynamic performance view columns listed in Table A-7 were renamed in release 9.2:

Dynamic Performance Views with Renamed Columns in Release 9.0.1

The dynamic performance view columns listed in Table A-8 were renamed in release 9.0.1:

Dynamic Performance Views with Renamed Columns in Release 8.1

The dynamic performance view columns listed in Table A-9 were renamed in release 8.1:

Dynamic Performance Views with Dropped Columns in Release 9.2

The following dynamic performance view columns were dropped in release 9.2:

Dynamic Performance Views with Dropped Columns in Release 9.0.1

The following dynamic performance view columns were dropped in release 9.0.1:

Dynamic Performance Views with Dropped Columns in Release 8.1

The following dynamic performance view columns were dropped in release 8.1: