ORA-01242: data file suffered media failure

ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01110: data file 17: 'H:\DATABASE\BMFDATA.DBF'
ORA-01115: IO error reading block from file 17 (block # 1)
ORA-27072: File I/O error
OSD-04006: ReadFile() 失败, 无法读取文件
O/S-Error: (OS 33) 另一个程序已锁定文件的一部分,进程无法访问。
error 1242 detected in background process
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01110: data file 17: 'H:\DATABASE\BMFDATA.DBF'
ORA-01115: IO error reading block from file 17 (block # 1)
ORA-27072: File I/O error
OSD-04006: ReadFile() 失败, 无法读取文件
O/S-Error: (OS 33) 另一个程序已锁定文件的一部分,进程无法访问。

my database well be auto shutdown at 12:02 veryday .but i donot kown why!
the follow is the whole error message:
Dump file d:\oracle\product\10.2.0\admin\hbhis\bdump\hbhis_ckpt_2872.trc
Sat Mar 26 00:02:56 2011
ORACLE V10.2.0.4.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 32 - type 586, 8 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:31264M/32763M, Ph+PgF:33119M/34449M, VA:1253M/2047M
Instance name: hbhis
Redo thread mounted by this instance: 1
Oracle process number: 10
Windows thread id: 2872, image: ORACLE.EXE (CKPT)
*** 2011-03-26 00:02:56.031
*** SERVICE NAME:(SYS$BACKGROUND) 2011-03-26 00:02:56.031
*** SESSION ID:(162.1) 2011-03-26 00:02:56.031
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01110: data file 17: 'H:\DATABASE\BMFDATA.DBF'
ORA-01115: IO error reading block from file 17 (block # 1)
ORA-27072: File I/O error
OSD-04006: ReadFile() 失败, 无法读取文件
O/S-Error: (OS 33) 另一个程序已锁定文件的一部分,进程无法访问。
error 1242 detected in background process
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01110: data file 17: 'H:\DATABASE\BMFDATA.DBF'
ORA-01115: IO error reading block from file 17 (block # 1)
ORA-27072: File I/O error
OSD-04006: ReadFile() 失败, 无法读取文件
O/S-Error: (OS 33) 另一个程序已锁定文件的一部分,进程无法访问。

Similar Messages

  • ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode

    Hi All,
    Need help from the gurus.
    Currently we are in state unable to do anything.
    Was using a database and all of a sudden it crashed. Tried to mount the database, open it, it failed. Also tried the recover and alter database open, even that failed. Errors are as follows.
    Errors in file e:\oracle\product\10.2.0 \admin\devrevdb\bdump\devrevdb_p000_2620.trc:
    ORA-00603: ORACLE server session terminated by fatal error
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-00449: background process 'DBW0' unexpectedly terminated with error 1242
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    In my spfile, the administrator has set only two control files and there is no mirroring and hence do not have another control file that will help me boot the db.
    Please let me know how I should go about it. I am only a timebeing person trying to carryout a db activity. Any help would be of great help.

    Hemant,
    thanks for the reply.
    I tried the way you suggested and it threw an error.
    ORA-01145: offline immediate disallowed unless media recovery enabled
    I searched and found that an additional tag of drop needs to be added to the command which you suggested.
    ALTER DATABASE DATAFILE '<filename>' OFFLINE DROP.
    i don't know what will the drop command have an effect ?
    i have copied the data file to another location. Since i don't know much, i just want to be sure of what im doing.
    if the above command is successfull, will it drop the datafile or the tablespace and i can no more use it. How can i use the copied datafile.
    Thanks,
    Sachin
    I

  • ORA-01242: data file suffered media failure - ORA-01208: data file is an

    Hi,
    I am running Oracle 9.2.0.5 and if fails almost on a daily basis.
    I get the following errors:
    *** 2008-04-09 09:31:46.334
    *** SESSION ID:(4.1) 2008-04-09 09:31:46.318
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 11 failed verification check
    ORA-01110: data file 11: 'E:\ORACLE\ORADATA\MYDB\MYDB.ORA'
    ORA-01208: data file is an old version - not accessing current version
    error 1242 detected in background process
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 11 failed verification check
    ORA-01110: data file 11: 'E:\ORACLE\ORADATA\MYDB\MYDB.ORA'
    ORA-01208: data file is an old version - not accessing current version
    I run the following SQL and DB is recovered but I can't keep doing this everytime it crashes:
    sqlplus>startup nomount;
    sqlplus>alter database mount;
    sqlplus>alter database recover;
    sqlplus> alter database open;
    Any ideas how can I resolve this problem.
    Regards
    Spiros

    Refer to this metalink note:
    ORA-1242, ORA-1122, ORA-1110 & ORA-1208 Errors Occurring Intermittently
    Doc ID: Note:471280.1
    Werner

  • System tablespace file suffered media failure

    Hi All,
    Our DB is shutdown due to this error:
    ===
    ORA-01243: system tablespace file suffered media failure
    ORA-01122: database file 1 failed verification check
    ORA-01110: data file 1: '/dumps/rmodevdb/db/apps_st/data/system01.dbf'
    ORA-01206: file is not part of this database - wrong database id
    CKPT: terminating instance due to error 1243
    Instance terminated by CKPT, pid = 8203
    ====
    Please let me know how to resolve this.
    Thanks,
    Kishore

    Yes Aman.. This happened after cloning in apps.
    However, issue got resolved.
    Data files were zipped using tar- cvzf ...
    I could successfully complete the cloning when backup is taken with "tar cvf" (with out including z)
    So, learnt that datafiles should not be zipped when tar.
    But datafiles can be zipped using gzip after " tar cvf " is completed.
    Am i right ?

  • About error ORA-01208: data file is an old version - not accessing current

    Hi friends,
    After getting an error ,what i have stated below, my database instance was crashed everytime. I have seen alert.log file nothing is there and this error never come in pattern maner it will come anytime during week.
    I have check with my application client they were doing nothing during this time even they have sent me their log i found no writing process was running and no jobs were running during this time.
    My oracle version is 10.2.0.3 and os version is W2k.
    Thanks in advance.
    PM
    Thu Oct 04 21:45:37 2007
    Errors in file d:\oracle\admin\prd347\bdump\prd347_ckpt_1296.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 7 failed verification check
    ORA-01110: data file 7: 'E:\ORADATA\PRD347\CCDM_DATA_SMALL_T01_01.DBF'
    ORA-01208: data file is an old version - not accessing current version
    Thu Oct 04 21:45:37 2007
    Errors in file d:\oracle\admin\prd347\bdump\prd347_ckpt_1296.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 7 failed verification check
    ORA-01110: data file 7: 'E:\ORADATA\PRD347\CCDM_DATA_SMALL_T01_01.DBF'
    ORA-01208: data file is an old version - not accessing current version
    _________________________________________________________________

    Hi,
    I am attaching this CKPT Trace file which might helpful to you all.
    V10 STYLE FILE HEADER:
    Compatibility Vsn = 169869312=0xa200000
    Db ID=2446524247=0x91d2ff57, Db Name='PRD347'
    Activation ID=0=0x0
    Control Seq=654516=0x9fcb4, File size=491520=0x78000
    File Number=7, Blksiz=16384, File Type=3 DATA
    Tablespace #7 - CCDM_DATA_SMALL_T01 rel_fn:7
    Creation at scn: 0x0781.e33c8c09 12/13/2004 15:16:45
    Backup taken at scn: 0x0000.00000000 01/01/1988 00:00:00 thread:0
    reset logs count:0x201c7917 scn: 0x0000.00000001 reset logs terminal rcv data:0x0 scn: 0x0000.00000000
    prev reset logs count:0x0 scn: 0x0000.00000000 prev reset logs terminal rcv data:0x0 scn: 0x0000.00000000
    recovered at 09/25/2007 12:17:31
    status:0x4 root dba:0x00000000 chkpt cnt: 211627 ctl cnt:211626
    begin-hot-backup file size: 0
    Checkpointed at scn: 0x079b.81db9e4f 10/04/2007 21:45:15
    thread:1 rba:(0x33cee.2.10)
    enabled threads: 01000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000
    Backup Checkpointed at scn: 0x0000.00000000
    thread:0 rba:(0x0.0.0)
    enabled threads: 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000
    External cache id: 0x0 0x0 0x0 0x0
    Absolute fuzzy scn: 0x0000.00000000
    Recovery fuzzy scn: 0x0000.00000000 01/01/1988 00:00:00
    Terminal Recovery Stamp 01/01/1988 00:00:00
    Platform Information: Creation Platform ID: 7
    Current Platform ID: 7 Last Platform ID: 7
    DATA FILE #7:
    (name #18) E:\ORADATA\PRD347\CCDM_DATA_SMALL_T01_01.DBF
    creation size=0 block size=16384 status=0xe head=18 tail=18 dup=1
    tablespace 7, index=7 krfil=7 prev_file=0
    unrecoverable scn: 0x0000.00000000 01/01/1988 00:00:00
    Checkpoint cnt:211628 scn: 0x079b.81dba014 10/04/2007 21:45:20
    Stop scn: 0xffff.ffffffff 10/03/2007 02:00:10
    Creation Checkpointed at scn: 0x0781.e33c8c09 12/13/2004 15:16:45
    thread:0 rba:(0x0.0.0)
    enabled threads: 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000
    Offline scn: 0x0000.00000000 prev_range: 0
    Online Checkpointed at scn: 0x0000.00000000
    thread:0 rba:(0x0.0.0)
    enabled threads: 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000
    Hot Backup end marker scn: 0x0000.00000000
    aux_file is NOT DEFINED
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 7 failed verification check
    ORA-01110: data file 7: 'E:\ORADATA\PRD347\CCDM_DATA_SMALL_T01_01.DBF'
    ORA-01208: data file is an old version - not accessing current version
    error 1242 detected in background process
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 7 failed verification check
    ORA-01110: data file 7: 'E:\ORADATA\PRD347\CCDM_DATA_SMALL_T01_01.DBF'
    ORA-01208: data file is an old versio n - not accessing current version
    ------------------------------------------------------------------------------------------------

  • ORA-01110: data file 1024:

    Hi ,
    Hi,
    While doing patch post installtion, that is running catbundle sql scripts I got the below error.
    Patch : 12419331 ( DATABASE PSU 11.2.0.2.3 (INCLUDES CPUJUL2011) )
    Processing components and files for bundle 1: PSU 11.2.0.2.1
    Processing components and files for bundle 2: PSU 11.2.0.2.2
    Exception - patch NOT installed
    ORA-01157: cannot identify/lock data file 1024 - see DBWR trace file
    ORA-01110: data file 1024: '/u01/oradata/mydbsid/temp01.dbf'
    PL/SQL procedure successfully completed.
    Checked on server and found a different path for temp tablespace .
    it is '/v01/oradata/mydbsid/temp01.dbf' . I mean FS is different .
    Could you please let me know where to change the file path .
    Thanks ,
    Mahesh

    on executing below I am seeing this .
    is dropping and recreating the solution . Why it is picking up the wrong path ?
    SYS@igodevrp AS SYSDBA>select * from dba_temp_files
    ERROR at line 1:
    ORA-01157: cannot identify/lock data file 1024 - see DBWR trace file
    ORA-01110: data file 1024: '/u01/oradata/mydbsid/temp01.dbf'
    Edited by: 871048 on Sep 8, 2011 5:36 AM
    Edited by: 871048 on Sep 8, 2011 5:37 AM

  • Need your help for ORA-01242 error

    Hi,
    Data base Relaease : 9.2.0.4.0
    OS release: Suse linux 2.4.21-198-smp
    Today morning i have faced one problem in my database. Today i tried to create statspack schema in my production environment from my login (my linux login is in DBA group)... so i just tried to create a tablespace. Once issued create tablespace command my production database gets down... after that i started my database (Database is started with out any problem....). In my alery log i have seen below entries
    Thu Mar 29 11:08:31 2007
    create tablespace stats
    datafile '/sw01/oracle/oradata/cargainz/stat.dbf' size 100M
    Thu Mar 29 11:08:49 2007
    KCF: write/open error block=0x3 online=1
    file=17 /sw01/oracle/oradata/cargainz/stat.dbf
    error=27072 txt: 'Linux Error: 9: Bad file descriptor
    Additional information: 2'
    Thu Mar 29 11:08:49 2007
    Errors in file /sw01/oracle/admin/cargainz/bdump/cargainz_dbw0_1292.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01114: IO error writing block to file 17 (block # 3)
    ORA-01110: data file 17: '/sw01/oracle/oradata/cargainz/stat.dbf'
    ORA-27072: skgfdisp: I/O error
    Linux Error: 9: Bad file descriptor
    Additional information: 2
    DBW0: terminating instance due to error 1242
    Thu Mar 29 11:08:49 2007
    Errors in file /sw01/oracle/admin/cargainz/bdump/cargainz_ckpt_1296.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Thu Mar 29 11:08:49 2007
    ORA-1242 signalled during: create tablespace stats
    datafile '/sw01/oracle/ora...
    Thu Mar 29 11:08:49 2007
    Instance terminated by DBW0, pid = 1292
    Thu Mar 29 11:08:54 2007
    USER: terminating instance due to error 1092
    Instance terminated by USER, pid = 24370
    Thu Mar 29 11:10:14 2007
    Starting ORACLE instance (normal)
    =================================================
    In cargainz_dbw0_1292.trc
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    ORACLE_HOME = /sw01/oracle/9.0.2
    System name: Linux
    Node name: ICM02006
    Release: 2.4.21-198-smp
    Version: #1 SMP Thu Mar 11 17:56:49 UTC 2004
    Machine: i686
    Instance name: cargainz
    Redo thread mounted by this instance: 1
    Oracle process number: 3
    Unix process pid: 1292, image: oracle@ICM02006 (DBW0)
    *** 2007-03-29 11:08:49.159
    *** SESSION ID:(2.1) 2007-03-29 11:08:49.146
    KCF: write/open error block=0x3 online=1
    file=17 /sw01/oracle/oradata/cargainz/stat.dbf
    error=27072 txt: 'Linux Error: 9: Bad file descriptor
    Additional information: 2'
    error 1242 detected in background process
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01114: IO error writing block to file 17 (block # 3)
    ORA-01110: data file 17: '/sw01/oracle/oradata/cargainz/stat.dbf'
    ORA-27072: skgfdisp: I/O error
    Linux Error: 9: Bad file descriptor
    Additional information: 2
    =====================================================
    in cargainz_ckpt_1296.trc
    /sw01/oracle/admin/cargainz/bdump/cargainz_ckpt_1296.trc
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    ORACLE_HOME = /sw01/oracle/9.0.2
    System name: Linux
    Node name: ICM02006
    Release: 2.4.21-198-smp
    Version: #1 SMP Thu Mar 11 17:56:49 UTC 2004
    Machine: i686
    Instance name: cargainz
    Redo thread mounted by this instance: 1
    Oracle process number: 5
    Unix process pid: 1296, image: oracle@ICM02006 (CKPT)
    *** 2007-03-29 11:08:49.182
    *** SESSION ID:(4.1) 2007-03-29 11:08:49.182
    error 1242 detected in background process
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Can you please any one explain me the reason for this problem?.....
    Regards,
    Karthik

    Your database faced media failure.
    Oracle says...
    ORA-01242 data file suffered media failure: database in NOARCHIVELOG mode
    Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure.
    Action: Restore accessibility to the file mentioned in the error stack and restart the instance.
    Oracle was unable to write to the file and instance got terminated.
    Is this your production database ? Your first step is to keep the database in archivelog mode.

  • ORA-01242 error

    Here is the log on alert_orcl.log:
    Sun May 09 03:17:14 2010
    KCF: write/open error block=0x3ae47 online=1
    file=33 D:\ORCL\ORADATA\AXIDX_10.ORA
    error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
    O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.'
    Sun May 09 03:17:14 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_dbw0_2876.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01114: IO error writing block to file 33 (block # 241223)
    ORA-01110: data file 33: 'D:\ORCL\ORADATA\AXIDX_10.ORA'
    ORA-27072: File I/O error
    OSD-04008: WriteFile() failure, unable to write to file
    O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
    DBW0: terminating instance due to error 1242
    Sun May 09 03:17:14 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_ckpt_628.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:15 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_pmon_4996.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:16 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_lgwr_4292.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:16 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mman_4504.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:28 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_psp0_492.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:29 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j000_6400.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:32 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_q001_3964.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:33 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_reco_3084.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:33 2010
    Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_5796.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Sun May 09 03:17:34 2010
    Instance terminated by DBW0, pid = 2876

    You can transfer all objects to other tablespace and drop this tablespace.
    1.backup database
    2.defile tablespace as
    select TABLESPACE_NAME from dba_data_files where
    FILE_NAME='/orahome/oracle/product/10.2.0/oradata/SBN/PD.ORA';
    then export all objects(or users/schemas) using exp/expdp(you can define user as
    select username from dba_users default_tablespace=<TS>)
    3. create new tablespace and import all objects into this TS.
    4. drop old tablespace
    5.backup database
    Edited by: admin on May 11, 2010 2:02 AM

  • ORA-01242 - Media failure when restarting DB - data file locked ?

    Hi all,
    I've been experiencing the same problem on several databases for about one month.
    This occured on 8.1.7.4.1 and 9.2.0.7.0 db, on windows servers (2000 & XP).
    Here is the problem : I have scheduled tasks that shutdown the db, then restart and dump it.
    But for the 5th or 6th time in one month, I've found a stopped database in the morning
    and the same error in the alert.log file :
    alter database open
    Sat Jun 09 03:10:06 2007
    Errors in file e:\oracle\admin\elu\bdump\elu_lgwr_5708.trc:
    ORA-01110: data file 3: 'E:\ORACLE\ORADATA\ELU\DATA01.DBF'
    ORA-01114: IO error writing block to file 3 (block # 1)
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 32) Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
         -> this error message in french says that the datafile is already used by another process.
    After performing a "recover datafile", I can restart the database.
    I don't understand what kind of process could lock a datafile in a db that has just been restarted...
    It seems that this problem never happened before, but now I get this error every week o_O
    can anyone help ?
    Thanks !
    regards,
    Antoine
    Message was edited by:
    Antoine.M

    I've found the source of the problem.
    Actually everytime I got this problem, the datafile was locked by the backup software (DAT) during the night.
    thx for your reply

  • ORA-01124: cannot recover data file 1 - file is in use or recovery

    I am trying to recover standby database, but it is giving the below error.
    ORA-00283: recovery session canceled due to errors
    ORA-01124: cannot recover data file 1 - file is in use or recovery, recovery is already stated
    ORA-01110: data file 1: 'I:\ORACLE\QAS\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'
    when i checked in the alert log the recovery is not started. and later i hae given "alter database recover cancel' and the command end up with the below line
    "media recovery not started".
    it seems that the recovery has stuck in between.
    please advise me how to kill the recovery session that's stuck. because i dont want to bounce the standby database.
    thanks in advance.

    Without dataguard and MRP, you are running a scripted standby.
    In a scripted standby, a RECOVER DATABASE session would have an UNTIL clause (most likely UNTIL SEQUENCE). At the end of the recovery to that point (SEQUENCE#), it exits and shuts down the database.
    Also, the scripting is such that when one RECOVER session is active, another session is not allowed to start. It may loop in wait state or exit and retry at the next scheduled interval.
    Apparently your standby scripting is not robust enough to prevent another RECOVER session from starting off even as the first is active (and/or it doesn't have a proper UNTIL clause and stop, exit, shutdown actions)
    What you have is a custom implementation of a standby database. Without complete details of the script, the "locking" between sessions (to prevent a second RECOVER from starting when one is already running) etc .... we really cannot do much to help you.
    Your scripts should be maintaing status information . It should be possible for you to discover the "other" sqlplus session that has issued a RECOVER DATABASE but not yet exited (e.g. ... how about a simple "ps -ef |grep sql" and "ps -ef | grep ora" combination ??)
    Hemant K Chitale
    Edited by: Hemant K Chitale on May 29, 2013 5:47 PM

  • ORA-01511:error in renaming data file & ORA-01516: nonexistent data file

    Hi all,
    DB version is 10.2.0.2 and Applications 12.0.6 on RHEL 4
    While creating data file mistakenly we created with '?' as follows:
    "/d01/CRP/db/apps_st/data/tx_?data53.dbf"
    After that we tried to rename those data file using below steps but we are geting error message as follows:
    1.SQL>ALTER TABLESPACE APPS_TS_TX_DATA OFFLINE NORMAL; at DB in OPEN stage
    2.$mv /d01/CRP/db/apps_st/data/tx_?data53.dbf /d01/CRP/db/apps_st/data/tx_data53.dbf
    3.ALTER TABLESPACE APPS_TS_TX_DATA RENAME DATAFILE '/d01/CRP/db/apps_st/data/tx_?data53.dbf' TO '/d01/CRP/db/apps_st/data/tx_data53.dbf';
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01516: nonexistent log file, datafile, or tempfile
    "/d01/CRP/db/apps_st/data/tx_?data53.dbf"
    After that we tried to revert back by moving to original name usinf os commnds i.e tx_?data53.dbf and tried to open the database as follows but getting error message as follows:
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 1073741824 bytes
    Fixed Size 1264892 bytes
    Variable Size 440402692 bytes
    Database Buffers 620756992 bytes
    Redo Buffers 11317248 bytes
    Database mounted.
    SQL> recover database;
    Media recovery complete.
    SQL> alter database open ;
    alter database open
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    Please help us t oresolve the Issue
    Edited by: 912734 on Feb 15, 2012 2:43 AM

    Errors in alert log file:
    ALTER TABLESPACE APPS_TS_TX_DATA RENAME DATAFILE '/d01/CRP/db/apps_st/data/tx_?data53.dbf' TO '/d01/CRP/db/apps_st/data/tx_data53.dbf'
    Wed Feb 15 15:38:58 2012
    ORA-1525 signalled during: ALTER TABLESPACE APPS_TS_TX_DATA RENAME DATAFILE '/d01/CRP/db/apps_st/data/tx_?data53.dbf' TO '/d01/CRP/db/apps_st/data/tx_data53.dbf'...
    Wed Feb 15 15:40:10 2012
    ALTER TABLESPACE APPS_TS_TX_DATA RENAME DATAFILE '/d01/CRP/db/apps_st/data/tx_ data53.dbf' TO '/d01/CRP/db/apps_st/data/tx_data53.dbf'
    Wed Feb 15 15:40:10 2012
    ORA-1525 signalled during: ALTER TABLESPACE APPS_TS_TX_DATA RENAME DATAFILE '/d01/CRP/db/apps_st/data/tx_ data53.dbf' TO '/d01/CRP/db/apps_st/data/tx_data53.dbf'...
    ALTER TABLESPACE APPS_TS_TX_DATA ONLINE
    Wed Feb 15 15:41:09 2012
    Errors in file /d01/CRP/db/tech_st/10.2.0/admin/CRP2_oraapps/bdump/crp2_dbw0_1605.trc:
    ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
    ORA-01110: data file 11: '/d01/CRP/db/apps_st/data/tx_
    data53.dbf'
    ORA-27037: unable to obtain file status

  • Java.sql.SQLException: ORA-01157: cannot identify/lock data file 7 - see DB

    I am deploying my application components on Oracle RAC database, when i install my app component i will run a script which creates a user and tablespace on bot rac-nodes(node1 and node2)
    as database is clustered, the user are created on 2 nodes and tablespace is stored in a shared location for two rac nodes
    i am able to successfully run my script on rac-node1 and and installed my component and when i started installing the app component on node2 getting error
    java.sql.SQLException: ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
    ORA-01110: data file 7: '/db/db/db/ora10g/10.2.0/admin/dbadmin_01.dbf'
    ORA-06512: at "ADMIN.XL_SP_DBCHECK", line 48
    ORA-06512: at line 1
    "dbadmin_01.dbf is the custom tablespace which created by me"
    i a mgetting error while installing the app component on rac-node2

    You should not create database files outside of the ASM.
    I'm not sure you can move the datafile, I would export the data from the tablespace (if there is data you need there), delete the tablespace and recreate it in the ASM, then import the data back.
    If you want to move the datafile, you can try using RMAN (from node1).
    First connect to the database with sqlplus and execute:
    alter tablespace <tbs_name> offline;Then start RMAN: rman target /
    BACKUP AS COPY DATAFILE '<file>' FORMAT '+<ASM_DG>';Then in sqlplus, execute:
    alter tablespace <tbs_name> online;I'm not sure it will work, and I hope I got the commands right because I can't check it right now.
    Good luck
    Liron Amitzi
    Senior DBA consultant
    [www.dbsnaps.com]
    [www.orbiumsoftware.com]

  • Java.sql.SQLException: ORA-01157: cannot identify/lock data file : PLz Help

    My datafiles are in ASM file system, however the only one file ACIPEN_DATA is the one, which is not in ASM file system, and this the file which is in concern.
    We are getting the following exception in the lxkratgas1.lex1.lexmark.com when connecting to ACIPEN_DATA.
    This exception is coming up sometimes and the sometimes the file is getting processed successfully
    Caused by: java.sql.SQLException: ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
    ORA-01110: data file 9: '/oracle/SE/product/10.2.0/db_1/dbs/ACIPEN_DATA'
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
    at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
    at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
    at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1169)
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
    at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368)
    at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:278)
    at atg.adapter.gsa.SQLStatement.executeUpdate(SQLStatement.java:725)
    at atg.adapter.gsa.Table.insert(Table.java:1378)
    at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:6272)
    ... 61 more
    ====================================================================
    We have checked the datafile, it is absolutely online.
    Can some expert jump in and resolve this issue Please.

    01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
    // *Cause:  The background process was either unable to find one of the data
    //         files or failed to lock it because the file was already in use.
    //         The database will prohibit access to this file but other files will
    //         be unaffected. However the first instance to open the database will
    //         need to access all online data files. Accompanying error from the
    //         operating system describes why the file could not be identified.
    // *Action: Have operating system make file available to database. Then either
    //         open the database or do ALTER SYSTEM CHECK DATAFILES.is this a RAC database?

  • ORA-01157: cannot identify/lock data file 13 - see DBWR trace file

    Hi all,
    I've a Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
    I'm using ASM.
    Yesterday I added new disks and then I changed the +/etc/udev/rules.d/98-oracle.rules+ file.
    Now it looks like this (the bolded are the new ones):
    # Oracle Configuration Registry
    KERNEL=="emcpowerd1", OWNER="root", GROUP="oinstall", MODE="640", NAME="ocr"
    # Voting Disks
    KERNEL=="emcpowerr1", OWNER="oracle", GROUP="oinstall", MODE="640", NAME="voting"
    # Spfile ASM+
    KERNEL=="emcpowers1", OWNER="oracle", GROUP="dba", MODE="660", NAME="spfileASM"
    # ASM Devices
    KERNEL=="emcpowerj1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm0" #onlineredo asm disk
    KERNEL=="emcpowern1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm1" #data asm disk
    KERNEL=="emcpowerh1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm2" #data asm disk
    KERNEL=="emcpowerq1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm3" #data asm disk
    KERNEL=="emcpowere1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm4" #data asm disk
    KERNEL=="emcpowerg1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm5" #data asm disk
    KERNEL=="emcpowerl1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm6" #data asm disk
    KERNEL=="emcpowero1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm7" #data asm disk
    KERNEL=="emcpowerf1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm8" #data asm disk
    KERNEL=="emcpowerm1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm9" #data asm disk
    KERNEL=="emcpoweri1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm10" #data asm disk
    KERNEL=="emcpowerp1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm11" #data asm disk
    KERNEL=="emcpowerk1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm12" #data asm disk
    KERNEL=="emcpowert", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm210" #data asm disk SATA
    KERNEL=="emcpowerc", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm211" #data asm disk SATA
    KERNEL=="emcpowerb", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm212" #data asm disk SATA
    KERNEL=="emcpowera", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm213" #data asm disk SATA
    It's the same on both RAC nodes.
    The operating system, a RedHat 5.4, see the new devices (both nodes):
    ls -ltr /dev/asm*
    brw-rw---- 1 oracle dba 120, 16 May 18 10:03 /dev/asm212
    brw-rw---- 1 oracle dba 120, 304 May 18 10:03 /dev/asm210
    brw-rw---- 1 oracle dba 120, 32 May 18 10:03 /dev/asm211
    brw-rw---- 1 oracle dba 120, 0 May 18 10:03 /dev/asm213
    brw-rw---- 1 oracle dba 120, 209 May 18 10:05 /dev/asm1
    brw-rw---- 1 oracle dba 120, 81 May 18 13:40 /dev/asm8
    brw-rw---- 1 oracle dba 120, 97 May 18 13:40 /dev/asm5
    brw-rw---- 1 oracle dba 120, 193 May 18 13:40 /dev/asm9
    brw-rw---- 1 oracle dba 120, 161 May 18 13:40 /dev/asm12
    brw-rw---- 1 oracle dba 120, 241 May 18 13:40 /dev/asm11
    brw-rw---- 1 oracle dba 120, 177 May 18 13:40 /dev/asm6
    brw-rw---- 1 oracle dba 120, 225 May 18 13:40 /dev/asm7
    brw-rw---- 1 oracle dba 120, 65 May 18 13:40 /dev/asm4
    brw-rw---- 1 oracle dba 120, 129 May 18 13:40 /dev/asm10
    brw-rw---- 1 oracle dba 120, 257 May 18 13:40 /dev/asm3
    brw-rw---- 1 oracle dba 120, 113 May 18 13:40 /dev/asm2
    brw-rw---- 1 oracle dba 120, 145 May 18 13:40 /dev/asm0
    Both ASM instance see new devices:
    From ASM1
    SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:43:10 2010
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
    With the Real Application Clusters option
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    +ASM1
    SQL> select path from v$asm_disk;
    PATH
    /dev/asm212
    /dev/asm211
    /dev/asm213
    /dev/asm210
    /dev/asm1
    /dev/asm4
    /dev/asm5
    /dev/asm0
    /dev/asm12
    /dev/asm9
    /dev/asm2
    /dev/asm10
    /dev/asm7
    /dev/asm11
    /dev/asm3
    /dev/asm8
    /dev/asm6
    17 rows selected.
    SQL>
    From ASM2
    SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:42:39 2010
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
    With the Real Application Clusters option
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    +ASM2
    SQL> select path from v$asm_disk;
    PATH
    /dev/asm213
    /dev/asm211
    /dev/asm210
    /dev/asm212
    /dev/asm8
    /dev/asm7
    /dev/asm6
    /dev/asm11
    /dev/asm4
    /dev/asm12
    /dev/asm5
    /dev/asm9
    /dev/asm1
    /dev/asm3
    /dev/asm10
    /dev/asm2
    /dev/asm0
    17 rows selected.
    SQL>
    Then I created a disk group:
    CREATE DISKGROUP STORE EXTERNAL REDUNDANCY DISK '/dev/asm210';
    Then I created a new tablespace:
    CREATE TABLESPACE store DATAFILE '+STORE';
    I did all this operations from NODE1.
    What is happening now is that everytime I try to read something from new diskgroup FROM NODE2 I get the ORA-01157:
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707
    No problem to read from NODE1.
    The simple query on dba_data_file work from NODE1 and fails from NODE2 with the ORA-01157.
    I found this on the alert log:
    <msg time='2010-05-18T10:06:41.084+00:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    module='' pid='11014'>
    <txt>Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc:
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: &apos;+STORE/evodb/datafile/store.256.719232707&apos;
    </txt>
    </msg>
    And this from the trace:
    Trace file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc
    Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
    With the Real Application Clusters option
    ORACLE_HOME = /u01/app/oracle/product/11.1.0/db1
    System name: Linux
    Node name: node02
    Release: 2.6.18-128.7.1.el5
    Version: #1 SMP Wed Aug 19 04:00:49 EDT 2009
    Machine: x86_64
    Instance name: EVODB2
    Redo thread mounted by this instance: 2
    Oracle process number: 19
    Unix process pid: 11014, image: oracle@node02 (SMON)
    *** 2010-05-18 10:06:41.084
    *** SESSION ID:(151.1) 2010-05-18 10:06:41.084
    *** CLIENT ID:() 2010-05-18 10:06:41.084
    *** SERVICE NAME:(SYS$BACKGROUND) 2010-05-18 10:06:41.084
    *** MODULE NAME:() 2010-05-18 10:06:41.084
    *** ACTION NAME:() 2010-05-18 10:06:41.084
    DDE rules only execution for: ORA 1110
    ----- START Event Driven Actions Dump ----
    ---- END Event Driven Actions Dump ----
    ----- START DDE Actions Dump -----
    ----- DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
    Successfully dispatched
    ----- (Action duration in csec: 0) -----
    ----- END DDE Actions Dump -----
    *** 2010-05-18 10:06:41.084
    SMON: following errors trapped and ignored:
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707'
    Any suggestion about how to solve the problem?
    Thanks in advance!
    Samuel

    I didn't understand what do you mean with thread...
    But I think you found the problem
    Initialization files of both ASM instance are: SPFILE='/dev/spfileASM'
    that SPFILE is (common for both):
    +ASM2.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    +ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
    +ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'#Manual Mount
    *.asm_diskstring='/dev/asm*'
    *.cluster_database=true
    *.diagnostic_dest='/u01/app/oracle'
    +ASM1.instance_number=1
    +ASM2.instance_number=2
    *.instance_type='asm'
    *.large_pool_size=12M
    +ASM1.local_listener='LISTENER_ASM'
    +AC
    Then I executed another query:
    From ASM1
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    +ASM1
    SQL> select name, state from v$asm_diskgroup;
    NAME STATE
    ARCHIVELOG MOUNTED
    DATA MOUNTED
    ONLINELOG MOUNTED
    STORE MOUNTED
    SQL>
    From ASM2
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    +ASM2
    SQL> select name, state from v$asm_diskgroup;
    NAME STATE
    ARCHIVELOG MOUNTED
    DATA MOUNTED
    ONLINELOG MOUNTED
    STORE DISMOUNTED
    SQL>
    Than the question is:
    how can I mount the disk group STORE also on ASM2?
    I think the problems is into the spfile lines:
    +ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
    +ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'
    How can I change the +ASM2.asm_diskgroups value?
    Thanks

  • ASM diskgroups unmounting, getting ORA-01157: cannot identify/lock data fil

    All,
    We've recently purchased a RAMSAN device for better throughput. I created the initial diskgroup with the following syntax:
    CREATE DISKGROUP EMTPRD0X_SSD01 NORMAL REDUNDANCY
    FAILGROUP RS1 DISK '/dev/rdsk_ramsan_primary' NAME ssd_prim
    FAILGROUP RS2 DISK '/dev/rdsk_ramsan_backup' NAME ssd_bkup;
    and then created a temporary tablespace on top of that diskgroup:
    create temporary tablespace temp04 tempfile '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g;
    Everything seemed fine at first and then end users started seeing the following errors in the alert log:
    SUCCESS: diskgroup EMTPRD0X_SSD01 was mounted
    SUCCESS: diskgroup EMTPRD0X_SSD01 was dismounted
    SUCCESS: diskgroup EMTPRD0X_SSD01 was mounted
    SUCCESS: diskgroup EMTPRD0X_SSD01 was dismounted
    Tue Oct 12 16:12:51 2010
    Errors in file /opt/oracle/oradump/emtprd02/udump/emtprd02_ora_11578.trc:
    ORA-01157: cannot identify/lock data file 3009 - see DBWR trace file
    ORA-01110: data file 3009: '+EMTPRD0X_SSD01/emtprd0x/tempfile/temp04.256.732210281'
    After talking with Oracle support I was told that the only workaround for diskgroups unmounting themselves is to put a control file/redo log/dummy tablespace inside of that diskgroup and continually write/read from it.
    Does that make sense?
    They pointed me to note 603204.1 - Why FRA Diskgroup Gets Mounted/Dismounted.
    The system is a 3 node Oracle 10.2.0.4 rac running on ASM Solaris x86 64bit.
    Any ideas?
    Thanks,
    Brian

    Post Operating System (OS) name & version for DB server system.
    Post results of
    SELECT * from v$version
    My db is not in archivelog mode poor choice
    and no backup was taken. Worse choise
    Is there any way I can recover this db? Recover as in no data loss?
    Very doubtful.
    Possible to open with data loss.
    01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
    // *Cause:  The background process was either unable to find one of the data
    //         files or failed to lock it because the file was already in use.
    //         The database will prohibit access to this file but other files will
    //         be unaffected. However the first instance to open the database will
    //         need to access all online data files. Accompanying error from the
    //         operating system describes why the file could not be identified.
    // *Action: Have operating system make file available to database. Then either
    //         open the database or do ALTER SYSTEM CHECK DATAFILES.What exactly cause this mess?
    Edited by: sb92075 on Jan 7, 2010 8:59 PM

Maybe you are looking for