Message Reference > W Message Codes > WRT Messages
  

WRT Messages

WRT_8000 Error processing table.

Explanation:
The database failed to write to a target table.
User Response:
Check the session log for related error messages.

WRT_8001 Error connecting to database.

Explanation:
The Integration Service failed to connect to the target database. You may have logged in incorrectly.
User Response:
Log in with correct information. User names and passwords may be case sensitive.

WRT_8004 Writer initialization failed <error message>. Writer terminating.

Explanation:
The Integration Service failed to connect to the target database. You may be logged in incorrectly.
User Response:
Log in with correct information. User names and passwords may be case sensitive.
Explanation:
The Integration Service does not have access to the one of the error/output/session log files.
User Response:
Ask the PowerCenter administrator to review write privileges for the user running the Integration Service.
Explanation:
The mapping includes target tables that do not exist or have not been appropriately updated in the target database.
User Response:
Check the target database for the appropriate tables. If necessary, create or update the tables.

WRT_8012 Writer Run: Data out of order for targets, Terminating.

Explanation:
A violation of a load-order criteria specified in a mapping occurred. This is an internal error.
User Response:
Contact Informatica Global Customer Support.

WRT_8019 No column marked as primary key for table <table name>.

Explanation:
The Integration Service could not locate the primary key for the specified target table, so it could not perform the delete operation.
User Response:
In the Target Designer, specify a primary key in the target table definition, then generate and execute the SQL.

WRT_8020 No column marked as primary key for table <table name>.

Explanation:
The Integration Service could not locate the primary key for the specified target table, so it could not perform the update operation.
User Response:
In the Target Designer, specify a primary key in the target table definition, then generate and execute the SQL.

WRT_8023 Error truncating target table <target name>. <database error string>.

Explanation:
Could not truncate the target table.
User Response:
Look at the database error string for more information.

WRT_8028 Error <error number> forking <loader type> external loader process for target <target name>.

Explanation:
The external loader process could not be forked.
User Response:
Look up the error code in errno.h on UNIX or winerror.h on Windows.

WRT_8031 Error <error number> unlinking named pipe <output file name>.

Explanation:
The Integration Service on UNIX could not unlink a named pipe used for external loading.
User Response:
Look up the error code in errno.h.

WRT_8032 External loader error.

Explanation:
An error occurred related to the external loader. See additional information logged with this error. Known additional messages:
Error getting [Oracle or Sybase] loader information.
Error executing external loader process.
Error generating control file.
Error opening the control file.
User Response:
Make sure the loader information is entered correctly.
In Oracle, verify that the loader executable name entered is correct, and that the executable directory is in the path. Make sure the user name, password and connect string are correct.
Make sure all fields contain a value when setting up an external loader connection.
Check the permissions on the directory where the output file is to be generated.

WRT_8046 Error <Windows system error number> checking for completion of external loader <handle=process ID>.

Explanation:
The Windows system encountered an error while attempting to check for external loader completion.
User Response:
Look up the Windows system error code and/or check the Windows system log.

WRT_8047 Error: External loader process <process ID> exited with error <exit loader error number>.

Explanation:
The external loader process exited with an error.
User Response:
Look up the error code in the database external loader documentation.

WRT_8048 Error <Windows system error number> retrieving the termination status for completed external loader [handle=<process ID>].

Explanation:
The Windows system encountered an error while attempting to retrieve the exit code for the external loader.
User Response:
Look up the Windows system error code and/or check the Windows system log.

WRT_8049 Error: External loader process <process ID> exited due to receipt of signal <UNIX signal number>.

Explanation:
External loader on UNIX exited due to receipt of a UNIX signal.
User Response:
Look up the UNIX signal number in signal.h, which is in /usr/include/sys/signal.h.

WRT_8053 Warning! Error executing pre-load stored procedures. Session <session name> user name <user name> Error <database error message>.

Explanation:
You ran a session with a pre-load stored procedure that failed to execute.
User Response:
Contact the database administrator.

WRT_8058 Error <system error number> opening session bad (reject) file <bad file name>.

Explanation:
During the initialization of a session, the Integration Service failed to open the reject file specified due to an operating system error.
User Response:
For Integration Service on Windows, see Windows help and look up the specified system error number.
For Integration Service on UNIX, locate the error in the /usr/include/sys/errno.h file. See the UNIX Documentation for explanation of the error.

