A potentially very timesaving feature in Oracle's adrci is the ability to search in the alert log for specific text, as I had to do to find when a specific parameter was set:
adrci ADRCI: Release 11.2.0.4.0 - Production on On Jun 11 12:03:34 2014 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. ADR base = "/u01/oracle/admin/proddb01/diagnostic" adrci> show homes ADR Homes: diag/rdbms/proddb01/proddb01 adrci> show alert -p "message_text like '%event%'" ADR Home = /u01/oracle/admin/proddb01/diagnostic/diag/rdbms/proddb01/proddb01: ************************************************************************* Output the results to file: /tmp/alert_3343326_1_proddb01_1.ado "/tmp/alert_3343326_1_proddb01_1.ado" 44 lines, 2408 characters 2013-08-25 14:35:46.344000 +02:00 One of the following events caused this: 2014-01-02 10:56:34.311000 +01:00 OS Pid: 8455160 executed alter system set events '10852 trace name context forever, level 16384' 2014-01-02 10:56:47.555000 +01:00 ALTER SYSTEM SET event='10852 trace name context forever, level 16384' SCOPE=SPFILE; 2014-01-10 00:43:02.945000 +01:00 event = "10852 trace name context forever, level 16384" 2014-01-31 19:32:59.471000 +01:00 event = "10852 trace name context forever, level 16384" 2014-02-01 09:12:59.653000 +01:00 event = "10852 trace name context forever, level 16384" CLOSE: Active sessions prevent database close operation 2014-02-01 18:10:54.100000 +01:00 event = "10852 trace name context forever, level 16384" 2014-06-10 19:38:42.536000 +02:00 ALTER SYSTEM SET event='10852 trace name context forever, level 16384 off' SCOPE=SPFILE; 2014-06-10 19:43:12.770000 +02:00 event = "10852 trace name context off"
Without much effort I was able to find that the parameter was set 02.01.2014, and switched off 10.06.2014.
No comments:
Post a Comment