RMAN-08135: some corrupt blocks found during conversion of
file string
Answer Posted / guest
Cause: While converting the specified file from one platform
to another, some corrupt blocks were discovered in the
specified file. Details about the corruption have been
written to a server trace file.
Action: If these corrupt blocks are unexpected, you may be
able to use Block Media Recovery at the source database to
fix the problem, then re-convert the files.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-26027: unique index string.string partition string initially in unusable state
ORA-16627: No standby databases support the overall protection mode.
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.............
RMAN-05017: no copy of datafile number found to recover
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.
ORA-26082: load of overlapping segments on table string.string is not allowed
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26079: file "string" is not part of table string.string
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-16626: failed to enable specified object
ORA-26095: unprocessed stream data exists
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.