Setting up multiple geodatabases in one PostgreSQL database cluster on Linux

You can have more than one database in a PostgreSQL database cluster. Therefore, you can have more than one geodatabase in a PostgreSQL database cluster—one geodatabase per database.

The steps to create the second geodatabase are the same as for the first. Just be sure that, if you are using an ArcSDE service for connections, you create a unique service for the second geodatabase.

Steps:

1. Create an additional database on the PostgreSQL database cluster.
   Tip:

   If storing PostGIS data in the second database, be sure to create the database from your PostGIS template.

2. Create a schema named sde in the new database.
3. Grant USAGE permissions to the Public role on the sde schema in the new database.
4. Add a new ArcSDE service name, port number, and network protocol to the services.sde file in your SDEHOME/etc directory and Linux services file (if you will be using an ArcSDE service for connections).
5. If you plan to set variables in the dbinit.sde file to connect to the second geodatabase, make a copy of your dbinit.sde file, giving it a new name. This name must include the name of the new ArcSDE service. For example, if the new service name is sdepgsql2, name the dbinit file dbinit_sdepgsql2.sde.
6. Set the appropriate variables in the new dbinit file.
7. If you will be using different configuration parameters in your second geodatabase, make a backup copy of your existing giomgr.defs and dbtune.sde files in your SDEHOME/etc directory, then alter the giomgr.defs and dbtune.sde files to contain the parameters and values you desire for the new geodatabase.
8. Run the sdesetup command with the install operation to create the geodatabase repository in your second database and authorize it with the ArcGIS Server Enterprise license.

   sdesetup –o install –d POSTGRESQL –D <name_of_second_database> 
   –u sde –p <sde_user_password> –l <license_key>

9. If using one, start the second ArcSDE service with the sdemon command.

   sdemon –o start –i <service_name> 
   –s <server_name> –p <sde_user_password>

10. Create schemas in the new database for users who will own data.
11. Grant appropriate permissions on the schemas to other users in the database.