Search
- Filter Results
- Location
- Classification
- Include attachments
- https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Primo_Pipe_error_-_Failed_to_split_record_-_No_identifier_found.Problem Symptoms: *The pipe fails in harvest, not in NEP *The Primo Home > Monitor Primo Status > Pipe Monitoring > View Harvest Log says "unable to parse record length" *The Primo Home > Monitor Prim...Problem Symptoms: *The pipe fails in harvest, not in NEP *The Primo Home > Monitor Primo Status > Pipe Monitoring > View Harvest Log says "unable to parse record length" *The Primo Home > Monitor Primo Status > Pipe Monitoring > View Harvest Log says "Premature end of file encountered" Cause: The pipe failed because the maximum error threshold was set to 1% (too low). Change the "Maximum error threshold" from 1% (or anything below 50%) to 50% during the testing phase.
- https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Newupdated_Aleph_Course_Reserve_records_not_displaying_in_PrimoProblem Symptoms: New/updated xxx30 (Course Reserve) records are not displaying in Primo. (New/updated xxx01 bib records are OK.) Cause: The ./xxx30/scratch/run_e_21.nnnnn shows that the ue_21 publish...Problem Symptoms: New/updated xxx30 (Course Reserve) records are not displaying in Primo. (New/updated xxx01 bib records are OK.) Cause: The ./xxx30/scratch/run_e_21.nnnnn shows that the ue_21 publishing process ended several weeks ago with this message: Oracle error: update_cursor z07p ORA-03135: connection lost contact Process ID: 13519 Session ID: 386 S *************************************************** * No ORACLE connection - process is terminated... * ************************************…
- https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Pipe_run_fails_during_harvest_stageProblem Symptoms: --------------------------- ?· ? Pipe fails during 'nep' stage with status " 'stopped error - threshold exceeded', while processing job." ?· In BE log: "INFO [t-SplitRecords] [c-Orig...Problem Symptoms: --------------------------- ?· ? Pipe fails during 'nep' stage with status " 'stopped error - threshold exceeded', while processing job." ?· In BE log: "INFO [t-SplitRecords] [c-OriginalSourceRecordJDBCInsertUpdateService] - Existing entities found: { Cause: ---------- Records are not split during the Harvest job due to existing records in the DB. Thus exceeding the initial threshold defined by the pipe (default 5%) and causing the job to fail.
- https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Pipe_Failed_with_Error%3A__deadlock_detected_while_waiting_for_resourceProblem Symptoms: Our pipe has just failed with error: The pipe <PIPE NAME>, that started at <DATESTAMP> failed at <DATESTAMP> in stage 'nep' with status 'stopped error', while processing job 2012.06....Problem Symptoms: Our pipe has just failed with error: The pipe <PIPE NAME>, that started at <DATESTAMP> failed at <DATESTAMP> in stage 'nep' with status 'stopped error', while processing job 2012.06.27-17.30.00-175023390 The error message is: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource Cause: Resolution: You can simply re-execute the Pipe and it should complete.
- https://knowledge.exlibrisgroup.com/bX/Knowledge_Articles/bX_Harvest_Connection_Failure_errorEmail response from bX Harvester reports "Harvest Connection Failure for SFX" error a) bX Publishing not enabled in SFX b) bX Publishing not possible in SFX after changing to Alma. Publishing has to b...Email response from bX Harvester reports "Harvest Connection Failure for SFX" error a) bX Publishing not enabled in SFX b) bX Publishing not possible in SFX after changing to Alma. Publishing has to be deactivated in SFX and bX service level has to be changed to "subscriber". In the SFX Admin, go to the bX Configuration menu In bX registrations page go to SFX Instance Edit Client Attributes to set service level from "Subscriber and Contributor" to "Subscriber"
- https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Regular_pipe_fails_at_harvest_phase_with_error_%E2%80%9CAdding_record_to_failed_records%E2%80%9DRegular pipe fails in the harvest stage Adding record to failed records, record id=BL-20130408150330184-00000-12266~opera~8445.warc.gz_FILE_100.xml,error=No records contained within record file BL-201...Regular pipe fails in the harvest stage Adding record to failed records, record id=BL-20130408150330184-00000-12266~opera~8445.warc.gz_FILE_100.xml,error=No records contained within record file BL-20130408150330184-00000-12266~opera~8445.warc.gz_FILE_100.xml -- Record data: null,bulk=BulkContext: HIB id=null,bulk id=1,stage=nep,status=new,last task=CreateBulksForNEP?€?. The harvested file has the wrong ownership. Go to the directory where the problematic file lies
- https://knowledge.exlibrisgroup.com/Verde/Knowledge_Articles/%22The_harvester_cannot_be_initialized_due_to_Verde_resource_problems%22_errorIn the harvesting section of the Verde interface, the following error appears in the log: "The harvester cannot be initialized due to Verde resource problems. The log shows that there is an Oracle tab...In the harvesting section of the Verde interface, the following error appears in the log: "The harvester cannot be initialized due to Verde resource problems. The log shows that there is an Oracle tablespace which needs to be enlarged in order for the harvester to run: either TS0, TS1, or TSLOB, depending on what appears in the log. Use the server utility in order to enlarge the relevant tablespace (TS0/TS1/TSLOB) by at least the minimum to reach the amount from the error.
- https://knowledge.exlibrisgroup.com/Primo/Training/Primo_Training/Additional_Primo_Training/Primo_How_To's/How_to_Develop_Enrichment_Plug-insLearn how to develop enrichment plug-ins to add information to source records and harvested records. (9 min)
- https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Harvesting_a_record_fails_with_an_UncategorizedSQLException_error_on_the_P_DEDUP_VECTOR_tableThe dedup vectors are limited to 4000 characters. Use the GetHeadTail transformation to trim the vector.