ORA-00068: invalid value 0 for parameter _query_execution_time_limit, must be between 1920170603 and 7041645
<<Back to DB Administration Main Page
ORA-00068: invalid value 0 for parameter _query_execution_time_limit, must be between 1920170603 and 7041645
looking into the alertlog found below errors
Wed Feb 19 14:47:27 2020
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
Wed Feb 19 14:47:27 2020
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
Wed Feb 19 14:47:49 2020
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
Wed Feb 19 14:47:27 2020
WARNING: Oracle executable binary mismatch detected.
Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
Wed Feb 19 14:47:49 2020
Tried to check the rman config also ended with errors
RMAN>
connected to recovery catalog database
recovery catalog schema release 19.04.00.00. is newer than RMAN release
connected to recovery catalog database
recovery catalog schema release 19.04.00.00. is newer than RMAN release
RMAN>
echo set on
echo set on
RMAN> show all;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 02/19/2020 15:43:01
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 02/19/2020 15:43:01
ORA-01403: no data found
Changes
disable some databases features while the database was online
Solution:
shut down the database
relink all
start database
Comments
Post a Comment