When using NetBackup Database extension for Oracle, a restore fails with RMAN error ORA-27029 and NetBackup status code: 135.

Article:TECH20718  |  Created: 2002-01-13  |  Updated: 2013-04-26  |  Article URL http://www.symantec.com/docs/TECH20718
Article Type
Technical Solution

Product(s)

Issue



When using NetBackup Database extension for Oracle, a restore fails with RMAN error ORA-27029 and NetBackup status code: 135.


Error



ORA-27029: skgfrtrv: sbtrestore returned error
status code 135: client peername is invalid for restore request


Solution



Detailed Problem Description:
The master server authenticates the host requesting an Oracle RMAN restore by performing a reverse IP lookup, gethostbyaddr().  However, the packet transporting the restore request was transmitted from an interface on the client which resolves to a hostname which does not match the client name which performed the backup.  Hence, the NBU master server rejects the restore request.

The host in the following example is named devo which resolves to NIC 172.31.46.28 and has a second NIC, named devo-b which resolves to 10.1.100.10, over which the backups and restores are to occur.  The CLIENT_NAME in /usr/openv/netbackup/bp.conf is set to 'devo-b'.

The /usr/openv/netbackup/logs/bprd on the master server logged the failed validation request, peername is the result of gethostbyaddr():

 

    16:08:26 [12763] <4> get_ccname: configured name is: devo-b
    16:08:26 [12763] <2> process_request: restore request 66, bufr = 329199 66 oracle oinstall devo-b devo devo devo-b /usr/openv/netbackup/logs/user_ops/dbext/logs/11876.0.1019592506 NONE NONE 0 1019592506 1019586470 1019586470 1019592506 4 0 0 0 0 12 0 4 0 1 10004 0 0 0 C C C C C 0 1 0 1 0 0 0 0 9
    16:08:26 [12763] <2> process_request: As rcvd from client:
    16:08:26 [12763] <2> process_request: browse_clnt: devo-b
    16:08:26 [12763] <2> process_request: requesting_clnt: devo
    16:08:26 [12763] <2> process_request: destination_clnt: devo
    16:08:26 [12763] <2> process_request: clnt_bp_conf_name: devo-b
    16:08:26 [12763] <2> process_request: peername: devo-b
    16:08:26 [12763] <2> process_request: ccname: devo-b
    16:08:26 [12763] <2> process_request: keyword =
    16:08:26 [12763] <2> process_request: restore_format: 0
    16:08:26 [12763] <2> process_request: true_image: 0
    16:08:26 [12763] <2> process_request: mpx_restore_possible: 1
    16:08:26 [12763] <4> get_type_of_client_port: db_getCLIENT() failed: no entity was found (227)
    16:08:26 [12763] <2> validate_hostname: Unknown hostname devo, switching to peername devo-b.
    ...lines deleted...
    16:08:27 [12763] <4> get_type_of_client_free_browse: db_getCLIENT_by_hostname() failed: no entity was found (227)
    ...lines deleted...
    16:08:27 [12763] <16> process_request: client devo-b peername devo-b is invalid for restore request

    The error can also be verified by inspecting the progress file on the client if the /usr/openv/netbackup/logs/bprd log is not available, because the master server recorded the error in the progress file ( /usr/openv/netbackup/logs/user_ops/dbext/logs/ ):

      16:08:27 client devo-b peername devo-b is invalid for restore request
      16:08:28 INF - Server status = 135

    Likewise, the /usr/openv/netbackup/logs/dbclient log on the Oracle database host also reflects progress file entry, rejecting the restore request:

            System name:      SunOS
            Node name:      devo
            Release:      5.8
            Version:      Generic_108528-12
            Machine:      sun4u
            User name:        oracle
            Group name:       oinstall
            Client Host:       devo
      ...lines deleted...
      15:29:02 [26493] <4> sendRequest: sending RESTORE request to bprd
      15:29:02 [26493] <4> sendRequest:    request: <oracle oinstall devo-b devo devo devo-b /usr/openv/netbackup/logs/user_ops/dbext/logs/26493.0.1019590142 NONE NONE 0  1019590142 1019586470 1019586470 1019590142 4 0 0 0 0 12 0 4 0 9047 10004 0 0 0 C C C C C 0 1 0 1 0 0 0 0 9>
      15:29:02 [26493] <2> getsockconnected: host=nbu service=bprd address=10.1.100.29 protocol=tcp non-reserved port=13720
      15:29:02 [26493] <2> bind_on_port_addr: bound to port 52000
      15:29:02 [26493] <2> bprd_connect: no authentication required
      15:29:03 [26493] <4> sendRequest: sending buf = 1019586470 1019586470 /cf_TRMAN2_t459959266_s112_p1
      15:29:03 [26493] <4> sendRequest: Date range: <-s 04/23/02 14:27:50>, <-e 04/23/02 14:27:50>
      15:29:03 [26493] <4> serverResponse: entering serverResponse.
      15:29:03 [26493] <4> serverResponse: initial client_read_timeout = <900>
      15:29:08 [26493] <4> serverResponse: read comm file:<15:29:04 client devo-b peername devo-b is invalid for restore request>
      15:29:08 [26493] <4> serverResponse: read comm file:<15:29:05 INF - Server status = 135>
      15:29:08 [26493] <16> serverResponse: ERR - server exited with status 135: client is not validated to perform the requested operation
      ...lines deleted...
      15:29:08 [26493] <4> closeApi: INF - EXIT STATUS 5: the restore failed to recover the requested files

    Additional Environment Information:

    Solution:
    Add REQUIRED_INTERFACE = <CLIENT_NAME> to the /usr/openv/netbackup/bp.conf file on the client host.  

    Example:
      CLIENT_NAME = devo-b  
      REQUIRED_INTERFACE = devo-b
    Oracle 8.1.6, Solaris 2.6/Solaris 7/Solaris 8, HP-UX 11.00/HP-UX 11.11



Legacy ID



248249


Article URL http://www.symantec.com/docs/TECH20718


Terms of use for this information are found in Legal Notices