[Firebird-devel] TCS on ARM

[Damyan I. <da...@mo...>]

-=| Damyan Ivanov,  1.04.2007 13:00 |=-
> -=| Alex Peshkov,  1.04.2007 11:14 |=-
>> On Saturday 31 March 2007 13:54, Damyan Ivanov wrote:
>>> Still needs to be tested if it works when installed.
>> Damyan, did you try TCS?
> 
> No. I'll try to arrange it with Alan.

Thanks to Alan's continuous generous hosting, I've given TCS a try.
There are problems :( I am not sure this is ARM-related, since I have
problems completing the fuill TCS on my i686 too, though the problems
on ARM seem different.

Firebird SuperServer 2.1 Alpha 1, ARM, build 15688

I post here the diffs in hope someone would have an idea where to look
further.

Here's a summary:

These two seem like a change in isql -x. Perhaps TCS should be adopted
to the change (if not already, the CVS checkout I am using is several
days old).

CF_ISQL_21:
32 c 32,35
<
---------------------------------------------
> /* Domain definitions */
> CREATE DOMAIN RDB$1 AS INTEGER;
> CREATE DOMAIN RDB$2 AS INTEGER;
>
++++++++++++++++++++++++++++++++++++++++++++++++++

CF_ISQL_22:
33 c 33,35
<
---------------------------------------------
> /* Domain definitions */
> CREATE DOMAIN RDB$1 AS INTEGER;
>
++++++++++++++++++++++++++++++++++++++++++++++++++

ISC_ERRSET:
1 a 1,58
> gbak:cannot commit index RDB$FOREIGN3
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object JOB is in use
> gbak:cannot commit index RDB$FOREIGN6
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object DEPARTMENT is in use
> gbak:cannot commit index RDB$FOREIGN8
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object EMPLOYEE is in use
> gbak:cannot commit index RDB$FOREIGN9
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object EMPLOYEE is in use
> gbak:cannot commit index RDB$FOREIGN10
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object DEPARTMENT is in use
> gbak:cannot commit index RDB$FOREIGN13
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object PROJECT is in use
> gbak:cannot commit index RDB$FOREIGN15
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object EMPLOYEE_PROJECT is in use
> gbak:cannot commit index RDB$FOREIGN16
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object EMPLOYEE_PROJECT is in use
> gbak:cannot commit index RDB$FOREIGN18
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object PROJ_DEPT_BUDGET is in use
> gbak:cannot commit index RDB$FOREIGN19
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object PROJ_DEPT_BUDGET is in use
> gbak:cannot commit index RDB$FOREIGN21
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object SALARY_HISTORY is in use
> gbak:cannot commit index RDB$FOREIGN23
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object CUSTOMER is in use
> gbak:cannot commit index RDB$FOREIGN25
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object SALES is in use
> gbak:cannot commit index RDB$FOREIGN26
> gbak: ERROR:lock conflict on no wait transaction
> gbak: ERROR:    unsuccessful metadata update
> gbak: ERROR:    object SALES is in use
> gbak:Database is not online due to failure to activate one or more
indices.
> gbak:Run gfix -online to bring database online without active indices.
++++++++++++++++++++++++++++++++++++++++++++++++++

DSQL_DOMAIN_13:
instead of result set, we have:
> Statement failed, SQLCODE = -901
> invalid transaction handle (expecting explicit transaction start)
> After line 48 in file domain_13.sql
> Statement failed, SQLCODE = -901
> invalid transaction handle (expecting explicit transaction start)
> After line 49 in file domain_13.sql
...numerous times...

$ cat ../output/DSQL_DOMAIN_20.diff
34 a 34,36
> Statement failed, SQLCODE = -901
> invalid transaction handle (expecting explicit transaction start)
> After line 4 in file domain_20b.sql
++++++++++++++++++++++++++++++++++++++++++++++++++

$ cat ../output/DSQL_DOMAIN_21.diff
49 a 49,51
> Statement failed, SQLCODE = -901
> invalid transaction handle (expecting explicit transaction start)
> After line 5 in file domain_21b.sql
++++++++++++++++++++++++++++++++++++++++++++++++++

$ cat ../output/DSQL_DOMAIN_22.diff
52 a 52,54
> Statement failed, SQLCODE = -901
> invalid transaction handle (expecting explicit transaction start)
> After line 7 in file domain_22b.sql
++++++++++++++++++++++++++++++++++++++++++++++++++

All the SQL_EVENTS series hang, endlessly writing 0xFF to the output.

I stop here with the hope someone can advise where to look.


	dam
-- 
Damyan Ivanov            JabberID: da...@ja...