Error List
RMAN-10026 network error number-number occurred registering connection
Description:
RMAN-10026 network error number-number occurred registering connection
Cause:
A network error occurred while attempting to register the target database connection to test for RPC completion. This is an internal error that should not be issued.
RMAN-10027 could not locate network layer context
Description:
RMAN-10027 could not locate network layer context
Cause:
Recovery Manager could not locate a necessary context area while attempting to register the target database connection to test for RPC completion. This is an internal error that should not be issued.
RMAN-10024 error setting up for rpc polling
Description:
RMAN-10024 error setting up for rpc polling
Cause:
The Recovery Manager could not create the RPC polling context which is required to test for RPC completion. This message should be accompanied by other error messages indicating the cause of the error.
RMAN-10025 connection is already registered for events
Description:
RMAN-10025 connection is already registered for events
Cause:
The Recovery Manager could not enable the target database connection to test for RPC completion. This is an internal error that should not be issued.
RMAN-06143 LIKE may only be specified with COPY
Description:
RMAN-06143 LIKE may only be specified with COPY
Cause:
The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, control files, or archive logs have file names that may be tested with a LIKE operand.
RMAN-03019 async RPCs are NOT working
Description:
RMAN-03019 async RPCs are NOT working
Cause:
The RPCTEST command has determined that RPCs are not executing asynchronously. Instead, they are blocking. This is caused by using a SQL*Net driver that does not support non-blocking UPI.
RMAN-03020 async RPC test will take 1 minute
Description:
RMAN-03020 async RPC test will take 1 minute
Cause:
This is an informational message.
PLS-00319 subquery in an IN or NOT IN clause must contain exactly one column
Description:
PLS-00319 subquery in an IN or NOT IN clause must contain exactly one column
Cause:
An invalid expression such as X IN (SELECT A,B …) was used. When a [NOT]IN clause is used with a subquery, it does not test for set membership. The number of expressions in the [NOT]IN clause and the subquery select list must match. So, in the example above, the subquery must specify at most one column.