Note 940420 - FAQ: Database structure check (CHECK DATA/VERIFY)

Summary

Symptom

This note deals with questions and answers on the subject of the SAP MaxDB/liveCache database structure check (VERIFY). The database structure check is also named CHECK DATA or CHECK TABLE. The note is both for the customer and support to answer queries on the topic of a database structure check in an SAP MaxDB/liveCache database. The note is in no way complete.

1. What is a database structure check (VERIFY)?

2. What types of database structure check can be carried out?

3. Which database structure checks are carried out on containers in the liveCache environment?

4. Is there a difference between the CHECK DATA in the ONLINE operational state and the CHECK DATA in the ADMIN operational state?

5. Can the database structure check also repair defective data pages?

6. What is an extended database structure check?

7. Is there also an extended database structure check in the liveCache environment regarding containers?

8. Is history data also checked during the CHECK DATA in liveCache?

9. When creating a backup, checks are also carried out. Are these the same checks that a VERIFY carries out?

10. Why must database structure checks be carried out regularly?

11. How often should a database structure check be carried out?

12. Why should the database structure check be carried out on a system copy?

13. What should you note if you use transaction DB59 to execute CHECK DATA on a system copy?

14. What are the advantages of carrying out a database structure check on a system copy?

15. Can the database structure check can be carried out when the system is running, or will this cause locking problems?

16. Can a backup check (CHECK SAVE) replace the database structure check?

17. Which type of the database structure check is recommended - with or without the option EXTENDED?

18. Which factors do the runtime of the database structure check depend on?

19. Which factors do the parallelism of a database structure check depend on?

20. How do I carry out a database structure check?

21. How do I start the database structure check using the Database Manager graphical user interface (GUI)?

22. How do I start the database structure check with the Database Studio?

23. How do I start the database structure check using the Database Manager command line interface (CLI)?

24. Which type of database structure check is recommended in the SAP environment (OLTP, BW, CS and liveCache)?

25. Which database structure check is carried out in transaction DB13 or DB13C during the 'Check database structure all objects'?

26. Which database structure check is carried out in transaction DB13 or DB13C during the 'Check database structure only tables'?

27. Which type of the database structure check is designated by the action VERI in transaction DB13 or DB13C?

28. Which type of the database structure check is designated by the action VERIX in transaction DB13 or DB13C?

29. Can I also carry out a database structure check in the liveCache environment for a certain container?

30. How can I tell that a database structure check is active?

31. Can I start a database backup during an active 'check database structure all objects ' or a 'check database structure only tables'?

32. Can I shut down the database using a 'normal shutdown', when a 'Check database structure all objects ' or a 'Check database structure only tables' is active?

33. How can I terminate a CHECK DATA?

34. How can I terminate a CHECK TABLE or CHECK INDEX?

35. Where are errors detected by the database structure check logged?

36. Can I also start a database structure check with an external program?

37. Are there SAP liveCache versions in the liveCache environment in which I should not start a database structure check?

38. Are there SAP MaxDB versions on the content server in which a database structure check must not be carried out?

39. Where can I find more information on the database structure check?

Other terms

FAQ; VERIFY; CHECK DATA; CHECK TABLE; Database structure check; Systems analysis

Reason and Prerequisites

You use SAP MaxDB/liveCache Version 7.4, 7.5, 7.6, 7.7or 7.8 in your SAP system environment.

Further FAQ notes about SAP MaxDB/liveCache are available in the SAP Developer Network (SDN) at:
https://wiki.sdn.sap.com/wiki/x/GkM

Solution

1. What is a database structure check (VERIFY)?

During a database structure check, the database system checks whether the database structures are consistent (for example the consistency of the B* trees), but not the semantics of the data model. Therefore you cannot use a database structure check to find any logical errors.

2. What types of database structure check can be carried out?

a) Check of the entire dataset (tables and indexes) in the ONLINE operational state (CHECK DATA)

b) Check of the entire dataset (tables and indexes) in the ADMIN operational state (CHECK DATA)

c) Check of one or several selected tables in the ONLINE operational state (CHECK TABLE)

d) Check of one of the selected indexes in the ONLINE operational state as of Version 7.8 (CHECK INDEX)

3. Which database structure checks are carried out on containers in the liveCache environment?

For containers, the following is checked during the CHECK DATA:

• A check is carried out to determine whether the double chain of pages in the container is correct and whether all the pages in the chain also belong to the container you want.

