SAP Note 869267 Note Language: English

FAQ: SAP MaxDB LOG area
Version: 34 Validity:
Valid Since 21.07.2011

Summary
Symptom
This note contains questions that are frequently asked by SAP staff and customers. It provides answers and refers you to other information sources. The note is in no way complete. 1. 2. 3. Which information is written into the log area of the MaxDB database? What does the log configuration in a MaxDB database consist of? What do I need to pay attention to when configuring the log with MaxDB? Why should the log, data area, and swap not be on the same hard disks? Can I use RAID technology for the log area? Can I mirror the log area using database means? Which log settings are available in MaxDB version >= 7.5? How can I reduce the size of an existing logging configuration? What is a log segment? How are log segments configured? How large should log segments be when configured? What happens when a log segment is completed? Can I enlarge log segments online? Can I reduce log segments? What happens if a log volume fails when a log area is mirrored with MaxDB? Can I convert the log area to SINGLE myself in online mode? How do I integrate a new hard disk as log volume if a log volume has previously failed in "mirrored" mode? What danger is there if I do not mirror the log area? How does a LOG full situation occur? How do I recognize a LOG full situation? How do I resolve a LOG full situation? Where can I find more information about log backup?

4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.

16. 17.

18. 19. 20. 21. 22.

22.11.2011

Page 1 of

15

31. 32. 46. 35. 38. 43. 47. 33. 37. 27. 45. 26. 28. 36.SAP Note 869267 - FAQ: SAP MaxDB LOG area 23. 34.11. 42. 25. 40. 22. What do I do if I cannot successfully restart in a LOG full situation? Why is adding a new LOG volume not helpful in a LOG full situation? Can I enlarge the log area online? Can I deactivate log writing? What are the dangers of deactivating log writing? Can the log be overwritten cyclically without having to perform a log backup? What are REDO log entries (After images)? What are UNDO log entries (Before images)? Where are UNDO and REDO log entries stored? What causes the log area to be released again for overwriting? Which information does the DBMCLI command db_restartinfo provide? Which information does the DBMCLI utility command "get restart version" provide? When is the login information written on hard disk? What is the LOG IO queue for? What are LOG QUEUE overflows? What does it mean when tasks are in the "LOG FULL" status? What parameter do I use to configure the size of the LOG-IO-QUEUE? How many LOG-IO-QUEUES are configured? Where can I see how many LOG-IO-QUEUES are active? If I reduce the number of LOG-IO-QUEUES online. 44. 30.2011 Page 2 of 15 . 41.5 to 7. 39.6? What is a GROUP COMMIT? If I use shutdown to set the status of the MaxDB database to ADMIN or offline. does the shutdown wait until all transactions have been ended? Where do I find additional information on the subject of the database log? 29. are the changes active immediately? How large should I configure the LOG-IO-QUEUE? Why can the log backup increase after the migration from MaxDB 7. 24.

