Database Analyzer: no actual system tables

[Former Member]

Hi,

In DBACOCKPIT -> Performances -> Database Analyzer -> Bottlenecks, I see once every day the same message after the application of MaxDB patch 7.6.05.15 (which ran successfully without warning):

High No actual system tables for kernel 7.6.05 Build 015-123-202-938

This error message doesn't seem to influence performances, but I want to get rid of this.

In the Database Manager, I see that it's possible to upgrade system tables.

Is this the solution ? Do I have to shutdown SAP instances to proceed ?

Thanks in advance for your advice.

Sincerely,

Christophe Brandt

[Former Member · Accepted solution]

Hi Melanie,

It's a little bit clearer now...

The application of MaxDB patch was performed with SDBSETUP on 20090304.

In the dbm.prt file I observe errors since then:

2009-04-03 09:25:38 0x00000bc4 INF 283 DBMSrv Command 'db_execute SELECT ID,CREATEDATE,USEDSIZE ...' is being executed.

2009-04-03 09:25:38 0x00000bc4 ERR -24580 DBMSrv ERR_COMMAND_FAILED: Command 'db_execute' has ended and failed with return code -24988.

0x00000bc4 ERR -24988 DBMSrv ERR_SQL: SQL error

0x00000bc4 ERR -24778 DBMSrv 100,Row not found

2009-04-03 15:14:39 0x0000130c INF 216 DBMSrv DBM Server client connection (established at 2009-04-03 15:14:39): PID 4168 on computer IMPSAPDVP.Intermed.local

2009-04-03 15:14:39 0x0000130c INF 421 DBMSrv Command 'file_getfirst ...' was executed since 2009-04-03 15:14:39.

2009-04-03 15:14:39 0x0000130c ERR -24580 DBMSrv ERR_COMMAND_FAILED: Command 'file_getfirst' has ended and failed with return code -24994.

0x0000130c ERR -24994 DBMSrv ERR_RTE: Runtime environment error

0x0000130c ERR -24778 DBMSrv 1,wrong file or device name

These errors occur repeatitly (last occurence of 'Row not found' today, last occurence of 'Runtime environement error' on 20090701).

In the Database Manager there's an option to upgrade system tables. Do I have to do it to solve the problem ? If yes, do I have to shutdown SAP instance before ?

Sincerely,

Christophe

[Melanie · Accepted solution]

Hello Christophe,

SDBSETUP should also automatically load the system tables. Did you check the mentioned log files?

You can update the system tables with DBMGUI or Database Studio while the system is up and running.

Regards, Melanie

[Melanie · Accepted solution]

Hello Christophe,

could you please also check, which configuration file you are using for the dbanalyzer?

Please post the output of the following dbmcli command: dban_state

How do you start the database analyzer?

Regards, Melanie

[Former Member · Accepted solution]

Hi Melanie,

The dbanalyzer76.cfg file is 295 KB big (modified 27/09/2007 20:10).

dban_state:

C:\Documents and Settings\dvpadm>dbmcli -u control,Impsap1$ -d DVP dban_state

OK

0,OK: everything works fine

0,"E:\sapdb\programs\bin\dbanalyzer" -d DVP -u , -state

MaxDB Database Analyzer, The Performance Analysis Tool, Version 7.7.02.17

Copyright 2000-2007 by SAP AG

Used protocol directory: E:\sapdb\data\wrk\DVP\analyzer

INFO 13: Database Analyzer active in directory "E:\sapdb\data\wrk\DVP\analyzer".

Database = DVP

Node =

Rundirectory = E:\sapdb\data\wrk\DVP

Configfile = E:\sapdb\programs\env\dbanalyzer76.cfg

Protocoldirectory = E:\sapdb\data\wrk\DVP\analyzer

Interval = 900

Reconnect = false

ProcessID = 7212

SessionID = 1389103

Driver = MaxDB 7.7

Started = 2009-07-14 00:13:46

I suppose the Driver is MaxDB 7.7 because another database (MaxDB 7.7) is also running on the same server.

Kind regards,

Christophe

[Melanie · Accepted solution]

Hello Christophe,

the reason for the warning is an outdated dbanalyzer config file. The config file is part of the independent software. That software was updated to version 7.7 when you installed/updated that database.

Although you updated your 7.6 database, the independent software does not get updated as it is already of version 7.7. So you didn't get a new dbanalyzer config file.

You can download the dbanalyzer config file from note 1102727 (although the note text describes a different problem...). An alternative would be to update the 7.7 database to a current version.

Best regards,

Melanie

[Former Member]

Hi Melanie,

I want to thank you for your great help to solve this issue.

Kind regards,

Christophe

[Former Member]

The Database Analyzer is automatically started by the system.

Christophe

[Former Member]

Hi Melanie,

Thanks for your answer.

I checked this note. I guess it isn't relevant, because the source version of the MaxDB upgrade was 7.6.03.09 here.

The Database Analyzer config file is OK here.

Christophe

[Melanie]

Hello Christophe,

when the upgrade to the currently used version was actually successful, the system tables were loaded during this update - if you used SDBUPD for the update... Please check the log file of the installation, if loading the system tables is mentioned in there. Additionally you can check file dbm.ins.

If the update was performed with SDBUPD and the system tables were loaded successfully, you can ignore this warning.

If you used SDBUPD but it could not load the system tables, try to load them manually. If this works, you'll need to start SDBUPD again to successfully finish the update. Otherwise you'll run into trouble with the next software update.

If you performed the update with SDBINST (which is not recommended...), then you probably missed loading the system tables. You can do that at any time manually.

Regards, Melanie

[Melanie]

Hi Christophe,

this might be an error of the dbanalyzer. Check note 1071912.

Regards,

Melanie