Exadata General (MOSC)

MOSC Banner

Is there any problem in changing diagnostic_dest of all dbs to another filesystem created in local d

edited Jan 4, 2013 6:21AM in Exadata General (MOSC) 3 commentsAnswered
Currently, we have 15 databases in a exadata database server. All dbs have diagnostic_dest pointing to $ORACLE_BASE/diag.$ORACLE_BASE and grid infrastructure ORACLE_HOME are located in the same filesystem /u01.
In this configuration, if the traces generated by all instances cause file system to become full, grid infrastructure stops working.
So, I would like to change diagnostic_dest to another filesystem in local disks.
Can I do that? Is there any recommendation about this issue, such as, size of diagnostic_dest per db?

Thanks in advance,

Luis Morimoto

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center