System resets when loading a large table

[Beau E. Cox]

Hi -

I have an application which is essentially 'read-only' -
once the database is loaded it is only read from. So,
I am trying to implement it with various indices and
a table containg some large content in blob columns.
I observe the max_allowed_packet setting and
'split' blobs too large among multiple rows. All is fine
during testing. However, when I try a production
load (which should load about 1.5G to the various
tables) the system resets at or near the 1G mark
leaving no logs/msgs (that I can find) telling me
what went wrong. I have tried the following to no
avail:
- 'disable' bin logging on the main 'content' table
- RAID that table into 8 chunks.
Sill, when the total in the .MYD chunks reaches
1GB - KABOOM!

My configuration:
SuSE Linux 8,1
Mysql 4.0.13
loading with perl 5.8 using DBI 1.37/
DBD::mysql 2.9002.

Can someone suggest a next step?

Aloha => Beau;
== please visit ==
<http://beaucox.com> => main site
<http://howtos.beaucox.com> => howtos
<http://PPM.beaucox.com> => perl PPMs
<http://CPAN.beaucox.com> => CPAN
== thank you ==

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/my***********...ie.nctu.edu.tw

[Aggro]

Beau E. Cox wrote:

tables) the system resets at or near the 1G mark
leaving no logs/msgs (that I can find) telling me
what went wrong. I have tried the following to no
avail:

I'm no expert but could this be hardware failure? Perhaps something
wrong with cpu, memory or motherboard that causes the hardware to do
panic solution.

I had a problem with cpu. It couldn't take a lot of cpu load without
booting the machine.

[Aggro]

Beau E. Cox wrote:

tables) the system resets at or near the 1G mark
leaving no logs/msgs (that I can find) telling me
what went wrong. I have tried the following to no
avail:

I'm no expert but could this be hardware failure? Perhaps something
wrong with cpu, memory or motherboard that causes the hardware to do
panic solution.

I had a problem with cpu. It couldn't take a lot of cpu load without
booting the machine.