ORA-28056: Writing audit records to Windows Event Log failed
C:\>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 星期四 1月 5 13:55:44 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ERROR:
ORA-28056: Writing audit records to Windows Event Log failed
ORA-28056: Writing audit records to Windows Event Log failed
ORA-28056: Writing audit records to Windows Event Log failed
ORA-28056: Writing audit records to Windows Event Log failed
如上錯誤的解決辦法在metalink上面有四種不同的解決辦法,我採用了其中的得一種,進入windows的事件管理器將相關日誌清空後可以正常登陸。
metalink 原文如下:
Cause
The Event Viewer log is full and not able to log any more events.
Justified by 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:
Try doing the following using Windows Event Viewer:
To open Event Viewer, click Start, click Control Panel,
click Performance and Maintenance, click Administrative Tools,
and then double-click Event Viewer.
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.
Administrators group to free an event log.
1) 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.
is one way to free the log and start recording new events.
2) 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.
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.
3) 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
log size. To increase the log size, on the Action menu, click Properties,
and then increase the Maximum log size.
References
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/20674423/viewspace-714467/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-28056 Writing audit records to Windows Event Log failedWindowsAI
- How to audit failed logon attemptsAIGo
- MySQL Binlogging Fails With Writing One Row To The Row-based Binary Log FailedMySqlAI
- Failed reading log event, reconnecting to retryAI
- Windows Sqlserver Automatic Log Audit Via C/C++WindowsSQLServerC++
- SAP Security Audit log size
- Oracle - ORA-09817: Write to audit file failedOracleAI
- fluentd 推送 mariadb audit log
- AIX 中audit 和syslogAI
- Windows XP中建立庫遇到ORA-28056錯誤Windows
- ORA-09817: Write to audit file failed 的解決AI
- [ERROR] Failed to open logErrorAI
- FAILED_LOGIN_ATTEMPTSAI
- SAP R/3 Audit log configuration
- windows10系統下Windows event log佔用CPU使用率高怎麼辦Windows
- 【MySQL】log event entry exceededMySql
- MySQL [ERROR] Slave I/O: Found a Gtid_log_event or Previous_gtids_log_eventMySqlError
- Failed to run 'create login' or 'sp_addsrvrolemeber' in sql Linux using windows authentcationAIVRSQLLinuxWindows
- 解析MYSQL BINLOG二進位制格式(8)--GTID_LOG_EVENT/ANONYMOUS_GTID_LOG_EVENT及其他MySql
- 解析MYSQL BINLOG 二進位制格式(7)--Xid_log_event/XID_EVENTMySql
- C#9.0:RecordsC#
- Debug-Records
- Oracle FAILED_LOGIN_ATTEMPTS 理解OracleAI
- zt_Failed Logon AttemptsAIGo
- Database Triggers and event attributes--Event Attributes【Blog 搬家】Database
- log buffer space wait event等待事件AI事件
- Database Audit and Audit trail purgingDatabaseAI
- ORA-28056的解決辦法
- SEC_MAX_FAILED_LOGIN_ATTEMPTS 用途AI
- Best Practice in Writing
- Writing on important detailsImportAI
- 精讀《Records & Tuples for React》React
- Use case driven" means writing the user manual first, then writing the code
- oracle Database Event trace 設定【Blog 搬家】OracleDatabase
- FN_AUDIT - Name of security audit file
- 執行mysqlbinlog出現Found invalid event in binary log錯MySql
- weblogic報錯: OPatch failed with error code 73WebAIError
- logstash retrying failed action with response code: 429AI