RMAN Register Database Problem

[JGolightly]

I'm in OEM trying to register a database held on a remote machine. I'm getting the following failure :


Recovery Manager: Release 8.1.5.0.0 - Production

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database: ORA-12154: TNS:could not resolve service name
child process exited abnormally
Last Message : The job failed

I can administer the database via OEM, so my Net8 settings seem ok. What could be the problem ?

[omegamark]

Go to the DOS mode and try using the sqlplus command .
Try first connect the target database
Try connecting the catalog database ...

See for any errors ...

Mostly this is a TNS problem only ...

[JGolightly]

OK. Managed to register database by using dos commands to connect:
rman target xxx/xxx@rovflt catalog yyy/yyyy@rcv

My tnsnames entry for rovflt is :

ROVFLT =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = jgolightly2)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = rovflt.companyname.com)
)
)

My tnsnames entry for rcv is same format.

Any ideas why OEM was giving me the error ?

[sambavan]

Check the tnsnames.ora file under OEM directory and configure it properly (if you have installed OEM under different directory). Otherwise search for all the tnsnames.ora files in your system and check they all the same and try again... Also I'ld check the sqlnet.ora for the Names qualifier if any and correct them accordingly...

Sam

[JGolightly]

Still stuck. My tnsnames files are the same now. Sqlnet has no names qualifier in it.
I can connect to database fine using sql*plus and OEM, but it seems to be when RMAN is connecting that it's not happy and is giving me the old ORA-12154: TNS:could not resolve service name error.
What does RMAN do differently ? Any ideas welcome

[sambavan]

Were you able to create a simple sql query job on the instances, and execute them successfully?

FYI: It could be the OEM backup bug that was fixed on 8.1.6 through a patch. If you call oracle, they would suggest that you upgrade to OEM 2.2 where they have fixed the bug.

Sam

[JGolightly]

SQL job runs fine. Can create users etc also. Just can't seem to get the backup stuff running.

Is it possible to get OEM 2.2 for free (other than with developers licence) ?

[reydp]

If your RMAN catalog is in different server
then configure your tnsnames in both server
to have an entry for both database server.
And in OEM tnsnames as well.
And try again.

Keep it cool.

[JGolightly]

TNSNames.ora is same in both Oracle and OEM directories and on the server I'm trying to access. Still no joy !

[sambavan]

Download it from technet. On such case you would also have to download the Oracle 8i and update your listener with 8.1.7 listener.

Remember RMAN runs on the command prompt and not under SQL. So make sure that you have the correct username and password for the node. The node username and password have to be the server user login name and password.

Sam

[Edited by sambavan on 09-21-2001 at 11:29 AM]