We usually require a bit more information to properly analyse the problem you are experiencing.
Answers to the following questions will help.
1)What OS and OS version are you running on Primary and Standby.
2)What Dbvisit Standby version are you running on Primary and Standby.
3)What Oracle Database version and Edition are you running on Primary and Standby.
4)Are you using ASM / file system on Primary?
5)Are you using ASM / file system on Standby?
6)What types of filesystems are you using, ext3, ext4, NFS ...?
7)Would you be able to provide some file stats on the Standby system?
8)Provide the alert.log from the Primary and Standby database.
9)Provide the tracefile reported - 2616_dbvctl_csd_DBAF_201708010932.trc
As well as the output of the following queries executed against the Standby db.
set linesize 200 pagesize 20
col name for a50
col error for a20
col checkpoint_change# for 999999999999
col unrecoverable_change# for 999999999999
col first_nonlogged_scn for 999999999999
col current_scn for 999999999999
col resetlogs_change# for 999999999999
col controlfile_change# for 999999999999
spool dbv-primary-{{ticket.id}}.txt
alter session set nls_date_format='dd/mm/yyyy:hh24:mi:ss';
select file#, status, enabled, name, round(bytes/1024/1024,2) size_mb, checkpoint_change#, unrecoverable_change#, first_nonlogged_scn, checkpoint_change# from v$datafile df order by file#;
select file#, name, status, error, recover, fuzzy, creation_change#, checkpoint_change#, round(bytes/1024/1024,2) size_mb from v$datafile_header order by 1;
select dbid, name, resetlogs_change#, checkpoint_change#, controlfile_change#, controlfile_sequence#, controlfile_time, current_scn from v$database;
select * from v$database_incarnation;
spool off
We've seen this behaviour before and usually this happens when the storage/disks are slow and the system load runs high.
These are messages from Oracle.
We suggest you review your system load and retry the operation.
Comment actions