1. Support
  2. Knowledge base
  3. 100021287

Oracle backups via RMAN that do not specify a policy fail with status 230: the specified policy does not exist configuration database

Article: 100021287
Last Published: 2013-10-24
Ratings: 1 0
Product(s): NetBackup

Problem

Oracle backups via RMAN backups that do not specify a policy, fail on some clients with status 230: the specified policy does not exist configuration database

The above problem can be seen even when the same RMAN script is run successfully on other clients that exist in the RMAN policy that contains the problem client(s).

Cause

When an RMAN script is run that does not specify a policy, the backup request first goes to bprd on the master server.  Bprd then forwards the request to nbpem, who then needs to search the policies for an RMAN policy that contains the requesting client, and has an open window in a user backup schedule.  
Even though other clients in the same RMAN policy are able to run successful backups using the same RMAN script, for certain clients a corruption in the pempersit2 file can cause nbpem to be unable to review the policies to find a match for the requesting client.  In this case the following message can be seen in the nbpem log, and nbpem would fail the job immediately with a status 230:
 
File ID:116 [jobid=-1 job_group_id=-1 client=cmhsawulrs01.safelite.as type=2 server= task=ID:31ce55a8 policy=] 1 V-116-195 [ExtReqTask::run_possiblePolicies] Failed to retrieve list of policies, 230  

Solution

1. Stop NetBackup processes and ensure all processes are stopped with "bpps -a"

2. Rename the pempersist2 file in /usr/openv/netbackup/db/jobs to pempersist2.old
3. Restart NetBackup and retry the backup
 
Workaround:
You can explicity specify the policy name by adding the line:
SEND NB_ORA_POLICY=<policy_name>';
where <policy_name> is the policy that you want the backup to use.
You should add this line after the ALLOCATE CHANNEL lines in the RMAN run block.

Was this content helpful?

Article Languages