Hi there,
Got an enormous problem. Don’t know if anybody has experienced it.
Upgraded an R5 to R6 server following the redbook. Did the compact -RX on all DBs as recommended.
Then realised later that -RX doesn’t convert to ODS 43, so did a compact on one large database. After the -RX, the DB had grown to 11gig. Ran a standard compact, and after 11 hours (yes!!) it is now back at 6.5gig, which is near to what it was under R5 the previous day.
So my problem? An enormous number of documents are not showing in views or available from documents (which use a simple Open document based on replica id response stuff, worked under R5). The docs, to all intents and purposes have vanished - even though the doc count is still correct.
Any ideas? I guess it’s indexes, and things, but I am stumped.
THIS IS MEGA-URGENT. THE WINNER GETS A CADBURY’S CREAM EGG POSTED TO THEM ANYWHERE IN THE WORLD!
Mark Haller
LogicSpot
UK
Subject: First off there is no “X” argument to compact. Try updall -r to rebuild all the view indicies.
Subject: RE: First off there is no “X” argument to compact. Try updall -r to rebuild all the view indicies.
Hello
after running compact (-c), you just run updall -RX to force a rebuild of all view indexes -R and FTindexes -X if your use them.
Furthermore as you have a large database, i would suggest to do that off-line (while your domino server is not running)
in addition to check if you view indexes are present , you can use your Domino administrator client open server select file tab , browse to your database in and right click on it to display sub menu and select “manage view” , you will see all view indexes & size contained in your database
JNK
Subject: RE: First off there is no “X” argument to compact. Try updall -r to rebuild all the view indicies.
Hi there,
I am quite sure I issued the updall and the compact commands correctly - just my posting was incorrect.
What I did find, however, and have now been working 48 hours solid, is that about 200,000 documents have gone AWOL.
So I have done a copy back in of a DB from the day before - but guess what, consistency check has been running for 11 hours and still not finished. Setting my alarm to wake me every 50 minutes is not nice 
Warning to anyone doing a server upgrade to R6 - patience is the virtue. Copy and copy again before doing the upgrade, and backup all over the place. Do not do the ODS conversion until you are sure you have plenty of spare time if it is a large datbase (ours it 1.5mill docs and 5.5gig)
Why Lotus cannot put in place a % complete option for the fixup, updall and compact options, I have no idea.
Tim for another pot of coffee, mefinks. thanks for the replies so far.
Mark Haller
LogicSpot
UK
Subject: RE: First off there is no “X” argument to compact. Try updall -r to rebuild all the view indicies.
Hi Mark,
Sorry that you’re having the issues.
In helping our clients perform their upgrades, I’ve seen on 3 different
occasions where rebuilding the view didn’t work…
UNTIL we ‘cut’ the b>]design/b>] of the misbehaving view out of the
database and then pasted it right back in. Don’t know how… don’t know why
… perhaps it’s something related to view index data being removed by the
‘cut’ operation as opposed to doing a rebuild on already corrupted data…
whatevah…
Also, one of my developers has reported that he had several instances where he
had to recreate the key column from a view in order to get it recognize the
(formerly) “missing” documents.
Hope one (or both!) of these help out.
Richard Echeandia
Cool Notes Stuff, Inc.
Save time & money on your Notes 6 upgrade with Migration Pro for 6.
http://www.CoolNotesStuff.com
Subject: RE: First off there is no “X” argument to compact. Try updall -r to rebuild all the view indicies.
Hi there,
Many thanks for your response, really appreciate it 
I truly do - I’ve been working non-stop on this since Sunday night. When I say non-stop, I mean non-stop!! Not slept for an age now, client still managing to smile, just … it’s horrendous
Well, I had tried earlier today to remove a view which only showed a portion of the documents and then paste the view in from the design template, and build the view again, but to no avail.
The doc count matches that before the COMPACT (to ODS43) so nothing has gone out of the DB.
I look in the view and top level docs are there - it’s random responses, and their responses which have gone.
So I tried a test - I wrote some v.simple LS to get a document I had in a very small replica of the DB from a while ago, which no longer shows in the dodgy database - and guess what, I can get the doc by NOTEID but not get it by UNID.
So it looks like the internal UNIDs for many of the docs has just gone AWOL.
So I’m left with a DB that I can try and FIXUP but have to wait about 18 hours for it to run (horrendous, no & bar, no nothing, maybe it might work stuff), or I am currently fixing up a restored DB and I write some script to find matching docs, pull them in, then .Makeresponse on them as required - which I am plumping for, as the restored DB has been consistency checking since 10AM this morning (now 9:30PM).
this is all so naff. been with notes since V2 and this is one of my worst days ever.
Mark
LogicSpot
UK
Subject: RE: First off there is no “X” argument to compact. Try updall -r to rebuild all the view indicies.
Have you tried doing a b>]non-/b>]replica copy of the database(s) and then
working with that replica?
I’ve seen some databases where the corruption could only be corrected by
breaking the replica ID of the db (doing that also re-creates all of the note
UNIDs).
My guess is you probably can’t do that anymore 'cuz it sounds like you’re
storing the UNID and using it to do the lookup.
Sorry you’re having to live through such a bollocks (did I spell that right?).
Richard Echeandia
Subject: RE: First off there is no “X” argument to compact. Try updall -r to rebuild all the view indicies.
Hi Richard,
Spelling was perfect. The kids on the street often spell it “bollox” now, just for a quick lesson in modern street-language jokes
Can I ask - how do I do a non-replica copy of a database? I could write a looped bit of script to get all docs … but the docs are not seen by the script?
Many thanks for your continued responses. Just starting a restored backup now.
Hey, an aside for anyone - why does fixup/consistency check run on a DB that has been copied by DOS when nothing has changed in the DB? Spoke to one of our admin guys and he reckons it’s because I copied it when the Domino server was up, and it had locks on it. If I copied with the server down, it would’ve just opened straight away. Do u agree?
Getting my smile back as I can see a way forward, allbeit a slow one! I’ve been elected R6 upgrade expert in the company now and have to do all future upgrades here.
Mark Haller
LogicSpot
UK
Subject: RE: First off there is no “X” argument to compact. Try updall -r to rebuild all the view indicies.
Well, I’m not sure if anyone is following this thread, but if they are -
The problem is now solved.
And what was it? A SEVERE FAULT WITH LOTUS DOMINO.
I had a copy of the .NSF and placed it on a workstation, with R5 client only on it. I then opened the database locally and it carried out a consistency check overnight. I opened the database next morning - 1.6mill docs all there, and beautiful to my eyes.
I had a copy (same file) on the R6 server, under the \data directory and tried to open it with an R6 client. A consistency check was also carried out - and guess what?
No failures, no nothing, no errors, opened the database AND IT HAD 300,000+ less documents in it. Gone. That’s DB info doc count. Sure enough, not in the views.
So - anyone got any comments? Cos I’m happy as it’s Red Nose/Comic Relief Day here and people are dressed in the strangest outfits, it’s sunny and I’m out on the beers tonight, but I’m highly dissapointed in this product.
As usual, any feedback most welcome
Mark
LogicSpot
UK