stupid bug in HDR
IDS921UC4
this statement fails on secondary server
create temp table t
( fld1 char(10) not null unique
) with no log ;
626: Cannot obtain or set serial value.
140: ISAM error: operation illegal on a DR Secondary
however this statement succeeds on secondary server}
create temp table t
( fld1 char(10) not null
) with no log ;
create unique index t_u on t(fld1);
Isn't it a bug. Both statements are effectively the same:- one maintains
uniqueness thru constraint
and the other thru unique index.
Is this bug reproducible in later version(s).
I think what you 've got is a bug, but your version is too old.
I 've tested it in 9.30.FC5 and have found the same behaviour you
found in 9.21, also have tested in 9.40.UC2 and I 've found a
different error code, but it fails with both test cases:
229: Could not open or create a temp file.
140: ISAM error: operation illegal on a DR Secondary.
Which is weird, because you should be able to do sorting and temp
tables on the secondary server.
from 9.40 documentation:
"When HDR is working, the primary database server is online and
accepts
updates and queries just as a standard database server does. The
secondary
database server is in logical-recovery mode and cannot accept SQL
statements
that result in writes to disk (except for sorting and temporary
tables)."
esteban.-
"rkusenet" <rkusenet@sympatico.ca> wrote in message news:<30u763F351h8rU1@uni-berlin.de>...
> IDS921UC4
>
> this statement fails on secondary server
>
> create temp table t
> ( fld1 char(10) not null unique
> ) with no log ;>
> 626: Cannot obtain or set serial value.>
> 140: ISAM error: operation illegal on a DR Secondary>
>
> however this statement succeeds on secondary server}
>
> create temp table t
> ( fld1 char(10) not null
> ) with no log ;
> create unique index t_u on t(fld1);>
> Isn't it a bug. Both statements are effectively the same:- one maintains
> uniqueness thru constraint
> and the other thru unique index.
>
> Is this bug reproducible in later version(s).