on 03-22-2011 1:41 PM
Hi friends,
My server was halted as power to the server was cut (no UPS in place).
After this my MaxDB is in unknow state. I tried to empty and even delete directory "rtedump_dir" as per SAP note and other treads about the subject. It did not work.
How the heck, do I convince/force MaxDB to start when I can allow my self to loose any uncommited transactions?
Any advice would be great
Thanks
Jan
dbmcli -d SX2 -u superdba,xxxxx show state
OK
Open of map file /sapdb/data/wrk/SX2/rtedump_dir/RTEMemory_Table.0 failed
No mapping chunk entries found
'RTECons_MemoryDumpMapping' instance could not be created
Failed to map memory dump files
ERR 13638 RTE RTE_ConsoleRequestCommunication.cpp:280
ERR 13638 RTE 2011-03-16 16:41:51 RTE Error 13638
ERR 13638 RTE Console: Server DB 'SX2' has not been started
dbmcli -d SX2 -u superdba,xxxxxx db_stop
ERR
-24960,ERR_DBRUN: Database instance is running
dbmcli -d SX2 -u superdba,xxxxxx db_admin
ERR
-24783,ERR_WRONGDBSTATE: Operational state UNKNOWN of the database instance is unsuitable.
-24779,ERR_DBSTATENEEDED4: Database instance must be in one of the operational states OFFLINE, ADMIN, STANDBY or ONLINE.
dbmcli -d SX2 -u superdba,xxxxxx db_online
ERR
-24783,ERR_WRONGDBSTATE: Operational state UNKNOWN of the database instance is unsuitable.
-24779,ERR_DBSTATENEEDED4: Database instance must be in one of the operational states OFFLINE, ADMIN, STANDBY or ONLINE.
dbmcli db_enum
OK
SX2 /sapdb/SX2/db 7.7.06.10 fast offline
SX2 /sapdb/SX2/db 7.7.06.10 quick offline
SX2 /sapdb/SX2/db 7.7.06.10 slow offline
SX2 /sapdb/SX2/db 7.7.06.10 test offline
dbmcli inst_enum
OK
7.7.06.10 /sapdb/SX2/db
sdbregview -l
Server Utilities /sapdb/programs 7.7.06.10 64 bit valid
DB Analyzer /sapdb/programs 7.7.06.10 64 bit valid
PCR 7300 /sapdb/programs 7.3.00.60 valid
PCR 7301 /sapdb/programs 7.3.01.22 valid
PCR 7500 /sapdb/programs 7.5.00.50 64 bit valid
SAP Utilities /sapdb/programs 7.7.06.10 64 bit valid
Base /sapdb/programs 7.7.06.10 64 bit valid
Redist Python /sapdb/programs 7.7.06.10 64 bit valid
JDBC /sapdb/programs 7.6.06.02 valid
Messages /sapdb/programs MSG 0.7732 valid
ODBC /sapdb/programs 7.7.06.10 64 bit valid
Database Kernel /sapdb/SX2/db 7.7.06.10 64 bit valid
SQLDBC 77 /sapdb/programs 7.7.06.10 64 bit valid
Loader /sapdb/programs 7.7.06.10 64 bit valid
SQLDBC /sapdb/programs 7.7.06.10 64 bit valid
SQLDBC 76 /sapdb/programs 7.6.05.15 64 bit valid
Fastload API /sapdb/programs 7.7.06.10 64 bit valid
xinstinfo SX2
IndepData : /sapdb/data
IndepPrograms : /sapdb/programs
InstallationPath : /sapdb/SX2/db
Kernelversion : KERNEL 7.7.06 BUILD 010-123-204-327
Rundirectory : /sapdb/data/wrk/SX2
Hello Jan,
1.
Are you SAP customer?
If yes => Did you create the SAP message on this issue?
2.
Please update the message with output of the following commands:
ls -l /sapdb/data/pid
ls -l /sapdb/data/ppid
ls -l /sapdb/data/fifo
ps -efe | grep kernel
ps -efe | grep sdb
more /etc/opt/sdb
uname -a
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,
1)
About-to-be partner. This is "just" a demo system.
So, I have not created an OSS message about this.
2)
mibsx2:sx2adm 51> ls -l /sapdb/data/pid
total 8
drwxrwx--- 2 sdb sdba 4096 2010-10-31 21:01 serverpids
-rw-rr 1 sdb sdba 5 2010-12-15 18:27 SX2
mibsx2:sx2adm 52> ls -l /sapdb/data/ppid
total 0
mibsx2:sx2adm 53> ls -l /sapdb/data/fifo
total 0
prwww- 1 sdb sdba 0 2011-03-08 16:32 SX2
prw-rw---- 1 sdb sdba 0 2011-03-16 00:33 xserver_mibsx2_logger
prw-rw---- 1 sdb sdba 0 2010-10-31 21:01 xserver_mibsx2_update
mibsx2:sx2adm 54>
mibsx2:sx2adm 54> ps -efe | grep kernel
sx2adm 30169 29946 0 20:47 pts/0 00:00:00 grep kernel
mibsx2:sx2adm 55> ps -efe | grep sdb
sdb 5726 1 0 Mar16 ? 00:00:00 /sapdb/programs/pgm/niserver
sdb 5729 1 0 Mar16 ? 00:00:00 /sapdb/programs/pgm/vserver start
sdb 5730 5729 0 Mar16 ? 00:00:00 xserver.prt logger
sx2adm 30171 29946 0 20:47 pts/0 00:00:00 grep sdb
mibsx2:sx2adm 56> ps -efe | grep sdb
sdb 5726 1 0 Mar16 ? 00:00:00 /sapdb/programs/pgm/niserver
sdb 5729 1 0 Mar16 ? 00:00:00 /sapdb/programs/pgm/vserver start
sdb 5730 5729 0 Mar16 ? 00:00:00 xserver.prt logger
sx2adm 30173 29946 0 20:47 pts/0 00:00:00 grep sdb
mibsx2:sx2adm 56> more /etc/opt/sdb
[Globals]
IndepData=/sapdb/data
IndepPrograms=/sapdb/programs
SdbOwner=sdb
SdbGroup=sdba
mibsx2:sx2adm 57> uname -a
Linux mibsx2 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux
Everything was fine until the power-cut ....
Cheers
Jan
Hello Jan,
Run
more /sapdb/data/pid/SX2
to see the number, then grep the process by this pid number:
ps -efe | grep <pid-number>
After the server was restarted I assume that the database kernel pid was assign to another process.
If I'm correct, please, run the following steps:
mv /sapdb/data/pid/SX2 /sapdb/data/pid/SX2.old
< there are no database kernel processes active according your info, you cold delete /sapdb/data/pid/SX2.old later. >
After that use the dbm command db_admin to restart the database SX2 and post the results.
Regards, Natalia Khlopina
Natalia !
YOU ARE THE GREATEST
Seriously, how can I send you a BIG box of chocolate?
Thanks a 1000 !
cheers
Jan
mibsx2:sx2adm 51> more /sapdb/data/pid/SX2
3811
mibsx2:sx2adm 52> ps -ef | grep -i 3811
root 3811 1 0 Mar15 ? 00:00:33 /usr/sbin/irqbalance
sx2adm 30519 30298 0 21:42 pts/0 00:00:00 grep -i 3811
mibsx2:root > mv /sapdb/data/pid/SX2 /sapdb/data/pid/SX2.old
mibsx2:sx2adm 54> dbmcli -d SX2 -u superdba,xxxxx db_admin
OK
mibsx2:sx2adm 55> dbmcli -d SX2 -u superdba,xxxxx db_online
OK
Hi Jan,
As per SAP note 1283278 - Database cannot be started.
Please check the permission for the following directory /sapdb/data/wrk/<SAPSID>/rtedump_dir/.
Regards,
Sahil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jan,
There is no problem to ask.
http://www.sapdb.org/webpts?wptssimple
This Problem Tracking System (MaxDB PTS) is the Web interface to the internal SAP program PTS for documenting problem messages for MaxDB software.
With this program, you have only read access to the problem messages recorded in the internal SAP program PTS.
Regards,
Eduardo
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.