ORA-16802: downgrading log transport mode from SYNC disallowed
Answer Posted / guest
Cause: An attempt was made to downgrade the log transport
mode of a standby database from SYNC to ASYNC or ARCH when
the configuration was in Maximum Protection or Maximum
Availability mode and the primary database was a RAC
database. This is not allowed, even if there are other
standby databases with log transport modes set to SYNC to
support the data protection mode.
Action: You can do one of the following if you need to
downgrade the log transport mode of the standby: (1) Shut
down all instances of the primary database and restart one
instance with initialization parameter CLUSTER_DATABASE set
to FALSE. Downgrade the log transport mode, shutdown the
instance, and restart all instances with CLUSTER_DATABASE
set to TRUE. (2) Downgrade the protection mode to Maximum
Performance mode first. Then downgrade the log transport
mode, then upgrade the protection mode again (which involves
a shutdown and restart of the primary database). Note that
the above only works when there exists at least one more
standby database in the configuration that has the log
transport mode set to SYNC.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-26079: file "string" is not part of table string.string
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26027: unique index string.string partition string initially in unusable state
ORA-16516: The current state is invalid for the attempted operation.
IMP-00064: Definition of LOB was truncated by export
ORA-26095: unprocessed stream data exists
ORA-26028: index string.string initially in unusable state
ORA-26094: stream format error: input column overflow
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
RMAN-05017: no copy of datafile number found to recover
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
IMP-00070: Lob definitions in dump file are inconsistent with database.