I have an aqua script that reads queries from files and executes them against an Oracle database. It was all working fine until this week, when I started getting ORA-00911 errors from the database when the script executes the queries. When I look at the files there's a three byte UTF8 BOM marker that precedes the select statement, and I think that's what is causing my db error.
I can go through the files and remove that marker, but the mystery is that it just randomly started doing this. The other curious thing is that these queries run fine if I load them into the editor, and even when I deploy the aqua project to the server and execute the aquascript from there. I think the UTF8 mark was probably put there when I opened the files in another editor, but the difference in behavior is interesting.
It works fine in production, but it makes developing and debugging a bit of a pain. I'm trying to narrow down what might be going on. Here's what I'm doing in my script:
queryFile = aqua.project.getAquaScript("query path");
dataSet = conn.executeSnapshot(query);
My two possibilities so far are that the behavior hasn't changed in ADStudio or ADServer, but that the database stopped handling the UTF8 mark for some reason. My other thought is that I updated ADStudio, and now the execute or read works differently from the server. Should there be a parameter to specify the encoding of the file I'm reading as I might do in Java? I'm just looking for some guidance on which direction to go for troubleshooting.
Here's my system details if you need it.
Aqua Data Studio 10.0.0 Build #: 23536 Built on: 2011-Sep-23 05:36:02 PM on Mac OSX 10.7.2
Product: Aqua Data Server
Build #: 23727
Build Date: 2011-Oct-07 11:04:33 AM
Operating Environment: Windows Server 2008 R2 (6.1, amd64) / Cp1252 / en / US / Sun Microsystems Inc. 1.6.0_20-b02
Memory: Max=477,233,152; Total=184,483,840; Free=45,846,568;