本文详细介绍了如何解决Oracle数据库连接时出现的ORA-28056错误，该错误提示在写入Windows事件日志时失败。通过清理Windows应用程序日志，成功解决了问题。文章提供了详细的步骤和解决方案。
ORA-28056错误处理过程：
D:\>sqlplus /nolog
SQL*Plus: Release 11.1.0.7.0 - Production on 星期四 10月 8 20:03:50 2009
Copyright (c) 1982, 2008, Oracle. All rights reserved.
SQL> conn /as sysdba
ERROR:
ORA-28056: Writing audit records to Windows Event Log failed
OSD-1627319533: Message 1627319533 not found; product=RDBMS; facility=SOSD
O/S-Error: (OS 1502) ??????????????????
ORA-28056: Writing audit records to Windows Event Log failed
OSD-1627319533: Message 1627319533 not found; product=RDBMS; facility=SOSD
O/S-Error: (OS 1502) ??????????????????
解决过程：
打开windows 事件查看器，将应用程序日志清理一下，重新连接数据库，连接成功。启动数据库，启动正常。
解决这个问题的时候经过了多次的尝试都失败了，开始想到可能是系统日志的问题了，但没想到是日志满了，最后突然想到这个问题，试了一下，成功了。
论坛上有个哥们给了个很好的回复，以下是他的回复：
回复 #1 jiayuping 的帖子
Subject: Connect As Sysdba Fails With ORA-28056
Doc ID: 784068.1 Type: PROBLEM
Modified Date: 20-MAR-2009 Status: MODERATED
Applies to:
Oracle Server - 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.
Doc ID: 784068.1 Type: PROBLEM
Modified Date: 20-MAR-2009 Status: MODERATED
Applies to:
Oracle Server - 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.
扫一扫
8656
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
