cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot acccess SAP via GUI after kernel upgrade

Former Member
0 Kudos

Hi SAP GURUs,

Assistance please,

After we upgraded the kernel from 133 to 185 ( Solaris Server, ECC 6) and then restart the system. We able to start the SAP system without error message. But when we tried to login thru SAP GUI, we cannot login to the system.(no network issue).

return code -10

error no 10061

error text: WSAECONNREFUSED: CONNECTION REFUSED

What logs do we need to check for errors? What command tools do we need to execute to check errors?

Thanks,

vin

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Vin,

You need to give imp trace file( dispachter, dev_w* etc)

Check SAP NOte 1202542 - Error: "WSAECONNREFUSED: connection refused" when trying to log on to the SAPGui

Thanks,

Sushil

Edited by: Sushil Suryawanshi on Jun 16, 2009 5:31 PM

markus_doehr2
Active Contributor
0 Kudos

> After we upgraded the kernel from 133 to 185 ( Solaris Server, ECC 6) and then restart the system. We able to start the SAP system without error message.

If you get the below message I doubt that the system was started.

Please check

dev_disp

dev_w0

Markus

Former Member
0 Kudos

Hi Markus,

Sorry, i'm still new in SAP administration.

How do I check the following?

dev_disp

dev_w0

Thanks!

vin

Former Member
0 Kudos

Hi,

From OS level check the trace files from usr/sap/SID/DVEBMGSXX/work path

Here xx means system number

Thanks

Sushil

markus_doehr2
Active Contributor
0 Kudos

> Sorry, i'm still new in SAP administration.

> How do I check the following?

>

> dev_disp

> dev_w0

No offense but you shouldn't do kernel upgrades if you have no clue how the system works

logon as <sid>adm

enter

cdD
cd work
vi dev_w0

Markus

Former Member
0 Kudos

Hi Sushil,

What trace file I'm going to check?

I have sapstartsrv.log below:

bash-3.00$ more sapstartsrv.log

-


trc file: "sapstartsrv.log", trc level: 0, release: "700"

-


pid 5756

Tue Jun 16 12:29:38 2009

No halib defined => HA support disabled

Initializing SAPControl Webservice

SapSSLInit failed => https support disabled

Starting WebService thread

Webservice thread started, listening on port 50013

Trusted http connect via Unix domain socket '/tmp/.sapstream50013' enabled.

Thanks,

vin

markus_doehr2
Active Contributor
0 Kudos

> What trace file I'm going to check?

The trace files

dev_disp

dev_w0

Markus

Former Member
0 Kudos

Hi Markus,

No worries, not offended, Thanks for helping.

Actually, I already done a kernel update without error in one of our SAP Server. I thought it just a copy paste procedure.Anyway, is this the log that we need?

bash-3.00$ more dev_w0

-


trc file: "dev_w0", trc level: 1, release: "700"

-


*

  • ACTIVE TRACE LEVEL 1

  • ACTIVE TRACE COMPONENTS all, MJ

*

M sysno 00

M sid ECD

M systemid 370 (Solaris on SPARCV9 CPU)

M relno 7000

M patchlevel 0

M patchno 185

M intno 20050900

M make: single threaded, Unicode, 64 bit, optimized

M pid 5527

M

M

M Tue Jun 16 12:26:36 2009

M kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)

M length of sys_adm_ext is 576 bytes

M ***LOG Q01=> ThInit, WPStart (Workproc 0 1 5527) [thxxhead.c 1290]

M ThInit: running on host pnocecdev1

M calling db_connect ...

C Oracle Client Version: '10.2.0.2.0'

C Client NLS settings: AMERICAN_AMERICA.UTF8

C Logon as OPS$-user to get SAPSR3's password

C Connecting as /@ECD on connection 0 (nls_hdl 0) ... (dbsl 700 030508)

C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch

C 0 UTF8 1 0x1073b64c0 0x1073bdf80 0x1073ce718

C Attaching to DB Server ECD (con_hdl=0,svchp=0x1073ce648,srvhp=0x1073d0998)

