467,114 Members | 1,338 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,114 developers. It's quick & easy.

SQL/PL Stored Procedures and SYSIBM.SYSDUMMY1

Hi - a straight-forward question for which I would be grateful for an
explanation.

Why are ALL SQL/PL Stored Procedures associated with SYSIBM.SYSDUMMY1
even though the latter is NOT directly accessed via SQL within the SP?

Both an Explain against the Plan_Table and SYSPACKDEP state that the
Table is used.
From the Plan_Table:-

- Lock Mode: UR Isolation
- Access: Sequential Scan / No Index.

Thanks

Mar 24 '06 #1
  • viewed: 1928
Share:
1 Reply
al**********@btinternet.com wrote:
Hi - a straight-forward question for which I would be grateful for an
explanation.

Why are ALL SQL/PL Stored Procedures associated with SYSIBM.SYSDUMMY1
even though the latter is NOT directly accessed via SQL within the SP?

Both an Explain against the Plan_Table and SYSPACKDEP state that the
Table is used.
From the Plan_Table:-

- Lock Mode: UR Isolation
- Access: Sequential Scan / No Index.

The SQL Procedure is doing some basic house-keeping which is done using
SQL Statements.
Keep in mind that SYSIBM.SYSDUMMY1 is just a VIEW over VALUES('Y').
None of these statements ever does an I/O or as much as hit the buffer pool.
There may be some fat in there to reduce basic CPU cycles for trivial
procedures, but that's about it.

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Mar 24 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Peter Arrenbrecht Opus | last post: by
9 posts views Thread by Raquel | last post: by
5 posts views Thread by Mike Gemmell | last post: by
5 posts views Thread by PJackson@txfb-ins.com | last post: by
reply views Thread by a573851 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.