Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Identifying tables in Load Pending state

2,691 views
Skip to first unread message

Troels Arvin

unread,
Jan 29, 2011, 2:47:21 AM1/29/11
to
Hello,

Is there a way to get a list of tables being in the "Load Pending" state?

syscat.table's status and access_mode columns don't seem to be useful for
this (I just compared the values of these for a table in normal state and
in Load Pending state).

--
Troels

Lennart Jonsson

unread,
Jan 29, 2011, 3:34:40 AM1/29/11
to

I think you can use SYSIBMADM.ADMINTABINFO.load_status for this, if I
remember correctly the value is 'PENDING'


/Lennart

The Boss

unread,
Jan 29, 2011, 6:15:29 AM1/29/11
to
On Jan 29, 9:34 am, Lennart Jonsson <erik.lennart.jons...@gmail.com>
wrote:

That's correct, following query will show tables in "Load Pending"
state:
db2 "select tabschema, tabname from SYSIBMADM.ADMINTABINFO where
load_status = 'PENDING'"

--
Jeroen

Troels Arvin

unread,
Jan 30, 2011, 4:49:27 PM1/30/11
to
Hello,

Lennart Jonsson wrote:
> I think you can use SYSIBMADM.ADMINTABINFO.load_status for this, if I
> remember correctly the value is 'PENDING'

Thanks (and thanks to "The Boss", as well).

However, queries in SYSIBMADM.ADMINTABINFO are surprisingly slow.
Like in http://groups.google.com/group/comp.databases.ibm-db2/
browse_thread/thread/1f19045b8def6812/61edbc947b7e1ad1 I suspect that
queries in SYSIBMADM.ADMINTABINFO triggers I/O in all involved tables.

I wish IBM would re-consider table availability instrumentation aiming at
making it more useful, i.e. realistic to use for regular monitoring.

--
Troels

The Boss

unread,
Jan 31, 2011, 10:28:38 AM1/31/11
to
On Jan 30, 10:49 pm, Troels Arvin <tro...@arvin.dk> wrote:
> Hello,
>
> Lennart Jonsson wrote:
> > I think you can use SYSIBMADM.ADMINTABINFO.load_status for this, if I
> > remember correctly the value is 'PENDING'
>
> Thanks (and thanks to "The Boss", as well).
>
> However, queries in SYSIBMADM.ADMINTABINFO are surprisingly slow.
> Like inhttp://groups.google.com/group/comp.databases.ibm-db2/

> browse_thread/thread/1f19045b8def6812/61edbc947b7e1ad1 I suspect that
> queries in SYSIBMADM.ADMINTABINFO triggers I/O in all involved tables.
>
> I wish IBM would re-consider table availability instrumentation aiming at
> making it more useful, i.e. realistic to use for regular monitoring.
>

(You probably already considered this, but just to be sure)
If you suspect a specific table (or a limited number of them) you
could use LOAD QUERY like explained here:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0002000.html

Useful for adhoc situations, not so for regular monitoring of more
than a few tables.

--
Jeroen

0 new messages