Trying to create a seq. dump of a table, I get an "error 113". It is also not possible to update the table.
We are talking about tttxt001 and tttxt002.

In Baan threre is no app.lock concerning this tables.

Is there a way in oracle to remove a lock?

Hi spartacus,

Is your database Oracle?

If it is true, please check your dml_locks value in init.ora.

Use this to determine the locks:

set pagesize 25
column object_name format a20

select c.id1, c.sid, o.object_name, s.sid, s.serial#, s.osuser, s.username
from v$lock c, dba_objects o, v$session s
where c.id1 = o.object_id
and c.sid = s.sid;


after that:

alter system kill session (#,#)

with the numbers found.

Spartacus,

Killing sessions after determining locks possible using above query/command. I searched "error 113" into KQ, here is info -

- Table Update Lock
When a table has been locked with an Update Lock, then the table is in Read Only mode. Update actions on the table are suspended till the Update Lock is released. (This action differs from the Baan action to lock a table. A process which has put such kind of lock on a table can perform any action on that table. All other processes which try to do an update action will get error EFLOCKED (113).

The procedure for backup will be now:
1) Put Database Lock
2) Put Update Lock on all tables to be backed up.
3) Release Database Lock
Since each table which has to be backed up is locked now, the lock for the database can be released. The status (contents) of the database as it is backed up, is the status at the moment of releasing this lock. Processes which were waiting for some read action on a locked table can continue now.
4) Release table’s Update Lock
When a table is backed up, its lock can be released. From that moment on, also updates are allowed on this table. Processes which were waiting for some update action on a locked table can continue when the table’s lock has been released.
5) All locks on all tables are released.
Update and read actions can be done on all tables.

Hope this helps.

-Suhas