Re: intermittent long "log file sync" waits
From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Wed, 5 Feb 2020 17:44:42 -0500
Message-ID: <CAMHX9JLwePmDbx9-XJWZC2j8ck-wnbOHxLr_rPTjQ8WO598FJQ_at_mail.gmail.com>
Date: Wed, 5 Feb 2020 17:44:42 -0500
Message-ID: <CAMHX9JLwePmDbx9-XJWZC2j8ck-wnbOHxLr_rPTjQ8WO598FJQ_at_mail.gmail.com>
The short version (possibly with typos):
*4) *Cursor #0 is shown when the client is making "cursorless" top-level database calls like OCICommit() in OCI or conn.commit() in JDBC, instead of parsing and executing a SQL statement with text "commit" in it. The top_level_call_name in ASH or OPI trace event 10051 would show "COMMIT" as the database call instead of V8 Bundled Exec <https://tanelpoder.com/2011/08/23/v8-bundled-exec-call-and-oracle-program-interface-opi-calls/> .
SQL> _at_tlc commit
Display top-level call names matching %commit% (Oracle 11.2+)
TOP_LEVEL_CALL# TOP_LEVEL_CALL_NAME
--------------- --------------------------------------------- 12 COMMIT ON 13 COMMIT OFF 14 COMMIT 89 XA XA Commit 104 Transaction Commit/Rollback 117 Commit Remote Sites 127 Commit Remote Sites >= V813
-- Tanel Poder https://tanelpoder.com/seminar On Wed, Feb 5, 2020 at 5:32 PM Tanel Poder <tanel_at_tanelpoder.com> wrote:Received on Wed Feb 05 2020 - 23:44:42 CET
>
>>>>
-- http://www.freelists.org/webpage/oracle-l