dropping chunk

Hello all, IDS9.40.FC4 HP-UX 11.11 I have successfully dropped an empty chunk from the database and tried to allocate it to another dbspace (after a Level 0 Archive) I am getting the message "The chunk specified already exists.". However, when looking for the chunk using "onstat -d" and "oncheck -pe" no reference can be found. Is there a system table where chunk information is kept? How do I get around this? Thanks in advance, Howard

howie wrote: > Hello all, > > IDS9.40.FC4 > HP-UX 11.11 > > I have successfully dropped an empty chunk from the database and tried > to allocate it to another dbspace (after a Level 0 Archive) I am > getting the message "The chunk specified already exists.". However, > when looking for the chunk using "onstat -d" and "oncheck -pe" no > reference can be found. Is there a system table where chunk > information is kept? How do I get around this? > > Thanks in advance, > > Howard Post your onstat -d output and also the onspaces command that you are using. Could it be that offsets were in use?

TBP wrote: > howie wrote: > > Hello all, > > > > IDS9.40.FC4 > > HP-UX 11.11 > > > > I have successfully dropped an empty chunk from the database and tried > > to allocate it to another dbspace (after a Level 0 Archive) I am > > getting the message "The chunk specified already exists.". However, > > when looking for the chunk using "onstat -d" and "oncheck -pe" no > > reference can be found. Is there a system table where chunk > > information is kept? How do I get around this? > > > > Thanks in advance, > > > > Howard > > Post your onstat -d output and also the onspaces command that you are using. > > Could it be that offsets were in use?

The offset used is 0. onspaces -d arcdatdbs -p /dev/vg_archive/rlvol34 -o 0 -y Remove the link /dev/vg_archive/rlvol34 to /dev/vg_database/rlvol34 rm /dev/vg_archive/rlvol34 Run a level 0 archive to /dev/null onspaces -c -d temp5dbs -t -p /dev/vg_database/rlvol34 -o 0 -s 2048000 The output of onstat -d is to large to post but there is now reference to /dev/vg_archive/rlvol34 or /dev/vg_database/rlvol34 in the output

The offset used is 0. onspaces -d arcdatdbs -p /dev/vg_archive/rlvol34 -o 0 -y Remove the link /dev/vg_archive/rlvol34 to /dev/vg_database/rlvol34 rm /dev/vg_archive/rlvol34 Run a level 0 archive to /dev/null onspaces -c -d temp5dbs -t -p /dev/vg_database/rlvol34 -o 0 -s 2048000 The output of onstat -d is to large to post but there is now reference to /dev/vg_archive/rlvol34 or /dev/vg_database/rlvol34 in the output

howie_lfc@hotmail.com wrote: > The offset used is 0. > > onspaces -d arcdatdbs -p /dev/vg_archive/rlvol34 -o 0 -y> > Remove the link /dev/vg_archive/rlvol34 to /dev/vg_database/rlvol34 > rm /dev/vg_archive/rlvol34 > > Run a level 0 archive to /dev/null > > onspaces -c -d temp5dbs -t -p /dev/vg_database/rlvol34 -o 0 -s 2048000> > The output of onstat -d is to large to post but there is now reference > to /dev/vg_archive/rlvol34 or /dev/vg_database/rlvol34 in the output > Did you check to see that none of the remaining chunk links is actually linked to /dev/vg_database/rlvol34 or to the physical device that it links to itself? IDS follows the links to their ultimate terminal file/device to check for possible chunk overlap. There may be another link used as a chunk withan offset a bit smaller than 2048000 and that would overlap with the new chunk you are trying to create. Art S. Kagel