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

EXP-00047: Missing tablespace name(s)

1 Answers  

---

RMAN-12012: multiple records for string parallelism found in catalog

1 Answers  

---

ORA-39317: illegal validation_check() call: only applys after clone/sync_code/valdation_check

1 Answers  

---

ORA-00155: cannot perform work outside of global transaction

1 Answers  

---

NNL-00509: set|show cache_checkpoint_interval [<seconds>] [<server_list>] : set|show the server's cache checkpoint interval

1 Answers  

---

---

RMAN-05010: target database must be opened in READ WRITE mode for TSPITR

1 Answers  

---

ORA-23344: constraint (string.string) does not exist

1 Answers  

---

ORA-28047: database is not a member of any enterprise domain in OID

1 Answers  

---

ORA-16058: standby database instance is not mounted

1 Answers  

---

TNS-12225: TNS:destination host unreachable

1 Answers  

---

AMD-00100: not found: string "string"

1 Answers   Wipro,

---

ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page

1 Answers  

---