Home » RDBMS Server » Backup & Recovery » RMAN-00554: initialization of internal recovery manager package failed (Oracle 9i Release 2 64Bit - Production on SPARC 5.8)
icon8.gif  RMAN-00554: initialization of internal recovery manager package failed [message #494030] Fri, 11 February 2011 01:15 Go to next message
drovnik
Messages: 34
Registered: January 2011
Location: Gaborone, Botswana
Member
I have recently patched my catalog home to 9208 from 9204; the target database is still on 9204 but now I cannot connect to the catalog database.



oracle@mogw:TES1:/u01/app/oracle/admin/TES1/bdump
rman rcvcat rman/rman@RMANDB

Recovery Manager: Release 9.2.0.4.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04004: error from recovery catalog database: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
oracle@mogw:TES1:/u01/app/oracle/admin/TES1/bdump

[/error]

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494031 is a reply to message #494030] Fri, 11 February 2011 01:28 Go to previous messageGo to next message
hkchital
Messages: 128
Registered: September 2008
Location: Singapore
Senior Member
The database instance "RMANDB" is not running. It was shutdown or it has crashed. Check the alert.log for RMANDB.


Hemant K Chitale

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494035 is a reply to message #494030] Fri, 11 February 2011 01:48 Go to previous messageGo to next message
Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator
The catalog database must be open if you want to use it for your RMAN session.
(The target database does not need to be open.)

Regards
Michel

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494036 is a reply to message #494031] Fri, 11 February 2011 01:50 Go to previous messageGo to next message
drovnik
Messages: 34
Registered: January 2011
Location: Gaborone, Botswana
Member
Nope, the RMANDB is up and running I can connect to it just fine .
The funny is when I issue

##> sqlplus rman/rman (it connect)

but when I issue
##> sqlplus rman/rman@RMANDB (it does connect and gives message below)

morojwa:RMANDB:/u01/app/oracle/product/RMANDB/dbs
sqlplus rman/rman@RMANDB

SQL*Plus: Release 9.2.0.8.0 - Production on Fri Feb 11 09:45:14 2011

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494037 is a reply to message #494036] Fri, 11 February 2011 01:52 Go to previous messageGo to next message
drovnik
Messages: 34
Registered: January 2011
Location: Gaborone, Botswana
Member
Both database nodes are open (read write) I can do a tnsping to both from either of the nodes.
Is it possible this is caused by the catalog database being 9208 and the target da 9204 ; I read
that it should work fine as the code level is 9.2.x .

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494040 is a reply to message #494037] Fri, 11 February 2011 02:04 Go to previous messageGo to next message
Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator
Quote:
Both database nodes are open (read write) I can do a tnsping to both from either of the nodes

A tnsping does not prove the database is open, just that the listener is there and listening for what you ask.

Quote:
sqlplus rman/rman@RMANDB (it does connect and gives message below)

So this instance is not started and open.

Regards
Michel

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494042 is a reply to message #494040] Fri, 11 February 2011 02:17 Go to previous messageGo to next message
drovnik
Messages: 34
Registered: January 2011
Location: Gaborone, Botswana
Member
The instance is started.



Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
JServer Release 9.2.0.8.0 - Production

SQL> select name, open_mode from v$database;

NAME OPEN_MODE
--------- ----------
RMANDB READ WRITE

SQL>

[/output]

I cannot connect remotely even from any dba tool, TOAD, SQLDeveloper, etc.

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494045 is a reply to message #494042] Fri, 11 February 2011 02:36 Go to previous messageGo to next message
Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator
No, it is not.
I trust Oracle over you.
If you want to convince me then execute and copy and paste the result of:
sqlplus rman/rman@RMANDB
followed by
select name, open_mode from v$database;

Regards
Michel

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494048 is a reply to message #494045] Fri, 11 February 2011 02:52 Go to previous messageGo to next message
drovnik
Messages: 34
Registered: January 2011
Location: Gaborone, Botswana
Member
v$database is not available to rman user. But see below.



morojwa:CCBET:/u01/app/oracle/product/CCBET/network/admin
. oraenv
ORACLE_SID = [CCBET] ? RMANDB
morojwa:RMANDB:/u01/app/oracle/product/CCBET/network/admin
sqlplus rman/rman@RMANDB

SQL*Plus: Release 9.2.0.8.0 - Production on Fri Feb 11 10:49:55 2011

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.


Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
JServer Release 9.2.0.8.0 - Production

SQL> select name,open_mode from v$database;
select name,open_mode from v$database
*
ERROR at line 1:
ORA-00942: table or view does not exist


SQL>

[/OUT]

With sys



morojwa:RMANDB:/u01/app/oracle/product/CCBET/network/admin
sqlplus "/as sysdba"

SQL*Plus: Release 9.2.0.8.0 - Production on Fri Feb 11 10:51:49 2011

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.


Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
JServer Release 9.2.0.8.0 - Production

SQL> select name,open_mode from v$database;

NAME OPEN_MODE
--------- ----------
RMANDB READ WRITE

SQL>

[/OUT]

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494049 is a reply to message #494048] Fri, 11 February 2011 03:04 Go to previous messageGo to next message
knight
Messages: 111
Registered: January 2009
Senior Member
post 
lsnrctl status
and 
lsnrctl services
from node where rmandb is running


initially you posted
Quote:
but when I issue
##> sqlplus rman/rman@RMANDB (it does connect and gives message below)

morojwa:RMANDB:/u01/app/oracle/product/RMANDB/dbs
sqlplus rman/rman@RMANDB

SQL*Plus: Release 9.2.0.8.0 - Production on Fri Feb 11 09:45:14 2011

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory


and now you say it gets connected?

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494051 is a reply to message #494048] Fri, 11 February 2011 03:10 Go to previous messageGo to next message
drovnik
Messages: 34
Registered: January 2011
Location: Gaborone, Botswana
Member
Yes initially that was the case I could not connect to the database in that way. If I specify the db_name in the connect string it did not connect. Having taken a closer look at the listener.ora file I have found that the oracle home running the catalog database was cloned and therefore the OracleHome had changed. The database is registered in the listener.ora file when the listener startup. The wrong OracleHome was used in the listener.ora file. I found it and sorted it out. I can now connet remotely from any tool.



Quote:

LSNR_RMANDB =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = moar)(PORT = 2130))
)
)
)

SID_LIST_LSNR_RMANDB =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = RMANDB)
(ORACLE_HOME = /u01/app/oracle/product/92040)
(SID_NAME = RMANDB)
)
)





!!! Correct OracleHome should have been . Thanks Knight I would not have looked there had you not asked me to post those outputs.

/u01/app/oracle/product/RMANDB

!!!

Report message to a moderator

Re: RMAN-00554: initialization of internal recovery manager package failed [message #494058 is a reply to message #494051] Fri, 11 February 2011 03:24 Go to previous message
Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator
Quote:
I would not have looked there had you not asked me to post those outputs.

Because it is OBVIOUS for us that a DBA knows that when he uses @... then he uses tnsnames.ora and he should have first looked at this file.

Regards
Michel

Report message to a moderator

Previous Topic: Database recovery with missing one of the archivelog
Next Topic: restore with rman
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Nov 21 21:41:43 CST 2024
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.