MaxDB: dbmcli doesn't find its own database instance

[Former Member]

Hello,

the upgrade Maxdb 7.5.00 32 to 7.6.00 35 (OS: Win 2003 Server) was

successful until the database switches to admin mode. The start failed,

the database dumped. On Windows exits a MaxDB service which referes to

the program kernel.exe in the program-directory of the maxdb, this

service can't be started too.

When I call dbmcli -d SID, I become the error message:

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

instance not found (the messages above were similar).

When I call db_enum, I receive only the answer ok instead of the

registered database.

What can I do? Where will the database instance registered or where/how

finds the dbmcli the database instance?

Does uninstall and reinstall of the database software brings a solution

and how can I do this?

here are some more informations (output of some instructions):

C:\sapdb\programs\bin>sdbregview -l

DB Analyzer c:/sapdb/programs 7.6.00.35 32 bit valid

Server Utilities c:/sapdb/programs 7.6.00.35 32 bit valid

PCR 7300 c:/sapdb/programs 7.3.00.55 valid

PCR 7301 c:/sapdb/programs 7.3.01.20 valid

PCR 7500 c:/sapdb/programs 7.5.00.38 32 bit valid

PCR 7104 c:/sapdb/programs 7.1.04.45 valid

SAP Utilities c:/sapdb/programs 7.6.00.35 32 bit valid

Redist Python c:/sapdb/programs 7.6.00.35 32 bit valid

Base c:/sapdb/programs 7.6.00.35 32 bit valid

JDBC c:/sapdb/programs 7.6.00.30 valid

Messages c:/sapdb/programs MSG 0.3951 valid

ODBC c:/sapdb/programs 7.6.00.35 32 bit valid

Database Kernel f:/sapdb/bw3/db 7.6.00.35 32 bit valid

Loader c:/sapdb/programs 7.6.00.35 32 bit valid

SQLDBC c:/sapdb/programs 7.6.00.35 32 bit valid

SQLDBC 76 c:/sapdb/programs 7.6.00.35 32 bit valid

Fastload API c:/sapdb/programs 7.6.00.35 32 bit valid

PCR 7403 c:/sapdb/programs 7.4.03.44 32 bit valid

C:\sapdb\programs\bin>xinstinfo

IndepData : e:\sapdb\data

IndepPrograms : c:\sapdb\programs

C:\sapdb\programs\bin>dbmcli -s inst_enum

OK

7.6.00.35 F:\sapdb\bw3\db

C:\sapdb\programs\bin>xinstinfo BW3

IndepData : e:\sapdb\data

IndepPrograms : c:\sapdb\programs

Installationpath of serverdb <BW3> not found!

Rundirectory : e:\sapdb\data\wrk\BW3

I assume, that maybe the instruction sdbreg in the folder C:\sapdb\programs\bin can help, how can I work with it?

best regards

Karin Marsmann

[roland_mallmann · Accepted solution]

Hi Karin,

you could try to reregister the instance using (substitute BW3 for another instance if it's not the correct DB SID):

c:\sapdb\programs\bin\dbmcli -R F:\sapdb\BW3\db inst_reg -k F:\sapdb\BW3\db

Hope that helps.

Regards,

Roland

[Former Member · Accepted solution]

Hello Roland,

unfortunately this brings no solution. Here is a copy of the sequence:

C:\sapdb\programs\pgm>dbmcli -R F:\sapdb\bw3\db inst_reg -k F:\sapdb\bw3\db

OK

C:\sapdb\programs\pgm>dbmcli -s inst_enum

OK

7.6.00.35 F:\sapdb\bw3\db

C:\sapdb\programs\pgm>xinstinfo BW3

IndepData : e:\sapdb\data

IndepPrograms : c:\sapdb\programs

Installationpath of serverdb <BW3> not found!

Rundirectory : e:\sapdb\data\wrk\BW3

C:\sapdb\programs\pgm>dbmcli db_enum

OK

regards,

Karin

[roland_mallmann · Accepted solution]

Hi again,

hm, kinda weird.

Can you please

a.) tell me if the MaxDB 7.5.00 version is also of the 32bit variety (i.e. not 64bit)?

b.) tell me if you see a service entry for your BW3 db instance in the Windows Registry under HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > SAP DBTech-BW3?

c.) tell me if the paramfiles (e:\sapdb\data\config\BW3) and Rundirectory-logfiles (e:\sapdb\data\wrk\BW3\knldiag, dbm) are available?

d.) show me the content of the latest MaxDB migration logfile (starts with 'MaxDB' from the directory e:\sapdb\data\wrk\)?

Thx & regards,

Roland

[Former Member · Accepted solution]

Hello Roland,

ad a) 32-bit version

ad b) there are 4 entries, the are named M760035 instead of bw3, reference to F:\sapdb\bw3\db\pgm\kernel.exe

ad c) the paramfile and the rundirectory-logfiles are available

(the rundirectory logfiles are in the directory E:\sapdb\data\wrk\BW3)

ad d) the files will I sent you per Mail.

Regards,

Karin

[roland_mallmann · Accepted solution]

Hi Karin,

I just wanted to let you know that I've received your emai(s). I'm currently analyzing them and will disuss your issue with development.

Regards,

Roland

[roland_mallmann · Accepted solution]

Hi Karin,

ok, let's try this:

1.) reconfigure your Windows machine to be able to use 3GB of address space per process instead of the current 2GB. To change this, please use note<a href="https://websmp104.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=112403&_NLANG=EN>">112403</a>.

Please make sure the machine is rebooted after this change before proceeding.

This should aid you in not getting the crash again, which you've faced a couple of times so far (excerpt from knldiag follows):

"

Could not allocate 133169152 Bytes (heap) for task stacks, rc=8

Could not allocate the tasks stack, rc = 8

...

RTE Abort exception

...

Kernel aborts

...

"

2.) After the 3GB option is set, we will need to recreate your instance using the still available config files (parameters, volumes etc.) command:

dbmcli -R F:\sapdb\bw3\db db_create <DB-name> <DBM-user>,<password>

Please enter the databasename, the user and it's password in CAPS.

Hope that solves your issues.

Regards,

Roland

[Former Member · Accepted solution]

Hello Roland,

ad 1) I entered the /3GB option and rebooted the server.

ad 2) Now I have a question:

Is it shure that a db_create doesn't delete the already available database BW3 and creates an empty new one?

Regards, Karin

[roland_mallmann · Accepted solution]

Hi Karin,

ad 2) Yes, it should <b>not</b> delete the already available instance, but just use the available paramfile, volumes etc. Just make sure to specify the correct dependent path, DB name and DBM user and password.

Regards,

Roland

[Former Member · Accepted solution]

Hi Roland,

the problem is solved, the upgrade ends successfully. But I had never assumed that the problem was a memory problem.

Thanks for your help, my colleagues can now work further.

Best Regards, Karin Marsmann