evo-s
1 Copper

WARNING: The savegrp summary could not be obtained.No save sets can be found in the NetWorker media database for this backup.

Jump to solution

Hi All

what this warning means? Backup copy was done successfully but networker job is marked failed.

How to correct this?

Regards,

Wed Jan 31 09:07:18 2018

Wed Jan 31 09:07:18 2018

cmd_args = LOG=/nsr/apps/logs/rcat_cob.log append

cmd_args = send 'NSR_ENV=(NSR_SERVER=nw01.eservice.local,NSR_GROUP=oracle/RCAT - Full/backup/oracle_RCAT - Full,NSR_CLIENT=ldorac01p.eu,NSR_SAVESET_BROWSE=1519858799,NSR_SAVESET_RETENTION=1519858799,NSR_PARENT_JOBID=259200,NSR_DIRECT_ACCESS=default,NSR_DATA_VOLUME_POOL=1MonthOracleDD01,NSR_APPS_PASS_THROUGH="*policy action jobid=259200, *policy name=oracle, *policy workflow name=RCAT - Full, *policy action name=backup",NSR_SAVESET_NAME=RMAN:\rcat_cob_FULL)'

rman_script = /nsr/apps/tmp/tmp_rman.9470

saveset_name = RMAN:\rcat_cob_FULL

Launching backup process

Recovery Manager: Release 11.2.0.4.0 - Production on Wed Jan 31 09:07:19 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target *

2>

3> connect catalog *

4>

5> RUN {

6> ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

7> BACKUP

8>  FULL

9>  FORMAT '%d_%U'

10>  DATABASE

11> ;

12> RELEASE CHANNEL CH1;

13> }

14>

connected to target database: RCAT (DBID=737868671, not open)

connected to recovery catalog database

allocated channel: CH1

channel CH1: SID=97 instance=rcat_cob2 device type=SBT_TAPE

channel CH1: NMDA Oracle v9.2.1.0

sent command to channel: CH1

Starting backup at 31-JAN-18

channel CH1: starting full datafile backup set

channel CH1: specifying datafile(s) in backup set

input datafile file number=00002 name=+DATA/rcat_cob/datafile/sysaux.275.965716833

input datafile file number=00007 name=+DATA/rcat_cob/datafile/rcat_repo.291.965730383

input datafile file number=00001 name=+DATA/rcat_cob/datafile/system.274.965716829

input datafile file number=00006 name=+DATA/rcat_cob/datafile/tools.290.965730381

input datafile file number=00003 name=+DATA/rcat_cob/datafile/undotbs1.276.965716837

input datafile file number=00005 name=+DATA/rcat_cob/datafile/undotbs2.277.965716837

input datafile file number=00004 name=+DATA/rcat_cob/datafile/users.278.965716839

channel CH1: starting piece 1 at 31-JAN-18

channel CH1: finished piece 1 at 31-JAN-18

piece handle=RCAT_1msq1aln_1_1 tag=TAG20180131T040615 comment=API Version 2.0,MMS Version 9.2.1.0

channel CH1: backup set complete, elapsed time: 00:00:45

channel CH1: starting full datafile backup set

channel CH1: specifying datafile(s) in backup set

including current control file in backup set

including current SPFILE in backup set

channel CH1: starting piece 1 at 31-JAN-18

channel CH1: finished piece 1 at 31-JAN-18

piece handle=RCAT_1nsq1an4_1_1 tag=TAG20180131T040615 comment=API Version 2.0,MMS Version 9.2.1.0

channel CH1: backup set complete, elapsed time: 00:00:35

Finished backup at 31-JAN-18

released channel: CH1

Recovery Manager complete.

RMAN returned success.

WARNING: The savegrp summary could not be obtained.No save sets can be found in the NetWorker media database for this backup.

ldorac01p.eu: Oracle Backup: RMAN:\rcat_cob_FULL    level=full,    -1 MB 11:11:11 -1 files

completed savetime=1517389639

0 Kudos
1 Solution

Accepted Solutions
Highlighted
tomek_lipinski
1 Copper

Re: WARNING: The savegrp summary could not be obtained.No save sets can be found in the NetWorker media database for this backup.

Jump to solution

Hi

Group name not contain ("/") it's name is "oracle_RCAT - Full". It works fine with that. Avoiding spaces is good idea. Problem is that Group Name cannot be easily changed by Networker Administration Console rather new must be created.

I think real problem is:

WARNING: The savegrp summary could not be obtained.No save sets can be found in the NetWorker media database for this backup.

Reason is

The snapshot of control file was created on local non-sharable storage based on RMAN policy.

After changed to shared location (ASM), RMAN completed backups without warnings.

Enjoy

0 Kudos
5 Replies
bingo.1
4 Tellurium

Re: WARNING: The savegrp summary could not be obtained.No save sets can be found in the NetWorker media database for this backup.

Jump to solution

The group name looks strange:

  -  I am pretty sure that a slash ("/") is not allowed.

  -  If you cannot avoid spaces, set the string either in "...." or in '.....' quotes.

0 Kudos
Highlighted
tomek_lipinski
1 Copper

Re: WARNING: The savegrp summary could not be obtained.No save sets can be found in the NetWorker media database for this backup.

Jump to solution

Hi

Group name not contain ("/") it's name is "oracle_RCAT - Full". It works fine with that. Avoiding spaces is good idea. Problem is that Group Name cannot be easily changed by Networker Administration Console rather new must be created.

I think real problem is:

WARNING: The savegrp summary could not be obtained.No save sets can be found in the NetWorker media database for this backup.

Reason is

The snapshot of control file was created on local non-sharable storage based on RMAN policy.

After changed to shared location (ASM), RMAN completed backups without warnings.

Enjoy

0 Kudos
buyixiaohuo
1 Copper

Re: WARNING: The savegrp summary could not be obtained.No sa

Jump to solution
My friend, has this problem been solved?
0 Kudos
buyixiaohuo
1 Copper

回复: WARNING: The savegrp summary could not be obtained.No sa

Jump to solution

Hello, my friend, has this problem been finally solved?

0 Kudos
evo-s
1 Copper

回复: WARNING: The savegrp summary could not be obtained.No sa

Jump to solution

Yes, problem solved.

but i'd like to notice that there is at least one more backup issue which finishes with mentioned warning.

I've seen this warning few days ago when one of oracle db archive logs backup job started fail with it. 

The problem was solved by removing old obsolete entries in the RMAN catalog database. RMAN crosscheck  shrinked over 40000 old entries. In fact crosscheck has to be done in regular basis not once a year we did. 🙂

 

It seems that a warning pointing to issue with the networker's media database may actually concern problems in a completely different place.

Regards

0 Kudos