-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using OpenTelemetry instrumentation and setting EnableSqlIdTracing = true causes errors when working with refcursor output of a packaged procedure #416
Comments
Can you turn on ODP.NET tracing and share the trace? |
@alexkeh , can I provide it via email ? |
Yes, you can send it to dotnet_us(at)oracle.com. |
Traces sent. |
Thanks @omon77 for reporting this issue. I was able to reproduce your findings with the test case. I've filed a bug (37160309) and will have the ODP.NET dev team review the issue to identify the root cause. |
Thank you @alexkeh ! |
Hello, I'm having problems when I use I think this problem is related to this issue. query (column SELECT
ADA.CODANEXO,
ADA.TIPODOCUMENTOANEXO,
ADA.ANEXADOEM,
ADA.ARQUIVO,
ADA.NOMEARQUIVO,
ADA.EXTENSAOARQUIVO
FROM ADM$DOCUMENTOANEXO ADA
WHERE CODPACIENTE = :CodPaciente
AND ADA.DELETADO = 0 exception:
|
@andrevlins Your issue could be a separate one. The exception reported in the original issue is the following:
That's different from your issue. Can you share a trace from the ODP.NET app? That will tell us more details about what is generating the error. |
@alexkeh here are the traces |
While using Oracle.ManagedDataAccess.Core v23.5.1 and v23.6.0 (not sure about prior versions), and wiring up OpenTelemetry via Oracle Data Provider Instrumentation, setting EnableSqlIdTracing to
true
causes Oracle exception to be thrown when reading refcursor returned by a packaged procedure.
The text was updated successfully, but these errors were encountered: