SYSTEM statement to dynamically alter your Oracle database instance. The settings stay in effect as long as the database is mounted.
(archive_log_clause ::=, checkpoint_clause::=, check_datafiles_clause::=, distributed_recov_clauses::=, end_session_clauses::=, quiesce_clauses::=, rolling_migration_clauses::=, alter_system_security_clauses::=, shutdown_dispatcher_clause::=, alter_system_set_clause::=, alter_system_reset_clause::=)
archive_log_clause manually archives redo log files or enables or disables automatic archiving. To use this clause, your instance must have the database mounted. The database can be either open or closed unless otherwise noted.
This clause is relevant only if you are using Oracle Real Application Clusters (RAC). Specify the name of the instance for which you want the redo log file group to be archived. The instance name is a string of up to 80 characters. Oracle Database automatically determines the thread that is mapped to the specified instance and archives the corresponding redo log file group. If no thread is mapped to the specified instance, then Oracle Database returns an error.
SEQUENCE to manually archive the online redo log file group identified by the log sequence number
integer in the specified thread. If you omit the
THREAD parameter, then Oracle Database archives the specified group from the thread assigned to your instance.
CHANGE to manually archive the online redo log file group containing the redo log entry with the system change number (SCN) specified by
integer in the specified thread. If the SCN is in the current redo log file group, then Oracle Database performs a log switch. If you omit the
THREAD parameter, then Oracle Database archives the groups containing this SCN from all enabled threads.
You can use this clause only when your instance has the database open.
CURRENT to manually archive the current redo log file group of the specified thread, forcing a log switch. If you omit the
THREAD parameter, then Oracle Database archives all redo log file groups from all enabled threads, including logs previous to current logs. You can specify
CURRENT only when the database is open.
NOSWITCH if you want to manually archive the current redo log file group without forcing a log switch. This setting is used primarily with standby databases to prevent data divergence when the primary database shuts down. Divergence implies the possibility of data loss in case of primary database failure.
You can use the
NOSWITCH clause only when your instance has the database mounted but not open. If the database is open, then this operation closes the database automatically. You must then manually shut down the database before you can reopen it.
GROUP to manually archive the online redo log file group with the
GROUP value specified by
integer. You can determine the
GROUP value for a redo log file group by querying the data dictionary view
DBA_LOG_GROUPS. If you specify both the
GROUP parameters, then the specified redo log file group must be in the specified thread.
LOGFILE to manually archive the online redo log file group containing the redo log file member identified by '
filename'. If you specify both the
LOGFILE parameters, then the specified redo log file group must be in the specified thread.
If the database was mounted with a backup control file, then specify
CONTROLFILE to permit archiving of all online logfiles, including the current logfile.
Restriction on the LOGFILE clause You must archive redo log file groups in the order in which they are filled. If you specify a redo log file group for archiving with the
LOGFILE parameter, and earlier redo log file groups are not yet archived, then Oracle Database returns an error.
NEXT to manually archive the next online redo log file group from the specified thread that is full but has not yet been archived. If you omit the
THREAD parameter, then Oracle Database archives the earliest unarchived redo log file group from any enabled thread.
ALL to manually archive all online redo log file groups from the specified thread that are full but have not been archived. If you omit the
THREAD parameter, then Oracle Database archives all full unarchived redo log file groups from all enabled threads.
In earlier releases, this clause enabled automatic archiving of redo log file groups for the thread assigned to your instance. This clause has been deprecated, because Oracle Database automatically enables automatic archiving of redo log file groups. This clause has no effect. If you specify it, then Oracle Database writes a message to the alert log.
location' to indicate the primary location to which the redo log file groups are archived. The value of this parameter must be a fully specified file location following the conventions of your operating system. If you omit this parameter, then Oracle Database archives the redo log file group to the location specified by the initialization parameters
In earlier releases, this clause disabled automatic archiving of redo log file groups for the thread assigned to your instance. This clause has been deprecated. It has no effect, and if you specify it, Oracle Database writes a message to the alert log.
CHECKPOINT to explicitly force Oracle Database to perform a checkpoint, ensuring that all changes made by committed transactions are written to datafiles on disk. You can specify this clause only when your instance has the database open. Oracle Database does not return control to you until the checkpoint is complete.
See Also:"Forcing a Checkpoint: Example"
In a distributed database system, such as an Oracle RAC environment, this clause updates an instance's SGA from the database control file to reflect information on all online datafiles.
GLOBAL to perform this synchronization for all instances that have opened the database. This is the default.
LOCAL to perform this synchronization only for the local instance.
Your instance should have the database open.
end_session_clauses give you several ways to end the current session.
SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever). To use this clause, your instance must have the database open. You must identify the session with both of the following values from the
integer1, specify the value of the
integer2, specify the value of the
If system parameters are appropriately configured, then application failover will take effect.
POST_TRANSACTION setting allows ongoing transactions to complete before the session is disconnected. If the session has no ongoing transactions, then this clause has the same effect described for as
IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
If you also specify
POST_TRANSACTION and the session has ongoing transactions, then the
IMMEDIATE keyword is ignored.
If you do not specify
POST_TRANSACTION, or you specify
POST_TRANSACTION but the session has no ongoing transactions, then this clause has the same effect as described for
See Also:"Disconnecting a Session: Example"
SESSION clause lets you mark a session as terminated, roll back ongoing transactions, release all session locks, and partially recover session resources. To use this clause, your instance must have the database open. Your session and the session to be terminated must be on the same instance unless you specify
integer3.You must identify the session with the following values from the
integer1, specify the value of the
integer2, specify the value of the
For the optional
integer3, specify the ID of the instance where the target session to be killed exists. You can find the instance ID by querying the GV$ tables.
If the session is performing some activity that must be completed, such as waiting for a reply from a remote database or rolling back a transaction, then Oracle Database waits for this activity to complete, marks the session as terminated, and then returns control to you. If the waiting lasts a minute, then Oracle Database marks the session to be terminated and returns control to you with a message that the session is marked to be terminated. The
PMON background process then marks the session as terminated when the activity is complete.
Whether or not the session has an ongoing transaction, Oracle Database does not recover the entire session state until the session user issues a request to the session and receives a message that the session has been terminated.
See Also:"Terminating a Session: Example"
RECOVERY clause lets you enable or disable distributed recovery. To use this clause, your instance must have the database open.
You may need to issue the
RECOVERY statement more than once to recover an in-doubt transaction if the remote node involved in the transaction is not accessible. In-doubt transactions appear in the data dictionary view
See Also:"Enabling Distributed Recovery: Example"
POOL clause lets you clear all data from the shared pool in the system global area (SGA). The shared pool stores
Cached data dictionary information and
Shared SQL and PL/SQL areas for SQL statements, stored procedures, function, packages, and triggers.
This statement does not clear shared SQL and PL/SQL areas for items that are currently being executed. You can use this clause regardless of whether your instance has the database dismounted or mounted, open or closed.
See Also:"Clearing the Shared Pool: Example"
BUFFER_CACHE clause lets you clear all data from the buffer cache in the system global area (SGA).
Caution:This clause is intended for use only on a test database. Do not use this clause on a production database, because as a result of this statement, subsequent queries will have no hits, only misses.
This clause is useful if you need to measure the performance of rewritten queries or a suite of queries from identical starting points.
LOGFILE clause lets you explicitly force Oracle Database to begin writing to a new redo log file group, regardless of whether the files in the current redo log file group are full. When you force a log switch, Oracle Database begins to perform a checkpoint but returns control to you immediately rather than when the checkpoint is complete. To use this clause, your instance must have the database open.
See Also:"Forcing a Log Switch: Example"
SUSPEND clause lets you suspend all I/O (datafile, control file, and file header) as well as queries, in all instances, enabling you to make copies of the database without having to handle ongoing transactions.
Do not use this clause unless you have put the database tablespaces in hot backup mode.
Do not terminate the session that issued the
SUSPEND statement. An attempt to reconnect while the system is suspended may fail because of recursive SQL that is running during the
If you start a new instance while the system is suspended, then that new instance will not be suspended.
RESUME clause lets you make the database available once again for queries and I/O.
Use these clauses in a clustered Automatic Storage Management (ASM) environment to migrate one node at a time to a different ASM version without affecting the overall availability of the ASM cluster or the database clusters using ASM for storage.
<version_num>, <release_num>, <update_num>,<port_release_num>,<port_update_num>
ASM_version must be equal to or greater than 188.8.131.52.0. Automatic Storage Management first verifies that the current release is compatible for migration to the specified release, and then goes into limited functionality mode. Automatic Storage Management then determines whether any rebalance operations are under way anywhere in the cluster. If there are any such operations, then the statement fails and must be reissued after the rebalance operations are complete.
Rolling upgrade mode is a cluster-wide in-memory persistent state. The cluster continues to be in this state until there is at least one ASM instance running in the cluster. Any new instance joining the cluster switches to s migration mode immediately upon startup. If all the instances in the cluster terminate, then subsequent startup of any Automatic Storage Management instance will not be in rolling upgrade mode until you reissue this statement to restart rolling upgrade of the Automatic Storage Management instances.
STOP ROLLING MIGRATION Use this clause to stop rolling upgrade and bring the cluster back into normal operation. Specify this clause only after all instances in the cluster have migrated to the same software version. The statement will fail if the cluster is not in rolling upgrade mode.
When you specify this clause, the Automatic Storage Management instance validates that all the members of the cluster are at the same software version, takes the instance out of rolling upgrade mode, and returns to full functionality of the Automatic Storage Management cluster. If any rebalance operations are pending because disks have gone offline, then those operations are restarted if the
ASM_POWER_LIMIT parameter would not be violated by such a restart.
See Also:Oracle Database Storage Administrator's Guide for more information about rolling upgrade
UNQUIESCE clauses to put the database in and take it out of the quiesced state. This state enables database administrators to perform administrative operations that cannot be safely performed in the presence of concurrent transactions, queries, or PL/SQL operations.
RESTRICTEDclause is valid only if the Database Resource Manager is installed and only if the Resource Manager has been on continuously since database startup in any instances that have opened the database.
UNQUIESCE statements issue at the same time from different sessions or instances, then all but one will receive an error.
RESTRICTED to put the database in the quiesced state. For all instances with the database open, this clause has the following effect:
Oracle Database instructs the Database Resource Manager in all instances to prevent all inactive sessions (other than
SYSTEM) from becoming active. No user other than
SYSTEM can start a new transaction, a new query, a new fetch, or a new PL/SQL operation.
Oracle Database waits for all existing transactions in all instances that were initiated by a user other than
SYSTEM to finish (either commit or abort). Oracle Database also waits for all running queries, fetches, and PL/SQL procedures in all instances that were initiated by users other than
SYSTEM and that are not inside transactions to finish. If a query is carried out by multiple successive OCI fetches, then Oracle Database does not wait for all fetches to finish. It waits for the current fetch to finish and then blocks the next fetch. Oracle Database also waits for all sessions (other than those of
SYSTEM) that hold any shared resources (such as enqueues) to release those resources. After all these operations finish, Oracle Database places the database into quiesced state and finishes executing the
If an instance is running in shared server mode, then Oracle Database instructs the Database Resource Manager to block logins (other than
SYSTEM) on that instance. If an instance is running in non-shared-server mode, then Oracle Database does not impose any restrictions on user logins in that instance.
During the quiesced state, you cannot change the Resource Manager plan in any instance.
UNQUIESCE to take the database out of quiesced state. Doing so permits transactions, queries, fetches, and PL/SQL procedures that were initiated by users other than
SYSTEM to be undertaken once again. The
UNQUIESCE statement does not have to originate in the same session that issued the
alter_system_security_clauses let you control access to the instance.
SESSION clause lets you restrict logon to Oracle Database. You can use this clause regardless of whether your instance has the database dismounted or mounted, open or closed.
ENABLE to allow only users with
SESSION system privilege to log on to Oracle Database. Existing sessions are not terminated.
This clause applies only to the current instance. Therefore, in an Oracle RAC environment, authorized users without the
SESSION system privilege can still access the database by way of other instances.
DISABLE to reverse the effect of the
SESSION clause, allowing all users with
SESSION system privilege to log on to Oracle Database. This is the default.
See Also:"Restricting Sessions: Example"
Use this clause to manage database access to information in the server wallet. Although this statement begins with the keyword
WALLET statement is not a DDL clause. However, you cannot roll back such a statement.
OPEN When you specify this clause, the database uses the specified password to load information from the server wallet into memory for database access for the duration of the instance. This clause lets the database retrieve keys from the server wallet without an SSO wallet. If the server wallet is not available or is already open, then the database returns an error. In this context, the double quotation marks around the password are required.
See Also:Oracle Real Application Clusters Administration and Deployment Guide for information on setting encryption wallets in an Oracle Real Application Clusters (Oracle RAC) environment
Use this clause to generate a new encryption key and to set it as the current transparent data encryption master key. This clause also loads information from the server wallet into memory for database access. The
certificate_id is the integer that identifies the certificate. It is not required if you are using basic keys, but it is required if you are using PKI-based keys. You can find this value by querying the
CERT_ID column of the
V$WALLET dynamic performance view. For
password, specify the password used to connect to the security module. If you specify an invalid
certificate_id or password, then the database returns an error. In this context, the double quotation marks around the password are required.
KEY statement is a DDL statement and will automatically commit any pending transactions in the schema.
You must set both an encryption wallet and an encryption key to use the transparent data encryption feature.
Oracle Database Advanced Security Administrator's Guide for more information on using the server wallet and encryption keys and on transparent data encryption
The description of the
TABLE "encryption_spec " for information on using that feature to encrypt table columns
SHUTDOWN clause is relevant only if your system is using the shared server architecture of Oracle Database. It shuts down a dispatcher identified by
Note:Do not confuse this clause with the SQL*Plus command
SHUTDOWN, which is used to shut down the entire database.
dispatcher_name must be a string of the form '
xxx indicates the number of the dispatcher. For a listing of dispatcher names, query the
NAME column of the
V$DISPATCHER dynamic performance view.
If you specify
IMMEDIATE, then the dispatcher stops accepting new connections immediately and Oracle Database terminates all existing connections through that dispatcher. After all sessions are cleaned up, the dispatcher process shuts down.
If you do not specify
IMMEDIATE, then the dispatcher stops accepting new connections immediately but waits for all its users to disconnect and for all its database links to terminate. Then it shuts down.
REGISTER to instruct the
PMON background process to register the instance with the listeners immediately. If you do not specify this clause, then registration of the instance does not occur until the next time
PMON executes the discovery routine. As a result, clients may not be able to access the services for as long as 60 seconds after the listener is started.
See Also:Oracle Database Concepts and Oracle Database Net Services Administrator's Guide for information on the
PMONbackground process and listeners
You can change the value of many initialization parameters for the current instance, whether you have started the database with a traditional plain-text parameter file (pfile) or with a server parameter file (spfile). Oracle Database Reference indicates these parameters in the "Modifiable" category of each parameter description. If you are using a pfile, then the change will persist only for the duration of the instance. However, if you have started the database with an spfile, then you can change the value of the parameter in the spfile itself, so that the new value will occur in subsequent instances.
Oracle Database Reference documents all initialization parameters in full. The parameters fall into three categories:
Basic parameters: Database administrators should be familiar with and consider the setting for all of the basic parameters.
Functional categories: Oracle Database Reference also lists the initialization parameters by their functional category.
Alphabetical listing: The Table of Contents of Oracle Database Reference contains all initialization parameters in alphabetical order.
The ability to change initialization parameter values depends on whether you have started up the database with a traditional plain-text initialization parameter file (pfile) or with a server parameter file (spfile). To determine whether you can change the value of a particular parameter, query the
ISSYS_MODIFIABLE column of the
V$PARAMETER dynamic performance view.
When setting a parameter value, you can specify additional settings as follows:
COMMENT clause lets you associate a comment string with this change in the value of the parameter. If you also specify
SPFILE, then this comment will appear in the parameter file to indicate the most recent change made to this parameter.
You must specify
DEFERRED if the value of the
ISSYS_MODIFIABLE column of
V$PARAMETER for this parameter is
DEFERRED. If the value of that column is
IMMEDIATE, then the
DEFERRED keyword in this clause is optional. If the value of that column is
FALSE, then you cannot specify
DEFERRED in this
See Also:Oracle Database Reference for information on the
V$PARAMETERdynamic performance view
SCOPE clause lets you specify when the change takes effect. Scope depends on whether you started up the database using a traditional plain-text parameter file (pfile) or server parameter file (spfile).
MEMORY indicates that the change is made in memory, takes effect immediately, and persists until the database is shut down. If you started up the database using a parameter file (pfile), then this is the only scope you can specify.
SPFILE indicates that the change is made in the server parameter file. The new setting takes effect when the database is next shut down and started up again. You must specify
SPFILE when changing the value of a static parameter that is described as not modifiable in Oracle Database Reference.
BOTH indicates that the change is made in memory and in the server parameter file. The new setting takes effect immediately and persists after the database is shut down and started up again.
If a server parameter file was used to start up the database, then
BOTH is the default. If a parameter file was used to start up the database, then
MEMORY is the default, as well as the only scope you can specify.
'*' if you want Oracle Database to change the value of the parameter for all instances that do not already have an explicit setting for this parameter.
'sid' if you want Oracle Database to change the value of the parameter only for the instance
sid. This setting takes precedence over previous and subsequent
SET statements that specify
If you do not specify this clause, then:
If the instance was started up with a pfile (traditional plain-text initialization parameter file), then Oracle Database assumes the SID of the current instance.
If the instance was started up with an spfile (server parameter file), then Oracle Database assumes
If you specify an instance other than the current instance, then Oracle Database sends a message to that instance to change the parameter value in the memory of that instance.
See Also:Oracle Database Reference for information about the
USE_STORED_OUTLINES is a system parameter, not an initialization parameter. You cannot set it in a pfile or spfile, but you can set it with an
SYSTEM statement. This parameter determines whether the optimizer will use stored public outlines to generate execution plans.
TRUE causes the optimizer to use outlines stored in the
DEFAULT category when compiling requests.
FALSE specifies that the optimizer should not use stored outlines. This is the default.
category_name causes the optimizer to use outlines stored in the
category_name category when compiling requests.
GLOBAL_TOPIC_ENABLED is a system parameter, not an initialization parameter. You cannot set it in a pfile or spfile, but you can set it with an
SYSTEM statement. This parameter determines whether all queues and topics created in Oracle Streams AQ are automatically registered with the LDAP server. If
TRUE when a queue table is created, altered, or dropped, then the corresponding Lightweight Directory Access Protocol (LDAP) entry is also created, altered or dropped.
The parameter works the same way for the Java Message Service (JMS). If a database has been configured to use LDAP and the
GLOBAL_TOPIC_ENABLED parameter has been set to
TRUE, then all JMS queues and topics are automatically registered with the LDAP server when they are created. The administrator can also create aliases to the queues and topics registered in LDAP. Queues and topics that are registered in LDAP can be looked up through JNDI using the name or alias of the queue or topic.
When you start your instance, Oracle Database creates shared server processes and dispatcher processes for the shared server architecture based on the values of the
DISPATCHERS initialization parameters. You can also set the
DISPATCHERS parameters with
SYSTEM to perform one of the following operations while the instance is running:
Create additional shared server processes by increasing the minimum number of shared server processes.
Terminate existing shared server processes after their current calls finish processing.
Create more dispatcher processes for a specific protocol, up to a maximum across all protocols specified by the initialization parameter
Terminate existing dispatcher processes for a specific protocol after their current user processes disconnect from the instance.
This clause lets you remove the setting, for any instance, of any initialization parameter in the spfile that was used to start the instance. Neither
BOTH are allowed. The
SPFILE clause is not required, but is included for syntactic clarity. You can use this clause in a single-instance environment, but only if the instance was started using an spfile rather than a pfile.
SID clause to remove the spfile parameter setting for a specified instance. In a non-RAC environment, you can omit this clause, because there is only one instance. In a RAC environment, if you omit this clause, then the default of
SID = '*' is used, which means that the all settings of the parameter of the form
parameter = value are removed.
Oracle Real Application Clusters Administration and Deployment Guide for information on setting parameter values for an individual instance in an Oracle Real Application Clusters environment
The following examples of using the
SYSTEM statement: "Changing Licensing Parameters: Examples", "Enabling Query Rewrite: Example", "Enabling Resource Limits: Example", "Shared Server Parameters", and "Changing Shared Server Settings: Examples"
ALTER SYSTEM ARCHIVE LOG CHANGE 9356083;
The following statement manually archives the redo log file group containing a member named '
diskl:log6.log' to an archived redo log file in the location '
ALTER SYSTEM ARCHIVE LOG LOGFILE 'diskl:log6.log' TO 'diska:[arch$]';
ALTER SYSTEM SET QUERY_REWRITE_ENABLED = TRUE;
Restricting Sessions: Example You might want to restrict sessions if you are performing application maintenance and you want only application developers with
SESSION system privilege to log on. To restrict sessions, issue the following statement:
ALTER SYSTEM ENABLE RESTRICTED SESSION;
You can then terminate any existing sessions using the
SESSION clause of the
After performing maintenance on your application, issue the following statement to allow any user with
SESSION system privilege to log on:
ALTER SYSTEM DISABLE RESTRICTED SESSION;
ALTER SYSTEM SET ENCRYPTION WALLET OPEN IDENTIFIED BY "welcome1"; ALTER SYSTEM SET ENCRYPTION KEY IDENTIFIED BY "welcome1";
These statements assume that you have initialized the security module and created a wallet with the password
ALTER SYSTEM FLUSH SHARED_POOL;
ALTER SYSTEM CHECKPOINT;
ALTER SYSTEM SET RESOURCE_LIMIT = TRUE;
ALTER SYSTEM SET SHARED_SERVERS = 25;
If there are currently fewer than 25 shared server processes, then Oracle Database creates more. If there are currently more than 25, then Oracle Database terminates some of them when they are finished processing their current calls if the load could be managed by the remaining 25.
The following statement dynamically changes the number of dispatcher processes for the TCP/IP protocol to 5 and the number of dispatcher processes for the ipc protocol to 10:
ALTER SYSTEM SET DISPATCHERS = '(INDEX=0)(PROTOCOL=TCP)(DISPATCHERS=5)', '(INDEX=1)(PROTOCOL=ipc)(DISPATCHERS=10)';
If there are currently fewer than 5 dispatcher processes for TCP, then Oracle Database creates new ones. If there are currently more than 5, then Oracle Database terminates some of them after the connected users disconnect.
If there are currently fewer than 10 dispatcher processes for ipc, then Oracle Database creates new ones. If there are currently more than 10, then Oracle Database terminates some of them after the connected users disconnect.
If there are currently existing dispatchers for another protocol, then the preceding statement does not affect the number of dispatchers for that protocol.
ALTER SYSTEM SET LICENSE_MAX_SESSIONS = 64 LICENSE_SESSIONS_WARNING = 54;
If the number of sessions reaches 54, then Oracle Database writes a warning message to the
ALERT file for each subsequent session. Also, users with
SESSION system privilege receive warning messages when they begin subsequent sessions.
If the number of sessions reaches 64, then only users with
SESSION system privilege can begin new sessions until the number of sessions falls below 64 again.
The following statement dynamically disables the limit for sessions on your instance. After you issue this statement, Oracle Database no longer limits the number of sessions on your instance.
ALTER SYSTEM SET LICENSE_MAX_SESSIONS = 0;
The following statement dynamically changes the limit on the number of users in the database to 200. After you issue the preceding statement, Oracle Database prevents the number of users in the database from exceeding 200.
ALTER SYSTEM SET LICENSE_MAX_USERS = 200;
Forcing a Log Switch: Example You might want to force a log switch to drop or rename the current redo log file group or one of its members, because you cannot drop or rename a file while Oracle Database is writing to it. The forced log switch affects only the redo log thread of your instance. The following statement forces a log switch:
ALTER SYSTEM SWITCH LOGFILE;
ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY;
You might want to disable distributed recovery for demonstration or testing purposes. You can disable distributed recovery in both single-process and multiprocess mode with the following statement:
ALTER SYSTEM DISABLE DISTRIBUTED RECOVERY;
When your demonstration or testing is complete, you can then enable distributed recovery again by issuing an
SYSTEM statement with the
Terminating a Session: Example You might want to terminate the session of a user that is holding resources needed by other users. The user receives an error message indicating that the session has been terminated. That user can no longer make calls to the database without beginning a new session. Consider this data from the
V$SESSION dynamic performance table, when the users
oe both have open sessions:
SELECT sid, serial#, username FROM V$SESSION; SID SERIAL# USERNAME ---------- ---------- ------------------------------ 29 85 SYS 33 1 35 8 39 23 OE 40 1 . . .
The following statement terminates the session of the user
scott using the
SERIAL# values from
ALTER SYSTEM KILL SESSION '39, 23';
ALTER SYSTEM DISCONNECT SESSION '13, 8' POST_TRANSACTION;