3. Definition of term: The term log area describes the quantity of log volumes. their name.sap. The cache of the hard disk system must be large enough so that it is not necessary to wait for physical hard disks . RAID-1. or the system delivers a comparable security that does not negatively affect performance. the log must be mirrored using the operating system devices or secured using the hardware that has comparable mechanisms (for example. or liveCache environment. If the parameter LOG_MIRRORED is set to NO. What do I need to pay attention to when configuring the log with MaxDB? Use the fastest hard disks available on the market for the log area. -0+1.I/O during writing of log pages. -10. Why should the log.sdn. If there is no sufficient redundancy of the log volumes. Configuration.2011 Page 3 of 15 . The database system uses these log entries in order to roll back or repeat individual SQL statements where necessary and thereby ensure transaction consistency.SAP Note 869267 - FAQ: SAP MaxDB LOG area Other terms FAQ. What does the log configuration in a MaxDB database consist of? A log area can consist of between 1 and 32 log volumes.11.com/wiki/x/GkM Solution 1. RAID.5 or above in an OLTP. under UNIX. and swap not be on the same hard disks? 22. 2. In systems in which the database must guarantee the persistence of the data. Further FAQ notes about MaxDB/live Cache are available available on SDN (SAP Developer Network): https://wiki. Mirroring can be done using MaxDB. When the database is installed. LOG. -DP) . Log Full. A log area that is not secured accordngly is therefore recommended only in test systems. The term log entry describes both UNDO and REDO log entries. loss of data will occur in the case of a disk error. Logging. data area. size and. the log volumes must either be mirrored. BW. 4. the number of log volumes (must not exceed/fall short of the parameter: MAXLOGVOLUMES). The information on the log volume is only used for the roll forward that is. Which information is written into the log area of the MaxDB database? The database system logs all changes to data by transactions in log entries. Reason and Prerequisites You are using a MaxDB database version 7. their type. Striping of hard disks for log volumes is only recommended if the hard disk system works with a large cache and log volumes are also mirrored. restart/recovery. is configured.

bear in mind that after log mode status has terminated. Which log settings are available in MaxDB version >= 7. However. The database instance can be in any operation status. 22. then start the activity. Choose -> Properties and. go to -> Instance -> Configuration -> Log Settings. You can activate mirroring of the log area using the Database Manager Gui. -10.5? For MaxDB-Version 7. Use this setting only if you cannot perform a hardware-based mirroring of the log area. The database system can only overwrite the log areas again if the log entries of the primary log area have been saved. Can I use RAID technology for the log area? You can use RAID-1. 5. the database system describes two log areas at the same time (primary and secondary log area). You are requested by the database manager to create the necessary mirror for the log volumes. specify the situation for the mirror. During software-based mirroring. under "Location". All users wishing to make changes have to wait in this situation. the database instance is always transferred to the OFFLINE operational status and then to the ONLINE operational status. A software-based mirroring will impair the performance of your database system. Select the log setting "Log Mode". Database-side mirroring is not proposed as default. 7.5 and above.). 6.SAP Note 869267 - FAQ: SAP MaxDB LOG area Changes to the data of a MaxDB database (AFTER images) are written asynchronously in the log area on the hard disk using a buffer known as the LOG IO queue. If the Logwriter cannot copy the log pages in the Log IO queue fast enough. log queue overflows occur in the case of write I/O for log volumes being too slow. You must therefore keep in mind that the I/O is not made worse by other actions (possibly because the data area or SWAP area are also contained on the log hard disks. RAID 5 is not to be recommended for safety and performance reasons. In most cases. The database instance is transferred on to the OFFLINE operational status and then OFFLINE operating status upon completion of this operation. the Log IO queue can fill up with pages that have not yet been written. -0+1.2011 Page 4 of 15 . This effect is called Log Queue Overflow. -DP to secure the log areas. Database-side mirroring should only be used when it is not possible to perform hardware-based mirroring of the log area. The situation can therefore be very critical for performance. Can I mirror the log area using database means? Yes.11. In the DBMGUI. the following log settings exist: a) Log mode The Log mode defines whether mirroring of the log area by the database system is software-based.

SAP Note 869267 - FAQ: SAP MaxDB LOG area The other log modes (DEMO. Overwrite mode is not activated as default. 10.11. you must execute a complete data backup. as they were known on MaxDB versions lower than 7. DUAL). The log backup history is thus interrupted. it can be useful to switch off Redo Log Management. Segmentation is not a physical division of the log area. This means you cannot restore your database instance up to the last COMMIT before system failure or any other time but only up to the time the last data backup was made. no log entries are then available for this time period. Note that log backup history is thus interrupted. In rare cases. Log segments determine the size of the files in which the log pages are saved. How are log segments configured? You set the size of log segments using the database kernel parameter 22. REDO Log Management is activated and the after images (REDO-LOG-entries) are saved in the log area.5. If you need to restore the database instance after an error. 8. The database system can only overwrite the log area if the corresponding log entries have been saved. b) Overwrite mode for log area Overwrite mode for the log area defines whether the database system can overwrite the log area without the log entries having been saved previously. are no longer supported. SINGLE.2011 Page 5 of 15 . 9. for example during a large loading job or an SAP upgrade. You set log settings in the Database Manager using Configuration -> Log Settings. How can I reduce the size of an existing logging configuration? You can reduce the size of the logging configuration using a restore data with an integrated configuration change (recovery with initialization). If overwrite mode is activated. Overwrite mode corresponds to the DEMO Log mode known from older versions of MaxDB. c) Switching off Redo Log Management (Activate or Deactivate the REDO Log Management) Redo Log Management defines whether the database system writes Redo Log entries (After Images). the database system overwrites the log area cyclically if no previous backups have been made to log entries. The log area is divided into segments of fixed length. What is a log segment? Log segments are backup units. If you switch off overwrite mode when this was switched on.

