ORA-12001: cannot create log: table 'string' already has a
trigger
- 1 Answers
- 3425 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: Materialized view logs are filled by a trigger on the
master table. That trigger cannot be created.
Action: To create a materialized view log, drop the current
trigger on the master.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 1 No |
Post New Answer View All Answers
ORA-16516: The current state is invalid for the attempted operation.
ORA-26032: index string.string loading aborted after string keys
NZE-28868: Peer certificate chain check failed.
if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires
ORA-26082: load of overlapping segments on table string.string is not allowed
ORA-26079: file "string" is not part of table string.string
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-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-26084: direct path context already finished
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
IMP-00070: Lob definitions in dump file are inconsistent with database.
NZE-28890: Entrust Login Failed
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
ORA-26029: index string.string partition string initially in unusable state
ORA-26030: index string.string had string partitions made unusable due to:
