fighting for truth, justice, and a kick-butt lotus notes experience.

Traveler Scheduled Defragmentation using the DBMAINT Command

 26 Januar 2016 16:03:59
IBM introduced with IBM Notes Traveler 9.0.1.8 a new tool to get better control of the defragmentation of the used relational state database (Derby in Standalone / DB2 or MS SQL in HA).
Before 9.0.1.8 the periodic defragmentation could be configured by using the notes.ini setting NTS_DEFRAG_INTERVAL_DAYS. This INI-setting is no longer used by Traveler and 9.0.1.9 will show you a warning:

Image:Traveler Scheduled Defragmentation using the DBMAINT Command

Since 9.0.1.8 you need to configure scheduled defragmentation by using the new DBMAINT-Command:

To check the current config and status:

tell traveler dbmaint show


To enable periodic defragmentation you will have to enable and configure it using this commands:

tell traveler dbmaint set interval 30
tell traveler dbmaint set auto on


From the Traveler documentation:

Running defragmentation on a scheduled basis (9.0.1.8 and later)


To perform defragmentation on a scheduled basis, perform the following procedure:
  1        Use the tell command DBMaint set interval in order to set the interval to a number greater than 0. For example, to set an interval of 30 days, enter into the console:tell traveler dbmaint set interval 30
  2        Use the tell command DBMaint set auto on to turn on automatic defragmentation.
  3        To force a defragmentation, enter the command tell traveler dbmaint run. This sets NTS_DEFRAG_ONCE to 1 and the Derby database will be defragmented the next time the IBM Traveler server restarts.

Running defragmentation on a scheduled basis (8.5.3.1 to 9.0.1.7)

To run defragmentation on a scheduled basis with IBM Traveler server 8.5.3.1 to 9.0.1.7, perform the following procedure:
  1        Add NTS_DEFRAG_INTERVAL_DAYS to the notes.ini file. For example, to set an interval of 30 days add: NTS_DEFRAG_INTERVAL_DAYS=30
  2        Restart the IBM Traveler server. From that point on, if the IBM Traveler server is restarted and it has been 30 days since the last defragmentation, then the defrag operation will run.
  3        To force a defragmentation, simply delete the parameter NTS_LAST_DEFRAG from the notes.ini file and restart the server.

If NTS_DEFRAG_INTERVAL_DAYS is set and there is no last defragmentation timestamp, then the server will perform a defragmentation and reset the NTS_LAST_DEFRAG timestamp.

DBMaint Run Immediately performs online maintenance. If the server is standalone, then it will configure maintenance to run on restart.
DBMaint Show Displays various database maintenance scheduling information.
DBMaint Fragmentation Recommends database maintenance based on fragmentation levels.
DBMaint Set Interval days Sets the interval of days in which automatic database maintenance will perform.
DBMaint Set Time hh:mm Sets the time in 24-hour format in which automatic database maintenance will perform.
DBMaint Set Day monday-sunday/off Sets the day of the week on which the first scheduled automatic maintenance will start. Set this to Off if you want the first scheduled maintenance to be based off of the last maintenance time.
DBMaint Set Threshold on/off Configures automatic database maintenance to check fragmentation levels before execution.
DBMaint Set Auto on/off Enables automatic database maintenance. Re-enablement will reschedule maintenance if either the time or interval have changed.
DBMaint Set Indexes number Configures the number of fragmented indexes for the fragmentation threshold.
DBMaint Set Ownership Configures ownership of database maintenance to the executing server. This server will be the only server that can perform automatic database maintenance.
DBMaint Set Percent 0-100 Only applicable for SQL Server. Configures the fragmentation percentage of indexes for the fragmentation threshold.
DBMaint Set Functions 1-4 Only applicable for DB2. Configures the number of functions that are used to determine if an index is fragmented for the fragmentation threshold.





Kommentare
noch keine Kommentare vorhanden
  •  
  • Hinweis zum Datenschutz und Datennutzung:
    Bitte lesen Sie unseren Hinweis zum Datenschutz bevor Sie hier einen Kommentar erstellen.
    Zur Erstellung eines Kommentar werden folgende Daten benötigt:
    - Name
    - Mailadresse
    Der Name kann auch ein Nickname/Pseudonym sein und wird hier auf diesem Blog zu Ihrem Kommentar angezeigt. Die Email-Adresse dient im Fall einer inhaltlichen Unklarheit Ihres Kommentars für persönliche Rückfragen durch mich, Detlev Pöttgen.
    Sowohl Ihr Name als auch Ihre Mailadresse werden nicht für andere Zwecke (Stichwort: Werbung) verwendet und auch nicht an Dritte übermittelt.
    Ihr Kommentar inkl. Ihrer übermittelten Kontaktdaten kann jederzeit auf Ihren Wunsch hin wieder gelöscht werden. Senden Sie in diesem Fall bitte eine Mail an blog(a)poettgen(punkt)eu

  • Note on data protection and data usage:
    Please read our Notes on Data Protection before posting a comment here.
    The following data is required to create a comment:
    - Name
    - Mail address
    The name can also be a nickname/pseudonym and will be displayed here on this blog with your comment. The email address will be used for personal questions by me, Detlev Pöttgen, in the event that the content of your comment is unclear.
    Neither your name nor your e-mail address will be used for any other purposes (like advertising) and will not be passed on to third parties.
    Your comment including your transmitted contact data can be deleted at any time on your request. In this case please send an email to blog(a)poettgen(dot)eu

Archive