on 06-23-2008 12:59 PM
hi
when i did a failed backup (in order to do a homogeneus copy system), i can't connect to database with database manager, the dabase shows the next message error:
-24724 ERR_RESLOCK_NO_LOCK Resource ParamAccess not locked
In the db50 transaction i have the same message error.
any suggestion?
Hi,
could it be that the /sapdb/data/ folder is located on an NFS path?
Please post the dbm.prt and the knldiag file.
KR Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Lars
the directory sdb/sapdatax are in local filesystem.
The files can be downloaded from the next url: http://glup.uv.es/~ritoros/
thanks in advance
Hi,
please execute the following and post the output:
dbmcli -d ... -u ... dbm_shm_info
Was there any trouble with the machine on 2008-06-19 at about 15:22?
This snippet of the dbm.prt just makes me wonder...
2008-06-19 15:22:39 0x00003686 INF 216 DBMSrv DBM Server client connection (established at 2008-06-19 15:21:27): PID 4216 on computer notsap0136.domsrv.gsm
2008-06-19 15:22:39 0x00003686 INF 283 DBMSrv command backup_save_state
2008-06-19 15:22:39 0x00003686 ERR -24961 DBMSrv ERR_STATE: The operational state of the database instance could not be determined
0x00003686 ERR -24994 DBMSrv ERR_RTE: Runtime environment error
0x00003686 ERR -24778 DBMSrv 1,database MID not found
2008-06-19 15:22:39 0x00003686 INF 226 DBMSrv DBM Se2008-06-19 15:23:56 0x0000367f INF 283 DBMSrv command db_execute SELECT ID,CREATEDATE,USEDSIZE
2008-06-19 15:23:56 0x0000367f ERR -24961 DBMSrv ERR_STATE: The operational state of the database instance could not be determined
0x0000367f ERR -24994 DBMSrv ERR_RTE: Runtime environment error
0x0000367f ERR 1 RTEDBState database MID not found
2008-06-19 15:23:56 0x0000367f ERR -24961 DBMSrv ERR_STATE: The operational state of the database instance could not be determined
0x0000367f ERR -24994 DBMSrv ERR_RTE: Runtime environment error
0x0000367f ERR -24778 DBMSrv 1,database MID not found
Regards,
Marc-Philip
Edited by: Marc-Philip Werner on Jun 24, 2008 3:27 PM
Edited by: Marc-Philip Werner on Jun 24, 2008 3:30 PM
hi lars
The output of the command is:
VERSION
Required 1
Found 1
LOCKING
Normal lock UNLOCKED
Reserve lock UNLOCKED
Locking pid 0
PROCESSES
pid | status
6218 | ALIVE
12416 | ALIVE
20694 | ALIVE (*)
LOCKCOUNTER
182333
HALFSWITCHER
overall size 446
used size 223
offset 223
LINES
Resource Locks
Existing lines 16777216
thanks in advance
Hi,
besides the dbm.prt, some other files of the DBM Server are damaged (the unusual high number of ressoruce locks indicates this). Please do the following:
Stop all DBM Server processes related to database MID (image name is dbmsrv, if you need to kill some).
Remove files /sapdb/data/wrk/MID.dbm.shi and /sapdb/data/wrk/MID.dbm.shm or if they don't exist /sapdb/data/wrk/MID/dbm.shi and /sapdb/data/wrk/MID/dbm.shm
Now you should be able to manage MID again.
Regards,
Marc-Philip
Edited by: Marc-Philip Werner on Jun 25, 2008 2:43 PM
User | Count |
---|---|
90 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.