Update statistics for Java only SAP systems

[Former Member]

Hello,

We've got several standalone Java instances for SAP NetWeaver 7.0 SR2.

I've read that you shouldn't use the DBMgui for the update of the database statistics, but you should use DB13 instead. In Java only, DB13 is obviously not available. How should I update the database statistics in a standalone Java installation?

best regards, Wilbert

[markus_doehr2]

You can connect from a WebAS 7.00 (with a recent support stack level) using DB59 (to create the connection) and then DB13C to schedule the update statistics.

You can also use the new DBACOCKPIT as of WebAS 7.00 SP12 (or SP13? I don´t remember exactly).

You can also schedule it using operating system scheduler (e. g. cron).

Have a look at note 927882 - FAQ: MaxDB Update Statistics

Markus

[Former Member]

Hello Marcus,

Would you also know the syntax if I want to schedule it using dbmcli? I'll look into DB59 aswell.

Regards, Wilbert

[markus_doehr2]

Did you have a look at the mentioned note? Point 16...

Markus

[Former Member]

Hello Marcus,

Yes, I saw the note. When I execute the update from dbmcli, nothing is done. Table SYSUPDSTATWANTED contains no records. I've setup the connection from DB59 and am awaiting a system restart. After that, I'll try DB13C for the update.

Regards, Wilbert

[markus_doehr2]

What do you mean with "nothing is done"? Table SYSUPDSTATWANTED is not updated by that call.

A Java database is pretty small compared to an ABAP database and due to that call using parallel execution, it may finish pretty quickly.

Markus

[Former Member]

I thought that table SYSUPDSTATWANTED was used to determine which tables need a statistics update. Since the table is empty, noting is done. The call immediately replies "Ok" when executed.

[markus_doehr2]

If you execute "dbmcli -U c_J2EE db_execute update statistics * estimate" the update statistics is done for ALL tables.

The table SYSUPDSTATWANTED is filled by running dbanalyzer or by an explicit "check" for the statistics.

If this is a Java-only system, you need to use the above command with xuser key "c_J2EE" instead of "c".

Markus

[Former Member]

Okay, now it gets a bit confusing.....

I execute the call with CONTROL as user. That is not correct?

[markus_doehr2]

The control user is correct.

The control user in an ABAP system has an xuser key "c", in a Java-only system, this key is "c_J2EE". If you call dbmcli with the full user and password it´s ok

Markus