Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 394 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
ORA-01017 with Managed Provider 4.112.3.60. Bug with ODP on Win 2008 R2?
Answers
-
Can you try setting "none" in your sqlnet.authentication_services in sqlnet.ora?
-
Today's test 26 May
Compile x64
Sqlnet.authentication_services set to NONE
Recompile AnyCPU
sqlnet.authentication_services set to NONE
sqlnet.authentication_services set to NTS
ALL three tests Returned same exception handler and ODAC trace information that we saw in yesterday's test
+++++++++++++++++++++++++++++
Will the XCOPY 12cR1 ODAC MANAGED driver
be the same as the BETA 11g .60?
Or is it later version?
You mentioned XCOPY 12c ODAC MANAGED driver will be out soon.
-
Will the XCOPY 12cR1 ODAC MANAGED driver be the same as the BETA 11g .60? Or is it later version?
It's a later version. Additional features have been added, such as LDAP support, and bug fixes were made based on Beta 2 feedback.
-
My next test will be with 12cR1 ODAC managed driver unless your staff has additional tests based on all the logs sent your way and todays authentication and bitness testing.
-
Tried the latest version ODAC MANAGED driver from Oracle 12cR1 Client x64 bit installer.
Same trace file and exception errors.
So I guess you will be calling me sometime.
-
Does the Oracle Client built into the MANAGED driver dll have any limitations??
The SQL statement in the test app is a simple call to get list of table names for parameter "owner"
SELECT table_name FROM all_tables WHERE owner = {bind var colon symbol}owner
not privilege issue as the sql statement runs from SQLPlus
nor ODP.NET parameter, cmd, open issue as the sql statement runs via Unmanaged R4 driver using full Client 11g203.
But the MANAGED driver uses its own client within the DLL (I presume similar to instant client),
and it may have limitations I am not aware of (at least from reading OPD.NET Guide)
-
All known limitations are documented in the ODP.NET Developer's Guide and README. Managed ODP.NET does not implement every feature in umanaged ODP.NET. We tried to implement the major features and keep performance comparable so that the great majority of existing unmanaged ODP.NET users could seamlessly switch to managed if they would like to. Over time, the goal is feature parity between the two providers.
What error did you receive?
-
Same error reported above in trace and log files.
-
I just tried the managed provider that comes with 12c client install and am able to reproduce this behavior also.
My dev machine is Windows 7 32bit and a console application doing nothing but opening a connection to a database with a hardcoded connection string, and it opens and closes the connection successfully.
Our development test server is on Windows Server 2008 R2 and that same console application with the same connection string and the same version of the managed ODP.NET yeilds the following error when opening the connection: "OracleException (0x3f9): ORA-01017: invalid username/password; logon denied"
-
I think I know what's going on here. It looks like the AES algorithm is being used to encrypt the password while connecting to the database. The AES implementation in .NET is NOT FIPS compliant which causes problems in the public sector (I noticed you were in the government, as am I). The only way I was able to get around this issue was to turn off FIPS Policy enforcement (http://msdn.microsoft.com/en-us/library/hh202806.aspx.) The joys of security...
