Answer Posted / bhuvneshwar singh
ORA-38706 "Cannot turn on flashback database logging"
ORA-38709 "Recovery area is not enabled"
Solution :
1. do the proper shutdown of database (shut normal,immediate).
2. start up database in mount phase ( startup mount).
3. set this parameter one by one
a.ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=2G
SCOPE=BOTH;
B.ALTER SYSTEM SET DB_RECOVERY_FILE_DEST=/HOME/FRA
SCOPE=BOTH;
4. ALTER DATABASE OPEN;
5. NOW USE THIS COMMAND AND CHECK IT OUT WHETHER FLASHBACK
AREA IS ENABLED ?
SELECT NAME, FLASHBACK_ON FROM V$DATABASE;
I am sure this information will help you a lot
Regards
Bhvuneshwar singh
Is This Answer Correct ? | 6 Yes | 2 No |
Post New Answer View All Answers
IMG-02003: 2FF03 - incorrect color histogram feature specification
[ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) Unsuccessful: alter table user.CEN_USER_MASTER add constraint FKF4EDEDC3D0BAAE75 foreign key (ROLE_ID) references user.CEN_ROLE_MASTER [ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) ORA-02275: such a referential constraint already exists in the table
IMP-00070: Lob definitions in dump file are inconsistent with database.
NZE-28868: Peer certificate chain check failed.
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
ORA-16516: The current state is invalid for the attempted operation.
ORA-26032: index string.string loading aborted after string keys
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26095: unprocessed stream data exists
IMP-00064: Definition of LOB was truncated by export
RMAN-05017: no copy of datafile number found to recover
ORA-26082: load of overlapping segments on table string.string is not allowed
ORA-26027: unique index string.string partition string initially in unusable state
ORA-26029: index string.string partition string initially in unusable state
ORA-16627: No standby databases support the overall protection mode.