cancel
Showing results for 
Search instead for 
Did you mean: 

I cannot connect to SAP(very High )

Former Member
0 Kudos

Hi all,

I have changed the saposcol program owner from (sid)adm to root when DB and SAP is online.

After that I have restarted SAP and DB.But I cannot connect to SAP from GUI.

i have checked R3trans -d command at OS level.it finished with return code 0000.

but when i check with ps -ef | grep dw the work processes are not generated.

Please kindly help on this immediately

regads

nani

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

Check dev_disp and dev_w0 why the system is not starting. Also check that your listener is running.

--

Markus

Former Member
0 Kudos

When i ran start sap it is showing below

sandbox:sdbadm 5> startsap

Checking SDB Database

-


ABAP Database is not available via R3trans

Checking SDB Database

-


Starting SAP-Collector Daemon

-


20:15:34 08.06.2007 LOG: Effective User Id is root

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

  • This is Saposcol Version COLL 20.85 04/03/01 620 - hpxOscol 07/2003

  • 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 17816) is already running .....

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

saposcol already running

Running /usr/sap/SDB/SYS/exe/run/startdb

Trying to start SDB database ...

Log file: /home/sdbadm/startdb.log

SDB database started

/usr/sap/SDB/SYS/exe/run/startdb completed successfully

Checking SDB Database

-


ABAP Database is running

Starting SAP Instance DVEBMGS00

-


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

Instance on host sandbox started

Listener is starting but work process are not started

Regards

nani

Former Member
0 Kudos

this is result of STOPSAP

sandbox:sdbadm 1> stopsap

Checking SDB Database

-


ABAP Database is running

Checking SDB Database

-


Stopping the SAP instance DVEBMGS00

-


Shutdown-Log is written to /home/sdbadm/stopsap_DVEBMGS00.log

Instance on host sandbox stopped

Waiting for cleanup of resources.........

Running /usr/sap/SDB/SYS/exe/run/stopdb

Trying to stop SDB database ...

Log file: /home/sdbadm/stopdb.log

SDB database stopped

/usr/sap/SDB/SYS/exe/run/stopdb completed successfully

Checking SDB Database

-


ABAP Database is not available via R3trans

sandbox:sdbadm 2>

Regards

Nani

markus_doehr2
Active Contributor
0 Kudos

As I said, check dev_disp and dev_w0 files in your work directory.

Check that your listener is running.

--

Markus

Former Member
0 Kudos

this is my dev_disp result

-


trc file: "dev_disp", trc level: 1, release: "640"

-


Fri Jun 8 20:24:07 2007

