Creating a geodatabase in a user's schema in Oracle
You create user geodatabases by running the sdesetup command with the install operation. You must include the –i option and specify the port number and schema name. The user name and password must be those of the user in whose schema the geodatabase is to be installed.
It is recommended that you store the system tables that get created in the user's schema with the sdesetup –o install command in a different tablespace than the one used for your sde master geodatabase. This helps avoid I/O contention and allows you to back up the tablespace separately if needed. To create the system tables of the user-schema geodatabase in a different tablespace, make a copy of your dbtune.sde file and edit the parameters under the DATA_DICTIONARY keyword in the dbtune file to point them to a different tablespace. Do this prior to running the sdesetup command to create the geodatabase in a user's schema.
Note:If the tablespace for the user-schema geodatabase is the default schema of the user, and if you left the tablespace values for the DATA_DICTIONARY parameters commented out (in other words, you had not specified tablespaces for the SDE master geodatabase), you do not have to alter the parameters of the DATA_DICTIONARY keyword to point to the new schema.
- Grant the proper permissions to the user to allow him or her to create a geodatabase.
-
As the schema owner, run the sdesetup command.
sdesetup –o install –d ORACLE11G –i 5151:Thor –u Thor –p rot –l licensefile.ecp
Caution:Be sure you specify the schema name with the –i option. If it is not specified, and only a port number is provided, the sde schema is used by default. Since the geodatabase in the sde schema already exists, this fails.
Even if you are using a direct connection to the master sde geodatabase, you must add an ArcSDE service port number to the operating system services file on the server. You don't have to start a service, this entry just needs to be in the operating system services file.