Search found 87 matches

by mab_arif16
Thu Jun 08, 2006 12:05 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: truncate and write transaction scope
Replies: 6
Views: 1786

Well then you will have to investigate on how to set the commit size in the odbc stage. As per your second question, the odbc stage uses the generic driver to connect to the databases. Where as the DRS stage uses the native interface. The performance difference with both these stages is relative to...
by mab_arif16
Thu Jun 08, 2006 11:52 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: truncate and write transaction scope
Replies: 6
Views: 1786

The size should be 0. A 0 transaction size mean that the data will only be committed once the job finsihes successfull. It will roll back the data if the job aborts. But i believe the table will be truncated because it issues the truncate command even before inserting. I have to look into that myse...
by mab_arif16
Thu Jun 08, 2006 11:39 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Varbinary error
Replies: 6
Views: 1887

ray.wurlod wrote:Reserved for future use? Also, the list of SQL data types is those decreed by the SQL 92 standard.
If we use stringtoraw fn in transformer what data type the string gets converted to .
Thanks
Arif
by mab_arif16
Thu Jun 08, 2006 11:34 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: truncate and write transaction scope
Replies: 6
Views: 1786

A delete is a logged operatioin and is at a row level. Truncate is at the table level and is much faster than a delete. When you use truncate and then insert update action, it wipes out the entire table and then inserts. The commit depends upon the transaction size you provide. . Hi Does defining i...
by mab_arif16
Thu Jun 08, 2006 11:10 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: truncate and write transaction scope
Replies: 6
Views: 1786

truncate and write transaction scope

Hi
In ODBC enterprise stage if you use the option truncate and write ,will these two operations be done in one transaction.I mean will the data disappear and reappear i.e will there be a commit after truncate and then data is written.
Is trucate just a faster delete?
Thanks
Arif
by mab_arif16
Wed Jun 07, 2006 5:22 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Varbinary error
Replies: 6
Views: 1887

Re: Varbinary error

ray.wurlod wrote:
mab_arif16 wrote:While compiling I am getting an error varbinary dataype not supported does the data stage supports varbinary?
Isn't it obvious from the message?
Why does the datastage has it then
by mab_arif16
Wed Jun 07, 2006 4:10 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Enterprise load error
Replies: 16
Views: 5457

In your enterprise stage. There has to be an option to specify whether the table has indexes on it or not. I think you need to set that to Yes. I dont have access to PX at the moment. Try to locate it in your properties. I used the rebuild index option ,but got the error Oracle_Enterprise_8: Disk l...
by mab_arif16
Wed Jun 07, 2006 4:02 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Varbinary error
Replies: 6
Views: 1887

Varbinary error

I am sourcing the data from sybase which contains a varbinary feild ,While compiling I am getting an error varbinary dataype not supported does the data stage supports varbinary? I had to use bintostr() fn in the sql and that data type to varchar ,Its working but I am not sure how to change it back ...
by mab_arif16
Wed Jun 07, 2006 3:49 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Fast Load
Replies: 1
Views: 1070

Oracle Fast Load

I am trying to use the fast load option in oracle enterprise stage ,are there any special things that need to taken care of before using it . As I am getting index errors Oracle_Enterprise_8: Indexes on table 'thk.track' preclude direct parallel loading unless an index option is included. Add an ind...
by mab_arif16
Wed Jun 07, 2006 11:47 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Enterprise load error
Replies: 16
Views: 5457

kris007 wrote:Did you try setting the scale to 0 and then insert/upsert the data?
I am not able to set the scale to 0 min I can go is 1.
Thanks
Arif
by mab_arif16
Wed Jun 07, 2006 11:43 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Enterprise load error
Replies: 16
Views: 5457

Ok last resort. Try changing the meta data from timestamp to varchar. That usually works almost all the time in server. Dont know about PX. Worth a try. Changing to varchar in the target meta data works but Now I get a different error Oracle_Enterprise_47: Indexes on table 'ars.gim_table' preclude ...
by mab_arif16
Wed Jun 07, 2006 11:31 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Enterprise load error
Replies: 16
Views: 5457

DSguru2B wrote:try concatenating ".000000 PM" and then loading it.
That also didnt work.
As kris said I event tried changing the meta data and using feild fn but that also doesnt seem to go thru.For upsert I was using auto generated query
Thanks
Arif
by mab_arif16
Wed Jun 07, 2006 10:54 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Enterprise load error
Replies: 16
Views: 5457

DSguru2B wrote:While inserting the database puts the extra milli seconds to fulfill the precision. I dont think that is true for a LOAD operation. Try adding the extra part. like do a concatenation

Code: Select all

in.date:".000000"
Tried it but still the same error
Thanks
Arif
by mab_arif16
Wed Jun 07, 2006 10:43 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Enterprise load error
Replies: 16
Views: 5457

As per my understanging the problem exists in the last part of your timestamp after the "." character. I am not sure how Oracle is accepting that format while doing an upsert but not while an insert. Use a FIELD function to trim of the trailing zeroes( assuming they are not an important p...
by mab_arif16
Wed Jun 07, 2006 10:21 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Enterprise load error
Replies: 16
Views: 5457

Re: Oracle Enterprise load error

rwierdsm wrote:Oracle wants it's date/times to be format CCYY-MM-DD HH:MM:SS. Does the resulting SQL command in the OCI convert the date?

Not sure why Upsert would work but not insert....

Rob
While doing the upsert the date is loaded in the format 4/13/2004 5:14:16.000000 PM ,but the load doesnt work