Oracle 8 and earlier releases offer a DATE data type that provides date and time components but does not offer subsecond precision. To ensure compatibility with Oracle 8 and earlier releases, DataServer for Oracle by default converts the DATE data type in a result set to an OpenEdge DATE column that stores the DATE portion and an OpenEdge INTEGER column that stores the time portion of the specific Oracle DATE. However, if your application does not require Oracle DATE data type mapping to OpenEdge DATE and INTEGER columns and you have since upgraded to Oracle 9i or later, you should consider using the Data Dictionary to explicitly map the Oracle DATE data type to the new OpenEdge DATETIME data type. If your Oracle data source has limited support for time zones, you may want to consider parsing OpenEdge DATETIME columns and storing those attributes, such as precision and time zone, that may not exist in the foreign datetime description, into associated companion columns to the foreign data type. See Pre-selection criteria for the schema pull for more detail about changing the OpenEdge type mapping for Oracle DATE types.