I think NMO 4.5 works only with NW 7.4.x. Are you using NW 7.4.x clients?

Which Nw client, OS and Oracle versions are you running?

But install guide says "NetWorker client release 7.4 or later (with all applicable patches) must be installed on the Oracle host."

I love when they do this!!

Legato Server: Sun StorageTek EBS version 7.4.Build.187
Legato Client: VERSION: 7.4,REV=187
Oracle: 10.1.0
OS: SunOS 5.9 Generic_122300-13 sun4u sparc SUNW,Ultra-4

Message was edited by:
mpsh356

SCG says Nw 7.2 and up for NMO 4.5.

Hi !

I have the same error. In my case:
Oracle 10gR2 64bit
Networker serwer 7.4.1 (EBS 7.4+patch)
Networker client 7.4 or 7.4.1 (EBS 7.4+patch)
Solaris 10U4

Any ideas ?

Hello,
Have you created the NWORA resource file ?
Otherwise execute 'nsrnmoadmin.exe'


To enable instant backups and catalog synchronization, specific NWORA resources
must be added to the file with the nsrnmoadmin program.
The NWORA resource file is created by the nsrnmoadmin program when it is run for the
first time.
===============================================================
To create the NWORA file execute the following from command prompt.form the file
server
.
nsrnmoadmin.exe -r add sid=< Valid SID value of
the Oracle database..> home=< Valid pathname of the Oracle home directory.> connect= tns=< Valid pathname of Oracle network configuration directory.>
===============================================================

After executing the command the NWORA file (nwora.res) will be available under directory.

for more detail please refer to
EMC® NetWorker®Module for Oracle Release 4.5
Multiplatform Version
Administration Guide
P/N 300-003-563
REV A01


With Regards
Hemant Joshi.
Bangalore India.

Yes, I saw techfile about nwora.res. But this is not a case. I've found solution - NMO 4.2 works from first hit. But looks like NMO 4.5 64bit + EBS 7.4 on Solaris are causing problems. Strange, that no-one saw this before.

Maybe because it works fine for the others. That still can indicate specific configuration issue

Yes - that is exactly what I meant. Strange that no-one hit this problem before. But I cannot find any misconfiguration. I should mention that there is cluster installed (SC3.2)

Alan