Crawl Fails Showing "DBMS Job Execution Error. Check The Database Job Trace File."
(Doc ID 1503130.1)
Last updated on NOVEMBER 15, 2023
Applies to:
Oracle Secure Enterprise Search - Version 11.1.2 and laterInformation in this document applies to any platform.
Symptoms
Crawls stopped working.
From SES Administration web app, Home > Schedules screen,
A previously working crawl was started by selecting "radio button" next to subject crawl schedule, and click "Start" button.
"Status" column changes to "Launching", and after 20 seconds or so, refreshing the screen shows "Status" = "Failed".
No log file is generated for the action.
The crawl statistics show a failed crawl, with an Error Log entry of "DBMS job execution error. Check the database job trace file.".
The SES query is still working, but cannot crawl the source for new documents to be indexed.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |