Re: [Info-Ingres] ODBC trace
- From: Grant Croker <grant.croker@xxxxxxxxxx>
- Date: Thu, 02 Jul 2009 17:35:42 +0200
On/El 02/07/09 17:01, Paul White wrote/escribió:
Hi all,Paul,
There doesn't seem to be a simple way to trace the ODBC calls from the
client side.
I'm trying to track down a problem in a crystal report with a date
parameter.
It started occurring after updating the client to OpenROAD 2006. Ingres Net
is 2006.
The developer has received an ODBC only patch from Ingres Support but it
hasn't solved the problem.
The date parameters are entered dd/mm/yyyy. An Ingres ODBC error is returned
something like YYYY is not a valid month.
Is server side tracing still the recommended approach?
I read trace point sc902 and printqry could be used.
To see what's going across the wire you can use OpenAPI and GCA tracing:
II_API_TRACE=5
II_GCA_TRACE=5
II_API_LOG=c:\api.log
This will need to be set in the environment before the application starts. I am not sure the service side tracing will work as I guess the "invalid" data is being rejected by the Ingres client. I am a bit confused as to how the YYYY component can end up in the month position unless there is a funky locale being used?
g
--
Grant Croker - Ingres PHP and Ruby maintainer
http://blogs.planetingres.org/grant
Generally, old media don't die. They just have to grow old gracefully.
Guess what, we still have stone masons. They haven't been the primary
purveyors of the written word for a while now of course, but they still
have a role because you wouldn't want a TV screen on your headstone.
.
- Follow-Ups:
- Re: [Info-Ingres] ODBC trace
- From: Ingres Forums
- Re: [Info-Ingres] ODBC trace
- Prev by Date: Re: [Info-Ingres] ODBC trace
- Next by Date: Re: [Info-Ingres] ODBC trace
- Previous by thread: Re: [Info-Ingres] ODBC trace
- Next by thread: Re: [Info-Ingres] ODBC trace
- Index(es):
Relevant Pages
|
