• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
When creating new patron records on our Test server, we get the message "Duplicate patron ID" for the record number (and/or "Duplicate patron barcode" for the barcode). Then I enter the duplicate number into the patron search box, and yes, there is already a patron using that number.

Can you tell us why the system would generate a number for new patron when the number is already being used by an existing patron?

Resolution:
The abc50 util g/2 currently has:

5. last-bor-id 81508 y S ABCP
6. last-bor-id-1 106919 n S ABCB

But the following sql shows that there are z303_rec_key's through ABCP89999:

abc50@ALEPH20> select max(z303_rec_key) from z303 where z303_rec_key like 'ABCP8%';
**** Hit return to continue ****

MAX(Z303_REC
------------
ABCP89999


and on to ABCP92614:

abc50@ALEPH20> select max(z303_rec_key) from z303 where z303_rec_key like 'ABCP9%';
**** Hit return to continue ****

MAX(Z303_REC
------------
ABCP92614

Thus, the abc50 last-bor-id value needs to be changed to 92614.


Similarly, this SQL shows that there's a z308 barcode with the value 118937:

abc50@ALEPH20> select max(z308_rec_key) from z308 where z308_rec_key like '01ABCB%';
**** Hit return to continue ****

MAX(Z308_REC_KEY)
---------------------------
01ABCB000118937 ABC50

Thus, the abc50 last-bor-id-1 value needs to be changed to 118937.

• Article last edited: 10/8/2013