ODL Messages

Explanation:	You entered braces ( { } ) in a Source Qualifier join override or extract override without using Informatica join syntax within the braces.
User Response:	Either remove the braces and use database-specific join syntax or use Informatica join syntax within the braces.

ODL_26002 Informatica Outer Join syntax error.

Explanation:	The Integration Service found an error in the outer join syntax in the Source Qualifier transformation.
User Response:	Correct the error before running the session again. Look for related messages in the session log.

ODL_26003 No OUTER keyword found after LEFT keyword.

Explanation:	You omitted the OUTER keyword from the join syntax for a left outer join.
User Response:	Correct the join syntax in the Source Qualifier. To create a left outer join, use the keywords LEFT OUTER JOIN.

ODL_26004 No JOIN keyword found after OUTER keyword.

Explanation:	You omitted the JOIN keyword from the syntax for an outer join.
User Response:	Correct the join syntax in the Source Qualifier.

ODL_26005 No OUTER keyword found after RIGHT keyword.

Explanation:	You omitted the OUTER keyword from the join syntax for a right outer join.
User Response:	Correct the join syntax in the Source Qualifier. To create a right outer join, use the keywords RIGHT OUTER JOIN.

ODL_26006 No JOIN keyword found after INNER keyword.

Explanation:	You omitted the JOIN keyword from the syntax for an inner join.
User Response:	Correct the join syntax in the Source Qualifier. To create an inner join, use the keywords INNER JOIN.

ODL_26007 No LEFT or RIGHT keyword found before OUTER keyword.

Explanation:	You omitted the LEFT or RIGHT keyword from the join syntax for an outer join.
User Response:	Correct the join syntax in the Source Qualifier. To create a left outer join, use the keywords LEFT OUTER JOIN. To create a right outer join, use the keywords RIGHT OUTER JOIN.

ODL_26008 More than one RIGHT OUTER JOINs are not supported.

Explanation:	You combined two right outer joins in the same join syntax. Use only one right outer join in a single Source Qualifier.
User Response:	Correct the join syntax in the Source Qualifier. If appropriate, change the right outer joins to left outer joins. You can use multiple left outer joins in a single Source Qualifier.

ODL_26009 No comma (,) found between table names.

Explanation:	You omitted a comma between table names in the FROM clause of the outer join syntax.
User Response:	Correct the join syntax in the Source Qualifier. Place commas between table names in the FROM clause.

ODL_26012 Internal error in function <function name>. Database not in correct state.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

ODL_26023 Deadlock error encountered.

Explanation:	The database has deadlocked.
User Response:	Contact the database administrator.

ODL_26025 Error getting sort order from the database.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

ODL_26026 Driver does not support the data type.

Explanation:	You selected an unsupported datatype for the database.
User Response:	Select a datatype that is supported by the database.

ODL_26028 File <file name> is either missing or corrupt.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

ODL_26035 ODBC call to SQLError failed.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

ODL_26036 ODBC call <ODBC call> failed.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

ODL_26045 Error allocating DB2 environment handle.

Explanation:	DB2 database error.
User Response:	Verify the DB2 environment is configured correctly. Also, contact the database administrator.

ODL_26046 Error loading bulk API library.

Explanation:	DB2 database error.
User Response:	Verify the DB2 environment is configured correctly. Also, contact the database administrator.

ODL_26047 Could not allocate a bulk API instance.

Explanation:	DB2 database error.
User Response:	Verify the DB2 environment is configured correctly. Also, contact the database administrator.

ODL_26060 Fatal Error: Encountered Teradata error that aborts current transaction.

Explanation:	The Integration Service encountered one of the following Teradata errors that aborted the current transaction: •2801 Duplicate unique prime key error. •2802 Duplicate row error. •2803 Secondary index uniqueness violation. •3604 Cannot place a null value in a NOT NULL field.
User Response:	Remove the row that caused the Teradata error and restart the session.

ODL_26069 Failed to create and initialize SQL OLE DB instance. Reason <error code>: <system error>.

Explanation:	The Repository Service or Integration Service failed to connect to the Microsoft SQL Server database because one or more Microsoft SQL Server API function calls failed.
User Response:	Verify that all specified Microsoft SQL Server classes are properly registered in the registry. Then re-register oledb32.dll. [Regsvr32 \Program Files\Common Files\System\Ole DB\oledb32.dll]. Use the returned error code and error message to determine the cause of this error.

ODL_26071 Graphic/vargraphic partition key types are supported only on servers with UNICODE data movement enabled.

