[p4] Problem recovering from database and versioned files

[Thierry Lam]

That's right, I was using the wrong p4d, thanks for the help.

Thierry

-----Original Message-----
From: steve at vance.com [mailto:steve at vance.com]
Sent: Monday, November 19, 2007 6:52 PM
To: Thierry Lam; perforce-user at perforce.com
Subject: RE: [p4] Problem recovering from database and versioned files

First of all, you should at least include Perforce Support on this kind of
issue. It's deeper magic than most users get into, and it's some pretty
technical stuff that they have all the right tools for if anyone does.

That said, it looks like your error is from replaying a newer journal into
an older server. First of all, I would guess that this is the first db.have
entry in this checkpoint. If it's not, then something is really wrong.

Assuming it is, this is telling you that the p4d executable you are using
does not recognize db.have version 2, which means it's a 2005.2 or earlier
server and the checkpoint was made with a 2006.1 or later server.

Make sure you have your server version correct for your restore and try it
again.

Steve

Original Message:
-----------------
From: Thierry Lam Thierry.Lam at autodesk.com
Date:   Mon, 19 Nov 2007 15:06:20 -0800
To: perforce-user at perforce.com
Subject: [p4] Problem recovering from database and versioned files


I'm following the Perforce System Administrator's Guide from
http://www.perforce.com/perforce/technical.html and I'm currently on page
35(of the pdf) where it talks about "Both database and versioned files lost
or damaged".  I have the latest checkpoint file(let's call it
myserver.ckp.123) as well as the versioned files. However, when I try
running the following commands(P4ROOT already defined in my environment):

                p4d -r $P4ROOT -jr /home/perforce/myserver.ckp.123

I get the following error:

Recovering from /home/perforce/myserver.ckp.123...
Perforce server error:
        Journal file '/home/perforce/myserver.ckp.123' replay failed at
line 356!
        Record version not known in journal record!


Line 356 looks like the following:

@pv@ 2 @db.have@ @//MAINSERVER/branch/World/Hello.xml@
@//depot/branch/World/Hello.xml@ 1 0


MAINSERVER is defined earlier as the following:

@pv@ 1 @db.view@ @MAINSERVER@ 0 0 @//MAINSERVER/...@ @//depot/...@

Any idea what's wrong?

Thierry
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user


--------------------------------------------------------------------
mail2web LIVE - Free email based on Microsoft(r) Exchange technology -
http://link.mail2web.com/LIVE