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

Description:
When we did our test upgrade to v.18, all of our ALEPH local patron records were maintained in the upgrade. In the final upgrade of our prod region all of the ALEPH local patron records seems to have been lost. A query for ALEPH local patron records based on a KB entry shows we only have 1300, which are probably new adds since our upgrade last month.

Can you suggest an SQL statement that would add an ALEPH local patron record to every existing z303 that doesn't have an associated ALEPH z305? It would need to include a default patron status and expiry date.

Resolution:
Per KB 8192-7319, if you have USER-SHARING=N in tab100, having no ALEPH z305's is normal.

But since you have USER-SHARING=Y, you should have ALEPH Z305's.

The p_cir_83 job can be used to produce them. KB 10762 describes p_cir_83.

• Article last edited: 10/8/2013