db_create waiting forever without doing anything?

[former_member192710]

Folks;

rather strange situation: Had 7.7.x running on my machine, removed it again to go back to 7.6 (in order to get on par with our productive environment again). Installed the latest 7.6 linux 32bit build, tried to run my database recovery script (the one I always make use of to restore a MaxDB instance off a full backup medium), to see - nothing. Retried, killed most of the MaxDB processes, again nothing.

Taking a closer look, it seems the thing reproducibly comes to a halt when trying to do db_create using dbmcli, and actually, this is what I can reproduce by manually opening a dbmcli session and trying to do db_create from within there - db_create seems to wait for something(?) until I eventually kill off the process, as I did so after waiting for almost an hour without any success. Unfortunately, I cannot even provide much log file output as it seems the working directory for the database hasn't yet been created. The only thing that seems peculiar to me is dbmsrv_n428.prt which looks like this:

------------------------------------------------------------------------------
Date       Time     TID(hex)   Typ MsgID      Label    Message
------------------------------------------------------------------------------
2010-07-13 09:43:19 0x00002dfd INF        216 DBMSrv   DBM Server client connection (established at 2010-07-13 09:43:19): PID 11771 on computer n428
2010-07-13 09:43:19 0x00002dfd INF        283 DBMSrv   Command 'inst_reg -k /opt/maxdb/7606 ' is being executed.
2010-07-13 09:43:19 0x00002dfd ERR     -24748 DBMSrv   ERR_FILEOPEN: Error opening file /opt/maxdb/data/config/.M760603.cfg
                    0x00002dfd ERR     -24994 DBMSrv   ERR_RTE: Runtime environment error
                    0x00002dfd ERR     -24778 DBMSrv   1,OS error: 'No such file or directory'
                    0x00002dfd ERR     -24748 DBMSrv   ERR_FILEOPEN: Error opening file /opt/maxdb/data/wrk/.M760603/dbm.cfg
                    0x00002dfd ERR     -24994 DBMSrv   ERR_RTE: Runtime environment error
                    0x00002dfd ERR     -24778 DBMSrv   1,OS error: 'No such file or directory'
                    0x00002dfd ERR     -24748 DBMSrv   ERR_FILEOPEN: Error opening file /opt/maxdb/data/wrk/.M760603/dbm.cfg
                    0x00002dfd ERR     -24994 DBMSrv   ERR_RTE: Runtime environment error
                    0x00002dfd ERR     -24778 DBMSrv   1,OS error: 'No such file or directory'
2010-07-13 09:43:19 0x00002dfd INF        419 DBMSrv   Command 'inst_reg' has ended with return code 0.
2010-07-13 09:43:19 0x00002dfd INF        226 DBMSrv   DBM Server client disconnected: PID 11771 on computer n428
2010-07-13 09:43:44 0x00002e4a INF        216 DBMSrv   DBM Server client connection (established at 2010-07-13 09:43:44): PID 11848 on computer n428
2010-07-13 09:43:44 0x00002e4a INF        283 DBMSrv   Command 'db_create BFLOWDB ...' is being executed.
2010-07-13 09:46:03 0x00002f5c INF        216 DBMSrv   DBM Server client connection (established at 2010-07-13 09:46:03): PID 12122 on computer n428
2010-07-13 09:46:03 0x00002f5c INF        283 DBMSrv   Command 'db_create BFLOWDB ...' is being executed.

I wonder about the "error opening file" messages (indeed, these files do not exist). Could it be a problem caused by MaxDB file structure? In our productive environment, MaxDB lives in /opt/maxdb/[data,apps,7606]), whereas on my notebook it lives in /home/maxdb/[data,apps,7606], with /home/maxdb being symlinked to /opt/maxdb/? This so far seems the only difference I can see...

TIA and all the best,

Kristian

[former_member229109]

Hello Kristian,

1. What is version of database software installed on the server?

Is 7606 the name of the database?

Update with output of the commands:

sdbregview u2013l

xinstinfo

xinstinfo 7606

uname u2013a

more /etc/opt/sdb

2. What password of the SYSDBA user u201CBFLOWDBu201D did you use?

Did you have the character "@" in password?

3. Could you login to the database server as user in the sdba group and run the following commands:

Dbmcli u2013d 7606 u2013u <dbm-user>,<pwd>

<enter>

Dbmcli on 7606>db_admin

<enter>

Dbmcli on 7606> db_activate BFLOWDB,admin

<enter>

Update with the results.

Thank you and best regards, Natalia Khlopina

[former_member192710]

Natalia,

first off, thanks a bunch for your reply and taking care of my issue here. Generally, I need to stress that this in my opinion is not a MaxDB related issue as I used to successfully run both MaxDB 7.6, 7.7 and my recovery script a few days ago on the same machine / operating system platform. It seems that "something" got trashed / jammed however after removing 7.7 in order to go with 7.6 again. My problem is "just" that I so far can't figure out what's wrong as the dbmcli command is not very verbose and so far kept itself from providing me with any information on what could be wrong...

Anyway, for the details you requested:

kr@n428:~$ sdbregview -l
Server Utilities           /home/maxdb/apps    7.6.06.03     32 bit    valid
DB Analyzer                /home/maxdb/apps    7.6.06.03     32 bit    valid
Synchronization Manager    /home/maxdb/apps    7.6.06.03               valid
Base                       /home/maxdb/apps    7.6.06.03     32 bit    valid
Redist Python              /home/maxdb/apps    7.6.06.03     32 bit    valid
JDBC                       /home/maxdb/apps    7.6.05.06               valid
Messages                   /home/maxdb/apps    MSG 0.8215              valid
ODBC                       /home/maxdb/apps    7.6.06.03     32 bit    valid
Database Kernel            /home/maxdb/7606    7.6.06.03     32 bit    valid
Loader                     /home/maxdb/apps    7.6.06.03     32 bit    valid
MaxDB PHP Driver           /home/maxdb/apps    7.6.06.03     32 bit    valid
SQLDBC                     /home/maxdb/apps    7.6.06.03     32 bit    valid

kr@n428:~$ xinstinfo
IndepData           : /home/maxdb/data
IndepPrograms       : /home/maxdb/apps

kr@n428:~$ xinstinfo 7606
IndepData           : /home/maxdb/data
IndepPrograms       : /home/maxdb/apps
Installationpath of serverdb <7606> not found!
ERR 20010  RTE      Could not open file /home/maxdb/data/config/7606 for read, rc = 2

kr@n428:~$ uname -a
Linux n428 2.6.32-23-generic-pae #37-Ubuntu SMP Fri Jun 11 09:26:55 UTC 2010 i686 GNU/Linux

kr@n428:/home/maxdb/data/config$ more /etc/opt/sdb 

[Globals]
IndepData=/home/maxdb/data
IndepPrograms=/home/maxdb/apps
SdbOwner=sdb
SdbGroup=sdba

> 2. What password of the SYSDBA user u201CBFLOWDBu201D did you use?

> Did you have the character "@" in password?

Well, not that I know of. BFLOWDB is supposed to be the name of the database, actually...

> 3. Could you login to the database server as user in the sdba group and run the following commands:

> Dbmcli u2013d 7606 u2013u <dbm-user>,<pwd>

> <enter>

My primary everyday working account is in sdba, so I thought this to work:

kr@n428:~$ dbmcli -d 7606 -u kr,XXXXXXXX
Error! Connection failed to node (local) for database 7606:
database not found

Does that make any sense to you?

Thanks a bunch and best regards,

Kristian

[former_member229109]

Hello Kristian,

Thank you for the update.

1. Please run the following commands as user in sdba group and let me know the results:

dbmcli inst_enum

dbmcli db_enum -s

dbmcli -s -R /home/maxdb/7606 db_create BFLOWDB control,control

< To check if you could create the BFLOWDB database with control user and default password control. >

ls u2013l /home/maxdb/data/config

ls u2013l /home/maxdb/data

ls u2013l /home/maxdb

2. Are you SAP customer?

3. How did you u201Cremoveu201D the database 7.7 on your machine?

< Did you drop the database instance before to uninstall the database software using SDBUNINST? >

Best regards, Natalia Khlopina

[former_member192710]

Hi Natalia;

and first off, thanks a bunch for your reply. Playing with things, and trying to provide you with more in-depth information, I eventually figured out the cause of my problems: So far, I used to "simply" uninstall MaxDB by dropping the database, purging anything in /home/maxdb/*, /etc/opt/sdb, /usr/spool/sql, $HOME/.sdb and re-installed / restarted again. Examining things a little closer, however, I found *shm files related to BFLOWDB in /var/lib/sdb, which seemed too old to be interesting. Removing these immediately made dbmcli work as expected again.

So, overall outcome: Problem solved, blame my ignorance not to use SDBUNINST. The next time I'll know, meanwhile thanks a bunch for your help and patience.

Kristian