"Cannot write log record..." :((((((((
Posted in 1995
Topics: Error Codes & Troubleshooting, Connectivity: ESQL/C, 4GL & Embedded SQL, Server Administration, Security, Permissions & Auditing, Migration, Import/Export & Data Conversion
> Date: 12/07/1995 Time: 10:23:36
> Program error at "custom.4gl", line number 225.
> SQL statement error number -346.
> Could not update a row in the table.
> SYSTEM error number -121.
> ISAM error: cannot write log record
I'm getting this error message whenever I try to carry out the following
(simple) SQL update command. The command is part of a 4GL program, but it
falls over even I try to do the update from ISQL... :(
update stamtana ",
set area_code = "C2"
where cust_no = "XXXX"
I thought I might have a dodgy index so I ran bcheck, but it said
everything was OK, so to be safe I unloaded the tables in question,
dropped them, re-created them, loaded them up again and re-created the
indexes...
...but it still doesn't work <moan>.. 8(
I thought it might be permissions, so I did a find from the data
directory level and changed all file permissions to +rw,informix,informix
- I also did a "grant dba to public" just in case...
Also there are no space problems, I've pointed DBTEMP to a partition with
loads of space...
The log file is fine and I can write to it (other updates work...), so
what is this error message trying to tell me?
I'm doing a dbexport at the minute using v5.03 dbexport/dbimport from
what is a v4.00 database (taken from a customer site), hoping that it
will work in the new 5.03 engine, but I'll be happy if the bl**dy
dbexport/import works :(
Has anyone any idea why the hell this update won;t work, the schema
details are given below in case it helps and the table has about 300,000
records in it..
I think I've tried everything (other than the dbexport/import I'm waiting
on now) - am I missing anything, it could be something really daft that
I'm just not seeing, but any problems like this are usually cured by
either bringing the machine down & up again, or doing a rebuild on the
tables in question......
*Any* comments on this would be really welcome, it's a holiday here in
Ireland at the moment, but the customer in question will be giving me
s**t if he comes in tomorrow to find he still has this problem (you've
probably been there ;> )
A virtual pint to the person(s) who can help - I don't often get a chance
to read my UseNet postings, so replys by EMail would be responded to
faster :)
Thanks for reading this far,
// Chris@Home in Ireland (nice'n'sunny at the minute...)
=========================================================================
{ TABLE "informix".stamtana row size = 126 number of columns = 18 index
size = 126
}
{ unload file name = stamtan239.unl number of rows = 245684 }
create table "informix".stamtana
(
cust_no char(6),
prod_code char(20),
tr_year smallint,
tr_period smallint,
cust_gp char(6),
prod_gp char(6),
cust_rep char(6),
qty_sold decimal(14,4),
list_val decimal(14,4),
disc_val decimal(14,4),
prom_val decimal(14,4),
qty_ret decimal(14,4),
ret_val decimal(14,4),
shipto char(6),
anal_code char(6),
area_code char(6),
whs_code char(6),
cust_anl char(6)
);
revoke all on "informix".stamtana from "public";
create index "task".i8amtana on "informix".stamtana
(tr_year,tr_period,cust_no,shipto,cust_rep,cust_gp,prod_gp,prod_code);
create index "chris".i9amtana on "informix".stamtana (cust_no);
create index "chris".i10amtana on "informix".stamtana (cust_no,shipto);