Creating the geodatabase product library users and connections in Oracle

Available with Production Mapping license.

Creating the geodatabase user

The prodlib user created previously is a data owner. Anybody connecting as prodlib can delete the product library tables or make any schema changes. To protect the product library repository, an editor user can be created to access the product library. The editor user will not be able to create a new class in the product library, which only the data owner prodlib can do, but all the other functionality is available.

The example below shows how to create a geodatabase user in Oracle to access the product library.

Note:

Copying and pasting the examples may cause syntax errors.

Create user

CREATE USER PRODLIBUSER PROFILE "DEFAULT" 
	IDENTIFIED BY mapeditor 
	DEFAULT TABLESPACE "USERS" 
	TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK;

Grant privileges

GRANT "CONNECT" TO "PRODLIBUSER";
GRANT CREATE TABLE TO "PRODLIBUSER";
GRANT "CKB_USERS" TO "PRODLIBUSER";

Grant QUOTA on log file tablespaces

ALTER USER PRODLIBUSER QUOTA UNLIMITED ON "GDBLOGFILE";
ALTER USER PRODLIBUSER QUOTA UNLIMITED ON "GDBLOGFILEIDX";

Creating database connections for product library users

Database connections need to be created for the other product library users. Create a database connection in ArcCatalog with the PRODLIBUSER user; this will be the product library geodatabase connection.

For more information, see Database connections in ArcGIS for Desktop.

Note:

You can create a login for each user in the product library database and, if using database authentication, type the user name of the product library user for whom you want to create a database connection.