OraFAQ Forum: Backup & Recovery » View v$backup_datafile is not updated after a backup. Rman is skipping datafiles.

Home » RDBMS Server » Backup & Recovery » View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. (Oracle database 18.3.0.0, Oralinux 7.7)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. [message #681212]

Fri, 26 June 2020 08:25

dyrson
Messages: 3
Registered: June 2020

Junior Member

Hello,
Hope someone can help us with this tricky issue.

The problem:
------------
View v$backup_datafile is not updated after a backup. Rman is skipping datafiles.

Log from rman:
--------------
"channel t1: specifying datafile(s) in backup set
input datafile file number=00005 name=+DG_EXTPRO_DATA/DGEXTPRO6/DATAFILE/tbsd_ext_smartecm.256.974226737
skipping datafile 00005 because it has not changed"

Details:
--------
We use check_mk to monitor our databases. It uses the view v$backup_datafile(field completion_time) in order to verify how many days since last backup(all levels).
As the view is not getting updated after a rman backup, check_mk tool sends alerts.

We use a rman catalog. The backup finishes sucessfully. All datafiles are skipped since June 10. Nothing relevant found in the alert log.

The backup gets really done although the messages from rman. And the datafiles do have changed. The rman catalog gets updated and shows the recent backups.
But issuing LIST BACKUP SUMMARY without connecting on the catalog, only shows the backups until June 10.

Other related views also are not updated: v$backup_controlfile_summary for example.

It seems there is a new behaviour on Oracle 18c. Or a bug.

The Environment:
----------------
Red Hat Enterprise Linux Server release 7.7 (Maipo) - Oralinux
Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production Version 18.3.0.0.0 (both production and rman databases)
Recovery Manager: Release 18.0.0.0.0 - Production on Fri Jun 26 08:51:01 2020 Version 18.3.0.0.0 (client)
DGMGRL for Linux: Release 18.0.0.0.0 - Production on Fri Jun 26 09:28:27 2020 Version 18.3.0.0.0
asmcmd version 18.0.0.0.0 (compatibility: 12.1.0.0.0, database compatibility: 10.1.0.0.0)
Oracle High Availability Services version on the local node is [18.0.0.0.0]

It's a Data Guard environment and the backups are done on the physical standby node.

Thanks in advance.

Dyrson

Report message to a moderator

Re: View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. [message #681215 is a reply to message #681212]

Fri, 26 June 2020 17:41

Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille

Senior Member
Account Moderator

>>It's a Data Guard environment and the backups are done on the physical standby node.

What kind exactly?
Not sure about 18c.
Incremental backups are supported only on Active Standby.

Report message to a moderator

Re: View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. [message #681217 is a reply to message #681215]

Fri, 26 June 2020 21:37

dyrson
Messages: 3
Registered: June 2020

Junior Member

We do not have an Active Data Guard license. Pretty sure that we can have incremental backups on a physical standby database. We have been doing it for years.

"The standby database is a physical standby database, and backups are taken only on the standby database. See Standby Databases Too Geographically Distant to Share Backups for procedural changes if backups are taken on both primary and standby databases."

from https://docs.oracle.com/en/database/oracle/oracle-database/18/sbydb/using-RMAN-in-oracle-data-guard-configurations.html#GUID-33B70E30 -2454-484C-9110-A5AC452E63CB

"Use the BACKUP command to back up a primary or standby database, tablespace, data file (current or copy), control file (current or copy), server parameter file, archived redo log file, or backup set."

from https://docs.oracle.com/en/database/oracle/oracle-database/18/rcmrf/BACKUP.html#GUID-73642FF2-43C5-48B2-9969-99001C52EB50

Report message to a moderator

Re: View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. [message #681219 is a reply to message #681217]

Sat, 27 June 2020 00:12

Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille

Senior Member
Account Moderator

>>We have been doing it for years.
Doc ID 2416800.1 still says it is not supported.
Physical standby in readonly mode / Active dataguard is supported.

Report message to a moderator

Re: View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. [message #681220 is a reply to message #681219]

Sat, 27 June 2020 01:55

John Watson
Messages: 8960
Registered: January 2010
Location: Global Village

Senior Member

It is only fast incremental backups (you know, with the change tracking file) that need ADG.

Report message to a moderator

Re: View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. [message #681221 is a reply to message #681212]

Sat, 27 June 2020 02:01

John Watson
Messages: 8960
Registered: January 2010
Location: Global Village

Senior Member

I'm sorry if this sounds as though I do not trust you, but can you confirm thisQuote:

All datafiles are skipped since June 10.

and how you are determining it? It seems most unlikely. Can you post the output of the RMAN job? If you don't have it, you can extract it from v$rman_output.

Report message to a moderator

Re: View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. [message #681250 is a reply to message #681221]

Tue, 30 June 2020 06:30

dyrson
Messages: 3
Registered: June 2020

Junior Member

There is an excerpt of the log in my original post:

Log from rman:
--------------
"channel t1: specifying datafile(s) in backup set
input datafile file number=00005 name=+DG_EXTPRO_DATA/DGEXTPRO6/DATAFILE/tbsd_ext_smartecm.256.974226737
skipping datafile 00005 because it has not changed"

It repeats the skipping message for all datafiles.

Actually we found that in the standby node(where the backups are really taken) there are newer data in the v$backup_datafile. But it does not reflect the actual backup. And the view v$backup_set has the actual data. Strange. Anyway it solves our problem.

Another possibility is to get the data from the catalog view rc_datafile_backup.

Thanks everybody.

Report message to a moderator

Re: View v$backup_datafile is not updated after a backup. Rman is skipping datafiles. [message #682370 is a reply to message #681212]

Tue, 20 October 2020 08:58

PavanKast
Messages: 1
Registered: October 2020

Junior Member

Hi,

This error/informational message reports in RMAN backup log when your standby database are not in sync with production. It means no archives are being applied on standby database so there is no change in the database since last backup hence you are getting this informational message "skipping datafile xxxxx because it has not changed".

Thanks,
Pavan

Report message to a moderator

Previous Topic:	Block Change Tracking file is deleted
Next Topic:	RMAN duplicate database

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Nov 23 02:07:24 CST 2024