Return
-
Title
Error, "ORA-44737: Parameter max_dump_file_size did not exist" when starting a trace in Session Browser for a 12c database -
Description
When connected to an Oracle 12c Pluggable DB or 12c RAC and using the Session Browser in Toad to start a trace, the option settings prompt opens. Leaving all default settings and clicking OK causes the following error:
Error occurred: [44737] (ORA-44737: Parameter max_dump_file_size did not exist.ORA-06512: at "SYS.DBMS_SYSTEM", line 117ORA-06512: at line 1)However, in the default settings have Unlimited Max Dump File size set. Able to start the trace manually once the SID and serial number are queried and the start of the trace is reflected in the Toad Session Browser tool by being highlighted in green, however if attempting to stop the trace from the Toad tool the following error occurs:
Error occurred: [29283] (ORA-29283: invalid file operationORA-06512: at "SYS.UTL_FILE", line 536ORA-29283: invalid file operationORA-06512: at line 4) -
Resolution
The issue has been address in Toad for Oracle 12.7.
-
Defect ID
ST 115910 -
Additional Information
Issues seem to be isolated to 12c and 12c RAC pluggable database setups.