Is This Content Helpful?
We're glad to know this article was helpful.
When registering a table as versioned, the SDE user is granted privileges on the base table and other side tables to allow the SDE user to compress the geodatabase.
However, when registering an Oracle Spatial table as versioned in ArcSDE 8.3, there are certain privileges on the spatial index table that need to be granted to the SDE user.
This was corrected in ArcSDE 9.0. It is no longer necessary to grant the SDE user privileges on the spatial index of a versioned Oracle Spatial table in ArcSDE 9.0 or greater.
Instructions provided describe how to grant all privileges to the SDE user on the spatial index table of a versioned Oracle Spatial table.
It is necessary to determine the name of the spatial index table, register the feature class as versioned, grant the necessary privileges on the spatial index table to the SDE user, and verify the privileges were granted.
The table must already be registered with the geodatabase as a feature class before it can be registered as versioned. In the steps below, the business table of the feature class is MEX_STATE_SDO.
SELECT I.TABLE_NAME, U.SDO_INDEX_NAME, U.SDO_INDEX_TABLE
FROM USER_SDO_INDEX_METADATA U,
WHERE I.INDEX_NAME = U.SDO_INDEX_NAME
AND I.TABLE_NAME(+) = 'MEX_STATE_SDO';
GRANT SELECT, INSERT, UPDATE, DELETE
ON MDRT_B18F$ TO SDE;
WHERE TABLE_NAME = 'MEX_STATE_SDO'
AND OWNER = 'SDETEST';
SELECT OWNER, TABLE_NAME, PRIVILEGE
WHERE GRANTEE = 'SDE'
AND TABLE_NAME IN('MEX_STATE_SDO','A172','D172','MDRT_B18F$')
ORDER BY TABLE_NAME, PRIVILEGE;