WRT_8059 Writer initialization failed [Failed to Initialize OuputFile.] Writer terminating.

Explanation:
During the initialization of a session with a flat file target, the Integration Service failed to initialize the output file.
User Response:
Contact the system administrator.

WRT_8060 Writer initialization failed [Failed to get external loader information]. Writer terminating.

Explanation:
Internal error. You may have repository inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8062 Writer initialization failed [Failed to generate external loader control file]. Writer terminating.

Explanation:
The session failed during generation of an external loader control file.
User Response:
Check preceding error messages to see the cause for the error.

WRT_8063 Writer initialization failed [Failed to start external loader]. Writer terminating.

Explanation:
The external loader executable might not exist or you might not have permission to execute the external loader program.
User Response:
Verify that the external loader executable exists and that you have permission to execute it. Contact the system administrator if you do not have the correct permissions.
Explanation:
The operating system may be low on resources.
User Response:
Contact the system administrator.

WRT_8064 Error <system error number> opening session output file <output file name>.

Explanation:
During the initialization of a session, the Integration Service failed to open the output file specified due to an operating system error.
User Response:
For Integration Service on Windows, see Windows help and look up the specified system error number.
For Integration Service on UNIX, locate the error in the /usr/include/sys/errno.h file. See the UNIX documentation for explanation of the error.

WRT_8065 Writer initialization failed [Failed to Initialize IndicatorFile]. Writer terminating.

Explanation:
During the initialization of a session with a flat file target, the Integration Service failed to initialize the indicator file. The directory for the indicator file does not exist or the Informatica Services account or the operating system profile does not have write permission on the directory.
User Response:
Verify that the directory for the indicator file exists and grant write permission on the directory to the Informatica Services account or the operating system user in the operating system profile.
Explanation:
The operating system is low on resources.
User Response:
Contact the system administrator.

WRT_8066 Error <system error message> opening session log file <log file name>.

Explanation:
Operating system error.
User Response:
Contact the system administrator.

WRT_8067 Writer initialization failed [NTTrustedConn() failed]. Writer terminating.

Explanation:
Internal error.
User Response:
Contact the system administrator.

WRT_8068 Writer initialization failed. Writer terminating.

Explanation:
Internal error.
User Response:
Check preceding error messages to see the cause for the error.

WRT_8070 Writer initialization failed <Internal error:no mapping [1]>. Writer terminating.

Explanation:
Internal error. The repository may have inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8071 Writer initialization failed. [Total no. of load targets from all pipelines <load targets> do not match with the no. of load targets in the mapping <mapping name>.] Writer terminating.

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

WRT_8072 Error resolving bad file name for target <target name>.

Explanation:
Internal error. The repository may have inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8073 Error getting output file name for target <target name>.

Explanation:
Internal error. The repository may have inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8074 Writer initialization failed [Internal Error]. Writer terminating.

Explanation:
Internal error.
User Response:
Check preceding error messages to see the cause for the error.

WRT_8075 Writer initialization failed [Error creating truncate table order]. Writer terminating.

Explanation:
Internal error. The repository may have inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8076 Writer run terminated. [Commit Error].

Explanation:
Database error.
User Response:
Contact the database administrator.

WRT_8077 Writer run terminated. [Error in executing pre-load stored procedures.]

Explanation:
Internal error.
User Response:
Check preceding error messages to see the cause for the error.

WRT_8079 Writer run terminated.

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

WRT_8080 Writer run terminated. [Error loading data and error threshold reached: no data committed].

Explanation:
The Integration Service has reached the error threshold configured in the session properties.
User Response:
Eliminate the errors in the data.
Set the error threshold to zero.

WRT_8081 Writer run terminated. Error in loading data to target table <target instance name>.

Explanation:
Internal error.
User Response:
Check preceding error messages to see the cause for the error.

WRT_8082 Writer run terminated. [Errors encountered.]

Explanation:
Internal error.
User Response:
Check preceding error messages to see the cause for the error.

WRT_8085 Writer run terminated. [Internal Error].

Explanation:
Internal error.
User Response:
Check preceding error messages to see the cause for the error. Also, contact Informatica Global Customer Support.

WRT_8086 Writer run terminated. [Error in executing post-load stored procedures.]

