To work with Oracle data
Concept Procedure
 
 
 

To enable versioning for an Oracle data store

  1. You enable versioning with the Oracle SQL*Plus tool, which you use to execute the scripts. Before executing the scripts, make sure that the following conditions are true:
    • You connect directly to the Oracle user (or FDO data store) to be processed.
    • The Oracle user executing the script has sufficient privileges (has been granted the Workspace Manager role WM_ADMIN_ROLE).
    • The Oracle user executing the script is the only user processing or accessing the current Oracle user (or FDO data store) during the execution of the script. Otherwise, a script failure may result from a session conflict.
  2. To create a script log file, execute the spool <log file name>; command before invoking the scripts and the spool off; command after the invoked script finishes. The log file can help you resolve any issues encountered by the scripts.
  3. Read the documentation contained within the script files themselves to determine what privileges are required for each script, how to run the scripts, and what errors may occur.

    Problems can occur if you respond incorrectly to errors you encounter while running a script.

  4. Execute the EnableVersioning.sql script in the /FDO/bin/com folder in your AutoCAD Map 3D folder.

    This will enable the tables for OWM.

    NoteThe DisableVersioning.sql script in the same folder provides the opposite functionality.
  5. If you create a data store in AutoCAD Map 3D 2010 that you want to use with the 2007 version of AutoCAD Map 3D, you must set the value of the lock and long transaction options in the table F_Options in the generated data store to 2. You can do this with the supplied SQL script EnableVersioning.sql, which also enables versioning for all tables and allows the creation of conditional data. Do not make this change to F_Options in the database if you do not plan to use it with the previous version of AutoCAD Map 3D.

To work with Oracle data