Answer / guest

Cause: There are several possible causes for this message:
First, you will get this message if your username in the
second database specified was not granted the CREATE SESSION
system privilege. Second, you will get this message if the
username specified in the connect string of the database
link definition was not granted the CREATE SESSION system
privilege.

Action: The action you take depends upon the cause of the
message: In the first case, ensure that your username in the
secondary database was granted the CREATE SESSION system
privilege. In the second case, ensure the username specified
in the connect string of the database link definition was
granted the CREATE SESSION system privilege in the secondary
database.

Please add more information about this Error

RMAN-08102: channel string: located backup piece: string

1 Answers  

---

ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.

1 Answers  

---

KUP-04023: field start is after end of record

1 Answers  

---

ORA-26717: SCN limit reached

1 Answers  

---

ORA-26528: local store callback proc phase failed for 'string.string'

1 Answers  

---

O2I-00133: An error occurred for which no message is available

1 Answers  

---

ORA-19664: file type: string, file name: string

1 Answers  

---

ORA-12922: concurrent ALTER DATABASE [NO] FORCE LOGGING command is running

1 Answers  

---

ORA-01675: max_commit_propagation_delay inconsistent with other instances

1 Answers  

---

ORA-01176: data dictionary has more than the string files allowed by the controlfie

1 Answers  

---

RMAN-06169: could not read file header for datafile string error reason string

1 Answers  

---

TNS-00084: * trace_off - ask process name to turn tracing off

1 Answers  

---