• A check is carried out to determine whether all pages from the root to the end of the chain have a descending sequence number. This is important, to avoid the object iterators creating deadlocks.

• A check is carried out to determine whether all pages that have "free" objects also hang in the free chain of the container.

• For each page, the object management on the page is checked (these are various counters and the free chain of unused objects).

• A check is carried out to determine whether the fixing of the history (Undo/Before Image) exists and whether it is valid for all objects indicated as 'Deleted'. The garbage collector can only release this object later if this history still exists.

• For OmsKeyedObjects, checks are carried out for each object to determine whether the entry with the key of the object exists in the inversion and whether this entry also refers back to the object (meaning that it contains the correct OID).

4. Is there a difference between the CHECK DATA in the ONLINE operational state and the CHECK DATA in the ADMIN operational state?

a) CHECK DATA in the ONLINE operational state

In the ONLINE operational state, the database system checks the structural consistency of all tables, indexes, LONG columns and so on, in the cache and in the data area.

Whenever the database system reads data pages from the data area, it calculates a check sum that must correspond to the check sum stored on the page.

The database system goes through all B* trees and page chains once completely. It checks whether all the pages in the B* trees or page chains can be reached, and whether the management structures on the pages are intact (for example, the separators at the B* tree index level).

b) CHECK DATA in the ADMIN operational state

First, in the ADMIN operational state, the database system carries out the same checks as in the ONLINE operational state.

If no errors occur during this CHECK DATA, the database system cleans up the converter using the results of the checks: it deletes all pages that it did not read during the checks, to which there are no longer any references to the converter.

If 'BAD INDEXES' are found during the CHECK DATA, the converter is not cleaned up. Therefore, make sure that the indexes indicated as BAD are created again before the database structure check is carried out in the ADMIN operational state.

5. Can the database structure check also repair defective data pages?

No, the database structure check in the ONLINE status only checks the structures and does not carry out any corrections in the dataset.

The database structure check in the ADMIN operational state cleans up only the converter of references to data that no longer exists. Defective data structures cannot be corrected in the ADMIN operational state either (for example -9026 BAD DATA PAGE).

6. What is an extended database structure check?

The extended database structure check is also known as CHECK DATA EXTENDED or CHECK TABLE EXTENDED. In addition to the checks already listed above in the ONLINE operational state of the database, you can check the length and ascending sequence of the keys (among other things).

In SAP MaxDB Versions 7.5 and 7. 6, this check was previously not carried out by default during CHECK DATA or CHECK TABLE. You must specify the keyword EXTENDED in SAP MaxDB Version 7.5 to carry out this extended check.

As of SAP MaxDB Version 7.6. 00 Build 30 (PTS 1141376), the extended check (as it is known in Version 7.5) is also carried out if you do not specify the keyword EXTENDED.

7. Is there also an extended database structure check in the liveCache environment regarding containers?

No, the EXTENDED option has no effect with regard to containers. No extended checks are carried out.

8. Is history data also checked during the CHECK DATA in liveCache?

History data (history directory, history file and undo file) are not checked during CHECK DATA.

9. When creating a backup, checks are also carried out. Are these the same checks that a database structure check carries out?

No, when you create backup, a check sum is always calculated when the database system reads a data page from the data area in the data cache. This check sum must correspond with the check sum stored on the page. All further checks that are carried out during the database structure check are not carried out during the backup.

A CHECK SAVE does not replace the CHECK DATA.

10. Why must database structure checks be carried out regularly?

Minimal checks are carried out on the data pages during a backup, but no structure check is carried out on the B* trees. To determine inconsistencies caused by hardware errors, a database structure check at regular intervals is absolutely necessary.

11. How often should a database structure check be carried out?

We recommend that you carry out the database structure check once a week on a system copy with a current backup.

12. Why should the database structure check be carried out on a system copy?

To check the B* trees of the tables, indexes and blobs, the data pages of the hard disk must be loaded into the data cache. As a result, application data from the cache can be displaced on the hard disk. Indirectly, the applications are affected negatively by the displacement of the data. The I/O load increases and the response time of the applications worsens. Therefore, you should carry out the database structure check on a system copy.

13. What should you note if you use transaction DB59 to execute CHECK DATA on a system copy?

