PSession Log file for a session that sometimes runs and at times fails

[coolspartan]

Please help. It fails most of the times... It is scheduled to run at nights..... after it is restarted by me... it runs... This is the log when it failed to run at the scheduled time



MASTER> CMN_1688 Allocated [12000000] bytes from process memory for [DTM Buffer Pool].
MASTER> PETL_24000 Parallel Pipeline Engine initializing.
MASTER> PETL_24001 Parallel Pipeline Engine running.
MASTER> PETL_24003 Initializing session run.
MAPPING> TM_6014 Initializing session [SIL_AssessmentDimension] at [Thu Oct 21 02:56:08 2004]

MAPPING> TM_6101 Mapping name: SIL_AssessmentDimension Version 1.0.0
MAPPING> CMN_1569 Server Mode: [ASCII]
MAPPING> CMN_1570 Server Codepage: [MS Windows Latin 1 (ANSI), superset of Latin1]
MAPPING> TM_6151 Session Sort Order: [Binary]
MAPPING> TM_6156 Using LOW precision decimal arithmetic
MAPPING> TM_6180 Deadlock retry logic will not be implemented.
MAPPING> TE_7022 TShmWriter: Initialized
MAPPING> TM_6007 DTM initialized successfully for session [SIL_AssessmentDimension]
MASTER> PETL_24004 Starting pre-session tasks.
MASTER> PETL_24027 Pre-session task completed successfully.
MASTER> PETL_24006 Starting data movement.
READER_1_1_1> DBG_21438 Reader: Source is [SBANPR], user [siebel]
READER_1_1_1> CMN_1021 Database driver event...
CMN_1021 [DB2 Event Using Array Fetch and Insert. connect string = [SBANPR]. userid = [siebel]]
READER_1_1_1> BLKR_16003 Initialization completed successfully.
WRITER_1_1_1> WRT_8148 Writer: Target is database [SBANPR], user [siebel], bulk mode [N/A]
WRITER_1_1_1> Thu Oct 21 02:56:32 2004
WRITER_1_1_1> WRT_8001 Error connecting to database...
WRT_8001 [Session SIL_AssessmentDimension Username siebel DB Error -1

[IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001




Database driver error...

Function Name : Connect

Database driver error...

Function Name : Connect

Database Error: Failed to connect to database using user [siebel] and connection string [SBANPR].]
WRITER_1_1_1> Thu Oct 21 02:56:32 2004
WRITER_1_1_1> WRT_8068 Writer initialization failed. Writer terminating.
MASTER> PETL_24020

***** RUN INFO FOR TGT LOAD ORDER GROUP [1], SRC PIPELINE [1] *****
MASTER> PETL_24023 Thread [READER_1_1_1] created for the read stage of partition point [SQ_W_ASSESS_DS] has completed. The total run time was insufficient for any meaningful statistics.
MASTER> PETL_24024 Thread [TRANSF_1_1_1_1] created for the transformation stage of partition point [SQ_W_ASSESS_DS] has completed. The total run time was insufficient for any meaningful statistics.
MASTER> PETL_24025 Thread [WRITER_1_1_1] created for the write stage of partition point(s) [KA_W_ASSESS_D] has completed. The total run time was insufficient for any meaningful statistics.
MASTER> PETL_24021 ***** END RUN INFO *****

MASTER> PETL_24005 Starting post-session tasks.
MASTER> PETL_24028 Post-session task completed with failure.
MAPPING> TM_6020 Session [SIL_AssessmentDimension] completed at [Thu Oct 21 02:56:32 2004]
MAPPING> TM_6018 Session [SIL_AssessmentDimension] run completed with [0] row transformation errors.
MAPPING> TM_6022

SESSION LOAD SUMMARY
================================================

MAPPING> TM_6252 Source Load Summary.
MAPPING> CMN_1740 Table: [SQ_W_ASSESS_DS] (Instance Name: [SQ_W_ASSESS_DS])
Output Rows [0], Affected Rows [0], Applied Rows [0], Rejected Rows [0]
MAPPING> TM_6253 Target Load Summary.
MAPPING> TM_6023
===================================================

MASTER> PETL_24002 Parallel Pipeline Engine finished.
MASTER> PETL_24013 Session run completed with failure

 

[Dagon]

It looks as if it is failing to connect to the database. Could your database have been down at the time the job was supposed to run e.g. taken down to do backups ?

 

[vln]

There are three reasons for the failure.

1. The dB server could be down at the time when the run started.
2.The DSN connection could not established.So try to recreate the DSN & again schedule for test load.
3.The Timeout for the connection would have occured due to network connection out.

Thanks
VLN

 

[coolspartan]

Thanks for the responses guys