ArcSDE won't compress now that a direct connect has been established

[KevinReeves]

We have daily scripts that run at night which compresses our database back down to state id 0.  One of our end users established a direct connect to our Oracle database yesterday through their server.  Now our SDE isn't compressing.  I noticed this morning when I tried to kill all the users, it wouldn't let me kill the DC connections.  Is there a way to still compress the database while there is a direct connect on it?  Any help would be greatly appreciated.

Kevin

[SathiaG]

Have you tried compressing the DB using Direct Connection?

[JakeSkinner]

You can only kill direct connections with the 'sdemon -o kill' command at version 10.  If you are at version 10, you will need to grant a couple other user permissions to the SDE user in order to kill direct connections:

ALTER SYSTEM
SELECT_CATALOG_ROLE

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/User_permissions_for_geodatabases_in_O...

If you are not at 10 you can still delete direct connections, but this must be done by deleting them through the 'sde.process_information' table.  I always recommend creating a database backup before editing/modifying any repository table.

[deleted-user-AYsXjhkrwuAA]

We have daily scripts that run at night which compresses our database back down to state id 0.  One of our end users established a direct connect to our Oracle database yesterday through their server.  Now our SDE isn't compressing.  I noticed this morning when I tried to kill all the users, it wouldn't let me kill the DC connections.  Is there a way to still compress the database while there is a direct connect on it?  Any help would be greatly appreciated.

Kevin

Hi Kevin

At ArcSDE 9.3 and below Direct Connections can be killed by terminating the users session on the database.  This requires the alter system privileges on your Oracle database which would only usually be available to your DBA.

Instructions on how to identify and kill direct connects can be found in KB Article 35889 - Kill Direct Connect Processes to the ArcSDE Database.

We ran into similar problems to you struggling to compress to state 0 and got round it by registering layers as versioned with the option to move edits to base. Now most edits are immediately moved into the business table when a user saves edits.

Hope this helps,

Andrew