Skip Headers

Oracle9i Database Migration
Release 2 (9.2)

Part Number A96530-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page Go to next page
View PDF

A
Changes to Initialization Parameters and the Data Dictionary

This appendix lists changes to initialization parameters and the data dictionary across different releases of Oracle. This appendix also discusses compatibility issues with certain initialization parameters.

This appendix covers the following topics:

Initialization Parameter Changes

The following sections list changes to initialization parameters across different releases of Oracle:

Deprecated Initialization Parameters

The following sections list initialization parameters that have been deprecated. A deprecated parameter behaves the same way as a regular parameter, except that a warning message is displayed at instance startup if a deprecated parameter is specified in a parameter file. In addition, all deprecated parameters are logged to the alert log at instance startup:

Initialization Parameters Deprecated in Release 9.2

The following initialization parameters were deprecated in release 9.2:

Deprecated In Favor Of

DRS_START

DG_BROKER_START

Initialization Parameters Deprecated in Release 9.0.1

The following initialization parameters were deprecated in release 9.0.1:

Deprecated In Favor Of

MTS_CIRCUITS

CIRCUITS

MTS_DISPATCHERS

DISPATCHERS

MTS_MAX_DISPATCHERS

MAX_DISPATCHERS

MTS_MAX_SERVERS

MAX_SHARED_SERVERS

MTS_SERVERS

SHARED_SERVERS

MTS_SESSIONS

SHARED_SERVER_SESSIONS

PARALLEL_SERVER

CLUSTER_DATABASE

PARALLEL_SERVER_INSTANCES

CLUSTER_DATABASE_INSTANCES

Obsolete Initialization Parameters

The following sections list initialization parameters that have been made obsolete:

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_LISTENER_ADDRESS

MTS_MULTIPLE_LISTENERS

MTS_RATE_LOG_SIZE

MTS_RATE_SCALE

MTS_SERVICE

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

Compatibility Issues with Initialization Parameters

The lists of deprecated and obsolete initialization parameters earlier in this appendix show changes to initialization parameters across different releases of Oracle. However, certain initialization parameter changes require special attention because they may raise compatibility issues for your database. These parameter changes are described in this section.

New Default Value for DB_BLOCK_CHECKSUM

Starting with release 9.0.1, the DB_BLOCK_CHECKSUM initialization parameter has a new default value. In previous releases, the default value was false, but in release 9.0.1 and higher, the default value is true.

See Also:

DB_BLOCK_CHECKSUM in Oracle9i Database Reference

Maximum Number of Job Queue Processes

In Oracle9i, the maximum number of job queue processes that can be spawned per instance is 1000. In previous releases, the maximum number was 36. The JOB_QUEUE_PROCESSES initialization parameter controls the number of job queue processes.

See Also:

JOB_QUEUE_PROCESSES in Oracle9i Database Reference

The ORACLE_TRACE_ENABLE Parameter

Starting with release 8.1.7, the ORACLE_TRACE_ENABLE initialization parameter is dynamic. The default value is false.

To enable Oracle Trace collections for the server, use ALTER SYSTEM or ALTER SESSION to set ORACLE_TRACE_ENABLE to true. This setting alone does not start an Oracle Trace collection, but it allows Oracle Trace to be used with the server.

With ORACLE_TRACE_ENABLE set to true, Oracle Trace collection of server event data can then be performed in one of the following ways:

The SERIALIZABLE Parameter

Starting with release 8.1.6, setting the SERIALIZABLE initialization parameter to true is no longer supported. This is not the same as "obsolete". The parameter still shows up as a valid parameter in the V$PARAMETER data dictionary view.

The default behavior henceforth is as if SERIALIZABLE were set to false. Use the SET TRANSACTION ISOLATION LEVEL SERIALIZABLE command to achieve similar transaction isolation behavior. You can also use ALTER SESSION SET ISOLATION_LEVEL = SERIALIZABLE to get the behavior for a full session.

SORT_AREA_SIZE and SORT_DIRECT_WRITES Parameters

The SORT_DIRECT_WRITES initialization parameter is obsolete in release 8.1 and higher. If you had SORT_DIRECT_WRITES set to FALSE or AUTO in a past release, then the sort buffers were kept in the buffer cache whenever possible. Because SORT_DIRECT_WRITES is obsolete in release 8.1 and higher, the sort buffers could go directly to disk if you do not adjust your SORT_AREA_SIZE initialization parameter.

