| Oracle® Database Upgrade Guide 10g Release 2 (10.2) Part Number B14238-01 |
|
|
View PDF |
| Oracle® Database Upgrade Guide 10g Release 2 (10.2) Part Number B14238-01 |
|
|
View PDF |
This appendix lists changes to initialization parameters and the data dictionary across different releases of the Oracle Database. This appendix also discusses compatibility issues with certain initialization parameters.
This appendix covers the following topics:
Note:
Some of the initialization parameters listed in this appendix are operating system-specific. See your operating system-specific Oracle documentation for more information about these initialization parameters.The following sections list changes to initialization parameters across different releases of the Oracle Database:
See Also:
The "What's New in Oracle Database Reference" section of Oracle Database Reference for a list of new initialization parameters in Oracle Database 10gThe following sections list initialization parameters that have been deprecated. To get a list of all deprecated initialization parameters, issue the following SQL statement:
SQL> SELECT name FROM v$parameter
WHERE isdeprecated = 'TRUE';
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 the parameter file. In addition, all deprecated parameters are logged to the alert log at instance startup:
The following initialization parameters were deprecated in release 10.2:
LOGMNR_MAX_PERSISTENT_SESSIONSMAX_COMMIT_PROPAGATION_DELAYREMOTE_ARCHIVE_ENABLESERIAL_REUSESQL_TRACEThe 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_SIZELOCK_NAME_SPACELOG_ARCHIVE_STARTMAX_ENABLED_ROLESPARALLEL_AUTOMATIC_TUNINGPLSQL_COMPILER_FLAGS (replaced by PLSQL_CODE_TYPE and PLSQL_DEBUG)The following initialization parameters were deprecated in release 9.2:
DRS_START (replaced by DG_BROKER_START)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)The following sections list initialization parameters that have been made obsolete:
Note:
An attempt to start a release 10.1 database using one or more of these obsolete initialization parameters will succeed, but a warning will be returned and recorded in the alert log.The following initialization parameters were made obsolete in release 10.1:
DBLINK_ENCRYPT_LOGINHASH_JOIN_ENABLEDLOG_PARALLELISMMAX_ROLLBACK_SEGMENTSMTS_CIRCUITSMTS_DISPATCHERSMTS_LISTENER_ADDRESSMTS_MAX_DISPATCHERSMTS_MAX_SERVERSMTS_MULTIPLE_LISTENERSMTS_SERVERSMTS_SERVICEMTS_SESSIONSOPTIMIZER_MAX_PERMUTATIONSORACLE_TRACE_COLLECTION_NAMEORACLE_TRACE_COLLECTION_PATHORACLE_TRACE_COLLECTION_SIZEORACLE_TRACE_ENABLEORACLE_TRACE_FACILITY_NAMEORACLE_TRACE_FACILITY_PATHPARTITION_VIEW_ENABLEDPLSQL_NATIVE_C_COMPILERPLSQL_NATIVE_LINKERPLSQL_NATIVE_MAKE_FILE_NAMEPLSQL_NATIVE_MAKE_UTILITYROW_LOCKINGSERIALIZABLETRANSACTION_AUDITINGUNDO_SUPPRESS_ERRORSThe following initialization parameters were made obsolete in release 9.2:
DISTRIBUTED_TRANSACTIONSMAX_TRANSACTION_BRANCHESPARALLEL_BROADCAST_ENABLEDSTANDBY_PRESERVES_NAMESThe following initialization parameters were made obsolete in release 9.0.1:
ALWAYS_ANTI_JOINALWAYS_SEMI_JOINDB_BLOCK_LRU_LATCHESDB_BLOCK_MAX_DIRTY_TARGETDB_FILE_DIRECT_IO_COUNTGC_DEFER_TIMEGC_RELEASABLE_LOCKSGC_ROLLBACK_LOCKSHASH_MULTIBLOCK_IO_COUNTINSTANCE_NODESETJOB_QUEUE_INTERVALOPS_INTERCONNECTSOPTIMIZER_PERCENT_PARALLELSORT_MULTIBLOCK_READ_COUNTTEXT_ENABLEThe lists of deprecated and obsolete initialization parameters earlier in this appendix show changes to initialization parameters across different releases of the Oracle Database. 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.
In previous Oracle Database releases, the number of SQL cursors cached by PL/SQL was determined by the OPEN_CURSORS initialization parameter. Starting with Oracle Database 10g release 10.1, the number of cached cursors is determined by the SESSION_CACHED_CURSORS initialization parameter.
In Oracle Database 10g, 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 to the new Oracle Database 10g release, then you will receive an error when attempting to start up your Oracle Database. Add the following to your parameter file:
DB_BLOCK_SIZE = 2048
If DB_BLOCK_SIZE is specified in the parameter file, then the Oracle Database will use this value instead of the default value of 8 KB.
Starting with Oracle Database 10g, the OPTIMIZER_MAX_PERMUTATIONS initialization parameter has been made obsolete. If you are upgrading from Oracle9i and have OPTIMIZER_FEATURES_ENABLE set to 8.1.7 or lower and OPTIMIZER_MAX_PERMUTATIONS explicitly set to 2000 in the parameter file, then the release 8.1.7 default of 80000 will be used when you start up the release 10.1 database.
Setting OPTIMIZER_FEATURES_ENABLE to 9.0.0 or higher will set the default to 2000.
Starting with Oracle Database 10g release 10.1, if the COMPATIBLE initialization parameter is set to 10.0.0 or higher, then archive log file names must contain each of the elements %s (sequence), %t (thread), and %r (resetlogs ID) to ensure that all archive log file names are unique. If the LOG_ARCHIVE_FORMAT initialization parameter is set in the parameter file, then make sure the parameter value contains the %s, %t, and %r elements.
Starting with Oracle Database 10g release 10.1, Automatic PGA Memory Management is now enabled by default (unless PGA_AGGREGATE_TARGET is explicitly set to 0 or WORKAREA_SIZE_POLICY is explicitly set to MANUAL). PGA_AGGREGATE_TARGET defaults to 20% of the size of the SGA, unless explicitly set. Oracle recommends tuning the value of PGA_AGGREGATE_TARGET after upgrading.
See Also:
Oracle Database Performance Tuning GuideIn previous releases, the amount of shared pool memory that was allocated was equal to the value of the SHARED_POOL_SIZE initialization parameter plus the amount of internal SGA overhead computed during instance startup. Starting with Oracle Database 10g release 10.1, the value of SHARED_POOL_SIZE must now also accommodate this shared pool overhead.
Starting with Oracle Database 10g release 10.1, the recommended way to turn on shared server mode is to set SHARED_SERVERS to a value greater than 0. This can be done at startup or dynamically after the instance is started. If shared server mode is turned off by setting SHARED_SERVERS to 0, then this only affects new clients (that is, no new clients can connect in shared mode; clients that are already connected in shared mode continue to be serviced by shared servers).
In previous releases, the recommended way to turn on shared server mode was to set DISPATCHERS. If SHARED_SERVERS was changed to 0 and shared server clients were still connected, client requests would hang.
Prior to release 10.1, the following shared server parameters could not be changed dynamically:
MAX_SHARED_SERVERS
MAX_DISPATCHERS
SHARED_SERVER_SESSIONS
CIRCUITS
Starting with release 10.1, these shared server parameters are dynamically modifiable.
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.
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.
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.
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.
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.
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.
Starting with Oracle9i 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 Oracle9i release 9.0.1 and higher, the default value is true.
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.
Starting with Oracle8i 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 Oracle8i release 8.1.5 and higher, the default value is 1800 seconds.
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 Oracle9i release 9.0.1, the default value of this initialization parameter is false.
The following sections list changes to static data dictionary views across different releases of the Oracle Database:
See Also:
The "What's New in Oracle Database Reference" section of Oracle Database Reference for a list of new static data dictionary views in Oracle Database 10gThe following sections list static data dictionary views that have been deprecated:
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)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)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)The following sections list static data dictionary views that have been made obsolete:
The following sections list static data dictionary views with renamed columns:
The static data dictionary view columns listed in Table A-1 were renamed in release 9.0.1:
Table A-1 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 |
The following sections list static data dictionary views with dropped columns:
Static Data Dictionary Views with Dropped Columns in Release 10.2
Static Data Dictionary Views with Dropped Columns in Release 9.0.1
The following static data dictionary view columns were dropped in release 10.2:
| Static Data Dictionary View | Dropped Columns |
|---|---|
DBA_HIST_SQLBIND |
CHILD_NUMBER |
The following sections list changes to dynamic performance views (V$ views) across different releases of the Oracle Database:
See Also:
The "What's New in Oracle Database Reference" section of Oracle Database Reference for a list of new dynamic performance views in Oracle Database 10gThe following sections list dynamic performance views that have been deprecated:
The following dynamic performance views were deprecated in release 10.1:
GV$CACHEGV$CACHE_TRANSFERGV$CLASS_CACHE_TRANSFER (replaced by GV$INSTANCE_CACHE_TRANSFER)GV$FALSE_PINGGV$FILE_CACHE_TRANSFER (replaced by GV$INSTANCE_CACHE_TRANSFER)GV$GC_ELEMENTS_WITH_COLLISIONSGV$LOCK_ACTIVITYGV$TEMP_CACHE_TRANSFER (replaced by GV$INSTANCE_CACHE_TRANSFER)V$CACHEV$CACHE_LOCKV$CACHE_TRANSFERV$CLASS_CACHE_TRANSFER (replaced by V$INSTANCE_CACHE_TRANSFER)V$FALSE_PINGV$FILE_CACHE_TRANSFER (replaced by V$INSTANCE_CACHE_TRANSFER)V$GC_ELEMENTS_WITH_COLLISIONSV$LOCK_ACTIVITYV$TEMP_CACHE_TRANSFER (replaced by V$INSTANCE_CACHE_TRANSFER)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)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)The following sections list dynamic performance views that have been made obsolete:
The following dynamic performance views were made obsolete in release 10.1:
| GV$ Views | V$ Views |
|---|---|
GV$COMPATIBILITY |
V$COMPATIBILITY |
GV$COMPATSEG |
V$COMPATSEG |
GV$MLS_PARAMETERS |
V$MLS_PARAMETERS |
GV$MTS |
V$MTS |
The following dynamic performance views were made obsolete in release 9.2:
| GV$ Views | V$ Views |
|---|---|
GV$LOADCSTAT |
V$LOADCSTAT |
GV$LOADTSTAT |
V$LOADTSTAT |
The following sections list dynamic performance views with renamed columns:
Dynamic Performance Views with Renamed Columns in Release 9.2
Dynamic Performance Views with Renamed Columns in Release 9.0.1
The dynamic performance view columns listed in Table A-2 were renamed in release 9.2:
Table A-2 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 |
GV$ARCHIVE_DEST and V$ARCHIVE_DEST |
REGISTER |
REMOTE_TEMPLATE |
GV$DATABASE and V$DATABASE |
STANDBY_MODE |
PROTECTION_MODE |
GV$LOGMNR_CALLBACK and V$LOGMNR_CALLBACK |
CALLBACK_STATE |
STATE |
GV$LOGMNR_CALLBACK and V$LOGMNR_CALLBACK |
CALLBACK_TYPE |
TYPE |
GV$LOGMNR_CALLBACK and V$LOGMNR_CALLBACK |
CALLBACK_CAPABILITY |
CAPABILITY |
GV$LOGMNR_REGION and V$LOGMNR_REGION |
ID |
MEMSTATE |
GV$LOGMNR_REGION and V$LOGMNR_REGION |
CURRENT_STATE |
STATE |
The dynamic performance view columns listed in Table A-3 were renamed in release 9.0.1:
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
Dynamic Performance Views with Dropped Columns in Release 9.0.1
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
|
GV$LOGMNR_REGION and V$LOGMNR_REGION |
ID
|
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
|
GV$RSRC_CONSUMER_GROUP and V$RSRC_CONSUMER_GROUP |
SESSIONS_QUEUED |