kernel runs with dp version 130(ext=102) (@(#) DPLIB-INT-VERSION-130)

length of sys_adm_ext is 312 bytes

sysno 00

sid SDB

systemid 274 (HP (IA-64) with HP-UX)

relno 6400

patchlevel 0

patchno 121

intno 20020600

make: single threaded, ASCII, 64 bit

pid 14349

***LOG Q00=> DpSapEnvInit, DPStart (00 14349) [dpxxdisp.c 1098]

shared lib "dw_xml.sl" version 121 successfully loaded

shared lib "dw_xtc.sl" version 121 successfully loaded

shared lib "dw_stl.sl" version 121 successfully loaded

shared lib "dw_gui.sl" version 121 successfully loaded

shared lib "dw_mdm.sl" version 121 successfully loaded

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpIPCInit2: start server >sandbox_SDB_00 <

DpShMCreate: sizeof(wp_adm) 13440 (840)

DpShMCreate: sizeof(tm_adm) 3082544 (15336)

DpShMCreate: sizeof(wp_ca_adm) 22800 (76)

DpShMCreate: sizeof(appc_ca_adm) 7600 (76)

DpShMCreate: sizeof(comm_adm) 216000 (432)

DpShMCreate: sizeof(vmc_adm) 0 (480)

DpShMCreate: sizeof(wall_adm) (25648/36736/80/104)

DpShMCreate: SHM_DP_ADM_KEY (addr: c00000000e500000, size: 3411296)

DpShMCreate: allocated sys_adm at c00000000e500000

DpShMCreate: allocated wp_adm at c00000000e5018a0

DpShMCreate: allocated tm_adm_list at c00000000e504d20

DpShMCreate: allocated tm_adm at c00000000e504d50

DpShMCreate: allocated wp_ca_adm at c00000000e7f5680

DpShMCreate: allocated appc_ca_adm at c00000000e7faf90

DpShMCreate: allocated comm_adm_list at c00000000e7fcd40

DpShMCreate: allocated comm_adm at c00000000e7fcd60

DpShMCreate: allocated vmc_adm_list at c00000000e831920

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at c00000000e831950

DpShMCreate: allocated wall_adm at c00000000e831960

MBUF state OFF

EmInit: MmSetImplementation( 2 ).

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

Using implementation std

EsIUnamFileMapInit: ES base = 0xc000000080000000

EsStdInit: Extended Memory 4092 MB allocated

<ES> 1022 blocks reserved for free list.

ES initialized.

Fri Jun 8 20:24:17 2007

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG Q0K=> DpMsAttach, mscon ( sandbox) [dpxxdisp.c 9915]

DpStartStopMsg: send start message (myname is >sandbox_SDB_00

<)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

DpMsgAdmin: Set release to 6400, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]

DpMsgAdmin: Set patchno for this platform to 121

Release check o.K.

Fri Jun 8 20:25:12 2007

      • ERROR => W0 (pid 14380) died [dpxxdisp.c 12391]

      • ERROR => W1 (pid 14381) died [dpxxdisp.c 12391]

      • ERROR => W2 (pid 14517) died [dpxxdisp.c 12391]

      • ERROR => W3 (pid 14522) died [dpxxdisp.c 12391]

      • ERROR => W4 (pid 14526) died [dpxxdisp.c 12391]

      • ERROR => W5 (pid 14527) died [dpxxdisp.c 12391]

      • ERROR => W6 (pid 14528) died [dpxxdisp.c 12391]

my types changed after wp death/restart 0xbf --> 0xbe

      • ERROR => W7 (pid 14535) died [dpxxdisp.c 12391]

      • ERROR => W8 (pid 14539) died [dpxxdisp.c 12391]

      • ERROR => W9 (pid 14545) died [dpxxdisp.c 12391]

my types changed after wp death/restart 0xbe --> 0xbc

      • ERROR => W10 (pid 14546) died [dpxxdisp.c 12391]

my types changed after wp death/restart 0xbc --> 0xb8

      • ERROR => W11 (pid 14551) died [dpxxdisp.c 12391]

      • ERROR => W12 (pid 14553) died [dpxxdisp.c 12391]

my types changed after wp death/restart 0xb8 --> 0xb0

      • ERROR => W13 (pid 14559) died [dpxxdisp.c 12391]

my types changed after wp death/restart 0xb0 --> 0xa0

      • ERROR => W14 (pid 14560) died [dpxxdisp.c 12391]

      • ERROR => W15 (pid 14565) died [dpxxdisp.c 12391]

my types changed after wp death/restart 0xa0 --> 0x80

      • DP_FATAL_ERROR => DpWPCheck: no more work processes

      • DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

killing W0-14380 (SIGUSR2)

      • ERROR => DpWpKill(14380, SIGUSR2) failed [dpxxtool.c 2502]

killing W1-14381 (SIGUSR2)

      • ERROR => DpWpKill(14381, SIGUSR2) failed [dpxxtool.c 2502]

killing W2-14517 (SIGUSR2)

      • ERROR => DpWpKill(14517, SIGUSR2) failed [dpxxtool.c 2502]

killing W3-14522 (SIGUSR2)

      • ERROR => DpWpKill(14522, SIGUSR2) failed [dpxxtool.c 2502]

killing W4-14526 (SIGUSR2)

      • ERROR => DpWpKill(14526, SIGUSR2) failed [dpxxtool.c 2502]

killing W5-14527 (SIGUSR2)

      • ERROR => DpWpKill(14527, SIGUSR2) failed [dpxxtool.c 2502]

killing W6-14528 (SIGUSR2)

      • ERROR => DpWpKill(14528, SIGUSR2) failed [dpxxtool.c 2502]

killing W7-14535 (SIGUSR2)

      • ERROR => DpWpKill(14535, SIGUSR2) failed [dpxxtool.c 2502]

: *** ERROR => DpWpKill(14535, SIGUSR2) failed [dpxxtool.c 2502]

killing W8-14539 (SIGUSR2)

      • ERROR => DpWpKill(14539, SIGUSR2) failed [dpxxtool.c 2502]

killing W9-14545 (SIGUSR2)

      • ERROR => DpWpKill(14545, SIGUSR2) failed [dpxxtool.c 2502]

killing W10-14546 (SIGUSR2)

      • ERROR => DpWpKill(14546, SIGUSR2) failed [dpxxtool.c 2502]

killing W11-14551 (SIGUSR2)

      • ERROR => DpWpKill(14551, SIGUSR2) failed [dpxxtool.c 2502]

killing W12-14553 (SIGUSR2)

      • ERROR => DpWpKill(14553, SIGUSR2) failed [dpxxtool.c 2502]

killing W13-14559 (SIGUSR2)

      • ERROR => DpWpKill(14559, SIGUSR2) failed [dpxxtool.c 2502]

killing W14-14560 (SIGUSR2)

      • ERROR => DpWpKill(14560, SIGUSR2) failed [dpxxtool.c 2502]

killing W15-14565 (SIGUSR2)

      • ERROR => DpWpKill(14565, SIGUSR2) failed [dpxxtool.c 2502]

NiWait: sleep (10000 msecs) ...

NiISelect: timeout 10000 ms

NiISelect: maximum fd=13

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Fri Jun 8 20:25:22 2007

NiISelect: TIMEOUT occured (10000 ms)

dump system status

Workprocess Table (long) Fri Jun 8 14:55:22 2007

========================

No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User

Action Table

-


-


0 DIA 14380 Ended no 1 0 0

1 DIA 14381 Ended no 1 0 0

2 DIA 14517 Ended no 1 0 0

3 DIA 14522 Ended no 1 0 0

4 DIA 14526 Ended no 1 0 0

5 DIA 14527 Ended no 1 0 0

6 DIA 14528 Ended no 1 0 0

7 UPD 14535 Ended no 1 0 0

8 UPD 14539 Ended no 1 0 0

9 UPD 14545 Ended no 1 0 0

10 ENQ 14546 Ended no 1 0 0

11 BTC 14551 Ended no 1 0 0

12 BTC 14553 Ended no 1 0 0

13 SPO 14559 Ended no 1 0 0

14 UP2 14560 Ended no 1 0 0

15 UP2 14565 Ended no 1 0 0

Dispatcher Queue Statistics Fri Jun 8 14:55:22 2007

===========================

--------


+
+

+

+
--


+

Typ

now

high

max

writes

reads

--------


+
+

+

+
--


+

NOWP

0

5

2000

7

7

--------


+
+

+

+
--


+

DIA

3

3

2000

3

0

--------


+
+

+

+
--


+

UPD

0

0

2000

0

0

--------


+
+

+

+
--


+

ENQ

0

0

2000

0

0

--------


+
+

+

+
--


+

BTC

0

0

2000

0

0

--------


+
+

+

+
--


+

SPO

0

0

2000

0

0

--------


+
+

+

+
--


+

UP2

0

0

2000

0

0

--------


+
+

+

+
--


+

max_rq_id 11

wake_evt_udp_now 0

wake events total 7, udp 1 ( 14%), shm 6 ( 85%)

since last update total 7, udp 1 ( 14%), shm 6 ( 85%)

Dump of tm_adm structure: Fri Jun 8 14:55:22 2007

=========================

Term uid man user term lastop mod wp ta a/i (modes)

Workprocess Comm. Area Blocks Fri Jun 8 14:55:22 2007

=============================

Slots: 300, Used: 1, Max: 0

--------


+
+
--


+

id

owner

pid

eyecatcher

--------


+
+
--


+

0

DISPATCHER

-1

WPCAAD000

NiWait: sleep (5000 msecs) ...

NiISelect: timeout 5000 ms

NiISelect: maximum fd=13

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Fri Jun 8 20:25:27 2007

NiISelect: TIMEOUT occured (5000 ms)

DpHalt: shutdown server >sandbox_SDB_00 < (normal)

: DpHalt: shutdown server >sandbox_SDB_00 < (normal)

Regards

nani.

Former Member
0 Kudos

Nani,

Stopsap and clean the shared memory and start sap

stopsap

cleanipc <system # > remove

startsap

thanks

prince

markus_doehr2
Active Contributor
0 Kudos

execute (as <sid>adm)

lsnrctl start

and then try to restart your instance.

--

Markus

Former Member
0 Kudos

what can i enter in (system#) place

our db sid is SDB and sap sid is SDB

what is the exact command

regards

nani

markus_doehr2
Active Contributor
0 Kudos

The exact command is

lsnrctl start

as user sdbadm

--

Markus

Former Member
0 Kudos

Hi Markus,

Please find the startdg.log below

  1. pg startsap_DVEBMGS00.log

ERROR : You are user orasdb, but you have to be sdbadm to start this scrip

t

ERROR : You are user orasdb, but you have to be sdbadm to start this scrip

t

  1. pg startdb.log

-


Tue Oct 18 11:51:01 IST 2005

LOGFILE FOR STARTING ORACLE

Trying to start SDB database ...

-


Tue Oct 18 11:51:01 IST 2005

checking required environment variables

ORACLE_HOME is >/oracle/SDB/920_64<

ORACLE_SID is >SDB<

-


Tue Oct 18 11:51:01 IST 2005

check initora

-


Tue Oct 18 11:51:01 IST 2005

check initora

-


Tue Oct 18 11:51:01 IST 2005

checking V2 connect

TNS Ping Utility for HPUX: Version 9.2.0.7.0 - Production on 18-OCT-2005 11:51:0

1

Copyright (c) 1997 Oracle Corporation. All rights reserved.

Used parameter files:

/oracle/SDB/920_64/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (SDU = 32768) (ADDRESS_LIST = (ADDRESS = (C

OMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = sandbox) (PORT = 1527))) (CONNECT

DATA = (SID = SDB) (GLOBALNAME = SDB.WORLD)))

OK (10 msec)

tnsping: V2 connect to SDB

-


Tue Oct 18 11:51:01 IST 2005

Connect to the database to check the database state:

R3trans: connect check finished with return code: 12

Database not available

-


Tue Oct 18 11:51:01 IST 2005

Shutdown database

First trying to shutdown the database - May be,

the database is in the nomount or mount state

-


Tue Oct 18 11:51:02 IST 2005

starting database

SQL*Plus: Release 9.2.0.7.0 - Production on Tue Oct 18 11:51:02 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to an idle instance.

ORACLE instance started.

Total System Global Area 856843872 bytes

Fixed Size 726624 bytes

Variable Size 469762048 bytes

Database Buffers 385032192 bytes

Redo Buffers 1323008 bytes

Database mounted.

Database opened.

Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Producti

on

With the Partitioning option

JServer Release 9.2.0.7.0 - Production

-


Tue Oct 18 11:51:08 IST 2005

Connect to the database to verify, that the database is now open

R3trans check finished with return code: 12

      • ERROR: Startup of database failed

Notify Database Administrator.

/usr/sap/SDB/SYS/exe/run/startdb: Terminating with error code 12

#

Please help on this

Regards

nani

Former Member
0 Kudos

Hi Nani,

"system#" is System Number. I see your is 00.

Please, follow Prince's instructions so you can make a clean restart.

If your "R3trans -d" ends with "0000", your listener is running fine.

Best Regards,

JC Llanes.

Former Member
0 Kudos

thanks a lot prince and Llanes.

now i can login to system but when i ran startsap commend the output is like

sandbox:sdbadm 9> startsap

Checking SDB Database

-


ABAP Database is not available via R3trans

Checking SDB Database

-


Starting SAP-Collector Daemon

-


21:46:14 08.06.2007 LOG: Effective User Id is root

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

  • This is Saposcol Version COLL 20.85 04/03/01 620 - hpxOscol 07/2003

  • 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 18287) is already running .....

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

saposcol already running

Running /usr/sap/SDB/SYS/exe/run/startdb

Trying to start SDB database ...

Log file: /home/sdbadm/startdb.log

SDB database started

/usr/sap/SDB/SYS/exe/run/startdb completed successfully

Checking SDB Database

-


ABAP Database is running

Starting SAP Instance DVEBMGS00

-


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

Instance on host sandbox started

#

in above what is the meaning of ABAP Database is not available via R3trans

Once again thanks to prince and Llanes

Regards

Nani

Former Member
0 Kudos

Nani,

startsap script checks whether database is running or not using R3trans.If it found database is not running it will start the database .If DB is already running it will skip database start and go to next step

Looks everything fine wit your system now.

Thanks

prince

ps: please assign ponts and close the thread if your issue is resolved

Answers (0)