Search found 17 matches
- Thu Nov 13, 2014 4:59 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: File Split logic
- Replies: 8
- Views: 6536
Re: File Split logic
You can use @INROWNUM system variable in transformer .take 4 output links from transfrmer for each sequential file . In the constarint of each link use @inrownum to distribute the rows in each output link.
- Wed Nov 12, 2014 10:50 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 consp
- Replies: 16
- Views: 17240
- Wed Nov 12, 2014 10:49 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error: Unable to start ORCHESTRATE job: APT_PMwaitForP
- Replies: 11
- Views: 9147
We have increased the below values from 60 to 120 APT_PM_CONDUCTOR_TIMEOUT 120 APT_PM_PLAYER_TIMEOUT =120 APT_PM_PLAYER_CONNECT_TIMEOUT=120 APT_PM_NODE_TIMEOUT =120 After this there is no failure for the last 5 days ,But it is too early to conclude . Where can I see the APT file like Path . APT file...
- Tue Nov 11, 2014 4:33 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error: Unable to start ORCHESTRATE job: APT_PMwaitForP
- Replies: 11
- Views: 9147
Scratch space ,Temp space everything is in same D: drive but we monitored the space utilization. Almost 50% of space is free in D: drive at peak times. So Physically there is no space issue .So Is there something to modify in the uvconfig file / values of environmental variables need to be increased ?
- Mon Nov 10, 2014 2:32 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error: Unable to start ORCHESTRATE job: APT_PMwaitForP
- Replies: 11
- Views: 9147
- Mon Nov 10, 2014 2:26 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 consp
- Replies: 16
- Views: 17240
- Mon Nov 10, 2014 2:25 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 consp
- Replies: 16
- Views: 17240
You could try disabling operator combination so that, when next the error occurs, you'll have a more precise idea of which operator actually threw the error. It's almost certainly related to running out of some kind of resource, or a timeout waiting for some resource (perhaps an answer from an exte...
- Thu Nov 06, 2014 4:40 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 consp
- Replies: 16
- Views: 17240
The 50% usage is the maximum utilization of memory when the job ran .we have monitored the space usage for one full day ,ita ranging between 40 to 50 % Is there any other parameter /checks we have to do . This is happening randomly and we are not sure about the reason. Since the server is Window ,Wi...
- Thu Nov 06, 2014 10:10 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 consp
- Replies: 16
- Views: 17240
- Wed Nov 05, 2014 11:54 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error: Unable to start ORCHESTRATE job: APT_PMwaitForP
- Replies: 11
- Views: 9147
- Wed Nov 05, 2014 11:52 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error: Unable to start ORCHESTRATE job: APT_PMwaitForP
- Replies: 11
- Views: 9147
- Tue Nov 04, 2014 3:31 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error: Unable to start ORCHESTRATE job: APT_PMwaitForP
- Replies: 11
- Views: 9147
Fatal Error: Unable to start ORCHESTRATE job: APT_PMwaitForP
We are getting this error randomly Fatal Error: Unable to start ORCHESTRATE job: APT_PMwaitForPlayersToStart failed while waiting for players to confirm startup. This likely indicates a network problem. When I searched this error in google , I have seen the below solution from IBM site Resolving the...
- Thu Oct 30, 2014 10:03 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 consp
- Replies: 16
- Views: 17240
Re: sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 c
We have 2 node configuration file in production { node "node1" { fastname "LKF-PISRVENG01" pools "" resource disk "D:/IBM/InformationServer/Server/Datasets" {pools ""} resource scratchdisk "D:/IBM/InformationServer/Server/Scratch" {pools &q...
- Wed Oct 29, 2014 10:49 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 consp
- Replies: 16
- Views: 17240
sendWriteSignal() failed on node LKF-PISRVENG01 ds = 7 consp
Hi , We have a parallel job which fails with below error message , We do not know its failed because of bad design or some resource contention Can anyone share some toughts please It run daily But it fails only some times Error Log: Error Timestamp: 2014-10-24 10:08:33 Error Job Name: J_NS_CATAMARAN...
- Wed Oct 29, 2014 10:43 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Parallel job reports failure (code -1073741819)
- Replies: 0
- Views: 1487
Parallel job reports failure (code -1073741819)
We have some jobs failing with below error message Parallel job reports failure (code -1073741819) When we reran the job it completed successfully .Is the error something related with resource contention? Its a simple job SQL server -> Transformer->TailStage->Transformer->SequentialFile Volume of re...