Re: Not using the new parameters in V10.0 upgrade.

minnickbrian@aol.com said: > > I've just inherited a system that has been recently upgraded from V9.21 > to V10.0. When they performed the upgrade, they just used the old > onconfig file and did not use the new BUFFERPOOL or BTSCANNER > parmeters. It seems to be working so far, but does anyone know if this > will cause problems? I'd be amazed if it caused any actual problems. You might not be getting full value, but that's about it. -- Bye now, Obnoxio "C'est pas parce qu'on n'a rien ` dire qu'il faut fermer sa gueule" - Coluche did i mention i like nulls? heck, i even go so far as to say that all columns in a table except the primary key could/should be nullable. this has certain advantages, for example, if you need to insert a child record and you don't have a parent row for it, just do an insert into the parent table with the primary key value (everything else null), and voila, relational integrity is preserved. but this is, admittedly, a bit controversial among modellers. --r937, dbforums.com sending to informix-list

Yes - I'd run some onstat's and check what the parameters have defaulted to. - I assume since you still use the BUFFERS line that you are just using the default page size for your platform. Check IDS didn't rewrite the onconfig as part of the upgrade - I thought BUFFERS was gone with IDS 10. - Use onstat -C to check what the BTSCANNER values have defaulted to. I would schedule time to upgrade the ONCONFIG file to explictly state what these parameters are set to. You don't want to upgrade to IDS.next whenever it arrives, find the defaults have changed and wonder what happened. REMEMBER IT'S BEST TO BE EXPLICIT ABOUT EVERYTHING!