Explanation:
Database error.
User Response:
Check preceding error messages to see the cause for the error. Also, contact the database administrator.

WRT_8088 Writer run terminated. [External loader error.]

Explanation:
Internal error.
User Response:
For a more specific error message, see the external loader log.

WRT_8091 Error truncating target table <table name>. Error forming query.

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

WRT_8092 Error truncating target table <table name>. Error preparing truncate target table query: <table query>.

Explanation:
Database error.
User Response:
Contact the database administrator.

WRT_8095 Error <system error number> forking isql external loader process for target <target name>.

Explanation:
You might be low on system resources.
User Response:
Contact the system administrator.
Explanation:
You might have encountered a database configuration error.
User Response:
Contact the database administrator.

WRT_8096 External loader error. Error getting Oracle loader information.

Explanation:
Internal error. You may have repository inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8097 External loader error. Unsupported external loader type.

Explanation:
Internal error. You may have repository inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8098 External loader error. Error executing external loader process: [No such file or directory] errno = [2].

Explanation:
The Integration Service could not run the external loader because the external loader is not included in the system path.
User Response:
Edit the system path to include the external loader executable.

WRT_8100 External loader error. Error getting Sybase loader information.

Explanation:
Internal error. You may have repository inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8109 Compare Targets for InfoSource.

Explanation:
The metadata in SAP NetWeaver BI has changed since it was imported. This message is followed by specific information.
User Response:
Reimport the BW target definition.

WRT_8110 BW Statement Init.

Explanation:
The Integration Service failed to initialize the InfoSource.
User Response:
Check that the Integration Service meets the minimum system requirements.

WRT_8111 SAPSendDone.

Explanation:
The session failed to delete a line from an SAP internal table.
User Response:
Reschedule the SAP NetWeaver BI workflow.

WRT_8116 ERROR: Target table <target table name> has no keys specified. Row # <row ID> in bad file.

Explanation:
You attempted to perform an UPDATE or a DELETE. These commands require a primary key be defined on the target table.
User Response:
Go to the target definition and define a primary key.
Do not use UPDATE or DELETE on the target table.

WRT_8117 ERROR: Target table <table name> does not allow INSERT. Row # <row ID> in bad file.

Explanation:
You attempted to INSERT rows into the target table. However, you might not have been granted rights to INSERT into the specified table.
User Response:
Contact the database administrator.

WRT_8118 ERROR: Target table <table name> does not allow UPDATE. Row # <row ID> in bad file.

Explanation:
You attempted to UPDATE rows into the target table. However, you might not have been granted rights to UPDATE into the specified table.
User Response:
Contact the database administrator.

WRT_8119 ERROR: Target table <table name> does not allow DELETE. Row # <row ID> in bad file.

Explanation:
You attempted to DELETE rows from the target table. However, you might not have the rights to DELETE from the specified table.
User Response:
Contact the database administrator.

WRT_8120 ERROR: Invalid row type for target table <table name>. Row # <row ID> in bad file.

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

WRT_8123 Failed to prepare target table load. Database error: <database error number>.

Explanation:
Database error.
User Response:
Contact the database administrator.

WRT_8132 Error executing truncate target table query.

Explanation:
Database error.
User Response:
Contact the database administrator.

WRT_8136 Error parsing stored procedure call text.

Explanation:
The Integration Service was unable to parse stored procedure call text.
User Response:
Revise the stored procedure call text.

WRT_8150 Invalid code page for output file <file name>.

Explanation:
The code page you specified for target is not valid.
User Response:
Specify a valid code page for the target.

WRT_8151 Field separator character <separator> is invalid for target's code page.

Explanation:
The hexadecimal value of the character you specified as the delimiter separator for the target is not valid.
User Response:
Specify a delimiter that is valid in the target code page.

WRT_8152 NULL-character <null character> is invalid for target's code page.

Explanation:
The HEX value of the null character you specified for the target is not valid.
User Response:
Specify a null character that is valid in the target code page.

WRT_8156 Error: External loading MBCS data to Sybase IQ 11 is not supported.

Explanation:
The Integration Service does not support external loading of data in multibyte character set to Sybase IQ 11. Sybase IQ 11 does not support multibyte data.
User Response:
Switch the Sybase IQ 11 server to ASCII mode and use ASCII data.
Load the multibyte data to a database that supports Unicode.

