Issues after last CPU 20180417 on Windows with ODP.NET — oracle-tech

    Forum Stats

  • 3,716,000 Users
  • 2,242,928 Discussions
  • 7,845,734 Comments

Discussions

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Issues after last CPU 20180417 on Windows with ODP.NET

799292
799292 Member Posts: 6
edited June 2018 in ODP.NET

I administrate a software which uses normaly the ODP.NET provider: "Oracle.DataAccess.Client".
After updating the database (which is also the client because database and application is on the same server) I got the following error:

System.IndexOutOfRangeException: Index was outside the bounds of the array.

at OracleInternal.ConnectionPool.ConnectionString.Compare(String constr)

at OracleInternal.ConnectionPool.ConnectionString.GetCS(String constr)

at Oracle.DataAccess.Client.OracleConnection.set_ConnectionString(String value)

...


The connection string is (and was not changed): "Password=<xxxx>; User Id=AUD1; Data Source=IADDB" (with corresponding entry in the tnsnames.ora file).

I use now the Microsoft Provider: "System.Data.OracleClient". But with this driver the software is not able to handle CLOB values.

There are many exceptions with this message: "System.Data.OracleClient.OracleException: ORA-01461: can bind a LONG value only for insert into a LONG column" and long texts cannot be inserted or updated in the database.

(And handling of CLOB values was possible with the oracle driver before!)

I would like to switch back to the Oracle driver to prevent these errors.


Oracle.DataAccess.dlls are registered via OraProvCfg.exe for "4" and "2.x".
Managed driver is not installed.

My system: Oracle Database is on same server as application.

Operation system: Windows Server 2008 R2 SP1

Installed Patch: WINDOWS DB BUNDLE PATCH 11.2.0.4.180417:(27381640)

Answers

  • Alex Keh-Oracle
    Alex Keh-Oracle Posts: 2,753 Employee
    edited June 2018

    Normally, I would recommend backing out the patch on the server or client or both, whichever causes the error. Since this is a CPU, the preferred solution is to diagnose the root cause and fix it. The problem itself may not be due to ODP.NET. It could some issue with the Oracle Client or DB server that the patch changed. I would recommend opening up an Oracle SR and working with Support to diagnose the issue, Oracle then should be able to provide you a workaround or fix to resolve it.

  • 799292
    799292 Member Posts: 6
    edited June 2018

    Thank you for your answers.

    I have created now a service request.

    Number is SR 3-17672759281
    (I am not able to paste copied things into this application!)

This discussion has been closed.