oracle commit wait

Triggers do not require a commitI can't write a commit.The trigger and the DML that triggered it are the same transactionDML commits, the action of the trigger is also submitted, or it is rolled back together.Of course, if you must write a commit in a trigger,Then use the autonomous businessEquivalent to a child transaction in a transactionUnder normal circumstances, Oracle stipulates that DDL statements an

1. RAC global wait Event Description In the RAC environment, the most common wait events related to global cache adjustment are global cache Cr request, global cache busy, and equeue. When a process needs to access one or more blocks, Oracle first checks whether the block exists in its cache, the shared access permission is granted to these blocks through global

Waiting event category: ========================================================== ========================================================== ==================================== Administrative: Wait for the user to wait for the DBA command execution result (for example, re-indexing) Waits resulting from DBA commands that cause users to wait (for example, an inde

Oracle11g, a new change in the full table scan algorithm for large tables, based on the large table Oracle 11 GB, new changes in the full table scan algorithm for large tables, according to the large table Db file scattered read For tables with frequent access, if no index is created or an appropriate index is not created, Oracle can only scan the entire table, resulting in a large number of waiting even

~]$ kill-9 8581 -bash:kill: (8581)-No such process Sql>/ Lock_tree ------------------------------------------------------------------------------- 1.1349 2.136 Sql>/ No rows selected. This SID process ends slowly because the background rollback operation is not finished after the kill session. After the kill-related lock process, the page operation is performed again, resulting in a new row lock wait. Analysis: The SQL statement that was traced

a permission on tabl from a user, all execution plans related to the TAB1 table will be invalid. After the cache is invalid, all memory blocks except the handle are cleared. After the object is used, the object must be reloaded. In the preceding example, if you use DDL statements for TAB1, all execution plans that use TAB1 statements will be invalid. When you use these statements, you must re-parse the statements.Therefore, you need to pay attention to using DDL statements. If you do not need t

Overview Wait events can be divided into two main categories, namely, Idle (IDLE) Wait events and non idle (non-idle) wait events. 1). Idle Wait Event Oracle is waiting for some kind of work, not paying too much attention to this part of the event when diagnosing and opti

SQL> select * from v $ version; BANNER--------------------------------------------------------------------------------Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-64bit ProductionPL/SQL Release 11.2.0.1.0-ProductionCORE 11.2.0.1.0 ProductionTNS for Linux: Version 11.2.0.1.0-ProductionNLSRTL Version 11.2.0.1.0-Production Sometimes there is a background wait event: db file async I/O submit This

Reproduce the library cache lock wait event at 11 GB in Oracle From the example below, we can see that re-Compilation of objects in the production database will lead to library cache lock, so we should try to avoid compiling objects during business peaks. If a package or complex dependency exists in the process, it can easily lead to library cache lock. Therefore, you should also pay attention to this issue

Several views related to the Oracle database and session wait events, v $ session: the connection will generate a session, and the information of the current session will be saved in v $ session, and the connection will disappear after disconnection; 2. v $ session_wait: copy the waiting session Status in the current session to the view, disconnect and disappear (wait