Increase Record ID Limit in ClearQuest 7.0 or later

Record ID Limit

From ClearQuest 7.0,  the record ID(DBID) limit from 16 million records to 100 million stateful and 2 billion stateless records.

 

Ensure to upgrade ClearQuest synchronization servers to 7.0 or above before you increase the record limit. Once you increate the record limit, the format of the oplog and the export packages will change a bit. Synchronization server from earlier versions can not work with packets with the changed format.

 

 

To check whether the user db has enabled the high record ID limit, you can use installutil getrecordlimits  on each user database or –all for all databases which are associated with a schema repository

 

How to increase the record ID limit

For nonreplicated databases, the installutil sethighrecordlimit command is run on each user database that needs the higher record limit. The command can also run on all user databases associated with a schema repository by using the –all option

 

For replicated databases, the installutil sethighrecordlimit command is used with the –for replication option. This option can be used only at the working master site and the changes will sync to other sites. To increase the record ID limit in an environment with replicated databases:

1. Stop sync jobs
2. Ship all outstanding synchronization packets
3. Import all outstanding synchronization packets
4. At the working master site, run the installutil sethighrecordlimit command with the –for replication options
5. Start sync jobs

 

For working master sites that also have non-replicated user databases, run the installutil sethighrecordlimit command on those databases individually or use the –all option. The –all option does not apply to replicated databases or affect them in any way.

 

Notice

All new schema repositories and its associated databases created in version 7.0 or later will be set to the higher record ID limit by default.

 

Databases created with version 7.0 and later in a clan use the record limit specified by the clan, which depends on whether the clan has been enabled for high record limits or not.