01-22-2014 12:08 AM
hi,
Solved! Go to Solution.
01-22-2014 12:53 AM
I don't understand - why is CLIENT_NAME in bp.conf on the client set as saecopt51-b when the actual name is saenold24-b?
Is this maybe a cluster with the one name physical hostname and the other the virtual name for the cluster?
Is there a NB_ORA_CLIENT variable in the rman script? If so, what is it set to?
The thing is - you can see from bpclntcmd -pn that the master is also resolving Client IP address as hostname saecopt51-b.
Which one is correct?
What does 'hostname' on the client show?
nslookup does not seem to know about these names.
Double-check DNS config and ensure that reverse lookup works, or else use hosts entries on master, media server(s) and client.
Your first step will be to ensure correct name lookup.
All of the following should show the SAME client hostname:
On client:
CLIENT_NAME in client's bp.conf
bpclntcmd -self and bpclntcmd -pn on the client
NB_ORA_CLIENT in rman script
On master:
bpclntcmd -ip 10.40.153.98
Client name in policy
If you have to chance hosts entries, remember to refresh NBU host cache where you made changes: bpclntcmd -clear_host_cache
Only when all above entries are the same can the backup be retried.
Create the following log folders for further throubleshooting:
On master: bprd (restart NBU to enable log)
On client: bpcd and dbclient (dbclient needs 777 permissions).
If all hostname entries match and backup is still failing. please post logs.
Copy log file to reflect process name (e.g. bprd.txt) and upload as File attachment.
01-22-2014 12:37 AM
Note : in the activity monitor it parent fails with 6 and child stream fails with 6
so where you are seeing the job failure with 239 ?
show us the output of failed job detail status and also the policy output
bppllist <policyname> -L
01-22-2014 12:53 AM
I don't understand - why is CLIENT_NAME in bp.conf on the client set as saecopt51-b when the actual name is saenold24-b?
Is this maybe a cluster with the one name physical hostname and the other the virtual name for the cluster?
Is there a NB_ORA_CLIENT variable in the rman script? If so, what is it set to?
The thing is - you can see from bpclntcmd -pn that the master is also resolving Client IP address as hostname saecopt51-b.
Which one is correct?
What does 'hostname' on the client show?
nslookup does not seem to know about these names.
Double-check DNS config and ensure that reverse lookup works, or else use hosts entries on master, media server(s) and client.
Your first step will be to ensure correct name lookup.
All of the following should show the SAME client hostname:
On client:
CLIENT_NAME in client's bp.conf
bpclntcmd -self and bpclntcmd -pn on the client
NB_ORA_CLIENT in rman script
On master:
bpclntcmd -ip 10.40.153.98
Client name in policy
If you have to chance hosts entries, remember to refresh NBU host cache where you made changes: bpclntcmd -clear_host_cache
Only when all above entries are the same can the backup be retried.
Create the following log folders for further throubleshooting:
On master: bprd (restart NBU to enable log)
On client: bpcd and dbclient (dbclient needs 777 permissions).
If all hostname entries match and backup is still failing. please post logs.
Copy log file to reflect process name (e.g. bprd.txt) and upload as File attachment.
01-22-2014 02:23 AM
hi,
issue got fixed, in the script, client name was incorrect.
Thanks Marianne for the tip to check NB_ORA_CLIENT in rman script
-Chan