WRT_8157 Field <field name> of the output file <file name> is not wide enough to fit at least one specified NULL character.

Explanation:
You specified a multibyte null character and the target field does not contain enough remaining bytes for one null character.
User Response:
Specify a single byte null character.
Increase the target column size in the Designer.

WRT_8171 Cannot locate CreateWrtTargetInstance function in the <library file name> shared library.

Explanation:
The DLL loaded for the specified target does not contain a function called CreateWrtTargetInstance.
User Response:
Make sure this is the correct DLL.

WRT_8172 Cannot create ASCII locale.

Explanation:
Third party library error.
User Response:
Make sure the paths to libraries and environments are set properly.

WRT_8173 Conversion from UNICODE failed - not all the characters were converted.

Explanation:
The number of characters converted from Unicode does not match the number of characters in the buffer. The number is less than the expected number.
User Response:
Contact Informatica Global Customer Support.

WRT_8174 Error while flushing the buffer to output file <output file name>. Error message is <error message>, data buffer <buffer>.

Explanation:
There was an operating system input/output error trying to output into target file.
User Response:
Check that the output file is not locked and has the correct user permissions. Make sure the system has enough disk space.

WRT_8175 Field separator string for file <file name> contains non-ASCII characters <Unicode characters>.

Explanation:
At initialization time, the Integration Service is in ASCII data movement mode, but the field separator string specified in the session for that target file contains some non-ASCII symbols.
User Response:
Change the Integration Service to UNICODE data movement mode or change the field separator string to be ASCII-only.

WRT_8176 NULL character for file <file name> is not ASCII <Unicode character>.

Explanation:
At initialization time, the Integration Service is in ASCII data movement mode, but the null character specified in the session for that target file is a non-ASCII character.
User Response:
Change the Integration Service to UNICODE data movement mode or change the null character to an ASCII character.

WRT_8178 Failed to get quote option for file <file name>.

Explanation:
Error getting options for the file from the repository.
User Response:
Save the session to reset a flag then run the session again. Or contact Informatica Global Customer Support.

WRT_8179 Unknown error occurred while trying to close output file <file name>.

Explanation:
Operating system input/output error occurred when closing the output target file.
User Response:
Check that the file is not locked, is accessible, and has the correct permissions. Check that there is sufficient disk space.

WRT_8180 Failed to generate indicator file name using <output file name>.

Explanation:
You used an unsuitable file name for automatic indicator file name generation.
User Response:
Contact Informatica Global Customer Support. The following are valid names (“/” is treated the same way as “\”). The Integration Service appends the following file names with the extension .ind:
  • •FNAME
  • •.FNAME
  • •FNAME
  • •./FNAME
  • •DIR/FNAME
    • The Integration Service replaces the following file names that have the file extension (.ext) with .ind:
  • •FNAME.EXT
  • •.FNAME.EXT
  • •/FNAME.EXT
  • •./FNAME.EXT
  • •DIR/FNAME.EXT
    • DIR.DIREXT/FNAME is an invalid input name. You cannot use a period (.) in the directory name because the Integration Service cannot process the input name.

WRT_8181 Specified locale <locale name> for the file <output file name> is not valid for NULL character <character>.

Explanation:
The null character you specified does not exist in the target code page.
User Response:
Make sure the target code page is compatible with the Integration Service code page or change the null character so that it exists in the target code page.

WRT_8183 Rollback failed for the target <target instance name>.

Explanation:
The database experienced a deadlock and the rollback failed for the specified target. The rollback segment could be too small to occur successfully.
User Response:
Check the database setup. Make sure the rollback segment is large and try the rollback again.

WRT_8184 WARNING: The output codepage specified for the target file <target file name> is not ASCII-based, whereas the Informatica Server is running in ASCII mode.

Explanation:
The Integration Service is running in ASCII data movement mode, but the code page you specified for the target is not ASCII-based.
User Response:
Change the Integration Service data movement mode to Unicode and run the session again.

WRT_8185 Error transferring data from target <target name> using FTP.

Explanation:
The Integration Service encountered an error while preparing to transfer the file using FTP.
User Response:
Verify that the FTP server is running, verify the file permissions and connection information, and run the session again.

WRT_8186 Error while finalizing load. Writer run terminated.

