Regarding I$ table in ODI...

Hi All,
I am new to ODI and testing interfaces whether data is flowing from source to target. I have more than 10 interfaces and those interfaces may use the same database tables.
Now I would like to run all interfaces in one go using a script. I understood, ODI creates a I$ table each time when executing interface.
Suppose If I run two scripts simultaneously which uses same tables, will ODI create two I$ tables or not?
Could anyone please explain me the mechanism?
Thank you in advance.
Regards,
Srini

Hi,
ODI will create and drop the I$ table while the integration process is running.
If your TARGET table is same for all interfaces then you have a problem in running those interfaces in parallel.
Why ? ODI will create C$ and I$table with the same name .
Suppose you 1st interface is running and it has created C$ and I4 table as C1 and I1. Now at the same time interface 2 kicks start . It will try to drop C1 and I1 (if exists ) and then create C1 and I1 once again. It will create problem in integration and your whole process will get messed up.
This situation does not comes if you run all interfaces in a sequence .
If you want to run in parallel then you need to do some changes.
Search in Metalink you will get some notes describing how to overcome this issue .
also see http://odiexperts.com/interface-parallel-execution-a-new-solution
Thanks,
Sutirtha

Similar Messages

How to read I$ table using ODI procedure

Hi
Can any one help me how to drop a I$ table from out sie of interface.
I have tried below approches but no luck
I have created ODI procedure with technology oracle and target logical schema (I$ tables are creating on target DB) with and with out begin and end;
Approch 1:
Given below code in ODi procedure
drop table <%=odiRef.getTable("L", "INT_NAME", "W")%> <% if (new Integer(odiRef.getOption( "COMPATIBLE" )).intValue() >= 10 ) { out.print( "purge" ); }; %>
Approch 2:
drop table I$_<%=odiRef.getTable("L", "TARG_NAME", "A") %>;
Approch 3:
drop table <%=odiRef.getTable("L", "INT_NAME", "W")%> (but it is fetching target dtabase schema anme not I$ table)
Please help me any other alternative way to drop a I$ table, more over this code should be unique for all interface
Regards,
Phanikanth

Thanks bhabani,
Actaul my requirement is some time my scenario is stoping due some issue at Merge Rows Step (I am using IKM Oracle Incremental Update(Merge) KM) when the next iteration starts it is thwoing and error at create flow table I$ step and error is table name is already exists, so i am doing is if the interface went failed I am storing those information in one table using ODI procedure (INF--ko-->ODI procedure) in same ODI procedure I want to call a I$ table to drop.
Can you please provide the steps so it will very useful for me using Java variable.
I have gievn a step as below on create I$ table step (after create I$ statement)
<@ java.lang.String Idollertable = <%=odiRef.getTable("L", "INT_NAME", "W")%> ; @>
I am calling Idollertable variable in ODI procedure which is ko>* of INF as <@=Idollertable@>
Note: I have followed below approch
ODI Procedure Code:
drop table <@=Idollertable@>; --> *2nd approch*
begin
insert into ODI_EXECUTION_ERROR_DETAILS
(SESSION_NO,
SCENARIO_NAME,
CONTEXT_NAME,
ERR_MESSAGE,
INSERT_COUNT,
ERROR_COUNT)
values
<%=snpRef.getSession("SESS_NO")%>,
'<%=odiRef.getPrevStepLog("STEP_NAME")%>',
'<%=odiRef.getContext( "CTX_NAME" )%>',
'<%=odiRef.getPrevStepLog("MESSAGE")%>',
'<%=odiRef.getPrevStepLog("INSERT_COUNT")%>',
'<%=odiRef.getPrevStepLog("ERROR_COUNT")%>'
commit;
drop table <@=Idollertable@>; --> * first approch *
end;
Please help me
Regards,
Phanikanth
Edited by: Phanikanth on Mar 3, 2013 9:52 PM
Edited by: Phanikanth on Mar 3, 2013 9:52 PM

Partition of table in ODI

Hi..friends.
can we use partition of table in ODI 11g?
please give an example with video or picture representation.
Regards
Soumya.

Its still not clear if we can load data in parallel in different partition if yes then how. Do we need to create seperate interface to load data in each partition?
Thanks
Kashi

Export the data with Alias from the alternative table using ODI

Hi!
How to export the data from Essbase with Alias from the alternative table using ODI?
Thanks.

Are you on 10.1.3.6.x? Then: http://john-goodwin.blogspot.com/2008/09/odi-series-part-2-agent.html
Are you on 11g? Then: http://john-goodwin.blogspot.com/2010/12/managing-odi-11g-standalone-agents.html
I will say with only a mild amount of shame and a large amount of gratitude that I installed both releases' agents through John's blog posts.
Regards,
Cameron Lackpour
Edited by: CL on Jun 4, 2012 5:48 PM
Whoops, had the same link in there twice.

