Partitions numbers at beginning of onstat -g ppf

2. RE: Partitions numbers at beginning of onstat -g ppf

Like

SangGyu Jeong

Posted Thu March 26, 2020 08:40 PM
Edited by System Admin Fri January 20, 2023 04:37 PM

Hi Jacob,

I stumbled across iiug presentations in 2019 and came across
On versions 14.10.xC2 and 12.10.xc14 and above, onstat -g ppf shows the name corresponding to the "low" partition number. Is this what you are looking for?
I don't know how to get this information under version 12.10.xC14.

IBM Informix Dynamic Server Version 12.10.FC14 -- On-Line -- Up 7 days 22:37:09 -- 358208 Kbytes

Partition profiles
partnum    lkrqs   lkwts dlks  touts isrd   iswrt isrwt isdel bfrd    bfwrt seqsc rhitratio name
0x1        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysrawdsk
0x2        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.syspaghdr
0x3        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysslttab
0x4        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.syssltdat
0x5        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.syschfree
0x6        0       0     0     0     9      0     0     0     0       0     0     0         sysmaster:informix.syscfgtab
0x7        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.syssymtab
0x8        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysproftab
0xa        0       0     0     0     7027   0     0     0     5171    0     0     92        sysmaster:informix.sysptnhdr
0xb        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysptnkey
0xc        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysptnext
0xd        0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysptncol
0xe        0       0     0     0     112366 0     0     0     1787    0     0     100       sysmaster:informix.sysptnbit
0xf        0       0     0     0     655    0     0     0     9       0     0     67        sysmaster:informix.systabnames
...
0x90       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.syscluster
0x91       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysaqt
0x92       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysaqtjp
0x93       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.syscdrrecvqprog
0x94       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysprobetables
0x95       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysprobecolumns
0x96       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysprobejds
0x97       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.sysprobejps
0x98       0       0     0     0     0      0     0     0     0       0     0     0         sysmaster:informix.syscdrtsapply
0x99       0       0     0     0     2598   0     0     0     0       0     0     0         sysmaster:informix.sysiohistory
0x401      0       0     0     0     0      0     0     0     0       0     0     0         Pseudo Table
0x402      0       0     0     0     0      0     0     0     0       0     0     0         Pseudo Table
0x403      0       0     0     0     0      0     0     0     0       0     0     0         Pseudo Table
0x404      0       0     0     0     0      0     0     0     0       0     0     0         Pseudo Table

------------------------------
SangGyu Jeong
Software Engineer
Infrasoft
Seoul Korea, Republic of
------------------------------

Original Message

Original Message:
Sent: Thu March 26, 2020 06:43 PM
From: Jacob Salomon
Subject: Partitions numbers at beginning of onstat -g ppf

Hi folks

This is a completely non-critical question, of no consequences to my current client. But the curiosity is just nagging at me!

Consider the following query on sysmaster:systabnames:

select hex(partnum) partition,
dbsname[1,18], owner[1,18], tabname[1,18]
from systabnames
order by 1

The first few lines are:
partition dbsname owner tabname

0x00100001 rootdbs informix TBLSpace
0x00100002 sysmaster informix sysdatabases
0x00100003 system informix syslicenseinfo
0x00100004 sysmaster informix systables
0x00100005 sysmaster informix syscolumns
0x00100006 sysmaster informix sysindices
0x00100007 sysmaster informix systabauth

So the lowest partition number in the server is 0x100001. I get the same lowest partnum if I select directly from systabinfo or a similar query on sysptprof, supposedly the SMI equivalent of onstat -g ppf:
select hex(partnum) partition, dbsname[1,18], tabname[1,18] from sysptprof order by 1

Now let's look at partition profiles as shown in onstat -g ppf:
onstat -g ppf | tail -n +4|

Partition profiles

partnum lkrqs lkwts dlks touts isrd iswrt isrwt isdel bfrd bfwrt seqsc rhitratio
0x1 0 0 0 0 0 0 0 0 0 0 0 0
0x2 0 0 0 0 0 0 0 0 0 0 0 0
0x3 0 0 0 0 0 0 0 0 0 0 0 0
0x4 0 0 0 0 0 0 0 0 0 0 0 0
0x5 0 0 0 0 0 0 0 0 0 0 0 0
0x6 0 0 0 0 32489 0 0 0 0 0 0 0
0x7 0 0 0 0 0 0 0 0 0 0 0 0
0x8 0 0 0 0 0 0 0 0 0 0 0 0
0xa 0 0 0 0 4421206 0 0 0 28809459 0 0 100
0xb 0 0 0 0 0 0 0 0 0 0 0 0
...
0x401 0 0 0 0 0 0 0 0 0 0 0 0
0x402 0 0 0 0 0 155 0 0 0 0 0 0
0x403 0 0 0 0 67557 0 0 0 0 0 0 0
0x404 0 0 0 0 0 0 0 0 0 0 0 0
0x100001 0 0 0 0 0 0 0 0 2445398 0 0 100
0x100002 4216078 0 0 0 1250981 0 0 0 5020867 0 3130 100
0x100003 0 0 0 0 0 0 0 0 16 0 0 100
0x100004 4651508 0 0 0 2512432 0 0 0 5862436 0 5 100
0x100005 1472 0 0 0 674 0 0 0 1690 0 0 100
0x100006 33 0 0 0 15 0 0 0 111 0 0 100
0x100007 259 0 0 0 149 0 0 0 405 0 0 100

Y'know, our code-formatter does an AWFUL job maintaining spacing :-(
In any case, you can see partitions listed with VERY low values, 0x1 through 0x404; these are listed before the very first actual partition, the TBLspace TBLspace's own entry within itself.

So what *are* those low partition numbers?

It has been said that curiosity has been implicated in the demise of the feline. I'll risk it fro now. :-)

Ideas, anyone?

------------------------------
Jacob Salomon
---
Nobody goes there anymore, it's too crowded. --Attr: Yogi Berra
------------------------------
#Informix

5. RE: Partitions numbers at beginning of onstat -g ppf

Like

Andreas Legner

IBM Champion

Posted Fri March 27, 2020 04:27 AM

select hex(partnum),tabname from sysmaster:systables where partnum > 0 and partnum < "0x100000";

In other words: these are, and always were, your SMI pseudo tables.
Look at $INFORMIXDIR/etc/sysmaster.sql for some of this magic.

------------------------------
Andreas Legner
------------------------------

Original Message

Original Message:
Sent: Thu March 26, 2020 06:43 PM
From: Jacob Salomon
Subject: Partitions numbers at beginning of onstat -g ppf

Hi folks

This is a completely non-critical question, of no consequences to my current client. But the curiosity is just nagging at me!

Consider the following query on sysmaster:systabnames:

select hex(partnum) partition,
dbsname[1,18], owner[1,18], tabname[1,18]
from systabnames
order by 1

The first few lines are:
partition dbsname owner tabname

0x00100001 rootdbs informix TBLSpace
0x00100002 sysmaster informix sysdatabases
0x00100003 system informix syslicenseinfo
0x00100004 sysmaster informix systables
0x00100005 sysmaster informix syscolumns
0x00100006 sysmaster informix sysindices
0x00100007 sysmaster informix systabauth

So the lowest partition number in the server is 0x100001. I get the same lowest partnum if I select directly from systabinfo or a similar query on sysptprof, supposedly the SMI equivalent of onstat -g ppf:
select hex(partnum) partition, dbsname[1,18], tabname[1,18] from sysptprof order by 1

Now let's look at partition profiles as shown in onstat -g ppf:
onstat -g ppf | tail -n +4|

Partition profiles

partnum lkrqs lkwts dlks touts isrd iswrt isrwt isdel bfrd bfwrt seqsc rhitratio
0x1 0 0 0 0 0 0 0 0 0 0 0 0
0x2 0 0 0 0 0 0 0 0 0 0 0 0
0x3 0 0 0 0 0 0 0 0 0 0 0 0
0x4 0 0 0 0 0 0 0 0 0 0 0 0
0x5 0 0 0 0 0 0 0 0 0 0 0 0
0x6 0 0 0 0 32489 0 0 0 0 0 0 0
0x7 0 0 0 0 0 0 0 0 0 0 0 0
0x8 0 0 0 0 0 0 0 0 0 0 0 0
0xa 0 0 0 0 4421206 0 0 0 28809459 0 0 100
0xb 0 0 0 0 0 0 0 0 0 0 0 0
...
0x401 0 0 0 0 0 0 0 0 0 0 0 0
0x402 0 0 0 0 0 155 0 0 0 0 0 0
0x403 0 0 0 0 67557 0 0 0 0 0 0 0
0x404 0 0 0 0 0 0 0 0 0 0 0 0
0x100001 0 0 0 0 0 0 0 0 2445398 0 0 100
0x100002 4216078 0 0 0 1250981 0 0 0 5020867 0 3130 100
0x100003 0 0 0 0 0 0 0 0 16 0 0 100
0x100004 4651508 0 0 0 2512432 0 0 0 5862436 0 5 100
0x100005 1472 0 0 0 674 0 0 0 1690 0 0 100
0x100006 33 0 0 0 15 0 0 0 111 0 0 100
0x100007 259 0 0 0 149 0 0 0 405 0 0 100

