myisampack / myisamchk Problem

2004-06-16 Thread Michael Arndt 
Hello *

my Problem (resolved for newer mysql Versions):
 
A MyIsam Table is packed with myisampack

A subsequent myisamchk -r or -o with index reordering erroneously
marks wrong indices in the packed table for 4.0.15
(unpacking reconstructs the original table)

This seems to be a known issue concerning myisamchk 
and to be resolved in versions  4.0.15, if i am not mistaken.

Question;

Due to practicial issues i'd like to keep to 4.0.15
and replace only the myisamck command from 4.0.20

The replaced command itself seems to work, the error message
disappears. 

But mysql marks the packed table still as bad. 
Is there a workaround to tell mysql 4.0.15 the packed table is ok ?

TIA
Micha

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

MERGE Table Problem

2004-06-11 Thread Michael Arndt 
Hello *

reproducable Problem:

Content of UNION: 
logs_20040608,logs_20040609,logs_20040611,logs_20040612,logs_20040613,logs_20040614, 
logs_20040615
results: 0E0
DBD::mysql::db do failed: Can't open file: '#sql-13c1_12.MRG'. (errno: 144) at 
/usr/local/sbin/new_MERGE_table.pl line 276.
Unable to ALTER TABLE logs  UNION=( 
logs_20040608,logs_20040609,logs_20040611,logs_20040612,logs_20040613,logs_20040614, 
logs_20040615 ) INSERT_METHOD=LAST: !Can't open file: '#sql-13c1_12.MRG'. (errno: 144)

Can anyone see a conceptional misunderstandig, i make ?

in pseudocode  do the following using perl dbi:

1. FLUSH TABLES
# take out all old tables from merge in order to compress the most recent
2. ALTER TABLE logs UNION (log_today) INSERT_METHOD=LAST;
3. FLUSH TABLES; # make mysql use the new merge table
3. mysiampack / mysiamcheck (log_yesterday)
4. FLUSH TABLES # just in case
5. ALTER TABLE logs UNION ( last_tenlogs, log_today) INSERT_METHOD=LAST;
- here the problem arises, i assume triggered by yesterdays table in the list of 
last_tenlogs

@commands  = ( FLUSH TABLES, ALTER TABLE $LOGTABLE  UNION=( $COMMA_TABLE_SET 
$newTABLE ) INSERT_METHOD=LAST);
for ( @commands){
$results=$dbh-do($_) or die Unable to $_: ! . $dbh-errstr . \n;

(COMMA_TABLE_SET is a list of commaseparated table names, ending with a comma)


TIA
Micha

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Problem with Merge Table,ERROR 1016: Can't open file: '#sql-407f_f.MRG'. (errno: 144)

2004-06-09 Thread Michael Arndt 
Hello *,


a) what could be reason /solution for the following Problem:

  ERROR 1016: Can't open file: '#sql-407f_f.MRG'. (errno: 144)


b) in which directory the below reported intermediate file should
   be generated

mysql use syslog
Database changed
mysql ALTER TABLE logs  UNION=( 
logs_20040512,logs_20040513,logs_20040514,logs_20040515,logs_20040516,logs_20040517,logs_20040518,logs_20040519,logs_20040520,logs_20040521,logs_20040522,logs_20040523,logs_20040524,logs_20040525,logs_20040526,logs_20040527,logs_20040528,logs_20040529,logs_20040530,logs_20040531,logs_20040601,logs_20040602,logs_20040603,logs_20040604,logs_20040605,logs_20040606,logs_20040607,logs_20040608,logs_20040610,
 logs_20040609 ) INSERT_METHOD=LAST;
ERROR 1016: Can't open file: '#sql-407f_f.MRG'. (errno: 144)

TIA
Micha

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

myisampack, check: already compressed ?

2004-06-07 Thread Michael Arndt 
Hello *

Question: 

Is there a (cheap) way to find out if a MyISAM Table is 
already compressed, before running a myisampack on it ?

Goal: 

-In a script that regularly compresses Tables
 i'd like to check before packing. In case the script
 has previously been started and already done the compression.

TIA
Micha

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

merge tables for big log files ?

2004-05-31 Thread Michael Arndt 
Hello *,

goal: using merge tables for annual / monthly storage of syslog information 
  using php-syslog-ng and syslog-ng

problem: 

-one actual table must be available for inserts
-the merge table needs to be the target for reports and queries
-static parts of the merge table should be compressed

question: 

what is the best strategy for grouping / using a merge table ?

a) have one separate table for continous syslog data
   and synchronise this table regularily to e.g. a monthly table log_2004_06 
  
  (log_2004_06 is Part of a merge table log_global to enable global access 
   to all monthly logs with php-syslog-ng)

   syslog-ng - log
   log --(INSERT INTO) - log_2004_06
   log_global ( log_2004_12,log2004_11,log_2004_10,...) 

b) let the insert table for syslog-ng already be part of the merge table 
   and reordering the merge table on a regularly schema, to be
   able to compress all old,static tables.
   log ( log_2004_12,log2004_11,log_2004_10,...)

Problem for this variant: merge table has to be dropped and recreated
  periodically.
  during the short lag interval the log merge table
  does not exist

anyone has done something like this already ?

TIA
Micha
 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]