Re: Long transaction aborted in Informix IDS 7.31
Hi.
Firstly you should check how many log files has your instance
(onstat -l, last line). If it has less than LOGFILES, you should add as many
log files as you need. If not, you should set LOGFILES to a higher value and
then add logfiles. By the way, if your database has 100 logfiles, it has 200
Mb, enought to handle 300,00 rows, I think. Anyway, if your task will run
just once, you can cut your load file un several pieces (using head and tail
on Unix environment) to solve it with no DBA work.
Later
Omar Muqoz
----- Original Message -----
From: "Massoroto" <alanmas@gmail.com>
To: <informix-list@iiug.org>
Sent: Tuesday, November 08, 2005 8:39 AM
Subject: Long transaction aborted in Informix IDS 7.31
> Hi,
>
> I am running under Informix IDS 7.31 under Solaris 9 a data load on a
> database with logging mode actived (transactional).
>
> Qhen I execute my load query appears the following message:
>
> 458: Long transaction aborted.
> 847: Error in load file line 329334.>
> It seems a problem with the configurable properties of my ONCONFIG
> file. Some of the properties from the ONCONFIG file are:
>
> # Logical Log Configuration
>
> LOGFILES 100 # Number of logical log files
> LOGSIZE 2000 # Logical log size (Kbytes)>
> # Shared Memory Parameters
>
> LOCKS 500000 # Maximum number of locks
> BUFFERS 20000 # Maximum number of shared buffers
> NUMAIOVPS 1 # Number of IO vps
> PHYSBUFF 80 # Physical log buffer size (Kbytes)
> LOGBUFF 16 # Logical log buffer size (Kbytes)> LOGSMAX 500 # Maximum number of logical log files
> CLEANERS 8 # Number of buffer cleaner processes>
>
>
> Any ideas which properties I have to modify?
>
> PS: It is not possible to turn momentally into non logging mode to
> carry out the load and the back to logging mode
>
> Thank you.
>
> Alan
sending to informix-list
Omar Mu'oz Perez wrote:
> Firstly you should check how many log files has your instance
> (onstat -l, last line). If it has less than LOGFILES, you should add as many
> log files as you need. If not, you should set LOGFILES to a higher value and
> then add logfiles. By the way, if your database has 100 logfiles, it has 200
> Mb, enought to handle 300,00 rows, I think. Anyway, if your task will run
> just once, you can cut your load file un several pieces (using head and tail
> on Unix environment) to solve it with no DBA work.
Or split, or ... The main caveat with such tools is if your data has
any fields containing newlines, then accurately splitting at the ends of
records may be harder than you'd like. If you're sure you don't have
any newlines in the data, then split and friends are great tools.
DB-Load has a facility to sub-divide the load into smaller transactions;
I assume HPL does too, though I've not confirmed that.
SQLCMD - from the IIUG Software Archive - does too. My latest version
has a skip option to skip over the first N records of a load.
> ----- Original Message -----
> From: "Massoroto" <alanmas@gmail.com>
> To: <informix-list@iiug.org>
> Sent: Tuesday, November 08, 2005 8:39 AM
> Subject: Long transaction aborted in Informix IDS 7.31
>
>
>
>>Hi,
>>
>>I am running under Informix IDS 7.31 under Solaris 9 a data load on a
>>database with logging mode actived (transactional).
>>
>>Qhen I execute my load query appears the following message:
>>
>>458: Long transaction aborted.
>> 847: Error in load file line 329334.>>
>>It seems a problem with the configurable properties of my ONCONFIG
>>file. Some of the properties from the ONCONFIG file are:
>>
>># Logical Log Configuration
>>
>>LOGFILES 100 # Number of logical log files
>>LOGSIZE 2000 # Logical log size (Kbytes)>>
>># Shared Memory Parameters
>>
>>LOCKS 500000 # Maximum number of locks
>>BUFFERS 20000 # Maximum number of shared buffers
>>NUMAIOVPS 1 # Number of IO vps
>>PHYSBUFF 80 # Physical log buffer size (Kbytes)
>>LOGBUFF 16 # Logical log buffer size (Kbytes)>>LOGSMAX 500 # Maximum number of logical log files
>>CLEANERS 8 # Number of buffer cleaner processes>>
>>
>>
>>Any ideas which properties I have to modify?
>>
>>PS: It is not possible to turn momentally into non logging mode to
>>carry out the load and the back to logging mode
>>
>>Thank you.
>>
>>Alan
>
> sending to informix-list
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/