Perforce Public Knowledge Base - p4d "-xx" checks db.integed/db.rev twice
× PRODUCTS SOLUTIONS CUSTOMERS LEARN SUPPORT
Downloads Blog Company Integrations Careers Contact Try Free
Menu Search
Perforce
Reset Search
 

 

Article

p4d "-xx" checks db.integed/db.rev twice

« Go Back

Information

 
Problem

Why is the db.integed/db.rev table checked twice during p4d "-xx" command?

Solution

The 'p4d -xx' command is used to P4D "-xx" Flag As the command runs, it prints out which table pair is being checked for consistency.

A successful output looks like this:

Check db.change/db.desc...
Check db.fix/db.job...
Check db.have/db.rev...
Check db.integed/db.rev...
Check db.integed/db.rev...
Check db.resolve/db.working...
Check db.working/db.have...
Check db.working/db.rev...
Check db.rev/db.revcx...
Check db.working/db.locks...
Check db.change/db.changex...
Check db.rev/db.revhx...
Check db.rev/db.revdx...

The db.integed/db.rev table pair appears twice. This is because this table pair check is done in two steps, one is to check the 'toFile' direction of an integration and the other is to check the 'fromFile' direction of an integration. Since these checks are done in turn, there are two entries for this table pair in the command output.

Related Links
P4D "-xx" Flag - Check and repair table inconsistencies

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255