Clarification regarding Shadow Table

Hi All,
Clarification regarding Shadow Table. FKK_GPSHAD is a shadow table that belongs to Business Partner. The doubts that i have is
What is Shadow Table?
What is the purpose of Shadow table?
Is it correct way to update Shadow table Manually(Not using any BAPi etc....)?
Is any BAPI available to update The above mentioned Shadow table.
Thanks in Advance..

Reclustering InfoCubes:
With reclustering, the InfoCube fact tables are always completely converted. The system createsshadow tables with a new clustering schema and copies all of the data from the original tables into the shadow tables. As soon as the data is copied, the system creates indexes and the original table replaces the shadow table. After the reclustering request has been successfully completed, both fact tables exist in their original state (name of shadow table) as well as in their modified state with the new clustering schema (name of original table).
You can only use reclustering for InfoCubes. Reclustering deactivates the active aggregates of the InfoCubes; they are reactivated after the conversion.
Reclustering DataStore Objects
Reclustering completely converts the active table of the DataStore object. The system creates a shadow table with a new clustering schema and copies all of the data from the original table into the shadow table. As soon as the data is copied, the system creates indexes and the original table replaces the shadow table. After the reclustering request has been successfully completed, both active tables exist in their original state (name of shadow table) as well as in their modified state with the new clustering schema (name of original table).
You can only use reclustering for standard DataStore objects and DataStore objects for direct update. You cannot use reclustering for write-optimized DataStore objects. User-defined multidimensional clustering is not available for write-optimized DataStore objects.
Pls chk this thread:
Shadow Table?
http://help.sap.com/saphelp_nw2004s/helpdata/en/47/5cf74153b6ca17e10000000a155106/content.htm
Hope this helps,
Reward points...

Exporting Data Of an RDBMS Table to another RDBMS Table using ODI Functions

Hi,
I'm facing a problem while Exporting Data Of an RDBMS Table to another RDBMS Table using ODI User Functions.
Name:- User_Func
Group:- Training
Syntax:- User_Func($(SrcField))
Implementation Syntax:-
(CASE
WHEN $(SrcField) > 40000 THEN 'HIGH'
WHEN $(SrcField) BETWEEN 30000 AND 40000 THEN 'MEDIUM'
ELSE 'LOW'
Linked Technology:-Oracle
To map the GRADE column of my TARGET_EMPTABLE I write
User_Func(SRC_TABLENAME.SALARY)
using Expression Editor.
I got the following error
ODI-1227: Task ODI_FUNC_INTERFACE (Export) fails on the source ORACLE connection Source_DataServer.
Caused By: java.sql.SQLSyntaxErrorException: ORA-00905: missing keyword
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
     at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
     at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
     at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
     at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:947)
     at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1283)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1441)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3823)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1671)
     at oracle.odi.query.JDBCTemplate.executeQuery(JDBCTemplate.java:189)
     at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:89)
     at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:1)
     at oracle.odi.runtime.agent.execution.DataMovementTaskExecutionHandler.handleTask(DataMovementTaskExecutionHandler.java:70)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:558)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:464)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
     at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
     at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
     at java.lang.Thread.run(Thread.java:619)
and in code tab it is:-
select
     SRC_FUNC_TABLE.E_NUMBER     E_NUMBER,
     SRC_FUNC_TABLE.E_NAME     E_NAME,
     SRC_FUNC_TABLE.E_LOC     E_LOC,
     (CASE
WHEN SRC_FUNC_TABLE.E_SAL > 40000 THEN 'HIGH'
WHEN SRC_FUNC_TABLE.E_SAL BETWEEN 30000 AND 40000 THEN 'MEDIUM'
ELSE 'LOW'
)     E_GRADE
from     SOURCE_SCHEMA.SRC_FUNC_TABLE SRC_FUNC_TABLE
where     (1=1)
Please Help

Anindya Chatterjee wrote:
Hi,
I'm facing a problem while Exporting Data Of an RDBMS Table to another RDBMS Table using ODI User Functions.
Name:- User_Func
Group:- Training
Syntax:- User_Func($(SrcField))
Implementation Syntax:-
(CASE
WHEN $(SrcField) > 40000 THEN 'HIGH'
WHEN $(SrcField) BETWEEN 30000 AND 40000 THEN 'MEDIUM'
ELSE 'LOW'
)Your CASE statement syntax is not correct
It is missing an END key word
It should be
(CASE
WHEN $(SrcField) > 40000 THEN 'HIGH'
WHEN $(SrcField) BETWEEN 30000 AND 40000 THEN 'MEDIUM'
ELSE 'LOW'
END )
Linked Technology:-Oracle
To map the GRADE column of my TARGET_EMPTABLE I write
User_Func(SRC_TABLENAME.SALARY)
using Expression Editor.
I got the following error
ODI-1227: Task ODI_FUNC_INTERFACE (Export) fails on the source ORACLE connection Source_DataServer.
Caused By: java.sql.SQLSyntaxErrorException: ORA-00905: missing keyword
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
     at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
     at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
     at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
     at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:947)
     at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1283)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1441)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3823)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1671)
     at oracle.odi.query.JDBCTemplate.executeQuery(JDBCTemplate.java:189)
     at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:89)
     at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:1)
     at oracle.odi.runtime.agent.execution.DataMovementTaskExecutionHandler.handleTask(DataMovementTaskExecutionHandler.java:70)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:558)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:464)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
     at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
     at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
     at java.lang.Thread.run(Thread.java:619)