C Starting user session (con_hdl=0,svchp=0x1073ce648,srvhp=0x1073d0998,usrhp=0x1073be798)

C Now '/@ECD' is connected: con_hdl=0, nls_hdl=0, session_id=214.

C Got SAPSR3's password from OPS$-user

C Disconnecting from connection 0 ...

C Closing user session (con_hdl=0,svchp=0x1073ce648,usrhp=0x1073be798)

C Now I'm disconnected from ORACLE

C Connecting as SAPSR3/<pwd>@ECD on connection 0 (nls_hdl 0) ... (dbsl 700 030508)

C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch

C 0 UTF8 1 0x1073b64c0 0x1073bdf80 0x1073ce718

C Starting user session (con_hdl=0,svchp=0x1073ce648,srvhp=0x1073d0998,usrhp=0x1073be798)

C Now 'SAPSR3/<pwd>@ECD' is connected: con_hdl=0, nls_hdl=0, session_id=214.

C Database NLS settings: AMERICAN_AMERICA.UTF8

C DB instance ECD is running on pnocecdev1 with ORACLE version 10.2.0.2.0 since JUN 16, 2009, 12:26:07

B Connection 0 opened (DBSL handle 0)

B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost

B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20090616 122636 pnocecdev1

C build_stmt: reallocating stmt buffer: 256 -> 2000 characters

M db_connect o.k.

M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.wa

r,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif

I

I Tue Jun 16 12:26:38 2009

I MtxInit: 0 0 0

M SHM_PRES_BUF (addr: 0xffffffff60c00000, size: 20000000)

M SHM_ROLL_AREA (addr: 0xfffffffe4a000000, size: 134217728)

M SHM_PAGING_AREA (addr: 0xfffffffe40000000, size: 134217728)

M SHM_ROLL_ADM (addr: 0xffffffff7397a000, size: 2672386)

M SHM_PAGING_ADM (addr: 0xffffffff77a00000, size: 656416)

M ThCreateNoBuffer allocated 572152 bytes for 1000 entries at 0xfffffffe3a004000

M ThCreateNoBuffer index size: 3000 elems

M ThCreateVBAdm allocated 12176 bytes (50 server) at 0xffffffff77c00000

X EmInit: MmSetImplementation( 2 ).

X MM global diagnostic options set: 0

X <ES> client 0 initializing ....

X Using implementation std

X <ES> Info: use normal pages (no huge table support available)

X ES initialized.

X mm.dump: set maximum dump mem to 96 MB

B dbntab: NTAB buffers attached

B dbntab: Buffer FTAB(hash header) (addr: 0xfffffffe3a092088, size: 584)

B dbntab: Buffer FTAB(anchor array) (addr: 0xfffffffe3a0922d0, size: 480104)

B dbntab: Buffer FTAB(item array) (addr: 0xfffffffe3a107638, size: 1920000)

B dbntab: Buffer FTAB(data area) (addr: 0xfffffffe3a2dc238, size: 6144000)

B dbntab: Buffer IREC(hash header) (addr: 0xfffffffe3a8bc088, size: 584)

B dbntab: Buffer IREC(anchor array) (addr: 0xfffffffe3a8bc2d0, size: 480104)

B dbntab: Buffer IREC(item array) (addr: 0xfffffffe3a931638, size: 480000)

B dbntab: Buffer IREC(data area) (addr: 0xfffffffe3a9a6938, size: 8192000)

B dbntab: Buffer STAB(hash header) (addr: 0xfffffffe3b17a088, size: 584)

B dbntab: Buffer STAB(anchor array) (addr: 0xfffffffe3b17a2d0, size: 480104)

B dbntab: Buffer STAB(item array) (addr: 0xfffffffe3b1ef638, size: 480000)

B dbntab: Buffer STAB(data area) (addr: 0xfffffffe3b264938, size: 3072000)

B dbntab: Buffer TTAB(hash header) (addr: 0xfffffffe3b556088, size: 3288)

B dbntab: Buffer TTAB(anchor array) (addr: 0xfffffffe3b556d60, size: 480104)

B dbntab: Buffer TTAB(item array) (addr: 0xfffffffe3b5cc0c8, size: 1200000)

