replicas without versions.

[David_JAnderson]

While doing some SDE maintenance I noticed that I had 7 versions listed in the versions table, while there are 19 records in the gdb_replicas table.  I thought that each replica had to have a least one entry in the versions table.  The naming protocol indicates that these were replicas created as checkouts.  This is the opposite of this problem:

http://support.esri.com/en/knowledgebase/techarticles/detail/37551

I am wondering if I can delete the records in the gdb_replicas table without corrupting the data?

[BenLin]

Hi David,

As you suspected, this might corrupt your replica/data.

Please do NOT delete any records from the SDE system tables, like the gdb_replicas, and sde_versions tables. I would suggest you contact with ESRI Technical Support geodata team @ 888-377-4575 for further investigation on this issue. You may need to prepare a full database backup for examination.

Good luck,
-Ben

[AbhijitMane]

When you synchronize changes from a checkout replica, the "checkout" replica in the parent SDE gdb  should automatically get  unregistered from the replica list i.e. 'replica manager' in  ArcCatalog and hence from the gdb_replicas table.  The entry however exists in the versions table. Hence, you are correct when you say that the replica entry from the replicas table should have the corresponding replica system versions in the versions table.

As suggested, its not a good idea to modify the system tables directly in the database. If the checkout replicas are synchronized, the replica should automatically get unregistered from the replica list in both the parent and child gdb. You can check the same in ArcCatalog in the "Replica Manager" Window (Right click on the sde connection in ArcCatalog --> Distributed geodatabase --> Manage replicas).

If you no longer need the replica and know if they are synch, you can unregister the replica from the replica manager by right clicking on the replica --> unregister. This should automatically delete the entry from the replicas table in the database.

Hope this helps.

Abhijit