Re: DG related events
- From: Ron Warshawsky <ronwarshawsky@xxxxxxxxx>
- To: fairlie rego <fairlie_r@xxxxxxxxx>
- Date: Thu, 19 Oct 2006 20:48:14 -0700 (PDT)
Hello Fairlie,
I am looking for more internal insight on how to interpret information
that are in the trace files generated by events.
Thanks,
Ron
fairlie rego <fairlie_r@xxxxxxxxx> wrote:
Hi Ron,
If you do an oerr ora before the event number on a Unix box u will get a
brief description of what the event does (as seen below)
The levels determine the amount of tracing that is to be done. I would
presume you are having a performance problem with a logical standby database. I
would also hope that you are not on 9i
Regards,
Fairlie
elephant-> oerr ora 16300
16300, 00000, "LSBY architected tracing event"
// *Cause:
// *Action:
elephant-> oerr ora 1349
01349, 00000, "LogMiner tracing event"
// *Cause:
// *Action:
elephant-> oerr ora 10308
10308, 00000, "replication testing event"
// *Document: NO
// *Cause:
// *Action:
elephant-> oerr ora 26700
26700, 00000, "STREAMS tracing event"
// *Document: NO
// *Cause:
// *Action:
Ron Warshawsky <ronwarshawsky@xxxxxxxxx> wrote:
Dear List,
Can you share insight on below dataguard related events:
event="16300 trace name context forever, level 63";
event="16300 trace name context forever, level 15";
event="1349 trace name context forever, level 4095";
event="26700 trace name context forever, level 1560";
event="10308 trace name context forever, level 8";
Regards,
Ron Warshawsky
Fairlie Rego
Senior Oracle Consultant
http://www.linkedin.com/in/fairlierego
http://el-caro.blogspot.com/
M: +61 402 792 405
---------------------------------
Want to be your own boss? Learn how on Yahoo! Small Business.
Other related posts:
