Re: Help with Transaction Log !! Urgent!!!
--=_0425A869.305106D2
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Don't remove the log file. That will make a lot of people unhappy.
Check the permissions on the log file. Make sure that the user that is
updating has read/write permissions on the log file, as well as the
directory that the file is in.
My SE memory is foggy but I think you can change to a different log
file also.
cat /dev/null > {new_log_file.log}
(Then Make all users disconnect)
dbaccess
close database;
start database {dbname} with log in {/directory/new_log_file.log};
Then check permissions on the file.
Brian Grellinger
I.S. Manager
DHIAC Information Systems
>>> "rkusenet" <rkusenet@sympatico.ca> 06/29/04 11:09AM >>>
"Madison Pruet" <mpruet@comcast.net> wrote in message
news:dlfEc.197076$Ly.67842@attbi_s01...
> Are you sure about 6.05? Could you post the output of "onstat -V".
>
>
> No removing the txn log file is not a good idea....
onstat !!!
I thought it is fairly obvious that he is talking about Standard
Engine.
ISAM error 121 seem to be too SE centric.
>
>
> "Kishore Bhageshpur" <kishore_b@hotmail.com> wrote in message
> news:73ea6c9.0406290558.1933864c@posting.google.com...
> > Hello...
> >
> > I am using Informix 6.05 on HPUX 11.11 and whenever I try a large
> > update (well, anything more than about 100 records), I get the
> > following error
> > 346: Could not update a row in the table.
> > 121: ISAM error: cannot write log record> >
> > This database has a log file which is huge - about 25 MB. But the
> > file system is not full. The volume is only about 25% full. I
> > thought maybe the log file was too big and so tried to empty the
log
> > file by cat /dev/null to the transaction log but I still get the
same
> > error message. I have no problems with selects, inserts and
deletes;
> > just updates.
> >
> > I am not really an Informix DBA and don't have a whole lot of
> > experience in Informix.., I inherited this db and any help would
be
> > appreciated. I have already looked at previous posts on this
> > newsgroup, but didn't find anything which I could use.
> >
> > Would removing the transaction log completely help? How do I do
that?
> >
> > Thanks,
> > Kishore
>
>
--=_0425A869.305106D2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 12pt Courier New; MARGIN-LEFT: 2px">
<DIV>Don't remove the log file. That will make a lot of people
unhappy.</DIV>
<DIV> </DIV>
<DIV>Check the permissions on the log file. Make sure that the user that is
updating has read/write permissions on the log file, as well as the directory
that the file is in.</DIV>
<DIV> </DIV>
<DIV>My SE memory is foggy but I think you can change to a different log file
also.</DIV>
<DIV> </DIV>
<DIV>cat /dev/null > {new_log_file.log}</DIV>
<DIV>(Then Make all users disconnect)</DIV>
<DIV> </DIV>
<DIV>dbaccess</DIV>
<DIV> </DIV>
<DIV>close database;</DIV>
<DIV>start database {dbname} with log in
{/directory/new_log_file.log};<BR></DIV>
<DIV>Then check permissions on the file.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Brian Grellinger<BR>I.S. Manager<BR>DHIAC Information Systems</DIV>
<DIV><BR>>>> "rkusenet" <rkusenet@sympatico.ca> 06/29/04 11:09AM
>>><BR><BR>"Madison Pruet" <mpruet@comcast.net> wrote in message
news:dlfEc.197076$Ly.67842@attbi_s01...<BR>> Are you sure about 6.05?
Could you post the output of "onstat -V".<BR>><BR>><BR>> No removing
the txn log file is not a good idea....<BR><BR>onstat !!!<BR>I thought it is
fairly obvious that he is talking about Standard Engine.<BR>ISAM error 121 seem
to be too SE centric.<BR><BR>><BR>><BR>> "Kishore Bhageshpur"
<kishore_b@hotmail.com> wrote in message<BR>>
news:73ea6c9.0406290558.1933864c@posting.google.com...<BR>> >
Hello...<BR>> ><BR>> > I am using Informix 6.05 on HPUX 11.11 and
whenever I try a large<BR>> > update (well, anything more than about 100
records), I get the<BR>> > following error<BR>> >
346: Could not update a row in the table.<BR>> > 121:
ISAM error: cannot write log record<BR>> ><BR>> > This database has
a log file which is huge - about 25 MB. But the<BR>> > file system
is not full. The volume is only about 25% full. I<BR>> >thought maybe the log file was too big and so tried to empty the log<BR>>
> file by cat /dev/null to the transaction log but I still get the
same<BR>> > error message. I have no problems with selects, inserts
and deletes;<BR>> > just updates.<BR>> ><BR>> > I am not
really an Informix DBA and don't have a whole lot of<BR>> > experience in
Informix.., I inherited this db and any help would be<BR>> >
appreciated. I have already looked at previous posts on this<BR>> >
newsgroup, but didn't find anything which I could use.<BR>> ><BR>> >
Would removing the transaction log completely help? How do I do
that?<BR>> ><BR>> > Thanks,<BR>> >
Kishore<BR>><BR>><BR><BR><BR></DIV></BODY></HTML>
--=_0425A869.305106D2--
sending to informix-list
"Brian Grellinger" <Brian.Grellinger@dhiac.com> wrote > Don't remove the log file. That will make a lot of people unhappy. > > Check the permissions on the log file. Make sure that the user that is > updating has read/write permissions on the log file, as well as the > directory that the file is in. I too thought the same, till I re-read his post "I have no problems with selects, inserts and deletes; just updates" That rules out any permission problem with the log file. I got in touch with the poster in email. It seems the update fails once it crosses 100 rows. Anything lower than that, it works fine. I haven't worked with SE for more than 10 yrs, but I recollect that it can't handle large updates in one atomic unit. I have asked the poster to break the code into smaller unit. A SP will be just fine for it.