You should increase the value of SORT_AREA_SIZE if either of the following conditions were true in a past release:

If either of these conditions were true in a past release, then increase the value of SORT_AREA_SIZE for better performance.

New Default Value for LOG_CHECKPOINT_TIMEOUT

Starting with release 8.1.5, the LOG_CHECKPOINT_TIMEOUT initialization parameter has a new default value. In previous releases, the default value was zero seconds, but in release 8.1.5 and higher, the default value is 1800 seconds.

See Also:

LOG_CHECKPOINT_TIMEOUT in Oracle9i Database Reference

The O7_DICTIONARY_ACCESSIBILITY Parameter

The O7_DICTIONARY_ACCESSIBILITY initialization parameter controls whether to continue Oracle7 data dictionary behavior. Use of this initialization parameter is only a temporary expedient. Starting with release 9.0.1, the default value of this initialization parameter is false.

See Also:

"Data Dictionary Protection" for more information.

The DML_LOCKS Parameter

Oracle9i systems typically consume more DML locks while performing DDL operations than are required for Oracle7 systems. Nevertheless, the Oracle7 DML_LOCKS parameter default settings are usually adequate for Oracle9i systems, even for DML-intensive applications.

The default value of DML_LOCKS is a multiple of the number of transactions, which is calculated from the number of rollback segments. However, in Oracle9i fewer transactions are used per rollback segment than are used in Oracle7. Consequently, DML_LOCKS has a lower default value in Oracle9i. Under some extreme load conditions, you may need to increase the DML_LOCKS parameter value.

You may also need to adjust the TRANSACTION_PER_ROLLBACK_SEGMENT parameter setting, depending on the operating system-specific settings. An informational message about this change may be displayed during database startup operations.

The DB_DOMAIN Parameter

Starting with release 8.1, if the DB_DOMAIN initialization parameter is not set, then it is set to NULL by default. In prior releases of Oracle, the default setting was the following:

WORLD

A NULL setting for DB_DOMAIN may cause database connection problems in some environments. If you are upgrading from release 8.0.6 or earlier, then make sure the DB_DOMAIN initialization parameter in your initialization parameter file is set to one of the following:

If DB_DOMAIN is not set in your current database, then set it to WORLD before you upgrade.

If DB_DOMAIN is set to a valid domain for your environment in your current database, then retain the setting in your initialization parameter file when you upgrade.

Parallel Execution Allocated from Large Pool

Starting with release 8.1, parallel execution message buffers are allocated from the large pool whenever PARALLEL_AUTOMATIC_TUNING is set to true. In previous releases, this allocation was from the shared pool. If you are upgrading from release 8.0.6 or earlier, and you choose to set PARALLEL_AUTOMATIC_TUNING to true, then you can avoid problems by modifying the settings for the following initialization parameters:

Typically, you should reduce the setting of SHARED_POOL_SIZE and raise the setting of LARGE_POOL_SIZE to avoid problems. Alternatively, you can reduce the setting of SHARED_POOL_SIZE and let Oracle calculate the setting of LARGE_POOL_SIZE. Oracle calculates a default LARGE_POOL_SIZE only if PARALLEL_AUTOMATIC_TUNING is set to true and LARGE_POOL_SIZE is not set.

If PARALLEL_AUTOMATIC_TUNING is not set or set to false, and if LARGE_POOL_SIZE is not set, then the value of LARGE_POOL_SIZE defaults to 0.

See Also:

Oracle9i Database Reference and Oracle9i Database Performance Tuning Guide and Reference for more information about other effects of the PARALLEL_AUTOMATIC_TUNING initialization parameter.

The following scenarios illustrate the behavior that results from various initialization parameter settings when you upgrade to release 8.1 or higher.

Retaining Parameter Settings without Modifications

You do not alter the parameters from their previous settings:

Table A-1  Retaining Parameter Settings without Modifications
Parameter Setting

PARALLEL_AUTOMATIC_TUNING

Unset (defaults to FALSE).

SHARED_POOL_SIZE

Set to a large value, including the space required for parallel execution.

LARGE_POOL_SIZE

Unset (defaults to zero).

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:

Table A-2  Using PARALLEL_AUTOMATIC_TUNING
Parameter Setting

PARALLEL_AUTOMATIC_TUNING

Set to true.

SHARED_POOL_SIZE

Set to a small value that accounts for all clients except parallel execution.

LARGE_POOL_SIZE

