ORA-16136: Managed Standby Recovery not active
- 2 Answers
- 22430 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-28264: Client identifier is too long
ORA-15092: I/O request size string is not a multiple of logical block size string
ORA-24417: Session pool size has exceeded the maximum limit
ORA-13459: GeoRaster metadata SRS error
NNL-01052: Server has been running for: string
PLS-00561: character set mismatch on value for parameter 'string'
ORA-31403: change table string already contains a column string
DRG-10828: token string is longer than maximum length for column string
ORA-00379: no free buffers available in buffer pool string for block size stringK
ORA-14104: RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
NZE-29031: SSL handshake is required.
ORA-15033: disk 'string' belongs to diskgroup "string"
Oracle Errors 
