NetWorker

Last reply by 07-04-2022 Unsolved
Start a Discussion
2 Bronze
2 Bronze
230

Unable to take Oracle RMAN backup from Solaris.

Hi All, 

We have our core banking DB running on Solris 11, oracle DB 19c version. The databases are two node (RAC). Generally we take the backup from node1 every time. For the last one month, we are trying to take the backup from NMC but every time it failed showing the below error: 

                                         RMAN-03009: failure of allocate command on CH1 channel at 06/22/2022 13:20:26
                                         ORA-19554: error allocating device, device type: SBT_TAPE, device name:
                                         ORA-27211: Failed to load Media Management Library

We can take file system backup from the same server using NMC but unable to take RMAN backup. NMDA's configuration looks ok but is unable to take backup. Support case logged already but still no hope.

1. libok.so link is created several time, but still no result.

2. We can initiate oracle backup using RMAN script the node itself via networker server and take backup on the same pool which is used for RMAN backup from NMC. But somehow NMC backup is failing every time showing same error.

3. ddpconnchk showing every data domain path is successful.

4. NMDA version 19.3.0.6

 

 

 

 

Replies (2)
2 Bronze
2 Bronze
229

@crazyrov , hope you could help.

3 Argentum
119

from the NMDA 19.3 administration guide:

If RMAN fails with the following error, ensure that NMDA and Oracle have the same bitness. Refer to the RMAN user guide for details on how to test that you have integrated the media management library correctly:
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 25

Has above been ruled out? As also stated in https://www.dell.com/support/kbdoc/en-us/000079670/networker-ora-27211-failed-to-load-media-manageme...


Ensure that have the correct bit number as the Oracle server.  i.e. if Oracle is 32-bit, you need to have the 32-bit version of NMDA.  If Oracle is 64-bit, you would need the 64-bit version of NMDA.

We have to take you on your word, that the relinking is actually done correctly, without specifying what the link is and where it is linked to? Also stated in above KB article?


Double check that as per part of the install process you have correctly linked NMDA with Oracle.  This can be referenced in the NMDA install guide, and as an example on Linux it looks as the following.

cd $ORACLE_HOME/lib
ln -s /usr/lib/libnsrora.so libobk.so

Were you already running nw and nw nmda 19.3.0.6 successful before? Or did it start failing after updating to nw19.3?

Doesn't setting a higher NSR_DEBUG_LEVEL show more info?

https://www.dell.com/support/kbdoc/en-us/000043312/rman-backup-in-rac-environment-is-randomly-failin... states another possible cause in a RAC env, when:


Cause

  1. Client is configured in Networker server using the Oracle SCAN hostname.
  2. Target Database Net service name used by the backup is defined using the Oracle SCAN hostname in DB server TNSNAMES.ORA.

Resolution

  1. Don t use the Oracle SCAN hostname as client name in Networker.
    • Select and use one of the node's VIP hostnames in the RAC system. (using a node physical name should work but it is preferred to use the VIP name for client indexing considerations)
  2. Make sure the Net Service Name of the Oracle target database is not defined in DB Server TNSNAMES.ORA by using the RAC SCAN hostname.
    • If that is the case, then ask the DBA to create new service name for the target DB, like  SID-RMAN   or  SID-LOCAL  and define it using the local host name, like the following example:
mySID-LOCAL=
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = local_host_name)(PORT = 1661))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SID = mySID)
    )
  )

  • The DBA should create the service name in each RCA node.

Additional Information

The provided resolution steps are not required for NMDA 9.2.
  • The NetWorker client can be configured using the RAC SCAN hostname.
  • The target DB service can be defined using the RAC SCAN hostname in TNSNAMES.ORA

 

Then again, the additonal info states, the resolution steps are not required for NMDA9.2, without stating if it can even encounter the same issue or if it would require another approach. I assume the former?

Latest Solutions
Top Contributor