Answer / guest

Cause: The database link name you specified on the ALTER
DATABASE statement is not an ROM: link. You must specify an
ROM: link when using the ALTER DATABASE statement to mount
or open a secondary database.

Action: Re-issue the ALTER DATABASE statement using a valid
ROM: link to the database you want to mount or open. If a
valid ROM: link does not exist, create one using the CREATE
DATABASE LINK command. See the Trusted ORACLE RDBMS Guide to
Security Features for more information about creating
database links using the ROM: link type.

Please add more information about this Error

RMAN-08006: database registered in recovery catalog

1 Answers  

---

DRG-12224: use ctx_ddl.create_section_group to create section groups

1 Answers  

---

NNL-00298: No cache dump currently scheduled

1 Answers  

---

ORA-27419: unable to determine valid execution date from repeat interval

2 Answers  

---

PCC-00088: User defined type identifier expected

1 Answers  

---

RMAN-06460: Controlfile copy string cannot be backed up by proxy.

1 Answers  

---

NID-00137: All datafiles that are not dropped should be readable

1 Answers  

---

ORA-28177: incorrect Kerberos ticket version

1 Answers  

---

RMAN-06142: DEVICE TYPE cannot be specified with this command

1 Answers  

---

RMAN-20204: translation not started

1 Answers  

---

RMAN-06167: already connected

1 Answers  

---

ORA-38402: invalid name: empty string or spaces in the name

1 Answers  

---