Explanation:	You ran a session using database partitioning on an Integration Service running in ASCII mode and the IBM DB2 target table uses a partitioning key with either a Graphic or Vargraphic column.
User Response:	Run the session on an Integration Service in Unicode mode.

ODL_26095 BigInt partition key type can be used only in high-precision mode.

Explanation:	A session that loads data to an IBM DB2 target is configured for database partitioning and the target table partition key is a Bigint column, but high precision is not enabled for the session.
User Response:	Enable high precision for the session, or select a target table partition key that is not a Bigint column.

ODL_26111 High availability license is absent. Resilience timeout specified for database connection <connection name> is ignored.

Explanation:	The connection retry period is configured in the database connection object, but you do not have the high availability option. The retry period is ignored.
User Response:	None.

ODL_26113 Number of Bulk mode parameters=<number of parameters> exceeded the number of parameters supported <number of parameters>.

Explanation:	The number of parameters specified for the DB2BulkModeParameters custom property is greater than four.
User Response:	Verify that the number of parameters specified in the DB2BulkModeParameters custom property is less than or equal to four.

ODL_26114 <Value> is not a valid parameter for the DB2BulkModeParameters custom property.

User Response:

Verify that the DB2BulkModeParameters custom property uses one or more of the following valid parameters: DATABUFFER, CPUPARALLELISM, WARNINGCOUNT, or FILETYPEMODE.

ODL_26115 <Value> is not a valid key:value pair for the DB2BulkModeParameters custom property.

Explanation:	The value of DATABUFFER, CPUPARALLELISM or WARNINGCOUNT was not specified correctly.
User Response:	Verify that the value of DATABUFFER, CPUPARALLELISM or WARNINGCOUNT is an integer.

ODL_26116 The FILETYPEMOD parameter requires single quotes at the start and end of the string value.

User Response:

Verify that single quotes appear at the start and end of the string value for the FILETYPEMOD parameter. For example, enter FILETYPEMOD:‘string’.

ODL_26138 The PowerCenter Integration Service could not find the run-time OSGi bundle for the adapter [{0}] for the operating system [{1}]. Copy the adapter run-time OSGi bundle and verify that you have set the correct entry for the API in the plugin.xml file.

User Response:

Ensure that you copied the adapter run-time OSGi bundle at INFA_HOME\plugins\dynamic\AdapterName\runtime. Also verify that you have set the correct entry for the API in the plugin.xml file for the operating system you are running adapter on.

ODL Messages

ODL_26001 Informatica Outer Join syntax not found.

ODL_26002 Informatica Outer Join syntax error.

ODL_26003 No OUTER keyword found after LEFT keyword.

ODL_26004 No JOIN keyword found after OUTER keyword.

ODL_26005 No OUTER keyword found after RIGHT keyword.

ODL_26006 No JOIN keyword found after INNER keyword.

ODL_26007 No LEFT or RIGHT keyword found before OUTER keyword.

ODL_26008 More than one RIGHT OUTER JOINs are not supported.

ODL_26009 No comma (,) found between table names.

ODL_26012 Internal error in function <function name>. Database not in correct state.

ODL_26023 Deadlock error encountered.

ODL_26025 Error getting sort order from the database.

ODL_26026 Driver does not support the data type.

ODL_26028 File <file name> is either missing or corrupt.

ODL_26035 ODBC call to SQLError failed.

ODL_26036 ODBC call <ODBC call> failed.

ODL_26045 Error allocating DB2 environment handle.

ODL_26046 Error loading bulk API library.

ODL_26047 Could not allocate a bulk API instance.

ODL_26060 Fatal Error: Encountered Teradata error that aborts current transaction.

ODL_26069 Failed to create and initialize SQL OLE DB instance. Reason <error code>: <system error>.

ODL_26071 Graphic/vargraphic partition key types are supported only on servers with UNICODE data movement enabled.

ODL_26095 BigInt partition key type can be used only in high-precision mode.

ODL_26111 High availability license is absent. Resilience timeout specified for database connection <connection name> is ignored.

ODL_26113 Number of Bulk mode parameters=<number of parameters> exceeded the number of parameters supported <number of parameters>.

ODL_26114 <Value> is not a valid parameter for the DB2BulkModeParameters custom property.

ODL_26115 <Value> is not a valid key:value pair for the DB2BulkModeParameters custom property.

ODL_26116 The FILETYPEMOD parameter requires single quotes at the start and end of the string value.

ODL_26138 The PowerCenter Integration Service could not find the run-time OSGi bundle for the adapter [{0}] for the operating system [{1}]. Copy the adapter run-time OSGi bundle and verify that you have set the correct entry for the API in the plugin.xml file.