Re: Database error and couldn't be opened

  • From: Andrew Kerber <andrew.kerber@xxxxxxxxx>
  • To: "dmarc-noreply@xxxxxxxxxxxxx" <dmarc-noreply@xxxxxxxxxxxxx>
  • Date: Mon, 29 Dec 2014 10:24:18 -0600

Ok, my fault for replying without thinking about it.  Block recover
requires a valid backup and archivelog mode, and dbv will only verify, it
wont fix data files.   If you do not have a valid backup up you are very
likely out of luck.  However, as others have noted do open a ticket with
Oracle support and see if they can help you.  If they cannot, there are
tools available that can try and read the good sections of your data file
directly.

On Sun, Dec 28, 2014 at 11:03 AM, Andrew Kerber <andrew.kerber@xxxxxxxxx>
wrote:

> Dbverify (dbv) might fix this, also look at block recover.  Both Oracle
> tools.  They might be able to fix this.
>
> Sent from my iPad
>
> On Dec 28, 2014, at 1:13 AM, Mostafa Eletriby (Redacted sender "
> m_etrib@xxxxxxxxx" for DMARC) <dmarc-noreply@xxxxxxxxxxxxx> wrote:
>
> Hello DBAs,
> Please I need top resolve these errors at database as database is mounted
> but couldn't be open.
> There is no backup and database is in noarchivelog mode.
> Database version:- standard edition.
> O.s:- linux redhat v5
>
> Please check.
> Thanks
>
> SQL> select status from v$instance;
>
> STATUS
> ------------------------------------
> MOUNTED
>
> SQL>
> SQL> alter database open;
> alter database open
> *
> ERROR at line 1:
> ORA-01115: IO error reading block from file 7 (block # 44988)
> ORA-01110: data file 7: '/oraData/cdsdbdata/ENRPGEST.dbf'
> ORA-27072: File I/O error
> Linux-x86_64 Error: 5: Input/output error
> Additional information: 4
> Additional information: 44988
> Additional information: -1
>
>
> SQL>
>
>
>


-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

Other related posts: