SYSIBM.SYSPACKSTMT db2 存储statement的表

SYSIBM.SYSPACKSTMT table

The SYSIBM.SYSPACKSTMT table contains one or more rows for each statement in a package.

Column name Data type Description Use
LOCATION

VARCHAR(128)

NOT NULL

Always contains blanks S
COLLID

VARCHAR(128)

NOT NULL

Name of the package collection. G
NAME

VARCHAR(128)

NOT NULL

Name of the package. G
CONTOKEN

CHAR(8)

NOT NULL

FOR BIT DATA

Consistency token for the package. This is either:

  • The "level" as specified by the LEVEL option when the package‘s program was precompiled
  • The timestamp indicating when the package‘s program was precompiled, in an internal format
S
SEQNO

INTEGER

NOT NULL

Not used. G
STMTNO

SMALLINT

NOT NULL

The statement number of the statement in the source program. A statement number greater than 32767 is stored as zero1 or as a negative number2. If the value is zero, see STMTNOI for the statement number. G
SECTNO

SMALLINT

NOT NULL

The section number of the statement.2 G
BINDERROR

CHAR(1)

NOT NULL

Whether an SQL error was detected at bind time:

N
No
Y
Yes
G
IBMREQD

CHAR(1)

NOT NULL

A value of Y indicates that the row came from the basic machine-readable material (MRM) tape. For all other values, see Release dependency indicators.

The value in this field is not a reliable indicator of release dependencies.

G
VERSION

VARCHAR(122)

NOT NULL

Version identifier for the package. G
 

VARCHAR(3500)

NOT NULL WITH

DEFAULT

FOR BIT DATA

Internal use only. I
ISOLATION

CHAR(1)

NOT NULL WITH

DEFAULT


Isolation level for the SQL statement:

R
RR (repeatable read)
T
RS (read stability)
S
CS (cursor stability)
U
UR (uncommitted read)
L
RS isolation, with a lock-clause
X
RR isolation, with a lock-clause
blank
The WITH clause was not specified on this statement. The isolation level is recorded in SYSPACKAGE.ISOLATION and in SYSPLAN.ISOLATION.

G
STATUS

CHAR(1)

NOT NULL WITH

DEFAULT

Status of binding the statement:

A
Distributed - statement uses DB2® private protocol access. The statement will be parsed and executed at the server using defaults for input variables during access path selection.
B
Distributed - statement uses DB2 private protocol access. The statement will be parsed and executed at the server using values for input variables during access path selection.
C
Compiled - statement was bound successfully using defaults for input variables during access path selection.
D
Distributed - statement references a remote object using a three-part name. DB2 will implicitly use DRDA® access either because the DBPROTOCOL bind option was not specified (defaults to DRDA), or the bind option DBPROTOCOL(DRDA) was explicitly specified. This option allows the use of three-part names with DRDA access but it requires that the package be bound at the target remote site.
E
Explain - statement is an SQL EXPLAIN statement. The explain is done at bind time using defaults for input variables during access path selection.
F
Parsed - statement did not bind successfully and VALIDATE(RUN) was used. The statement will be rebound at execution time using values for input variables during access path selection.
G
Compiled - statement bound successfully, but REOPT is specified. The statement will be rebound at execution time using values for input variables during access path selection.
H
Parsed - statement is either a data definition statement or a statement that did not bind successfully and VALIDATE(RUN) was used. The statement will be rebound at execution time using defaults for input variables during access path selection. Data manipulation statements use defaults for input variables during access path selection.
I
Indefinite - statement is dynamic. The statement will be bound at execution time using defaults for input variables during access path selection.
S
STATUS (cont.)  
J
Indefinite - statement is dynamic. The statement will be bound at execution time using values for input variables during access path selection.
K
Control - CALL statement.
L
Bad - the statement has some allowable error. The bind continues but the statement cannot be executed.
M
Parsed - statement references a table that is qualified with SESSION and was not bound because the table reference could be for a declared temporary table that will not be defined until the package or plan is run. The SQL statement will be rebound at execution time using values for input variables during access path selection.
O
Compiled for acceleration. The static query was bound successfully for acceleration and will be routed to an accelerator when executed.
blank
The statement is non-executable, or was bound in a DB2 release prior to Version 5.
 
ACCESSPATH

CHAR(1)

NOT NULL WITH

DEFAULT

For static statements, indicates if the access path for the statement is based on user-specified optimization hints:

H
Optimization hints were used.
A
The access path was reused because of the APREUSE bind option.
blank
One of the following situations:

  • The access path was determined without the use of hints, and a previous access path was not reused.
  • No access path is associated with the statement.
  • The statement is a dynamic SQL statement
G
STMTNOI

INTEGER

NOT NULL WITH

DEFAULT

If the value of STMTNO is zero, the column contains the statement number of the statement in the source program. If both STMTNO and STMTNOI are zero, the statement number is greater than 32767. G
SECTNOI

INTEGER

NOT NULL WITH

DEFAULT

The section number of the statement. G
EXPLAINABLE

CHAR(1)

NOT NULL WITH

DEFAULT

Contains one of the following values:

Y
Indicates that the SQL statement can be used with the EXPLAIN function and might have rows describing its access path in the owner.PLAN_TABLE.
N
Indicates that the SQL statement does not have any rows describing its access path in the owner.PLAN_TABLE.
blank
Indicates that the SQL statement was bound prior to Version 7.
G
QUERYNO

INTEGER

NOT NULL WITH

DEFAULT –1

The query number of the SQL statement in the source program. SQL statements bound prior to Version 7 have a default value of –1. Statements bound in Version 7 or later use the value specified on the QUERYNO clause on SELECT, UPDATE, INSERT, DELETE, EXPLAIN, DECLARE CURSOR, or REFRESH TABLE statements. If the QUERYNO clause is not specified, the query number is set to the statement number. G
ROWID

ROWID

NULL GENERATED

ALWAYS

ROWID column, created for the lob columns in this table. G
STMT_ID

BIGINT

NOT NULL

A unique statement identifier. G
STATEMENT

CLOB(2M)

NOT NULL

WITH DEFAULT

The complete text for the SQL statement that the row represents. G
 

BLOB(2M)

NOT NULL

WITH DEFAULT

Internal use only. I

1 Rows in which the value of SEQNO, STMTNO, and SECTNO are zero are for internal use.

2 To convert a negative STMTNO to a meaningful statement number that corresponds to your precompile output, add 65536 to it. For example, -26472 is equivalent to +39064 (-26472 + 65536).

时间: 2024-11-02 04:32:38

SYSIBM.SYSPACKSTMT db2 存储statement的表的相关文章

DB2中的系统表SYSIBM.SYSDUMMY1

ORACLE中有一张系统数据库表DUAL用来访问系统的相关信息 SELECT SYSDATE FROM DUAL;  --返回当前系统日期 ----------------------------------------------------------------------------------------- db2中的系统表为SYSIBM.SYSDUMMY1,不太好记 SELECT CURRENT DATE FROM SYSIBM.SYSDUMMY1  --返回当前系统日期SELECT

InnoDB存储引擎的表空间文件,重做日志文件

存储引擎文件:因为MySQL表存储引擎的关系,每个存储引擎都会有自己的文件来保存各种数据.这些存储引擎真正存储了数据和索引等数据. 表空间文件 InnoDB存储引擎在存储设计上模仿了Oracle,将存储的数据按表空间进行存放.默认配置下,会有一个初始化大小为10MB.名为ibdata1的文件.该文件就是默认的表空间文件(tablespace file).你可以通过参数innodb_data_file_path对其进行设置.格式如下: innodb_data_file_path=datafile_

动态分配存储的顺序表

/* * 动态分配存储的顺序表 */ #include <stdio.h> #include <stdlib.h> #define INIT_SIZE 100 #define EXPAND_SIZE 50 typedef int ElemType; typedef struct { ElemType *head; int len; // 顺序表当前元素个数 int size; // 顺序表当前最大容量 } Sqlist; int init_sqlist(Sqlist *list)

图的存储形式——邻接表

邻接表:邻接表是图的一种链式存储结构.在邻接表中,对图中每个顶点建立一个单链表,第i个单链表中的节点表示依附于顶点vi的边(对有向图是以顶点vi为尾的弧).每个结点有三个域组成,其中邻接点域指示与顶点vi邻接的点在途中的位置,链域指示下一条边或者弧的结点:数据域存储和边或者弧相关的信息,如权值等.每个链表上附设一个表头结点.在表头结点中,除了设置链域指向链表第一个结点之外,还设置有存储顶点vi的名.如下所示: 实现: /**************************************

浅谈MySql的存储引擎(表类型) (转)

什么是MySql数据库 通常意义上,数据库也就是数据的集合,具体到计算机上数据库可以是存储器上一些文件的集合或者一些内存数据的集合. 我们通常说的MySql数据库,sql server数据库等等其实是数据库管理系统,它们可以存储数据,并提供查询和更新数据库中的数据的功能等等.根据数据库如何存储数据和如何操作数据的实现机制不同,这些数据库之间即有区别又有共同点. MySql数据库是开放源代码的关系型数据库.目前,它可以提供的功能有:支持sql语言.子查询.存储过程.触发器.视图.索引.事务.锁.外

浅谈MySql的存储引擎(表类型)

来源:http://www.cnblogs.com/lina1006/archive/2011/04/29/2032894.html 什么是MySql数据库 通常意义上,数据库也就是数据的集合,具体到计算机上数据库可以是存储器上一些文件的集合或者一些内存数据的集合.    我们通常说的MySql数据库,sql server数据库等等其实是数据库管理系统,它们可以存储数据,并提供查询和更新数据库中的数据的功能等等.根据数据库如何存储数据和如何操作数据的实现机制不同,这些数据库之间即有区别又有共同点

MySQL InnoDB存储引擎之表(一)

主要介绍InnoDB存储引擎表的逻辑存储以及实现.重点介绍数据在表中是如何组织和存放的. 1.索引组织表(index organized table) 在InnoDB存储引擎中,表都是根据主键顺序组织存放的,这种存储方式的表叫索引组织表.在InnoDB存在引擎表中,每张表都有个主键(Primary key),如果在创建表时没有显示定义主键,则会按照如下方式选择或者创建主键:a.判定是否有非空的唯一索引(unique not null),如果有则该列即为主键.若果有多个,则选择建表是第一个定义的非

Atitit 数据存储的数据表连接attilax总结

1.1. 三种物理连接运算符:嵌套循环连接.合并连接以及哈希连接1 1.2. a.嵌套循环连接(nested loops join)1 1.3. b.合并连接(merge join)3 1.4. c.哈希连接(hash join) 4 1.5. 所以这三种算法,没有谁好谁坏,只有合适的场景应用合适的连接算法,这样才能发挥它自身的长处,而恰巧这些就是我们要掌握的技能.6 1.6. 这三种连接算法我们也可以显示的指定,loop merger hash6 1.7. 所有的最优计划的选择都是基于现有统计

python简单模拟:把树存储在数据表中

在数据库中建立一个表,有Id, fatherId, value 三个字段,就可以存储一个树. 如何把该表中的数据以树的形式呈现出来,下面小弟用python简单模拟一下. 初学python,请大家多多指点.另外非常感谢http://www.cnblogs.com/lzyzizi/对小弟的指点. 运行结果: A-1 B-1 C-1 D-1 E-1 E-2 C-2 B-2 C-3 C-4 源代码: 1 #!user/bin/python 2   3  class noteModel: 4 def __