Since the CCMS cannot determine whether the database structure check was carried out on the copy, after some time, alerts are generated that indicate to you that no database structure check has occurred for a long time. To prevent this, you should deactivate the "Database Structure Check" and "Last Check Return Code" nodes.

14. What are the advantages of carrying out a database structure check on a system copy?

SAP recommends that you carry out the database structure check on a system copy up to SAP MaxDB Version 7.6.00 Build 29 using the EXTENDED option that was set up with the most current backup (SAVE DATA) of the production system.

This has the following important advantages:

a) The backup is checked simultaneously. After a clean CHECK DATA on the system copy, this establishes that this backup can be used for a recovery, because no structural inconsistencies determined using CHECK DATA existed in the system at the time of the backup.

b) The CHECK DATA does not affect production operation by creating a high CPU load or displacing application data from the data cache.

15. Can the database structure check can be carried out when the system is running, or will this cause locking problems?

It is possible (but not recommended!) to start the database structure check in parallel during production.

In the SAP DB versions (7.3 and 7. 4), expect lock problems. The lock problems may occur because the database structure check run (VERIFY) sets locks on the root page whose tree has just been checked. You cannot access application tasks in parallel on the same page. This lock situation can last some time, particularly when checking large tables, and can cause significant problems. We therefore recommend strongly that you do not carry out the database structure checks parallel to online production.

In Version 7. 5 and higher, the entire B* tree is not locked; but SAP MaxDB works with partial tree locks. The system still sets locks during UPDATE STATISTICS, but these are more frequently released to the tasks that are waiting for the locks during a CHECK DATA. As a result, lock problems (PTS 1107714) as they occurred in Version 7.3 and 7.4 are no longer to be expected. From a performance point of view, however, we do not recommend that you start the database structure check in parallel to online production because a database structure check is very CPU-intensive and is quite time-consuming. In addition, all data in the cache must be loaded and as a result, a large number of I/O operations must be carried out. Only schedule a check in the production system at times when the database system is not under a heavy load, or better still, carry out the check in a current database copy of the production system.

In the liveCache environment, a DEADLOCK CANNOT occur during the CHECK DATA on a container in the ONLINE operational state.

16. Can a backup check (CHECK SAVE) replace the database structure check?

No, a CHECK SAVE only checks whether the backup is complete and not the pointing of individual pages to each other. A CHECK SAVE is not a database structure check and thus does not replace the CHECK DATA under any circumstances.

17. Which type of the database structure check is recommended - with or without the option EXTENDED?

The extended check with the EXTENDED option is possible as of Versions 7.3.00 Build 53, 7.4.03 Build 38 and 7.5.00 Build 20 (PTS 1131551).

If you use a SAPDB/SAP MaxDB that already provides the EXTENDED option, you must choose this in preference to the simple CHECK DATA or CHECK TABLE.

As of SAP MaxDB Version 7.6. 00 Build 30 (PTS:1141376), the extended check (as in 7.5) is also carried out without specifying the keyword EXTENDED.

18. Which factors do the parallelism of a database structure check depend on?

During the CHECK DATA, the number of data volumes determines the number of parallel processes (server tasks) with which the CHECK DATA is performed.

During the CHECK TABLE, a user task is started for every CHECK TABLE, which carries out the database structure check on the B* tree of the respective table.

19. Which factors do the runtime of the database structure check depend on?

The runtime of the CHECK DATA depends on:

• the size of the occupied area in the database

• the size of the data cache

• the workload

• the number of data volumes during CHECK DATA

• MAXCPU

By adding the option EXTENDED, an extended check is carried out, which does not have a significant effect on the runtime of the database structure check.

20. How do I carry out a database structure check?

a) Start the database structure check using the Database Manager GUI.

b) Start the database structure check using Database Studio.

c) Start the database structure check using the Database Manager CLI.

d) Start the database structure check using transactions DB13 and DB13C.

e) Start the database structure check using the external program XPU.

f) Start CHECK TABLE or CHECK INDEX in SQL Studio.

21. How do I start the database structure check using the Database Manager graphical user interface (GUI)?

You can start the database structure check in the Database Manager GUI using "Check".

a) ONLINE operational state:

• 'Check database structure' checks the complete database. Using the EXTENDED option, you can activate further checks. Using the EXTENDED option, you can activate further checks. Usually you can accelerate the runtime of the check using this option. This means that no indexes are checked. If structural inconsistencies are detected in an index during production operation, this is indicated as BAD and you can correct it using Delete and Create New.

