Getting around 8 partitions or 2 GIG Chunks
Posted in 1999
Topics: Storage & Space Management, Platform-Specific Issues
So what is the answer to having a large database? Is it hardware or are we not limited to only 8 partitions as Solaris says because then one would be limited to a 16 GIG Database server and that is small. marie At 01:15 AM 8/15/99 +0100, you wrote: >The rule that you are most likely to fall foul of is that the chunksize + >offset must be less than 2GBytes. So, if you have only two chunks, you are >limited to a 4GByte database server. > >Better get that sys admin manual out ....! > >Neil Truby >Londis Stores >Hampton Hill, UK > >Marie Usher wrote in message <7p4m8v$99u$1@news.xmission.com>... >> >>I have a database that i need to reorganize on 2 very large raw chunks. >>Presently the >>database is spread over 9 chunks. What is the concept using offset. How >>do i know where to start another dbspace. Is there a rule? >> >>marie >> >
For a large database, it is suggested that you spread the dbspaces over several disks (and preferably controllers as well), so it would be recommended that you have as many disk drives as possible - for a 16 GB database (especially if you use mirroring as well), I would want at least four separate drives. We always prefer many smaller drives (it is getting more difficult to find "small" drives any more!) to a few large drives... The chunksize+offset < 2GB is true unless you are on a native 64-bit platform (like Solaris 7 if you turn it on) and your Informix software is also the 64-bit version (I am not sure if this is available yet - it was not available about 10 months ago - we went with the 32-bit version although we have several Solaris 7 sites we support...). The short answer to having a large database (per your definition&question below) is then hardware (more disk drives). Hal Marie Usher wrote in message <7p6lhu$j3$1@news.xmission.com>... > > >So what is the answer to having a large database? Is it hardware or are we >not limited to only 8 partitions as Solaris says because then one would be >limited to a 16 GIG Database server and that is small. > >marie >At 01:15 AM 8/15/99 +0100, you wrote: >>The rule that you are most likely to fall foul of is that the chunksize + >>offset must be less than 2GBytes. So, if you have only two chunks, you are >>limited to a 4GByte database server. >> >>Better get that sys admin manual out ....! >> >>Neil Truby >>Londis Stores >>Hampton Hill, UK >> >>Marie Usher wrote in message <7p4m8v$99u$1@news.xmission.com>... >>> >>>I have a database that i need to reorganize on 2 very large raw chunks. >>>Presently the >>>database is spread over 9 chunks. What is the concept using offset. How >>>do i know where to start another dbspace. Is there a rule? >>> >>>marie >>> >> >
You have to get a volume manager. Sun resells the Veritas VM, though it is usually a few versions behind Veritas's own release for Solaris. Any of the VMs for Solaris will help you create more partitions per drive as well as handling striping and mirroring, etc. Without a VM you are indeed limited to the 7 (or 8 if you are a maverick) partitions that Solaris permits. Be careful on Solaris not to use the first 4K of a drive as part of ANY Informix chunk. Best to just skip the first cylinder when defining that first partition, again unless you are using a VM which avoids the problem. Art S. Kagel Marie Usher wrote: > > So what is the answer to having a large database? Is it hardware or are we > not limited to only 8 partitions as Solaris says because then one would be > limited to a 16 GIG Database server and that is small. > > marie > At 01:15 AM 8/15/99 +0100, you wrote: > >The rule that you are most likely to fall foul of is that the chunksize + > >offset must be less than 2GBytes. So, if you have only two chunks, you are > >limited to a 4GByte database server. > > > >Better get that sys admin manual out ....! > > > >Neil Truby > >Londis Stores > >Hampton Hill, UK > > > >Marie Usher wrote in message <7p4m8v$99u$1@news.xmission.com>... > >> > >>I have a database that i need to reorganize on 2 very large raw chunks. > >>Presently the > >>database is spread over 9 chunks. What is the concept using offset. How > >>do i know where to start another dbspace. Is there a rule? > >> > >>marie > >> > >