Regenerate database keys

In this example we regenerate the keys to the contacts table. Regenerating keys for other tables works the same way.

Applies to User Roles:

System Administrator

To regenerate database keys:

  1. Click Tailoring > Database Manager.
  2. Select Administration mode.
  3. In the Form field, type contacts, and then click Search.
  4. Select the form.
  5. Open the More Actions menu and choose Regen.

    The Confirm Action window opens.

  6. From the prompt, do one of the following:
    • Click OK to continue with the file/key regen.
    • Click Cancel to exit this screen without doing a regen.
    • Click Schedule to schedule a time to run the file regen operation, either once or repeatedly at a set interval.
  7. If you decide to schedule a time to run the file regen operation, do the following:
    • Provide a date in a DD/MM/YYYY format in the Date/Time to run field.
    • Provide a time in an HH:MM:SS format in the Date/Time to run field.
    • Select a Repeat Interval option if the database needs to be regenerated on a regular basis. This setting is optional. The interval period starts from the time and date set in steps 2 and 3.
      • Monthly – regenerate once a month.
      • Quarterly – regenerate every three months.
      • Semi-annually – regenerate every six months.
      • Annually – regenerate once a year.
      • Other – regenerate in the specified number of days, at the specified time.

        Use the dd hh:mm:ss format, where dd is the number of days from the initial date and time, and hh:mm:ss is the time of day at which the regen is run. For example, 26 10:00:00 sets the regen to run at 10 a.m., 26 days from the initial regeneration set in the Date/Time to run field.
    • Click Schedule to confirm this file/key regeneration action.

Note When you run an IR Regen, Service Manager needs to clear the current indexes. This causes a delete to the backend database. When Service Manager attempts to delete a large set of records, the database could run out of space for this activity and cause an error. Each supported database platform provides some type of transaction or undo log to back up data changes and allow a rollback in case of errors. If you encounter such an error, please contact your database administrator and ask them to increase the size available for this purpose.

Some examples of the errors you could encounter are:

Oracle:SQL code=30036 message=ORA-30036: unable to extend segment by % in undo tablespace

SQL Server SQL State: 42000-9002 Message: [Microsoft][SQL Native Client][SQL Server]The transaction log for database '%' is full

DB2 SQL State: 57011--964 Message: [IBM][CLI Driver][DB2/NT] SQL0964C The transaction log for the database is full. SQLSTATE=57011

Related topics

Regenerating database keys
Resetting a database table
Regenerating database keys

Regenerate IR keys
Regen a database dictionary
Open a record using Database Manager
Reset a database table from Database Manager
Schedule a regeneration
Schedule a reset