and in code tab it is:-
select
     SRC_FUNC_TABLE.E_NUMBER     E_NUMBER,
     SRC_FUNC_TABLE.E_NAME     E_NAME,
     SRC_FUNC_TABLE.E_LOC     E_LOC,
     (CASE
WHEN SRC_FUNC_TABLE.E_SAL > 40000 THEN 'HIGH'
WHEN SRC_FUNC_TABLE.E_SAL BETWEEN 30000 AND 40000 THEN 'MEDIUM'
ELSE 'LOW'
)     E_GRADE
from     SOURCE_SCHEMA.SRC_FUNC_TABLE SRC_FUNC_TABLE
where     (1=1)
Please Help

OIM - query regarding child tables

Hi All
I have a query regarding child tables. For example, when a user is removed from an AD group, his corresponding entry from the AD groups child table will be deleted. I want to know whether it is deleted of marked as deleted. Can I get the information later on that the user was removed from which AD group?
Please help.
Thanks

You will have to enable the audit level = Resource Form and perform the additional tasks to track the process form data changes. This will track all modifications to the forms.
-Kevin

Why do we need Work Table in ODI???

Hello All,
Please help me on this..
Why do we need Work table in ODI???
Why ODI is creating c$_0table_name (work table)?
Thanks
Ravikiran

Hi,
this is the standard "Load Data" from LKM SQL to SQL
+<%for (int i=odiRef.getDataSetMin(); i <= odiRef.getDataSetMax(); i++){%>+
+<%=odiRef.getDataSet(i, "Operator")%>+
select     <%=odiRef.getPop("DISTINCT_ROWS")%>
+     <%=odiRef.getColList(i, "", "[EXPRESSION]\t[ALIAS_SEP] [CX_COL_NAME]", ",\n\t", "", "")%>+
from     <%=odiRef.getFrom(i)%>
where     (1=1)
+*<%=odiRef.getFilter(i)%>*+
+*<%=odiRef.getJrnFilter(i)%>*+
+<%=odiRef.getJoin(i)%>+
+<%=odiRef.getGrpBy(i)%>+
+<%=odiRef.getHaving(i)%>+
+<%}%>+
as you can see in C$_ you could have some filtered data. If you have got a source table containing invoicing (10kk rows) you could filter last_update column and obtain 1k rows for example and copy only this tiny subset.

Creating a REF table in ODI without a source table

Hi,
How can I create a REF table in ODI, that REF table is teh target but I do not have a source table. It is a small table with 20 records two columns Program-id an incremental counter and Program Desc, text values to be keted in.
Thanks for your time and help.

you should use an ODI procedure to do that
in PL-SQL for example

How to load the data using a plsql table in ODI.

Hi All ,
Can anyone help me on this ?
We have a PLSQL procedure which returns a plsql table as out parameter.
We are supposed to load the data in to a file using this plsql table (Table type) in ODI.
Can this be done using ODI?
Regards,
Karthik+

Hi,
We have one process with a ref cursor (Oracle) as a source and remote Oracle DB as a target. I ended up writing my own KM that populates a global temporary table from the cursor first and then transfers the data to target. If temporary table is an option for you, the rest is pretty easy.
Regards.

How to capture Field validation errors in the Error table in ODI 11g

Hello,
We are using ODI 11g (11.1.1.5) and the scenario is to read the data from a flat file (.txt) and do a bulk insert into MS SQL Server database table.
We need to capture the error records (if the source field size is greater than the target column size) into the error table. However the interface errors out at step "Loading - SrcSet0 - Load data (BULK INSERT)" with error message "SQLServer JDBC Driver][SQLServer]Bulk load data conversion error (truncation) for row 33, column 6" but these errors are not being inserted into the error table.
Is there a way to capture these errors in the error table? Below is the KM details.
LKM: LKM File to MSSQL (BULK)
CKM: CKM SQL
IKM: IKM MSSQL Incremental Update
FLOW_CONTROL is set to true for the IKM.
Thanks,
Krishna

