I recreated all the db Catalogs on 8 of our servers by deleting them and letting the task run at 1am. I could’ve sworn they all had separate replica IDs as they were not stacking. Each catalog.nsf had info about the DBs only on the server on which it was created.
The next day, I noticed they were all stacked in my workspace and now all have the same replica ID. Does this mean they’re replicating between servers? Is this correct? I thought you didn’t want catalog.nsf to replicate, or is what you don’t want to do is create one catalog.nsf on one server and THEN create replicas on other servers?
Subject: RE: This is correct, the catalog task sets the replica id.
Hi,
Thanks for the info. After I let all 8 servers recreate their own catalog database from scratch, I set one server for the domain catalog the following evening. That is why they are now stacked and have the same replica ID.
Now, since I did set a domain catalog, there shouldn’t be a problem with them replicating, will there?
Also, I hope this makes sense:
Through the desginer client, you can modify the View → By ACL view in the catalog database to show all databases, even if they don’t have the “List in DB Catalog” option selected. You can do this by removing the “&(!ListInDBCatalog=0)” option, and then you will see all DBs.
If I want to do this with the domain catalog to see ALL databases on all servers, do I need to set this option per catalog database, or just set it on the Domain Catalog DB?