- Article Type: General
- Product: Voyager
- Product Version: 8.2.1
Releases replicated in: Voyager 8
Last version without bug: n/a (GDC new in Voyager 8)
Expected results: GDC would log an error and continue if it encounters unexpected data in a bib record.
Actual results: If GDC encounters a record whose 001 has trailing spaces, the job dies and never completes, and remains in a status of “Running” in Job Management until it is manually killed, even though the process has already died on the server.
Workflow implications: Jobs do not complete, and it may not be clear why.
1. Submit a scan job that will scan and pick up a record with a problem bib ID.
2. Job hangs in a status of Running and dies on server when it tries to write the problem bib ID to the database.
Other information: If you increase the logging in jobd.log prior to running the job, the following will be logged:
2012-04-10 10:59:22,411 321519 [main] ERROR com.exlibris.voyager.jobd.JobExecutor - Job Failed to run properly: For input string: "40009 "
Where 40009 is the bib ID of the record.
Workaround: Resave the records, or marcexport all affected records and then run a bulk import matching on bib_id to overlay all the affected records.
Fixed in GDC for 8.2.1
- Article last edited: 3/4/2015