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
- 2994 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 |
NNL-00533: ping [<server_list>] : ping one or more Names servers
ORA-31605: the following was returned from string in routine string: LPX-number: string
ORA-28155: user 'string' specified as a proxy is actually a role
TNS-01153: Failed to process string: string
ORA-19575: expected string blocks in file string, found string
IMG-00553: invalid rotate value
ORA-16001: database already open for read-only access by another instance
ORA-36988: (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
ORA-29961: too many warnings occurred in the execution of ODCIIndex DDL routine
ORA-36268: (XSCGMDLAGG01) 'string' is not a valid dimension value.
PCC-02357: Function calls may not be used as host variable expressions
LPX-00101: parameter-entity markup cannot be split up
Oracle Errors 
