Bib key range increased to high number
- Article Type: General
- Product: Aleph
- Product Version: 20
Description:
From the use of manage-18, a file which contained a high record key (010695360) caused the last-doc-number
counter to be reset.
Using util-G2/6, that number has now been reset to the correct range (003520432-).
However, there are bib records in the range 010695466 to 010695624 which need to be
re-numbered.
1. Are there other counters which need to be reset?
2. How can the records in that bad range be re-numbered?
Resolution:
There are no other counters to be concerned about. {The abc50 last-doc-number has previously been increased over 100000000 (per KB 8192-667). You can and should leave it as is.}
In regard to the abc01 numbers, you can, if desired, follow the detailed procedure in KB 16384-22993 for running p_manage_33 and physically deleting the stub records for the 264 records with keys over 10,000,000:
abc01@ALEPH20> select count(*) from z00 where z00_doc_number > 10000000;
**** Hit return to continue ****
COUNT(*)
----------
264
(and their associated ADM, HOL, and item records).
This is not *absolutely* necessary, but I think it would be desirable.
- Article last edited: 10/8/2013