ODI ERRORS

ODI variables and java.lang.exception : unresolved ODI errors

Hi Guru,


Some times we may encounter the error message


java.lang.exception: Unresolved variable






Then you have to enclose the ODI substitution variable instruction with quotes.


For example,


'#Counter'


And also you should not use bind variables in certain SQL statements like 


Creation of views in oracle


Thanks Guru
Ram kumar Lanke

String index out of range-ODI parsing Rules

Hi Guru, 


Some times we we will get an error message when we execute the following
1. an ODI procedure or
2. knowledge module command or 
3. ODI API
4. ODI tool
5. ODI OS command


The error message is following:


java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(Unknown Source) 


Because the ODI parser is unable to parse the command we will face this problem.


The parser is unable to detect the variable and the bind type in the code




For example,


#Variable and :Variable




Therefore when using any of the following it is necessary to keep in mind the parsing of elements:


1. an ODI procedure or
2. knowledge module command or 
3. ODI API
4. ODI tool
5. ODI OS command


The ODI parsing rules are 


1. use the follwoing style of comment


---/* your comment line here */--




2. The quotes open on the line must be closed on the same line




Thanks Guru


Ram kumar Lanke

An object will be in an un identified state

Hi Guru,




We may encounter some times the following error message which is randomly displayed


Error:


" An object will be in an un identified state "


Because it is in the state not found in the database and update is currently being performed on it 


For example, when refreshing an ODI variable, running a scenario...


Such a problem has been attributed to the odi log related table spaces being full.


Solution:


Increase the size of the appropriate tablespaces containing the odi work repositories.


Purge the log tables in ODI operator log 




Thanks Guru
Ram kumar Lanke

SATURDAY, 7 MAY 2011

Tips for preventing errors while developing interfaces

Hi Guru's,
Hope you are fine and doing well.
Today let us discuss some important tips for preventing errors while developing interfaces.

1. Always use the expression editor
2. Before executing the interface review them
3. Always use the error button on the interfaces
4. Always check the syntax of mappings, joins, filters
5. If possible test the joins and filters from the diagram
6. Unless you know the impact of the change, do not change the execution location of mappings
7. Always use static control and flow control for data quality

Thanks Guru's
Ram Kumar Lanke

Common errors while developing interfaces

Hi Guru's,


Let us know the common errors we get after executing the interfaces

1. Syntax error in mapping :Errors like

• Syntax error in join condition
• Syntax error in filter condition
• Obvious error appears in a SELECT/INSERT or WHERE clause
• Errors like Column does not exist
• Syntax error

2. Incorrect execution location for mapping: Errors Like

• Incorrect execution location for join condition
• Incorrect execution location for filter condition
• A valid clause cannot be executed
• A clause located at the wrong location (source/target)

3. Incorrect execution context or incoorect agent chosen: Erros like

• Data servers unreachable
• Tables/files/resources does not exist
• Table not found

4. Incorrect knowledge module chosen: Errors like 

• Irrelevant results

Note: java exceptions are not always ODI errors. In many cases , the error actually comes from a database server. It may be as simple as a violation of an integrity constarint, caused by duplicate errors.



Thanks Guru's
Ram Kumar Lanke 

FRIDAY, 6 MAY 2011

Fixing the errors by trouble shooting a session

Hi Guru's,


Today i am going to discuss about how to troubleshoot the sessions and fixing errors in ODI.


It is obvious that while we develop our ODI objects we may get errors.


I am going to give you some general steps to debug errors.

• Open the operator, find the session in error. Also find the step in Error state. And finally find the task in error.
• Then double click the task and click on description tab and click on code to look at the generated code by the ODI.This code will be usually in SQL for interfaces. And it is completely dependent on the knowledge modules which you used int the interface.
• Fix the errors in the code. This may be a complex task if you dont have solid understanding how the ODI works with the relevant technology.
• After fixing the errors clik apply and save. Refresh the session. Check error has been resolved or not. If the error has not been resolved try again the same method to resolve it.
• When you have fixed the error in the generated code, you should apply the same changes to your object (interface, procedure,package etc). And restart the session execution.
• Otherwise it will use the old code to generate the code.

Thanks Guru's

Ram Kumar Lanke