SQL Programming Manual for TAL

Program Compilation and Execution
HP NonStop SQL Programming Manual for TAL—527887-001
5-28
Understanding Run-Time Recompilation Errors
Understanding Run-Time Recompilation Errors
For automatic SQL recompilation of an entire program at run time, the SQL executor
returns compilation errors or warnings as follows:
•
If an SQL statement causes an error or warning, the statement remains
uncompiled in the program file and the SQL executor suppresses the error or
warning message.
•
If the SQL executor subsequently tries to execute the uncompiled statement, the
SQL executor tries again to automatically recompile the statement. If the statement
still causes a compilation error or warning, the SQL executor returns a run-time
error message to the program.
At run time, a program receives SQL compiler errors only when the SQL statement that
produces the error executes.
Maximizing Local Autonomy
Local autonomy in a network-distributed database ensures that a program can access
data on the local system, regardless of the availability of remote SQL objects. If your
program accesses a network-distributed database, you can maximize local autonomy
by:
•
Using a local partition, rather than the primary partition, as the table name for
partitioned tables
•
Using TACL DEFINEs
•
Using current statistics
•
Skipping unavailable partitions
For more information about managing applications for local autonomy, see the
SQL/MP Installation and Management Manual.
Using a Local Partition
If your program uses a remote partition, the SQL compiler looks for information about
the table in a remote catalog. If the remote system is down, the SQL compilation fails.
However, if your program uses a local partition, the SQL compiler looks for the
information in a local catalog. Provided the local system and data are available, the
SQL compilation is successful.