x_start doesn't online an instance in 7.8.02.21

[simon_matter]

Hi,

I did a test install of 7.8.02.21 and tried to adopt our init scripts to handle the new version.

Now, I'm wondering why x_start doesn't start an instance anymore to online state:

/opt/sdb/globalprograms/bin/x_start INVOCADB
OK
Warning: Expected database state was ONLINE
Database INVOCADB started to status ADMIN

and the log shows:

Thread     0x10ED Task      -  2012-01-30 20:15:21     RunTime        3:  State changed from STARTING to ADMIN
Thread     0x10ED Task      -  2012-01-30 20:15:21     STATE      12601:  SERVERDB is ready
Thread     0x10ED Task      -  2012-01-30 20:15:21     RTE        20223:  Database tries automatic restart
Thread     0x1104 Task      -  2012-01-30 20:15:21 ERR RTE        20125:  Database automatic restart failed,_FILE=RTE_ExternalCall+noPIC.cpp,_LINE=903

I can online the instance with dbmcli without any problems, but why does it not work with x_start anymore. I can't seem to find this documented somewhere.

IIRC x_start was useful to online an instance without knowing the DBM passwords.

Did I just miss something?

Thanks,

Simon

Edited by: Simon Matter on Jan 30, 2012 8:26 PM

[simon_matter]

Hi,

We never found out why x_start didn't work anymore and I don't know if it was fixed in newer releases.

We switched to start the instances using dbmcli instead. We run dbmcli and there first do a 'user_logon ...' and the run a 'db_restart' to (re)start the instance.

Regards,

Simon

[dptosap_cdatex]

Hi Simon

How did you solve this problem?, we have the same problem

Thanks, regards

[former_member229109]

Hello,

please update with output of the following commands:

/opt/sdb/globalprograms/bin/xinstinfo INVOCADB

/opt/sdb/globalprograms/bin/sdbregview -l

<IINVOCADB Installation Path>/bin/x_start INVOCADB

Regards, Natalia Khlopina

[simon_matter]

Hi Natalia,

Here is the requested info:

[root@install ~]# /opt/sdb/globalprograms/bin/xinstinfo INVOCADB
IndepData           : /var/opt/sdb/globaldata
IndepPrograms       : /opt/sdb/globalprograms
InstallationPath    : /opt/sdb/MaxDB
Kernelversion       : KERNEL    7.8.02   BUILD 021-121-242-175
Rundirectory        : /var/opt/sdb/globaldata/wrk/INVOCADB


[root@install ~]# /opt/sdb/globalprograms/bin/sdbregview -l
Installation: Global    /opt/sdb/globalprograms
Global Listener               7.8.02.21    valid    64 bit
Installation Compatibility    7.8.02.21    valid    64 bit
Installer                     7.8.02.21    valid

Installation: MaxDB    /opt/sdb/MaxDB
Base                7.8.02.21      valid    64 bit
DB Analyzer         7.8.02.21      valid    64 bit
Database Kernel     7.8.02.21      valid    64 bit
JDBC                7.6.06.07      valid
Loader              7.8.02.21      valid    64 bit
Messages            MSG 0.10269    valid
ODBC                7.8.02.21      valid    64 bit
Redist Python       7.8.02.21      valid    64 bit
SQLDBC              7.8.02.21      valid    64 bit
SQLDBC 77           7.8.02.21      valid    64 bit
Server Utilities    7.8.02.21      valid    64 bit


[root@install ~]# /opt/sdb/MaxDB/bin/x_start INVOCADB
OK
Warning: Expected database state was ONLINE
Database INVOCADB started to status ADMIN

As said before, doing a db_online with dbmcli works well, it's only that x_start doesn't put the DB into online mode but it goes into admin mode instead.

Thanks,

Simon

[former_member184473]

Hello Simon,

The x_start isn't mentioned in the documentation:

http://maxdb.sap.com/doc/7_8/1a/32c42a0fcf40b5b95ff7040a60aa41/frameset.htm

Regards,

Eduardo Rezende

[simon_matter]

Hi Eduardo,

x_start was really useful to start instances without knowing the DBM passwords. More so x_stop, it allows you to offline an instance without knowing the password - of course only as privileged user.

The lack of those commands would be sad. It's my impression that x_start just has a bug which is why I hoped it will be fixed.

Regards,

Simon