Changing Logs method in DataStage

-
DataStage logging was changed at release 8.1 to log job run detail records into the operational repository, (xmeta) rather than the local project level log files, (RT_LOGxxx).
In case XMETA repository logging causing problem (i.e not visible from designer), we able to change the logging method back to local project log files.


RTLogging ---> Log will saved in  project level log files which is UV binary files
ORLogging --->  Log will saved in XMETA DB

Here are the steps:

1) Log into DS machine
2) Go to /opt/IBM/InformationServer/Server/Projects/
3) Choose you project directory
4) Edit DSParams file
5) Look for RTLogging and ORLogging entries

RTLogging=0
ORLogging=1

 6) Change it to

RTLogging=1
ORLogging=0

The logging should now go to project level log files instead of xmeta DB.
Note: We still need to rely on Director client to verbose the log information as the log files data are in binary form.

@DataStage

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