B dbntab: Buffer TTAB(data area) (addr: 0xfffffffe3b6f1048, size: 8760000)

B db_con_shm_ini: WP_ID = 0, WP_CNT = 26, CON_ID = -1

B dbstat: TABSTAT buffer attached (addr: 0xfffffffe36013808)

I *** ERROR => shmget(10019,99999832,2016) (22: Invalid argument) [shmux.c 1556]

B dbtbxbuf: Shm Segment 19: Cannot attach

B ***LOG BBB=> ADM message TBX buffer: function shmcreate0 returns RC = 256 [dbtbxbuf#3 @ 16118] [d

btbxbuf1611 8]

B ***LOG BZL=> internal error in table buffer: table buf init fail [dbtbxbuf#3 @ 1701] [dbtbxbuf1701 ]

B dbtbxbuf: return code (sap_rc): 2, Buffer TBX_GENERIC will not be available

B db_tblinit failed

M *** ERROR => ThCallHooks: event handler db_init for event CREATE_SHM failed [thxxtool3.c 261]

M *** ERROR => ThIPCInit: hook failed [thxxhead.c 2105]

M ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c 1532]

M in_ThErrHandle: 1

M *** ERROR => ThInit: ThIPCInit (step 1, th_errno 17, action 3, level 1) [thxxhead.c 10524]

M

M Info for wp 0

M

M pid = 5527

M severity = 0

M status = 0

M stat = WP_RUN

M waiting_for = NO_WAITING

M reqtype = DP_RQ_DIAWP

M act_reqtype = NO_REQTYPE

M rq_info = 0

M tid = -1

M mode = 255

M len = -1

M rq_id = 65535

M rq_source =

M last_tid = 0

M last_mode = 0

M semaphore = 0

M act_cs_count = 0

M csTrack = 0

M csTrackRwExcl = 0

M csTrackRwShrd = 0

M mode_cleaned_counter = 0

M control_flag = 0

M int_checked_resource(RFC) = 0

M ext_checked_resource(RFC) = 0

M int_checked_resource(HTTP) = 0

M ext_checked_resource(HTTP) = 0

M report = > <

M action = 0

M tab_name = > <

M attachedVm = no VM

M PfStatDisconnect: disconnect statistics

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 723]

M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 261]

M ThCallHooks: call hook >BtcCallLgCl< for event BEFORE_DUMP

M Entering ThSetStatError

M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workproc 0 5527) [dpuxtool.c 269]

Thanks!

vin

markus_doehr2
Active Contributor
0 Kudos

> Actually, I already done a kernel update without error in one of our SAP Server. I thought it just a copy paste procedure.Anyway, is this the log that we need?

yes.

This is your problem:

> I *** ERROR => shmget(10019,99999832,2016) (22: Invalid argument) [shmux.c 1556]

> B dbtbxbuf: Shm Segment 19: Cannot attach

> B ***LOG BBB=> ADM message TBX buffer: function shmcreate0 returns RC = 256 [dbtbxbuf#3 @ 16118] [d

The OS is unable to create a shared memory segment. This happens, because your operating system is not configured properly.

Read Note 724713 - parameter settings for Solaris 10

It will tell you what you need to do (create an /etc/project and /etc/user_attr with proper values).

After you've done that do a SHUTDOWN of the SAP instance first, log off completely (and then restart).

Markus

Former Member
0 Kudos

see DEV_DISP

bash-3.00$ more dev_disp

-


trc file: "dev_disp.new", trc level: 1, release: "700"

-


sysno 00

sid ECD

systemid 370 (Solaris on SPARCV9 CPU)

relno 7000

patchlevel 0

patchno 185

intno 20050900

make: single threaded, Unicode, 64 bit, optimized

pid 5516

Tue Jun 16 12:26:35 2009

kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)

length of sys_adm_ext is 576 bytes

      • SWITCH TRC-HIDE on ***

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

shared lib "dw_xml.so" version 185 successfully loaded

shared lib "dw_xtc.so" version 185 successfully loaded

