FranklinFaces.com - Oracle & SQL Server Database Forums for all IT Professionals / Oracle Forum / RMAN - Error Codes / RMAN-06000-06999

RMAN-06059: expected archived log not found.

stacyliang83 — Thu, 15 Jan 2009 21:38:30 GMT

I got this error code for RMAN and I couldn't figure it out for a long time. Then, I finally did after some research so I'm putting my findings here.

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability.

If archived redo logs are deleted/moved/compressed by accident or if you have some scripts that clear your flash recovery area or what ever you was done to remove from disk without being backed up, the rman catalog will not know this has happened, and will keep attempting to backup the missing archived redo logs. That will cause rman archived redo log backups to fail altogether with an error like the one mentioned above.

If you can, you should bring back the missing archived redo logs to their original location and name, and let rman back them up. But if that is impossible, the workaround is to “crosscheck archivelog all”. Here is sample:

rman <connect target /
connect catalog username/password@catalog
run {
allocate channel c1 type disk ;
crosscheck archivelog all ;
release channel c1 ;
}
EOF

You’ll get output like this:

[i]validation succeeded for archived log
archive log filename=/u05/oradata/archive/redoarch_1038.arc recid=1017 stamp=611103638[/i]

for every archived log as they are all checked on disk. That should be the catalog fixed, run an archivelog backup to make sure.

Hope this helps.

Thanks,
Stacy

RMAN-06429: TARGET database is not compatible with this version of RMAN

Admin — Thu, 17 Dec 2009 03:02:56 GMT

Hi,

My archive log destination directory was getting filled up and i got alert that thresholds had been reached. I didn't know why until i looked at the archive log script backup log. This is what it showed in the log:

RMAN-06003: ORACLE error from target database:
ORA-04031: unable to allocate 41152 bytes of shared memory ("shared pool","DBMS_RCVMAN","PL/SQL MPCODE","BAMIMA: Bam Buffer")
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_RCVMAN"

RMAN-06438: error executing package DBMS_RCVMAN in TARGET database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06429: TARGET database is not compatible with this version of RMAN

I tried to login to rman manually to see what was going on and got the same error:

# rman

Recovery Manager: Release 10.2.0.3.0 - Production on Thu Dec 17 00:36:09 2009

RMAN> connect target /

ORACLE error from target database:
ORA-04031: unable to allocate 41152 bytes of shared memory ("shared pool","DBMS_RCVMAN","PL/SQL MPCODE","BAMIMA: Bam Buffer")
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_RCVMAN"

error executing package DBMS_RCVMAN in TARGET database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06429: TARGET database is not compatible with this version of RMAN

RMAN> exit

I then logged into sqlplus to check the rman packages to see because there was no recent upgrades of any kind.

# sqlplus '/ as sysdba'

SQL*Plus: Release 10.2.0.3.0 - Production on Thu Dec 17 00:36:31 2009

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options

SQL> SQL> select dbms_rcvman.getpackageversion from dual;
select dbms_rcvman.getpackageversion from dual
*
ERROR at line 1:
ORA-04031: unable to allocate 41152 bytes of shared memory ("shared
pool","DBMS_RCVMAN","PL/SQL MPCODE","BAMIMA: Bam Buffer")

I tried flushing my shared_pool and then checked to see how large my shared_pool was:

SQL> alter system flush shared_pool;

System altered.

SQL> select dbms_rcvman.getpackageversion from dual;
select dbms_rcvman.getpackageversion from dual
*
ERROR at line 1:
ORA-04031: unable to allocate 41152 bytes of shared memory ("shared
pool","DBMS_RCVMAN","PL/SQL MPCODE","BAMIMA: Bam Buffer")

SQL> show parameter shared_pool

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
shared_pool_reserved_size big integer 10M
shared_pool_size big integer 200M

Shared_pool size was small .. so i increased it and that fixed the problem:

SQL> alter system set shared_pool_size=300m;

System altered.

SQL> select dbms_rcvman.getpackageversion from dual;

GETPACKAGEVERSION
--------------------------------------------------------------------------------
08.00.04.00

backup is now running ok.

Hope this helps.

RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row

Admin — Thu, 21 May 2009 14:22:50 GMT

Hi,

I got the following error message when trying to connect to rman:

/u01/oradba/rman/config > rman

Recovery Manager: Release 10.2.0.3.0 - Production on Thu May 21 14:14:01 2009

RMAN> connect target /

connected to target database: PROD (DBID=1824257732)
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-19921: maximum number of 64 rows exceeded

I went online and every where searching for it but couldn't find a solution and then i immediately remembered that i had my laptop connect at home with another session that was already connected to rman. So i checked out ps command to see any other rman command connected and yup i was right. I killed it:

/u01/oradba/rman/config > ps -aef|grep rman
oracle 165 22875 0 21:45:59 pts/8 4:41 rman
oracle 19379 6839 0 14:14:54 pts/13 0:00 grep rman

prodnj54db1*PROD-(oracle)
/u01/oradba/rman/config > kill -9 165

prodnj54db1*PROD-(oracle)
/u01/oradba/rman/config > rman

Recovery Manager: Release 10.2.0.3.0 - Production on Thu May 21 14:15:04 2009

RMAN> connect target /

connected to target database: PROD (DBID=1824257732)

RMAN> connect rcvcat rman/rmanpasswd@rmancat

connected to recovery catalog database

RMAN>

The kill command did the trick.

Hope this helps. Do let me know if this helped you out.

===========================================================

Oracle Error :: RMAN-06901

WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows

Cause

Informational message only.

Action

No action required.

RMAN-06207: WARNING: 2170 objects could not be deleted for DISK channel(s) due

Admin — Thu, 09 Jul 2009 14:46:38 GMT

I was getting the following message when trying to backup the archive logs:

RMAN-06207: WARNING: 2170 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects

To resolve this i had to run a crosscheck command. I tried the traditional crosscheck and still the error kept coming so i had to do the following:

RMAN> connect target /
connected to target database: P655 (DBID=2454151442)

RMAN> connect rcvcat rman/rmanpassword@catalog

connected to recovery catalog database

RMAN> change archivelog all crosscheck;

Crosschecked 2202 objects

After doing this, it got rid of the message.

Solars 10 - running Oracle 10.2.0.3

Thanks,