DB_ERR_ORA_00057 is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: & - Text Include (no Short Dump, only Text Module)
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Please see ora information for more details about the possible cause of this runtime error and how it could be avoided.
Maximum number of DDL locks exceeded
Try performing the last operatoin again in the hope that the number of
locks has decreased again.
If this situation persists, notify the database administrator. S/he can
increase the maximum number of DDL locks in the DB profile.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Your program or transaction has triggered a DDL operation in ORACLE in
order to create a table or index, or to modify these. This operation
involves changes in the ORACLE Data Dictionary. A DDL lock is required
for these.
The DDL lock could not be set, as the maximum number of DDL locks in
the systen was exceeded.
The maximum number of DDL locks was exceeded when your program or
transactoin requested a lock.