Transactions_Per_rollback_segment:
Note: Specifies the number of parallel transactions allowed by each retreat section. The minimum number of returned segments for startup is Transactions
Remove the result of this parameter value. If you are named after the parameter rollback_segments, you can get these checkback segments.
Value range: 1 - Depending on the operating system.
Default: 5
Undo_management:
Note: Which revoked space management mode should be specified in the specified system. If set to Auto, the routine will start in SMU mode. Otherwise it will be started in RBU mode. in
In the RBU mode, the undo space will be allocated outside the restented segment. Under SMU mode, the revoked space will be allocated externally like withdrawal tables.
Value range: auto or manual
Default: If the undo_management parameter is ignored when the first routine is started, the default value Manual will be used, and the routines will be started in the RBU mode. If this is not the first routine, you will start the routine when the undo mode is used in other existing routines.
Undo_tablespace:
Note: The withdrawal table space is only used to store undo information. Undo_Tablespace only allows for system management to undo (SMU)
Use in mode. The routine will use the specified undo tablespace,
Or is used by another routine, the routine Startup will fail.
Default: Each database contains 0 or more withdrawal tables. In SMU mode, you will allocate one (and only one) withdrawal table space for each Oracle routine.
INSTANCE_NAME
Note: In the case where multiple routines use the same service name, it is used to uniquely identify a database routine. Instance_name should not be confused with SID,
It is actually a unique identifier for each routine that shares memory on a host.
Value range: any alphanumeric characters.
Default: Database SID
Service_names:
Description: Use the Oracle NET listener to identify a service (such as a specific database in the replication environment)
The routine specifies the service name. If the service does not have a domain, the db_domain parameter will be attached.
Syntax: service_names = name1.domain, name2.domain
Default: db_name.db_domain (if defined)
Local_Listener:
Description: A list of Oracle NET addresses for identifying Oracle Net
The database routine on the same computer is located. All routines and schedule are registered on this listener to enable client connections. This parameter is covered
The discarded mts_listener_address and mts_multiple_listeners parameters are discarded in version 8.1.
Value range: A list of valid Oracle NET addresses.
Default: (address_list = (pecol = tcp) (host = localhost) (address = (protocol = IPC))))
License_SESSIONS_WARNING:
Note: Specifies a warning limit on the number of parallel user sessions. Once this limit is reached, other users can still connect, but a message will be written to the Alert file. have
Users of Restricted session permissions will receive a warning message indicating that the system is close to the maximum capacity.
Value range: 0 - license_max_sessions
Default: 0
License_max_ssions:
Note: Specifies the maximum number of parallel user sessions that allow simultaneous permit. After the limit is reached, only RESTRICTED SESSION
Users of permissions can connect to the server. All other users receive a warning message indicating that the maximum capacity of the system has reached.
Value range: 0 - The number of session licenses.
Default: 0
License_max_users:
Description:
Specify the maximum number of users you can create in this database. Parallel sessions licenses and user licenses should not be enabled simultaneously. License_max_iesions or license_max_users or the value of both should be zero.
Value range: 0 - The number of user licensions.
Default: 0
DB_BLOCK_CHECKSUM:
Note: DBWN, ARCH, and SQL * Loader are read or write to each data block or write the checksum of the check block.
Value range: True | False
Default: False
Shadow_core_dump:
Description: A parameter for UNIX uses to specify whether to dump SGA information into a generated core file. If set to FULL, SGA
Will be included in the core dump. If set to Partial, SGA will not be documented.
Value range: Full | Partial
Default: full
DB_BLOCK_CHECKING:
Description: The block used to control whether the block is checked for transaction management is damaged.
Value range: True | False
Default: False
Background_core_dump:
Note: Do SGA information into a generated core file (for UNIX).
Value range: Full | Partial
Default: full
Event:
Note: Use Oracle Technical Support Personnel to debug the system. In general, the value should not be changed.
Value range: Not available.
Default: None
