Identifying dbspaces with auto-chunk addition

Hi all, Does anyone know if there is a way through the system monitoring interface, i.e. an SQL statement run against sysmaster, of determining if a dbspace can add new chunks from the storagepool? There appears to be nothing in sysdbspaces or syschunks. With 'onstat -d' this is easy and indicated by an 'A' in the fifth position of the dbspace flags. Ben.

sysdbspaces.create=5Fsize or extend=5Fsize being non-zero results in that '= A'=20 flag. From: "BENJAMIN THOMPSON" <benjamin.thompson@skybettingandgaming.com> To: ids@iiug.org Date: 10.02.2017 16:43 Subject: Identifying dbspaces with auto-chunk addition [38624] Sent by: ids-bounces@iiug.org Hi all,=20 Does anyone know if there is a way through the system monitoring=20 interface,=20 i.e. an SQL statement run against sysmaster, of determining if a dbspace=20 can=20 add new chunks from the storagepool? There appears to be nothing in=20 sysdbspaces or syschunks.=20 With 'onstat -d' this is easy and indicated by an 'A' in the fifth=20 position of=20 the dbspace flags.=20 Ben.=20 ***************************************************************************= ****=20 Forum Note: Use "Reply" to post a response in the discussion forum.=20

Hi Andreas, Thanks for your reply and to someone else who replied privately. Just to be clear we are not using expandable chunks; we only allow new chunks to be added to a dbspace from the storagepool. We have some new build systems where create_size>0 or extend_size>0 in the sysdbspaces table matches the 'A' flag from 'onstat -d' but others where it does not. All the systems where there is a mismatch have no storagepool and were migrated from version 11.50. 'onstat -d' shows in these nothing is expandable (chunks or dbspaces) but create_size=10 and extend_size=10000 are shown for all dbspaces in sysdbspaces. Is this a bug perhaps? This matters because we are trying to write a reliable monitoring script that works on all our servers. Ben.