Hi,

Intools have a locking process.

All the sestion store in the current info.

When I say connect to domain schem it's mean to connect to the project you face with the locing problem.

Each project (domain) store the connection information in the project table in admin schema(in_dbamn\in_dbamn) you need to connect first to the admin schema find the relevant project get the user and password and connect to domain schema.

you can run this SQL through Inernal setup.

If it's not oracle you can change the sql to delete from current_info; commit;

Ilan

Regards

Ilan

Hi Ilan,

Today, I just got another "The tag is locked" but did not mention specifically who has locked it and this occurs in specification module when assigning tag number to a spec form. FYI, I run the sql below:

select * from current_info where V_message <> ' ';

And I noticed that the V-Message column has some remark stating "686504#WEST_AMPA4_E-50134#P_JUSTINA#BSP\SERS0BSP0105#07-OCT-2008 09:15:58". Then when I run the sql below :

truncate table current_info;

And this occurs --> ORA-00054: resource busy and acquire with NOWAIT specified

Please advise if I miss anything.

Have a nice :) day.

Hi Ilan,

Please see below. FYI... WEST_AMPA4 is just to retrieve the information from where the locking is originating. Our INtools is version 06.00.06.06.

select s.sid, s.serial#, s.osuser, s.program, s.logon_time, s.terminal, s.schemaname from v$session s where schemaname like 'WEST_AMPA4%';

SELECT s.sid,
       s.serial#,
       s.osuser,
       s.program,
       s.logon_time,
       s.terminal,
       s.schemaname
FROM   v$session s;

ALTER SYSTEM KILL SESSION '27,451';

FYI, if I login to the domain (WEST_AMPA4), the system unable to execute as I encounter "ORA-01031: insufficient privileges". Therefore I login to IN_DBAMN (ie system level) then execute the KILL then the locking was removed.

Hope this will help for those who have similar problem.