Wednesday, 23 July 2014

ODI-15068: Unknown flexfield code.

ODI-15068: Unknown flexfield code.


Solution:

Check your Flex Field Short Code in SECURITY where you have defined flexfileds.

We need to consider Flex field Code or ID (Internal ID).

ODI Errors - ORA-02019 connection description for remote database not found

ORA-02019 connection description for remote database not found
You use a KM using non existing DBLinks. Check the KM options and pre-requisites.

ODI-17517: Error during task interpretation.

 ODI-17517: Error during task interpretation.


java.lang.Exception: The application script threw an exception: com.sunopsis.tools.core.exception.SnpsSimpleMessageException: Exception getObjectName("L", "FACT_CUR", "LOG_ORACLE_DATABASE_PERO", "ESSBASE_CONTEXT", "D") : SnpPschemaCont.getObjectByIdentSnpPschemaCont does not exist BSF info: Load data into essbase at line: 0 column: columnNo

This is common error while executing your interfaces or procedures Selected CONTEXT not mapped with Correct Physical Schema and Logical Schema. 

Solution:

Check your Context have assigned both Physical & Logical schemas mappings.

It should not be empty it should be assigned both logical and physical schemas.

ODI Error - ORA-12154 TNS:could not resolve service name

ORA-12154 TNS:could not resolve service name
It is an Common Error if your Database Invalid Service Name  or Database Service is Not available.

Solution:
Check your Database TNS names and  Database Host , Port Number ,  Service Name.
Or If you are using DBLink check the DBLink configuration details.

ODI Error - ORA-00600 internal error code

ORA-00600 internal error code
Internal error of the Oracle database. May be caused by a driver incompatibility.

Solution:

Check your Database Driver and Supporting Versions.


ODI Error - ORA-02287 : Sequence not allowed here

ORA-02287 : Sequence not allowed here
While Using  Native Sequences in Staging we will get this type of errors.

Solution: 

Native Sequences always Using on TARGET,  Don't Use in Staging.
 


ODI Error - ORA-01461 : Can Bind long Value into LONG Column

ORA-01461     : Can Bind long Value into LONG Column

This issue occurs while loading data from Source technology to target technology.

E.g. while loading data from file to oracle database table. Reason for the error is while defining the File data store , by mistake we have not specify the correct record separator which lead ODI to read whole row as one field and throws this error.

So to resolve this issue, check you have given the correct record separator.