RMAN Backup ERROR 239 after Server Migration

[Pierre_J]

Hi,

We have deleted a client from an Rman policy (from the All Policies pane in the GUI, not by opening and saving the policy).
The next night 3 jobs were started on that client which ended in Status 239, Job Schedule *NULL* and no Job Details.

We've never seen this before and we can't find an explanation for that. Does anybody has?

[quebek]

Hello

Exit code 239 stands for:

bperror -S 239
the specified client does not exist in the specified policy
The specified client is not a member of the specified policy.

So looks like there is some crontab job on this client which is trying to use the policy from which you deleted this client... Or maybe its even scheduled by NBU - can not tell as do not have these details. In Activity monitor what is in the client column??

[Michael_G_Ander]

Yes, the netbackup scheduler (nbpem) actually plans ahead.

Can often be solved by running nbpemreq -updatepolicies in admincmd.

Which normally runs about every 10 minutes, but some times needs a little help.

[Marianne]

I would look on the client for an OS-level scheduler (e.g. Task scheduler on Windows, cron on Linux/Unix) that is kicking off a script at specific time(s).

The other possibility is an external scheduler (e.g. Control-M).

[Pierre_J]

@quebek Activity Monitor Client column is empty.

@Michael_G_Ander The servers was definitely removed from the policy 10 minutes before the jobs ran.

@Marianne There is no other active scheduling mechanism involved.

So at the moment I go for Michael's answer that nbpemreq sometimes needs a little help.

Thanks all for replying!

[Amol_Nair]

Since you mentioned that it was an Oracle policy do check on the client machine if the script used earlier still exists and if someone had manually executed the script which may have triggered the job to run in NetBackup and reporting status 239..

Another possibility could be the same client is added in another Oracle policy and the script does not have SEND prameters mentioned in the script causing the child jobs to run with a different policy altogether and reporting the error.. If you could find bphdb folder on the client machine can help you..

[NBU35]

AS you said Client column is empty in Activity monitor, how are you sure these jobs from the same client ?

Most Possible reason is either that RMan backup script is getting executed from cron of client or someone is exceuting that script.