When trying to view a job log in DataStage Director, an error similar to the following is received:
Error selecting from log file RT_LOGnn
Command was: SSELECT RT_LOGnn WITH @ID LIKE '1NON' COUNT.SU
Error was: Internal data error. File <path_to>/RT_LOGnn/<filename>':
Computed blink of 0xnnnn does not match expected blink of 0xnnnn! Detected within group starting at address 0xnnnnnn!
The error message received indicates that the log file for the job is corrupted.
To resolve the problem, the log file must be discarded and recreated. There are a number of ways to accomplish this.
- Reimport the job and overwrite the existing job.
- Rename the job or do a File-->Save as in Designer. You can then delete the old job and rename your new job back to the original name.
- Manually recreate the RT_LOGxxx file.
Note: The job with the associated RT_LOG may need to be re-compiled before it can be run again.
When attempting to overwrite the job, or deleting the original, you may get the error message: Cannot get exclusive of the job. If this happens, make sure that the job is not open in the designer or the director client tools. If this error still appears, take the following steps:
- Login to DataStage Administrator and go to the "Projects" tab. Select the project in question and click "Command" button.
- Type "LIST.READU EVERY" in the command line. In the results, look for active record locks under "Item Id" column for RT_LOGnn (where nn is the description number as seen in the error)
- Write down the inode number and user number for the lock in question.
- Enter the command "CHDIR <path to DSEngine directory>". This is necessary because the subsequent UNLOCK command lives in UV account.
- Enter "UNLOCK INODE inode# USER user# ALL". This will unlock the lock hold on this file (inode#) and hold by this user (user#) for file locks, group locks and record locks.
Now you should be able to delete or overwrite the job.
Steps to manually recreate the RT_LOGxxx file
- Log on to DS Administrator and go to the Projects tab. Select the project in question and click on the "Command" button.
- Delete the existing damaged log file with the following command, where xxx is the description number as seen in the error:
DELETE.FILE DATA RT_LOGxxx
- Create a new log file with the following command, where xxx is the description number as seen in the error:
CREATE.FILE DATA RT_LOGxxx 30