归档日志可以实时传到standby，但是applied的状态是NO

jiaxu2000感谢您的回复，按照您的方法操作之后，问题还是不能应用，日志在上一个贴子中，问题现象如下：收起

日志如下：
starting up 1 shared server(s) ...
Thu Dec 25 21:24:19 2014
alter database mount standby database
Thu Dec 25 21:24:23 2014
Setting recovery target incarnation to 1
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=9816
Thu Dec 25 21:24:23 2014
ARC0: Archival started
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Dec 25 21:24:23 2014
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
ARC1 started with pid=17, OS id=9818
ARC1: Becoming the heartbeat ARCH
ARC1: Thread not mounted
Thu Dec 25 21:24:23 2014
Successful mount of redo thread 1, with mount id 2265310979
Thu Dec 25 21:24:23 2014
Physical Standby Database mounted.
Completed: alter database mount standby database
Thu Dec 25 21:24:54 2014
alter database recover managed standby database disconnect from session
Thu Dec 25 21:24:54 2014
Attempt to start background Managed Standby Recovery process (oradb)
MRP0 started with pid=18, OS id=9820
Thu Dec 25 21:24:54 2014
MRP0: Background Managed Standby Recovery process started (oradb)
Managed Standby Recovery not using Real Time Apply
WARNING! Recovering data file 5 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 6 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 7 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 8 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 9 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 10 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 11 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 12 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 13 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 14 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 15 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 16 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 17 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 18 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 19 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 20 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 21 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 22 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
parallel recovery started with 3 processes
Thu Dec 25 21:24:59 2014
Waiting for all non-current ORLs to be archived...
Clearing online redo logfile 1 /database/oradb/redo01_1.log
Clearing online log 1 of thread 1 sequence number 4771
Thu Dec 25 21:24:59 2014
Errors in file /oracle/admin/oradb/bdump/oradb_mrp0_9820.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/database/oradb/redo01_1.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 4698
Fetching gap sequence in thread 1, gap sequence 4698-4698
Thu Dec 25 21:25:00 2014
Completed: alter database recover managed standby database disconnect from session
Thu Dec 25 21:25:29 2014
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 4698-4698
DBID 2206462951 branch 808443751
FAL[client]: All defined FAL servers have been attempted.
-------------------------------------------------------------
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
-------------------------------------------------------------
Thu Dec 25 21:28:16 2014
Using STANDBY_ARCHIVE_DEST parameter default value as /arch
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 9838
RFS[1]: Identified database type as 'physical standby'
Thu Dec 25 21:28:16 2014
RFS LogMiner: Client disabled from further notification
Thu Dec 25 21:38:52 2014
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =182
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
  processes                = 1500
  sessions                 = 1655
  __shared_pool_size       = 4630511616
  shared_pool_size         = 2147483648
  __large_pool_size        = 268435456
  large_pool_size          = 268435456
  __java_pool_size         = 268435456
  java_pool_size           = 268435456
  __streams_pool_size      = 16777216
  sga_target               = 12884901888
  control_files            = /database/oradb/control01.ctl, /database/oradb/control02.ctl, /database/oradb/control03.ctl
  db_block_size            = 8192
  __db_cache_size          = 7683964928
  db_cache_size            = 7516192768
  compatible               = 10.2.0.3.0
  log_archive_config       = DG_CONFIG=(dlvtccsdb,oradb)
  log_archive_dest_1       = LOCATION=/arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=oradb
  log_archive_dest_2       = SERVICE=dlvtccsdb LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=dlvtccsdb
  log_archive_dest_state_1 = ENABLE
  log_archive_dest_state_2 = ENABLE
  log_archive_format       = log%t_%s_%r.arc
  fal_client               = oradb
  fal_server               = dlvtccsdb
  db_file_multiblock_read_count= 16
  standby_file_management  = AUTO
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  dispatchers              = (PROTOCOL=TCP) (SERVICE=oradbXDB)
  job_queue_processes      = 10
  background_dump_dest     = /oracle/admin/oradb/bdump
  user_dump_dest           = /oracle/admin/oradb/udump
  core_dump_dest           = /oracle/admin/oradb/cdump
  audit_file_dest          = /oracle/admin/oradb/adump
  db_name                  = oradb
  db_unique_name           = oradb
  open_cursors             = 300
  pga_aggregate_target     = 4294967296
