Basically, the Action=8 error, which I normally see when opening the DataStage Director Client application, means that one or more of the RT_LOG files have become corrupted. Usually, this problem occurs in relation to disk space issues; although, there can be other causes.
Error calling subroutine: *DataStage*DSR_PROJECT (Action=8); check DataStage is set up correctly in the project
(Subroutine failed to complete successfully (30107))
The Cleanup approach
The cleanup process really consists of three primary steps:
- Free disk space
- Restart the application process
- And, fix corrupted log
Free Disk Space
This can consist of:
- Cleaning ‘/tmp’ Space
- Removing any large unnecessary files
- Enlarging ‘/tmp’ space allocation
- Adding addition disks space, if necessary
Restart Application Processes
Once you have free the disk space available restarting VM/server is recommended, However, if that is not a realistic option, then at least reboot the Infosphere Datastage engine to ensure the newly freed memory is registering with the applications and to ensure everything is restarted and running.
Fix Corrupted logs
Perhaps, the cleanest way reset all logs is to perform a ‘Multiple Job Compile’. Running the jobs will also overwrite the logs, but is a little more hit and miss, if not all the jobs are not in job streams/batches, which can be run at this time. The logs can be manually overwritten by compiling the job or performing a reset. The trick, with manual reset, is that you have to know which job to reset, so, this could take a while to get them all. The logs can be manually, dropped and reset, but I recommend that approach only as a last resort.