Explanation:
After the target finished processing, the Integration Service finalized the file for FTP and encountered an error.
User Response:
See previous message in the log for more information.

WRT_8187 Error resolving output file <file name> for target <target name>.

Explanation:
Internal error. The repository may have inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8188 Invalid MQ header for <target name> target.

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

WRT_8189 Invalid field type (MQCHAR expected) for <target name> target.

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

WRT_8197 Error opening target merge file <file name>.

Explanation:
Operating system error.
User Response:
Contact the system administrator.

WRT_8198 Error opening target file <file name> during merge target file processing.

Explanation:
Operating system error.
User Response:
Contact the system administrator.

WRT_8199 Error reading target file <file name> during merge target file processing.

Explanation:
Operating system error.
User Response:
Contact the system administrator.

WRT_8200 Error writing to target file <file name>.

Explanation:
Operating system error.
User Response:
Contact the system administrator.

WRT_8201 Error getting the merge target file name for target <target name>.

Explanation:
Internal error. The repository may have inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8203 Bulk execute failed. Re-trying.

Explanation:
Check preceding error messages to see why the execute failed. However, the Integration Service continues to execute the command, so that the data loads eventually unless other errors occur.
User Response:
Try to correct the cause of the failure. The Integration Service executes the command and as a result, the session takes longer to run. For example, if the error is caused by a deadlock, contact the database administrator to see if the database can be set up for concurrent inserts.

WRT_8204 Error: Unable to set null character.

Explanation:
You specified a character for null that is incompatible with the code page defined for the target.
User Response:
Change the null character or change the code page defined for the target.

WRT_8205 Error: Could not find table name in catalog. This session cannot run with multiple partitions.

Explanation:
Internal error. The repository may have inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WRT_8206 Error: The target table has been created with page level locking. The session can only run with multi partitions when the target table is created with row level locking.

Explanation:
You configured an Informix target table incorrectly for multiple partitions.
User Response:
Create the Informix target table with row-level locking.

WRT_8208 Error truncating target table <target table name>. The Integration Service is trying the DELETE FROM query.

Explanation:
The Integration Service was unable to run a truncate command on the database and tried to issue a delete command.
User Response:
The delete from command impacts performance. If the database supports the truncate table command and you want to improve performance, review database table privileges and key constraints.

WRT_8209 External loader error, Teradata external loader cannot take table names greater than 24 characters. The table name <table name> has <table length> characters.

Explanation:
Teradata does not support external loads for table names greater than 24 characters.
User Response:
Use a table name of less than 24 characters.

WRT_8210 External loader error, Error generating Teradata loader control file.

Explanation:
The Integration Service encountered an error generating the control file.
User Response:
Verify that the file is a fixed-width file and that the table name does not exceed 24 characters.

WRT_8211 See external loader log <loader log file name> for more details.

Explanation:
There was an error loading the table into the database using the database external loader utility. Possible errors might be that the table does not exist or there is a lock on the table.
User Response:
Check the external loader log file for details.

WRT_8212 Error: There have been too many database deadlocks. Unable to continue with the session.

Explanation:
You configured the Integration Service to end a session when the database encounters the maximum number of deadlocks you defined.
User Response:
Increase the value for deadlock retries on the Integration Service.
Contact the database administrator.

WRT_8215 External loader error. The external loader process <process ID> exited prematurely.

Explanation:
This error is related to WRT_8216. The external loader exited unexpectedly, because the named pipe broke and the session failed.
User Response:
Check the external loader log file for details.

WRT_8216 External loader error. Broken Pipe.

Explanation:
The Integration Service could not write data to the named pipe because the external loader exited unexpectedly. The external loader may exit if it runs out of disk space.
User Response:
Check the external loader log file for details, and verify that there is sufficient disk space.

WRT_8218 Error: Teradata external loader requires a primary key on table <table name> when using load mode <load mode>.

Explanation:
You did not set a primary key on the table when using load mode update, upsert, or delete.
User Response:
Set a primary key on the target table.

WRT_8219 Error: Table mismatch, target table <table name> with <number of columns> columns mismatch with physical table with <number of columns> columns.

Explanation:
The number of columns in the target table is different than the physical table.
User Response:
In the Designer, recreate the table or reload the target table from the database.

WRT_8220 Error: get deadlock when reading /writing database.

Explanation:
Database error.
User Response:
Contact the database administrator.

