Bug Report NetBackup 8.3 Oracle RAC restore fails with Status code 227 no entity was found.

Problem

When attempting an Oracle RAC restore with NetBackup 8.3, the restore fails with an an error 227, stating that the image needed for the restore cannot be found. A bplist of the oracle images will show that the image is actually present. This can occur on RAC clusters that have more than one database.

Error Message

The dbclient log  on the oracle client will report the following:

18:05:39.265 [38983] <4> sendRequest: sending buf = 1610445683 1610445683 /arch_dEBSCSPD1_u4avkdt8v_s269450_p1_t1061614879
18:05:39.265 [38983] <4> sendRequest: Date range: <-s 01/12/21  5:01:23>, <-e 01/12/21 05:01:23>
18:05:39.266 [38983] <4> serverResponse: entering serverResponse.
18:05:39.266 [38983] <4> serverResponse: initial client_read_timeout = <900>
18:05:39.266 [38983] <4> readCommMessages: Entering readCommMessages
18:05:41.267 [38983] <4> serverResponse: read comm file:<18:05:40 INF - Server status = 227>
18:05:41.267 [38983] <16> serverResponse: ERR - server exited with status 227: no entity was found
18:05:41.267 [38983] <16> RestoreFileObjects: ERR - serverResponse() failed
18:05:41.267 [38983] <4> closeApi: entering closeApi.
18:05:41.267 [38983] <4> closeApi: INF - EXIT STATUS 5: the restore failed to recover the requested files
18:05:41.267 [38983] <8> VxBSAGetObject: WRN - RestoreFileObject was not able to find the object.  Status: 26
18:05:41.267 [38983] <2> xbsa_ProcessError: INF - entering
18:05:41.267 [38983] <2> xbsa_ProcessError: INF - leaving
18:05:41.267 [38983] <16> xbsa_GetObject: ERR - VxBSAGetObject: Failed with error: There is no copy of the requested object.
18:05:41.267 [38983] <2> xbsa_GetObject: INF - leaving (26)
18:05:41.267 [38983] <16> int_StartJob: ERR - Failed to open backup file for restore.
18:05:41.267 [38983] <2> int_StartJob: INF - leaving
18:05:41.267 [38983] <2> sbtrestore: INF - leaving
18:05:41.267 [38983] <2> sbterror: INF - entering
18:05:41.267 [38983] <2> sbterror: INF - Error=7501: Failed to open backup file for restore. .
18:05:41.267 [38983] <2> sbterror: INF - leaving
18:05:41.710 [38983] <2> sbtrestore: INF - entering

BPRD log file from the master

18:05:39.971 [198474.198474] <2> restorefiles: Looking for RAC images
18:05:39.971 [198474.198474] <2> restorefiles: Using RAC catalog host string instance1_833229337 as browse client instance1_833229337
.
18:05:39.972 [198474.198474] <2> logconnections: BPDBM CONNECT FROM 1.2.3.4.33354 TO 4.5.6.7.1556 fd = 19
18:05:39.981 [198474.198474] <2> isDONE: reply DONE 227 <?xml version="1.0" encoding="utf-8"?><StatusMsgDoc><StatusMsg NBUStatus="227" Severity="2"
VXULoid="271" VXULtid="227"><MsgString>no entity was found</MsgString></StatusMsg></StatusMsgDoc>
.
.
18:05:39.981 [198474.198474] <2> restorefiles: Using RAC catalog host string instance2_505949071 as browse client instance2_505949071
18:05:39.981 [198474.198474] <2> ConnectionCache::connectAndCache: Acquiring new connection for host olg1provernbma01, query type 76
18:05:39.981 [198474.198474] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:5451] Local [strong] check, using interface  ANY
18:05:39.982 [198474.198474] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:5451] Local [strong] check, using interface  ANY
18:05:39.982 [198474.198474] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:5451] Local [strong] check, using interface  ANY
18:05:39.982 [198474.198474] <2> async_connect: [vnet_connect.c:2982] connect in progress 1 0x1
18:05:39.982 [198474.198474] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded
18:05:39.982 [198474.198474] <2> do_pbx_service: [vnet_connect.c:3718] via PBX bpdbm CONNECT FROM 1.2.3.4.59589 TO 4.5.6.7.1556 fd = 20
18:05:39.982 [198474.198474] <2> async_connect: [vnet_connect.c:3174] connect async CONNECT FROM 1.2.3.4.59589 TO 4.5.6.7.1556 fd = 20
18:05:39.982 [198474.198474] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO racclient 1.2.3.4 bpdbm VIA pbx
18:05:39.982 [198474.198474] <2> logconnections: BPDBM CONNECT FROM 1.2.3.4.59589 TO 4.5.6.7.1556 fd = 20
.
18:05:40.005 [198474.198474] <2> isDONE: reply DONE 0 <?xml version="1.0" encoding="utf-8"?><StatusMsgDoc><StatusMsg NBUStatus="0" Severity="0" VXULoid="271"
VXULtid="0"><MsgString>the requested operation was successfully completed</MsgString></StatusMsg></StatusMsgDoc>
18:05:40.005 [198474.198474] <2> add_image_to_list: IM fragment number -2147482648 not used to sort images
18:05:40.005 [198474.198474] <2> add_image_to_list: Null query->obj_desc detected. Backup_time = 1610445683
18:05:40.005 [198474.198474] <2> isDONE: reply DONE 0 <?xml version="1.0" encoding="utf-8"?><StatusMsgDoc><StatusMsg NBUStatus="0" Severity="0" VXULoid="271"
VXULtid="0"><MsgString>the requested operation was successfully completed</MsgString></StatusMsg></StatusMsgDoc>

.
.
18:05:40.006 [198474.198474] <2> restorefiles: Using RAC catalog host string DB3_481376991 as browse client DB3_481376991
8:05:40.007 [198474.198474] <2> logconnections: BPDBM CONNECT FROM 1.2.3.4.45489 TO 4.5.6.7.1556 fd = 21
18:05:40.056 [198474.198474] <2> isDONE: reply DONE 227 <?xml version="1.0" encoding="utf-8"?><StatusMsgDoc><StatusMsg NBUStatus="227" Severity="2"
VXULoid="271" VXULtid="227"><MsgString>no entity was found</MsgString></StatusMsg></StatusMsgDoc>

Cause

NetBackup will look for all possible images needed for the restore across all possible RAC catalog names associated with the client.  The failure occurs when the last catalog name does not have any backup images in the requested time range and an error is returned.

Solution

ETA of Fix:
Veritas  has acknowledged that the above mentioned issue  is present in the current version(s) of the product(s) mentioned at the end of this article. Veritas  is committed to product quality and satisfied customers. Please note that Veritas Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Veritas's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own This issue has been seen in all present versions.

An EEB is available, and if one is required please contact Veritas support services.