By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,557 Members | 1,067 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,557 IT Pros & Developers. It's quick & easy.

SQL/PL Stored Procedures and SYSIBM.SYSDUMMY1

P: n/a
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
Share this Question
Share on Google+
1 Reply


P: n/a
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.