shared lib "dw_stl.so" version 185 successfully loaded

shared lib "dw_gui.so" version 185 successfully loaded

shared lib "dw_mdm.so" version 185 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >pnocecdev1_ECD_00 <

DpShMCreate: sizeof(wp_adm) 45760 (1760)

Tue Jun 16 12:26:41 2009

CCMS: start to initalize 3.X shared alert area (first segment).

      • ERROR => DpWPCheck: W0 (pid 5527) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5527) exited with exit code 255

      • ERROR => DpWPCheck: W1 (pid 5528) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5528) exited with exit code 255

      • ERROR => DpWPCheck: W2 (pid 5529) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5529) exited with exit code 255

      • ERROR => DpWPCheck: W3 (pid 5530) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5530) exited with exit code 255

      • ERROR => DpWPCheck: W4 (pid 5535) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5535) exited with exit code 255

child (pid=5573) exited with exit code 255

      • ERROR => DpWPCheck: W17 (pid 5574) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5574) exited with exit code 255

      • ERROR => DpWPCheck: W18 (pid 5577) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5577) exited with exit code 255

      • ERROR => DpWPCheck: W19 (pid 5582) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5582) exited with exit code 255

      • ERROR => DpWPCheck: W20 (pid 5583) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5583) exited with exit code 255

      • ERROR => DpWPCheck: W21 (pid 5586) died (severity=0, status=65280) [dpxxdisp.c 15555]

child (pid=5586) exited with exit code 255

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

hmCleanup( 62 )

ShmCreate( 62, 0, 2, 0x0xffffffff7fffe848 )

ShmProtect( 62, 3 )

ShmProtect( key 62 valid )

ShmProtect( slot Index 61 )

ShmProtect( Mode: 0 )

ShmProtect( before shmdt )

ShmProtect( after shmdt )

ShmProtect( before shmat )

ShmKeySharedMMU( 62 ) = 0 (octal)

ShmProtect( after shmat )

ShmProtect: shmat key 62 prot 3/0 done

ShmCreate( 62, 0, 2, -> 0x0xfffffffe5a000000 )

MpiCleanup() -> 0

removing Semaphore-Management

closing connect handles (dgm + tcp)

DpDelSocketInfo: del info for socket 0 (type=2)

NiICloseHandle: shutdown and close hdl 0 / sock 8

DpDelSocketInfo: del info for socket 1 (type=1)

NiICloseHandle: shutdown and close hdl 1 / sock 9 - sock 10

***LOG Q05=> DpHalt, DPStop ( 5516) [dpxxdisp.c 11257]

      • shutdown completed - server stopped ***

Good Bye .....

bash-3.00$

Former Member
0 Kudos

Hi Markus,

Is this the exact values and correct command that we need to execute?

Following is an example for the above steps:

$ projadd -p 200 -c "SAP System PRD" -U prdadm,oraprd \

-K "project.max-sem-ids=(priv,1024,deny)" \

-K "process.max-sem-nsems=(priv,2048,deny)" \

-K "project.max-shm-ids=(priv,256,deny)" \

-K "project.max-shm-memory=(priv,18446744073709551615,deny)" \

PRD

Thanks!

vin

markus_doehr2
Active Contributor
0 Kudos

> Is this the exact values and correct command that we need to execute?

I don't know. I don't know your hardware, what your run on it, how the parameters in the system are configured etc. Those are example values, they need to be adapted according to the system configuration.

> $ projadd -p 200 -c "SAP System PRD" -U prdadm,oraprd \

> -K "project.max-sem-ids=(priv,1024,deny)" \

> -K "process.max-sem-nsems=(priv,2048,deny)" \

> -K "project.max-shm-ids=(priv,256,deny)" \

I would definitely increase the number of id's to 1024 also

> -K "project.max-shm-memory=(priv,18446744073709551615,deny)" \

> PRD

Do that and also add the users prdadm and oraprd to /etc/user_attr as mentioned in the note.

Markus

Former Member
0 Kudos

Hi Markus,

What other requirements we need to consider for the project parameters?

T.Y.

vnoy

markus_doehr2
Active Contributor
0 Kudos