You determine the size of the files in which log pages are saved. How large should log segments be when configured? There is no absolute size recommendation for log segments. the database manager automatically calculates 1/3 of the entire log area.2011 Page 6 of 15 . 14.6. Can I reduce log segments? Yes. The segment size corresponds a maximum of half the log area. you change the size of the log segments using the parameter AutoLogBackupSize (LOG_SEGMENT_SIZE).11. As of MaxDB Version 7. reintegrate the full contents of the corresponding log volume mirrored in the primary log volume . but the change can only be 22. What happens if a log volume fails when a log area is mirrored with MaxDB? If the log area is mirrored by the database. A log segment is completed if the number of unsaved log pages exceeds AutoLogBackupSize (LOG_SEGMENT_SIZE). What happens when a log segment is completed? Log segments are NOT completed by a savepoint. it is essential that the database is started. some parameters can also be changed ONLINE.4 and above. With access problems to a log volume in the primary log area.6. 12. for example. If the value 0 is specified for the parameter AutoLogBackupSize (LOG_SEGMENT_SIZE). but the parameter AutoLogBackupSize (LOG_SEGMENT_SIZE) is among those that cannot be changed online. If autosave_log is activated. in the ADMIN operational status. the closed segment is saved automatically. 15. For a parameter change in MaxDB versions < 7.SAP Note 869267 - FAQ: SAP MaxDB LOG area AutoLogBackupSize (LOG_SEGMENT_SIZE). the database system selects the affected log volume as BAD and transfers the database instance to the OFFLINE operating status. 16. A log segment can consist of a maximum of half the entire log area. you can also reduce log segments using the parameter AutoLogBackupSize (LOG_SEGMENT_SIZE) without having to completely save the log area that is described beforehand. Log segments are backup units. 13. in DBMGUI using Configuration -> Log Settings -> LOG Mode. You can carry out the actions with the database in ONLINE status. A page has a size of 8 kbyte. These are specified in Pages. To restore the defective log volume. Enlarging the log area does not change the log segment size. Can I convert the log area to "SINGLE" in online mode? Converting the log area from "Mirrored" to SINGLE or vice versa always requires the database to be restarted. failure of a log volume results in an Emergency Shutdown. 11. replace the corresponding hard disk and then. Can I enlarge log segments online? No. the log volume cannot be integrated in the ONLINE status. For version 7.

see Note 1377148 (FAQ: SAP MaxDB Backup / Recovery). 17. If the log area is full. or if the log area has been switched off once in the meantime. If no database backup has been created on the affected database before the log backup. How does a LOG FULL situation occur? A Log Full situation only arises if the log area is not regularly saved. if the database is offline. What do I do if I cannot successfully restart in a LOG full situation? In a log full situation. the system can only write COMMITS/ROLLBACKS and SAVEPOINTS in the log. 23. How do I recognize a LOG full situation? If the log area becomes full.SAP Note 869267 - FAQ: SAP MaxDB LOG area carried out in conjunction with a stop/start database. the log area may not actually become full. How do I integrate a new hard disk as log volume if a log volume has previously failed in "mirrored" mode? For information about how to proceed.2011 Page 7 of 15 . Where can I find more information about log backup? For more information. You recognize a Log full situation in knldiag. you can see that user tasks were suspended due to another log full situation. a corresponding warning is written to knldiag. 21. 22. 18. as the unsaved log area cannot be used for a recovery. the tasks will have the status "LOG FULL" (x_cons <DBNAME> show tasks). for instance. a disk error will result in data loss. The log area can only be released for overwriting if it has been previously saved and then a SAVEPOINT was written. A log backup can also be created by switching on automatic log backup. Even if the log is set to OVERWRITE. What danger is there if I do not mirror the log area? If you do not make a copy of the log area. the restart may hang in rare cases due to the LOG full situation. 19. knldiag contains a relevant message. and no more changes can be made in the database. a data backup is still necessary before the log backup. In a LOG full situation. 20. Log backup can be created in ADMIN or ONLINE status.11. see Note 1177052. any further on-line operation is only possible if a log backup is created. An exception occurs if REDO Log Management is deactivated. With the database console. 22. as no log is then written. How do I resolve a LOG full situation? If the log has become full.

