- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
We ran into a problem with the Aleph2Alma extract!
Before I run the extract I do the following:
- Shut down aleph
- turn off oracle archive logging.
- restart aleph
- run the extract
EXCEPT I forgot to start aleph up after turning oracle archive logging off. So when I run the extract it just sits at pending. I tried starting up aleph and left it for about 10 minutes but the extract did not progress.
I determined all the extract job pids and killed them.
I go to start the extract again but I get the message:
"The extract is already running. You cannot repeat the extract."
Looking through the Aleph2Alma scripts it looks like there are status indicators written to the oracle database so the extract utility checks oracle and won't run because all areas of the exract are pending.
Here is the current status of the extract in the Aleph2Alma menu:
Area Status Start End Extracted
========== ======= =========== =========== =========
ADAM Pending 0
CALENDAR Pending 0
CODE_TABLE Pending 0
COURSE Pending 0
E_RESOURCE Pending 0
FUND Pending 0
FUND_TX Pending 0
INVENTORY Failure 2018-DEC-15 2018-DEC-15 0
INVOICE Pending 0
LIBRARY Pending 0
LOAN Pending 0
LOAN_H Skipped 0
LOCATION Pending 0
MAPPING Pending 0
PARTNER Pending 0
PATRON Pending 0
P_ORDER Pending 0
REQUEST Pending 0
VENDOR Pending 0
The screen is refreshed every 10 seconds.
Press ^C to exit this screen. You can return to this screen via the menu.
How do I clean up the extract mess so I can run it again?
In this case, the Migration team suggested reinstallation of the auto extract kit, and then running it again. That worked.
- Article last edited: 30-Jan-2019