DB_ERR_ORA_00058 SAP ABAP Runtime Error db err ora 00058

DB_ERR_ORA_00058 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.

DB_ERR_ORA_00058 ABAP Runtime Error

Please see ora information for more details about the possible cause of this runtime error and how it could be avoided.

Time limit exceeded while waiting for a DDL lock You need to wait until the other user's lock on this table is released.
In some cases, this lock is not released until the SAP system is switched off, as the locks might belong to DB cursors that are in an internal SAP cursor cache and are not released. 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. This DDL lock could not be set, as another user has already set it. A DDL lock was already set for the object that wanted to lock your transaction or program.

Old version:
Your DB transaction has requested a DDL lock (lock on a table whose structure you want to modify) from the database system. The lock could not be set, as another user has also set a DDL lock or a DML lock (lock on data in the table).