Unsolved

This post is more than 5 years old

4 Posts

4667

March 22nd, 2012 03:00

lnm_index_cfx_connect retry failed. See privious error messages

Hi all,

The Oracle resource on one of my projects is trying to restore from an RMAN backup and is getting the following error:

Channel ORA_SBT_TAPE_4: NMO v5.0.0.0

ORA-19870: error while restoring backup piece ABCD_20120111_qrn0asf_1_1

ORA-19507: failed to retrieve sequential file, handle="ABCD_20120111_qm0asf_1_1", parms=""

ORA-27029: skgfrtrv: sbtrestore returned error

ORA-19511: Error received from media manager layer, error test:

lnm_index_cfx_connect retry failed. See previous error messages. (3:3:13)

Initially the retention/browse time of the backups had expired, so we scanned them back in and extended the retension and browse time until the middle of next month. 

We can now browse for these save sets in the catalog and they're listed as browsable.  However he still appears to be unable to restore these save sets. 

Any suggestions as where to look?

544 Posts

March 22nd, 2012 15:00

Also you have to check the remote access on the source and target machines, as well as adding the source client into the target client's host file.

Please check the following Powerlink articles that may be helpful also:

https://solutions.emc.com/emcsolutionview.asp?id=esg117358

https://solutions.emc.com/emcsolutionview.asp?id=esg83533

Thanks,

Ahmed Bahaa

544 Posts

March 22nd, 2012 15:00

Hi matei,

It seems that it can't find the index, may be that because it can't communicate with the NetWorker server  or that the index isn't correct. 

Try to check the NetWorker indexes on the NetWorker server by running the following:

nsrinfo –n oracle CLIENTNAME

and for sure check the communication between the server and the client ( connectivity and name resolution )

Thanks,

Ahmed Bahaa

4 Posts

March 26th, 2012 01:00

Hello,

I believe that the issue involves incorrect syntax in the Oracle scripts.  Thanks for the helpful suggestions, once I know for certain I'll post back with what caused the issue.

No Events found!

Top