LDBG Messages

Explanation:	During a user-defined commit session, the Data Transformation Manager ran out of buffer pool data blocks, which caused the session to fail.
User Response:	In the session properties, increase the DTM buffer block size. Modify the Transaction Control expression or the Custom transformation procedure code so that the transformation issues commits more frequently.

LDBG_21035 Datablock write-lock error. offset <offset value>, reason [No space left on device].

Explanation:	The Integration Service could not write data to the disk because there is not enough space.
User Response:	Increase the amount of free space on the Integration Service system disk. Verify that the operating system does not limit the amount of disk space for the user who starts the Integration Service.
Explanation:	This message follows CMN_1107. The Integration Service could not write to a Joiner index or data cache file because there is not enough space on the disk.
User Response:	Increase the Joiner index and data cache sizes. If possible, increase the index and data cache sizes to hold all of the data.

LDBG_21149 ERROR determining truncate table order - could not create constraint load dependencies for target.

Explanation:	You are attempting to truncate target tables, but the Integration Service is unable to determine dependencies between target tables, possibly due to errors such as circular key relationships.
User Response:	Ensure the validity of dependencies between target tables.

LDBG_21178 ERROR: Self-referential constraint in target.

Explanation:	You have set the session for constraint-based loading, but the Integration Service is unable to determine dependencies between target tables, possibly due to errors such as circular key relationships.
User Response:	Ensure the validity of dependencies between target tables.

LDBG_21409 Target <target name> Warning: Primary key table for Foreign key <foreign key port name> is not from the same active source or transaction generator. This constraint will not be enforced; as a result, the session may hang because of potential deadlock.

Explanation:	The mapping writes to target tables that have a primary key-foreign key relationship, but the targets receive data from different transaction generators, such as a Transaction Control transformation, or active sources. The Integration Service cannot enforce the primary key-foreign key relationship. The session might hang depending on the source data.
User Response:	If the session hangs, design the mapping to enforce constraint-based loading. Or, remove the primary key-foreign key relationship between the targets in the target database.

LDBG_21511 TE: Fatal Transformation Error.

Explanation:	The Integration Service encountered a fatal row error and failed the session.
User Response:	See the additional error messages for more information.

LDBG_21604 Data block read-lock error, offset <number>, reason: <reason>.

Explanation:	Error occurred trying to read from the joiner cache.
User Response:	Truncate the targets and run the session again.

LDBG_21605 Cannot open files in the directory <directory name>.

Explanation:	Cannot open files in the joiner cache directory.
User Response:	Check file system permission and free space in the cache directory.

LDBG_21633 For the dynamic lookup cache for <Lookup transformation>, an input row has NULL value in condition fields. This row will not be used for update of the lookup cache.

Explanation:	The Lookup transformation in the mapping uses a dynamic lookup cache, and the source row contains a null value in a column used in the lookup condition.
User Response:	None. When the row exists in the lookup cache, the Integration Service does not update the row in the cache or target table.

LDBG_21668 Error: The Informatica server license does not allow more than one database license to be used at a time.

Explanation:	The Integration Service configuration contains more than one database license.
User Response:	The Informatica license does not allow you to use more than one database license at a time. Configure the Integration Service with only one database license.