| Trapping archival errors in 8.1.7 OSDI [message #113701] |
Tue, 24 July 2001 03:59  |
paul mansfield
Messages: 35
Registered: January 2001
|
Member |
|
|
|
The way archive logging is done under 8.1.7 has changed. It appears that no meesages appear on the console when archival errors occur. Does anyone have a good way of trapping an archival error message so that we can issue an alert for our operators.
|
|
|
|
| Re: Trapping archival errors in 8.1.7 OSDI [message #113702 is a reply to message #113701] |
Fri, 27 July 2001 04:02  |
paul mansfield
Messages: 35
Registered: January 2001
|
Member |
|
|
: The way archive logging is done under 8.1.7 has changed. It appears that no meesages appear on the console when archival errors occur. Does anyone have a good way of trapping an archival error message so that we can issue an alert for our operators.
Whoops, it does put out a message ORA-16014 so we can trap on archival error. Could do with a message on Console when the database is open though.
|
|
|
|
| Re: Trapping archival errors in 8.1.7 OSDI [message #113706 is a reply to message #113702] |
Tue, 31 July 2001 08:25 |
Subhash Roy
Messages: 24
Registered: January 2001
|
Junior Member |
|
|
: : The way archive logging is done under 8.1.7 has changed. It appears that no meesages appear on the console when archival errors occur. Does anyone have a good way of trapping an archival error message so that we can issue an alert for our operators.
: Whoops, it does put out a message ORA-16014 so we can trap on archival error. Could do with a message on Console when the database is open though.
: Trappting Oracle errors and writing them to the console (WTO) is a good idea, so the helpdesk can monitor them even on weekends and report them to the responsible DBAs for immediate action. The messages that go into the console are mostly MPM and TXM.
: The ORA messages hardly go there, and instead, go to the alert logs.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
