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

NNL-00020: warning: no TNSNAMES.ORA file and no preferred name servers in SQLNET.ORA

1 Answers  

---

ORA-09844: soacon: Archmon unable to open named pipe.

1 Answers  

---

ORA-00078: cannot dump variables by name

1 Answers  

---

ORA-12433: create trigger failed, policy not applied

1 Answers  

---

ORA-23427: deferred purge queue argument string out of range

1 Answers  

---

ORA-19616: output filename must be specified if database not mounted

1 Answers  

---

ORA-36999: (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specifed when creating any non-surrogate grouping id.

1 Answers  

---

ORA-25441: duplicate column value for table alias: string

1 Answers  

---

LSX-00234: invalid decimal "~S"

1 Answers  

---

ORA-06790: TLI Driver: poll failed

1 Answers  

---

ORA-13765: Value "string" is illegal for a result limit.

1 Answers  

---

ORA-23353: deferred RPC queue has entries for object group "string"."string"

1 Answers  

---