on 09-13-2009 9:20 AM
Hi
I was wondering is there any log files for RDC component of crystal 10 (CRAXDRT.dll) ?
thnx in advance
Hi Daniel,
What specific parts are you wanting to log and why?
Thank you
Don
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are using Crystal Reports 10 RDC component in ASP files to view reports in our web application deployed on IIS.
All of our reports are using stored procedures calling Oracle DB.
This web application is deployed on number of windows 2003 servers on customer sites.
We have one customer with unique problem that repeats about 1 time a month in the last 3 months.
The problem is that page showing crystal report never gets the requested data from DB and sometimes
And a general OCI error is returned u201CQuery Engine Error: 'Fail to execute SQL statement. OCI call: OCIStmtExecuteu201D
Now i am trying to track it down with no success, therefore i wanted to log everything i can to see where things go wrong
Hi Daniel,
We don't have anything for the RDC without escalating and getting R&D to build a version of craxdrt.dll that turns on specific logging for a specific area. We do have a DB logging dll but these can generate huge amounts of data and if it only happens once a month it would likely fill your hard drive up and then some... And also it will put an excess load on the system which will affect performance and production.
From the error it appears you are using ODBC as your connection method? Try using a different ODBC driver, we have one from Data Direct that supports Oracle you may want to test with. Choose any recent version of Crystal and you'll find them on our download page.
Also that error is what we are receiving from the Oracle Client, CR is simply passing the error message from the client to your host application. Logging of CR components won't tell you anything more.
ODBC tracing isn't going to tell you anything either but possibly it will catch if a bad SQL statement or a data read happens. Typically this OCIStmtExecute function is related to a new thread being opened by the client/CR. For each subreport Cr will create a new thread off the HDBC handle, original connection. It could be your client is simply running out of connections, I don't recall the exact number but I do believe Oracle is limited to the number of open connections/threads it can handle.
It may even be caused by bad data getting buffered in the ODBC driver.... You may want to search Oracles site also for that error. Typically it also includes a ORA number so currious what that number is? If you have a DBA who can turn on Oracle logging that may capture the problem also but again that log is likely going to be huge.
There is also the possibility it's neither of us and could be a network issue, too much traffic or too many requests going to the Oracle Server etc. It just shows up in your app. If they have an IT department they may want to log errors, could be an issue there also...
Does it happen around the same time each month? Say when end of month reports are being run and the server is very busy? Could be this is the cause also, loading....
Thanks again
Don
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.