Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16136: Managed Standby Recovery not active
- 2 Answers
- 23075 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / guest
Cause: An attempt was made to cancel a managed recovery
session but no managed recovery session was active.
Action: No action is necessary.
Please add more information about this Error
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / kvijayakumar
When i encoutered this error i followed this procedure
created standy control from primary database.
renamed the standby controlfile as control01.ctl to the
secondary database.
shutdown both primary and secondary database
copied the database files from primary to secondary
(coldbackup)
made the secondary database up in mount state.
opened the primary database
| Is This Answer Correct ? | 3 Yes | 5 No |
ORA-28102: policy does not exist
AMD-00107: no root level in hierarchy: "string"
QSM-01009: materialized view, string, matched query text
ORA-16167: LGWR network server could not switch to non-blocking mode
O2F-00331: A syntactically illegal name was seen in the INTYPE file
ORA-25296: Queue Table string has a buffered queue string
ORA-38423: Attribute set created from an ADT may not be extended.
ORA-30990: insufficient privileges to change owner of resource string
ORA-13143: invalid POLYGON window definition
ORA-15067: command or option incompatible with diskgroup redundancy
TNS-01028: Listener Log File string
ORA-02142: missing or invalid ALTER TABLESPACE option
Oracle Errors 
