Database Tuning (MOSC)

MOSC Banner

How to specify the systemstate dump directory when use oradebug

edited Apr 8, 2015 10:06AM in Database Tuning (MOSC) 3 commentsAnswered ✓



I am doing the following steps to get systemstate dump:

logged in as the sysdba user through SQLPLUS using oradebug:
SQL> select * from dual;
SQL> oradebug setmypid
SQL> oradebug unlimit
SQL> oradebug -g all dump systemstate 266
SQL> exit


And here is the directory of tracefile


 

>  oradebug tracefile_name

  /opt/oracle/diag/rdbms/<dbname>/<node>/trace/<node>_ora_17040.trc


Our /opt/oracle/ is small and system state dump will run out of space in /opt/oracle very fast. And there is no way to increase  the size of it since it is on a shared host. I am looking for a way to specify the directory when dump systemstate, like something we can use in oradebug? Or temporarily change the directory by setting diagnostic_dest and set it back after?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center