Skip to Main Content
Forums

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Windows 10 1809 ODBC Data Source Administrator Crash Oracle 19c Client

user4987584Dec 5 2019 — edited Jun 19 2020

Hi Everyone,

I have installed Windows 10 1809 and Oracle 19c Client with ODBC.

In the ODBC Data Source Administrator (32-bit) the "Oracle in OraClient19Home1_32bit" driver works fine.

But when I try to use the "Microsoft ODBC for Oracle" File MSORCL32.DLL with version 10.00.17763.01 the ODBC Data Source Administrator crashes.

I can find following information in the eventvwr.

Faulting application name: odbcad32.exe, version: 10.0.17763.1, time stamp: 0xecf45257

Faulting module name: ntdll.dll, version: 10.0.17763.831, time stamp: 0x6071cf9d

Exception code: 0xc0000005

Fault offset: 0x0004fe05

Faulting process id: 0x245c

Faulting application start time: 0x01d5ab7b4919c9e8

Faulting application path: C:\WINDOWS\syswow64\odbcad32.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: b9dc3f1e-e97a-468a-aaf9-ef607a63d3d4

Faulting package full name:

Faulting package-relative application ID:

I did not have this problem with the Oracle 12 Client.

Thanks,

Stephan

Comments

unknown-7404
Those are 'properties' and would be set on the command-line but you can set them in code before you begin referencing JDBC.

They are generally only (and then only rarely) used in an application server context.

See the Application Server Performance Guide

>
6.3.7 Setting the OC4J JDBC DMS Statement Metrics Option
To improve performance, by default OC4J does not collect JDBC statement metrics. The properties, oracle.jdbc.DMSStatementCachingMetrics and oracle.jdbc.DMSStatementMetrics are by default, set to false. When these properties are false, performance is improved since OC4J does not collect expensive JDBC statement level metrics.

Setting these properties to true may have a negative impact on performance. You should only set these properties to true when you need to collect JDBC statement metrics.

When oracle.jdbc.DMSStatementCachingMetrics property is set to true and JDBC statement caching is enabled, the JDBC statement metrics are available.

When JDBC statement caching is disabled, make the JDBC statement metrics available by setting the property oracle.jdbc.DMSStatementMetrics to true.
1002441
I set both oracle.jdbc.DMSStatementCachingMetrics and oracle.jdbc.DMSStatementMetrics to true, but still do not see the SQLText value in DMS Spy.

So I want to try another way, "If the 11.1 version of the DMS JAR file is present in the classpath environment variable, then JDBC checks the DMS update SQL text flag. If this flag is true, then the SQLText metric is updated." The problem is it does not mention what's the name of this "DMS update SQL text flag", or how to set it.
unknown-7404
This question has NOTHING to do with JDBC. As previously stated DMS is used ONLY within an application server context.

You should mark this question ANSWERED and repost it in the Fusion Middleware forum.
3377

DMS is used in Oracle Application Server and WebLogic Server. You shouldn't be using it except in those environments.
1 person found this helpful
1 - 3

Post Details

Added on Dec 5 2019
#odbc, #windows-and-net
13 comments
7,950 views