Depending on how many open files/network connection you will have you may also set "process.max-file-descriptors".

The project files are upper limits, they don't "reserve" memory so you can go higher with the values without any risk. They can be changed online (no need to reboot).

You also need to set

set rlim_fd_cur=65535

in /etc/system (as mentioned in the note). Setting that parameter requires once a reboot.

All other configurations are listed in the installation guide.

You may also check

Note 892631 - Solaris: mount options for best performance

Note 999524 - Oracle 10.2 platform support for Async IO

Markus

Former Member
0 Kudos

Hi Markus,

Is this error below will be address by the same solution with by the " PROJECT parameters "

I already able to login via SAP GUI after I free up the / (root) filesystem of Solaris.

But when I login to SAP GUI the error below occured.

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

Runtime Errors PXA_NO_SHARED_MEMORY

Date and Time 06/17/2009 19:57:41

Short text

300000 kilo bytes of shared memory for PXA not available.

What happened?

When starting the R/3 System, 300000 Kbytes of storage space

was required for the ABAP/4 program buffer (PXA), but this

was not available.

The system was started as an emergency system and is not fully

operational.

It is intended only for display and to eliminate errors.

Under no circumstances should it be used for production

purposes.

Error analysis

The error probably occurred when installing the

R/3 system.

The return code of the SAP shared memory control was 1.

The error reported by the operating system is:

Error number..... 22

Error text....... "Invalid argument"

Trigger Location of Runtime Error

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

Here's a partial error logs from DEV_W0

-PXA--


A

M *** ERROR => ThrInitRunTime: ab_init failed (-1) [thxxrun1.c 191]

M *** ERROR => ThrInitRunTime failed (-1) [thxxext.c 885]

M ***LOG R19=> ThInit, ThStartUp2 ( RUNT-000001) [thxxhead.c 1857]

M in_ThErrHandle: 1

M *** ERROR => ThInit: ThStartUp2 (step 1, th_errno 5, action 3, level 1) [thxx

head.c 10524]

M

M Info for wp 0

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

Thanks,

vnoy

Edited by: vnoy on Jun 17, 2009 3:25 PM

Former Member
0 Kudos

other error logs.

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

Runtime Errors PXA_NO_SHARED_MEMORY

Date and Time 06/17/2009 19:57:41

Short text

300000 kilo bytes of shared memory for PXA not available.

What happened?

When starting the R/3 System, 300000 Kbytes of storage space

was required for the ABAP/4 program buffer (PXA), but this

was not available.

The system was started as an emergency system and is not fully

operational.

It is intended only for display and to eliminate errors.

Under no circumstances should it be used for production

purposes.

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

Cheers!

vnoy

Former Member
0 Kudos

Hi,

PXA_NO_SHARED_MEMORY is ABAP buffer related dump. can you check number of Swaps for ABAP buffer in tcode ST02. You need to increase its size by 20-30 % & try.

Thanks

Sushil

markus_doehr2
Active Contributor
0 Kudos

> Is this error below will be address by the same solution with by the " PROJECT parameters "

> I already able to login via SAP GUI after I free up the / (root) filesystem of Solaris.

I'm not sure how this is related to your original problem. The "no free space" is a return code from a shared memory call (can be misleading).

> -PXA--


> A

> M *** ERROR => ThrInitRunTime: ab_init failed (-1) [thxxrun1.c 191]

> M *** ERROR => ThrInitRunTime failed (-1) [thxxext.c 885]

> M ***LOG R19=> ThInit, ThStartUp2 ( RUNT-000001) [thxxhead.c 1857]

> M in_ThErrHandle: 1

> M *** ERROR => ThInit: ThStartUp2 (step 1, th_errno 5, action 3, level 1) [thxx

> head.c 10524]

> M

> M Info for wp 0

This is not the problem, just the information that the initialization of the memory failed.

Apparently not all programs running with the new settings.

Try the following:

a) stop system and database and reboot the machine

or

b) stop database, stop listener, stop all processes running under <sid>adm (including sapstartsrv) and also saposcol, logoff all the terminals and re-login. The check using

