#DateForumTypeThreadPost
110919 May 2016 @ 02:31 PDTToolsReplyFEXP_OPERATOR: TPT12108: Output Schema does not match data from SELECT statementPlease provide the entire script. In the schema you defined one of the columns as ANSIDATE. But by default, the database will return DATE information in an integer format. In order for you to ge...
110818 May 2016 @ 06:31 PDTToolsReplyMLOAD - UTY4014 Access module error '43' received during 'set position' operationALWAYS include the version of MultiLoad you are running and the platform. A 'set position' message generally implies the job is trying to recover from a restart. Is this a brand new job? ...
110718 May 2016 @ 03:49 PDTToolsReplyTPT issue : not able to open the data fileThat message (ac cryptic as it is) is coming from the logger, which means it is having trouble opening up the job log. Are you sure that the user has write access to the directory in which the log...
110618 May 2016 @ 12:42 PDTToolsReplyExecuting multiple TPT scripts simultaneously will yield to better perfomance?It needs to be tbuild -f <script-name> -C
110518 May 2016 @ 12:41 PDTToolsReplyDATA_Selector: TPT15112: Column #1 in schema is too small to hold 11 bytes of dataLooking at the entire script again, if you are setting ReportModeOn to "yes", the schema *HAS* to be all-VARCHAR. Please modify your schema to be all-VARCHAR. You said you tried it but ...
110417 May 2016 @ 09:09 PDTToolsReplyDATA_Selector: TPT15112: Column #1 in schema is too small to hold 11 bytes of dataPlease send me the output of the layout of the view.
110317 May 2016 @ 10:04 PDTToolsReplyExecuting multiple TPT scripts simultaneously will yield to better perfomance?Yes, it is possible. Specify multiple instances of the DataConnector operator (the file writer). Each instance will write to a separate file. And make sure to specify the -C (uppercase) command ...
110217 May 2016 @ 10:01 PDTToolsReplyTPT error 13 in finalizing the table schema definition(SELECTOR OPERATOR)Via the ReportModeOn attribute for the Selector operator. Please refer to the documentation.
110117 May 2016 @ 10:00 PDTToolsReplyDATA_Selector: TPT15112: Column #1 in schema is too small to hold 11 bytes of dataWhat version of TPT are you running? On what platform are you running TPT? What is the client session character set you are using for the job? Please provide the script.
110016 May 2016 @ 10:57 PDTToolsReplyExecuting multiple TPT scripts simultaneously will yield to better perfomance?Better performance than what?  
109912 May 2016 @ 05:29 PDTToolsReplyTPT deadlock Issue.I believe in this case, the "Retrying request" message was output in error. As indicated above, we will handle it better. There were some areas where requests resulting in the deadlock ...
109811 May 2016 @ 01:42 PDTToolsReplyTPT without schema for STREAM OperatorVery good! That was going to be my next recommendation.    
109711 May 2016 @ 11:27 PDTToolsReplyTPT issue : not able to open the data fileFirst, when using a consumer operator, please use the syntax "SCHEMA *". Do not hardcode a schema name. This is because the schema might change. The Export operator might export 'n&...
109610 May 2016 @ 10:50 PDTToolsReplyTPT without schema for STREAM OperatorNot sure what you mean by "neither of them worked". The incomplete INSERT statement will never work.   If $INSERT did not work, please provide the information showing the failure. ...
109510 May 2016 @ 10:22 PDTToolsReplyTPT without schema for STREAM OperatorThe two examples are not equivalent. In your Load operator example, you are using the $INSERT macro. TPT takes that macro and generates the entire INSERT statement (with the VALUES clause). In y...
109410 May 2016 @ 09:44 PDTToolsReplyTPT without schema for STREAM OperatorI believe your INSERT statement in the APPLY clause is not complete. Where is the VALUES clause?
109309 May 2016 @ 10:57 PDTToolsReplyTPT without schema for STREAM OperatorPlease provide the entire script (and job variable file, if you use one), and the complete output from the console.   Thanks!
109209 May 2016 @ 03:25 PDTToolsReplyTPT without schema for STREAM OperatorTry removing the word INTEGER from in front of Pack.
109105 May 2016 @ 01:25 PDTTeradata ApplicationsReplyTPT - Load Operator consumes from a named pipe provided by a JNI processPlease refer to the Access Module Reference Manual. It says: Note: On Windows systems The access module creates them automatically, and they are destroyed when the access module closes them. Th...
109005 May 2016 @ 01:13 PDTTeradata ApplicationsReplyTPT - Load Operator consumes from a named pipe provided by a JNI processWhat (exact) version of TPT 14.10 are you running?  
108904 May 2016 @ 12:05 PDTToolsReplyTPT deadlock Issue.Deadlocks cannot ever go away. If you have enough jobs running on the system, there are bound to be deadlocks. The "fix" is that we will handle it better.  
108804 May 2016 @ 11:41 PDTToolsReplyError while loading DATE column using TPTThe FastLoad protocol (which is used by the TPT Load operator) is very restrictive in the syntax of the INSERT statement. The DBS is complaining about the CAST syntax. It is not allowed.   ...
108704 May 2016 @ 11:37 PDTToolsReplyTPT deadlock Issue.Please upgrade to the latest patch of 15.00, at least 15.00.00.08.
108603 May 2016 @ 04:23 PDTToolsReplyTPT deadlock Issue.Any time we get a 2631 from the DBS while accessing the restart log table, we retry the request. I believe we retry 5 times. If we still get the 2631 after the retries, we will terminate with tha...
108503 May 2016 @ 10:16 PDTToolsReplyHow to get values from TPT log file?In the log there are several "private" logs (virtual logs). One of them is called TWB_STATUS. If you look in the TPT documentation (at 14.00 I do not remember if the information is in th...

Pages