Increasing the user database record ID limit

You can increase the record ID limit in databases created by HCL Compass after the administrative hosts and the MultiSite synchronization servers are upgraded.

About this task

For nonreplicated databases, run the installutil sethighrecordlimit subcommand on each user database for which you want to increase the record limit. You can also run the subcommand on all user databases associated with a schema repository by using the -all option. This subcommand can be run on a database more than once, so you can use the -all option even if you have already run the subcommand on some of the databases in the schema repository.

For replicated databases, run the installutil sethighrecordlimit subcommand with the -for replication option. This option can be used only at the working master site and applies to the entire clan. Other sites learn about the subcommand through synchronization. You must have upgraded all MultiSite synchronization servers to version 7.1.x or later before running this subcommand. See Import all MultiSite packets and Restart MultiSite synchronization and Shipping Servers.

To increase the record ID limit in an environment with replicated databases:
  1. Shut down all export operations on synchronization servers.
  2. Ship all outstanding synchronization packets.
  3. Import all outstanding synchronization packets.
  4. At the working master site, run the installutil sethighrecordlimit subcommand with the -for_replication option.
  5. Restart export operations on the synchronization servers.

For working master sites that also have nonreplicated user databases, run the installutil sethighrecordlimit subcommand on the nonreplicated databases individually. The -all option does not apply to or affect replicated databases.

To verify that the installutil sethighrecordlimit subcommand has been run, run the installutil getrecordlimits subcommand on the database.