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-39311: illegal clone_recovery() call: it only applys to failed clones

1 Answers  

---

ORA-28024: must revoke grants of external roles to this role/user

1 Answers  

---

ORA-30071: conversion between datetime/interval and string fail

1 Answers  

---

ORA-30160: Unable to access the file

1 Answers  

---

QSM-01121: materialized view, string, is TRUSTED in ENFORCED integrity mode

1 Answers  

---

ORA-16090: archive log to be replaced not created by managed standby process

1 Answers  

---

ORA-29319: datafile string is not correct

1 Answers  

---

ORA-09709: soacon: failed to accept a connection.

1 Answers  

---

ORA-14298: LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

1 Answers  

---

TNS-00227: Unable to contact pump; Connection Manager declared pump dead

1 Answers  

---

TNS-02403: Bad alias string or alias not present in tnsnames.ora

1 Answers  

---

ORA-16047: DGID mismatch between destination setting and standby

1 Answers  

---