ORA-38708: not enough space for first flashback database log
file
- 2 Answers
- 11757 Views
- I also Faced
- E-Mail Answers
Answer Posted / sabbir rayhan,dba
GIVE THE MORE SPACE TO 'DB_RECOVERY_DEST_SIZE'.FIRST SEE
THE RECENT SPACE FROM DB_RECOVERY_DEST_SIZE,IF IT IS NOT
MORE THEN INCREASE .
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
ORA-26032: index string.string loading aborted after string keys
ORA-26079: file "string" is not part of table string.string
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-16626: failed to enable specified object
IMG-02003: 2FF03 - incorrect color histogram feature specification
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
ORA-26084: direct path context already finished
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?
RMAN-05017: no copy of datafile number found to recover
ORA-26082: load of overlapping segments on table string.string is not allowed
ORA-16627: No standby databases support the overall protection mode.
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
IMP-00064: Definition of LOB was truncated by export