Unset (defaults to a large value that includes the space required for parallel execution).

In this case, parallel execution allocates buffers from the large pool based on Oracle'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:

Table A-3  Using PARALLEL_AUTOMATIC_TUNING and Setting LARGE_POOL_SIZE
Parameter Setting

PARALLEL_AUTOMATIC_TUNING

Set to true.

SHARED_POOL_SIZE

Set to a small value that accounts for all clients except parallel execution.

LARGE_POOL_SIZE

Set to a value that includes the space required for parallel execution.

In this case, parallel execution allocates buffers from the large pool. After initial testing with LARGE_POOL_SIZE unset, 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:

Table A-4  Using PARALLEL_AUTOMATIC_TUNING without Modifying SHARED_POOL_SIZE
Parameter Setting

PARALLEL_AUTOMATIC_TUNING

Set to true.

SHARED_POOL_SIZE

Set to a large value, including the space required for parallel execution.

LARGE_POOL_SIZE

Unset (defaults to a large value that includes the space required for parallel execution).

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.

Archive Log Destination Parameters

Release 8.1 and higher supports new archive log destination parameters. After you upgrade, you can dynamically convert from the old pre-release 8.1 parameters (LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST) to the new release 8.1 and higher parameters (LOG_ARCHIVE_DEST_n and LOG_ARCHIVE_DEST_STATE_n). You can also dynamically revert to the old parameters.


Note:

In Oracle9i, the number of archive log destinations was increased from 5 to 10.


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 Corporation 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:

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

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:

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:

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 View Changes

The following sections list changes to static data dictionary views across different releases of Oracle:

Deprecated Static Data Dictionary Views

The following sections list static data dictionary views that have been deprecated:

Static Data Dictionary Views Deprecated in Release 9.2

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

Deprecated In Favor Of

ALL_RULESETS

ALL_RULE_SETS

DBA_RULESETS

DBA_RULE_SETS

USER_RULESETS

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:

Deprecated In Favor Of

ALL_REGISTERED_SNAPSHOTS

ALL_REGISTERED_MVIEWS

ALL_SNAPSHOT_LOGS

ALL_BASE_TABLE_MVIEWS

ALL_MVIEW_LOGS

ALL_SNAPSHOT_REFRESH_TIMES

ALL_MVIEW_REFRESH_TIMES

DBA_REGISTERED_SNAPSHOT_GROUPS

DBA_REGISTERED_MVIEW_GROUPS

DBA_REGISTERED_SNAPSHOTS

DBA_REGISTERED_MVIEWS

DBA_SNAPSHOT_LOG_FILTER_COLS

DBA_MVIEW_LOG_FILTER_COLS

DBA_SNAPSHOT_LOGS

DBA_BASE_TABLE_MVIEWS

DBA_MVIEW_LOGS

DBA_SNAPSHOT_REFRESH_TIMES

DBA_MVIEW_REFRESH_TIMES

USER_REGISTERED_SNAPSHOTS

USER_REGISTERED_MVIEWS

USER_SNAPSHOT_LOGS

USER_BASE_TABLE_MVIEWS

USER_MVIEW_LOGS

USER_SNAPSHOT_REFRESH_TIMES

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:

Deprecated In Favor Of

ALL_SNAPSHOTS

ALL_MVIEWS

ALL_SUMMARIES

ALL_MVIEW_ANALYSIS

ALL_SUMMARY_AGGREGATES

ALL_MVIEW_AGGREGATES

ALL_SUMMARY_DETAIL_TABLES

ALL_MVIEW_DETAIL_RELATIONS

ALL_SUMMARY_JOINS

ALL_MVIEW_JOINS

ALL_SUMMARY_KEYS

ALL_MVIEW_KEYS

DBA_SNAPSHOTS

DBA_MVIEWS

DBA_SUMMARIES

DBA_MVIEW_ANALYSIS

DBA_SUMMARY_AGGREGATES

DBA_MVIEW_AGGREGATES

DBA_SUMMARY_DETAIL_TABLES

DBA_MVIEW_DETAIL_RELATIONS

DBA_SUMMARY_JOINS

DBA_MVIEW_JOINS

DBA_SUMMARY_KEYS

DBA_MVIEW_KEYS

USER_SNAPSHOTS

USER_MVIEWS

USER_SUMMARIES

USER_MVIEW_ANALYSIS

USER_SUMMARY_AGGREGATES

USER_MVIEW_AGGREGATES

