Rman with commvault mml: database crash while delete obsolete

Question

Hello!
I have a problem concerning RMAN, delete obsolete and CommVault media management library: Every night at 23:00 we run a RMAN "Backup" to delete the obsolete backup files from tape. Since the update to CommVault agent 8 (from version 7) the database crashes while the delete obsolete command. The normal backup (incremental 0/1) works without problem.
After restarting the database i tried the delete obsolete via shell -> same result: CRASH.
The CommVault support says that there is an Oracle bug with different MML's, that causes this behaviour - but i can't find anything at Metalink.
This is the output of RMAN (tell me which other logs can be helpful):
RMAN-Sperr-Policy wird f³r den Befehl angewendet
RMAN-Sperr-Policy ist auf ein Recovery-Fenster von 0 Tagen festgelegt
Die folgenden veralteten Backups und Kopien werden gel÷scht:
Typ Schl³ssel Abschlusszeit Dateiname/Handle
Backup Set 7 01.09.10
Backup Piece 12 01.09.10 c-190884945-20100901-01
Backup Set 9 01.09.10
Backup Piece 17 01.09.10 c-190884945-20100901-02
M÷chten Sie die obigen Objekte wirklich l÷schen (geben Sie YES oder NO ein)? yes
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: Abbruchfehler bei der Ausf³hrung des Befehls
ORA-12514: TNS: Listener kann in Connect-Deskriptor angegebenen Service aktuell nicht aufl÷sen -> listener can not resolve service name
RMAN-03009: Fehler bei delete Befehl in ORA_MAINT_SBT_TAPE_1 Kanal auf 09/02/2010 08:57:37 -> error at delete command
ORA-03135: connection lost contact
Recovery Manager nicht kompatibel mit TARGET Datenbank: RMAN 14155912.14155908.14312748.1 bis 1651797107.0.27143.0 erforderlich -> recovery not compatible with TARGET database
Best regards,
Christian

Answer 1

Hi,
show parameter plsq
plsql_code_type           string     INTERPRETED
plsql_compiler_flags          string     INTERPRETED, NON_DEBUG
That database is in interpreted mode.
Check also the pacakages:
select OWNER, OBJECT_NAME , PARAM_NAME ||'='||PARAM_VALUE param from DBA_STORED_SETTINGS where OBJECT_NAME in ( 'DBMS_RCVCAT','DBMS_RCVMAN' )and param_name = 'plsql_code_type'
OWNER               OBJECT_NAME
PARAM
SYS               DBMS_RCVMAN plsql_code_type=INTERPRETED
SYS               DBMS_RCVMAN plsql_code_type=INTERPRETED
If it is native you have an issue!
François,