Hashed file corruption

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
DaleK
Premium Member
Premium Member
Posts: 68
Joined: Fri Jun 27, 2003 8:33 am
Location: Orlando

Hashed file corruption

Post by DaleK »

hello All,

We have a job that has been running for months without issue.
This morning the job fails while updating a hashed file.

the log has this entry:
"Job_DR07BR1D_ext..hf_DR07BU0D_cnts.ds_household_tbl_cnt_out: ds_uvput() - Write failed for record id 'HOUSEHOLD_TBL'"

when I try to view the hashed file in the job I get this error:
"Error calling subroutine:
DSD.Browse (Action=3); check DataStage is set up correctly in project ...."

I logged into admin and tried to do a uvfixfile but get the messege:
"hf_DR07BU0D_cnts is not a filename in voc"
we us directory path not account name when we create hash files.
This hashed file is created and initialized by another job and then updated by a series of jobs with load counts.

Is there another way to run a fix on this file?

thanks
DaleK
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Both fixtool and uvfixfile can be run from the command line. For example

Code: Select all

$DSHOME/bin/uvfixfile -file hf_DR07BU0D_cnts 
(You need to have run the dsenv script first.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

... but only for hashed files with a VOC record pointer. You'll need to manually create it for your pathed hashed files using SET.FILE, if I recall correctly.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Not true. The -file option takes a pathname as its argument.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

D'oh, missed that.
-craig

"You can never have too many knives" -- Logan Nine Fingers
chucksmith
Premium Member
Premium Member
Posts: 385
Joined: Wed Jun 16, 2004 12:43 pm
Location: Virginia, USA
Contact:

Post by chucksmith »

FYI: if it is a 64-bit hashed file, you may have to use fixtool.

Code: Select all

fixtool

The fixtool executable performs the file diagnostic and repair functions of

the File Tool option to UniVerse Admin locally.  (It is fixtool.exe on

NT.)  It has the following options:

      fixtool    -file filename
                         [-level n]
                         [-fix]
                         [-filepath pathname]
                         [-help]
                         [-logging]
                         [-logpath pathname]

-file                        Specifies filename you want to process

-level                       Sets diagnostic level to n where the default is 5

-filepath                    Specifies pathname location of file (the directory the file is in)

-help                        Displays these fixtool options

-logging                     Dumps errors to file in directory called log.filename

-logpath                     Creates log.filename in specified pathname instead of local directory
Post Reply