Backup history is broken down and flagged with the abbreviation HISTLOST. Switch off the Logwriter using the DBM command util_execute SET LOG WRITER OFF. you must first increase the parameter MaxLogVolumes (MAXLOGVOLUMES) before you can add a new log volume to the database. If the log volume is enlarged with a new log volume. 25. C A U T I O N: This is now permitted because the database is consistent with each savepoint. and repeat the restart. Expanding the log area does NOT resolve the LOG FULL situation. you have the option of switching off the Logwriter.4. 24. The function is used to accelerate such administration tasks as upgrades and larger loading jobs. What are the dangers of deactivating log writing? When the Logwriter is switched off.11. The current write position is only moved sequentially. To do this.2011 Page 8 of 15 . If the database crashes. you can only import 22. The backup history is restarted when you switch on the Logwriter again with the DBM command util_execute SET LOG WRITER ON in the ADMIN status and create a complete data backup in ADMIN or ONLINE status. 27. You must restart the database before the parameter change becomes active. you can perform a SAVE LOG in the ADMIN status of the database. this new volume is not described until the current write position from the last page of the preceding volume is changed. The position is not moved from the center of one log volume to the start of the next log volume. B U T: As long as the log is deactivated. the system writes NO savepoints implicitly. The Logwriter must not be deactivated for production operation. In the case of a RECOVERY triggered by hardware errors. this cannot be resolved by enlarging the log area. The log area can be enlarged online up to this number. 26. the backup history is lost.SAP Note 869267 - FAQ: SAP MaxDB LOG area In this situation. The parameter MaxLogVolumes (MAXLOGVOLUMES) specifies the maximum number of log volumes. Can I deactivate log writing? Yes. Can I enlarge the log area online? Yes. You can restart without log because you can roll back all open transactions based on the last savepoint. data loss may occur. Why is adding a new LOG volume not helpful in a LOG full situation? If the database has the status 'Log full'. If the value of MaxLogVolumes (MAXLOGVOLUMES) is reached. start the database with the ADMIN status. Log backups are not possible after switching off the the Logwriter. as of version 7.