Hello,
I had the same problem with ODI when I was trying BULK INSERT of the txt file into MS SQL. Check the cell(s) in your source file (txt) - it looks like the value in hte cell has hiding symbols: when pressing F2 tryng edit the value in the cell the coursor appared far to the right from the right end of the value. So, try to use backspace to delete the hiding symbols and verify the above. If avasrything is OK, then modify your txt file. Let me know if it works.
BTW , I've created procedure inside the MS SQL 2008R2, which BULK INSERTed records into temporary (#...) table and immediatelly, without any verification all the records were inserted into the final table in the DWH here is the statement:
if object_id('TEMPDB..#<table>','U') is not null drop table #<table>
CREATE TABLE [dbo].[#<table>]
[1] [varchar] (50) NULL,
[2] [varchar] (100) NULL,
[3] [varchar] (100) NULL,
[4] [varchar] (100) NULL,
[5] [varchar] (100) NULL,
[6] [varchar] (100) NULL,
[7] [varchar] (100) NULL,
[8] [varchar] (100) NULL,
[9] [varchar] (100) NULL,
[10] [varchar] (100) NULL,
[11] [varchar] (100) NULL
) ON [PRIMARY]
bulk INSERT #<table> FROM 'N:\<table>.txt'
with
(FIRSTROW=2,KEEPNULLS,CODEPAGE=1252,FIELDTERMINATOR='\t'
INSERT
INTO <table>
SELECT
* FROM #<table>
and it works! Let me also know if you find any other way around.
regards
Anatoli

Create target table using ODI model

Hi all,
I am new to ODI. I am trying export RDBMS table to RDBMS table from source to target.
whether we need to create target table structure in trg schema or we can create using obi trg model by selecting new datastore.
In owb while loading target tables are created and data will be loaded.
Pls help me regarding this.
thanks in advance.

Hi
You can create it in both ways.if you create datastore by using ODI you must select create target table option in flow while loading to target.

Creating fact Table in ODI

I just started working in ODI sometime back.
But getting problem while creating a fact table.
In datstore i am creating foreign keys(i.e Reference Key) for the fact table which have respective parent table and primary key.
but after executing the interface foreign key is not being created in the database.
Can anyone solve my problem for creating foreign key in fact table?
thanks
Gourisankar
Edited by: user10220907 on Oct 15, 2008 9:31 PM

Hi
My target Dimension:T_Comapany where Comp_SKEY is a Surrogate key which is mapped to a sequence.
My Fact Table :T_Fact_Sales where Company_Key is a column
My requirement is to map the T_Comapany.Comp_SKEY(Surrogate Key) to T_Fact_Sales.Company_Key(Foreign Key)
There are some other measures which i am mapping them in interface.
Can anyone explain the procedure how to map Surrogate KEY of a dimension table to fact table???
Thanks in advance
regards
Gourisankar
Edited by: user10220907 on Oct 29, 2008 10:06 PM

How to export the alias (not the default alias table) using ODI?

I met a problem.I set two alias tables in the outline of my essbase database.One of course is the default alias table.And the other i set the name conAlias.
I want to export the members and the alias of conAlias(not the default). I tried this using ODI (LKM Hyperion Essbase MetaData to SQL) ,but only the default alias can be exported.so i want know what can i do.

Hi Dileep,
In your query you are not specified whether the SUM of entire internal table SALARY or break up SALARY.
If you want just the SUM of the entire internal table SALARY.
Try this code.
begin of itab occurs 0,
name(10),
salary type i,
end of itab.
itab-name = 'ABC'. itab-salary = 25000.
append itab.
itab-name = 'CDF'. itab-salary = 50000.
append itab.
itab-name = 'FGH'. itab-salary = 30000.
append itab.
itab-name = 'LMN'. itab-salary = 35000.
append itab.
itab-name = 'QPR'. itab-salary = 40000.
append itab.
loop at itab.
at last.                " Note the control statement used here
    sum.
    write: 'The total salary is',itab-salary.
endat.
endloop.
Regards,
Smart

How to purge tables using odi ???

hi,
I want to purge the Data in target table.my Data Policy is to only retain the only 90 days. I have to keep only 90 days data. How can i do this in ODI. I have only one DATE column.
Thanks,
Regards,
AMSII

If your existing date field can be used to identify the records to be purged, then you could simply create a procedure in ODI along the lines of
delete from <%=odiRef.getSchemaName( )%>.*your_table* where your_date_field < (sysdate - 90)
This is the simplest way, but be wary of your indexes on the table that they don't get too fragmented. You could also investigate using a daily partition startegy on the table which would enable you to drop partitions older than 90 days which would be much faster.

Regarding I$ table in ODI...

Similar Messages

Maybe you are looking for