Answer / guest

Cause: The pipe that RMAN needs to use for its input or
output is either a public pipe or a private pipe that is not
owned by SYS. This is a potential security problem, because
it allows a non-SYS user to issue commands to RMAN or to
retrieve the RMAN output.

Action: 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.create_pipe
function to explicitely create the pipe as a private pipe.

Please add more information about this Error

ORA-13267: error reading data from layer table string

1 Answers  

---

DRG-11225: Third-party filter timed out.

1 Answers  

---

PLS-00379: CASE statements are not included in this release of PL/SQL

1 Answers  

---

LFI-00118: Unable to change type to Unknown.

1 Answers  

---

ORA-33084: (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify the dimensioned valueset workspace object.

1 Answers  

---

ORA-13764: Value "string" is illegal as a result percentage.

1 Answers  

---

SQL-02113: Unable to open message file

1 Answers  

---

ORA-06444: ssvpstev: Failed with unexpected error number.

1 Answers  

---

ORA-07239: slemrd: invalid file handle, seals do not match.

1 Answers  

---

LRM-00116: syntax error at 'string' following 'string'

1 Answers  

---

SQL*Loader-00556: unable to allocate read buffer

1 Answers  

---

RMAN-06027: no archive logs found that match specification

1 Answers  

---