USER_SUMMARY_DETAIL_TABLES

USER_MVIEW_DETAIL_RELATIONS

USER_SUMMARY_JOINS

USER_MVIEW_JOINS

USER_SUMMARY_KEYS

USER_MVIEW_KEYS

Obsolete Static Data Dictionary Views

The following sections list static data dictionary views that have been made obsolete:

Static Data Dictionary Views Obsolete in Release 8.1

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

ALL_LABELS

Static Data Dictionary Views with Renamed Columns

The following sections list static data dictionary views with renamed columns:

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:

Table A-5  Static Data Dictionary Views with Renamed Columns in Release 9.0.1
Static Data Dictionary View Pre-Release 9.0.1 Column Name Release 9.0.1 and Higher Column Name

DBA_RSRC_PLAN_DIRECTIVES

MAX_ACTIVE_SESS_TARGET_P1

ACTIVE_SESS_POOL_P1

DBA_RSRC_PLANS

MAX_ACTIVE_SESS_TARGET_MTH

ACTIVE_SESS_POOL_MTH

Static Data Dictionary Views with Dropped Columns

The following sections list static data dictionary views with dropped columns:

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 View Dropped Columns

DBA_RSRC_PLAN_DIRECTIVES

MAX_ACTIVE_SESS_TARGET_P1

DBA_RSRC_PLANS

MAX_ACTIVE_SESS_TARGET_MTH

Static Data Dictionary Views with Dropped Columns in Release 8.1

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

Static Data Dictionary Views Dropped Columns

DBA_AUDIT_OBJECT

USER_AUDIT_OBJECT

OBJECT_LABEL

SESSION_LABEL

DBA_AUDIT_SESSION

USER_AUDIT_SESSION

SESSION_LABEL

DBA_AUDIT_STATEMENT

USER_AUDIT_STATEMENT

SESSION_LABEL

DBA_AUDIT_TRAIL

USER_AUDIT_TRAIL

OBJECT_LABEL

SESSION_LABEL

DBA_CONTEXT

ATTRIBUTE

ALL_IND_COLUMNS

DBA_IND_COLUMNS

USER_IND_COLUMNS

COLUMN_EXPRESSION

ALL_JOBS

DBA_JOBS

USER_JOBS

CLEARANCE_HI

CLEARANCE_LO

CURRENT_SESSION_LABEL

ALL_REFS

DBA_REFS

USER_REFS

HAS_REFERENTIAL_CONS

REFERENTIAL_CONS_NAME

Static Data Dictionary Views with Columns That May Return Nulls

Starting with release 8.1, the static data dictionary view columns listed in Table A-6 may return nulls; in previous releases, these columns could not return nulls. If an application requires non-null values for one or more of these columns, then modify the application accordingly:

Table A-6  Static Data Dictionary Views with Columns That May Return Nulls in Release 8.1
Static Data Dictionary Views Columns Explanation

DBA_DATA_FILES

AUTOEXTENSIBLE

BLOCKS

BYTES

INCREMENT_BY

MAXBLOCKS

MAXBYTES

These columns return a null if the data file is offline and therefore not readable.

ALL_IND_COLUMNS

DBA_IND_COLUMNS

USER_IND_COLUMNS

COLUMN_NAME

This column returns a null if an index is on a function instead of a column. In this case, there is no column to list.

ALL_IND_PARTITIONS

DBA_IND_PARTITIONS

USER_IND_PARTITIONS

INITIAL_EXTENT

MAX_EXTENT

MIN_EXTENT

NEXT_EXTENT

PCT_INCREASE

These columns return a null if the index is partitioned using a composite method and no default value was specified for the partition.

ALL_OBJECT_TABLES

DBA_OBJECT_TABLES

USER_OBJECT_TABLES

TABLESPACE_NAME

This column returns a null in if an object table is partitioned or if it is a temporary table.

ALL_SEGMENTS

DBA_SEGMENTS

USER_SEGMENTS

BLOCKS

BYTES

EXTENTS

NEXT_EXTENT

PCT_INCREASE

The BLOCKS, BYTES, and EXTENTS columns return a null if the segment header cannot be read because the file is offline or if there is some other corruption.

The NEXT_EXTENT and PCT_INCREASE columns return a null if the tablespace storing the segment is locally managed and uses the AUTOALLOCATE option, because the system chooses the extent sizes, and the algorithm cannot be explained in terms of NEXT_EXTENT and PCT_INCREASE.

