Re: How can I create DBSCAPES in 20GB RAW partition

malc_p@hotmail.com wrote: > > In article <slrn6fpgoi.23p.frostbit@kali.brainlink.com>, > frostbit@brainlink.com (Raj Goel) wrote: > > I'm going through Carlton's ODS Handbook and there's something > > I don't quite understand. > > I've got a 20GB partition that I've reserved for my DBspaces. > > As I understand it, the maximum size dbspace I can create under > > Solaris 2.5.1/OWS 7.20 is 2GB. > > So, how do I go about creating the 10 DB spaces I need for my > > application? Or am I consigned to using cooked spaces? > (Assuming you've set the 20Gb space up as raw disk in the OS) > Each dbspace is set up with a SIZE and OFFSET. Thus, set up the first dbspace > at 2Gb, offset 0. Second dbspace size 2Gb, offset 2Gb (in whatever the units > used by your system are). > Third dbspace, size 2Gb, offset 4Gb. NO! This will not work! Read on. First: Dbspaces can be as large as you need them. A dbspace is made up of one or more 'chunks'. Each chunk is limited to 2GB and its offset plus size CANNOT EXCEED 2GB! This is not an Informix limit! It is because many UNIX's do not yet support the 64bit version of seek/fseek so Informix must continue to use seek/fseek which have the 2GB limit for absolute disk addressing. Therefore you must partition your drives, or stripe/RAID sets, into 2GB partitions or logical drives. Anyway a dbspace can have as many chunks as needed and the 7.xx engines support 1024 chunks or 2TB. Chunks can be less than 2GB and the offsets allow multiple smaller chunks to be allocated within one 2GB partition/drive. Second: It is my understanding that Solaris cannot create more than four partitions per drive/stripe set. So using Solaris tools you cannot use more than the first 8GB of a drive. There are third party storage managers available that can create more logical drives and use all of a 20GB drive on Solaris. BTW the first chunk of each Solaris partition must be offset by 2K to avoid overwritting Solaris partition managements data. Art S. Kagel