ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzajq_5.4.0.1/pimesodp.htm

91 lines
5.6 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Query optimization performance information messages and open data paths" />
<meta name="abstract" content="Several of the following SQL run-time messages refer to open data paths." />
<meta name="description" content="Several of the following SQL run-time messages refer to open data paths." />
<meta name="DC.subject" content="open data path, definition, definitions, data path, open, path, open data, open data path, information messages, performance, open data path messages, message, open data path information" />
<meta name="keywords" content="open data path, definition, definitions, data path, open, path, open data, open data path, information messages, performance, open data path messages, message, open data path information" />
<meta name="DC.Relation" scheme="URI" content="rzajqmsgref.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7910.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7911.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7912.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7913.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7914.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7915.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7916.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7917.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7918.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7919.htm" />
<meta name="DC.Relation" scheme="URI" content="sql7939.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="pimesodp" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Query optimization performance information messages and open data paths</title>
</head>
<body id="pimesodp"><a name="pimesodp"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Query optimization performance information messages and open data paths</h1>
<div><p>Several of the following SQL run-time messages refer to open data
paths.</p>
<p>An open data path (ODP) definition is an internal object that is created
when a cursor is opened or when other SQL statements are run. It provides
a direct link to the data so that I/O operations can occur. ODPs are used
on OPEN, INSERT, UPDATE, DELETE, and SELECT INTO statements to perform their
respective operations on the data.</p>
<p>Even though SQL cursors are closed and SQL statements have already been
run, the database manager in many cases will save the associated ODPs of the
SQL operations to reuse them the next time the statement is run. So an SQL
CLOSE statement may close the SQL cursor but leave the ODP available to be
used again the next time the cursor is opened. This can significantly reduce
the processing and response time in running SQL statements.</p>
<p>The ability to reuse ODPs when SQL statements are run repeatedly is an
important consideration in achieving faster performance.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="sql7910.htm">SQL7910 - All SQL cursors closed</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7911.htm">SQL7911 - ODP reused</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7912.htm">SQL7912 - ODP created</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7913.htm">SQL7913 - ODP deleted</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7914.htm">SQL7914 - ODP not deleted</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7915.htm">SQL7915 - Access plan for SQL statement has been built</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7916.htm">SQL7916 - Blocking used for query</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7917.htm">SQL7917 - Access plan not updated</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7918.htm">SQL7918 - Reusable ODP deleted</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7919.htm">SQL7919 - Data conversion required on FETCH or embedded SELECT</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="sql7939.htm">SQL7939 - Data conversion required on INSERT or UPDATE</a></strong><br />
</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajqmsgref.htm" title="See the following for query optimizer message reference:">Query optimizer messages reference</a></div>
</div>
</div>
</body>
</html>