sysmaster schema in IDS 9.4F5XF

hi.. we have upgraded informix from 7.31.FD2 to 9.4F5XF. Later we found that some tables in sysmaster database in new version are different that the earlier ones. what could be the reasons for it?

On 16/10/2007, VARTIKA AGRAWAL <vartika_agrawal@ril.com> wrote: > hi.. > > we have upgraded informix from 7.31.FD2 to 9.4F5XF. Later we found that some > tables in sysmaster database in new version are different that the earlier > ones. what could be the reasons for it? > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > You've upgraded the engine, what more did you expect !! sysmaster is a set of pseudo tables looking at the shared memory structures. These would have changed significantly between 7 and 9 therefore the systmaster tables would change. Part of the upgrade is to destroy and rebuild the sysmaster database in its entrety. Keith

Thanks, what i meant was the difference in table structure (in sysmaster database) ... look at systabextents - in 9.4 Column name Type Nulls te_partnum integer yes te_extnum smallint yes te_chunk integer yes te_offset integer yes te_size integer yes te_pagenum integer yes in 7.3 Column name Type Nulls te_partnum integer yes te_extnum smallint yes te_physaddr integer yes te_size integer yes te_pagenum integer yes 2. syslocktab in 9.4 Column name Type Nulls lk_id integer yes lk_addr int8 yes lk_same int8 yes lk_wtlist int8 yes lk_owner int8 yes lk_list int8 yes lk_type smallint yes lk_flags smallint yes lk_bsize smallint yes lk_keynum smallint yes lk_rowid integer yes lk_partnum integer yes lk_kvobj integer yes lk_dipnum integer yes lk_grtime integer yes in 7.3 Column name Type Nulls lk_id integer yes lk_addr integer yes lk_addrpad integer yes lk_same integer yes lk_samepad integer yes lk_wtlist integer yes lk_wtlistpad integer yes lk_owner integer yes lk_ownerpad integer yes lk_list integer yes lk_listpad integer yes lk_type smallint yes lk_flags smallint yes lk_bsize smallint yes lk_keynum smallint yes lk_rowid integer yes lk_partnum integer yes lk_kvobj integer yes lk_dipnum integer yes lk_grtime integer yes kindly explain.

Since 9.40+ supports chunk sizes larger than 2GB many internal addresses had to change. Any physical page addressing became 2 integers rather than one. Art S. Kagel ----- Original Message ----- From: Vartika Agrawal <ids@iiug.org> To: ids@iiug.org At: 10/16 8:29:12 Thanks, what i meant was the difference in table structure (in sysmaster database) ... look at systabextents - in 9.4 Column name Type Nulls te_partnum integer yes te_extnum smallint yes te_chunk integer yes te_offset integer yes te_size integer yes te_pagenum integer yes in 7.3 Column name Type Nulls te_partnum integer yes te_extnum smallint yes te_physaddr integer yes te_size integer yes te_pagenum integer yes 2. syslocktab in 9.4 Column name Type Nulls lk_id integer yes lk_addr int8 yes lk_same int8 yes lk_wtlist int8 yes lk_owner int8 yes lk_list int8 yes lk_type smallint yes lk_flags smallint yes lk_bsize smallint yes lk_keynum smallint yes lk_rowid integer yes lk_partnum integer yes lk_kvobj integer yes lk_dipnum integer yes lk_grtime integer yes in 7.3 Column name Type Nulls lk_id integer yes lk_addr integer yes lk_addrpad integer yes lk_same integer yes lk_samepad integer yes lk_wtlist integer yes lk_wtlistpad integer yes lk_owner integer yes lk_ownerpad integer yes lk_list integer yes lk_listpad integer yes lk_type smallint yes lk_flags smallint yes lk_bsize smallint yes lk_keynum smallint yes lk_rowid integer yes lk_partnum integer yes lk_kvobj integer yes lk_dipnum integer yes lk_grtime integer yes kindly explain. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.