PMON started with pid=2, OS id=3947
PSP0 started with pid=3, OS id=3949
MMAN started with pid=4, OS id=3951
DBW0 started with pid=5, OS id=3953
LGWR started with pid=6, OS id=3955
CKPT started with pid=7, OS id=3957
SMON started with pid=8, OS id=3959
RECO started with pid=9, OS id=3961
CJQ0 started with pid=10, OS id=3963
MMON started with pid=11, OS id=3965
Thu Dec 25 21:38:53 2014
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=3967
Thu Dec 25 21:38:53 2014
starting up 1 shared server(s) ...
Thu Dec 25 21:40:00 2014
alter database mount standby database
Thu Dec 25 21:40:04 2014
Setting recovery target incarnation to 1
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3976
Thu Dec 25 21:40:04 2014
ARC0: Archival started
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Dec 25 21:40:04 2014
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
ARC1 started with pid=17, OS id=3978
ARC1: Becoming the heartbeat ARCH
ARC1: Thread not mounted
Thu Dec 25 21:40:04 2014
Successful mount of redo thread 1, with mount id 2265292720
Thu Dec 25 21:40:04 2014
Physical Standby Database mounted.
Completed: alter database mount standby database
Thu Dec 25 21:40:31 2014
alter database recover managed standby database disconnect from session
Thu Dec 25 21:40:31 2014
Attempt to start background Managed Standby Recovery process (oradb)
MRP0 started with pid=18, OS id=3981
Thu Dec 25 21:40:31 2014
MRP0: Background Managed Standby Recovery process started (oradb)
Managed Standby Recovery not using Real Time Apply
WARNING! Recovering data file 5 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 6 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 7 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 8 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 9 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 10 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 11 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 12 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 13 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 14 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 15 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 16 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 17 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 18 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 19 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 20 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 21 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 22 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
parallel recovery started with 3 processes
Thu Dec 25 21:40:36 2014
Waiting for all non-current ORLs to be archived...
Clearing online redo logfile 1 /database/oradb/redo01_1.log
Clearing online log 1 of thread 1 sequence number 4774
Thu Dec 25 21:40:36 2014
Errors in file /oracle/admin/oradb/bdump/oradb_mrp0_3981.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/database/oradb/redo01_1.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 4698
Fetching gap sequence in thread 1, gap sequence 4698-4698
Thu Dec 25 21:40:37 2014
Completed: alter database recover managed standby database disconnect from session
Thu Dec 25 21:41:06 2014
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 4698-4698
DBID 2206462951 branch 808443751
FAL[client]: All defined FAL servers have been attempted.
-------------------------------------------------------------
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
-------------------------------------------------------------
Thu Dec 25 21:43:19 2014
Using STANDBY_ARCHIVE_DEST parameter default value as /arch
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3994
RFS[1]: Identified database type as 'physical standby'
Thu Dec 25 21:43:19 2014
RFS LogMiner: Client disabled from further notification
Thu Dec 25 21:43:44 2014
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 3996
RFS[2]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
Thu Dec 25 21:43:44 2014
RFS[1]: Archived Log: '/arch/log1_4774_808443751.arc'
Thu Dec 25 21:43:46 2014
RFS[2]: Archived Log: '/arch/log1_4775_808443751.arc'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Archived Log: '/arch/log1_4776_808443751.arc'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Archived Log: '/arch/log1_4777_808443751.arc'
Primary database is in MAXIMUM PERFORMANCE mode
Thu Dec 25 23:06:38 2014
ALTER SYSTEM SET log_file_name_convert='/database/oradb','/database/oradb' SCOPE=SPFILE;
Thu Dec 25 23:08:45 2014
RFS[2]: Archived Log: '/arch/log1_4778_808443751.arc'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Archived Log: '/arch/log1_4779_808443751.arc'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Archived Log: '/arch/log1_4780_808443751.arc'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Archived Log: '/arch/log1_4781_808443751.arc'
Primary database is in MAXIMUM PERFORMANCE mode
Thu Dec 25 23:26:04 2014收起

好的，我试试。谢谢！收起

主库与备库数据文件的路径最好是一致的，否则需要修改路径

参考
http://yunlongzheng.blog.51cto.com/788996/982961
把路径换成自己的收起

这个DG是刚搭建完，就出这个问题啦。收起

下面是/oracle/admin/oradb/bdump/oradb_dbw0_4620.trc 的日志：

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle/product/10.2.0/db_1
System name:    Linux
Node name:      oradb
Release:        2.6.18-194.el5
Version:        #1 SMP Tue Mar 16 21:52:39 EDT 2010
Machine:        x86_64
Instance name: oradb
Redo thread mounted by this instance: 1
Oracle process number: 5
Unix process pid: 4465, image: oracle@oradb (DBW0)

