DataStage Director crashing on View Job Log

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
nigel
Premium Member
Premium Member
Posts: 35
Joined: Tue May 07, 2002 2:48 am
Location: South Africa/UK
Contact:

DataStage Director crashing on View Job Log

Post by nigel »

Hi,

I am getting the following error that causes the Director client to crash with the following messages:

1) Attempt to convert invalid date '', 0 substituted
2)Run-time error '457' This key is already associated with an element of this collection

My job inserts rows into a new table in the local (to the datastage server)DB2 database. The job runs successfully (with a few warnings). The DB2 table contains all the rows.

I get this error when I try to view the log. Around 4 warning log entries is displayed, followed by these error messages in a pop-up. The Director closes once the OK button is clicked.

The 4 warning events in the log prior to the crash that I can view prior to the pop-up are along the lines of ...'APT_CombinedOperatorController,0: Invalid character(s) ([x8A]) foun convert...

The Client is the Refresh 2 Client for DataStage 8.1 Enterprise Edition

Has anyone experienced a similar error?
Nigel
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

I would try making a copy of the job, deleting the original, renamin & recompiling the copy and seeing if the error persists, it might be some problem with the log file used by the director.
nigel
Premium Member
Premium Member
Posts: 35
Joined: Tue May 07, 2002 2:48 am
Location: South Africa/UK
Contact:

Thanks

Post by nigel »

Hi

Thanks, copying the job fixes the problem
Nigel
nigel
Premium Member
Premium Member
Posts: 35
Joined: Tue May 07, 2002 2:48 am
Location: South Africa/UK
Contact:

Still problematic on subsequent runs..

Post by nigel »

nigel wrote:Hi

Thanks, copying the job fixes the problem
This error is still occuring on subsequent job runs.... :(
Nigel
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Got nothing to do with the job, per se, sounds like your XMETA repository is corrupted. I'd suggest contacting your official support provider to get this straightened out.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply