CONTEXT Index issue
Mike, January 14, 2025 - 8:10 pm UTC
Hi
We have one database where the CONTEXT index is working and another database where it is NOT working.
I noticed that the timezone for the scheduler was different on the 2 environments, so I updated the scheduler time zone and dropped / recreated the index, but it did not work.
The DBTIMEZONE for each database is the same on both databases:
SQL> SELECT dbtimezone FROM DUAL;
DBTIMEZONE
------------------
-06:00
The issue seems to be with the NEXT_RUN_DATE on the ALL_SCHEDULER_JOBS table. On the database that is working, the NEXT_RUN_DATE looks like this:
14-JAN-25 02.06.50.000000000 PM -06:00
However, on the database where it is NOT working, it seems like the time zone is wrong:
14-JAN-25 01.07.21.000000000 PM -07:00
Does anyone know where that TIME ZONE is coming from for the last_start_date and next_run_date on the all_scheduler_jobs table for the CONTEXT INDEX?
Thanks. Mike