Restrictions and limitations of semi-live reformatVOB

Understand the restrictions and limitations of the semi-live reformatVOB process.
  • The existing reformatvob restrictions still apply to the semi-live reformatVOB process. The user must be one of the following:
    • VOB owner
    • (UNIX or Linux) root
    • (Windows) Member of the HCL VersionVault group

    You can execute the reformatvob only from the VOB server.

  • Cleartool requires at least four (4) times the size of the current VOB database directory available in disk space before it allows the initiating of the semi-live reformatVOB process.
  • The initiating stage of the semi-live reformatVOB process must be run to completion without interruption. If the initialization stage is not completed successfully, the administrator has to look to manually clean up any directories that resulted from the initiating stage, and then restart the initiating stage from the beginning.
  • There might be a performance impact on the VOB server, depending on when the db_replay_server is running, and the number of operations being performed on the VOB server.
  • When the initiating stage is executing, there is no way to cancel the operation, except to either manually kill the reformatvob dump or load the process. This leaves the semi-live reformatVOB process in an inconsistent mode. To completely cancel the semi-live reformatVOB process and clear out the database, execute the following commands:
    1. mkdir <vob_stg_pname>/db.semilive
    2. cleartool reformatvob -semilive -cancel <vob_stg_pname>
    3. Remove the <vob_stg_pname>/db.copy directory, if there is one.
    4. Remove the <vob_stg_pname>/dump.inprog directory if there is one.
  • You can use the semi-live reformatVOB process to reformat VOBs only to schema 81 or higher (when available).