SQL*Net communities, domains, etc.

I'm trying to set up a tiny SQL*Net 2.x network that will (hopefully) evolve into a large SQL*Net network. I am trying to do things the Right Way, but I find the Oracle-supplied examples in the understanding SQL*Net manual a little lacking. The examples are designed to show tactical stuff for small networks, but I am interested in strategic stuff for large networks.

For example, how do I want to set up my domains? Do I want them to map to sites or protocols? Do I need separate communities for each site, even though everyone is using TCP? What is a "remote" database, anyway? I can see all the database machines as notes on my WAN, does that mean that I have no "remote" database?

Any and all thoughts and suggestions appreciated...

-darin! Received on Sun Apr 14 1996 - 00:00:00 CEST