A question about db_restartinfo

[Former Member]

In MaxDB documention there is an example of db_restartinfo:

-

---

>dbmcli -u OLEG,MONDAY -d DEMODB db_restartinfo

OK

Used LOG Page 710

First LOG Page 2147483647

Restartable 1

Id Restart Record PARMA:DEMODB_20060202_141737

Id LOG Info PARMA:DEMODB_20060202_141737

Consistent 1

Log Volume Enabled 1

Log Auto Overwrite 1

Master Servernode PARMA

Converter Version 13

Oldest Compatible Version 7.6.00.22

Queue Count 1

-

---

Can somebody on this list explain why "First LOG Page" has

such a high value and why it is greater than "Used Log Page"?

I have also seen a similar output on one of our systems?

(It can also not be a misprint in the documentation:-))

Edited by: Mahmoud Nikbakht on Mar 30, 2010 9:57 AM

[Former Member]

Hi,

the value for FIRST LOG PAGE is the maximal value storable in a signed int4-variable.

And such thing is used very often for initialization, perhaps before the first shutdown of your system is done.

You should not worry about this.

Elke

[Former Member]

Hi,

I'm curious about your explanation regarding "First LOG Page" and "Used LOG Page"

in the following example:

-

---

Used LOG Page 63032192

First LOG Page 61093090

Restartable 1

Id Restart Record hilbert:mindb_20091128_165725

Id LOG Info hilbert:mindb_20091128_165725

Consistent 1

Log Volume Enabled 1

Log Auto Overwrite 0

Master Servernode HILBERT

Converter Version 154878

Oldest Compatible Version 7.7.03.07

Queue Count 15

Repository Imports NO

-

---

Can you make a statement about how big the log volume (a lower bound)

is based on these numbers (page size = 8K)?

Edited by: Mahmoud Nikbakht on Apr 1, 2010 7:20 PM

[former_member229109]

Hello Mahmoud,

1. u201CCan you make a statement about how big the log volume (a lower bound)

is based on these numbers?u201D

If you are SAP customer, please see the answer on the question 33. In the SAP note 869267. The db_restartinfo dbm command is used to display the restart information after importing a backup.

Please review the document at http://maxdb.sap.com/doc/7_7/44/fc2a1fed0641dee10000000a1553f6/content.htm

Please also review the document u201CLog Areau201D at http://maxdb.sap.com/doc/7_7/19/d2235b234b4339b07627c8a1f2bfab/content.htm

The Comprehensive information about the log area you could get using u201Cinfo logu201D dbm command,

see more details at http://maxdb.sap.com/doc/7_7/95/fb57fa58fa4136b98efe181bd24a97/content.htm

You could run u201Cparam_getvolsallu201D to check how big the log volume is. May be you have more as 1 log volume. Using param_getvolume you will display the info-data of an individual volume.

Example:

u2026

dbmcli on NLK>param_getvolsall

OK

LOG_MIRRORED YES

MAXLOGVOLUMES 2

MAXDATAVOLUMES 11

LOG_VOLUME_NAME_001 1920 F LOG_001

M_LOG_VOLUME_NAME_001 F LOG_M_001

DATA_VOLUME_NAME_0001 2560 F DAT_0001

---

dbmcli on NLK>param_getvolume 1 LOG

OK

LOG_001 -> Name of the device/file

F -> Type of volume (such as file, raw device)

1920 -> Size of the volume < in pages >

2. u201C(page size = 8K)? u201C Yes. The unit that the database system uses to write information to and read it from the permanent storage is a page of 8 KB. A page corresponds to a certain number of operating system blocks. Pages are often the unit used to specify memory and disk space.

Thank you and best regards, Natalia Khlopina