projects -l `projects -d <userid>`

if the settings are as in /etc/project. If yes, start database, listener and system again. The system should now come up completely and no more error messages should be logged in the dev_w* traces.

Markus

Former Member
0 Kudos

Hi Sushil,

Below is the output from ST02, any important stats here?

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

Buffer HitRatio % Alloc. KB Freesp. KB % Free Sp. Dir. Size FreeDirEnt % Free Dir Swaps DB Acc

Nametab (NTAB) 0

Table definition 89,35 6.798 4.491 78,75 20.000 15.749 78,75 0 7.422

Field definition 93,26 31.563 23.210 77,37 20.000 16.334 81,67 0 4.294

Short NTAB 99,27 3.625 2.915 97,17 5.000 4.693 93,86 0 307

Initial records 54,14 6.625 4.961 82,68 5.000 3.783 75,66 0 1.217

0

program 92,20 32.768 450 1,50 8.192 7.155 87,34 5.458 19.545

CUA 96,31 3.000 2.038 85,34 1.500 1.457 97,13 0 72

Screen 99,20 4.297 3.785 92,47 2.000 1.964 98,20 0 36

Calendar 100,00 488 359 75,10 200 29 14,50 0 171

OTR 100,00 4.096 3.282 100,00 2.000 2.000 100,00 0

0

Tables 0

Generic Key 99,13 29.297 7.241 26,09 5.000 2.340 46,80 0 2.672

Single record 61,67 10.000 6.896 70,14 500 467 93,40 0 19.304

0

Export/import 37,57 4.096 3.186 97,07 2.000 1.964 98,20 0

Exp./ Imp. SHM 4.096 3.282 100,00 2.000 2.000 100,00 0

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

Thanks!

vnoy

Former Member
0 Kudos

Hi Markus,

I already restarted the SAP application and Server but still no luck, Same error.

regards,

Vnoy

markus_doehr2
Active Contributor
0 Kudos

> I already restarted the SAP application and Server but still no luck, Same error.

Did you also end/cancel/kill all the SAP application server related processes? "stopsap" does not stop sapsoscol nor does it stop sapstartsrv.

Please see my above posting.

If it does still not work please post dev_w0 again.

Markus

Former Member
0 Kudos

Hi Markus,

I already stop all SAP services including sapstartsrv and saposcol, still same problem when login to SAP GUI.

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

Runtime Errors PXA_NO_SHARED_MEMORY

Date and Time 18.06.2009 08:31:05

Short text

300000 kilo bytes of shared memory for PXA not available.

What happened?

When starting the R/3 System, 300000 Kbytes of storage space

was required for the ABAP/4 program buffer (PXA), but this

was not available.

The system was started as an emergency system and is not fully

operational.

It is intended only for display and to eliminate errors.

Under no circumstances should it be used for production

purposes.

Error analysis

The error probably occurred when installing the

R/3 system.

The return code of the SAP shared memory control was 1.

The error reported by the operating system is:

Error number..... 22

Error text....... "Invalid argument"

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

partial logs from dev_w0

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

-PXA--

-


A PXA INITIALIZATION

A PXA: Locked PXA-Semaphore.

A System page size: 8kb, total admin_size: 20384kb, dir_size: 20328kb.

I *** ERROR => shmget(10006,307200000,2016) (22: Invalid argument)

A RABAX in run level 1

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

Thu Jun 18 08:29:40 2009

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

A ** RABAX: level LEV_RX_ROLLBACK completed.

A ** RABAX: level LEV_RX_DB_ALIVE entered.

A ** RABAX: level LEV_RX_DB_ALIVE completed.

A ** RABAX: level LEV_RX_HOOKS entered.

A ** RABAX: level LEV_RX_HOOKS completed.

A ** RABAX: level LEV_RX_STANDARD entered.

A ** RABAX: level LEV_RX_STANDARD failed.

A ** RABAX: level LEV_RX_STOR_VALUES entered.

A ** RABAX: level LEV_RX_STOR_VALUES completed.

A ** RABAX: level LEV_RX_C_STACK entered.

