RMAN-10014: PL/SQL error 306: Wrong Number Or Types Of Arguments In Call
(Doc ID 1274019.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.5 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03010: fatal error during library cache pre-loading
RMAN-10015: error compiling PL/SQL program
RMAN-10014: PL/SQL error 0 on line 26 column 7: Statement ignored
RMAN-10014: PL/SQL error 306 on line 26 column 7: wrong number or types of arguments in call to 'FILERESTORED'
RMAN-10014: PL/SQL error 0 on line 13 column 7: Statement ignored
RMAN-10014: PL/SQL error 306 on line 13 column 20: wrong number or types of arguments in call to 'FETCHFILERESTORED'
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03010: fatal error during library cache pre-loading
RMAN-10015: error compiling PL/SQL program
RMAN-10014: PL/SQL error 0 on line 26 column 7: Statement ignored
RMAN-10014: PL/SQL error 306 on line 26 column 7: wrong number or types of arguments in call to 'FILERESTORED'
RMAN-10014: PL/SQL error 0 on line 13 column 7: Statement ignored
RMAN-10014: PL/SQL error 306 on line 13 column 20: wrong number or types of arguments in call to 'FETCHFILERESTORED'
The above error can occur on connection to either target or catalog.
The procedure identified, in this case FILERESTORED/FETCHFILERESTORED will vary.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |