ORA-28056 Writing audit records to Windows Event Log failed
ORA-28056：Writing audit records to Windows Event Log failed
今天同事遇到這個問題。表面現象是，odbc無法連線。不過我檢查問題，首先會去檢查Oracle相關的一些情況，比如說：監聽有沒有啟動、資料庫服務有沒有起來、tnsnames.ora配置是否正確、用sqlplus或plsql dev是否可以連線。這些排除後，再檢查是否是應用的問題。
所以，按照這個步驟，我先用sqlplus去連線了下，發現此問題。
看意思是Oracle寫審計日誌到windows事件日誌記錄失敗。對此我的第一反應是：是不是日誌寫滿了，寫不下了。所以我想去找它會把日誌寫到哪裡，但是無從下手，因為沒給目錄呀～～。這是常規的思維習慣，思路其實是正確的，但是沒有聯想到windows事件檢視器。直到google了下，才發現。將同事的事件日誌一刪除，立馬就可以了。這個是windows應用記錄事件日誌的地方，限制了記錄的最大事件數，超過了就寫不下了。
不過，這個問題，根據網上發生報錯的情況，和同事的情況都有個共性：都是11g。
應該是11g新增的功能所致，可能需要把這個停掉才能避免此類錯誤再次發生。
錯誤詳細資訊：
ORA-28056: Writing audit records to Windows Event Log failed
OSD-2094672: Message 2094672 not found; product=RDBMS; facility=SOSD
O/S-Error: (OS 1502) ??????????????????
ORA-28056: Writing audit records to Windows Event Log failed
OSD-2094672: Message 2094672 not found; product=RDBMS; facility=SOSD
O/S-Error: (OS 1502) ??????????????????
這是網上參考的解決方案：
Subject: Connect As Sysdba Fails With ORA-28056
Doc ID: 784068.1 Type: PROBLEM
Modified Date: 20-MAR-2009 Status: MODERATED
Applies to:
Oracle - Personal Edition - Version: 11.1.0.6 to 11.1.0.7
This problem can occur on any platform.
Symptoms
connect as sysdba fails with:
ORA-28056: Writing audit records to Windows Event Log failed.
Cause
Event Viewer log is full and not able to log anymore 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 Event Viewer:
.
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.
.
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.
.
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.
.
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.
這是網上參考的解決方案：
Subject: Connect As Sysdba Fails With ORA-28056
Doc ID: 784068.1 Type: PROBLEM
Modified Date: 20-MAR-2009 Status: MODERATED
Applies to:
Oracle - Personal Edition - Version: 11.1.0.6 to 11.1.0.7
This problem can occur on any platform.
Symptoms
connect as sysdba fails with:
ORA-28056: Writing audit records to Windows Event Log failed.
Cause
Event Viewer log is full and not able to log anymore 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 Event Viewer:
.
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.
.
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.
.
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.
.
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.
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/12932950/viewspace-689831/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- 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事件
- Best Practice in Writing
- Writing on important detailsImportAI
- 精讀《Records & Tuples for React》React
- Database Audit and Audit trail purgingDatabaseAI
- SEC_MAX_FAILED_LOGIN_ATTEMPTS 用途AI
- ORA-28056的解決辦法
- 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