Please rate your experience Yes No. Any additional feedback? Important This feature will be removed in a future version of Windows. Submit and view feedback for This product This page. View all page feedback. In this article. IA64, and ZLinux. Oracle Database Server The following table summarizes the Windows operating system versions on which ODBC driver was certified. See Software Required. See the information about configuring the data source in Oracle Database Development Guide for more information.
By default, this is set to , and the database would not check for a time out set by the ODBC application. It is based on features of Oracle See Software Problems Fixed. See the Installation guide of each platform to learn more about each operating system and Oracle Client software requirements.
Most of the software bug fixes are generic in nature though some may have been discovered on a particular platform. There could be a small number of platform specific software bug fixes as well. Software bug fixes are described for the following versions. SQLColumns returned an incorrect data type for some columns when fetched Bug Bug It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.
If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties.
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
JavaScript must be enabled to correctly display this content. New Features Describes new features by release from release Support is added for time stamp with time zone and time stamp with local time zone. Bug Changed the behavior of describing metadata for stored procedures that exist in some package.
Post-installation Task Complete these post-installation tasks. Bugs Fixed Follow the link to software problems fixed. IA64 bit, bit 2.
Software Problems Fixed Software problems fixed are shown by version for versions Most of the software bug fixes are generic in nature though some may have been discovered on a particular platform.
There could be a small number of platform specific software bug fixes as well. Software bug fixes are described for the following versions: Version Bug OdbcConnection. Bug Migrating an Oracle Database 11 g Release 2 Bug ODBC Bug A Microsoft Access client hung trying to link a table over a database link. Bug Crash is due to array bind when the array bind is done a number of times.
Bug Temporary lob not free after data is fetched. Bug Oracle ODBC driver use to throw pop up window of change-password repeatedly when database password expired. Bug ODBC driver use to return wrong suffix and prefix lengths on bit environment. Click Finish. You can provide the other information requested in the dialog box, or you can leave the fields blank and provide the information when you run the application.
After you have entered the data, click OK or click Return. You can change or delete a data source at any time. The following subtopics explain how to add, change, or delete a data source.
To modify an Oracle data source:. To delete an Oracle data source:. The following list is an explanation of the main setup options and fields found on the Oracle ODBC Driver Configuration dialog box shown in the preceding graphic. The tabs found on the lower half of this dialog box are described in subsequent topics. For example, "odbc-pc". You must enter a DSN.
Description - A description or comment about the data in the data source. For example, "Hire date, salary history, and current review of all employees. User ID - The user name of the account on the server used to access the data. For example, "scott". The User ID field is optional. You can provide the other information requested in the dialog box or you can leave the fields blank and provide the information when you run the application. In addition to the main setup options previously described, there is a Test Connection button available.
When you press the Test Connection button, you are prompted for the username and password. Application Options. Oracle Options. Workarounds Options. The following list is an explanation of the fields found on the Application Options tab shown in the preceding graphic:. If Result Sets are not required for your application, Result Set support can be disabled.
There is a small performance penalty for procedures called from packages not containing Result Sets. Result Sets are enabled by default. Query Timeout is enabled by default. Read-Only Connection - Check this box to force read-only access. The default is write access. Enable Closing Cursors - Enables closing cursors. By default, closing cursors is disabled the field is empty , meaning a call to close a cursor does not force the closing of OCI cursors when this behavior is not desired because it can cause an unnecessary performance hit.
Enable closing cursors when you want to force the closing of OCI cursors upon a call to close a cursor. Enable Thread Safety - Thread safety can be disabled for a data source.
If thread safety is not required, disabling this option eliminates the overhead of using thread safety. By default, thread safety is enabled. Batch Autocommit Mode - By default, commit is executed only if all statements succeed. Numeric Settings - Allows you to choose the numeric settings that determine the decimal and group separator characters when receiving and returning numeric data that is bound as strings. The following list is an explanation of the fields found on the Oracle Options tab shown in the preceding graphic:.
Fetch Buffer Size - The amount of memory used to determine how many rows of data the ODBC Driver prefetches at a time from an Oracle database regardless of the number of rows the application program requests in a single query. However, the number of prefetched rows depends on the width and number of columns specified in a single query. Applications that typically fetch fewer than 20 rows of data at a time improve their response time, particularly over slow network connections or to heavily loaded servers.
Setting Fetch Buffer Size too high can make response time worse or consume large amounts of memory. There is a small performance penalty for insert and update statements when LOBs are enabled.
Enable Statement Caching - Enables statement caching feature, which increases the performance of parsing the query, in case the user has to parse the same text of query and related parameters multiple times.
The default is disabled. The default cache buffer size is 20 that are used only if statement caching option is enabled. Setting cache buffer size to 0 disables statement caching feature. The default size is 8 KB bytes. The maximum value that can be set is KB bytes. Translate ORA errors - Any migrated third party ODBC application, which is using the SQL Translation Framework feature, expects that errors returned by the server to be in their native database format, then users can enable this option to receive native errors based on the error translation registered with SQL Translation Profile.
Convert Empty String - Any third party ODBC application that is migrated to Oracle Database requires handling empty string data Oracle Database does not handle empty string data in table columns , then they can enable this option so that the application can insert empty string data or retrieve empty string data.
This feature is not implemented for Oracle Database 12 c Release 1 Enable this option to configure additional failover retries. The default is enabled. Retry - The number of times the connection failover is attempted. The default is 10 attempts.
Delay - The number of seconds to delay between failover attempts. The default is 10 seconds. The following list is an explanation of the fields found on the Workarounds Options tab shown in the preceding graphic:. This support is disabled by default. ODBC calls made by the application to specifically change the value of the attribute after connection time are unaffected by this option and complete their functions as expected.
By default, this option is off. This enhancement improves the performance of Oracle ODBC driver up to 10 times, depending on the prefetch size set by the user. The default value is 0. The maximum value that you can set is 64 KB bytes. If the value of prefetch size is greater than , the data fetched is only bytes.
If you pass a buffer size less than the prefetch size in nonpolling mode, a data truncation error occurs if the LONG data size in the database is greater than the buffer size.
By default, this function is enabled. A subprogram call specified in an EXEC statement is translated to its equivalent Oracle subprogram call before being processed by an Oracle database server. By default this option is disabled.
Schema , which is the translated Oracle subprogram assumed to be defined in the user's default schema. However, if all subprograms from the same SQL Server database are migrated to the same Oracle schema with their database name as the schema name, then set this field to database. If all subprograms owned by the same SQL Server user are defined in the same Oracle schema, then set this field to owner.
This field is empty by default.
0コメント