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

Description:
On creating a patron record, error "patron ID already exists" occurs.

On checking the assigned ID, it was found that this was already assigned to another patron.

Resolution:
The ADM last-bor-id determines the patron ID which the system assigns. The STA50 util g/2 showed:

5. last-bor-id 17876 y S ID


But SQL shows that this was *not* the highest borrower ID:

SQL-STA50> select z303_rec_key from z303 where z303_rec_key like 'ID1787%';
**** Hit return to continue ****

Z303_REC_KEY
------------
ID1787
ID17870
ID17871
ID17872
ID17873
ID17874
ID17875
ID17876
ID17877
ID17878
ID17879


SQL-STA50> select max (z303_rec_key) from z303 where z303_rec_key like 'ID1%';
**** Hit return to continue ****

MAX(Z303_REC
------------
ID19999

SQL-STA50> select max (z303_rec_key) from z303 where z303_rec_key like 'ID2%';
**** Hit return to continue ****

MAX(Z303_REC
------------
ID29999

SQL-STA50> select max (z303_rec_key) from z303 where z303_rec_key like 'ID3%';
**** Hit return to continue ****

MAX(Z303_REC
------------
ID398

I have changed the sta50 util g/2 last-bor-id to "40000". It should be OK now.

• Article last edited: 10/8/2013