DSD.UVOpen error
Moderators: chulett, rschirm, roy
DSD.UVOpen error
Hi all, i'm facing the following error
"DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..Hashed_LOG_PRE_DAILY_BAL_DUP_HASH_TMP4.IDENT2: |DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..LOG_PRE_DAILY_BAL_DUP_HASH_FROM4.in: DSD.UVOpen Unable to open file LOG_PRE_DAILY_BAL_DUP_HASH4.|"
Any solutions for this ? Thank you.
"DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..Hashed_LOG_PRE_DAILY_BAL_DUP_HASH_TMP4.IDENT2: |DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..LOG_PRE_DAILY_BAL_DUP_HASH_FROM4.in: DSD.UVOpen Unable to open file LOG_PRE_DAILY_BAL_DUP_HASH4.|"
Any solutions for this ? Thank you.
dwcw
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard. :D
The message is "unable to open hashed file LOG_PRE_DAILY_BAL_DUP_HASH4".
Can you prove to us (with an ls -llisting, for example) that this hashed file exists and that you have appropriate permission to open it? Can you also confirm how the Hashed File stage refers to it - in the account or in a directory?
The message is "unable to open hashed file LOG_PRE_DAILY_BAL_DUP_HASH4".
Can you prove to us (with an ls -llisting, for example) that this hashed file exists and that you have appropriate permission to open it? Can you also confirm how the Hashed File stage refers to it - in the account or in a directory?
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.
Is the hashed file in an 'account' or pathed into a directory? How did you try to delete the file? Has the job ever worked and is just now having this problem?
Describe your job - are you using the hashed file as a reference lookup? If yes, it must exist first and have been created by another 'process' first. Typically that would be another job but doesn't absolutely have to be.
More details from you are required to properly answer your question.
Describe your job - are you using the hashed file as a reference lookup? If yes, it must exist first and have been created by another 'process' first. Typically that would be another job but doesn't absolutely have to be.
More details from you are required to properly answer your question.
-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:
hi chulett,
"Is the hashed file in an 'account' or pathed into a directory? How did you try to delete the file? Has the job ever worked and is just now having this problem?
Describe your job - are you using the hashed file as a reference lookup? If yes, it must exist first and have been created by another 'process' first. Typically that would be another job but doesn't absolutely have to be.
More details from you are required to properly answer your question."
i tried to delete the hash file by executing
"DELETE VOC LOG_PRE_DAILY_BAL_DUP_HASH4"
The job was working fine previously. This job is used as a reference lookup. How do i find out which 'process' is responsible to create the hash file? I was wondering if i re-compile or re-export my backup copy of the job to the production environment, will it help? This is killing me. need help badly.
Thank you !!!
"Is the hashed file in an 'account' or pathed into a directory? How did you try to delete the file? Has the job ever worked and is just now having this problem?
Describe your job - are you using the hashed file as a reference lookup? If yes, it must exist first and have been created by another 'process' first. Typically that would be another job but doesn't absolutely have to be.
More details from you are required to properly answer your question."
i tried to delete the hash file by executing
"DELETE VOC LOG_PRE_DAILY_BAL_DUP_HASH4"
The job was working fine previously. This job is used as a reference lookup. How do i find out which 'process' is responsible to create the hash file? I was wondering if i re-compile or re-export my backup copy of the job to the production environment, will it help? This is killing me. need help badly.
Thank you !!!
dwcw
hi all thanks for ur kind assistance,
I've able to delete the hash file. I rerun the job hoping that i would run without abort but it didnt and it shows this error
DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..LOG_PRE_DAILY_BAL_DUP_HASH_FROM4.in: DSD.UVOpen Unable to open file LOG_PRE_DAILY_BAL_DUP_HASH4.
DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..Hashed_LOG_PRE_DAILY_BAL_DUP_HASH_TMP4.IDENT2: |DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..LOG_PRE_DAILY_BAL_DUP_HASH_FROM4.in: DSD.UVOpen Unable to open file LOG_PRE_DAILY_BAL_DUP_HASH4.|
Attempting to Cleanup after ABORT raised in stage DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..Hashed_LOG_PRE_DAILY_BAL_DUP_HASH_TMP4.IDENT2
Job DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0 aborted.
Please advice. Thank you.
I've able to delete the hash file. I rerun the job hoping that i would run without abort but it didnt and it shows this error
DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..LOG_PRE_DAILY_BAL_DUP_HASH_FROM4.in: DSD.UVOpen Unable to open file LOG_PRE_DAILY_BAL_DUP_HASH4.
DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..Hashed_LOG_PRE_DAILY_BAL_DUP_HASH_TMP4.IDENT2: |DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..LOG_PRE_DAILY_BAL_DUP_HASH_FROM4.in: DSD.UVOpen Unable to open file LOG_PRE_DAILY_BAL_DUP_HASH4.|
Attempting to Cleanup after ABORT raised in stage DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0..Hashed_LOG_PRE_DAILY_BAL_DUP_HASH_TMP4.IDENT2
Job DJobFlushLogicaPrepaidDailyBalanceHash4%rel50.1.0 aborted.
Please advice. Thank you.
dwcw
hi all,
Thanks a lot for the advice. Its actually an error caused by the job which creates the hash file. It was not compiled. So i recompile it and its fine now.
But its kind of weird, the job was compiled and running fine previously. How on earth did the job status became "Not Compiled" ? Weird
Thanks anyway.
Thanks a lot for the advice. Its actually an error caused by the job which creates the hash file. It was not compiled. So i recompile it and its fine now.
But its kind of weird, the job was compiled and running fine previously. How on earth did the job status became "Not Compiled" ? Weird
Thanks anyway.
dwcw
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Anyone opening the job in Designer, or its properties in Manager, and making any little change (even moving an annotation) then clicking Save constitutes an "edit". This will change the job's status to Not Compiled until it is once again compiled. The DS_AUDIT table tracks edits made with DataStage clients, identifying by whom and when each edit was made.
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.