Page 1 of 1

ORABULK and ORAOCIBL difference and when to use

Posted: Thu Mar 01, 2007 1:47 pm
by Smeitei
1. What is the difference between ORABULK & ORAOCIBL stage.
2. What is the best scenario in which to use to use this stages

Scenario in which i want it to use.
1. Unload data from Redbrick database (I am using an ODBC stage to unload record and it is working fine)
2. Load the unloaded data to Oracle database(oracle 9i).

Should I use ORABULK or ORAOCIBL stage.

Posted: Thu Mar 01, 2007 2:27 pm
by chulett
ORABULK is for Oracle 7, ORAOCIBL is for 8 (and up). Both are 'bulk loader' stage so use them (the latter, actually) when ever it is appropriate to bulk load the data.

Posted: Thu Mar 01, 2007 2:48 pm
by Smeitei
Thanks for the information . So for my scenario I should be using ORAOCIBL stage as I have to load it to Orcale 9i.

I am planning to have this design approach now.

ODBCstage -----> Transformer ------> ORAOCIBL stage

And in ORAOCIBL stage have a after job subroutine to invoke the sqlldr to load the Oracle table.

Will this design approach work out.

Posted: Thu Mar 01, 2007 3:22 pm
by ray.wurlod
Review the properties of the ORAOCIBL stage carefully. Look for a property with "automatic" in its name.

Posted: Fri Mar 02, 2007 11:13 am
by Smeitei
What is the meaning of that automatic. Does it mean i have to just specify the target table and don't have to create Ctrtl file and data file to load it .

Posted: Fri Mar 02, 2007 11:20 am
by chulett
Basically, yes. Put your cursor in the 'Mode' field and click on 'Property Help'.

Posted: Wed Mar 28, 2007 5:37 am
by vpauls
I,m sorry to step into this conversation but with automatic load in oracibil do you still need to use sqlldr or will the data be automatically put into the given table?

BR
/Elin

Posted: Wed Mar 28, 2007 6:43 am
by ray.wurlod
YOU don't need to use sqlldr in automatic mode, but the stage process does invoke sqlldr (automatically). The implications for Oracle client software and environment variables should therefore be apparent.

Posted: Wed Mar 28, 2007 7:38 am
by chulett
Technically, it doesn't 'invoke sqlldr' as in the command line function but instead hooks directly into the database via an API. This also means it does not generate the 'bad' or 'ctl' or 'dsc' logs you would normally be interested in.

Posted: Wed Mar 28, 2007 12:29 pm
by ray.wurlod
... although sometimes you will get "log" and "logbad" files in /tmp.