A ** RABAX: level LEV_RX_C_STACK completed.

A ** RABAX: level LEV_RX_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_MEMO_CHECK completed.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A ** RABAX: level LEV_RX_INTERFACES entered.

A ** RABAX: level LEV_RX_INTERFACES completed.

A ** RABAX: level LEV_RX_GET_MESS entered.

A ** RABAX: level LEV_RX_GET_MESS completed.

A ** RABAX: level LEV_RX_INIT_SNAP entered.

A ** RABAX: level LEV_RX_INIT_SNAP completed.

A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.

X *** ERROR => invalid MM administration (adm) (nil) (admCheck)(nil)

A ** RABAX: level LEV_RX_WRITE_SNAP_BEG failed.

A ** RABAX: level LEV_RX_WRITE_SNAP entered.

A ** RABAX: level LEV_SN_END completed.

A ** RABAX: level LEV_RX_WRITE_SNAP_END entered.

A ** RABAX: level LEV_RX_WRITE_SNAP_END completed.

A ** RABAX: level LEV_RX_SET_ALERT entered.

A ** RABAX: level LEV_RX_SET_ALERT completed.

A ** RABAX: level LEV_RX_COMMIT entered.

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

Error Code PXA_NO_SHARED_MEMORY.

A Module $Id: //bas/700_REL/src/krn/runt/abload3.c#40 $ SAP.

A Function ab_pbinit Line 1906.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

Shared Memory von 300000 Kilo-Bytes für PXA nicht verfügbar..

A

A *** Allocation of PXA failed.

A *** Shared Memory in size 300000K not available.

A *** Starting up system in emergency mode.

A *** Please don't use as productive system.

A *** Please decrease value of profile parameter

A *** abap/buffersize and restart the system.

A *** For further information please refer to note 307976.

A **GENER Trace switched on ***

A PXA: Locked PXA-Semaphore.

A System page size: 8kb, total admin_size: 2712kb, dir_size: 2656kb.

A PXA allocated (address 0xfffffffe3e000000, size 32768K)

A System name

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

ABAP Program SAPMSYST .

A Source SAPMSYST Line 1766.

A Error Code PXA_NO_SHARED_MEMORY.

A Module $Id: //bas/700_REL/src/krn/runt/abload3.c#40 $ SAP.

A Function ab_pxa_check_shared_memory Line 12218.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A ** RABAX: level LEV_RX_ERROR_SAVE entered.

A ** RABAX: level LEV_RX_ERROR_SAVE completed.

A ** RABAX: level LEV_RX_ERROR_TPDA entered.

A ** RABAX: level LEV_RX_ERROR_TPDA completed.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A ** RABAX: level LEV_RX_END entered.

A ** RABAX: level LEV_RX_END completed.

A ** RABAX: end no http/smtp

A ** RABAX: end RX_GOTO_RABAX

A 300000 kilo bytes of shared memory for PXA not available..

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

Thank you,

vnoy

Edited by: vnoy on Jun 18, 2009 2:52 AM

Edited by: vnoy on Jun 18, 2009 2:53 AM

Edited by: vnoy on Jun 18, 2009 2:54 AM

markus_doehr2
Active Contributor
0 Kudos

> -PXA--


> A PXA INITIALIZATION

> A PXA: Locked PXA-Semaphore.

> A System page size: 8kb, total admin_size: 20384kb, dir_size: 20328kb.

> I *** ERROR => shmget(10006,307200000,2016) (22: Invalid argument) [shmux.c 1556]

> A RABAX in run level 1

that's still a shared memory problem.

Please post the output of the commands of my last post.

Markus

Former Member
0 Kudos

Hi SAP Gurus,

Our SAP system is now running without the errors.

What we did was updated the following parameters as per SAP Note 103747:

ztta/roll_area = 6500000

zcsa/table_buffer_area = 50000000

zcsa/presentation_buffer_area = 20000000

zcsa/db_max_buftab = 10000

rsdb/obj/buffersize = 20000

rtbb/buffer_length = 30000

Also with the reference from OSS Note 103747 and 146289.

Thanks for your assistance.

Cheers!

vnoy