1. ps -ef |grep dsrpc
1. ps -ef |grep slave
1. netstat -a |grep dsrpc
1. ps -ef |grep JobMon
1. ps -ef |grep dscs
1. . ./dsenv
1. DSHOME/bin/uv -admin -start
1. DSHOME/bin/uv -admin -stop
1. ps -ef | grep
1. ps -ef | grep phantom
1. ps -ef | grep osh
1. ps -ef | grep dsapi
1. ipcs - mop | grep ade
1. ps -ef |grep slave
1. netstat -a |grep dsrpc
1. ps -ef |grep JobMon
1. ps -ef |grep dscs
1. . ./dsenv
1. DSHOME/bin/uv -admin -start
1. DSHOME/bin/uv -admin -stop
1. ps -ef | grep
1. ps -ef | grep phantom
1. ps -ef | grep osh
1. ps -ef | grep dsapi
1. ipcs - mop | grep ade
2.
*******************************************************************
To Clear RT Log :
CLEAR.FILE RT_LOG(JOB_NUMBER)
Ex: CLEAR.FILE RT_LOG22
Ex: CLEAR.FILE RT_LOG22
………………………………………………..
1. .
/opt/IBM/InformationServer/Server/DSEngine/dsenv
1. cd ./opt/IBM/InformationServer/Server/DSEngine
bin/uv –admin –stop
1. cd ./opt/IBM/InformationServer/Server/DSEngine
bin/uv –admin –start
1. cd /opt/IBM/InformationServer/ASBNode/bin
./NodeAgents.sh stop
1. /opt/IBM/WebSphere/AppServer/profiles/default/bin/stopServer.sh -username <WAS_Username> -password <WAS_Password>
1. /opt/IBM/WebSphere/AppServer/profiles/default/bin/startServer.sh -username <WAS_Username> -password <WAS_Password>
1. cd /opt/IBM/InformationServer/ASBNode/bin
./NodeAgents.sh start
1. cd ./opt/IBM/InformationServer/Server/DSEngine
bin/uv –admin –stop
1. cd ./opt/IBM/InformationServer/Server/DSEngine
bin/uv –admin –start
1. cd /opt/IBM/InformationServer/ASBNode/bin
./NodeAgents.sh stop
1. /opt/IBM/WebSphere/AppServer/profiles/default/bin/stopServer.sh -username <WAS_Username> -password <WAS_Password>
1. /opt/IBM/WebSphere/AppServer/profiles/default/bin/startServer.sh -username <WAS_Username> -password <WAS_Password>
1. cd /opt/IBM/InformationServer/ASBNode/bin
./NodeAgents.sh start
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
I have a whole Word
document of admin commands. Most are occasional-to-rare use, notably those
passed to me by IBM support. It does contain very good documentation on
bouncing 8.x services. Outside of the document I also define the following
aliases for Solaris, IIS 8.0/8.1. I also have many KSH scripts for admin tasks
and monitoring.
alias cleanup_abandoned_locks='/opt/etl/IBM/InformationServer/ASBServer/bin/cleanup_abandoned_locks.sh -U $LOGNAME -P '
alias example=/opt/etl/IBM/InformationServer/Server/branded_odbc/example/example
alias ws_collector='/opt/etl/IBM/WebSphere/AppServer/profiles/default/bin/collector.sh'
alias ds_iis='ps -fp "$(pgrep java) $(pgrep resource) $(pgrep dsrpcd)"'
alias ds_job='pgrep dsjob|doloop.ksh ptree'
alias ds_job_ps='ps -fp $(ds_job|awk '"'{print "'$1'"}'|tr "'"n" '"',')"
alias ds_net='netstat -a|grep dsrpc'
alias ds_ports='netstat -an|egrep "31538|60000|60004|31531|31533"|grep LISTEN|sort'
alias ds_myjobs='ps -u $LOGNAME|grep dsjob|awk '"'"'{print $1}'"'"'|doloop.ksh /usr/ucb/ps -auxww|awk '"'"'{print $2","$NF}'"'"
alias cleanup_abandoned_locks='/opt/etl/IBM/InformationServer/ASBServer/bin/cleanup_abandoned_locks.sh -U $LOGNAME -P '
alias example=/opt/etl/IBM/InformationServer/Server/branded_odbc/example/example
alias ws_collector='/opt/etl/IBM/WebSphere/AppServer/profiles/default/bin/collector.sh'
alias ds_iis='ps -fp "$(pgrep java) $(pgrep resource) $(pgrep dsrpcd)"'
alias ds_job='pgrep dsjob|doloop.ksh ptree'
alias ds_job_ps='ps -fp $(ds_job|awk '"'{print "'$1'"}'|tr "'"n" '"',')"
alias ds_net='netstat -a|grep dsrpc'
alias ds_ports='netstat -an|egrep "31538|60000|60004|31531|31533"|grep LISTEN|sort'
alias ds_myjobs='ps -u $LOGNAME|grep dsjob|awk '"'"'{print $1}'"'"'|doloop.ksh /usr/ucb/ps -auxww|awk '"'"'{print $2","$NF}'"'"
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
•Check
the permissions
1.Log on to server as dsadm or root
2.cd $DSHOME/bin
3.ls -l | grep rws
The output should be (6) files owned by root with the setuid bit set -- especially the uv file.
•Check to ensure that there was a clean restart of the DataStage Engine.
Here are the instructions for a clean restart of DataStage Engine:
1. Log on to server as dsadm or root
2. cd $DSHOME
3. source the environment:
. ./dsenv --> that's dot space dot slash dsenv
4. Check for DataStage client connections
ps -ef | grep dsapi_slave
ps -ef | grep dscs
If there are any connections found, use kill -9 to remove them.
5. Check for jobs processes:
ps -ef | grep phantom
If there are any connections found, use kill -9 to remove them.
6. Check datastage shared memory segments:
ipcs - mop | grep ade
If there any shared memory segments returned, remove them, use command:
ipcrm -m ID , where ID is the number from the second column of ipcs -mop
7. Check if there is any port hung using:
netstat -a | grep dsrpc
If you get any results and the dsrpc is in WAIT then you need to wait until this it disappears (you can also reboot the machine).
8. At this point you can stop or start the DataStage Engine.
bin/uv -admin -stop
bin/uv -admin –start
1.Log on to server as dsadm or root
2.cd $DSHOME/bin
3.ls -l | grep rws
The output should be (6) files owned by root with the setuid bit set -- especially the uv file.
•Check to ensure that there was a clean restart of the DataStage Engine.
Here are the instructions for a clean restart of DataStage Engine:
1. Log on to server as dsadm or root
2. cd $DSHOME
3. source the environment:
. ./dsenv --> that's dot space dot slash dsenv
4. Check for DataStage client connections
ps -ef | grep dsapi_slave
ps -ef | grep dscs
If there are any connections found, use kill -9 to remove them.
5. Check for jobs processes:
ps -ef | grep phantom
If there are any connections found, use kill -9 to remove them.
6. Check datastage shared memory segments:
ipcs - mop | grep ade
If there any shared memory segments returned, remove them, use command:
ipcrm -m ID , where ID is the number from the second column of ipcs -mop
7. Check if there is any port hung using:
netstat -a | grep dsrpc
If you get any results and the dsrpc is in WAIT then you need to wait until this it disappears (you can also reboot the machine).
8. At this point you can stop or start the DataStage Engine.
bin/uv -admin -stop
bin/uv -admin –start
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
No comments:
Post a Comment