Re: CLOB updates using ADODB not showing in trace file

On Mar 7, 1:17 pm, SR <s...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Oracle 8i database on Solaris 9. I know 8i is old, but given that (in our case) Oracle are happy to
take the money and provide extended support, then I feel perfectly within rights to post a question
here, so please, try none of the tiresome replies on getting upgraded.

SQL_TRACE is set to TRUE at the database level.

Initially trace was being enabled via a logon database trigger, but since we noticed the problem I
am about to describe we also switched it on at database level to be sure.

The problem is that updates to CLOB columns on the database in a VB app are not showing up in the
trace files. Granted, the "Updates" are being performed via the ADODB AppendChunk method (and not
via direct SQL), but I would have thought that the ADODB API would have to present pucka SQL (or
PLSQL) to Oracle. The columns value is being updated - we can see it change. Either this method is
somehow bypassing the SQL layer (how likely is that?), or trace gets turned off for the duration of
the "update". Just to add to the confusion, the SQL statements before and after the CLOB "update"
are present.

We have noticed no difference between enabling trace via "alter session set sql_trace=true" and the
event 10046 command (cant remember exact syntax).

MTS is not enabled - server connection is dedicated. Even so, we have searched all the trace files
in udump in case there was some separation of the trace info into different files occurring.

Anyone seen this?

You can post questions here even if you do not have a support
contract.

My guess is that since LOB data is not buffered like normal table/
index blocks that the normal trace process does not see the LOB
update. There may be an event you can set to get the trace
information but I do not know it and a quick scan of the message files
did not turn up any useful information.

I suspect that you are out of luck but someone else may know more.

HTH -- Mark D Powell --


.

Relevant Pages

  • [ANNOUNCE][PATCH 0 of 4] zedtrace, a general-purpose binary tracer
    ... It's called zedtrace and is ... Trace events from different subsystems ... This results in a set of per-cpu trace files in the current directory: ... script as native param variables. ...
    (Linux-Kernel)
  • CLOB updates using ADODB not showing in trace file
    ... Initially trace was being enabled via a logon database trigger, but since we noticed the problem I am about to describe we also switched it on at database level to be sure. ... Granted, the "Updates" are being performed via the ADODB AppendChunk method (and not via direct SQL), but I would have thought that the ADODB API would have to present pucka SQL to Oracle. ...
    (comp.databases.oracle.misc)
  • Re: Setting up Trace in SQL
    ... > The company has a policy and states that we have to audit> our databases. ... >>SQL Server MVP ... But supposed if I were to re-start the DB, the>>> audit does not kick off at all coz the trace files still ...
    (microsoft.public.sqlserver.security)
  • Re: urgent problem that I want to have a comment about
    ... We get exactly the same problem when we build the MFC dll in debug mode. ... You have not said what kind of trace facility you are using, and therefore, there is no ... If these "really good trace files" allocate memory, ...
    (microsoft.public.vc.mfc)
  • Re: WSE Authentication problem when calling from a dll
    ... You are not being able to see the trace files on the web service side ... So I have the web page call a dll which calls the proxy. ... password that I want to use in the wse policy wizard on the web page ...
    (microsoft.public.dotnet.framework.webservices.enhancements)