Applies to:
Oracle Server – Enterprise Edition – Version: 9.0.1 to 11.1
Oracle Server – Enterprise Edition – Version: 8.0 to 11.1
This problem can occur on any platform.
Symptoms
Using oradebug to create a systemstate may lead to the following error:
oradebug dump systemstate 266
Error 2819 encountered by local process [ospid=5529]
or
oradebug -g all dump systemstate 266
Error 2819 encountered by local DIAG [ospid=9936]
Error 2819 encountered by remote DIAG [ospid=27337][instance=3]
The error may be encountered for one or more instances in a RAC system as well (see above example).
Cause
The write to the tracefile failed either because there was not enough space to write the trace or the maximum size of the file was reached. Max_dump_file_size is the parameter to limit the size of tracefiles.
Solution
1. Make sure there is enough space to write tracefiles
2. Set max_dump_file_size
Without instance restart:
For single instance use the following command before creating the systemstate dump:
# sqlplus “/ as sysdba”
> oradebug setmypid — my process
> oradebug unlimit
> oradebug dump systemstate 266
> oradebug tracefile_name — makes it easier to collect the file
For RAC databases attach to DIAG process and increase that parameter manually using
oradebug:
# sqlplus “/ as sysdba”
> oradebug setospid
> oradebug unlimit
> oradebug tracefile_name — makes it easier to collect the file
> exit
In a RAC system repeat the procedure on every instance of the database.
With instance restart
Before restarting the instance set the parameter to unlimited:
sqlplus “/ as sysdba”
> alter system set max_dump_file_size=unlimited scope=spfile sid=’*’;
> exit
3. Get the systemstate after the above changes