Phantom error in Datastage jobs

-
Resolution – Datastage Services have to be started
So follow the following steps.
  1. Login to server through putty using dsadm user.

  1. Check whether active or stale sessions are there.
ps –ef|grep slave

  1. Ask the application team to close the active or stale sessions running from application's user.
If they have closed the sessions, but sessions are still there, then kill those sessions.

  1. Make sure no jobs are running
If any, ask the application team to stop the job
ps –ef|grep dsd.run

Check for output for below command before stopping Datastage services.
netstat –a|grep dsrpc
If any processes are in established, check any job or stale or active or osh sessions are not running.
If any processes are in close_wait, then wait for some time, those processes
will not be visible.

  1. Stop the Datastage services.
cd $DSHOME
./dsenv
cd $DSHOME/bin
./uv –admin –stop
  1. Check whether Datastage services are stopped.
       netstat –a|grep dsrpc
      No output should come for above command.

  1. Wait for 10 to 15 min for shared memory to be released by process holding them.
Start the Datastage services.
 ./uv –admin –start
If asking for dsadm password while firing the command , then enable impersonation.through root user
              ${DSHOME}/scripts/DSEnable_impersonation.sh




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