I am loading Teradata (V13.10.03.08) database using informaticav9.1.0 (with Hotfix1). In Infa, i am using TPT connection.
I have the follwing property on the TPT Connection string used in informatica..
Tenacity 4, Max/Min, 10/10. Sleep 6. Block Size 64000. System Operator: Export.
With this connection i have read around 1billion records and jobs ran to success. But with the same connection one of our job is giving CLI error. I have traced the load and i found the below error message in the Trace File.
The below trace file is from the source table.
FETCHBUFFER: got end-of-request (done with block)
FETCHBUFFER: session 72, initiating request for stmt: 1 block: 50869
PC_INITIATEREQ: entering with request: ''
PC_INITIATEREQ: request length: 8
PC_INITIATEREQ: Using length: 0
PC_INITIATEREQ: leaving with return code: 0
FETCHBUFFER: session 72, sent irq stmt: 1 block: 50869
PC_FETCHRESP: entering, expecting flavor: 0
PC_ERRORSET: entering with CLI error code: 220
PC_ERRORSET: leaving with CLI error code: 220
PC_FETCHRESP: leaving with return code: 220
PC_SETCODE: current condition code: 0
PC_SETCODE: setting condition code: 12
**** 13:57:15 Total processor time used = '2413.29 Second(s)'
. Start : Wed May 1 13:09:09 2013
. End : Wed May 1 13:57:15 2013
. Highest return code encountered = '12'.
EXPORT_OPERATOR: Total processor time used = '2413.29 Second(s)'
**** 13:57:15 This job terminated
In informatica, i get the below error,
Message Code: TPTRD_21215
Message: [ERROR] Plug-in failed to fetch data on row  with status .
Message: Partition-level [SQ_source]: Plug-in #315000 failed in run().
Message Code: TPTRD_21509
Message: [ERROR] Plug-in failed to read data from table [source_table_name] of Teradata database.
Any help on how to resolve this would be appreciated. Thanks for your time.
We are encountering CLI errors with TPT via Informatica. Did you get resolution to your post in May 2013 for the CLI errors? If so, what did you need to do?
What are the errors you are getting? And are/were you able to run the similar jobs using same TPT connection?
We are getting the following CLI errors (just a snapshot out of a session log). When error occurs, they restart and then it finishes successfully. The errors are sporadic and we can't recreate them. We have incidents open with both Teradata and Informatica to address. The sessions include the 'truncate and then fast-load' to a Teradata Staging Database. I am just looking for information on others who had the same error to see if I can gleen anything while we wait for responses.
Have you resolved the issue? If you got a resolution can you please share? We are getting the following Error from Informatica 9.6 to Teradata TD15.0 connection. The jobs runs fine most of the time. If it fails we restart again and job successfully completes. Lately this issue is causing lots of failures and looking for a solution as soon as possible.
This is what we get from the log file:
WRITER_1_*_1> TPTWR_32604 [INFO] Table information (schema) retrieved successfully.
WRITER_1_*_1> TPTWR_32605 [INFO] DML statements on table [<$DATABASE>.<$TABLE_NAME>] for system operator [TD_UPDATE] built successfully.
TPTWR_35120 [INFO] A error has occured for instance  for target .
TPTWR_34210 [DEBUG] Formatting TPT API error message...
CMN_1761 Timestamp Event: [Sat Feb 27 05:18:36 2016]
TPTWR_207 [ERROR] Type:(Teradata CLI Error), Error: (CLI error 207 (no message text available))
CLI 207 means that the client OS told CLIv2 that the TCP/IP connection request failed.
If this is a Unix / Linux server, be sure you have the environment variable THREADONOFF=1
It also appears COPERR is not set properly, though I suspect the message text won't provide much help.
Or perhaps you have exceeded some OS limit. Contact the system administrator for the Informatica server for help.
Thanks Fred !! Our Linux server's THREADONOFF is set to 1 (THREADONOFF=1) . Followings are our COPERR settings. Is there anything to do with Maxsessions settings for each job and concurrency of load jobs? Our Maxsession limit is set to 16 for each job and 20 load utility slots are available. Total number of nodes 12 and 2 PEs per node and 288 AMPs. Do you you see any issues with these settings?
COPERR settings for informatica server:
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
Those look like ulimit settings (and I see no issues with those).
COPERR is an environment variable (typically set to /opt/teradata/client/vv.vv/lib64)
If the problem was exceeding a database limit, e.g. too many sessions or too many concurrent utilities, then you should have received a different message. CLI 207 is typically a problem on the client; perhaps it's a system-wide limit rather than a user-specific limit, e.g. number of open file descriptors (which includes TCP socket connections). Enlist the help of your Linux sysadmin to troubleshoot.