Upgrade Counters

SUMMARY

Beginning with server version 2001.1, the Perforce Server determines during startup if your Perforce database requires an upgrade by using an Upgrade Counter. A Perforce database upgrade is required whenever running a newer Perforce Server executable against a database created with an earlier version of the Perforce Server.

DETAILS

The upgrade counter is created when upgrading a server database created with a 2000.2 or earlier server.

A database upgrade occurs automatically when launching a Perforce Server using a database with fewer than 1000 changelists. Otherwise, a Perforce database upgrade requires running the "p4d -xu" command.

You can see the current value for the upgrade counter by entering:

p4 counter upgrade

or, simply

p4 counters

The following table displays the Perforce upgrade counter value and the associated server database change(s) for each Perforce Server release since 2001.1.

   Upgrade      Database Changes Made
   ---------------------------------------------------------------------- 
     18         2007.3: removing old db.archive.
     17         2007.3: (re)building db.archmap (lazy-copy map) table.
     16         2007.3: (re)building haveMap from db.have/db.working.
     15         2006.2: removing old db.archive.
     14         2006.2: building db.archmap (lazy-copy map) table.
     13         2005.2: moving spec depot entries into db.revsx.
     12         2005.2: building haveMap from db.have/db.working.
     11         2005.2: building db.revdx (delrev) table.
     10         2005.1: building lazy-copy index.
      9         2005.1: upgrading db.locks table.
      8         2005.1: building db.revhx (headrev) table.
      7         2003.2: upgrading db.user.
      6         2003.1: initialize default depot.
      5         2002.2: upgrading tempobj filetype in db.working.
      4         2002.2: upgrading tempobj filetype in db.rev.
      3         2002.1: splitting pending db.change into db.changex.
      2         2001.1: splitting db.have into db.have and db.label.
      1         2001.1: splitting db.integ into db.integed and db.resolve.