ALL_TAB_PARTITIONS

DBA_TAB_PARTITIONS

USER_TAB_PARTITIONS

INITIAL_EXTENT

MAX_EXTENT

MIN_EXTENT

NEXT_EXTENT

PCT_INCREASE

These columns return a null if the table is partitioned using a composite method and no default value was specified for the partition.

ALL_TABLESPACES

DBA_TABLESPACES

USER_TABLESPACES

NEXT_EXTENT

PCT_INCREASE

These columns return a null if the tablespace is locally managed and uses the AUTOALLOCATE option, because the system chooses the extent sizes, and the algorithm cannot be explained in terms of NEXT_EXTENT and PCT_INCREASE.

ALL_TRIGGERS

DBA_TRIGGERS

USER_TRIGGERS

TABLE_NAME

This column returns a null if the trigger is a system trigger. In this case, the base object type of the trigger will be SCHEMA or DATABASE, instead of TABLE or VIEW.

Dynamic Performance View Changes

The following sections list changes to dynamic performance views (V$ views) across different releases of Oracle:

Deprecated Dynamic Performance Views

The following sections list dynamic performance views that have been deprecated:

Dynamic Performance Views Deprecated in Release 9.2

The following dynamic performance views were deprecated in release 9.2:

Deprecated In Favor Of

GV$SORT_USAGE

GV$TEMPSEG_USAGE

V$SORT_USAGE

V$TEMPSEG_USAGE

Dynamic Performance Views Deprecated in Release 9.0.1

The following dynamic performance views were deprecated in release 9.0.1:

Deprecated In Favor Of

GV$BSP

GV$CR_BLOCK_SERVER

GV$CLASS_PING

GV$CLASS_CACHE_TRANSFER

GV$DLM_ALL_LOCKS

GV$GES_ENQUEUE

GV$DLM_CONVERT_LOCAL

GV$GES_CONVERT_LOCAL

GV$DLM_CONVERT_REMOTE

GV$GES_CONVERT_REMOTE

GV$DLM_LATCH

GV$GES_LATCH

GV$DLM_LOCKS

GV$GES_BLOCKING_ENQUEUE

GV$DLM_MISC

GV$GES_STATISTICS

GV$DLM_RESS

GV$GES_RESOURCE

GV$DLM_TRAFFIC_CONTROLLER

GV$GES_TRAFFIC_CONTROLLER

GV$FILE_PING

GV$FILE_CACHE_TRANSFER

GV$LOCK_ELEMENT

GV$GC_ELEMENT

GV$LOCKS_WITH_COLLISIONS

GV$GC_ELEMENTS_WITH_COLLISIONS

GV$MAX_ACTIVE_SESS_TARGET_MTH

GV$ACTIVE_SESS_POOL_MTH

GV$MTS

GV$SHARED_SERVER_MONITOR

GV$PING

GV$CACHE_TRANSFER

GV$TEMP_PING

GV$TEMP_CACHE_TRANSFER

V$BSP

V$CR_BLOCK_SERVER

V$CLASS_PING

V$CLASS_CACHE_TRANSFER

V$DLM_ALL_LOCKS

V$GES_ENQUEUE

V$DLM_CONVERT_LOCAL

V$GES_CONVERT_LOCAL

V$DLM_CONVERT_REMOTE

V$GES_CONVERT_REMOTE

V$DLM_LATCH

V$GES_LATCH

V$DLM_LOCKS

V$GES_BLOCKING_ENQUEUE

V$DLM_MISC

V$GES_STATISTICS

V$DLM_RESS

V$GES_RESOURCE

V$DLM_TRAFFIC_CONTROLLER

V$GES_TRAFFIC_CONTROLLER

V$FILE_PING

V$FILE_CACHE_TRANSFER

V$LOCK_ELEMENT

V$GC_ELEMENT

V$LOCKS_WITH_COLLISIONS

V$GC_ELEMENTS_WITH_COLLISIONS

V$MAX_ACTIVE_SESS_TARGET_MTH

V$ACTIVE_SESS_POOL_MTH

V$MTS

V$SHARED_SERVER_MONITOR

V$PING

V$CACHE_TRANSFER

V$TEMP_PING

V$TEMP_CACHE_TRANSFER

Obsolete Dynamic Performance Views

The following sections list dynamic performance views that have been made obsolete:

Dynamic Performance Views Obsolete in Release 9.2

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

