2011

Table Of Contents

■ Create versions of your data. Versioning (page 2078) creates a copy of the

data in the data source. Your changes are made to the new version of the

data. Versioning is useful for proposed changes or changes that need

approval. When the changes are final, you can make your version the

current one.

■ Use a data source set up for AutoCAD Map 3D. If your data source schema

is not set up to work with AutoCAD Map 3D, AutoCAD Map 3D creates a

custom mapping so you can use the data in your map.

■ View and edit the schema definition.

■ Create an Oracle data source.

■ Move SHP data into Oracle to take advantage of better data sharing.

■ Bring in a static copy of Oracle data as drawing objects.

■ Customize the Oracle

FDO provider (page 2063).

NOTE Functionality for OSE (the Oracle Spatial OO40, which is similar to OLE DB)

is not available in a 64-bit environment. The Oracle library that OSE is built on

(Oracle Object for OLE) is 32-bit only. There is no 64-bit version.

In the 2008 release of AutoCAD Map 3D, a new column called geometrytype

was added to the table named F_AttributeDefinition. To use AutoCAD Map

3D 2011 to access FDO data stores that were created in AutoCAD Map 3D

2007 and earlier, you must first connect to the data store containing this table

and run a SQL script. Instructions for this are on the Procedure tab of this

topic. To do this, you must have the privileges required to execute the ALTER

TABLE request. In the command line, enter the following:

sqlplus <datastorename>/<yourpassword>@<tnsServiceName>

@<MapInstallDir>/Fdo/bin/com/AlterSchemaOracle.sql; exit;

NOTE For information on customizing this provider, refer to the FDO API Reference

and the FDO Provider for Oracle API Reference. The API has custom commands for

gathering information about a provider, transmitting client services exceptions,

getting lists of accessible data stores, creating connection objects, and creating

and dropping spatial indexes.