Scribd
Upload
41 views3 pages

Stop Start Process

The document provides instructions for restarting all components of an Information Server installation, including stopping and starting DataStage, the ASB Agent, WebSphere Server, database, and automated scripts. The instructions include stopping each component in the listed order, then restarting in the reverse order. Detailed steps are provided for stopping and starting each process, checking for complete shutdown, and verifying successful startup. Logs are also identified to check for issues with WebSphere startup or shutdown.

Uploaded by

Madhu Srinivasan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
41 views3 pages

Stop Start Process

The document provides instructions for restarting all components of an Information Server installation, including stopping and starting DataStage, the ASB Agent, WebSphere Server, database, and automated scripts. The instructions include stopping each component in the listed order, then restarting in the reverse order. Detailed steps are provided for stopping and starting each process, checking for complete shutdown, and verifying successful startup. Logs are also identified to check for issues with WebSphere startup or shutdown.

Uploaded by

Madhu Srinivasan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Instructions for restarting everything in Information Server Version 8 (see instructions below for each step).

1. Stop DataStage (bin/uv -admin -stop)


2. Stop the ASB Agent
3. Stop the WebSphere Server
4. Stop xmeta (DB2, Oracle, whatever)

1. Stop DataStage
a. Log into DataStage machine as dsadm*** on the conductor node.
b. Run ' cd $DSHOME; bin/dssh "LIST.READU" ' and ' bin/uv -admin -info ' to check if there are users.
c. Use isadmin or ' bin/dssh "LOGOUT -pid" ' to log users out.
d. Check if there are any processes left ' ps -ef | egrep "phantom|dsapi|dscs|dsrpc|PID" '.
These commands shouldn't return any results. If they return results, it means that there are still some processes. You can wait for the users to
stop their processes or kill the processes (using kill -9 PID).
e. Check if dsrpc is running
i. ' netstat -a | grep dsrpc '
ii. If dsrpc is running then you should get a line with the status LISTEN. If you get more lines it means that there are still some
connections and you need to identify the processes holding those connections and kill them.
iii. If you see that dsrpc or other connections are in status WAIT then you also need to wait until this it disappears or reboot the machine.
f. Stop DataStage Services
i. ' cd $DSHOME; . ./dsenv '
ii. ' bin/uv -admin -stop '
g. Then see if there is any memory segments left
i. ' ipcs -a | grep ade '
ii. If you get a result, take note of the SHMID and remove it (you will need root access for this part)
iii. ' ipcrm -m <SHMID> '
h. Verify that the dsrpc listener and daemon has stopped
i. ' netstat -a | grep dsrpc '
ii. If you get any and the dsrpc is in WAIT then wait until they terminate or reboot the machine.
iii. ‘ ps -ef | egrep 'dscs|dsapi|phantom|dsrpc|dsjob|uvsh|osh.exe|resource_tracke|PID|Ascential '
i. Stop the resource tracker if it is running “cd $DSHOME; /opt/IBM/Engine/InformationServer/Server/PXEngine/java/jobmoninit stop”
2. Stop the ASB Node and Logging Agents (as ASB process owner [root or dsadm***] on Conductor Node)
a. Logon as ASB process owner (dsadm*** or root) on the conductor node (Engine Tier).
b. Run ' cd /opt/IBM/Engine/InformationServer/ASBNode/bin; ./NodeAgents.sh stop '
c. Type 'yes' if you receive the following message:
rm: remove write-protected regular file `Agent.pid'?
d. Check the agent has stopped:
e. Run “ ps -ef | egrep ascential “ to verify that ASB Node and logging agents have stopped.
f. Run “ pkill -9 -f 'ascential' “ to Kill ASB agents processes if not stopped. Do not kill the ctmagent Control-M agents.
3. Stop the WebSphere Server. (as Websphere process owner [root or wasetlad] on Domain Node)
a. Logon as Websphere process owner (root or wasetlad) on the application (WebSphere Domain) node.
b. Run ‘ /opt/IBM/Domain/InformationServer/ASBServer/bin/MetadataServer.sh stop ‘
c. If above does not work, try ' cd /opt/IBM/WebSphere/AppServer/bin; ./stopServer.sh server1 '
d. If above does not work, try ' cd /opt/IBM/WebSphere/AppServer/bin; ./stopServer.sh server1 -username wasadmin|wasetladmin -password
<password> '
e. Be sure the java processes go away. Check there are no java processes left behind. Remove them if any exists:
i. ' ps -ef | grep java '
ii. ' kill -3 pid ' to get a javacore.yyyymmdd.hhmmss.pid.txt formatted dump file or ' kill pid (NO -9) '.
iii. Run ' cd /opt/IBM/WebSphere/AppServer/bin; ./stopServer.sh server1 ' again to complete stop.
f. If there are any Websphere problems review the logs below: /opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/SystemOut.log
Websphere System Log. /opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/SystemErr.log Websphere Error Log.
/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/stopServer.log Websphere shutdown log.
/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/startServer.log for Websphere start-up log.
4. Stop Database Manager and Database Administration Server
a. List and stop all DB2 connections ' db2 list applications ' & ' db2 force applications all '.
b. Deactivate databases ' deactivate db xmeta ' & ' deactivate db iadb '.
c. Enter ' su - udbi00## -c "db2stop force" ' to stop database manager. If db2stop hangs and the UNIX top command shows that DB2 processes
such as db2sysc are idle, use the ' su – udbc00## -c "db2_kill" ' to kill DB2 processes and release DB2 shared memory and semaphores.
d. Enter ' su - dasusr1 -c "db2admin stop" ' to stop database administration server.
e. Enter ' ps –ef|egrep db2 ' to verify that DB2 processes have stopped.

Now, you can restart, in this order:


1. Start xmeta (DB2, Oracle, whatever)
2. Start WebSphere Server
3. Start ASB Agent
4. Start DataStage

1. Start Database Manager and Database Administration Server


a. Enter ' su - dasusr1 -c "db2admin start" ' to start database administration server (skip).
b. Enter ' su – udbi00## -c "db2start" ' to start database manager.
2. Start WebSphere Server
a. sudo to domain server (ap1 or ha1) as root or wasetlad if Websphere has not been converted to run as non-root.
b. Run ‘ /opt/IBM/Domain/InformationServer/ASBServer/bin/MetadataServer.sh start ‘
c. If it does not start, try ' cd /opt/IBM/WebSphere/AppServer/bin; ./startServer.sh server1 '
d. If it does not start, try ' ./startServer.sh server1 -username wasetladmin -password <password> '
e. If Error: “Cannot start WAS” message then see if WAS left a /opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/###.pid file when
it crashed previously. If that is there, delete the ####.pid file and try to start again.
f. If there are any Websphere problems review the logs below: /opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/SystemOut.log
Websphere System Log. /opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/SystemErr.log Websphere Error Log.
/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/stopServer.log Websphere shutdown log.
/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/startServer.log for Websphere start-up log.
3. Start ASB Node and Logging Agents (Must start as dsadm*** on the conductor node)
a. Logon as dsadm*** on the conductor node.
b. Run ' cd /opt/IBM[/Engine]/InformationServer/ASBNode/bin; ./NodeAgents.sh start ' to start ASB agents.
c. If logging agent component does not start run ' ./LoggingAgent.sh start ' to start logging agent component.
4. Start DataStage on the conductor node.
a. Run ' su - dsadm -c "cd $(cat /.dshome); . ./dsenv; bin/uv -admin -start" '
b. Start resource tracker if it is not running “cd $DSHOME; /opt/IBM/Engine/InformationServer/Server/PXEngine/java/jobmoninit start”

Automated Scripts may be used to stop/start the components of DataStage.


a. Process to stop all components of Information Server using automated scripts.
i. Logon to the conductor node using the dsadm### or root account.
ii. Run ' sudo /opt/IBM/Engine/ha_dir/InfoSrv stop ' to shut down DataStage Engine and ASB nodes.
iii. Enter " ps -ef | egrep 'dscs|dsapi|phantom|dsrpc|dsjob|uvsh|osh.exe|resource_tracke|PID|ascential' " to check for any
hanging DataStage jobs processes or agents. If hanging processes are found,
enter " pkill -9 -f 'dscs|dsapi|phantom|dsrpc|dsjob|uvsh|osh.exe|resource_tracke|ascential' " to kill these processes.
This will require help from a UNIX admin to execute the command.
iv. Logon to the application (Domain) node using the root or dsadm### account.
v. Run ' sudo /opt/IBM/Domain/ha_dir/InfoSrv stop ' to stop Websphere and DB2 UDB.
vi. Enter “ ps -ef|egrep 'db2|java|PID' “ to verify that Websphere and Db2 processes have shut down.
b. Process to start all components of Information Server using automated scripts.
i. Logon to the application (Domain) node using the root or dsadm### account.
ii. Run ' sudo /opt/IBM/Domain/ha_dir/InfoSrv start ' to start DB2 UDB and Websphere. If there are any problems review the logs below:
/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/SystemOut.log Websphere System Log.
/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/SystemErr.log Websphere Error Log.
/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/stopServer.log Websphere shutdown log.
/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/startServer.log for Websphere start-up log.
/udb/udbi00##/sqllib/db2dump/db2diag.log DB2 diagnostic log or use db2diag DB2 command.
iii. Enter “ ps -ef|egrep 'db2|java|PID' “ to verify that Websphere and Db2 processes have started.
iv. Logon to the conductor node using the root or dsadm### account.
v. Run ' sudo /opt/IBM/Engine/ha_dir/InfoSrv start ' to start the ASB Node and DataStage Engine.
vi. Enter " ps -ef | egrep 'dscs|dsapi|phantom|dsrpc|dsjob|uvsh|osh.exe|resource_tracke|PID|ascential' " to check that ASB
node agent, logging agent, dsrpc daemon and resource tracker daemon have started.

You might also like