GV$LOADCSTAT

V$LOADCSTAT

GV$LOADTSTAT

V$LOADTSTAT

Dynamic Performance Views Obsolete in Release 9.0.1

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

GV$TARGETRBA

V$TARGETRBA

Dynamic Performance Views Obsolete in Release 8.1

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

GV$CURRENT_BUCKET

V$CURRENT_BUCKET

GV$RECENT_BUCKET

V$RECENT_BUCKET

Dynamic Performance Views with Renamed Columns

The following sections list dynamic performance views with renamed columns:

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:

Table A-7  Dynamic Performance Views with Renamed Columns in Release 9.2
Dynamic Performance View Pre-Release 9.2 Column Name Release 9.2 and Higher Column Name

GV$ARCHIVE_DEST and V$ARCHIVE_DEST

MANIFEST

REGISTER

REGISTER

REMOTE_TEMPLATE

GV$DATABASE and V$DATABASE

STANDBY_MODE

PROTECTION_MODE

GV$LOGMNR_CALLBACK and V$LOGMNR_CALLBACK

CALLBACK_STATE

STATE

CALLBACK_TYPE

TYPE

CALLBACK_CAPABILITY

CAPABILITY

GV$LOGMNR_REGION and V$LOGMNR_REGION

ID

MEMSTATE

CURRENT_STATE

STATE

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:

Table A-8  Dynamic Performance Views with Renamed Columns in Release 9.0.1
Dynamic Performance View Pre-Release 9.0.1 Column Name Release 9.0.1 and Higher Column Name

GV$RSRC_CONSUMER_GROUP and V$RSRC_CONSUMER_GROUP

SESSIONS_QUEUED

QUEUE_LENGTH

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:

Table A-9  Dynamic Performance Views with Renamed Columns in Release 8.1
Dynamic Performance View Pre-Release 8.1 Column Name Release 8.1 and Higher Column Name

GV$DISPATCHER_RATE and V$DISPATCHER_RATE

NUM_LOOPS_TRACKED

TTL_LOOPS

NUM_MSG_TRACKED

TTL_MSG

NUM_SVR_BUF_TRACKED

TTL_SVR_BUF

NUM_CLT_BUF_TRACKED

TTL_CLT_BUF

NUM_BUF_TRACKED

TTL_BUF

NUM_IN_CONNECT_TRACKED

TTL_IN_CONNECT

NUM_OUT_CONNECT_TRACKED

TTL_OUT_CONNECT

NUM_RECONNECT_TRACKED

TTL_RECONNECT

Dynamic Performance Views with Dropped Columns

The following sections list dynamic performance views with dropped columns. If an application requires one or more of these columns, then modify the application accordingly:

Dynamic Performance Views with Dropped Columns in Release 9.2

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

Dynamic Performance View Dropped Columns

GV$DATABASE and V$DATABASE

STANDBY_MODE

GV$LOGMNR_CALLBACK and V$LOGMNR_CALLBACK

FUNC_NAME

CALLBACK_ID

CALLBACK_RESULT_SIZE

CALLBACK_STATE

CALLBACK_TYPE

CALLBACK_CAPABILITY

NUMBER_INVOKED

GV$LOGMNR_REGION and V$LOGMNR_REGION

ID

CURRENT_STATE

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 View Dropped Columns

GV$LOGMNR_CONTENTS and V$LOGMNR_CONTENTS

PH1_NAME

PH1_REDO

PH1_UNDO

PH2_NAME

PH2_REDO

PH2_UNDO

PH3_NAME

PH3_REDO

PH3_UNDO

PH4_NAME

PH4_REDO

PH4_UNDO

PH5_NAME

PH5_REDO

PH5_UNDO

GV$RSRC_CONSUMER_GROUP and V$RSRC_CONSUMER_GROUP

SESSIONS_QUEUED

Dynamic Performance Views with Dropped Columns in Release 8.1

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

Dynamic Performance View Dropped Columns

V$ARCHIVE_DEST

ARCMODE

V$DLM_LATCH

IMM_GETS

LATCH_TYPE

TTL_GETS

V$DLM_LOCKS

RESOURCE_NAME

V$SESSION_LONGOPS

APPLICATION_DATA_1

APPLICATION_DATA_2

APPLICATION_DATA_3

COMPNAM

CURRENT_TIME

MSG

OBJID

OPID

STEPID

STEPSOFAR

STEPTOTAL

UPDATE_COUNT