cancel
Showing results for 
Search instead for 
Did you mean: 

After ./sapstart ,not able to login

Former Member
0 Kudos

Dear Experts,

After increasing the size of /oracle , i am not able to login through SAPGUI. Our /Oracle directory was full, so we increased the size and start the ./sapstart.

SAPECCDEV:devadm 6> ./startsap

Checking DEV Database

-


ABAP Database is running

Starting SAP-Collector Daemon

-


16:33:48 29.09.2009 LOG: Effective User Id is root

***********************************************************************

  • This is Saposcol Version COLL 20.95 700 - V2.6.1 2007-06-14 HP-UX PA-RISC

  • Usage: saposcol -l: Start OS Collector

  • saposcol -k: Stop OS Collector

  • saposcol -d: OS Collector Dialog Mode

  • saposcol -s: OS Collector Status

  • The OS Collector (PID 3638) is already running .....

************************************************************************

saposcol already running

Running /usr/sap/DEV/SYS/exe/run/startj2eedb

Trying to start DEV database ...

Log file: /home/devadm/startdb.log

/usr/sap/DEV/SYS/exe/run/startj2eedb completed successfully

Starting SAP Instance SCS01

-


Startup-Log is written to /home/devadm/startsap_SCS01.log

Instance Service on host SAPECCDE started

Instance already running

Starting SAP Instance DVEBMGS00

-


Startup-Log is written to /home/devadm/startsap_DVEBMGS00.log

Instance Service on host SAPECCDE started

Instance already running

SAPECCDEV:devadm 7>

-


After that i am trying to start ./sapstart, it is not allowing me to login

Please help me out

Regards

Ajit

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

You might want to run stopsap and then cleanipc to remove any shared memory segments (full command will be something like 'cleanipc 00 remove'). The try running startsap to see what happens.

Hope that helps.

J. Haynes

Former Member
0 Kudos

Dear Joe Haynes,

You made my day, Cheers!!!

Many Many thanks to you, as you suggested cleanipc, i did and problem got resolved.

Really thanks to you and everybody who tried to help me out.

Warm Regards,

Ajit

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Ajit,

The instance has already been started. Where are you trying to login and whats the error/warning message you are getting while doing so.

Regards,

Varadhu

Former Member
0 Kudos

Dear Varadhu,

Once i click on GUI, it says partner'192.168.51.31':sapdp00 not reached.

Regards,

Ajit

Former Member
0 Kudos

If no work processes are running you won't be able to reach the system - therefore the ouput is normal.

But did you actually restart the whole system while patching it and the /oracle dir got full? You did not check /oracle/SID/oraarch in order to find out whether the archives from oracle need to be saved and afterwards deleted?

In case you performed a shutdown while patching - I hope you backed up your system right before you attempted to patch. Otherwise you might just have killed your system because it got haywire while trying to apply the SAP_APPL patches and got shutdown.

Former Member
0 Kudos

Perform a check with ps -ef | grep <SID> to see whether there are any work processes running once you restarted the system. Also check the trace files for within /usr/sap/SID/Instance/work - maybe you find a reason there.

Former Member
0 Kudos

Dear Dinter,

Thanks for your promt reply.

After ps -ef | grep DEV there are no any work processes running. Also I am trying to check the trace files for within /usr/sap/SID/Instance/work. Could you please tell me some specific file to check.

Actually i was applying SAP_APPL patches and /oracle directory got full, so i increased the oracle size and then restarted the ./startsap. But i am not able to login again. I am strugling hard to login again. Please help me out.

Thanks n Regards

Ajit

Former Member
0 Kudos

Check the trace files of the work processes: dev_wp## (## = number of WP process) --> there should be a hint why the work process was stopped.

It might also be helpful to check the file dev_disp (trace of the dispatcher).

anindya_bose
Active Contributor
0 Kudos

If nothing works , stop SAP, stop database, restart the server ( if possible) and then start everything afresh.