The pureQueryXML file contains "n" Special Register SET statements or methods that were recorded after other SQL statements were issued using the associated Connection. This might indicate that the file contains SQL statements that were originally prepared using multiple, different special register settings.
An example of an application that might run differently when executing SQL statements statically and dynamically is if statements are encountered first with a CURRENT SCHEMA of WEEK1_SALES, and later with a CURRENT SCHEMA of WEEK5_SALES. Such statements cannot be safely run statically if they contain unqualified names. It is possible, to use the Configure utility groupSQLBySpecialRegisters option as part of the process of configuring that application to run such statements dynamically.
If the packages need to be bound only at specific isolation levels, use the StaticBinder -isolationLevel option to specify the isolation level.
If a problem occurs with the pureQueryXML file, you can validate pureQueryXml files by specifying the -validateXml TRUE option with the pureQuery utilities Merge, Configure, and StaticBinder. Any XML validation errors are displayed when the utility is run. The utility validates the input XML documents with the pureQueryXML schema.
If you manually edit a pureQueryXML file, be sure that you create a backup copy of the file first. Use the -validateXml option with the pureQuery Merge, Configure, and StaticBinder utilities to perform XML schema validation on input pureQueryXML files.