I have 3 Oracle 12c DBs which are clones of one another. On my production DB if I enter a syntax error when constructing a query using SQLDeveloper, It will generate ORA-12801 and then the syntax error. On the other two DBs I just get the syntax error.
Since it is the production DB exhibiting the issue I would like to resolve it. I have verified disk space, temp table space, looked in the alert.log and the event viewer, the DB runs on Windows 2016, and found nothing.
This offending query is missing a format string ('yyyymmdd') in two to_date functions.
select TO_DATE(PATHMAST_DATE_OF_SPECIMEN),to_date(PATHMAST_PATIENT_DOB,'YYYYMMDD'),count(*)
from pathmast
where substr(pathmast_date_of_specimen,1,4) = '2017'
and substr(PATHMAST_PATIENT_DOB,1,4) IS NOT NULL
and substr(PATHMAST_PATIENT_DOB,1,4) != '9999'
group by TO_DATE(PATHMAST_DATE_OF_SPECIMEN),to_date(PATHMAST_PATIENT_DOB,'YYYYMMDD')
order by 1;
The error on the production DB is;
ORA-12801: error signaled in parallel query server P00G
ORA-01861: literal does not match format string
12801. 00000 - "error signaled in parallel query server %s"
*Cause: A parallel query server reached an exception condition.
*Action: Check the following error message for the cause, and consult
your error manual for the appropriate action.
*Comment: This error can be turned off with event 10397, in which
case the server's actual error is signaled instead.
On either cloned test server I get;
ORA-01861: literal does not match format string
01861. 00000 - "literal does not match format string"
*Cause: Literals in the input must be the same length as literals in
the format string (with the exception of leading whitespace). If the
"FX" modifier has been toggled on, the literal must match exactly,
with no extra whitespace.
*Action: Correct the format string to match the literal.
Yes I know how to fix my syntax errors, but I am concerned the ORA-12801 may be indicative of an underlying problem.