

A transaction should consist of all of the necessary parts for one logical unit of work, no more and no less. Transactions must be defined properly so work is accomplished in logical units and data is kept consistent. In general, only application designers using the programming interfaces to Oracle are concerned with which types of actions should be grouped together as one transaction. Where level can be either ENTRY, INTERMEDIATE, or FULL.įigure 7-1 The Stages in Processing a SQL Statement ORA-00097: Use of Oracle SQL feature not in SQL92 level Level When flagging is on and non-standard SQL is encountered, the following message is returned: The Oracle Precompilers and SQL*Module also support FIPS flagging of embedded and module language SQL. The FIPS flagging feature supports flagging through interactive SQL statements submitted using Enterprise Manager or SQL*Plus. If any non-standard constructs are found, then the Oracle Server flags them as errors and displays the violating syntax. When FIPS flagging is active, your SQL statements are checked to see whether they include extensions that go beyond the ANSI/ISO SQL92 standard.
#SQL BALANCE LOCK PORTABLE#
Oracle provides a FIPS flagger to help you write portable applications. The Federal Information Processing Standard for SQL (FIPS 127-2) requires a way to identify SQL statements that use vendor-supplied extensions. Identifying Extensions to SQL92 (FIPS Flagging) Refer to Oracle8i Conceptsfor a description of each stage of SQL statement processing for each type of SQL statement. However, you might find this information useful when writing Oracle applications. Most users do not need to be concerned with, or aware of, this level of detail.
#SQL BALANCE LOCK CODE#
For example, the DEFINE stage could occur just before the FETCH stage, depending on how your code is written.įor many Oracle tools, several of the stages are performed automatically. In some cases, these steps might be executed in a slightly different order. Table 7-1 outlines the stages commonly used to process and execute a SQL statement. Any other data access method would circumvent the security built into Oracle and potentially compromise data security and integrity. Concurrency Control Using Serializable TransactionsĪlthough some Oracle tools and applications simplify or mask the use of SQL, all database operations are performed using SQL.Ensuring Repeatable Reads with Read-Only Transactions.This chapter describes how Oracle processes Structured Query Language (SQL) statements.
