DATAGUARD ORA-01274 ORA-01111 Treatment

Source: Internet
Author: User

Wrong

Mis-:file  #483  added to control file as  ' UNNAMED00483 '  becausethe  Parameter standby_file_management is set to manualthe file should be  manually created to continue. errors with log +fra/cweolb/archivelog/2015_08_02/thread_1_seq_225515.7695.886664431mrp0:  Background media recovery terminated with error 1274errors in file  /oracle/orabase/admin/CWEOLB/diag/rdbms/cweolb/CWEOLB/trace/CWEOLB_pr00_19398846.trc:ORA-01274:  cannot add datafile  ' +data/cweol/datafile/tstlog.2015080201 '  - file could  not be createdmanaged standby recovery not using real time  applyrecovery interrupted! Sun aug 02 21:55:44 2015recovered data files to a consistent  state at change 61278149367sun aug 02 21:55:44 2015mrp0: background media recovery process shutdown  ( Cweolb) mon aug 03 10:57:23 2015alter system set standby_file_management= ' AUTO '  SCOPE=BOTH; Mon aug 03 10:58:29 2015 alter database recover managed standby  database using current logfile disconnect from sessionattempt to  start background Managed Standby Recovery process  (Cweolb) Sun aug  02 21:58:29 2015MRP0 STARTED WITH PID=38, OS ID=7733714 MRP0:  Background Managed Standby Recovery process started  (Cweolb)  started  logmerger processsun aug 02 21:58:34 2015managed standby recovery  starting Real Time ApplySun Aug 02 21:58:34 2015Errors in  file /oracle/orabase/admin/cweolb/diag/rdbms/cweolb/cweolb/trace/cweolb_dbw0_9896432.trc:ora-01186: file  483 failed verification testsora-01157: cannot identify/lock data file  483 - see dbwr trace fileora-01111: name for data file  483 is unknown - rename to correct fileora-01110: data file  483:  '/oracle/orabase/ora11gr2/dbs/unnamed00483 ' file 483 not verified due  to error ora-01157mrp0: background media recovery terminated with  error 1111errors in file /oracle/orabase/admin/cweolb/diag/rdbms/cweolb/cweolb/trace/ cweolb_pr00_20250790.trc:ora-01111: name for data file 483 is unknown  - rename to correct fileora-01110: data file 483:  '/oracle/orabase/ ora11gr2/dbs/unnamed00483 ' ORA-01157: cannot identify/lock data file 483 - see dbwr trace  Fileora-01111: name for data file 483 is unknown - rename to  correct fileORA-01110: data file 483:  '/oracle/orabase/ora11gr2/dbs/ UNNAMED00483 ' managed standby recovery not using real time applyslave  exiting with ora-1111 exceptionerrors in file /oracle/orabase/admin/cweolb/diag/ rdbms/cweolb/cweolb/trace/cweolb_pr00_20250790.trc:ora-01111: name for data file 483  is unknown - rename to correct fileora-01110: data file 483 :  '/oracle/orabase/ora11gr2/dbs/unnamed00483 ' ora-01157: cannot identify/lock data  File 483 - see dbwr trace fileora-01111: name for data file  483 is unknown - rename to correct fileORA-01110: data file 483:  '/oracle/ orabase/ora11gr2/dbs/unnamed00483 ' recovery slave pr00 previously exited with  exception 1111mrp0: background media recovery process shutdown  (CWEOLB) Completed:  alter database recover managed standby database using  current logfile disconnect from sessionMon Aug 03 11:03:03  2015alter database recover managed standby database using current  logfile disconnect from sessionattempt to start background managed  standby recovery process  (Cweolb) sun aug 02 22:03:03 2015mrp0 started  with pid=38, OS id=16253320 MRP0: Background Managed Standby  recovery process started  (CWEOLB)  started logmerger processsun aug 02 22:03:08 2015managed standby  recovery starting real time applysun aug 02 22:03:08 2015errors  in file /oracle/orabase/admin/cweolb/diag/rdbms/cweolb/cweolb/trace/cweolb_dbw0_9896432.trc:o Ra-01186: file 483 failed verification testsora-01157: cannot identify/lock  data file 483 - see dbwr trace fileora-01111: name for  DATA FILE 483 IS UNKNOWN - RENAME TO CORRECT FILEORA-01110:  data file 483:  '/oracle/orabase/ora11gr2/dbs/unnamed00483 ' file 483 not  verified due to error ora-01157mrp0: background media recovery  Terminated with error 1111errors in file /oracle/orabase/admin/cweolb/diag/rdbms /cweolb/cweolb/trace/cweolb_pr00_19661014.trc:ora-01111: name for data file 483 is unknown -  rename to correct fileORA-01110: data file 483:  '/oracle/orabase/ ora11gr2/dbs/unnamed00483 ' ora-01157: cannot identify/lock data file 483 -  see dbwr trace fileora-01111: name for data file 483 is  unknown - rename to correct fileora-01110: data file 483:  '/ oracle/orabase/ora11gr2/dbs/unnamed00483 ' Managed standby recovery not using real  time applyslave exiting with ora-1111 exceptionerrors in file / oracle/orabase/admin/cweolb/diag/rdbms/cweolb/cweolb/trace/cweolb_pr00_19661014.trc:ora-01111: name  for data file 483 is unknown - rename to correct  Fileora-01110: data file 483:&nBSP; ' /oracle/orabase/ora11gr2/dbs/unnamed00483 ' ora-01157: cannot identify/lock data file  483 - see dbwr trace fileora-01111: name for data file 483  is unknown - rename to correct fileora-01110: data file 483 :  '/oracle/orabase/ora11gr2/dbs/unnamed00483 ' recovery slave pr00 previously exited  with exception 1111mrp0: background media recovery process shutdown   (CWEOLB) completed: alter database recover managed standby database  Using current logfile disconnect from session

Workaround:

ALTER SYSTEM SET standby_file_management= ' MANUAL ' Scope=both; sql> ALTER DATABASE Create DataFile '/oracle/orabase/ora11gr2/dbs/unnamed00483 ' as ' +data/cweolb/datafile/  tstlog.2015080201 ';D atabase altered.alter database recover managed standby database using current logfile disconnect from Session


DATAGUARD ORA-01274 ORA-01111 Treatment

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.