WRT_8226 Target Load Order Group <TLOG> is set for real-time flushing. Target based commit is switched to source based commit and target based commit interval is used as source based commit interval.

Explanation:
This is an informational message. You configured the session for real-time data extraction with target-based commits. The Integration Service will run the session with source-based commits.
User Response:
If you want to run the session in real time, you do not need to take any action.
If you want to run the session with target-based commits, remove the flush latency function from the filter condition.

WRT_8229 Database errors occurred: <database error message>.

Explanation:
The Integration Service encountered an error from the database.
User Response:
See the Informatica Knowledge Base.

WRT_8244 Error outputting row # <row number> for output file <flat file target>. The row was rejected.

Explanation:
The Integration Service encountered an error outputting the row to the flat file target, and wrote the row in the reject file. The Integration Service may have rejected the row for one of the following reasons:
  • •The target is a fixed-width file, and the field width for a datetime column is not large enough to accommodate the datetime value, including the datetime format.
  • •The target is a fixed-width file, and the field width for a numeric column is not large enough for the numeric value, including the decimal and thousand separator.
User Response:
Edit the target definition in the Designer, and verify you configure the precision and field width to accommodate the total length of the target column.

WRT_8246 Error: External loader is not supported for direct flat files. Target instance <target instance name>.

Explanation:
In the session properties, you chose an external loader connection for a target based on a flat file target definition. This might have happened if you chose an external loader connection for a target based on a relational target definition and then in the Designer, you changed the relational target definition to a flat file definition.
User Response:
In the Designer, change the flat file target definition to a relational target definition. You can only choose an external loader connection when the target is based on a relational target definition.

WRT_8247 Error: Cannot run in bulk mode for a test load for connection <target name>.

Explanation:
In the session properties, you configured the Integration Service to perform a test load and you chose bulk mode for a relational target.
User Response:
Choose Normal for the target load type. You can perform a test load for relational targets when you configure a session for normal mode. If you configure the test load session for bulk mode, the session fails.

WRT_8250 Target (test load not supported for this target type): <target name> (Instance Name: <target instance name>).

Explanation:
In the session properties, you configured the Integration Service to perform a test load, but the Integration Service does not perform a test load on some of the targets in the mapping.
User Response:
None. The Integration Service only performs a test load on relational targets.

WRT_8270 Target connection group #<group number> consists of target(s) <target name>.

Explanation:
Informational message.
User Response:
None. The Integration Service writes in the session log which targets belong to a target connection group. The target connection group number is an arbitrary number. It does not specify the order the Integration Service loads to the targets. A target connection group is a group of targets that the Integration Service uses to determine commits and loading.

WRT_8281 Error: The same character <character> is used as both field and decimal separator for the field <port name> of the target <target name>.

Explanation:
For the delimited flat file target definition, you chose the specified character as the decimal separator and as the field delimiter.
User Response:
In the session properties, choose a different delimiter for the target. Or, in the Designer, choose a different decimal separator for the target definition.

WRT_8282 Error: The same character <character> is used as both field and thousand separator for the field <port name> of the target <target name>.

Explanation:
For the delimited flat file target definition, you chose the specified character as the thousand separator and as the field delimiter.
User Response:
In the session properties, choose a different delimiter for the target. Or, in the Designer, choose a different thousand separator for the target definition.

WRT_8297 External loader process <loader process> exited with warning code <action file code>.

Explanation:
You are using an external loader warning action file. The external loader returned a non-zero warning code.
User Response:
Locate the warning code in the external loader warning action file. You can edit the warning action file to treat each warning code as a warning or as a fatal error. For details on loader warning codes, see the loader documentation.

WRT_8299 External loader error. Cannot find loader warning action file.

Explanation:
You configured the Integration Service to use an external loader warning action file. The Integration Service cannot locate the loader warning action file.
User Response:
Locate the warning action file and copy it to the location you specified for the loader warning action file when you configured the Integration Service. Verify that the name of the action file matches the name you specified when you configured the Integration Service.

WRT_8300 External loader error. Error opening loader warning action file <file name> for reading. errno = <system error code>.

Explanation:
You configured the Integration Service to use an external loader warning action file. The Integration Service cannot read the warning action file.
User Response:
Verify that the system account that started the Integration Service has read permission for the directory the loader warning action file is located in.
Explanation:
System error.
User Response:
Contact the system administrator.

