Check Datastage Project for any corrupted files

How to verify if DataStage project has any corrupted files :DK®

If DataStage project or temp directory runs out of disk space, some of the buffered write requests might not get correctly completed and the project might ended up having corrupted hash files.DK®

How to Proceed :DK®

Run the uvbackup process and redirect the backup to null devices. The uvbackup produces an output file that can be used to identify the corrupted files.

Process to Check Corrupted Datastage Jobs/Files :DK®

1. Source your dsenv file in $DSHOME (. ./dsenv)
2. Go to your project directory (../InformationServer/Project/)
3. List all files and direct them to a file (ls > DevProjFiles.txt) - this is used to list of files for the uvbackup
4. Run the uvbackup and redirect output to null with this command: DK®
   
   cd /opt/IBM/InformationServer/Server/DSEngine
   . ./dsenv
   cd bin
   ./uvbackup -V -f -cmdfil DevProjFiles.txt -s uvbackupout.txt -t /dev/null 2>&1 > testing123.txt
   
   "$DSHOME/bin/uvbackup -V -f -cmdfil DevProjFiles.txt -s uvbackupout.txt -t /dev/null 2>&1 > testing123.txt"
5. grep "WARNING:" uvbackupout.txt
   You will get the list of corrupted jobs/files in project directory.

Corrupted Files/Jobs List :DK®

The output file: uvbackupout.txt will help to identify if there are any corrupted files in the project.

i.e

Here is an example what you might see in the uvbackupout.txt file:DK®

WARNING: Unable to open file 'RT_STATUS3334' for reading. File not saved!

The uvbackup verifies the integrity of the files and will not backup any files that are corrupted.