Oracle Call Interface
The client has two Oracle Business Intelligence servers that make Oracle database calls thru the Oracle Call Interface (OCI). Unfortunately, the dynaTrace is blind to those calls and the Oracle database connections are not shown in the Transaction Flow dashlet. Moreover, there no JDBC API displayed in the API Breakdown dashlet.
Is there anything that can be done (i.e., sensors, etc..) that can make the Oracle database queries visible to dynaTrace (i.e., shown in the transaction Flow dashlet, etc...).
Regards,
Anoh Brou
Hello,
I am testing Tuxedo Servers Instrumentation via ADK. I am able to see in the transaction flow, the service requests, the time spent, etc but I am not able to see the Database calls coming from Tuxedo servers (I just see these calls coming from Weblogic).
The thing is that via Weblogic we use JDBC and Weblogic Agent Group has "JDBC" sensor pack associated. For ADK I just have activated "Agent Development kit" sensor pack. I am making Database calls using OCI (library libclntsh.so ). I am looking for something like "OCI Sensor Pack" but I don't meet it.
Do you know a way to get Database calls using OCI (not JDBC) via ADK?
Thanks in advance.
Alberto.
Just had a short conversation with an ADK developer and we think it is better to go forward with the customer sensor pack. However by using the java calls to Siebel.dll we will not get any database attachments and therefore no information in the database dashlet. So they are only visible via the API. The queries are only visible if you capture them via method arguments.
- stefan
Hello Stefan,
Thank you once again for the information. The issue is that I have never written a custom sensor pack. Would it be possible for the ADK developer to send me a version of the custom sensor pack? I can modify it as need be.
Regards,
Anoh
Hi maybe a custom sensor pack which takes care of all java calls to the siebel.dll and marks them the desired API if these calls are made by native components you can still use the ADK for that I'll forward this information to a colleague of mine.
- stefan
Hi,
the OCI calls you are mentioning are they done via a java application where a java agent is injected? Additionally is OCI via JDBC used?
regards
Stefan
Good morning Stephan,
The OCI calls are indeed made via a Java application where the agent is injected. The OCI via JDBC is not used. The call is made via a Siebel DLL. This process encapsulated all the Oracle calls, hence making them invisible to dynaTrace. I would like to know if there were any ways available to unravel the "blackbox".
Regards,
Anoh Brou
