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.
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.
# IP-Address Full-Qualified-Hostname Short-Hostname
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
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';
# recommended format
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.
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.