bind datatype: dty=180
- From: "Igor Neyman" <ineyman@xxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 9 Mar 2005 16:28:01 -0500
Oracle version: 10.1.0.2.0
Platform: WinXP
Interface: ODBC
I see wrong execution plan for the following (traced) statement. I
assume, it's because Oracle is doing implicit conversion for
"CYCLE_DATE_TIME".
Datatype for "CYCLE_DATE_TIME" in GP_CYCLE is DATE, so I was expecting
to see (in the trace file) dty=12 for bind variable.
Instead it shows dty=180. What type is "dty=180"?
Here is pieces of relevent information from the trace file:
PARSING IN CURSOR #4 len=229 dep=0 uid=34 oct=6 lid=34 tim=2103637833
hv=4014771486 ad='245d3c4c'
UPDATE GP_CYCLE SET quality_code_id=:1,alarm_count=:2 WHERE
"CYCLE_DATE_TIME" = :3 AND "CELL_ID" = :4 AND "PART_TYPE_ID" = :5 AND
"CYCLE_MODE_CODE_ID" = :6 AND "ERROR_COUNT" = :7 AND "QUALITY_CODE_ID" =
:8 AND "ALARM_COUNT" = :9
........
BINDS #4
...........
bind 2: dty=180 mxl=11(11) mal=00 scl=09 pre=00 oacflg=07 oacfl2=0000
size=0 offset=48
bfp=05a4ff64 bln=11 avl=07 flg=01
value=
Dump of memory from 0x05A4FF64 to 0x05A4FF6B
5A4FF60 08036978 000E0E0B [xi......]
Anyone encountered this problem when using ODBC interface?
Igor Neyman, OCP DBA
ineyman@xxxxxxxxxxxxxx
--
//www.freelists.org/webpage/oracle-l
Other related posts:
