odi-20730: There are critical issues still outstanding, please fix all critical issues.

odi-20730: There are critical issues still outstanding, please fix all critical issues.

Solution:

This is an common issue with if are using smart import. While using smart import we need to select action as
"Merge" or "Overwrite" or "Ignore" . It will throw this error if objects are already exits in repository.

ODI-26163: Access Denied

ODI-26163: Access Denied

 A connection to the repository could not be established because of insufficient user privilege.

Solution: Ensure the ODI user has sufficient privilege to connect to the specified repository.

ODI-26168: Client requires a repository with version 0 but the repository version found is 1

ODI-26168: Client requires a repository with version {0} but the repository version found is {1}


It is an issue with Repository Version miss-match between two work repositories.

Please check your Repository version.

ODI-26170: JDBC url is mandatory.

ODI-26170: JDBC url is mandatory.


JDBC Url was missing in Topology=>Physical Data Server.

Please goto your Physical technologies=>Data Server=> JDBC Tab=> Provide JDBC User details like  HOST :  PORT NO :  SID (Service Name)

ODI-26174: Database connection is not available.

ODI-26174: Database connection is not available.


It is an issue with Source / Target Database was Down or Not available.  Check your Database
Connection and TNS Details.

ODI-26177: ODI-26177: Unable to connect to the DBA user.

ODI-26177: ODI-26177: Unable to connect to the DBA user.


Check Your DBA Privileged user Credentials.  It is common error for Invalid User name and Password.

ODI-26179: ODI-26179: Invalid Date Format

ODI-26179: ODI-26179: Invalid Date Format


Invalid Date Format In Filter Condition or Mappings.

Solution:

Check your Filter/Mapping expression Datatype and if it is not DATE data type using convert function to convert DATE.

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.getObjectByIdent :  SnpPschemaCont 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.

ODI Error - ORA-01017: invalid username/password; logon denied

ORA-01017: invalid username/password; logon denied

While Connecting Physical Data Server we will get this error due to invalid user name and password.

Goto=>Topology=>Physical Architecture=>Physical Technologies=>Dataservers=>  Test your Data Server 

Credentials.

ODI Error - ORA-01790 expression must have same datatype as corresponding expression

ORA-01790 expression must have same datatype as corresponding expression

If you are trying to connect two different values that can not be implicitly converted (in a mapping, a join...). Use the explicit conversion functions on these values.

ODI Errors - ORA-00972 Identifier is too Long

ORA-00972 Identifier is too Long

Oracle Database Object Names Max it will accept 30 Characters Only.  So We need consider this while

Creating  $ temporary tables at staging level.   If you are hard-coding any value at Physical Schema level

like  I$_STG or  I$_SESSION_NO it should not exceed more than 30 characters.

ODI Errors - ORA-00903 invalid table name

ORA-00903 invalid table name

The table used (source or target) does not exist in the Oracle schema. Check the mapping logical/physical schema for the context, and check that the table physically exists on the schema accessed for this context.

ODI errors ORA-00904 invalid column name

ORA-00904 invalid column name

1) Keying error in a mapping/join/filter. A string which is not a column name is interpreted as a column name, or a column name is misspelled.

 2) This error may also appear when accessing an error table associated to a datastore with a recently modified structure. It is necessary to impact in the error table the modification, or drop the error tables and let Oracle Data Integrator recreate it in the next execution.

Solution:

1) Check the Column names in Filter or Join Condition Editor, It should not contain column name with "".

2) Update E$table using CKM Options like Drop temporary table is True or Update Error Table is True.

ODI 12.1.3 New For Creating Directly Combined Model and Topology Objects in Wizard option

ODI 12.1.3 New For Creating Directly Combined  Model and Topology Objects in Wizard option.