Oracle schedule backup fails with error The NMDA error message has been lost. Set NSR_DEBUG_LEVEL to a value greater than 0 and run NMDA.

Resumen: Oracle schedule backup fails with error The NMDA error message has been lost. Set NSR_DEBUG_LEVEL to a value greater than 0 and run NMDA.

Este artículo se aplica a: Este artículo no se aplica a: Este artículo no está vinculado a ningún producto específico. En este artículo no se identifican todas las versiones de los productos.

Síntomas

Rman stack ended up with error message:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on CH1 channel at 02/16/2022 11:07:59
ORA-19506: failed to create sequential file, name="ej0lvn8i_1_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:


   The NMDA error message has been lost. Set NSR_DEBUG_LEVEL to a value greater than 0 and run NMDA.

NMDA operational log display error message:
02/16/22 14:17:30 (pid 86766): 02/16/22 14:17:30.767781 lgto_auth for `nsrmmd' failed: no matching devices for save of client `Oracle hostname'; check storage nodes, devices or pools
02/16/22 14:17:30 (pid 86766): 02/16/22 14:17:30.767800 Unable to acquire the user credentials for direct save nsrmmd authentication: no matching devices for save of client `Oracle hostname'; check storage nodes, devices or pools.
(pid = 86766) (02/16/22 14:17:30.767843) no matching devices for save of client `Oracle hostname'; check storage nodes, devices or pools.

Causa

Corruption observed in the peer certificate after operating system updating and NetWorker upgrade performed.

Resolución

Clear peer information from the NetWorker client, NetWorker server, and NetWorker Storage Node (if applicable).

1. To stop the NetWorker processes on Linux host:
a. On sysVinit enabled Linux machines, type /etc/init.d/networker stop
b. To rename /nsr/res/nsrladb run: mv /nsr/res/nsrladb /nsr/res/nsrladb_old

2. Clear peer information from NetWorker server and NetWorker storage node for this client.

NetWorker server:

a. From root/admin command prompt on NetWorker server run: nsradmin -p nsrexecd
b. From nsradmin prompt run: delete type: nsr peer information; peer hostname: client_name
Note: for client_name use the client name as it appears in the clients tab of the Management Console. For example, if FQDN use FQDN, and vice versa. It is recommended to also check for additional entries, such as shortname.
c. When prompted if you would like to delete, type yes and press enter.
 
If the backup for this client passes through a remote NetWorker storage node; meaning, not the NetWorker server, delete the peer information for the client from the Storage Node:

a. From root/admin command prompt on NetWorker server run: nsradmin -p nsrexecd
b. From nsradmin prompt run: delete type: nsr peer information; peer hostname: client_name
Note: For client_name use the client name as it appears in the clients tab of the Management Console. For example, if FQDN use FQDN, and vice versa. It is recommended to also check for additional entries, such as shortname.
c. When prompted if you would like to delete, type yes and press enter.

3. Start networker client service on client: /etc/init.d/networker start

Información adicional

Other methods for stopping and starting services:

Stopping:
nsr_shutdown
Or 
systemctl stop networker

Starting:
systemctl start networker
Propiedades del artículo
Número de artículo: 000197098
Tipo de artículo: Solution
Última modificación: 28 sept 2022
Versión:  4
Encuentra las respuestas que necesitas con la ayuda de otros usuarios de Dell
Servicios de asistencia
Comprueba si tu dispositivo está cubierto por los servicios de asistencia.