Hi everybody,
Something about the temporary ( dbspace ) ( tables ) always fasinates me. I
have more questions. I was monitoring the progress of a temporary table created
by a process, and here's what I found.
1. If the process creates a temporary table with logging, ( say select *
from tab1 into temp tmptab1 ) then you can get the exact number of rows
read/written/updated by the SYSPTPROF view ( isreads, iswrites and isrewrites )
in the sysmaster database. You also get only ONE row in the sysptprof with the
partnum the same as specified in the onstat -g ses output
BUT
2. If the process creates a temporary with NO LOG , then we get two rows in
SYSPTPROF ( ie two rows in systabnames ), but different partnum , and neither of
the partnum(s) match what is shown in the onstat -g ses. Morover, the isreads,
iswrites and isrewrites in the sysptprof have no connection to the actual number
of rows read/written/updated.
Does anybody know what is going on ?? How do I follow the progress of a
temporary table. On the same note, if we use sysptprof to follow the progress of
permanent tables, would it be accurate ( albeit a little off by time ). I do
know that onperf reports a more accurate count.
Any suggestions ??
Thanks
Sujata
********************************************************************************
******************************
* Sujata Soman
*
* E-Mail: ssoman@omm.com
*
* Database Administrator ( Informix )
*
* O'Melveny & Myers, Los Angeles
*
********************************************************************************
******************************