Xavier,

If it a master data set I would use the FIX DATASET command and for a
detail data set use the FIX PATH command. Also if it is a detail data
set you would want to use the FIX DATASET command on the linked master
first. Of course with any database changes this requires exclusive
access to the database. This is the path we used when we had to fix
several chains on several databases. The broken chains were caused by
some weird hardware problems.

Rich Holloway
Systems Administrator
Providence Health Plans
Phone: (503) 574-7457
Fax: (503) 574-8614
[log in to unmask]

The opinions expressed are not necessarily those of my company. They
belong solely to me.

If everything seems under control, you're just not going fast enough. --
Mario Andretti




> -----Original Message-----
> From: Xavier Boschian [SMTP:[log in to unmask]]
> Sent: Friday, May 07, 1999 2:28 AM
> To:   [log in to unmask]
> Subject:      BROKEN CHAIN POINTERS pb
>
> I get this error during a query :
>
> BROKEN CHAIN POINTERS
>
> What is the best solution ?
> ADAGER --> REPACK or DBUNLOAD DBLOAD ?
>
> Tx in advance.
> Xavier
>
> I tried with REPACK and I get another error :
> ----------------------------------------------------------------------
> ------------------
> Repack.  Please specify any dataset:
> TV8PAR.DB.DRAUT.  Dataset [NO MORE] ? ligne
> Possible methods to repack this detail dataset:
>
> 1) SERIAL+
> 2) SORTED+, by up to 4 fields of any kind
> 3) CHAINED+
> 4) SuperCHAINED+ (defaults to CHAINED+ on RISC hardware)
>
> (For a description of these methods, enter "0" as your choice)
>
> Number of your choice [3] ? 3
>
>
> This detail has only one path, which we shall optimize.
>
> You may specify the new capacity thus:
>
> A NUMBER specifies a particular capacity.
>
> A NUMBER FOLLOWED BY A PERCENT SIGN "%" specifies a percentage full.
>     Minimum 1%, maximum 100%.
>
> A PLUS SIGN "+" before a number specifies THAT MANY FreeEntries.
>
> Given the current entries (14051940), the new capacity will
> be 14052140 if you type "+200"
> or 14051940 if you type "100%", or 28103880 if you type "50%".
>
> #4 LIGNE: 14051940 entries, 89.65% full; MinimumCap: 14051940
>
> CURRENT Capacity: 15674144
> This dataset is NOT enabled for dynamic dataset expansion (DDX)
>
> If you enable this dataset for ddx, "NewCapacity" will mean "New
> MAXIMUM"
>
> (If you don't know the meaning of "!" in this context, answer "?" for
> help.)
>
>          { NewCapacity   }      [ { NewInitCap }      [ { NewIncrement
> } ] ]
>          { PercentFull % }        { !          }
>          { + FreeEntries }
>          { !             }
>
> Present :  15674144
>     New ?  98%
>
> Scheduled:
>                             Capacity will DECREASE from 15674144 to
> 14338714
>
>   LIGNE BF (16) rounds MaxCap: 14338720 [PutRootDdxBit]
>   LIGNE BF (16) rounds Capacity: 14338720 [PutRootDdxBit]
> Device-class name (or LDEV #) for LIGNE [DISC] ?
>  NewSetError @ 2025:     46 TV8PAR04.DB.DRAUT
> Out of space in device class DISC.
> X
>
> You may decide to purge some files (after backing them up, of course)
> to recycle their disc space.  At any point in the Adager dialogue, you
> can enter any operating-system command (including ":run" commands)
> that you may need to invoke your favorite utilities.
>
> Would you like to specify the purging of some MPE files
> ------------------