*** 2014-12-19 14:52:41.589
*** SERVICE NAME:() 2014-12-19 14:52:41.589
*** SESSION ID:(1652.1) 2014-12-19 14:52:41.589
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: '/usr/local/blackboard/oracle/bbadmin_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: '/usr/local/blackboard/oracle/bbadmin_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: '/usr/local/blackboard/oracle/bb_bb60_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
ORA-01110: data file 8: '/usr/local/blackboard/oracle/bb_bb60_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: '/usr/local/blackboard/oracle/bb_bb60_stats_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10: '/usr/local/blackboard/oracle/bb_bb60_stats_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
ORA-01110: data file 11: '/usr/local/blackboard/oracle/cms_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
ORA-01110: data file 12: '/usr/local/blackboard/oracle/cms_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '/usr/local/blackboard/oracle/cms_files_users_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
ORA-01110: data file 14: '/usr/local/blackboard/oracle/cms_files_users_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
ORA-01110: data file 15: '/usr/local/blackboard/oracle/cms_files_courses_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 16 - see DBWR trace file
ORA-01110: data file 16: '/usr/local/blackboard/oracle/cms_files_courses_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 17 - see DBWR trace file
ORA-01110: data file 17: '/usr/local/blackboard/oracle/cms_files_orgs_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 18 - see DBWR trace file
ORA-01110: data file 18: '/usr/local/blackboard/oracle/cms_files_orgs_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 19 - see DBWR trace file
ORA-01110: data file 19: '/usr/local/blackboard/oracle/cms_files_inst_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 20 - see DBWR trace file
ORA-01110: data file 20: '/usr/local/blackboard/oracle/cms_files_inst_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 21 - see DBWR trace file
ORA-01110: data file 21: '/usr/local/blackboard/oracle/cms_files_library_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-01157: cannot identify/lock data file 22 - see DBWR trace file
ORA-01110: data file 22: '/usr/local/blackboard/oracle/cms_files_library_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
[oracle@oradb bdump]$ ORACLE_HOME = /oracle/product/10.2.0/db_1收起

是的主库和备库是否都存在data file 5 、6、7、8、9收起

看看主库和备库是否都存在data file 5 、6、7、8、9收起

新建的DG？自己测试用的?
贴一下这个文件吧
/oracle/admin/oradb/bdump/oradb_dbw0_4620.trc收起

备库日志：
Setting recovery target incarnation to 1
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=4643
Fri Dec 19 12:18:53 2014
ARC0: Archival started
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=4645
Fri Dec 19 12:18:53 2014
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
Fri Dec 19 12:18:53 2014
ARC1: Becoming the heartbeat ARCH
ARC1: Thread not mounted
Fri Dec 19 12:18:53 2014
Successful mount of redo thread 1, with mount id 2264738089
Fri Dec 19 12:18:53 2014
Physical Standby Database mounted.
Completed: alter database mount standby database
Fri Dec 19 12:19:19 2014
alter database recover managed standby database disconnect from session
Fri Dec 19 12:19:19 2014
Attempt to start background Managed Standby Recovery process (oradb)
MRP0 started with pid=18, OS id=4647
Fri Dec 19 12:19:19 2014
MRP0: Background Managed Standby Recovery process started (oradb)
Managed Standby Recovery not using Real Time Apply
Fri Dec 19 12:19:24 2014
Errors in file /oracle/admin/oradb/bdump/oradb_dbw0_4620.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: '/usr/local/blackboard/oracle/bbadmin_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Fri Dec 19 12:19:24 2014
Errors in file /oracle/admin/oradb/bdump/oradb_dbw0_4620.trc:
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: '/usr/local/blackboard/oracle/bbadmin_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Fri Dec 19 12:19:24 2014
Errors in file /oracle/admin/oradb/bdump/oradb_dbw0_4620.trc:
ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: '/usr/local/blackboard/oracle/bb_bb60_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Fri Dec 19 12:19:24 2014
Errors in file /oracle/admin/oradb/bdump/oradb_dbw0_4620.trc:
ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
ORA-01110: data file 8: '/usr/local/blackboard/oracle/bb_bb60_indx_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Fri Dec 19 12:19:24 2014
Errors in file /oracle/admin/oradb/bdump/oradb_dbw0_4620.trc:
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: '/usr/local/blackboard/oracle/bb_bb60_stats_data_file1.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Fri Dec 19 12:19:24 2014收起