When datastage file system becomes full, RT_LOGxxx files can become corrupted. Here is a manual procedure to recreate them.

-

​​
Problem(Abstract)

When many datastage jobs are running for long time, the RT_LOGxxx files can become very big. If the log files are not regularly purged, in some cases, a file system full on the datastage file system can occur. If the corruption of datastage system files is restricted to the RT_LOGxxx files, a procedure to delete and recreate the RT_LOGxxx files can be attempted in order to recover from the corruption.

Symptom

Error message appears when trying to open specific job from Director client:

"Error calling subroutine: DSR_PROJECT (Action=8); check DataStage is set up correctly in project PPPP (Subroutine failed to complete successfully (30107)"

Other similar errors may occur as well.

Cause

RT_LOGxxx files got corrupted for file system full, or other similar system crash.

Resolving the problem

To delete the problem RT_LOGxxx, you need to first identify the job number relative to the problem job, using the command LIST DS_JOBS jobname
(the number that is output corresponds to the job number) and then run the following from Administrator client or uvsh prompt, in the specific project:


1) DELETE.FILE DATA RT_LOGnn where nn is the job number.
2) CREATE.FILE DATA RT_LOGnn 30 wh

​​
ere nn is the job number


Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more