on 01-11-2007 5:17 PM
Hi
My sap is running fine but the problem i face is when i log on to maxdb wirth database manager and cilck on anything i get the below error
-24994 RUNTIME ENVIRONMENT ERROR [PARAM_STARTSESSION ] ; -24724, ERR_RESLOCK_NO_LOCK : RESOURCE PARAMACCESS NOT LOCKED
I am not able to view any details in database manager gui but my SAP is working with few tcodes like db02 and other related to db is not working.
Please respond ASAP. Thanks in advance
Cheers
Arun
Hello Arun,
Could you please provide more information:
-> What version of the DBMGUI are you using?
-> What version of the database do you have?
Please logon to the database server & update with the output of the following commands:
dbmcli -s inst_enum
dbmcli -s db_enum
sdbregview -l
dbmcli -d <DB-name> -u <dbm_user>,<pwd> db_state
dbmcli -d <DB-name> -u <dbm_user>,<pwd> param_directgetall
xinstinfo <DB-name>
-> With the output of the command 'xinstinfo <DB-name>' you will see the IndepData value. Please review the files at <IndepData>/config directory. Please give the list of the files. Please check, if you have <DB-name>,<DB-name>.01 & <DB-name>.pah files. What size & when they were changed.
-> Are DBMGUI & database running on the same server?
If not =>
When you add the Database Instance to be monitored in DBMGUI what OS user you use?
-> You wrote: "I am not able to view any details in database
manager gui but my SAP is working with few tcodes like db02
and other related to db is not working."
Could you please give example of the not working.
Was the database working before & when the problems started?
Thank you and best regards, Natalia Khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Natalia,
I am using 7.6 version of Maxdb database and DBMGUI.
the below command executed in offlline mode as am not able to bring it online
inst_enum
OK
7.6.00.18 f:\sapdb\asm\db
7.6.00.18 c:\program files\sdb\7600
140.1.1.61:ASM> db_enum
OK
ASM f:\sapdb\asm\db 7.6.00.18 slow offline
ASM f:\sapdb\asm\db 7.6.00.18 fast offline
140.1.1.61:ASM> param_directgetall
ERR
-24994,ERR_RTE: Runtime environment error
-24724,ERR_RESLOCK_NO_LOCK: Resource ParamAccess not locked
-24726,ERR_SHMLINESEXCEEDED: Too many lines of type 1
140.1.1.61:ASM> db_state
OK
State
OFFLINE
the below is the KINDIAG.ERR file last few lines
7.6.00 Build 018-123-119-055
2006-12-06 18:35:16 --- Starting GMT 2006-12-06 14:35:16 7.6.00 Build 018-123-119-055
2006-12-14 17:36:02 0xB68 ERR 18431 MESSAGES Could not write to event log, rc = 5
2006-12-14 17:36:03 ___ Stopping GMT 2006-12-14 13:36:03 7.6.00 Build 018-123-119-055
2006-12-16 08:30:29 --- Starting GMT 2006-12-16 04:30:29 7.6.00 Build 018-123-119-055
2006-12-16 09:54:26 0xDDC ERR 18431 MESSAGES Could not write to event log, rc = 5
2006-12-16 09:54:27 ___ Stopping GMT 2006-12-16 05:54:27 7.6.00 Build 018-123-119-055
2006-12-16 10:02:41 --- Starting GMT 2006-12-16 06:02:41 7.6.00 Build 018-123-119-055
2006-12-21 11:40:19 --- Starting GMT 2006-12-21 07:40:19 7.6.00 Build 018-123-119-055
2007-01-03 10:46:50 --- Starting GMT 2007-01-03 06:46:50 7.6.00 Build 018-123-119-055
2007-01-04 13:12:34 0xEFC ERR 18431 MESSAGES Could not write to event log, rc = 5
2007-01-04 13:12:35 ___ Stopping GMT 2007-01-04 09:12:35 7.6.00 Build 018-123-119-055
2007-01-07 13:48:59 --- Starting GMT 2007-01-07 09:48:59 7.6.00 Build 018-123-119-055
2007-01-10 11:31:26 0xE84 ERR 18431 MESSAGES Could not write to event log, rc = 5
2007-01-10 11:31:27 ___ Stopping GMT 2007-01-10 07:31:27 7.6.00 Build 018-123-119-055
2007-01-10 11:45:14 --- Starting GMT 2007-01-10 07:45:14 7.6.00 Build 018-123-119-055
2007-01-11 16:25:20 0xD14 ERR 18431 MESSAGES Could not write to event log, rc = 5
2007-01-11 16:25:21 ___ Stopping GMT 2007-01-11 12:25:21 7.6.00 Build 018-123-119-055
2007-01-11 19:46:58 --- Starting GMT 2007-01-11 15:46:58 7.6.00 Build 018-123-119-055
2007-01-11 20:31:22 ___ Stopping GMT 2007-01-11 16:31:22 7.6.00 Build 018-123-119-055
2007-01-11 20:36:43 --- Starting GMT 2007-01-11 16:36:43 7.6.00 Build 018-123-119-055
2007-01-12 03:15:10 0xDB4 ERR 18878 DIAGHIST Resetting the semaphore failed: Could not open file c:\maxdb\config\ASM for write, rc = 2, rc=0
2007-01-12 03:15:10 0xDB4 ERR 18431 MESSAGES Could not write to event log, rc = 5
2007-01-12 03:15:12 ___ Stopping GMT 2007-01-11 23:15:12 7.6.00 Build 018-123-119-055
Now my SAP itself is not starting
Please help
Cheers
Arun
Hi,
it could be that you've run in a DBM Shared Memory bug. Please try the following: delete the following files <db_name>.dbm.shm and <db_name>.dbm.shi from the <Independent_data_path>/wrk (i.e. <disk>:\sapdb\data\wrk) directory and try again.
<b>Edit:</b> please be aware that you're using a relatively old MaxDB 7.6.00 version, I'd recommend to upgrade to the latest available 7.6.00 or 7.6.01 version.
Regards,
Roland
Hello Arun,
From the knldiag.err:
"2007-01-12 03:15:10 0xDB4 ERR 18878 DIAGHIST Resetting the semaphore failed: Could not open file c:\maxdb\config\ASM for write, rc = 2, rc=0"
Errortext for errorcode 2 ( OS RC 😞
'The system cannot find the file specified.'
=> You need to check, if you have the file c:\maxdb\config\ASM
on the database server.
As I wrote you above, please update with additional info:
-> Please logon to the database server & update with the output of the
following command:
xinstinfo ASM
-> With the output of the command 'xinstinfo <DB-name>' you will see the IndepData value. Please review the files at <IndepData>/config directory. Please give the list of the files. Please check, if you have <DB-name>,<DB-name>.01 & <DB-name>.pah files. What size & when they were changed.
-> If the <IndepData> directory was not changed on the database server, please check, if you have files ASM.dbm.shm and ASM.dbm.shi in the c:\maxdb\wrk. Please rename those files to ASM.dbm.shm.old and ASM.dbm.shi.old
< Hint recommended by Roland. >
***
I assumed that you have <IndepData> = c:\maxdb.
The c:\maxdb\config\ASM is the binary configuration file & it was created by the initialization of the database parameters, when you were creating the database instance.
As the file c:\maxdb\config\ASM could not be found, please check if you have configuration files in c:\maxdb\config. May be the <IndepData> setting was changed by you & the database config files located in another directory. If the <IndepData> directory was not changed, please check, if you have the file c:\maxdb\config\ASM.01. If you have it, please copy c:\maxdb\config\ASM.01 to c:\maxdb\config\ASM & run:
dbmcli -d ASM -u <dbm_user>,<pwd> param_directgetall
& please update with results.
Thank you and best regards, Natalia Khlopina
Hello Arun,
So sorry, but it's difficult to answer on the question, how the file got disappeared form no where.
The 'windows update and anti-virus dated few days back' should be NOT 'the consequence of' deletion files.
Please give more details about updates.
I could only guess, for example, if you had memory problems, and there were no space on the disk.
Please check, when the reported problem started in the dbm.prt and knldiag.err files. Please review around this time if you will see any OS errors reported by 'eventvwr'.
Thank you and best regards, Natalia Khlopina
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.