Y'know, our code-formatter does an AWFUL job maintaining spacing :-(
In any case, you can see partitions listed with VERY low values, 0x1 through 0x404; these are listed before the very first actual partition, the TBLspace TBLspace's own entry within itself.

So what *are* those low partition numbers?

It has been said that curiosity has been implicated in the demise of the feline. I'll risk it fro now. :-)

Ideas, anyone?

------------------------------
Jacob Salomon
---
Nobody goes there anymore, it's too crowded. --Attr: Yogi Berra
------------------------------

#Informix

6. RE: Partitions numbers at beginning of onstat -g ppf

Like

Art Kagel

IBM Champion

Posted Fri March 27, 2020 06:41 AM

Jacob:

The reserved pages don't have "partition" numbers and those are the pages preceding partition 0x00100001

Art S. Kagel, President and Principal Consultant

ASK Database Management

www.askdbmgt.com

Blog: http://informix-myview.blogspot.com/

Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.

Original Message

Original Message------

Hi folks

This is a completely non-critical question, of no consequences to my current client. But the curiosity is just nagging at me!

Consider the following query on sysmaster:systabnames:

select hex(partnum) partition,
dbsname[1,18], owner[1,18], tabname[1,18]
from systabnames
order by 1

The first few lines are:
partition dbsname owner tabname

0x00100001 rootdbs informix TBLSpace
0x00100002 sysmaster informix sysdatabases
0x00100003 system informix syslicenseinfo
0x00100004 sysmaster informix systables
0x00100005 sysmaster informix syscolumns
0x00100006 sysmaster informix sysindices
0x00100007 sysmaster informix systabauth

So the lowest partition number in the server is 0x100001. I get the same lowest partnum if I select directly from systabinfo or a similar query on sysptprof, supposedly the SMI equivalent of onstat -g ppf:
select hex(partnum) partition, dbsname[1,18], tabname[1,18] from sysptprof order by 1

Now let's look at partition profiles as shown in onstat -g ppf:
onstat -g ppf | tail -n +4|

Partition profiles

partnum lkrqs lkwts dlks touts isrd iswrt isrwt isdel bfrd bfwrt seqsc rhitratio
0x1 0 0 0 0 0 0 0 0 0 0 0 0
0x2 0 0 0 0 0 0 0 0 0 0 0 0
0x3 0 0 0 0 0 0 0 0 0 0 0 0
0x4 0 0 0 0 0 0 0 0 0 0 0 0
0x5 0 0 0 0 0 0 0 0 0 0 0 0
0x6 0 0 0 0 32489 0 0 0 0 0 0 0
0x7 0 0 0 0 0 0 0 0 0 0 0 0
0x8 0 0 0 0 0 0 0 0 0 0 0 0
0xa 0 0 0 0 4421206 0 0 0 28809459 0 0 100
0xb 0 0 0 0 0 0 0 0 0 0 0 0
...
0x401 0 0 0 0 0 0 0 0 0 0 0 0
0x402 0 0 0 0 0 155 0 0 0 0 0 0
0x403 0 0 0 0 67557 0 0 0 0 0 0 0
0x404 0 0 0 0 0 0 0 0 0 0 0 0
0x100001 0 0 0 0 0 0 0 0 2445398 0 0 100
0x100002 4216078 0 0 0 1250981 0 0 0 5020867 0 3130 100
0x100003 0 0 0 0 0 0 0 0 16 0 0 100
0x100004 4651508 0 0 0 2512432 0 0 0 5862436 0 5 100
0x100005 1472 0 0 0 674 0 0 0 1690 0 0 100
0x100006 33 0 0 0 15 0 0 0 111 0 0 100
0x100007 259 0 0 0 149 0 0 0 405 0 0 100

Y'know, our code-formatter does an AWFUL job maintaining spacing :-(
In any case, you can see partitions listed with VERY low values, 0x1 through 0x404; these are listed before the very first actual partition, the TBLspace TBLspace's own entry within itself.

So what *are* those low partition numbers?

It has been said that curiosity has been implicated in the demise of the feline. I'll risk it fro now. :-)

Ideas, anyone?

------------------------------
Jacob Salomon
---
Nobody goes there anymore, it's too crowded. --Attr: Yogi Berra
------------------------------

#Informix

Informix

Informix