Error 139 in logical log backup (resubmitted with additional info) 
Author Message
 Error 139 in logical log backup (resubmitted with additional info)

We are running ontape -c and often (but not always) get the following
message in online.log:

Process exited with return code 139: /bin/sh /bin/sh -c /home/informix
_s/etc/log_full.sh 2 23 "Logical Log 8380 Complete." "Logical Log 8380
Complete

From finderr, we are told to increase LOGSMAX; but this is set to 350 and we
have only 106 log files.
What happens ? Do we risk that backup of logs be incomplete/erroneous ?

We perform logical log backup on local disk; there is ample space and
LTAPESIZE is adequately set.

Pierre Henrotay



Wed, 18 Jun 1902 08:00:00 GMT
 Error 139 in logical log backup (resubmitted with additional info)



Quote:
>We are running ontape -c and often (but not always) get the following
>message in online.log:

>Process exited with return code 139: /bin/sh /bin/sh -c /home/informix
>_s/etc/log_full.sh 2 23 "Logical Log 8380 Complete." "Logical Log 8380
>Complete

  This is a known bug and not really a problem since the log files
  still get backed up.

Quote:
>From finderr, we are told to increase LOGSMAX; but this is set to 350 and we
>have only 106 log files.
>What happens ? Do we risk that backup of logs be incomplete/erroneous ?

>We perform logical log backup on local disk; there is ample space and
>LTAPESIZE is adequately set.

>Pierre Henrotay

--
David Williams


Wed, 18 Jun 1902 08:00:00 GMT
 Error 139 in logical log backup (resubmitted with additional info)
The log max stands for how many maximum log file ur server is allowed to
have. The 106 log files that u see , is the number currently configured.
Just reconfigure the LOGFILES parameter in the onconfig file to increase the
log files. This will need the server to be restarted. I guess its a script
that fires when a log gets full. Only if u get en error during ontape it
warrants attention. Its a standard informix script. You could change the
logical log backup mode to continous in the onconfig file and remove this
script from the ALARMPROGRAM parameter in the onconfig. Test this
configuration on a test server before u implent it.

neil


Quote:
> We are running ontape -c and often (but not always) get the following
> message in online.log:

> Process exited with return code 139: /bin/sh /bin/sh -c /home/informix
> _s/etc/log_full.sh 2 23 "Logical Log 8380 Complete." "Logical Log 8380
> Complete

> From finderr, we are told to increase LOGSMAX; but this is set to 350 and
we
> have only 106 log files.
> What happens ? Do we risk that backup of logs be incomplete/erroneous ?

> We perform logical log backup on local disk; there is ample space and
> LTAPESIZE is adequately set.

> Pierre Henrotay



Wed, 18 Jun 1902 08:00:00 GMT
 Error 139 in logical log backup (resubmitted with additional info)

Neil, you misunderstand Pierre's problem.  He, like many, did not know
what to do with the ALARMPROGRAM parameter in the ONCONFIG file and
left the sample value of $INFORMIXDIR/bin/logs_full.sh which is an
example alarm event handler script that only handles the log full event
by starting onbar to backup the newly filled logfile.  Obviously
Pierre is not using onbar and has not set it up so when the script
tries to run onbar onbar returns an error return which is not an ISAM
error -139 but a misinterpretation by the script of the return code.

It just means that onbar is not configured.  You should replace
log_ful.sh with your own event handler script or executable.  I have
submitted two such to the IIUG Repository in package utils3_ak.  One
is a version of log_ful.sh that uses ontape and the other is a very
complete event handler executable that does the log backup and also
logs and emails event messages to you on your email, text beeper,
and/or cell phone.

Art S. Kagel

Quote:
> The log max stands for how many maximum log file ur server is allowed to
> have. The 106 log files that u see , is the number currently configured.
> Just reconfigure the LOGFILES parameter in the onconfig file to increase the
> log files. This will need the server to be restarted. I guess its a script
> that fires when a log gets full. Only if u get en error during ontape it
> warrants attention. Its a standard informix script. You could change the
> logical log backup mode to continous in the onconfig file and remove this
> script from the ALARMPROGRAM parameter in the onconfig. Test this
> configuration on a test server before u implent it.

> neil



> > We are running ontape -c and often (but not always) get the following
> > message in online.log:

> > Process exited with return code 139: /bin/sh /bin/sh -c /home/informix
> > _s/etc/log_full.sh 2 23 "Logical Log 8380 Complete." "Logical Log 8380
> > Complete

> > From finderr, we are told to increase LOGSMAX; but this is set to 350 and
> we
> > have only 106 log files.
> > What happens ? Do we risk that backup of logs be incomplete/erroneous ?

> > We perform logical log backup on local disk; there is ample space and
> > LTAPESIZE is adequately set.

> > Pierre Henrotay



Wed, 18 Jun 1902 08:00:00 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Error 139 in logical log backup

2. ADO Connection fails? Resubmit w/additional info

3. ADO Connection fails? Resubmit w/additional info

4. error status 139

5. error 139 before INPUT ARRAY

6. logical log backup and shmat error

7. Logical Log Backup Errors

8. Logical Log Continous Backup - ArcServer Software Backup

9. IFX: Info - Logical Log Complete (wiwbei)

10. deciding on logical log backup strategy - advice, anyone?

11. Can IDS backup logical logs in parallel?

12. Logical log backup - Why!?


 
Powered by phpBB® Forum Software