Hi Gino,
Yes as the above posts mentioned,
00055, 00000, "maximum number of DML locks exceeded" is caused as it ran out of DML lock state objects. To resolve this increase the value of the DML_LOCKS initialization parameter (in your case initopenview.ora file) and warm start the database.
DML_LOCKS is an integer type parameter and the default value is tables referenced for each transaction (derived ├Г 4 * transactions). Since it is a static parameter, when changed the database as to be re-started for the change to be effective. Range os values is 20 to unlimited, and it varies for different releases. (Note: a setting of 0 disables enqueues). There is no maximum value to this parameter. You can set this parameter to any value. Setting this parameter to a very large value will consume more memory within the shared pool.
Here is a short description about DML_LOCKS
A DML lock is a lock obtained on a table that is undergoing a DML operation (insert, update, delete). DML_LOCKS specifies the maximum number of DML locks--one for each table modified in a transaction. The value should equal the grand total of locks on tables currently referenced by all users.
For example, if three users are modifying data in one table, then three entries would be required. If three users are modifying data in two tables, then six entries would be required
The default value assumes an average of four tables referenced for each transaction. For some systems, this value may not be enough.
Enqueues are shared memory structures that serialize access to database resources. If you set the value of DML_LOCKS to 0, enqueues are disabled and performance is slightly increased. However, you cannot use DROP TABLE, CREATE INDEX, or explicit lock statements such as LOCK TABLE IN EXCLUSIVE MODE.
Oracle holds more locks during parallel DML than during serial execution. Therefore, if your database supports a lot of parallel DML, you may need to increase the value of this parameter.
Indira
Never give up, Keep Trying
