Happy New Year, folks. My year has started rather eventfully, as I have spent the most productive part of my day trying to resolve a problem with a DDL statement being executed as part of a product CI build.
The problem? There is a stored procedure on a project that I am able to run successfully via Oracle SQL Developer but have been unable to get working as part of the build. Currently, the Oracle JDBC Driver spits out the following nondescript SQL exception message: Non supported SQL92 token at position: x. X in this case seems to be some arbitrary location in the script ( this currently resolves to end of the file, meaning it has been misdiagnosed), which I cannot decipher as being an invalid token.
What would have been useful in the exception message, and I hark back to the days of Oracle SQL*plus, is a line number and column number with some mention of the errant token.
I am still trying to manually debug this problem in the hope that I am able to resolve it, as no successful build means no check-in. My suspicion is that the driver is doing something nasty or is unable to properly deal with a token that should ordinarily pose no problem.
I am using a v10.x Driver.
If you are reading this, have you encountered a problem like this recently? Any light you can shed is appreciated.
Thanks
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment