Updating System Temporary Tables
Go Up to Monitoring with System Temporary Tables
There are cases where, having acquired information about the state of the database, you need to take appropriate action. You might, for example, detect a transaction that had unexpectedly been open for many hours, or one that was consuming resources that were needed by others. By updating the TMP$STATE
column of certain temporary tables, you can perform the following updates:
- Roll back an active or limbo transaction
- Commit a limbo transaction
- Cancel an attachment’s executing operation
- Shut down the current attachment
- Ping database attachments to check if they are alive
- Make an executing statement stop running
Making single changes
The following examples operate on a single attachment or transaction.
Action | Statement |
---|---|
To roll back an active transaction |
|
To roll back a limbo transaction |
|
To commit a limbo transaction |
|
To cancel the attachment’s currently executing operation |
|
To shut down the current attachment |
|
To ping an attachment by sending a keepalive request. If the connection/attachment is defunct, the server will automatically cleanup the port |
|
To make an executing statement stop running |
|
Shutting down an attachment detaches the user from the database and terminates the local or network attachment to the server.
Making global changes
You can make more global changes, as listed below.
Action | Statement |
---|---|
To roll back all active transactions |
|
To roll back all limbo transactions |
|
To commit all limbo transactions |
|