Hmmmmm, maybe I am doing something wrong, but....

- I open 2 instances of ISQL.EXE

- In ISQL1 I write: SELECT * FROM CLIENTS;

- In ISQL2 I write: SELECT MON$TIMESTAMP, MON$TRANSACTION_ID FROM
MON$STATEMENTS;

- In ISQL1 I write: COMMIT;

- In ISQL2 I write: SELECT MON$TIMESTAMP, MON$TRANSACTION_ID FROM
MON$STATEMENTS;

- In ISQL1 I write: SELECT * FROM CLIENTS;

- In ISQL2 I write: SELECT MON$TIMESTAMP, MON$TRANSACTION_ID FROM
MON$STATEMENTS;

In all cases, ISQL2 shows me the same data, nothing change. So I can not
see the transaction's timestamp or Id of the transactions started by ISQL1.

ISQL2 absolutly ignores that happens in the ISQL1 instance.

Is there a way to know in ISQL2 the transaction's data started by ISQL1?

Version 2.5.2, SuperServer, Windows 7

Greetings.

Walter.


On Thu, Jan 22, 2015 at 1:50 PM, Svein Erling Tysvær
[email protected] [firebird-support] <
[email protected]> wrote:

>
>
> >I looked in a database, and in MON$STATEMENTS tabla I have the following
> fields:
>
> MON$STATEMENT_ID
> MON$ATTACHMENT_ID
> MON$TRANSACTION_ID
> MON$STATE
> MON$TIMESTAMP
> MON$SQL_TEXT
> MON$STAT_ID
>
> >How can I detect which is the record I have to delete to unlock my
> record? This is the only table I have to modify?
>
> I typically just look at the mon$sql_text with a mon$timestamp that seems
> to be the correct one.
>
> HTH, Set
>
> -------- Mensaje original -------
> >> May be I can modify or delete some record in any MON$ table or do some
> other thing?
>
> >I typically locate and delete records from MON$STATEMENTS. Mind you, that
> is 2.5 and typically when I have a long-
> >running query. Don't know whether deleting from this table is possible or
> safe with 2.1 or sensible WITH LOCK.
>  
>

Reply via email to