This content has been marked as final. Show 15 replies
ORA-28056: Writing audit records to Windows Event Log failed
Cause: Unable to write an audit entry to the Windows event log used as the audit trail.
Action: Check the error number for a possible operating system error. If there is no error, contact Oracle Support Services.
Guessing here. Can you try making a backup of the event viewer in Windows and truncating the same after backup and then repeat this operation?
Clear the Event Logs. This solved the problem for me after updating from 18.104.22.168 to 22.214.171.124.
Control Panel --> Administrative Tools --> Event Viewer --> Clear All Events
Increase the log size.
Clearing event logs helped. thanks for the solution
So how about marking answers as "helpful" or "correct" and flagging the thread as "answered" ....
Do like our friend said. Control Panel --> Administrative Tools --> Event Viewer --> Clear All Events. After open the CMD, write "sqplus /nolog" and press enter. now, write "connect as sysdba", enter the user name, for example, "sys" and the password. After connect, write "startup". Tell if works.
tip: Grown the space of the Event viewer. you only need to right click th type of event, for example, "application" --> "properties" and grown the size. You should mark "change when necessary" too. You shouldn't have more problems like this now.
Edited by: lucas rehem on 09/09/2010 11:04
I got the same error while creating new db using dbca for Oracle11gR2.
So cleared all events log as suggested above which helped database creation to completed successfully.
Edited by: haider.ali on 31-Oct-2010 14:05
I would ask Tom Kyte. Although he dismisses ORA errors as ambiguous, he told me so at Oracle World 2010. Better off re-installing Windows Server 2008
I would also consider migrating OS to Red Had LINUX 5.x or higher. Very much gooder than Windows Server 2008
Did Oracle Server upgrade migrate sucessfully? I am getting a red X. I will check out the log when I am done assuming Sun Spots do not occur first.
clearing event log solves the problem.. even I faced this problem using DBCA in 11g R2.
This thread should be marked as answered.
Edited by: Saad on Jan 2, 2011 6:43 AM
This thread should be marked as answered.OP last posted to forum about 1 year ago.
I doubt your requested will be seen and honored.
Why do you resurrect zombie posts?
The solution is simple go to Control Panel->Administrative Tools->Event Viewer->Clear All Events and then run the configuration wizard again
It helped me to solve the error