No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Oracle Database Recovery Fails and Error Message "ORA-27191: sbtinfo2 returned error" Is Displayed

Publication Date:  2015-07-29 Views:  41 Downloads:  0
Issue Description
The product versions are as follows:

HDP3500E master server: NetBackup 7.0.1, SUSE 11 SP1 x64
Oracle database server: Oracle 10.2.0.1 SUSE 11 SP1 x64

Run the following script to restore the parameter file spfile of the Oracle database:

RMAN> RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
SEND 'NB_ORA_SERV=hdp3500a04, NB_ORA_CLIENT=slot03';
RESTORE SPFILE FROM 'bk_u06mgecm1_s6_p1_t755446465';
RELEASE CHANNEL ch00;
}2> 3> 4> 5> 6>


The following information is displayed during restoration:

using target database control file instead of recovery catalog
allocated channel: ch00
channel ch00: sid=36 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
sent command to channel: ch00
Starting restore at 02-JUL-11
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/02/2011 14:32:56
ORA-27191: sbtinfo2 returned error
Additional information: 2
Handling Process
1.  Change the host name of the master server in the restoration script of the parameter file.

The restoration script of the parameter file is as follows:
RMAN> RUN { ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE'; SEND 'NB_ORA_SERV=hdp3500a04, NB_ORA_CLIENT=slot03'; RESTORE SPFILE FROM 'bk_u06mgecm1_s6_p1_t755446465'; RELEASE CHANNEL ch00; }2> 3> 4> 5> 6>
NB_ORA_SERV=hdp3500e04 indicates the host name of the HDP3500E master server. Change this host name to the actual host name of the HDP3500E master server.

2.  Perform the restoration again.
Root Cause
Possible Causes:

Error ORA-27191 is caused by the HDP3500E master server that is connected to the Oracle database.

Fault Diagnosis:
To further identify problem causes, enable the NetBackup debugging function to collect more logs.

1.  On the Oracle database server, run the mklogdir script to create a directory for storing debugging logs.

NOTE:
By default, the NetBackup client does not provide the mklogdir script. You can copy this script from the /usr/openv/netbackup/logs directory on the HDP3500E master server to the same directory on the NetBackup client.

2.  Create the dbclient directory under /usr/openv/netbackup/logs/ on the Oracle database server.

3.  Restore the spfile file.

4.  Check the database restoration logs generated in dbclient.

14:32:56.649 [8222] <2> int_GetMMInfo: INF - Initialized Signal
14:32:56.649 [8222] <2> int_GetMMInfo: INF - support for Proxy Copy enabled
14:32:56.796 [8222] <4> int_ProcessCommandString: INF - cmd_key=<NB_ORA_SERV> cmd_val=<hdp3500a04>
14:32:56.796 [8222] <2> int_ProcessCommand: INF - Server <hdp3500a04> will be used for this API session.
14:32:56.796 [8222] <4> int_ProcessCommandString: INF - cmd_key=<NB_ORA_CLIENT> cmd_val=<slot03>
14:32:56.796 [8222] <2> int_ProcessCommand: INF - Client <slot03> will be used for this API session.
14:32:56.866 [8222] <2> setup_connect_options: gethostbyname failed for hdp3500a04: HOST_NOT_FOUND (1)
14:32:56.866 [8222] <2> setup_connect_options: cannot find host: hdp3500a04, h_errno=1
14:32:56.866 [8222] <2> nb_connect_to_vnetd_or_legacy: ../../../nb/lib/comm.c.2017: setup_connect_options failed: 48 113
14:32:56.866 [8222] <2> bprd_connect: Cannot connect to server hdp3500a04 automatically: 48
14:32:56.866 [8222] <2> bprd_connect: Cannot connect to server hdp3500a04
14:32:56.866 [8222] <2> bprd_connect:    errno = 0 - Success
14:32:56.866 [8222] <2> bprd_get_features: bprd_connect(hdp3500a04) failed, cannot connect on socket (25)
14:32:56.866 [8222] <2> setup_connect_options: gethostbyname failed for hdp3500a04: HOST_NOT_FOUND (1)
14:32:56.866 [8222] <2> setup_connect_options: cannot find host: hdp3500a04, h_errno=1
14:32:56.866 [8222] <2> nb_connect_to_vnetd_or_legacy: ../../../nb/lib/comm.c.2017: setup_connect_options failed: 48 113
14:32:56.866 [8222] <2> bprd_connect: Cannot connect to server hdp3500a04 automatically: 48
14:32:56.866 [8222] <2> bprd_connect: Cannot connect to server hdp3500a04
14:32:56.866 [8222] <2> bprd_connect:    errno = 0 - Success
14:32:56.866 [8222] <2> bprd_get_features: bprd_connect(hdp3500a04) failed, cannot connect on socket (25)
14:32:56.866 [8222] <2> setup_connect_options: gethostbyname failed for hdp3500a04: HOST_NOT_FOUND (1)
14:32:56.866 [8222] <2> setup_connect_options: cannot find host: hdp3500a04, h_errno=1
14:32:56.866 [8222] <2> nb_connect_to_vnetd_or_legacy: ../../../nb/lib/comm.c.2017: setup_connect_options failed: 48 113
14:32:56.866 [8222] <2> bprd_connect: Cannot connect to server hdp3500a04 automatically: 48
14:32:56.866 [8222] <2> bprd_connect: Cannot connect to server hdp3500a04
14:32:56.866 [8222] <2> bprd_connect:    errno = 0 - Success
14:32:56.866 [8222] <2> bprd_get_features: bprd_connect(hdp3500a04) failed, cannot connect on socket (25)
14:32:56.867 [8222] <16> bsa_checkFeatureId: unable to check if feature <36> is licensed
14:32:56.867 [8222] <16> bsa_checkFeatureId: Server exit status = 25: cannot connect on socket
14:32:56.867 [8222] <16> xbsa_ValidateFeatureId: ERR - VxBSAValidateFeatureId: Failed with error:

   Server Status:  cannot connect on socket
14:32:56.867 [8222] <16> int_GetImageInfo2: ERR - Failed to get info on backup file, bk_u06mgecm1_s6_p1_t755446465.
14:32:56.885 [8222] <4> sbtend: INF - --- END of SESSION ---


5.  The log analysis result shows that the Oracle database fails to connect to host hdp3500a04 during restoration.

6.  Check the host name of the master server. The host name is not hdp3500a04. However, hdp3500a04 is used as the host name in the restoration script of the parameter file.

END