I Have a problem with a VOC file, my DS Server run on Unix and the VOC file from a project was deleted, I can't login in this project and I need make a backup of Jobs to install in other server, how I can do this??
The VOC file are very important files for DS, in this case if you can ask your UNIX administartor if they do a back up of all what is available on the UNIX Server and ask them to give you a dump of it and then you can reinitialize the DS Project and it should be fine.
as Mahesh stated, your VOC is an important file - it stands for VOCabulary and lists _everything_ about that account... It is quite difficult (almost impossible) to reconstitute a DS account whose VOC is missing. The two major (and relatively painless) options are:
(a) do a UNIX restore of the VOC
(b) re-install the project from a DataStage .dsx backup
If you have neither you are up a swiftly moving creek armed only with a little spoon as a paddle.
OK, so the (a) system restore option won't work. What about a DataStage export?
If not that either, what sort of a project did you have - how many jobs? Did you have your own routines/functions? If you go to the project directory, how many files of the type RT_BP<nnn> do you have (this gives a rough count of how many jobs you do have)?
If you do not have any other resort, you may try to create a dummy DS installation in some other machine and copy the VOC created in new to your current area.
there is NO fully automated way to get your project back. If all you have are 100 jobs and nothing else (i.e. no functions/routines or custom stages) then you will need to do several things, all of which will take a lot of time.
I sent that posting off before I wanted to, sorry.
You will need to do some work at the shell level, or you might write a DS job to do the hash file I/O.
Essentially you will need to re-create the VOC entries as well as the DS_JOBS entries for each of your missing files. The Job information along with it's number needs to be put into the DS_JOBS file, then some/all of the VOC entries for RT_STATUS<nnn>, RT_BP<nnn>, RT_TEMP<nnn>, RT_CONFIG<nnn>, RT_LOG<nnn> and maybe RT_SC<nnn> need to be created and point to the original locations where the files reside. This could probably be automated, or at least simplified.
This is the first part of recovery, there is a bit more work and checking necessary to recover completely.
I think that a couple of the members here would, as an actual consulting job against payment for services rendered, be able to restore your project for you if you do not have the time to attempt to recover. I know I would.
This *should* create pointers to all the repository tables to which Arnd referred. While this approach is not 100% guaranteed, it will probably get you back at least to a position where you can export the jobs.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I had completely forgotten about CLEAN.ACCOUNT! I would think that using that, doing a full export of all jobs and then importing into a fresh account should get you going again.
Once again Ray has come up with a viable & simple solution!
The project name is in the header of the VOC file. You use the VERIFY.SQL command to repair it. First use VERIFY.SQL without the FIX option to verify what will be fixed.