This content has been marked as final. Show 4 replies
You've probably killed the server completely and need to restart it. Using the kill command as root has its hazards...
Do you have physical access to the server? You may need to "press the button". If it's virtualized you may be able to do this from the virtualization tool.
Hope this helps,
I think I will have to talk to my admin team about it. I hope it's not a serious issue.
Meanwhile It would be a great help if someone could tell me the entire procedure as to how to go about restarting the server.
You may want to check the IPC resources and see if they got cleaned up. You can manually clean them up with "ipcrm ...".
kill -9 -1 tells the operating system to send a SIGKILL (uncatchable signal that causes a process to exit immediately) to all processes with a PID greater than 1, pretty much killing every process on the system other than init. It is unlikely you can recover from this without physical access to the machine.
If you are just trying to administer your Tuxedo application, you should login with a group and user that is the same as Tuxedo was started with, and set up the TUXCONFIG environment variable at a minimum Ideally you should simply source the tux.env file that is in the Tuxedo installation directory as that will set up your path and library paths. Then issue the command "tmshutdown" to shutdown the Tuxedo application. Using kill -9, especially from root is always dangerous as you may kill critical operating system processes. In general kill -9 to any single Tuxedo process isn't a problem as Tuxedo monitors processes and can restart them should they exit unexpectedly.
Oracle Tuxedo Chief Architect