Answer / guest

Cause: All instances in the physical standby database were
put into a log-apply-off state instead of read-only.

Action: Issue the set state command to move the database to
read-only state.

Please add more information about this Error

ORA-37080: Advice requested for hierarchy with too many levels

1 Answers  

---

ORA-01290: cannot remove unlisted logfile string

1 Answers  

---

ORA-25020: renaming system triggers is not allowed

1 Answers  

---

ORA-29511: could not resolve Java class

1 Answers  

---

ORA-25003: cannot change NEW values for this column type in trigger

1 Answers  

---

TNS-01174: The sum of the POOL_SIZEs from each PRESPAWN_DESC is greater than the PRESPAWN_MAX

1 Answers  

---

ORA-04012: object is not a sequence

1 Answers  

---

PLS-00421: synonym definitions nested too deeply; possible loop in synonyms

1 Answers  

---

PLS-00573: cannot constrain scale, precision, or range of an anchored type declaration

1 Answers  

---

ORA-30653: reject limit reached

2 Answers  

---

ORA-13408: invalid blockSize storage parameter

1 Answers  

---

ORA-27018: BLKSIZE is not a multiple of the minimum physical block size

1 Answers  

---