Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
This topic has been discussed a couple of times on
this forum. In Google Groups search for "ids large
chunk" and you'll get a short list. Here is a link to
the thread that my similar question resulted in.
http://groups.google.com/group/comp.databases.informix/browse_frm/thread/cc3afebda528765/c80cd18d6106336b?lnk=st&q=ids+large+chunk&rnum=1&hl=en#c80cd18d6106336b
--- Ben <ben_informix@comcast.net> wrote:
> All,
>
> Any thoughts on the below dbspace and chunk
> configuration? I very much
> appreciate this group and its collective knowledge -
> thanks in advance!
>
> We are building a medium size server with database
> storage on a SAN device.
> I have been given 3 x 140 GB "raw" devices to use
> for data - the root,
> logging, etc.
> spaces are on separate devices.
>
> We will probably use about 20 GB on each of the 140
> GB devices.
>
> My first thought is to create a 20 GB dbspace (one
> chunk each) on each of
> these
> devices for a total of 60 GB:
>
> dbs_1 = 20 GB
> dbs_2 = 20 GB
> dbs_3 = 20 GB
>
> Backup strategy is ER + Nightly Level 0 dumps to the
> filesystem. We may
> include
> ontape in the near-term.
>
> Environment = Solaris 10 | IDS 10.0 FC3 | OLTP
> System
>
>
> Thank you!!
>
> Ben
> sending to informix-list
sending to informix-list
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.