on 05-21-2015 7:17 AM
If your SAP instance is not up now clean all resources left from previous run with
sidadm> cleanipc 00 remove
command and try to start instance again. In case you get the same error check your kernel parameters kernel.shmmax and kernel.shmall.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Experts.
Thanks for your response.
@Roman, i have run the cleanipc 00 remove and restarted the server but the issue still not resolved, please find the kernel details below.
development:d01adm 56> cat /proc/sys/kernel/shmall
5242880
development:d01adm 57> cat /proc/sys/kernel/shmmax
23136829430
Please Help.
Thanks
Mohd
Dear Roman, please find the output below:
development:d01adm 58> ipcs -m
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 29884418 root 644 80 2
0x00000000 29917188 root 644 16384 2
0x00000000 29949957 root 644 280 2
0x00004dc4 30015494 sapadm 760 40141728 1
0x00004dbe 30081032 root 777 802238 1
0x10de813c 42139658 orad01 640 18440257536 19
0x00000000 42172427 d01adm 740 1024 1
0x0382be84 42205196 d01adm 640 4096 3
0x00000000 45744143 d01adm 740 588 1 dest
0x00000000 45776912 d01adm 740 7140072 1 dest
0x00000000 45809681 d01adm 740 13096000 1 dest
0x00000000 45842450 d01adm 740 179368 1 dest
0x00000000 45875219 d01adm 740 6387876 1 dest
Note: the above output was taken when sap & db is up and running.
@Gaurav- Please find the latest dev_w0 file attached, and please cuold you please guide me step by step procedure to preform in the KBA u recomended earlier please.
Thanks
Mohd
Message was edited by: Mohd Basis
hello,
First of all, please check this question:
Are Message Server, a dispatcher and work processes up and running?
Startup sequence
897933 - Start and stop sequence for SAP systems
In short, SAP system instances can be started up by the following sequence:
Database instance
Central instance or (A)SCS
Application servers (Dialog Instances)
also go to cdpro and check dpmon process ...
also check ps –ef | grep sapstartsrv
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Could you RUN the R3trans -d command at OS level and paste the error message here.
Thanks,
BM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mohd,
You have to increase the Kernel memory for Linux OS.
You have to increase kernel.shmmax parameter in /etc/sysctl.conf.
Then activate changes by running the command 'sysctl -p'.
Also do follow the wiki ERROR shmget ... (28: No space left on device), ERROR semget ... (28: No space left on device) - Bas...
I don;t think the problem is with SAPUSER table. If the table SAPUSER , is not present then still SAP connect to the Database by using the defaul user from the table DBA_USERS table.Although to make this work , Your SAP and Database will have to be on the same server.
I think , in your landscape you are having the SAP and Database on the same host.If it is distributed , then SAP will not able to connect to Database with the default mechanism.
If you are not in a situation to change the parameter related to OS kernel , then take a reboot of the server which may resolve your issue.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Basis,
After researching more on issue,found SAP KBA 2105838 - 'shmget' call failed with error number 28 (No space left on device). Failed to create or a...
which corrects Fidel Vales
Suggest you to follow mentioned SAP KBA & above suggestions to resolve your issue.
@Fidel Vales Thanks for correcting.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Follow SAP Notes 662644 - Composite SAP Note: ORA-00942
& 400241 - Problems with ops$ or sapr3 connect to Oracle
Good luck !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gaurav Rana wrote:
Hi,
Follow SAP Notes 662644 - Composite SAP Note: ORA-00942
& 400241 - Problems with ops$ or sapr3 connect to Oracle
Good luck !!
Hi,
That is not the problem.
If you check, it does not find the SAPUSER table but it is able to connect to the database using the default password.
It is a security risk as the default password is known, but it is not the reason the SAP user cannot connect.
It does not seem to be a DATABASE problem but an enqueue one, so I enter in "wters" not familiar to me.
on the dev_w0 I can see the following error:
W =================================================
N SignInit: successfully obtained handle for Security Context cache
N VSI: WP init in ABAP VM completed with rc=0
E Enqueue Info: rdisp/wp_no_enq=1, rdisp/enqname=<empty>, assume development_D01_00
E Enqueue Info: enque/use_pfclock2 = FALSE
E Enqueue Info: row condense enabled
E EnqLockTableCreate: create lock table (size = 33554432)
I *** ERROR => shmget(10034,33554432,2016) (28: No space left on device) [shmux.c 1532]
E *** ERROR => EnqLockTableCreate: size = 33554432 failed. rc = 1 [enxxmini.h 467]
M ***LOG GEF=> [enxxmini.h 468]
M ***LOG GZZ=> Creation of lock table failed [enxxmini.h 469]
M ***LOG GZZ=> Size = 33554432, rc = 1 [enxxmini.h 470]
M in_ThErrHandle: 1
M *** ERROR => ThInit: create lock table (step 1, th_errno 2, action 3, level 1) [thxxhead.c 11422]
it seems that there is not enough memory to create the lock table
Hi,
That is not the problem.
If you check, it does not find the SAPUSER table but it is able to connect to the database using the default password.
It is a security risk as the default password is known, but it is not the reason the SAP user cannot connect.
It does not seem to be a DATABASE problem but an enqueue one, so I enter in "wters" not familiar to me.
Hi,
This is not the solution here,for me now it's completely depends on the current dev_w0 log file,the file which he shared is from Wed May 20 16:58:03 2015 .
I *** ERROR => shmget(10034,33554432,2016) (28: No space left on device) [shmux.c 1532]
E *** ERROR => EnqLockTableCreate: size = 33554432 failed. rc = 1 [enxxmini.h 467]
Issue which you highlighted could be before
As there was oraarch directory full i was unable to access SAP,i have cleared the archive logs
when there was no space on the device.
So the solution of thread depends completely on the availability of current logs from the system.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.