Determines whether the driver creates the internal files required for a relational map of the native data model when establishing a connection.
Valid Values
0 | 1 | 2 | 3
Behavior
If set to 0 (NotExist), the driver uses the current group of internal files specified by the Schema Map (SchemaMap) option. If the files do not exist, the driver creates them.
If set to 1 (ForceNew), the driver deletes the group of internal files specified by the Schema Map option and creates a new group of these files at the same location.
Warning:1 (ForceNew) causes all views, data caches, and map customizations defined in the current schema map to be lost.
If set to 2 (No), the driver uses the current group of internal files specified by the Schema Map option. If the files do not exist, the connection fails.
If set to 3 (Session), the driver uses memory to store the internal configuration information and relational map of the native data model. After the session, the view is discarded.
Notes
The internal files share the same directory as the schema map configuration file. This directory is specified with the Schema Map connection option.
You can refresh the internal files related to an existing relational view of your data with the SQL extension Refresh Map. Refresh Map runs a discovery against your native data and updates your internal files accordingly.
The internal files share the same directory as the schema map configuration file. This directory is specified with the Schema Map connection option.