Director Crashing
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 39
- Joined: Wed Jun 23, 2004 4:33 am
- Location: UK, chester
Director Crashing
I have imported a job, compiled it and ran it successfully but when I try to view the job details in director I get the following message:-
'Run-time error '457'
This key is already associated with an element of this collection'
The Director session then terminates.
Any ideas.
'Run-time error '457'
This key is already associated with an element of this collection'
The Director session then terminates.
Any ideas.
Pete Morris
-
- Charter Member
- Posts: 39
- Joined: Wed Jun 23, 2004 4:33 am
- Location: UK, chester
Is it only t that job or for all the job? What about the same job in other server?
Have you tried to delete the job and reimport it?
If you make a search, you can find that its error associated to the Universe error code. Which required support from specialized people. Log a eCase for this in IBM website.
Have you tried to delete the job and reimport it?
If you make a search, you can find that its error associated to the Universe error code. Which required support from specialized people. Log a eCase for this in IBM website.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Have you re-booted one of the PCs to clear any scrambled DLL/OCX files from memory? What is the exact version of DataStage (use the Help menu, About topic to find out)?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Charter Member
- Posts: 39
- Joined: Wed Jun 23, 2004 4:33 am
- Location: UK, chester
Sounds like a repository issue. Make sure your projects have plenty of space on their filesystem. Make sure /tmp is not full. Get everyone out of the project and do a full export. Run DS.TOOLS and rebuild the repository indices.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
-
- Charter Member
- Posts: 39
- Joined: Wed Jun 23, 2004 4:33 am
- Location: UK, chester
Just to update this post for Version 8.1
Code: Select all
APAR status
Closed as fixed if next.
Error description
The following error message is displayed:
Run-time error 457: The key is already associated with an
element of this collection.
Local fix
This can be caused when unexpected duplicate log records exist
in the repository for the selected job.
To work around the issue it will be necessary to clear
the existing log entries for the affected job by using one of
the following procedures:
Start the Director client and select the job in the status
view. Select Job > Clear Log from the menu. Click OK for
immediate purge.
Use the Web Console Log management functionality to purge
the log for that job.
Problem summary
****************************************************************
USERS AFFECTED:
Viewing Job Logs
****************************************************************
PROBLEM DESCRIPTION:
Unexpected duplicate log records in the repository can cause a
failure.
****************************************************************
RECOMMENDATION:
Will be fixed in a future release.
****************************************************************
APAR information
APAR number JR30638
Reported component name WIS DATASTAGE
Reported component ID 5724Q36DS
Reported release 810
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2008-09-30
Closed date 2009-01-07
Last modified date 2009-01-07