WRT_8301 Error loading warning codes from external loader warning action file <file name>.

Explanation:
The Integration Service could not load the warning codes from the external loader warning action file.
User Response:
Check preceding messages to see the cause of the error.
Explanation:
The Integration Service could not load the warning codes from the external loader warning action file because you did not specify the name or location of the file when you configured the Integration Service.
User Response:
Specify a name and location for the external loader warning action file.

WRT_8302 External loader error. Error duplicating handle to stderr for DB2 EEE external loader. System error message is <system error message>. errno = <error number>.

Explanation:
System error.
User Response:
Contact the system administrator.

WRT_8303 External loader error. Error opening DB2 EEE external loader log file for writing. System error message is <system error message>. errno = <error number>.

Explanation:
System error.
User Response:
Contact the system administrator.

WRT_8304 External loader error. Error redirecting stderr to loader log file for DB2 EEE external loader. System error message is <system error message>. errno = <error number>.

Explanation:
System error.
User Response:
Contact the system administrator.

WRT_8305 External loader error. Error restoring stderr for DB2 EEE external loader. System error message is <system error message>. errno = <error number>.

Explanation:
System error.
User Response:
Contact the system administrator.

WRT_8308 Error: Failed to write metadata for target table <target instance> to the output file <target file name>.

Explanation:
You configured the Integration Service to write flat file metadata to the target file. The Integration Service could not write to the target.
User Response:
Verify the Integration Service can connect to the flat file target directory and that the disk has enough space.

WRT_8309 External loader error. The Date Format <format> is invalid. Target instance <target instance name>.

Explanation:
You entered an invalid value for the Date Format option when you configured the MultiLoad external loader.
User Response:
Edit the MultiLoad external loader connection and enter a valid value for Date Format. Restart the session.

WRT_8310 External loader error. Update is not valid for target instance <target instance name> since no primary key(s) is mapped to the target.

Explanation:
The MultiLoad or TPump external loader cannot run in update mode because you did not define a primary key for the target.
User Response:
Run the external loader in a different mode, or define a primary key for the target.

WRT_8311 External loader error. Update is not valid for target instance <target instance name> since no non-key field(s) is mapped to the target.

Explanation:
The MultiLoad or TPump external loader cannot run in update mode because you did not define any non-key columns in the target instance.
User Response:
Run the external loader in a different mode, or add a non-key column to the target.

WRT_8312 External loader error. Delete is not valid for target instance <target instance name> since no primary key(s) is mapped to the target.

Explanation:
The MultiLoad or TPump external loader cannot run in delete mode because you did not define a primary key for the target.
User Response:
Run the external loader in a different mode, or define a primary key for the target.

WRT_8313 External loader error. Upsert is not valid for target instance <target instance name> since update is not valid for the target.

Explanation:
The MultiLoad or TPump external loader cannot run in upsert mode for one of the following reasons:
  • •You did not define a primary key for the target.
  • •You did not define any non-key columns for the target.
User Response:
Run the external loader in a different mode, define a primary key for the target, or add a non-key column to the target.

WRT_8315 The user-defined commit session is not supported for this type of mapping (no targets in commit groups).

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

WRT_8324 Warning: Target Connection Group's connection doesn't support transactions. Targets <target names> may not be loaded according to specified transaction boundary rules!

Explanation:
You are running a source-based commit or user-defined commit session, and the named targets may not recognize transaction boundaries. This might happen with flat file targets or with bulk loading.
User Response:
This is an informational message for flat file targets, as flat files are commit-neutral. If you run the session in bulk mode, and you want to ensure that the targets load according to transaction boundaries, you can edit the session and run the session in normal mode.

WRT_8329 Warning. Ignoring external loader control file directory <directory> since it is all whitespace.

Explanation:
You configured the Integration Service LoaderControlFileDirectory option to use a directory separate from the Integration Service installation directory to create and store external loader control files, but you did not specify a directory name.
User Response:
Specify a directory name for LoaderControlFileDirectory.

WRT_8343 Error: Target filename <file name> exceeded maximum allowable length <bytes>.

Explanation:
The target file name length exceeds the system limit (260 on Windows, 255 on UNIX).
User Response:
Reduce the length of the file name.

