SAP not starting because of database Error

Problem: SAP was not starting, because the dispatcher work process was unable to connect to the database.

Observations:1. Found in the dispatcher log (disp_dev) that all the Work Process were getting killed.
2. Ran R3trans –d and found that the log showed the error

4 ETW000 [dev trc ,00000] Logon as OPS$-user to get SAPSID's password 68 0.066880
4 ETW000 [dev trc ,00000] Connecting as /@SID on connection 0 ... 28 0.066908
4 ETW000 [dev trc ,00000] Allocating service context handle 30 0.066938
4 ETW000 [dev trc ,00000] Allocating server context handle 25 0.066963
4 ETW000 [dev trc ,00000] Attaching to DB Server SID (con_hdl=0,svchp=025EA574,svrhp=025EB17C)
4 ETW000 70 0.067033
4 ETW000 [dev trc ,00000] Assigning server context 025EB17C to service context 025EA574
4 ETW000 40583 0.107616
4 ETW000 [dev trc ,00000] Allocating user session handle 56 0.107672
4 ETW000 [dev trc ,00000] Wed Nov 21 12:19:55 2007 227 0.107899
4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=025EA574,srvhp=025EB17C,usrhp=025F3948)
4 ETW000 39 0.107938
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000 7285 0.115223
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000 34 0.115257
4 ETW000 [dev trc ,00000] Try to connect with default password 95 0.115352
4 ETW000 [dev trc ,00000] Connecting as SAPSID/@SID on connection 0 ...
4 ETW000 29 0.115381
4 ETW000 [dev trc ,00000] Assigning username to user session 025F3948 20 0.115401
4 ETW000 [dev trc ,00000] Assigning password to user session 025F3948 29 0.115430
4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=025EA574,srvhp=025EB17C,usrhp=025F3948)
4 ETW000 35 0.115465
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000 8428 0.123893
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000 32 0.123925
4 ETW000 [dblink ,00419] ***LOG BY2=>sql error 1017 performing CON [dblink#1 @ 419]
4 ETW000 145 0.124070
4 ETW000 [dblink ,00419] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#1 @ 419]
4 ETW000 29 0.124099
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'SID'"

3. When tried to logging into sqlplus “ / as sysdba” from command prompt using the userid (adm), it gave the following error “Insufficient Privileges”




4. Found that the parameter
SQLNET.AUTHENTICATION_SERVICES = was having the value “(NONE)” in file “sqlnet.ora” Parameter file.

5. Changed the parameter to SQLNET.AUTHENTICATION_SERVICES = (NTS), since then it started working

Read More

SAP R/3 dispatcher and work processes

Types of work processes:

Message : Coordinates the communication between different instances of a single SAP R/3 system. Used for Logon purpose and load balancing.

Dispatcher : Redirect the request from GUI client to free process.

Dialog : Interpreting the ABAP code and execute the business logic. Used for interactive online processing.

Batch : For Background jobs.

Enqueue : Single “Central Lock Management Service” that controls the locking mechanism between the different application servers and the database.

Update : Responsible for consistency in asynchronous data changes.

Gateway : Used for transport of bigger amount of data between application servers as well as external (non SAP) systems that communicate with SAP.

Read More

How to "kill" a work process

Stopping Run-Away or “Bad” Work Processes

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM50.

3. On the Process Overview screen, find the process which must be

stopped. Place a √ in the □ to the left of the process number

to be stopped by pressing Space. On the top-most menu bar,

click the Process → Cancel without core.

4. Click the blue arrow circle picture-icon to refresh the Process

Overview screen until the stopped process has cleared from the

display.

5. You may now leave the SM50 transaction.

If this does not kill the process, you can go to transaction SM04 and kill the user’s session. If this does not kill the process, you can log on to the server, open a Task Manager session, and End the Process. If this does not kill the session, there is an executable in the RUN directory on the server called sapntkill.exe. Run it providing the process ID number. If none of the above work, you have no choice but to “bounce” the SAP instance and/or possibly the serve.

Read More