In a BIND again...

Forgot to include the list in the reply...
 
 bind 5: dty=180 mxl=11(11) mal=00 scl=00 pre=00 oacflg=03 oacfl2=0
size=0 offset=120
   bfp=40759cbc bln=11 avl=07 flg=01
   value=
Dump of memory from 0x40759CBC to 0x40759CC3
40759CB0                            0C0A6B78              [xk..]
40759CC0 00010101                             [....]


________________________________

From: Sweetser, Joe 
Sent: Friday, October 12, 2007 11:17 AM
To: 'Allen, Brandon'
Subject: RE: In a BIND again...


Thanks yet again, Brandon.  The datatype is 180 (timestamp) and when  I
describe the table the column is defined as number(1).
 
More fun to come, I'm sure!
 
-joe

________________________________

From: Allen, Brandon [mailto:Brandon.Allen@xxxxxxxxxxx] 
Sent: Friday, October 12, 2007 10:35 AM
To: Sweetser, Joe; oracle-l@xxxxxxxxxxxxx
Subject: RE: In a BIND again...


Take a look at the BIND section of the raw trace file and see what they
look like there.  Maybe some of them were NULL so trace analyzer doesn't
show them.  I'm not sure since I haven't played with the trace analyzer
much.  I usually get by with just the raw trace file, tkprof and
manually looking up the relevant table/index stats.
 
Regards,
Brandon

 

Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do
not consent to Internet email for messages of this kind. Opinions,
conclusions and other information in this message that do not relate to
the official business of this company shall be understood as neither
given nor endorsed by it.

Other related posts: