Release 1 (9.0.1)
Part Number A90191-02
 Home |
 Book List |
 Contents |
 Index |  Master Index |  Feedback |
| Oracle9i Database Migration Release 1 (9.0.1) Part Number A90191-02 |
|
Oracle9i supports new initialization parameters for use in the initialization parameter file, and some initialization parameters have been renamed or have become obsolete in Oracle9i. Typically, the initialization parameter file is named initsid.ora, where sid is your database instance name. However, the initialization parameter file may be named differently in your environment. This appendix lists the new, renamed, and obsolete initialization parameters in version 8 and Oracle9i, and this appendix discusses compatibility issues with certain initialization parameters.
This appendix covers the following topics:
Oracle9i Database Reference for detailed information about the initialization parameters in Oracle9i.
See Also:
The following sections list the new, renamed, and obsolete initialization parameters in Oracle9i:
The initialization parameters listed in this section are new in Oracle9i.
The following initialization parameters were added in release 9.0.1:
The initialization parameters listed in this section have been renamed in Oracle9i.
The following initialization parameters were renamed in release 9.0.1:
| Pre-Release 9.0.1 Name | Release 9.0.1 Name |
|---|---|
|
|
|
|
|
|
|
|
|
The initialization parameters listed in this section are obsolete in Oracle9i.
The following initialization parameters became obsolete in release 9.0.1 and cannot be used in release 9.0.1 and higher:
The following sections list the new, renamed, and obsolete initialization parameters in version 8:
The initialization parameters listed in this section are new in version 8.
The following initialization parameters were added in release 8.0:
The following initialization parameters were added in release 8.1:
The initialization parameters listed in this section have been renamed in version 8.
The following initialization parameters were renamed in release 8.0:
* The units are different for CCF_IO_SIZE (bytes) and DB_FILE_DIRECT_IO_COUNT (database blocks).
The initialization parameters listed in this section are obsolete in version 8.
The following initialization parameters became obsolete in release 8.0 and cannot be used in release 8.0 and higher:
The following initialization parameters became obsolete in release 8.1 and cannot be used in release 8.1 and higher:
The lists of new, changed, and obsolete initialization parameters earlier in this appendix show differences in 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.
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.
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 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:
ORACLE_TRACE_COLLECTION_NAME server 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.
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, 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 in release 8.1 if either of the following conditions were true in a past release:
SORT_DIRECT_WRITES was set to FALSE.
SORT_DIRECT_WRITES was set to AUTO, and SORT_AREA_SIZE was set to 640 KB or less.
If either of these conditions were true in a past release, then increase the value of SORT_AREA_SIZE for better performance.
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 the Oracle9i Database Reference for more information.
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.
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.
Starting with release 8.1, if the DB_DOMAIN initialization parameter is unset, 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. Before you migrate or upgrade to release 8.1 or higher, 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 migrate or upgrade to release 8.1 or higher.
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 migrate or upgrade to release 8.1 or higher.
Starting with release 8.1, parallel execution message buffers are allocated from the large pool whenever PARALLEL_AUTOMATIC_TUNING is set to true. In past releases, this allocation was from the shared pool. If you are migrating or upgrading to release 8.1 or higher 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 unset.
The calculation is based on the settings of the following initialization parameters:
PARALLEL_MAX_SERVERS
PARALLEL_THREADS_PER_CPU
PARALLEL_SERVER_INSTANCES
MTS_DISPATCHERS
DBWR_IO_SLAVES
If PARALLEL_AUTOMATIC_TUNING is unset or set to FALSE, and if LARGE_POOL_SIZE is unset, then the value of LARGE_POOL_SIZE defaults to zero.
|
See Also:
Oracle9i Database Reference and Oracle9i Database Performance Guide and Reference for more information about other effects of the |
The following scenarios illustrate the behavior that results from various initialization parameter settings when you migrate or upgrade to release 8.1 or higher.
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.
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 Oracle's automatic calculation. Buffer allocation is more efficient, and failures to allocate are isolated from the clients of the shared pool.
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 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.
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.
Release 8.1 and higher supports new archive log destination parameters. After you migrate or upgrade to release 8.1 or higher, 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.
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:
ALTER SYSTEM to set LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.
ALTER SYSTEM to set LOG_ARCHIVE_DUPLEX_DEST to NULL.
ALTER SYSTEM to set LOG_ARCHIVE_DEST to NULL.
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.
ALTER SYSTEM to set at least one LOG_ARCHIVE_DEST_n parameter to a value specifying a local destination.
ALTER SYSTEM to set other LOG_ARCHIVE_DEST_n parameters as required.
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;
Complete the following steps to change back to the old archive log destination parameters:
ALTER SYSTEM to set LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.
ALTER SYSTEM to set all LOG_ARCHIVE_DEST_n parameters to NULL.
ALTER SYSTEM to set the LOG_ARCHIVE_DEST parameter to a value specifying a local destination.
ALTER SYSTEM to set the LOG_ARCHIVE_DUPLEX_DEST parameter as required.
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;
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.
|
 Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|