Database Not start [message #182098] |
Thu, 13 July 2006 00:52  |
razzakram
Messages: 1 Registered: July 2006
|
Junior Member |
|
|
when i start database give error your database initialize startup / shutdown procedure error 01033.
I open Sqlplus/nolog
connect / as sysdba
startup nomount
alter database mount
alter database open (after this command give me a errors)
ERROR at line 1:
ORA-01115: IO error reading block from file 2 (block # 785)
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\ABBUSYS\UNDOTBS01.DBF'
ORA-27070: skgfdisp: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).
I have no Archive files,
I have no Oracle Database files backup
I want database startup
anyone help me - thanks
|
|
|
Re: Database Not start [message #182136 is a reply to message #182098] |
Thu, 13 July 2006 04:36   |
Frank Naude
Messages: 4593 Registered: April 1998
|
Senior Member |
|
|
Your UNDO tablespace is corrupted. You can try to force the database open. However, if you don't need the data anymore, it would be easier to just create a new database.
PS: Next time, remember to setup proper backups!
|
|
|
Re: Database Not start [message #182141 is a reply to message #182098] |
Thu, 13 July 2006 04:42  |
biswagourav
Messages: 1 Registered: July 2006 Location: INDIA
|
Junior Member |
|
|
You need to check the O/S logfiles for any kind of read errors.
Another way to check the datafiles is to copy them to another
filesystem
If the above action generates a read error from the O/S, it is an indication
that the datafile was not readable and/or the disk may be corrupted.
case 2:You will need to restore the datafile from a cold backup and try it again.
It is possible that there will be a need to restore all the database files,
control files, and redo logs, so that they are in a consistent state.
as you dont have any backup, create new database as suggested by frank
|
|
|