DSD.UVOpen error

dannywcw · Post by **dannywcw** » Wed Feb 07, 2007 1:57 am

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.

ray.wurlod · Post by **ray.wurlod** » Wed Feb 07, 2007 2:21 am

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?

dannywcw · Post by **dannywcw** » Wed Feb 07, 2007 11:23 am

hi, thanks for the help but i'm just a regular member. i cant read the whole message u replied. please help. i did tried to delete the hash file. but it reply there's no such hash file.

chulett · Post by **chulett** » Wed Feb 07, 2007 11:31 am

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.

ray.wurlod · Post by **ray.wurlod** » Wed Feb 07, 2007 1:01 pm

For a few cents per day you can read premium posts and help to pay for the bandwidth charges that DSXchange incurs.

dannywcw · Post by **dannywcw** » Thu Feb 08, 2007 1:16 am

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 !!!

dannywcw · Post by **dannywcw** » Thu Feb 08, 2007 1:54 am

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.

ArndW · Post by **ArndW** » Thu Feb 08, 2007 3:45 am

Is the stage DJobFlushLogicaPrepaidDailyBalanceHash4 a write, read or a reference stage? How do you reference the hashed file - by path or by name?

dannywcw · Post by **dannywcw** » Thu Feb 08, 2007 4:26 am

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.

ray.wurlod · Post by **ray.wurlod** » Thu Feb 08, 2007 5:00 am

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.