Latest Contributions by JonDeRose

Ligia: Registration of a table as versioned requires an exclusive lock.  From your post it would appear as though there are other user's currently connected that are accessing feature classes within the Feature Dataset which puts shared locks on the data and prevents the creation of an exclusive lock. You did not post your configuration so I am not sure if you have access to sde command line to check current connections; however, this may also be done by looking at the 'dbo.sde_process_information' table to identify the user connecting (owner) and the machine from which the connection was issued (nodename). Additionally, if you have the the 'registration_id' for the tables contained within the feature dataset (dbo.sde_table_registry)you can see if any table_locks exist that could be preventing the registration from within (dbo.sde_table_locks).  The 'sde_id' for the session and the registration_id corresponding to the table in 'table_locks' will enable you to determine which sessions are connecting to the tables in the Feature Dataset through comparison with the 'process_information' table's 'sde_id' [ATTACH=CONFIG]14071[/ATTACH] FAQ:  How are the various lock mechanisms implemented in ArcSDE and the geodatabase? ... View more

anncrystal - OK, so i tested my earlier suggestion including the topology and also see the same issues.  While that should work in theory you have to get tricky with how you copy data around.  Without the topology this does work. An easier option which I have also tested that DOES work is as follows: 1) Create a one-way replica using the SIMPLE model with all defaults.  This  will exclude the Topology. 2) On the child geodatabase drag the feature classes outside of the Feature Dataset 3) Delete the Feature Dataset.  You will get warnings stating that this Feature Dataset belongs to a replica...continue with deletion. As this is a one way replica there should be no issues yet please note that this is not a usual or documented workflow so please test this extensively before putting something like this into Production.  - Jon ... View more

Bharathi, Using the default of shared logfiles in Oracle you should see the SDE_LOGFILES and SDE_LOGFILE_DATA tables within each schema that will perform selections et al following the creation of a selection set >100. The choice of which log file type to use is dependent upon various factors yet for most configurations within Oracle shared will suffice. ArcSDE log file tables in a geodatabase in Oracle From a review of your sdeconfig.txt file it appears as though your config file is set to use both shared, session, and standalone log files to some extent.  It could be that due to the settings within this table your instance is trying to use standalone log files which require more elevated permissions than the other types. In what order do ArcSDE log file types get used? The following settings are needed in the SERVER_CONFIG table to create shared log file tables: MAXSTANDALONELOGS = 0 ALLOWSESSIONLOGFILE = FALSE LOGFILEPOOLSIZE = 0 Granting the following permissions to the user schema in question should enable the logfile tables to be created: CREATE SESSION CREATE TABLE CREATE SEQUENCE After the log file tables are created within the user's schema the CREATE TABLE permissions can be revoked. - Jon ... View more