• 'Check database structure for a selected table': here you can restrict the check to individual tables. When you specify the table name, you cannot use any wildcards. If the table has BLOBs, you can use the option WITH LONG CHECK to check whether all LONG values defined there exist. Due to the transaction consistency, an SQL shared lock is requested for the duration of the check.

b) ADMIN operational state

'Check database structure and clear converter' checks the entire dataset and cleans up the converter. We recommend this check, for example, if a backup terminates with a system error after you recreate an index that was indicated as 'Bad', because the pages of the index that was already deleted is still indicated as relevant for the backup in the converter. You can also carry out an extended check using EXTENDED in the ADMIN operational state.

22. How do I start the database structure check using Database Studio?

You can start the database structure check in the Database Studio by choosing "Administration Tasks -> Check Database Structure".

"Check the complete database structure" checks the entire dataset. By choosing "Advanced", you can select the following alternatives:

• Check a table

• Check an index

• Check the complete database structure in operational state ADMIN

23. How do I start the database structure check using the Database Manager command line interface (CLI)?

a) Up to and including Version 7.4.02, the CHECK DATA is carried out using a utility session:

dbmcli util_execute verify

b) As of Version 7.4.03, you should use the DBM command db_execute:
dbmcli db_execute check data [extended] [except index]
dbmcli db_execute check table [extended] [with long check]
dbmcli db_execute check table catalog
dbmcli db_execute check index on

In the ADMIN operational state, the call of CHECK DATA must look as follows:
dbmcli db_execute check data [extended] with update

24. Which type of database structure check is recommended in the SAP environment (OLTP, BW, CS and liveCache)?

During the database structure check, the system distinguishes between:
-> a check on the entire dataset
-> a check on the dataset except for the indexes
-> a check on tables

In OLTP systems, content server systems, and BW systems, all three types of database structure check are useful. In the SAP liveCache environment, it does not make sense to analyze only the tables, because the liveCache objects are not checked in this case.

In the SAP System, we recommend that you carry out the database structure check on a system copy. If the system copy is a complete OLTP or BW system with an application server, you can use transaction DB13 to schedule the database structure check. If the system copy is only a database (content server, SAP liveCache, or even OLTP or BW), you can include it in an SAP system using transaction DB59, and you can carry out the database structure check remotely using transaction DB13C or using the DBA Cockpit.

In SAP Releases 46C and 46D, Transaction DB13C is not yet available. A remote database structure check is not possible using DB13C. In the case of pure databases, you can carry out the database structure check using the Database Manager CLI or the Database Manager GUI on the system copy.

25. Which database structure check is carried out in transaction DB13 or DB13C during the 'Check database structure all objects'?

In this instance, it is important to distinguish between the individual SAP releases:

a) SAP Basis 4.6C and 4.6D

In these earlier releases, the XBACKUP tool with the option -a VERIFY is used for the database structure check. A utility session is used to execute the CHECK DATA. You cannot run this in parallel.

b) SAP Basis 6.10 lower than Support Package 46, SAP Basis 6.20 lower than Support Package 58, and SAP Basis 6.40 lower than Support Package 16

In the specified Support Packages, a utility session is opened using the Database Manager CLI.
dbmcli util_execute verify

c) SAP Basis 6.10 Support Package 48 and higher, SAP Basis 6.20 Support Package 62 and higher, and SAP Basis 6.40 Support Package 20 and higher

Which commands are started in these releases depends on the database version used (PTS:1146232):

If you use an SAP MaxDB version lower than Version 7.5, a utility session is opened using the Database Manager CLI:
dbmcli util_execute verify

If you use SAP MaxDB Version 7.5 or higher, the DBM command 'db_execute check data' is executed.

The command db_execute uses a user task to perform the CHECK DATA as long as free user tasks are available. If all user tasks are occupied, the utility task is still used in SAP MaxDB Version 7.5.

d) SAP Basis 7.0

The commands started in these releases also depends on the database version used:

If you use an SAP MaxDB version lower than Version 7.4, the utility session is also started in these SAP releases:
dbmcli util_execute verify

If the customer uses SAP MaxDB Version 7.4.03 or higher and lower than 7.6, a utility session is started with the command CHECK DATA:
dbmcli util_execute check data

