Repository Corruption

Question

We have a problem with our development repository, which says that it
has inconsistency ID. I have enclosed the actual forte error below.
This problem happened to us a month before and we did the following
corrective action. We created the new repository by importing all the
Forte and conductor plans. It worked and all went well until yesterday
when our backup script, which has the rpcopy and rpclean, failed. And
the old problem is back again. We could not start our repository
anymore. We tried to start by recreating the index file but it failed.
Since the regular rpclean failed we tried the -q option and tried
starting our repository. This time it worked. Even though it is up and
running now the repository looks very unstable now. It would be helpful
if someone can shed more light onto this problem. Any suggestion is far
beyond welcome. The Repository size is 450 MB now.
Forte Error
C:\forte\BackupScripts>echo on
C:\forte\BackupScripts>C:\forte\BackupScripts\RepBackUp.bat
c:\forte\BackUpRepositories wisor20Repos wisor20Repos1205
C:\forte\BackupScripts>if xc:\forte == x goto noroot
C:\forte\BackupScripts>set
sourceRepos=bt:c:\forte\repos\wisor20Repos1205
C:\forte\BackupScripts>set
destRepos=bt:c:\forte\BackUpRepositories\wisor20Repos1205
C:\forte\BackupScripts>set cmdstr=c:\forte\install\bin\rpcopy
C:\forte\BackupScripts>goto common
C:\forte\BackupScripts>rpstop -n wisor20Repos -k
rpstop Version 3.0.M.2
Windows NT
Forte Application Environment (tm), Forte Runtime Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-2000, Forte Software, Inc. and its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-2000, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws of the United
States.
Thu Mar 23 22:46:52 2000
Type Service Flags Level
err sh * 255
Memory Configuration:
Minimum Allocation: 2000.
Maximum Allocation: 64000.
DoContract Percent: 65.
Allocation Increment: 1280.
Loaded Forte Message Catalog 'fortemsg/en_us.cat'
NLM Startup is Complete - Partition's Locale is 'en_us.win'
rpstop:Repository Server wisor20Repos successfully killed.
C:\forte\BackupScripts>c:\forte\install\bin\rpcopy -s
bt:c:\forte\repos\wisor20Repos1205 -fr
bt:c:\forte\BackUpRepositories\wisor20Repos1205 -r -fm(n:4000,x:64000)
rpcopy Version 3.0.M.2
Windows NT
Forte Application Environment (tm), Forte Runtime Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-2000, Forte Software, Inc. and its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-2000, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws of the United
States.
Thu Mar 23 22:47:00 2000
Type Service Flags Level
err sh * 255
Memory Configuration:
Minimum Allocation: 4000.
Maximum Allocation: 64000.
DoContract Percent: 65.
Allocation Increment: 1280.
Loaded Forte Message Catalog 'fortemsg/en_us.cat'
NLM Startup is Complete - Partition's Locale is 'en_us.win'
rpcopy: Copying to B-tree repository
c:\forte\BackUpRepositories\wisor20Repos1205
rpcopy: Removing old target repository
c:\forte\BackUpRepositories\wisor20Repos1205.
ERROR: Exiting due to following exception:
SYSTEM ERROR: A serious error has occurred in Repository
(c:\forte\repos\wisor20Repos1205). Corrective action may be necessary.
Notify
your repository administrator.
Class: qqsp_ImplementationException
Error #: [1101, 198]
Detected at: qqrp_Repository::Fetch
Error Time: Wed Jan 03 22:02:13
Exception occurred (locally) on partition "Default LOM",
(partitionId =
9E06B050-B4CA-11D4-B5A6-82D3EA47AA77:0x2065, taskId =
[9E06B050-B4CA-11D4-B5A6-82D3EA47AA77:0x2065.1]) in application
"rpcopy",
pid 414 on node LEOPARD in environment centrale.
SYSTEM ERROR: Internal consistency error. InstanceId (64,0,8500514)
found
in record header did not match expected InstanceId (64,0,111906).
Class: qqsp_ImplementationException
Error #: [1106, 636]
Detected at: qqbt_BtreeAccess::GetPhysicalRecordSize
Error Time: Wed Jan 03 22:02:13
Exception occurred (locally) on partition "Default LOM",
(partitionId
= 9E06B050-B4CA-11D4-B5A6-82D3EA47AA77:0x2065, taskId =
[9E06B050-B4CA-11D4-B5A6-82D3EA47AA77:0x2065.1]) in
application
"rpcopy", pid 414 on node LEOPARD in environment centrale.

Answer 1

I've had a similiar problem on a project I was working on.
We had a real load of old and unused variables in Interconnect so that we decided to clean up the repository using iStudio. During that process we ran into the weird thing that some object could be removed even though we KNEW they were in use and vice versa.
This specific problem could be traced back to the usecount column in the interconnect repository. The usecount column was sometimes not updated properly.