Any ideas about this? It's very aggravating and I have no idea how to debug
this any further. Thanks.
Hi.
I am having a problem with a program I am writing. The program reads a
file, checks an object file, and if the record doesn't exist, it inserts to
a node table (one table per node) and
Hi.
I am having a problem with a program I am writing. The program reads a
file, checks an object file, and if the record doesn't exist, it inserts to
a node table (one table per node) and the objects file. I wrote a C program
to do this, with multiple processes running at one time. I have 15
Make sure you check you ulimit on file - I have hit that on AIX more than
once.
On Mon, Feb 9, 2009 at 2:42 PM, JD King jeff_d_k...@hotmail.com wrote:
I am running MySQL 5.1.30 on AIX 5.3. When a table reaches 1GB the table
gets marked as corrupt. Is there a setting that limits table size to
If you do what Baron suggests, you may want to set Innodb to create a
file-per-table - that way, in the future, you could save space when tables
are dropped, or you could recreate innodb tables individually to save space,
not have to dump all your innodb tables at one time.
On 10/10/07, Baron
I have created a new table, with an auto_increment value. I would like the
first auto_increment value to be 1001. So I -
1) inserted a fake record with an id of 1000
2) alter table tblname auto_increment=1000 (with and without a fake record)
3) alter table tblname auto_increment=1001 (with and
I upgraded to Mysql 5.0.42 from 4.1.14 yesterday. Afterwards, a query the I
run every day to capture data on nodes that have increased backup load the
most in TSM, seems to be ignoring my order by statement. Here is the query
and the output:
mysql select occupancy.node_name as
