Re: [David Kosenko: Re: turbo extents used]
Anbarnes@letterkenn-emh1.army.mil writes:
>Dave K writes in response to my request for help on determining how many
>extents are in use in Turbo 2.10.03G:
>>If the table is active (and you can make it active by going into isql and
>>issuing a LOCK TABLE statement), then tbstat -t will show the number of
>>extents allocated for the table (nextns). There is a trick, however, in that
>>tbstat shows the table with its tblspace number (partition number in Turbo
>>parlance) not the table name. To get a list of table names and their
>>respective (hex) partition/tblspace numbers, use the following query:
>>
>> select tabname, hex(partnum) from systables;>>>
>>Dave
>Good idea, and I had been told that before, but on our system that gives
>a syntax error. It doesnt like the hex word. We are running ISQL
>2.10.03G on a Unisys 5000. Is that a "bug?". Yes, we are on our way to
I *hate* when that happens! I can only assume that the hex() function was not
yet added in that version (I can't even check, as the version is so old).
The next best thing is to get the numbers out in decimal and convert them
to hex. I use the following little C program to do such conversions:
#include <stdio.h>
main(argc, argv)
int argc;
char *argv[];
{
long x;
if (argc<2) return(-1);
x = atoi(argv[1]);
printf("%x\\n", x);
}
Use the following SQL:
select tabname, partnum from systables;
>On-Line, but not until our application programmers get the application
>ready to go. The Unisys platform has only progressed to 4.1 that I am
>aware of, there is no 5.0 or 6.0 like all you Sun etc. types are longing
>for or even using. Yes, it is an "antique" platform, but we do the best
>we can with your tax dollars, and right now that doesnt include new
>hardware. Is there any further assistance on the problem of hex(partnum)
>or how to tell what extents are being used? Thank you for your responses.
Well, looking at my "witholdings", you should have enough tax $$ to buy
some new equipment in 93 ;-). If the above suggestion doesn't do it for
you, you could do the following iterative operations:
1. Do a tbstat -t. Note the partnums of all the tblspaces.
2. STart up isql and select your database. tbstat -t again and note any
new partnums (I don't think there will be any, but just to be safe).
3. LOCK TABLE tabname IN EXCLUSIVE MODE. tbstat -t and look for the new
active tblspace. It will be the table you just locked. Check the
nextns file for the number of extents.
>PS: Dave K, I cannot seem to succesfully e-mail to you. My phone is
>717-267-9869. Please call re: ISAM info you wrote about. Thanks.
I have received at least 2 emails from you, to which I have responded.
Look to the U.S.Mail for an envelope from me.
Dave
--
Disclaimer: These opinions are not those of Informix Software, Inc.
**************************************************************************
"I look back with some satisfaction on what an idiot I was when I was 25,
but when I do that, I'm assuming I'm no longer an idiot." - Andy Rooney