As of SAP MaxDB Version 7.6, the command 'db_execute check data' is used, which no longer opens a utility session as of these SAP MaxDB versions. This means that backups and a normal shutdown are possible in parallel with the action 'Check database structure all objects'.

26. Which database structure check is carried out in transaction DB13 or DB13C during 'Check database structure only tables' (VERIX)?

In this instance, it is important to distinguish between the individual SAP releases and database versions:

a) SAP Basis 4.6C and 4.6D

SAP MaxDB version lower than 7.6:
The database structure check on tables is carried out using five parallel XPU processes in five SQL sessions. This action cannot be carried out remotely using Transaction DB13C because the XPU tool is not remote-enabled.

SAP MaxDB Version 7.6 or higher
See Note 978717.

b) SAP Basis 6.10, 6.20, and 6.40

SAP MaxDB Version lower than 7.6:
The database structure check on tables is carried out using XPU in SQL sessions. As of the SAP versions mentioned here, the number of parallel XPU sessions can be configured. The default setting is 10 parallel XPU sessions. This action cannot be carried out remotely using Transaction DB13C because the XPU tool is not remote-enabled.

SAP MaxDB Version 7.6 or higher
See Note 978717.

c) SAP Basis 7.0

As of SAP MaxDB Version 7.04.03, the DBM command 'dbmcli db_execute check data except index' is available. All objects apart from the indexes are checked in the database. This action is now also remote-enabled and can therefore be used by transaction DB13C, for example, in the SAP liveCache environment.

If you use database Version 7.4.03 or higher and lower than 7.6, then this action is executed by Database Manager CLI using a utility session.

As of SAP MaxDB Version 7.6, this action is executed using an SQL session.

27. Which type of the database structure check is designated by the action VERI in transaction DB13 or DB13C?

The entry VERI in the DBA Planning Calendar (transaction DB13 or DB13C) designates the action 'Check database structure all objects'.

28. Which type of the database structure check is designated by the action VERIX in transaction DB13 or DB13C?

The entry VERIX in the DBA Planning Calendar (transaction DB13 or DB13C) designates the action 'Check database structure only tables'.

29. Can I also carry out a database structure check in the liveCache environment for a certain container?

Up to now, you could not carry out a CHECK DATA on individual containers.

30. How can I tell that a database structure check (CHECK DATA) is active?

a) You can find the following entries in knldiag while CHECK DATA is active:
53022 INDEX Check Index: 15876 (Root)
53022 B*TREE Check Table: 44919 (Root)
53022 INDEX Check Index: 74733 (Root)
53022 B*TREE Check Table: 104408 (Root)
53022 B*TREE Check Long: 181 (Root)
53022 B*TREE Check Table: 433 (Root)
53022 B*TREE Check Long: 15844 (Root)
53022 B*TREE Check Table: 30221 (Root)
53022 B*TREE Check Table: 62955 (Root)

b) In the DBM logs (dbm.utl), you can find the following entry:
REQ CHECK DATA EXCEPT INDEX

However, no return code (RETURN CODE 0) has been entered for this action yet.

c) You use SAP MaxDB Version 7.5:

You find a user task with the status 'Wait for servertask' in the Task Manager of the Database Assistant (transaction DB50, active tasks) or in the console (x_cons show active). This indicates that server tasks were requested using these user tasks. Note however: These server tasks must not necessarily carry out a CHECK DATA, but this message also appears when a CREATE INDEX is active, for example.

d) You use SAP MaxDB Version 7.6:

You find a user task with the status 'Wait for Job' in the Task Manager of the Database Assistant (transaction DB50). This user task requested server tasks to perform the CHECK DATA. Server tasks that are busy with the CHECK DATA are listed in the Task Manager under the name CHKDATA.

31. Can I start a database backup during an active 'check database structure all objects ' or a 'check database structure only tables'?

You cannot start a database backup if the utility session is occupied during the 'Check database structure all objects ' or during the 'Check database structure only tables' by the DBM command util_execute.

32. Can I shut down the database with a 'normal shutdown', when a 'Check database structure all objects ' or a 'Check database structure only tables' is active?

You cannot carry out a 'normal shutdown' if the utility session is occupied during the 'Check database structure all objects' or during the 'Check database structure only tables' by the command util_execute.

33. How can I terminate a CHECK DATA?

