Remote_dependencies_mode:
Description: The process processing that the database is dependent on the object is depends on the process. If set to TimeStamp,
This process can only be performed only if the server matches the local timestamp. If set to Signature,
This process can be performed in the case of signing security.
Value range: TimeStamp | Signature
Default: TimeStamp
Shared_Memory_Address:
Description: Shared_memory_address and hi_shared_memory_address specified runtime SGA
The start address. Many platforms specify the SGA start address in the link time, which will be ignored on such platforms. If both parameters are set to 0 or
NULL, then the address will depend on the platform.
Value range: Any integer value.
Default: 0
LOCK_SGA:
Description: Used to lock the entire SGA in physical memory. This value will be ignored on a platform that does not support this function.
Value range: True | False
Default: False
Hi_Shared_Memory_Address:
Description: Specifies the runtime starting address of the system global zone (SGA). This value is ignored on the platform of the start address when specifying the SGA connection. On the 64-bit platform,
Use this value to specify a high 32-bit and low 32 bits. If this value is not specified, the default value is the location specified in the platform.
Value range: Any integer value.
Default: 0
PRE_PAGE_SGA:
Description: A parameter according to the platform, if this parameter is true, all SGA pages will be loaded into memory,
In order to make this routine quickly reach the best performance. This will increase the time of routine startup and user login, but can reduce the occurrence of the fault failure on the system of sufficient memory.
Value range: True | False
Default: False
SGA_MAX_SIZE:
Description: The maximum size of the system's global zone occupied by the specified routine survival.
Value range: 0 to the maximum allowed by each operating system. Please note that because the minimum value of the parameter value has been adjusted at startup, it has nothing to do.
Default: If the value is not specified, the default value of SGA_MAX_SIZE will be the same as the initial size (such as X) of the SGA at startup. This size depends on the size of various pools in the SGA, such as buffer cache, sharing pool, large pool, etc. If the specified value is less than X, the value of the SGA_MAX_SIZE used will be X. That is, it is a larger value between the X and the user specified by the user.
Fast_start_parallel_rollback:
Description: Perform the maximum number of processes for performing parallel return. This value is useful on the system where most transaction processing is running.
Value Range: False | Low | HIGH
Default: Low (2 * CPU_COUNT)
Transaction_auditing:
Description: Determine whether the transaction layer generates a special redo record, which contains the user's login name, user name, session ID,
Some operating system information and client information. These records may be useful when using a redo log analysis tool.
Value range: True | False
Default: True
TRANSACTIONS:
Description: Specifies the maximum number of parallel transactions. If this value is set, it will increase the size of the SGA.
And can increase the number of retort segments allocated during the routine startup. The default is greater than Sessions to implement recursive transaction processing.
Value range: a value.
Default: Delivery (1.1 * sessions)
Enqueue_Resources:
Note: The team enables the parallel process to share resources. For example, Oracle allows a process to lock a table in sharing mode to lock another table in sharing update mode.
Value range: 10 - 65535 (7.3) or 10 - no limit (8.1).
Default: derived (this value is greater than DML_LOCKS 20 is enough)
DML_LOCKS:
Note: The maximum number of table locks acquired by all users. One DML lock is required for performing DML operations for each table. For example, if three users modify 2 tables,
This value is required to be 6.
Value range: 0 or 20 to unlimited. Default: 4 * Transactions (derived)
Hash_join_ENABED:
Note: If set to TRUE, the optimizer will consider the hash linkage when calculating the most efficient join method. Oracle recommends that data warehouse applications should use True
value.
Value range: True | False
Default: True
Optimizer_features_enable:
Description: Allow changes to the init.ora parameter, which controls the behavior of the optimizer. Parameters affected by this include push_join_predicate,
FAST_FULL_SCAN_ENABED, Complex_View_merge and
B_tree_bitmap_plans.
Value range: 8.0.0; 8.0.3; 8.0.4; 8.1.3.
Default: 8.0.0
Query_rewrite_integrity:
Description: The degree of query override executed by Oracle Server. If set to Enforces, Oracle
It will ensure its consistency and integrity. If you are set to trusted, you will use a clear declaration to allow rewrite. If set to
Stale_Tolerated, even if the physicalized view is inconsistent with the base data, it can still be overwritten.
Value range: Enforced, Trusted, Stale_Tolerate
Default: enforces
Query_rewrite_enabled
Description: Enable or disable the query override to the physicalized view. A specific physicalized view is only enabled under the following conditions: session parameters and individual solidized views are enabled.
And based on cost optimization is enabled.
Value range: True | False
Default: False
