1

Topic: OCI Direct Path Load API and SQLT_TIMESTAMP

Actually a question
The documentation unambiguously hints that SQLT_TIMESTAMP is supported in OCI Direct Path API. As 187th code.
https://docs.oracle.com/database/122/LN … LNOCI16910
But to push it in a database it was possible only specifying 180th code, peeping it in DUMP ()
On 187th falls, speaking about conversion errors and though you burst.
With other types (SQLT_NUM, SQLT_TIMESTAMP_TZ, SQLT_TIMESTAMP_LTZ) such tricks it is not watched.
To greater surprise intensive ,  and  did not produce generally any examples in this respect, from a word generally anything.
All native examples and demos from Oracle show how to work only with SQLT_CHR
Sketchy review of any libraries (FireDAC/AnyDAC, DOA, ODAC) showed and at all any rudimentary development in this question - in them is supported only SQT_DAT (i.e. DATE), about TIMESTAMP generally anything.
Can at whom there are examples as it is necessary to work correctly with TIMESTAMP Direct Path Loading OCI API?
No, not that that absolutely is necessary,  hands it was possible to me, but doubts that it in any way not documentary method turned out, it guards.

2

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

dbpatch;

select o.name,
t.typecode
from sys.type $ t, sys.obj $ o;
sys.obj $ so, sys.user $ su
where typecode between 180 and 188
and bitand (t.properties, 64) = 64 - u.name is null
and o.oid $ = t.tvoid
and o.subname IS NULL - only the latest version
and o.type# <> 10 - must not be invalid
and bitand (t.properties, 2048) = 0 - not system-generated
and t.supertoid = so.oid $ (+) and so.owner# = su.user# (+)
order by t.typecode

and what for type 180? What version ?

SQL> select dump (timestamp ' 2017-01-01 0:00:00 AM ') from dual;
DUMP (TIMESTAMP ' 2017-01-0100:00:00 ')
---------------------------------------------------------
Typ=187 Len=20: 225,7,1,1,0,0,0,0,0,0,0,0,0,0,3,0,0,0,0,0

3

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

dbpatch;
, reached...

create table ts (ts timestamp);
insert into ts values (systimestamp);
select dump (ts) from ts;

4

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

xtender wrote:

SQL> select dump (timestamp ' 2017-01-01 0:00:00 AM ') from dual;
DUMP (TIMESTAMP ' 2017-01-0100:00:00 ')
---------------------------------------------------------
Typ=187 Len=20: 225,7,1,1,0,0,0,0,0,0,0,0,0,0,3,0,0,0,0,0

My God, a kindergarten trousers on straps.
You dump () look at field value from the table, instead of result of function or a scalar.
There both type, and length another.
In internals it is all it is described http://www.orafaq.com/wiki/Timestamp

5

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

dbpatch;
https://ellebaek.wordpress.com/2011/02/ … -mappings/

6

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

dbpatch;
Showed off? Calmed down? smile))
... Storages at me on all do not suffice

7

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

It I saw, but it does not answer a question - that it is legally necessary/is possible to put in this pancake OCI Direct Path Loader API ()
The documentation speaks put SQLT_TIMESTAMP - and it is not put.
Thus for  TIMESTAMP it is possible to put SQLT_ types or DUMP () types in the column description - that the most interesting, understands both variants with identical result

8

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

dbpatch;
Well you very clever and without straps, probably checked up both on 11.2 and on> =12.1 after fix Bug 9447780?

9

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

And in 12.2 too was "bind changes" which generated still a small group of bugs so and there can be separate

10

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

xtender wrote:

dbpatch;
Well you very clever and without straps, probably checked up both on 11.2 and on> =12.1 after fix Bug 9447780?

It about OCCI and bind
And I about OCI and direct path API, two times by

11

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

dbpatch;
Well and on what versions you checked up?

12

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

xtender wrote:

dbpatch;
Well and on what versions you checked up?

> = 10.2

13

Re: OCI Direct Path Load API and SQLT_TIMESTAMP

xtender wrote:

Well and on what versions you checked up? Whether

There are bases to doubt?
Timestamp appeared in 9.0 as in the documentation of that version type 180 code is specified, and in 12.2. Otherwise serviceability of OCI-appendices in doubt.