Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Khan asked whether DYNAMIC_LOGS=2 on IDS 11.70.FC7 will automatically add logical logs when all logs are full and unbacked-up; he observed it only adds logs to let a long transaction roll back, after which the instance hangs. Replies (plus one off-topic Spanish disclaimer post): DYNAMIC_LOGS isn't intended for that. Use ALARMPROGRAM to trap the "log full"/"all logs full" alarms and run onparams (or the SQL admin API) to add a log, optionally triggering at n-1 full logs via a count on sysmaster:syslogs. Another poster suggested instead backing up logs automatically via ALARMPROGRAM with onbar/ontape, or setting LTAPEDEV to /dev/null if log recovery isn't needed. No confirmation from the original poster is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi,
I am using the IDS 11.70 FC7, I have a question about the functionality of the
DYNAMIC_LOGS parameter when it is set as 2.
I have seen that when DYNAMIC_LOGS=2, and the server runs out of free logical
logs (all logs are used and not backed up), it does not add the new logical
logs dynamically. Unless, there is any open transaction in the next log, so
that long transaction can be rolled back.
Also, after the rollback, the instance stops its processing due to
non-availability of logical logs.
I want to ask that is there any way that instance can automatically add the
logical logs in the log dbspace, in case if all logs are consumed and not
backed up?Can DYNAMIC_LOGS=2 address this requirement or not?
Thanks.
Regards,
Khan
La informaci?n y archivos anexos contenidos en este mensaje pueden ser
confidenciales y/o contener informaci?n legalmente privilegiada. Si usted no
es destinatario del mismo: queda formalmente notificado que (i)cualquier
divulgaci?n, distribuci?n, reproducci?n o copiado de esta comunicaci?n est?
estrictamente prohibido y (ii) que no deber? tomar ninguna acci?n basada en
este correo electr?nico o cualquier otra informaci?n incluida en ?l. Favor de
notificar al remitente de inmediato mediante el reenv?o de este correo
electr?nico y borrar a continuaci?n el mismo y sus anexos.
Si ?ste mensaje est? dirigido a uno de los clientes de CIATEQ, A.C., cualquier
opini?n o punto de vista contenidos en este correo electr?nico, est?n sujetos
a los t?rminos y condiciones expresados en los correspondientes contratos
firmados con CIATEQ, A.C."
DYNAMIC_LOGS is not done for that purpose really.
What you could do is use the ALARMPROGRAM.
There is an *alarmprogram.sh* script provided by the product. You could
modify it or write your own and add the correct instruction "onparams"
or the equivalent SQL API command to add a log whenever all logs are
full which one of the alarms you can trap.
Be aware, there is 1 alarm whenever an individual log is full and
another alarm when all of the logs are full. You can even make it more
intelligent and perform what you want to do (add another log) when n-1
logs are full (you need to count using a SELECT COUNT(*) on the
sysmaster:syslogs table with the correct WHERE clause.
Hope that this helps and that it did not confuse you.
Cordialement, Regards,
Khaled Bentebal
Directeur Général - ConsultiX
Président UGIF - User Group Informix France
IIUG - Board of Directors
Tél: 33 (0) 1 39 12 18 00
Fax: 33 (0) 1 39 12 18 18
Mobile: 33 (0) 6 07 78 41 97
Email: khaled.bentebal@consult-ix.fr
Site Web: www.consult-ix.fr
Le 13/01/14 20:50, O KHAN a écrit :
> Hi,
>
> I am using the IDS 11.70 FC7, I have a question about the functionality of
the
> DYNAMIC_LOGS parameter when it is set as 2.
>
> I have seen that when DYNAMIC_LOGS=2, and the server runs out of free logical
> logs (all logs are used and not backed up), it does not add the new logical
> logs dynamically. Unless, there is any open transaction in the next log, so
> that long transaction can be rolled back.
> Also, after the rollback, the instance stops its processing due to
> non-availability of logical logs.
>
> I want to ask that is there any way that instance can automatically add the
> logical logs in the log dbspace, in case if all logs are consumed and not
> backed up?Can DYNAMIC_LOGS=2 address this requirement or not?
>
> Thanks.
>
> Regards,
> Khan
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
↪ replying to Khaled Bentebal
JON RITSON — — source: IIUG Forums & Mailing Lists
Hi,
Silly question ... do you backup your logical logs?
If you do want to backup your logs, then consider using ALARMPROGRAM to backup
logical logs when complete (using onbar or ontape) - that way you should not
encounter full logical logs because they are not being backed up.
If you do NOT want to keep your logical logs (i.e. NO LOGICAL RECOVERY
CAPABILITY) then just set LTAPEDEV to /dev/null.
Or perhaps I am missing the point?
JJ
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.