WRT_8371 Row rejected since a rollback was issued due to errors in the transaction.

Explanation:
The Integration Service encountered an error in the transaction and the session is configured to roll back on error.
User Response:
Read other messages in the log file to find the row that caused the error.
Explanation:
The transaction control expression in a Transaction Control transformation evaluated to roll back the transaction. The Integration Service rolled back all rows in the transaction, including this row.
User Response:
Read other messages in the log file to find the row that caused the transaction control expression that evaluated to roll back.

WRT_8372 Row rejected since a rollback was issued due to a failed commit.

Explanation:
The Integration Service failed to commit a transaction and the session is configured to roll back on failed commit.
User Response:
Read other messages in the session log to find the cause of the failed commit.

WRT_8398 Error opening session output file <file name>. Error: <error text>.

Explanation:
The Integration Service could not open the target output file for the session. This error can occur if the target output file does not exist, the path to the file is invalid, the Informatica Services account or the operating system user in the operating system profile does not have permission to open the file, or another process is using the file. As a result, the session failed.
User Response:
Verify that the target output file exists, grant read and write permissions on the file to the Informatica Services account or the operating system user in the operating system profile, and verify that the file is not currently in use by another process. If the session is enabled for recovery, recover the session. Otherwise, run the session again.

WRT_8399 Error closing target output file <file name>. Error: <error text>.

Explanation:
The Integration Service could not close the target output file. This error can occur if there is not sufficient disk space available to close the file. As a result, the session failed.
User Response:
Verify that there is sufficient disk space for the target output file. If the session is enabled for recovery, recover the session. Otherwise, run the session again.

WRT_8414 High availability license is absent. Retry period specified for Integration Service connection to target is ignored.

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

WRT_8419 Flat file target <target name> FileName port is not supported with connection or merge option.

Explanation:
The Integration Service failed the session because the FileName port is not supported with the target type or connection. You cannot configure a FileName port with an FTP target, merge file, or file list.
User Response:
Remove the FileName port from the target.

WRT_8424 The Integration Service cannot read the control file template <control file template name>.

Explanation:
The Integration Service was unable to find the control file template.
User Response:
Verify that the directory and file name for the control file template are entered correctly in the session properties. Verify that the file exists in the specified directory.

WRT_8425 ERROR: Writer execution failed.

Explanation:
The session failed to write to the target.
User Response:
Check preceding error messages to see the cause for the error.

WRT_8426 ERROR: Writer preparation failed.

Explanation:
The session failed while the Integration Service was preparing to write to the target. The target might not exist, or the Integration Service encountered other errors.
User Response:
Check preceding error messages to see the cause for the error.

WRT_8428 Error transferring data from target <target name> using SFTP.

Explanation:
The Integration Service encountered an error while preparing to transfer the files using SFTP.
User Response:
Verify that the SFTP server is running, verify the file permissions and connection information, and run the session again.

WRT_8430 The Integration Service could not create a locale for code page ID: <code page>.

Explanation:
The Integration Service failed to create an I18N converter object.
User Response:
Contact Informatica Global Customer Support.

WRT_8435 Error occurred opening the recovery queue: <error message>.

User Response:
Review the session log for related messages.

WRT_8436 Error occurred closing the recovery queue: <error message>.

User Response:
Review the session log for related messages.

WRT_8437 The following error occurred writing recovery information to the recovery queue: <error message>.

User Response:
Review the session log for related messages.

WRT_8438 The following error occurred deleting recovery information from the recovery queue: <error message>.

User Response:
Review the session log for related messages.

WRT_8439 The following error occurred reading recovering information from the recovery queue: <error message>.

User Response:
Review the session log for related messages.

WRT_8442 The Integration Service cannot recover multi-partitioned flat file targets with the concurrent merge option.

User Response:
Disable recovery for the workflow.

WRT_8443 The Integration Service cannot repeat a multibyte NULL character in the file <file name>.

Explanation:
The session has a fixed width target configured to repeat null characters. The session fails because the null character is a multibyte character and the field length is not divisable by the number of bytes in the null character.
User Response:
Choose a single-byte null character.

WRT_31215 Valid PowerCenter Connect for Salesforce.com license key is not found.

Explanation:
The license key does not have the PowerExchange for Salesforce option.
User Response:
Contact Informatica Global Customer Support to obtain a new incremental license key.