当前位置: 首页 > MOS, ORA > 正文

今天群里面一位兄弟在问ORA-28056的报错,其实WIN环境,很常见的报错,并且一BAIDU,GOOGLE一下,大量的解决方法。

APPLIES TO:

Oracle Server – Personal Edition – Version 11.1.0.6 and later
Information in this document applies to any platform.
***Checked for relevance on 06-Jul-2012***

SYMPTOMS

Connect as sysdba fails with:

ORA-28056: Writing audit records to Windows Event Log failed.

CAUSE

The Event Viewer log is full and not able to log any more events.

This is addressed in unpublished 
Bug 6823281 – ORA-28056 WRITING AUDIT RECORDS TO WINDOWS EVENT LOG FAILED
which was closed as not a bug.

SOLUTION

Try doing the following using Windows Event Viewer: 

1. To open Event Viewer, click Start, click Control Panel, click Performance and Maintenance, click Administrative Tools, and then double-click Event Viewer. 

You must be logged on as an administrator or a member of the Administrators group to free an event log.

2. Then use any of the next options:

  • When a log is full, it stops recording new events. Clearing the log is one way to free the log and start recording new events.
  • You can also free a log and start recording new events by overwriting old events. To overwrite events, on the Action menu, click Properties, and then click Overwrite events as needed. This ensures that all new events are written to the log, even when the log is full.
  • You can also start logging new events by increasing the maximum log size. To increase the log size, on the Action menu, click Properties, and then increase the Maximum log size.

REFERENCES

@ BUG:6823281 – ORA-28056: WRITING AUDIT RECORDS TO WINDOWS EVENT LOG FAILED

ORA-28056: Writing audit records to Windows Event Log failed.:等您坐沙发呢!

发表评论

gravatar

? razz sad evil ! smile oops grin eek shock ??? cool lol mad twisted roll wink idea arrow neutral cry mrgreen

快捷键:Ctrl+Enter