Re: (LONGTX) V 9.30.UC2 How to get out of this
Posted in 2004
Topics: Backup & Restore, Platform-Specific Issues
If the LTX won't finish rolling back either you'll have to:
- dynamically add some more logs (if IDS will allow you to enable this
once the problem has already happened, which it very likely won't as
it probably won't let you shut down the instance which you need to do
in order to set DYNAMIC_LOGS). If this doesn't work your instance is
stuffed and you'll have to restore the whole instance from a backup.
(Don't replay the logs - unless you're using onbar and can do
point-in-time restores - or you'll probably make it happen again)
To prevent a recurrence of the LTX, either
- Turn logging off for the database for the duration of the load - but
only if you can stop any programs running that need logging to be on
OR
- Load the table using HPL with the "no logging" option (requires an X
windows front end or a PC with an X emulator such as Reflection -
otherwise a knowledge of an impenetrable command line syntax)
OR
- Create / Alter the table as type RAW for the load; you'll have to
alter it to type STANDARD before you can put any indexes on or get
logging features
OR (this is the most versatile one)
- Use dbload to load the data with the commit (-c?) switch so it
commits every x no of rows
To prevent an LTX locking up your instance again, either
- Enable dynamic log allocation with the DYNAMIC_LOGS parameter
AND / OR
- Set LTXHWM and LTXEHWM to values not greater than 50.
Good luck
Andy
To prevent a recurrence of the lock-up set LTXHWM
"Azeemuddin, Basheer" <bahmed@knrq.com> wrote in message news:<c5f0m2$kmc$1@terabinaries.xmission.com>...
> AIX 4.3.3 V 9.30 UC2
>
> Informix Dynamic Server Version 9.30.UC2 -- On-Line (LONGTX) -- Up 2
> days 04:00:45 -- 737696 Kbytes Blocked:LONGTX
>
>
> Started a load job about 100,000 Records. After few minutes got LONGTX.
>
> How to get out of this.
>
> Thanks
> Basheer
> sending to informix-list
[cutting > To prevent an LTX locking up your instance again, either > - Enable dynamic log allocation with the DYNAMIC_LOGS parameter I think this is a very bad idea as you can quite quickly fill a dbspace. -- Paul Watson # Oninit Ltd # Growing old is mandatory Tel: +44 1436 672201 # Growing up is optional Fax: +44 1436 678693 # Mob: +44 7818 003457 # www.oninit.com #
When the alternative is a dead instance ... But I'd agree with the principle that prevention is better than cure. Andy Paul Watson <paul@oninit.com> wrote in message news:<407BF052.489654A3@oninit.com>... > [cutting > > To prevent an LTX locking up your instance again, either > > - Enable dynamic log allocation with the DYNAMIC_LOGS parameter > > I think this is a very bad idea as you can quite quickly fill a > dbspace.