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

The Oracle Backup Failed and an Error Message Indicates: Communication with the server has not been initiated or the server status has not been retrieved from the server (status code 6)

Publication Date:  2015-07-29 Views:  38 Downloads:  0
Issue Description
The Oracle 11g R1 database backup failed and the status code is 6. The log information in the backup script:

channel ch01: starting piece 1 at 08/07/2012 18:45:33
RMAN-03009: failure of backup command on ch00 channel at 08/07/2012 19:00:58
ORA-19506: failed to create sequential file, name="al_208_1_790713933", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   VxBSACreateObject: Failed with error:
   Server Status:  Communication with the server has not been initiated or the
server status has not been retrieved from the server
channel ch00 disabled, job failed on it will be run on another channel
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch01 channel at 08/07/2012 19:00:58
ORA-19506: failed to create sequential file, name="al_209_1_790713933", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   VxBSACreateObject: Failed with error:
  Server Status:  Communication with the server has not been initiated or the
server status has not been retrieved from the server


Product and version information:
  • The NetBackup version: NetBackup 7.0
  • The Oracle database version: Oracle 11g R1
Handling Process
1.  Change the client host name in the backup script to the backup client name.

Change NB_ORA_CLIENT=vmcp1a in the backup script to NB_ORA_CLIENT=nbuvmcp1a.

2.  Restart the backup service.
Root Cause
1.  View /etc/hosts of the Oracle database server, IP addresses of the client and HDP3500E, and the host name resolution information.

vmcp1a:~ # cat /etc/hosts
#
# hosts         This file describes a number of hostname-to-address
#               mappings for the TCP/IP subsystem.  It is mostly
#               used at boot time, when no name servers are running.
#               On small systems, this file can be used instead of a
#               "named" name server.
# Syntax:
#
# IP-Address  Full-Qualified-Hostname  Short-Hostname
#

127.0.0.1       localhost

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts
192.168.125.36 nbuvmcp1a
172.16.50.36 vmcp1a
172.16.50.37 vmcp1b
172.16.50.34 scpshare_ip
172.16.50.35 smpshare_ip
${hostsInfo}
192.168.125.106   hdp3500e


2.  View /usr/openv/netbackup/bp.conf of the Oracle database server. The client information recorded is CLIENT_NAME = nbuvmcp1a.

The system host name and backup client name of the Oracle database server are vmcp1a and nbuvmcp1a respectively. Therefore, the system host name is inconsistent with the backup client name.

3.  View the host name information about the client in the Oracle database backup script.

The corresponding information in the backup script:

ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
send 'NB_ORA_SERV=hdp3500e,NB_ORA_CLIENT=vmcp1a,NB_ORA_POLICY=vmcp1_db';
BACKUP
    $BACKUP_TYPE
    SKIP INACCESSIBLE
    TAG $tag
    FILESPERSET 5
    # recommended format
    FORMAT 'bk_%s_%p_%t'
    DATABASE;
    sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;


The client host name in the backup script is vmcp1a. It is the client system host name instead of the backup client name. This causes the backup service failure.
Suggestions
The operating system manages the host name and the backup system manages the backup client name. When backup software client programs are installed, the default system host name is the backup client name. If the backup client name needs to be different from the system host name to facilitate backup system management or meet requirements of network environments in some cases, use the backup client name instead of system host name in backup.

END