How to start MaxDB ?

[Former Member]

Hi people,

I get the next error when I call the maxDB database from tcode LC10:

Name und Server : ORA - avast

DBMRFC Funktion : DBM_CONNECT

Fehler : Fehler des DBM

Rückgabewert : -4

Fehlermeldung : database instance not found

What can I do for to follow all the rest post-installation activities of the livecache.

How can startup manually the instance from command line?

More thnaks

With the command I get the next error

root:sidadm> ./dbmcli -d ORA -u CONTROL,PASS db_start

Error! Connection failed to node (local) for database ORA:

database instance not found

Edited by: Ruben Torres on Jan 3, 2010 6:55 PM

[Former Member]

This is optional information

host:sidoadm> sdbregview -l

SAP Utilities /sapdb/programs 7.7.04.29 64 bit valid

Server Utilities /sapdb/programs 7.7.04.29 64 bit valid

DB Analyzer /sapdb/programs 7.7.04.29 64 bit valid

APO LC APPS /sapdb/LC1/db/sap 7.00.006 64 bit valid

APO LC APPS /sapdb/LV2/db/sap 7.00.006 64 bit valid

APO LC APPS /sapdb/LC3/db/sap 7.00.006 64 bit valid

Redist Python /sapdb/programs 7.7.04.29 32 bit valid

Base /sapdb/programs 7.7.04.29 64 bit valid

JDBC /sapdb/programs 7.6.05.06 valid

Messages /sapdb/programs MSG 0.7113 valid

ODBC /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC 77 /sapdb/programs 7.7.04.29 64 bit valid

Database Kernel /sapdb/LCP/db 7.7.04.29 64 bit valid

Database Kernel /sapdb/LVC/db 7.7.04.29 64 bit valid

Database Kernel /sapdb/LCA/db 7.7.04.29 64 bit valid

Loader /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC 76 /sapdb/programs 7.6.05.11 64 bit valid

Fastload API /sapdb/programs 7.7.04.29 64 bit valid

host:sidadm> ./dbmcli -s inst_enum

RTE_CallSdbStarter(): Failed to change to indep data work path:/sapdb/data/wrk [13]

Error! Connection failed to node (local) for database (no dbname):

Reading header from pipe:closed by serv

host:sidoadm> ./dbmcli -s db_enum

RTE_CallSdbStarter(): Failed to change to indep data work path:/sapdb/data/wrk [13]

Error! Connection failed to node (local) for database (no dbname):

Reading header from pipe:closed by serv

[former_member229109]

Hello Ruben Torres,

For SAP liveCache documentation please see the SAP note 767598.

1. First posted problem.

You failed to restart the liveCache in LC10, because the liveCache instance ORA on the server avast was not found.

Also you failed to connect to the ORA database using dbmcli with control user due the same reason:

Error! Connection failed to node (local) for database ORA:

database instance not found

To run the analysis of this problem, you need to login to the server avast as user in the sdba group

And run the following commands :

sdbregview u2013l

< to see the database software packages installed on the server >

xinstinfo

dbmcli inst_enum

dbmcli db_enum

Next steps are dependent from the output results.

2. Second posted problem.

On which server did you run those commands?

The list of the database software packages has not /sapdb/ORA/db dependent Database kernel path

=> How did you create/install the ORA liveCache?

Please run as root user:

cd /sapdb/programs/bin

./sdbverify

to check if the database software installed correctly.

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi Natalia,

sdbregview u2013l

< to see the database software packages installed on the server >

avast:oraadm> sdbregview -l

SAP Utilities /sapdb/programs 7.7.04.29 64 bit valid

Server Utilities /sapdb/programs 7.7.04.29 64 bit valid

DB Analyzer /sapdb/programs 7.7.04.29 64 bit valid

APO LC APPS /sapdb/LV1/db/sap 7.00.006 64 bit valid

APO LC APPS /sapdb/LV2/db/sap 7.00.006 64 bit valid

APO LC APPS /sapdb/LV3/db/sap 7.00.006 64 bit valid

Redist Python /sapdb/programs 7.7.04.29 32 bit valid

Base /sapdb/programs 7.7.04.29 64 bit valid

JDBC /sapdb/programs 7.6.05.06 valid

Messages /sapdb/programs MSG 0.7113 valid

ODBC /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC 77 /sapdb/programs 7.7.04.29 64 bit valid

Database Kernel /sapdb/LV1/db 7.7.04.29 64 bit valid

Database Kernel /sapdb/LV2/db 7.7.04.29 64 bit valid

Database Kernel /sapdb/LCV3/db 7.7.04.29 64 bit valid

Loader /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC 76 /sapdb/programs 7.6.05.11 64 bit valid

Fastload API /sapdb/programs 7.7.04.29 64 bit valid

xinstinfo

avast:oraadm> xinstinfo

IndepData : /sapdb/data

IndepPrograms : /sapdb/programs

dbmcli inst_enum

avast:oraadm> dbmcli inst_enum

RTE_CallSdbStarter(): Must be called by root or effective user 102 effective group 105

Error! Connection failed to node (local) for database (no dbname):

Reading header from pipe:closed by serv

The user oraadm is in the group sdba, but I get the result that appears up.

If I executed with the root user I get this:

root@avast # ./dbmcli inst_enum

OK

7.7.04.29 /sapdb/LV1/db

7.7.04.29 /sapdb/LV2/db

7.7.04.29 /sapdb/LV3/db

dbmcli db_enum

RTE_CallSdbStarter(): Must be called by root or effective user 102 effective group 105

Error! Connection failed to node (local) for database (no dbname):

Reading header from pipe:closed by serv

With the root user this appear:

root@apo # ./dbmcli db_enum

OK

LV2 /sapdb/LV2/db 7.7.04.29 fast offline

LV2 /sapdb/LV2/db 7.7.04.29 quick offline

LV2 /sapdb/LV2/db 7.7.04.29 slow offline

LV2 /sapdb/LV2/db 7.7.04.29 test offline

Next steps are dependent from the output results.

2. Second posted problem.

On which server did you run those commands?

The list of the database software packages has not /sapdb/ORA/db dependent Database kernel path

=> How did you create/install the ORA liveCache?

I´ve installed the livecache whit the installation guide, with the default paths of the sapinst. Only I´ve change the path of the datafiles.

Please run as root user:

cd /sapdb/programs/bin

./sdbverify

The output of the file sdbverify is more large. What part of the file are you need?

to check if the database software installed correctly.

More thanks.

[former_member229109]

Hello Ruben Torres,

1. Did you create the SAP message for SAP support.

You could attach the output of the u2018sdbverifyu2019 to the SAP ticket to review the results.

2. Please update with output of the commands:

Id sdb

Id oraadm

Please post the summary results of the sdbverify check at the end.

Also please check and post the modified or changed owner/permissions entries in the output of the sdbverify check.

Thank you and best regards, Natalia Khlopina