Hi All,
I am getting the below mentioned issue when i am trying to run one of my jobs:
DataStage Job 1706 Phantom 286
Program "DSD.StageRun": Line 626, Internal data error.
Program "DSD.StageRun": Line 626, Unable to open the operating system file "DSD_BP.O/JOB.154583408.DT.1486473321.TRANS1".
[ENOENT] No such file or directory
Program "DSD.StageRun": Line 626, Unable to load file "JOB.154583408.DT.1486473321.TRANS1".
Program "DSD.StageRun": Line 626, Unable to load subroutine.
File '/usr/datastage/Ascential/DataStage/Projects/bncpr_ods/VOC':
Computed blink of 0x12C800 does not match expected blink of 0x12F800!
Detected within group starting at address 0x13A000!
Attempting to Cleanup after ABORT raised in stage xfmHKHGNDLLoadVolumeDepositToODS1..ODSLoad
DataStage Phantom Aborting with @ABORT.CODE = 3
The job design is very simple, I am reading the data from a squential file and loading the same into an Oracle table. I tried searching the forum and most of the posts are saying that it is related to hash file where as i am not using any hash files in this job. Please help me in identifying the reason of this issue and please guide me if we have some method to resolve this issue. Thank You for the help.
Thanks & Regards,
Punar Deep Singh
Server Job Abort Issue
Moderators: chulett, rschirm, roy
Actually, every job 'uses' hashed files - they are used to store all of the information about the job itself, design, config, etc etc. And that is what seems to be corrupted in your case, the job.
Can you export the job design (just that) successfully? If so, I'd suggest you do so, then reimport the job. That will delete the 'old' version of the job, assign it a new internal number and rebuild everything needed.
Can you export the job design (just that) successfully? If so, I'd suggest you do so, then reimport the job. That will delete the 'old' version of the job, assign it a new internal number and rebuild everything needed.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's worse than that. VOC is corrupted. Without specialist support (which your support provider will need to buy from IBM) you will not be able to fix this, and your project will remain unusable. There are very few specialists who know how to repair corrupted VOC file, and most of them work for IBM.
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.