When the CHECK DATA is triggered by a user task (Coordinator), this activates a corresponding number of server tasks that carry out the CHECK DATA. To terminate the CHECK DATA, you must terminate the Coordinator. If you scheduled the CHECK DATA using WebAs, then check which work process the CHECK DATA carries out under "Job Details" in transaction SM37. Using the application PID of the work process, you can then determine the database task (coordinator) that was instructed to carry out the CHECK DATA and terminate it using the Task Manager in the Database Assistant (transaction DB50).

If the CHECK DATA is active on large objects, it may also be necessary to terminate the server tasks that are busy with the CHECK DATA.

SAP MaxDB Version 7.5:

In Version 7. 5 (as described above), it is not easy to find out which server tasks are busy with a CHECK DATA. You should make sure that no other actions are active in the system to avoid inadvertently terminating a CREATE INDEX, for example, before you have terminated the server tasks, or allowed SAP Support to do this.

SAP MaxDB Version 7.6:

As of Version 7. 6, however, you can easily identify the server tasks by the name (CHKDATA) and also terminate them if required.

SAP MaxDB Version 7.7:

Important: As of Version 7.7.03. 14, a "check data with update" (that is, in the ADMIN operational state) leads to the deletion of data that is still required if one of the server tasks involved is terminated using "Cancel". These problems do not occur if only the coordinator tasks or the CHECK DATA in the ADMIN operational state are terminated using db_stop. (PTS:1189360) See Note 1366652.

The corrections should be available as of the following database versions:
7.7.04 Build 37 (PTS 1189365)
7.7.06 Build 16 (PTS 1189367)
7.7.07 Build 07 (PTS 1189368)
7.7.08 Build 00 (PTS 1189358)
7.8.00 Build 18 (PTS 1189361)
7.8.01 Build 04 (PTS 1189363)
7.9.00 Build 06 (PTS 1189362)
7.9.01 Build 03 (PTS 1189364)
7.9.02 Build 01 (PTS 1189359)

34. How can I terminate a CHECK TABLE or CHECK INDEX?

The CHECK TABLE or CHECK INDEX is not performed using server tasks, but is performed directly by the user task on the B* tree. To terminate a CHECK TABLE or CHECK INDEX, you must terminate the corresponding user task (I/O WAIT). To ensure that you do not inadvertently terminate the wrong user task in the task manager, make sure no other applications are active.

35. Where are errors detected by the database structure check logged?

Errors that were found during the database structure check are written to knldiag.err (Error database) knldiag or to the database files. As of MaxDB-Version 7.7, the name of these files is KnlMsg or KnlMsgArchive.

36. Can I also start a database structure check with an external program?

The external program XPU with the option -v is replaced by the DBM command db_execute in the long run. We recommend that you adjust customer-specific scripts accordingly because you should no longer use XPU outside of transaction DB13 in the new SAP MaxDB Versions 7.5 and 7.6 and the following versions.

The external program XBACKUP is used exclusively in the SAP Releases 46C and 46D in transaction DB13. Using XBACKUP outside of these releases and outside of transaction DB13, for example, in scripts or at operating system level, is not supported.

37. Are there SAP liveCache versions in the liveCache environment in which I should not start a database structure check?

In the past, if you used certain SAP liveCache versions, a database structure check was counter-productive. If this occurs, this will be described in a new note. Search the SAP support portal for notes with the keywords 'CHECK DATA' or 'VERIFY' in the component BC-DB-LVC.

38. Are there SAP MaxDB versions in the content server environment in which a database structure check must not be carried out?

For more information, see Note 852168.

To take current problems in this environment into account, search the SAP support portal for notes with the key word 'CHECK DATA' or 'VERIFY' in the component BC-DB-SDB.

39. Where can I find more information about the database structure check?

Refer to Note 767598. This note tells you where you can find the SAP MaxDB documentation. Use the glossary under the keyword 'database structure' to access the documentation.

Alternatively, you can use the SDN to access the SAP MaxDB documentation on the SAP MaxDB page:

https://www.sdn.sap. com/irj/sdn/maxdb

Header Data

Release Status:	Released for Customer
Released on:	04.11.2011 07:58:10
Master Language:	German
Priority:	Recommendations/additional info
Category:	FAQ
Primary Component:	BC-DB-SDB MaxDB
Secondary Components:	BC-DB-LVC liveCache
	BW-SYS-DB-SDB BW MaxDB
	BC-DB-LVC-CCM LiveCache Administration and Montitoring