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-30116: syntax error at 'string' following 'string'

1 Answers  

---

ORA-01981: CASCADE CONSTRAINTS must be specified to perform this revoke

1 Answers  

---

CLSR-00506: Unmatched resource name prefix string is specified

1 Answers  

---

ORA-27125: unable to create shared memory segment

1 Answers  

---

ORA-10614: Operation not allowed on this segment

1 Answers  

---

ORA-15073: diskgroup string is mounted by another ASM instance

1 Answers  

---

LPX-00014: context is not clean

1 Answers  

---

RMAN-06220: Creating automatic instance

1 Answers  

---

SQL*Loader-00433: no attributes found for column object string in table string

1 Answers  

---

ORA-28137: Invalid FGA audit Handler

1 Answers  

---

KUP-04055: column string is both a field in the data file and a column transform

1 Answers  

---

ORA-12453: label string already exists

1 Answers  

---