Since no backup history exists for the following changes in the database. In Undo Log entries. 30.11. therefore you cannot tracked them. Log backups are not possible after switching on automatic overwrite. These are handled in exactly the same way as data pages with table and index information at the Savepoint . If you do not stop the database with a correct shutdown. The database system uses the Undo Log entries if it must roll back transactions that have not yet been completed (ROLLBACK).knl file). What are UNDO Log entries (BEFORE IMAGES)? The database system writes Undo Log entries (Before images) for every transaction that changes data in the database. C A U T I O N: Note that after you deactivate the log. With version 7.03 and above. 29. 28. The backup history is restarted when you switch off automatic overwrite without log backups using the command util_execute SET LOG AUTO OVERWRITE OFF and by creating a complete data backup in the ADMIN or ONLINE status.that is they are written into data volumes.4. Automatic overwrite of the log area without log backups is NOT suitable for production operation. the log area can be automatically overwritten without log backups. all data changes are irretrievably lost. Changes to the data will not have been logged. 22.SAP Note 869267 - FAQ: SAP MaxDB LOG area the last complete backup and any possible incremental backups. the system no longer writes implicit savepoints in love operation. a) UNDO Log entries (BEFORE images) Undo Log entries consist of one or more permanent data pages. Therefore.2011 Page 9 of 15 . What are REDO Log entries (After images)? The database system uses Redo Log entries (After images) if it has to repeat data changes carried out by a transaction that has already been completed. changes to data are not written to the disk. Redo Log entries therefore allow complete recovery of data after a crash or in the case of hard disk defects. you cannot track transactions in the case of recovery. this behavior can be set online. Backup history is broken down and flagged by the abbreviation HISTLOST in the backup history (dbm. Use the DBM command util_execute SET LOG AUTO OVERWRITE ON to set this status. All information that the database system needs to repeat transactions is saved in Redo Log entries. Where are UNDO and REDO log entries stored? MaxDB manages Redo and Undo Log entries separately. Can the log area be overwritten cyclically without having to make a log backup? Yes. the database system saves the original values for all database objects that the transaction is going to change. 31. The behavior of the database corresponds to the DEMO log mode in older versions.

known as the INFORMATION PAGE. for example.ber.The position before which the last backup was made . Log entries may only be overwritten if they have been saved and if the position of the last savepoint is still in the log area (Exception: SET LOG AUTO OVERWRITE ON).<DBMPWD> db_restartinfo OK Used LOG Page 7451 First LOG Page 2527 Restartable 1 Id Restart Record BERD00144137A.SAP Note 869267 - FAQ: SAP MaxDB LOG area b) REDO LOG entries (After images) Redo Log entries are written to the log area (log volumes) using the Log IO queue. Possible values are: 1: The database instance is restartable. 22. exists in the Log Volumes header. 0: The database instance is not restartable. This command is particularly important if shadow databases have been set up. After a successful log backup. The current write position is only moved sequentially. the database kernel first writes a Savepoint. In such cases the database does not allow any more write transactions to be made. Log pages can only be overwritten if they have been saved.The current character position .corp:MAXDB_75_20050914_165 Consistent 1 Used LOG Page is the log page number currently being used. Positions are managed on the information page. It is used. and the area that has just been saved is re-released for overwriting by the new position being noted in the LOG Info page.The position up to which overwriting may occur . Including: . the log area is full. A reserved page. What causes the log area to be released again for overwriting? The Log-area is cyclically overwritten. Which information does the DBMCLI command db_restartinfo provide? This command can be executed in the data base status ADMIN or ONLINE. (Exception: SET LOG AUTO OVERWRITE ON). This status cannot be resolved by enlarging the log area. Call: dbmcli -d <DBNAME> -u <DBMUser>.sap.2011 Page 10 of 15 .The number of the last log backup When the current write position reaches the page up to which overwriting may occur. 32. Restartable shows the restartability of the database.11. A subsequent log backup saves the area starting from the position after which a backup has not yet been made. If the Log Full status occurs. First LOG page is the oldest log page still contained in the log volume that may be imported directly by the log volume in the case of a recovery. that is not overwritten cyclically.ber. 33. to determine the setup point for a RESTORE LOG in the log area.sap.corp:MAXDB_75_20050914_165 Id LOG Info BERD00144137A. for example. the position after which a backup has not yet been made is moved accordingly.

sap. Output for the both commands described here may therefore differ. Restartable shows the restartability of the database.sap. Id LOG info provides the identifier for the log area of the database instance. RESTARTABLE WITHOUT LOG shows the restartability of the database.corp:MAXDB_75_20050914_165 RESTARTABLE WITHOUT LOG = 1 LOG VOLUME ENABLED = 1 LOG AUTO OVERWRITE = 0 MASTER SERVERNODE = CONVERTER VERSION = 57 OLDEST COMPATIBLE VERSION = 7. dbmcli -d <DBNAME> -u <dbmUser>.<pwd> util_execute get restart version OK FIRST IO SEQUENCE NEEDED = 7451 FIRST IO SEQUENCE ON LOG = 2527 RESTARTABLE = 1 DB IDENT FROM RESTARTRECORD = BERD00144137A. LOG VOLUME ENABLED specifies whether REDO Log Management is deactivated.corp:MAXDB_75_200509 DB IDENT FROM LOGINFO = BERD00144137A.0. 1= REDO Log Management is activated. Output for "get restart version" is subject to constant revision by developers however where a demand exists for more information. DB IDENT FROM RESTARTRECORD shows the DBIdent of the Restart Record. In MaxDB documentation. Log entries must be tracked so that you can track the open transactions. restartability without Log_Entries having to be tracked 1: Restartable without log 0: Not restartable without Log 34.ber. DB IDENT FROM LOGINFO shows the DBIdent of the Log area. 0: The database instance is not restartable.SAP Note 869267 - FAQ: SAP MaxDB LOG area Id Restart Record specifies the identifier for the restart record in the database instance. you will only find the command db_restartinfo described in the DBMCLI handbook. FIRST IO SEQUENCE ON LOG corresponds to the First LOG Page. 22. Possible values are: 1: The database instance is restartable.that is. These outputs are then copied successively to the DBMCLI command db_restartinfo.2011 Page 11 of 15 . Which information does the DBMCLI utility command "get restart version" provide? This command contains the same information as the command db_restartinfo.5.11.8 FIRST IO SEQUENCE NEEDED corresponds to the Used LOG Page.ber. This command can be sent in ADMIN and online status and is used by Development Support for detailed analysis in the case of recovery problems. 0: The database instance is not restartable. 0= REDO Log Management is deactivated. Possible values are: 1: The database instance is restartable without log entries having to be tracked. Consistent specifies the consistency of the database instance .

the database system writes Undo Log entries (Before images) for all database objects to be changed by the transaction into an Undo log file in the data area. 38.2011 Page 12 of 15 . OLDEST COMPATIBLE VERSION is the version that can still be reached with a downgrade. and this information is used for internal testing purposes. What are LOG QUEUE overflows? If the logwriter is unable to copy the log pages contained in the log queue quickly enough. 39. The database system then writes the Redo Log entries from the Log queues to the log area in asynchronously. 35. CONVERTER VERSION specifies the converter versions. you can display the status of database tasks using the "show tasks" command. All users wishing to make changes have to wait in this situation. A LOG Full Situation means no more entries can be written from the LOG IO queue to the Log area. The log queue may have to be enlarged. The DBM command "info log" displays the number of log queue overflows that have occurred since the instance was last restarted. What is the LOG IO queue for? The LOG IO queue (log queue) enables asynchronous writing of log entries. The database system always writes the redo log entries from the log queues into the log area when a page is full in the log queue or when a transaction is completed using a COMMIT. What does it mean when tasks are in the "LOG FULL" status? With the x_cons database console. 36.11. 1= the Log area is overwritten cyclically. When are the log entries (After Images) written to hard disk? At the beginning of a transaction in which data is going to be changed. After a transaction of this type has been completed using COMMIT. This status only occurs if the log area has become full and does not occur in normal operation. log queue overflows occur when the write I/O is too slow for the log volumes. 37. 0= The log area is NOT in overwrite mode. The situation can therefore be very critical for performance. log backup is not possible. This effect is called the log queue overflow. this means no more entries can be written in the Log IO queue.SAP Note 869267 - FAQ: SAP MaxDB LOG area LOG AUTO OVERWRITE specifies whether overwrite mode is activated for the log area. This problem is solved by a log backup. What parameter do I use to configure the size of the LOG-IO-QUEUE? 22. the database system first writes Redo Log entries into the log IO queue (log queues) in the main memory. If the tasks are in "LOGQ FULL" status. then the log queue can fill up with pages that have not yet been written. MASTER SERVERNODE specifies the master in Hotstandby systems. the database system writes Redo Log entries (After images) in the LOG IO queue in the main memory. In most cases.

