Re: Can't add new chunk

Hi all! Yes, my second check showed that those raw devices were given to the temp dbspaces. Maybe my first check with 'ls -l | grep ...' wasn't written right and I blamed informix for nothing. Thank you! Best regards, Milen At 01:07 04/01/2001 +0000, David Williams wrote: >In article <92v8vg$bpr$1@mailint03.im.hou.compaq.com>, Frank ><paul.meaden@compaq.com> writes > >Long shot, but is there a chance that your symbolic links for calldbs67 and > >calldbs68 are pointing to raw device you have already used ? > > > Which online version? > > Very old 7.x versions (7.1x) had onconfig parameters like CHUNKS, > DBSPACES which set maximums for these! > > Try doing this through onmonitor, it tends to validate better. > > > > >Milen <milen@mobiltel.bg> wrote in message > >news:92v8kn$a05$1@news.xmission.com... > >> > >> Hi, > >> > >> After executing the command: > >> onspaces -a calldbs -p /informix/chunks/instance1/calldbs67 -o 0 -s> >2048000 > >> > >> I receive the following message : > >> The chunk specified already exists. > >> > >> > >> There isn't any rows in syschunks matching "**". > >> > >> I have the same message after attempting to add chunk calldbs68, too. > >> > >> > >> Chunks calldbs67 and calldbs68 point to unique raw devices. > >> > >> > >> I found limitation of 2048 chunks per system, but I didn't find any > >> limitation chunks per dbspace. What to do, where to check to add more > >space > >> to the dbspace? > >> > >> Thank you in advance! > >> > >> Best regards, > >> Milen. > >> > >> > >> ====================================================== > >> onstat -d output:> >> > >> Dbspaces > >> address number flags fchunk nchunks flags owner name > >> 5004c13c 1 2 1 1 M informix rootdbs > >> 50081f40 2 2001 2 1 N T informix temp01dbs > >> 50d39590 3 2001 3 1 N T informix temp02dbs > >> 50d3964c 4 1 4 66 N informix calldbs > >> 4 active, 2047 maximum > >> > >> Chunks > >> address chk/dbs offset size free bpages flags pathname > >> 5004c1f8 > >> 1 1 0 128000 99501 PO- > >> /informix/chunks/instance1/rootdbs01p > >> 5004c2d4 > >> 1 1 0 128000 0 MO- > >> /informix/chunks/instance1/rootdbs01m > >> 50081a18 > >> 2 2 0 512000 511947 PO- > >> /informix/chunks/instance1/temp01dbs01 > >> 50081af4 > >> 3 3 0 512000 511947 PO- > >> /informix/chunks/instance1/temp02dbs01 > >> 50081bd0 > >> 4 4 0 512000 3 PO- > >> /informix/chunks/instance1/calldbs01 > >> 50081cac > >> 5 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs02 > >> 50081d88 > >> 6 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs03 > >> 50081e64 > >> 7 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs04 > >> 50d36014 > >> 8 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs05 > >> 50d360f0 > >> 9 4 0 512000 3 PO- > >> /informix/chunks/instance1/calldbs06 > >> 50d361cc > >> 10 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs07 > >> 50d362a8 > >> 11 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs08 > >> 50d36384 > >> 12 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs09 > >> 50d36460 > >> 13 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs10 > >> 50d3653c > >> 14 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs11 > >> 50d36618 > >> 15 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs12 > >> 50d366f4 > >> 16 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs13 > >> 50d367d0 > >> 17 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs14 > >> 50d368ac > >> 18 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs15 > >> 50d36988 > >> 19 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs16 > >> 50d36a64 > >> 20 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs17 > >> 50d36b40 > >> 21 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs18 > >> 50d36c1c > >> 22 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs19 > >> 50d36cf8 > >> 23 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs20 > >> 50d36dd4 > >> 24 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs21 > >> 50d36eb0 > >> 25 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs22 > >> 50d36f8c > >> 26 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs23 > >> 50d37068 > >> 27 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs24 > >> 50d37144 > >> 28 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs25 > >> 50d37220 > >> 29 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs26 > >> 50d372fc > >> 30 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs27 > >> 50d373d8 > >> 31 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs28 > >> 50d374b4 > >> 32 4 0 512000 3 PO- > >> /informix/chunks/instance1/calldbs29 > >> 50d37590 > >> 33 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs30 > >> 50d3766c > >> 34 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs31 > >> 50d37748 > >> 35 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs32 > >> 50d37824 > >> 36 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs33 > >> 50d37900 > >> 37 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs34 > >> 50d379dc > >> 38 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs35 > >> 50d37ab8 > >> 39 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs36 > >> 50d37b94 > >> 40 4 0 512000 3 PO- > >> /informix/chunks/instance1/calldbs37 > >> 50d37c70 > >> 41 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs38 > >> 50d37d4c > >> 42 4 0 512000 5 PO- > >> /informix/chunks/instance1/calldbs39 > >> 50d37e28 > >> 43 4 0 512000 5

Milen wrote in message <9329af$9ir$1@news.xmission.com>... > >Hi all! > >Yes, my second check showed that those raw devices were given to the temp >dbspaces. >Maybe my first check with 'ls -l | grep ...' wasn't written right and I >blamed informix for nothing. Almost certainly... But it's nice to know that the engine tries very hard to stop accidents, yes?