AutoCAD Map 3D, supports
Oracle versions 10gr2, 11g, and XE. You can create and edit an Oracle data store and schema,
and you can access existing spatial schemas in Oracle that were
created by other applications. Oracle has comprehensive support
for all the data types and operations that AutoCAD Map 3D supports,
including spatial index, long transaction, and persistent locking.
Before you add features
to an Oracle data store, make sure your user privileges for that
Oracle data store are adequate and appropriate, and that the data
in that data store is accurate and current.
You can add
a user for an Oracle data store using a utility provided
with AutoCAD Map 3D.
What Oracle Schemas Support
An Oracle schema can
support the following:
- Multiple schemas
- Object properties (with limitations)
- Association properties (with limitations)
- Schema overrides
- Auto ID generation
- Data store scope unique ID generation
- Default values
- Inclusive value range constraints
- Exclusive value range constraints
- Value constraints list
- Null value constraints
- Unique value constraints
- Composite unique value constraints
- Spatial contexts
- These geometry types: point, line string,
polygon, multi-point, multi-line string, multi-polygon, curve string,
curve polygon, multi-curve string, multi-curve polygon, linear ring,
line string segment, circular arc segment, and ring
Restrictions of Oracle
When you create an Oracle
schema, the following restrictions apply:
- A feature class must
define or inherit at least one identity property.
- You cannot add a non-nullable data property
to a class that already has data.
- Identity properties cannot be nullable.
- Read-only identity properties must be
- The length for string properties must
be between 1 byte and 4000 bytes, inclusive.
- For decimal properties, precision must
be between 1 and 38, inclusive, and scale must be between -84 and
- A feature class can have multiple geometric
properties. Although it is not mandatory, having a main geometry
as an attribute of the feature class can help you to identify which
geometry property to use as the default for queries and rendering.
Both HasMeasure and HasElevation are supported.
The Autodesk FDO Provider
for Oracle included with AutoCAD Map 3D 2010 creates tables in the FDO data store that
are not automatically version-enabled. Therefore, when you create
a new Oracle data store using the default options, the resulting
table is not version-enabled, so persistent locking and long transaction are
not supported. (This differs from previous releases.)
Oracle Workspace Manager
(OWM) is used for versioning and persistent locking support.
and persistent locking are not available with the Oracle XE version.