Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16136: Managed Standby Recovery not active
- 2 Answers
- 23127 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-13206: internal error [string] while creating the spatial index
TNS-01401: Class: string
TNS-04073: Passwords do not match.
RMAN-20034: resync not needed
ORA-16530: invalid buffer or length
ORA-31072: Too many child nodes in XMLType fragment for updateXML
QSM-01081: no primary key or row id found for table, string, in MV, string
ORA-07647: sszfck: $OPEN failure
NNL-00853: Renames refused, new name already exists: number
ORA-16721: unable to set LOG_ARCHIVE_DEST_n parameters
ORA-09874: TASDEF_READ: read error, unable to read tasdef@.dbf file.
ORA-22954: This multiset operation is not supported for this element type.
Oracle Errors 
