#WORKSPACE MANAGER ORACLE HOW TO#

SQL> select app_no from test_sdo where objectid=21569

Save the edits and select Editor > Stop Editing.

From ArcMap, open the attribute table, and update one attribute column, for example, update column 'APP_NO' to set the value as '123' for one particular feature (objectid=21569).

Switch to the workspace in the Execute SQL window.īegin dbms_wm.gotoWorkspace('LOGON_TEST') end.Under Editor > Options, uncheck the option to edit a version of the database with the ability to undo and redo, so that edits are directly written against the base table, and start editing.Open up a direct connection/3-tier connection in ArcMap and add the TEST_SDO layer.The default workspace for a session context is called LIVE. SQL> EXEC dbms_wm.createWorkspace('LOGON_TEST') Note:Īn Oracle Workspace is like a version in a geodatabase. Using SQL*Plus, create a testing workspace.SQL> EXEC dbms_wm.EnableVersioning(table_name => 'TEST_SDO', hist => 'VIEW_WO_OVERWRITE') Using SQL*Plus, enable versioning on a table that maintains history:.Even with ArcMap, a third-party add-on DLL is needed to execute SQL directly from ArcMap so that workspaces can be switched within an ArcMap session.īoth ArcMap and Oracle SQL*Plus are used in following workflow. There are still some limitations to working with Oracle Workspace Manager on geodatabase feature classes, such as the inability to preview the data changes from ArcCatalog.

#WORKSPACE MANAGER ORACLE HOW TO#

The purpose of this article is to demonstrate working with Oracle versioning, but not using Enterprise geodatabase versioning, and how to edit and check data changes from ArcGIS Desktop (ArcMap). Instructions provided in this article describe a general workflow for working with Oracle versioning.

Workspace manager oracle