7.7.x vs. 7.6.x: New parameter names confusing/ambigous

[Former Member]

7.6:

USE_OPEN_DIRECT			YES
USE_OPEN_DIRECT_FOR_BACKUP	YES

If set to "yes" O_DIRECT is used.

7.7:

UseFilesystemCacheForVolume	YES
UseFilesystemCacheForBackup	YES

So does that mean, that this needs to be set to "NO" to archive the same as with "YES" under 7.6?

If yes, are there more of those semantic + rename changes?

Markus

[lbreddemann · Accepted solution]

Hi Markus,

yes, the Parameternames have been changed (and the semantics according to the parameter name).

Please don't ask me how I like this, but at least it has been documented:

[Documentation of SAP MaxDB Database Version 7.7 - Database Parameter|http://maxdb.sap.com/doc/7_7/44/bd1ec6a5d51388e10000000a155369/frameset.htm].

Best regards,

Lars

--> Just to add:

As you may know or not know, the MaxDB parameters are all defined in a textfile called cserv.pcf that can be found in <dependent_path>/db/env/.

Part of these definitions is not only the current parameter name, but also the old, now deprecated parameter name.

The following is an example for such a definition:

ID MaxSavepointTimeInterval
  TYPE int
  DEFAULT 600
  CLASS SUPPORT LOGGING
' SCOPE UNDECIDED
  MANDATORY YES
  *DEPRECATEDID _RESTART_TIME*
  CODE
    CONSTRAINT  \
               0 MaxSavepointTimeInterval <=  \
               100000 MaxSavepointTimeInterval >=  \
               AND
  ENDCODE
EXPLAIN
 Minimum number of seconds between two subsequent savepoints

 If the value of MaxSavepointTimeInterval is increased the number of savepoints
 within a unit of time and thus the system load decrease.

 Note: The time required for a restart after a system failure increases.

 Regardless of the above specified MaxSavepointTimeInterval a savepoint is written
 in the following cases:
      - COMMIT in a NOLOG session modifying data.
      - CREATE INDEX with COMMIT
      - The number of blocks released by a savepoint would be higher
        than the current number of free blocks on the data volumes

 The lower and upper limits are:
     0 <= MaxSavepointTimeInterval <= 100000

 (4 bytes integer)
ENDEXPLAIN
HELP
Minimum number of seconds between two subsequent savepoints
ENDHELP

In DEPRECATEDID you can find the old parameter name.

regards,

Lars

Edited by: Lars Breddemann on Oct 16, 2008 11:58 PM

[hannes_kuehnemund]

Hi Markus,

I'll ask my colleagues and let you know asap.

Thanks,

Hannes