The PIPE option obtains its input from, and writes its output to, an Oracle database pipe in the target database.
The user attempted to modify the configuration which cannot be changed for a BACKUP or STANDBY control file while the mounted control file was either BACKUP or STANDBY.
The following configurations can be changed only when connected to primary database instance that has CURRENT/CREATED control file type mounted: CONFIGURE RETENTION POLICY CONFIGURE EXCLUDE CONFIGURE ENCRYPTION CONFIGURE DB_UNIQUE_NAME RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified Point-in-Time.
An attempt was made to restore the datafile/archived logs/ control file/SPFILE using a previous existing backup.
A RECOVER COPY command was not able to proceed because no copy of indicated file was found to recover. no copy of indicated file exists on disk that satisfy the criteria specified in the user's recover operands. copy of indicated datafile exists on disk but no incremental backup was found to apply to the datafile copy.
Either: -) The control file mounted by the auxiliary database does not have an entry for this datafile, therefore file name conversion is not possible.
-) A COPY DATAFILE TO AUXNAME command was issued, but no auxname was set for this datafile.
This happened because the current recovery catalog was not in use at the specified Point-in-Time.
A list of tablespaces with undo segments was supplied.
If you are attempting to put data on the RMAN input pipe prior to starting RMAN, so RMAN will process the data on the pipe as soon as it starts, you must be connected as SYS and you must first use the DBMS_PIPE.