Informix 9.4 expanded chunk size is disabled?

I had expanded chunks with IDS 9.4UC2. I upgraded to IDS 9.4UC5 and when I tried to use onmonitor to add a chunk larger than 2gig it barked. Yet all of my existing chunks are greater than 2gig. I search google and found mention to onmode -B 1 or 2. This is not working on my version. It wants onmode -BC 1 or 2. But what do I do to make this default to always on? I chickened out on onmode -BC 2 here's what it prompted: onmode -BC 1This command will enable creation of large chunks. ** WARNING ** This action cannot be undone. ** WARNING ** A level 0 archive of Root DBSpace will need to be done. Do you wish to continue (y/n)? y Expanded chunk capacity mode: enabled onmode -BC 2This command will cause all chunks to be written in the new (big) format. ** WARNING ** This action cannot be undone. ** WARNING ** A level 0 archive of Root DBSpace will need to be done. Do you wish to continue (y/n)? n quitting... Thanks Gary Quiring

"Gary Quiring" <gquiring@msn.com> wrote in message news:pdtmp0hdqs8kl4hqko96f56jet60rn90bc@4ax.com... >I had expanded chunks with IDS 9.4UC2. I upgraded to IDS 9.4UC5 and when I > tried to use onmonitor to add a chunk larger than 2gig it barked. Yet all > of my > existing chunks are greater than 2gig. > > I search google and found mention to onmode -B 1 or 2. This is not > working on > my version. It wants onmode -BC 1 or 2. But what do I do to make this > default > to always on? I chickened out on onmode -BC 2 here's what it prompted: > > onmode -BC 1> This command will enable creation of large chunks. > ** WARNING ** This action cannot be undone. > ** WARNING ** A level 0 archive of Root DBSpace will need to be done. > Do you wish to continue (y/n)? y > > Expanded chunk capacity mode: enabled > onmode -BC 2> This command will cause all chunks to be written in the new (big) format. > ** WARNING ** This action cannot be undone. > ** WARNING ** A level 0 archive of Root DBSpace will need to be done. > Do you wish to continue (y/n)? n > quitting... Have I missed something here? The change, as it says above, is irreversible. So to make it the default, run it.

On Wed, 17 Nov 2004 16:34:29 -0000, "Neil Truby" <neil.truby@ardenta.com> wrote: >"Gary Quiring" <gquiring@msn.com> wrote in message >news:pdtmp0hdqs8kl4hqko96f56jet60rn90bc@4ax.com... >>I had expanded chunks with IDS 9.4UC2. I upgraded to IDS 9.4UC5 and when I >> tried to use onmonitor to add a chunk larger than 2gig it barked. Yet all >> of my >> existing chunks are greater than 2gig. >> >> I search google and found mention to onmode -B 1 or 2. This is not >> working on >> my version. It wants onmode -BC 1 or 2. But what do I do to make this >> default >> to always on? I chickened out on onmode -BC 2 here's what it prompted: >> >> onmode -BC 1>> This command will enable creation of large chunks. >> ** WARNING ** This action cannot be undone. >> ** WARNING ** A level 0 archive of Root DBSpace will need to be done. >> Do you wish to continue (y/n)? y >> >> Expanded chunk capacity mode: enabled >> onmode -BC 2>> This command will cause all chunks to be written in the new (big) format. >> ** WARNING ** This action cannot be undone. >> ** WARNING ** A level 0 archive of Root DBSpace will need to be done. >> Do you wish to continue (y/n)? n >> quitting... > >Have I missed something here? The change, as it says above, is >irreversible. >So to make it the default, run it. > I guess what I don't understand is I already have big chunks. Why would it need to write them in a 'new big' format?

"Gary Quiring" <gquiring@msn.com> wrote in message news:n06np05dn3jo1kfnq2fa9dkqq5cdt4tjsd@4ax.com... > On Wed, 17 Nov 2004 16:34:29 -0000, "Neil Truby" <neil.truby@ardenta.com> wrote: > > >"Gary Quiring" <gquiring@msn.com> wrote in message > >news:pdtmp0hdqs8kl4hqko96f56jet60rn90bc@4ax.com... > >>I had expanded chunks with IDS 9.4UC2. I upgraded to IDS 9.4UC5 and when I > >> tried to use onmonitor to add a chunk larger than 2gig it barked. Yet all > >> of my > >> existing chunks are greater than 2gig. > >> > >> I search google and found mention to onmode -B 1 or 2. This is not > >> working on > >> my version. It wants onmode -BC 1 or 2. But what do I do to make this > >> default > >> to always on? I chickened out on onmode -BC 2 here's what it prompted: > >> > >> onmode -BC 1> >> This command will enable creation of large chunks. > >> ** WARNING ** This action cannot be undone. > >> ** WARNING ** A level 0 archive of Root DBSpace will need to be done. > >> Do you wish to continue (y/n)? y > >> > >> Expanded chunk capacity mode: enabled > >> onmode -BC 2> >> This command will cause all chunks to be written in the new (big) format. > >> ** WARNING ** This action cannot be undone. > >> ** WARNING ** A level 0 archive of Root DBSpace will need to be done. > >> Do you wish to continue (y/n)? n > >> quitting... > > > >Have I missed something here? The change, as it says above, is > >irreversible. > >So to make it the default, run it. > > > I guess what I don't understand is I already have big chunks. Why would it need > to write them in a 'new big' format? > Larger than 2G on what platform? >

Hi Gary What does the ouptut of onstat -d say for IDS 9.4UC5? After doing a onmode -BC 1 it gives Expanded chunk capacity mode: enabled Which mean adding new dbspaces of greater that 2Gig is allowed and has the new big format and any old dbspaces upto 2 gig will have the old format onmode -BC 2 gives Expanded chunk capacity mode: always Coverts all the dbspaces to new big format including the "old" dbspaces and any new spaces have new the new big format. I think the reason for this was to do with if you want to downgrade your IDS version. Not really sure if I am answering your question. Hopefully not teaching Grandmother to suck eggs:-) Do you have an output of the "onstat -d" for 9.40UC2 version. Traveller

On Thu, 18 Nov 2004 02:41:55 GMT, "Madison Pruet" <mpruet@comcast.net> wrote: >> >Larger than 2G on what platform? > Sun Solaris 9 on a 880 using Veritas Volume Manager. The confusion is I loaded the server with 9.4UC2. I setup large chunks (50gig each) and never used onmode -BC. I knew that onstat -d showed that large chunks were disabled in UC2 and I never understood why since I was able to setup large chunks. When I upgraded to UC5 last week it changed onmonitor. Now I could not add a chunk over 2gig. I got a nice email from IBM explaining what they did and why. So I am not confused anymore, just pointing out that they changed the default from UC2 to UC5. Gary Quiring