2011 Page 13 of 15 .6. This means that. The changes become active if all entries from the LOG-IO-QUEUES that are no longer used due to the online changes of the parameter LogQueues (LOG_QUEUE_COUNT) are written to the log volume. 44. at most. For larger systems with more than 4 LOG-IO-QUEUES. A recommendation for setting the parameter LogQueues (LOG_QUEUE_COUNT) is available in the parameter notes for the MaxDB/liveCache version you use. the storage space on the log 22. and then written to disk again completely after a subsequent I/O. 42.6. 41.000 and 2. even if the LOG-QUEUE-PAGE is not full yet. you should first check whether the computer has sufficient memory available. Up to and including the MaxDB Version 7. the parameter of the MaxCPU (MAXCPU) determines the number of LOG-IO-QUEUES that are set.5 to 7. LOG_IO_QUEUE (parameter LogQueueSize (LOG_IO_QUEUE)) should be configured between 1. 43. LOG-QUEUE-PAGES that were partially filled and written to disk could be filled further. are the changes active immediately? No. The parameters MaxLogQueues (MAX_LOG_QUEUE_COUNT) and LogQueues (LOG_QUEUE_COUNT) determine the number of LOG queues.11. LOG-QUEUE pages that were already written to disk are no longer filled further. 40. If I reduce the number of LOG-IO-QUEUES online. only subsequent log entries are written to a new page. The memory area for the LOG-IO-QUEUE(s) is reserved. The system table contains one line for each LOG-IO-QUEUE.SAP Note 869267 - FAQ: SAP MaxDB LOG area Use the parameter LogQueueSize (LOG_IO_QUEUE) to configure the size of a log queue.5. This process takes place immediately. Where can I see how many LOG-IO-QUEUES are active? The system table LOGQUEUESTATISTICS provides detailed information about Log-IO-queues. As of MaxDB Version 7. Why can the log backup increase after the migration from MaxDB 7. on 64-bit platforms. The parameter LogQueues (LOG_QUEUE_COUNT) determines the actual number of LOG-IO-QUEUES used. The usable log area is calculated from the difference of the configured log area (size of the log file(s)) and (number of LOG-IO-QUEUES * size of LOG-IO-QUEUES). For this reason. Note that the size of the LOG-IO-QUEUE reduces the usable log area. MaxLogQueues (MAX_LOG_QUEUE_COUNT) is set to 0. The background for this is that the log entries that are already located in the LOG-IO-QUEUE(s) can still be written even if a LOG FULL situation occurs. How many LOG-IO-QUEUES are configured? As of MaxDB Version 7.000 pages if the number of LOG-IO-QUEUES is lower than 5. How large should I configure the LOG-IO-QUEUE? Experience has shown that. you can allocate the number of LOG-IO-QUEUES set with MaxCPUs (MAXCPU).6? LOG queue entries must be written to the log volume as fast as possible after a commit.

You must then roll back these terminated transactions the next time you start the database. log entries are written into the LOG IO queue.com/irj/sdn/maxdb In addition.sap. The database starts a save point to write all of the changed data from the cache to the hard disk. the subject of database logging is dealt with in detail in the MaxDB Internals Workshop WB550. this also applies to a "normal shutdown". it is known as a group commit. terminates any transactions that are still running.com/training/internals_7. "Log entry". "Log setting". If I use shutdown to set the status of the MaxDB database to ADMIN or offline.6/logging_EN_76. If there are several commit entries on a LOG_IO_QUEUE page. Several commits with an IO are written to the log device. you can use the SDN to access the MaxDB documentation. The database system does not wait until all transactions have ended. Where do I find additional information on the subject of the database log? You can find more information on the subject of the MaxDB Database Log in the glossary in the MaxDB documentation (Note 767598) under the key words "Log area". What is a GROUP COMMIT? Before they are written in the log volume. "Log reader" "Log mode".6) on maxdb.com under: http://maxdb. 47.11.sdn. 45.2011 Page 14 of 15 .sap. does the shutdown wait until all transactions have been ended? No. 46. Alternatively.07.SAP Note 869267 - FAQ: SAP MaxDB LOG area volume and therefore the log backups will increase for applications with a lot of short transactions (a lot of commits). "Logging".2011 06:17:49 German Recommendations/additional info Consulting BC-DB-SDB MaxDB The Note is release-independent 22.pdf Header Data Release Status: Released on: Master Language: Priority: Category: Primary Component: Secondary Components: BC-DB-LVC liveCache BW-SYS-DB-SDB BW MaxDB Released for Customer 21. "Log page" and so on. https://www. "Log segment". The system then shuts down the database instance and. as a result.sap. You can find the documents of the unit about logging (Version 7.

11.SAP Note 869267 - FAQ: SAP MaxDB LOG area Related Notes Number 1377148 1177052 1173395 1167342 993848 936058 846890 820824 534036 Short Text FAQ: SAP MaxDB backup/recovery Mirrored log: Recovery of deficient log volume FAQ: MaxDB configuration MaxDB parameter LOG_QUEUE_COUNT as of version 7.2011 Page 15 of 15 .6 Direct I/O mount options for liveCache/MaxDB FAQ: SAP MaxDB Runtime Environment FAQ: SAP MaxDB Administration FAQ: SAP MaxDB/liveCache technology SAP LT: System settings for conversions 22.

Sign up to vote on this title
UsefulNot useful