|Oracle® Database Administrator's Guide
10g Release 1 (10.1)
Part Number B10739-01
See Also:Oracle Database Application Developer's Guide - Fundamentals for more information about application development in an Oracle Database environment
Number of transactions posted from each location
Amount of data (portion of table) used by each node
Performance characteristics and reliability of the network
Speed of various nodes, capacities of disks
Importance of a node or link when it is unavailable
Need for referential integrity among tables
When a global object name is referenced in a SQL statement or remote procedure call, database links establish a connection to a session in the remote database on behalf of the local user. The remote connection and session are only created if the connection has not already been established previously for the local user session.
The connections and sessions established to remote databases persist for the duration of the local user's session, unless the application or user explicitly terminates them. Note that when you issue a
SELECT statement across a database link, a transaction lock is placed on the undo segments. To rerelease the segment, you must issue a
Terminating remote connections established using database links is useful for disconnecting high cost connections that are no longer required by the application. You can terminate a remote connection and session using the
ALTER SESSION statement with the
CLOSE DATABASE LINK clause. For example, assume you issue the following transactions:
SELECT * FROM emp@sales; COMMIT;
The following statement terminates the session in the remote database pointed to by the
sales database link:
Note:Before closing a database link, first close all cursors that use the link and then end your current transaction if it uses the link.
See Also:Oracle Database SQL Reference for more information about the
If a part of a distributed statement fails, for example, due to an integrity constraint violation, the database returns error number
ORA-02055. Subsequent statements or procedure calls return error number
ORA-02067 until a
ROLLBACK TO SAVEPOINT is issued.
Design your application to check for any returned error messages that indicate that a portion of the distributed update has failed. If you detect a failure, you should roll back the entire transaction before allowing the application to proceed.
The database does not permit declarative referential integrity constraints to be defined across nodes of a distributed system. In other words, a declarative referential integrity constraint on one table cannot specify a foreign key that references a primary or unique key of a remote table. Nevertheless, you can maintain parent/child table relationships across nodes using triggers.
If you decide to define referential integrity across the nodes of a distributed database using triggers, be aware that network failures can limit the accessibility of not only the parent table, but also the child table. For example, assume that the child table is in the
sales database and the parent table is in the
hq database. If the network connection between the two databases fails, some DML statements against the child table (those that insert rows into the child table or update a foreign key value in the child table) cannot proceed because the referential integrity triggers must have access to the parent table in the
See Also:Oracle Database Application Developer's Guide - Fundamentals for more information about using triggers to enforce referential integrity
The local Oracle Database server breaks the distributed query into a corresponding number of remote queries, which it then sends to the remote nodes for execution. The remote nodes execute the queries and send the results back to the local node. The local node then performs any necessary post-processing and returns the results to the user or application.
You have several options for designing your application to optimize query processing. This section contains the following topics:
For example, assume you reference five remote tables from two different remote databases in a distributed query and have a complex filter (for example,
50000). You can improve the performance of the query by rewriting the query to access the remote databases once and to apply the filter at the remote site. This rewrite causes less data to be transferred to the query execution site.
Rewriting your query to access the remote database once is achieved by using collocated inline views. The following terms need to be defined:
Two or more tables located in the same database.
SELECT statement that is substituted for a table in a parent
SELECT statement. The embedded
SELECT statement, shown within the parentheses is an example of an inline view:
SELECT e.empno,e.ename,d.deptno,d.dname FROM (SELECT empno, ename from firstname.lastname@example.org) e, dept d;
Collocated inline view
An inline view that selects data from multiple tables from a single database only. It reduces the amount of times that the remote database is accessed, improving the performance of a distributed query.
Oracle recommends that you form your distributed query using collocated inline views to increase the performance of your distributed query. Oracle Database cost-based optimization can transparently rewrite many of your distributed queries to take advantage of the performance gains offered by collocated inline views.
In addition to rewriting your queries with collocated inline views, the cost-based optimization method optimizes distributed queries according to the gathered statistics of the referenced tables and the computations performed by the optimizer.
For example, cost-based optimization analyzes the following query. The example assumes that table statistics are available. Note that it analyzes the query inside a
CREATE TABLE statement:
CREATE TABLE AS ( SELECT l.a, l.b, r1.c, r1.d, r1.e, r2.b, r2.c FROM local l, remote1 r1, remote2 r2 WHERE l.c = r.c AND r1.c = r2.c AND r.e > 300 );
and rewrites it as:
CREATE TABLE AS ( SELECT l.a, l.b, v.c, v.d, v.e FROM ( SELECT r1.c, r1.d, r1.e, r2.b, r2.c FROM remote1 r1, remote2 r2 WHERE r1.c = r2.c AND r1.e > 300 ) v, local l WHERE l.c = r1.c );
v is assigned to the inline view, which can then be referenced as a table in the preceding
SELECT statement. Creating a collocated inline view reduces the amount of queries performed at a remote site, thereby reducing costly network traffic.
The main task of optimization is to rewrite a distributed query to use collocated inline views. This optimization is performed in three steps:
All mergeable views are merged.
Optimizer performs collocated query block test.
Optimizer rewrites query using collocated inline views.
After the query is rewritten, it is executed and the data set is returned to the user.
While cost-based optimization is performed transparently to the user, it is unable to improve the performance of several distributed query scenarios. Specifically, if your distributed query contains any of the following, cost-based optimization is not effective:
If your distributed query contains one of these elements, see "Using Hints" to learn how you can modify your query and use hints to improve the performance of your distributed query.
After you have set up your system to use cost-based optimization to improve the performance of distributed queries, the operation is transparent to the user. In other words, the optimization occurs automatically when the query is issued.
You need to complete the following tasks to set up your system to take advantage of cost-based optimization:
To enable cost-based optimization, set the
OPTIMIZER_MODE initialization parameter to
COST. You can set this parameter by:
OPTIMIZER_MODE parameter in the initialization parameter file
Setting it at session level by issuing an
ALTER SESSION statement
Issue one of the following statements to set the
OPTIMIZER_MODE initialization parameter at the session level:
ALTER SESSION OPTIMIZER_MODE = CHOOSE; ALTER SESSION OPTIMIZER_MODE = COST;
See Also:Oracle Database Performance Tuning Guide for information on setting the
For cost-based optimization to select the most efficient path for a distributed query, you must provide accurate statistics for the tables involved. You do this using the
DBMS_STATS package or the
Note:You must connect locally with respect to the tables when executing the
ANALYZE TABLE email@example.com COMPUTE STATISTICS;
You must first connect to the remote site and then execute the preceding
DBMS_STATS procedures enable the gathering of certain classes of optimizer statistics:
For example, assume that distributed transactions routinely access the
scott.dept table. To ensure that the cost-based optimizer is still picking the best plan, execute the following:
BEGIN DBMS_STATS.GATHER_TABLE_STATS ('scott', 'dept'); END;
If a statement is not sufficiently optimized, then you can use hints to extend the capability of cost-based optimization. Specifically, if you write your own query to utilize collocated inline views, instruct the cost-based optimizer not to rewrite your distributed query.
Additionally, if you have special knowledge about the database environment (such as statistics, load, network and CPU limitations, distributed queries, and so forth), you can specify a hint to guide cost-based optimization. For example, if you have written your own optimized query using collocated inline views that are based on your knowledge of the database environment, specify the
NO_MERGE hint to prevent the optimizer from rewriting your query.
This technique is especially helpful if your distributed query contains an aggregate, subquery, or complex SQL. Because this type of distributed query cannot be rewritten by the optimizer, specifying
NO_MERGE causes the optimizer to skip the steps described in "How Does Cost-Based Optimization Work?".
DRIVING_SITE hint lets you define a remote site to act as the query execution site. In this way, the query executes on the remote site, which then returns the data to the local site. This hint is especially helpful when the remote site contains the majority of the data.
See Also:Oracle Database Performance Tuning Guide for more information about using hints
NO_MERGE hint prevents the database from merging an inline view into a potentially noncollocated SQL statement (see "Using Hints"). This hint is embedded in the
SELECT statement and can appear either at the beginning of the
SELECT statement with the inline view as an argument or in the query block that defines the inline view.
/* with argument */ SELECT /*+NO_MERGE(v)*/ t1.x, v.avg_y FROM t1, (SELECT x, AVG(y) AS avg_y FROM t2 GROUP BY x) v, WHERE t1.x = v.x AND t1.y = 1; /* in query block */ SELECT t1.x, v.avg_y FROM t1, (SELECT /*+NO_MERGE*/ x, AVG(y) AS avg_y FROM t2 GROUP BY x) v, WHERE t1.x = v.x AND t1.y = 1;
Typically, you use this hint when you have developed an optimized query based on your knowledge of your database environment.
DRIVING_SITE hint lets you specify the site where the query execution is performed. It is best to let cost-based optimization determine where the execution should be performed, but if you prefer to override the optimizer, you can specify the execution site manually.
Following is an example of a
SELECT statement with a
SELECT /*+DRIVING_SITE(dept)*/ * FROM emp, firstname.lastname@example.org WHERE emp.deptno = dept.deptno;
An important aspect to tuning distributed queries is analyzing the execution plan. The feedback that you receive from your analysis is an important element to testing and verifying your database. Verification becomes especially important when you want to compare plans. For example, comparing the execution plan for a distributed query optimized by cost-based optimization to a plan for a query manually optimized using hints, collocated inline views, and other techniques.
See Also:Oracle Database Performance Tuning Guide for detailed information about execution plans, the
Before you can view the execution plan for the distributed query, prepare the database to store the execution plan. You can perform this preparation by executing a script. Execute the following script to prepare your database to store an execution plan:
After you execute
utlxplan.sql, a table,
PLAN_TABLE, is created in the current schema to temporarily store the execution plan.
After you have prepared the database to store the execution plan, you are ready to view the plan for a specified query. Instead of directly executing a SQL statement, append the statement to the
EXPLAIN PLAN FOR clause. For example, you can execute the following:
EXPLAIN PLAN FOR SELECT d.dname FROM dept d WHERE d.deptno IN (SELECT deptno FROM email@example.com GROUP BY deptno HAVING COUNT (deptno) >3 ) /
After you have executed the preceding SQL statement, the execution plan is stored temporarily in the
PLAN_TABLE that you created earlier. To view the results of the execution plan, execute the following script:
utlxpls.sql script displays the execution plan for the
SELECT statement that you specified. The results are formatted as follows:
Plan Table ------------------------------------------------------------------------------- | Operation | Name | Rows | Bytes| Cost | Pstart| Pstop | ------------------------------------------------------------------------------- | SELECT STATEMENT | | | | | | | | NESTED LOOPS | | | | | | | | VIEW | | | | | | | | REMOTE | | | | | | | | TABLE ACCESS BY INDEX RO|DEPT | | | | | | | INDEX UNIQUE SCAN |PK_DEPT | | | | | | -------------------------------------------------------------------------------
If you are manually optimizing distributed queries by writing your own collocated inline views or using hints, it is best to generate an execution plan before and after your manual optimization. With both execution plans, you can compare the effectiveness of your manual optimization and make changes as necessary to improve the performance of the distributed query.
To view the SQL statement that will be executed at the remote site, execute the following select statement:
SELECT OTHER FROM PLAN_TABLE WHERE operation = 'REMOTE';
Following is sample output:
SELECT DISTINCT "A1"."DEPTNO" FROM "EMP" "A1" GROUP BY "A1"."DEPTNO" HAVING COUNT("A1"."DEPTNO")>3
Note:If you are having difficulty viewing the entire contents of the
SET LONG 9999999
SQL errors such as
BEGIN ... EXCEPTION WHEN ZERO_DIVIDE THEN /* ... handle the exception */ END;
Notice that the
WHEN clause requires an exception name. If the exception does not have a name, for example, exceptions generated with
RAISE_APPLICATION_ERROR, you can assign one using
PRAGMA_EXCEPTION_INIT. For example:
DECLARE null_salary EXCEPTION; PRAGMA EXCEPTION_INIT(null_salary, -20101); BEGIN ... RAISE_APPLICATION_ERROR(-20101, 'salary is missing'); ... EXCEPTION WHEN null_salary THEN ... END;
When calling a remote procedure, exceptions can be handled by an exception handler in the local procedure. The remote procedure must return an error number to the local, calling procedure, which then handles the exception as shown in the previous example. Note that PL/SQL user-defined exceptions always return
ORA-06510 to the local procedure.
Therefore, it is not possible to distinguish between two different user-defined exceptions based on the error number. All other remote exceptions can be handled in the same manner as local exceptions.
See Also:PL/SQL User's Guide and Reference for more information about PL/SQL procedures