Troubleshooting Server Startup

Checklist for troubleshooting SAP server startup:

What to CheckHow to Check ItTips
Network
  1. Make sure that your database is mounted and open.
  2. Use either Control Panel >> Services >> Oracle TNSListener, or the command lsnrctl (preferable) to start the listener service
  3. execute tnsping
  4. execute tp connect (from /usr/sap/trans/bin dir). If it doesn't work, do a tp go to show the environment variables.
Check listener.ora, tnsnames.ora, sqlnet.ora. Using lsnrctl gives more feedback, which is recorded in the file listener.log. Also see sqlnet.log
Database Use svrmgr or sqldba to check database startup and shutdown:
  1. connect internal
  2. shutdown
  3. startup
  1. add the immediate or abort options to shutdown if necessary
  2. divide startup into phases by starting startup nomount, then continuing with alter database mount and alter database open
  3. try alter database recover after a crash or power failure
Applications After successfully starting the database, start the application services (from NT, use the SAP Service Manager). From UNIX, use the startsap r3 script).
  • Check the logs in the directory usr/sap/SID/DVEBMGS/work
  • For NT, make sure the Oracle and SAP Services are started. Also check that the NT service RPC is started and working (test it by adding a new printer; if the first screen shows up, it should be OK).
SAP DB + Applications If both the DB and applications startup are fine when performed separately, try starting them together with the SAP Service Manager (NT) or startsap (UNIX). For NT, the startsap script can be found in usr/sap/SID/SYS/exe/run/strdbs.cmd

Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

topics