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

ORA-06578: output parameter cannot be a duplicate bind

1 Answers  

---

ORA-09319: slgtd: unable to obtain the current date and time

1 Answers  

---

NID-00131: Control file is not current

1 Answers  

---

ORA-12920: database is already in force logging mode

1 Answers  

---

DRG-11708: too many thesauri

1 Answers  

---

ORA-00360: not a logfile member: string

1 Answers  

---

PCB-00002: Command line processor severe error

1 Answers  

---

ORA-00304: requested INSTANCE_NUMBER is busy

1 Answers  

---

RMAN-08515: archive log filename=string thread=string sequence=string

1 Answers  

---

ORA-19682: file string not in block media recovery context

1 Answers  

---

RMAN-04020: target database name "string" does not match channel's name: "string"

1 Answers  

---

ORA-39502: failed to notify CRS of a Startup/Shutdown event [number] (ignored)

1 Answers  

---