Interested to Buy Any Domain ? << Click Here >> for more details...
SQL*Loader-00259: Could not escalate DDL share lock to
exclusive on table string
- 1 Answers
- 2887 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: This error occurs when another user has a parse lock
on the table, for example, when another user is doing a
select on the table. The parse lock should clear momentarily.
Action: Give the parse lock a chance to clear and then retry
or else use the conventional path load.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
LPX-00250: invalid attribute declaration
ORA-28501: communication error on heterogeneous database link
RMAN-06416: PROXY ONLY was specified and some files could not be proxy copied
ORA-07680: sou2os: another call to ORACLE currently executing
PCC-00072: Input file name length exceeds the maximum length
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?
ORA-01692: unable to extend lob segment string.string partition string by string in tablespace string
ORA-16641: failure to acquire broker configuration metadata lock
PLS-00201: identifier 'string' must be declared
ORA-39064: unable to write to the log file
ORA-27001: unsupported device type
QSM-01004: no query rewrite before view merging
Oracle Errors 
