Sunday, January 15, 2017

ODI Learning

When ever we create a complex file in ODI and test the connection

It actually creates the table structure in the DB Schema where it is pointing to .

There is an option of defining s=Schema in ODI complex file JDBC String

jdbc:snps:complexfile?f=C:\Users\arahi\Desktop\sample.txt&d=C:\Users\arahi\EDI.xsd&re=EDIX12&s=Arpit&db_props=odistagedb.properties

Here i have specified Arpit, this will get added to all the table which will be created out of the complex file

i.e. if i have three complex type in my complex file

Invoice
Header and Detail

It will create three tables in the backend database

Arpit_Invoice, Arpit_Header and Arpit_Detail.

All the table will be created in the sb schema which is specified in the odistagedb.properties file mentioned above.

This file needs to be stored in %ODI_DOMAIN_DIR%/bin directory

This file contains following sample values

driver=oracle.jdbc.driver.OracleDriver
url=jdbc:oracle:thin:@localhost:1521:XE
user=odi_stage
password=Jn9h9kjXM6d3wqsljXtetA==
schema=odi_stage
drop_on_connect=N
create_tables=AUTO
create_indexes=Y
truncate_before_load=Y
ids_in_db=Y
drop_tables_on_drop_schema=Y
use_prepared_statements=Y
use_batch_update=Y
batch_update_size=30
commit_periodically=Y
num_inserts_before_commit=1000
reserve_chars_for_column=3
reserve_chars_for_table=3


Here the password is encrypted and you can use ODIFTP activities in a package to encrypt this password

1 comment:

Srinu Vasu said...

This concept is a good way to enhance the knowledge.thanks for sharing..
ODI Online Training
ODI Training
ODI support