Hi again,

I really think you should walk yourself through the InnoDB user manual at
http://www.innodb.com/ibman.html
There's a lot of usefull and explanory information in there.

For your question:
ib_archXXXXXXXX and ib_logfileX are the logs that InnoDB uses to track
committed transactions
and perform recovery in case of an DataBase crash.

Having all these files in the same directory is kinde messy, maybe you wanne
use a config file like the one at the bottom of my reply.
The kind of logging you need is the one indicated by the log parameter in
the config file.
The binary logging that we use is only usefull if you want to be able to do
recovery for certain time spans.

Also you can start your server manually at the command prompt with
c:\yourmysqldir\bin\mysqld-max-nt --console
This way you will be able to see any (error) messages directly in the
console ...

Have fun, I know I did ;)
CB.

=================================
# The MySQL server
[mysqld]

# Activate binary logging for MySQL
log-bin=C:/mysql/binlogs/localhost-bin
# Only binary log queries for table TW
binlog-do-db=tw

# Prevent those stupid lower case table names when importing/exporting dumps
set-variable = lower_case_table_names=0

# InnoDB logging file
# log=log.txt

# Default table type for new tables
default-table-type=InnoDB

# BDB home - mysqld-max will not start without this parameter
# and the directory must exist
bdb-home=../bdbhome

# Data home dir of your InnoDB tables
innodb_data_home_dir = c:\mysql\ibdata
#                                            Data files must be able to
#                                            hold your data and indexes
innodb_data_file_path = ibdata1:500M
#                                            Set buffer pool size to 50 - 80
%
#                                            of your computer's memory
set-variable = innodb_buffer_pool_size=200M
set-variable = innodb_additional_mem_pool_size=15M

# Logging
innodb_log_group_home_dir = c:\mysql\iblogs
#                                            .._log_arch_dir must be the
same
#                                            as .._log_group_home_dir
innodb_log_arch_dir = c:\mysql\iblogs
innodb_log_archive=0
set-variable = innodb_log_files_in_group=3
#                                            Set the log file size to about
#                                            15 % of the buffer pool size
set-variable = innodb_log_file_size=25M
set-variable = innodb_log_buffer_size=10M

#                                            Set ..flush_log_at_trx_commit
to
#                                            0 if you can afford losing
#                                            a few last transactions 
innodb_flush_log_at_trx_commit=1
set-variable = innodb_file_io_threads=4
set-variable = innodb_lock_wait_timeout=50
======================================================================

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 01, 2002 23:14
To: [EMAIL PROTECTED]
Subject: Re: high level: enabling transactions in mysql-max with
WebLogic TX datasource?


>>>>> "Bert" == Bert VdB <[EMAIL PROTECTED]> writes:

    Bert> Hi,
    Bert> all you have to do use a transaction enabled data-source and use
the
    Bert> Mm-MysqlDriver
    Bert> for your JDBC connections. (http://mmmysql.sourceforge.net/)

    Bert> Best is to read the InnoDB documentation carefully
(http://www.innodb.com),
    Bert> as you cannot choose from a wide
    Bert> variety of transaction-levels ... in my experience, most of the
detailed
    Bert> transaction-handling
    Bert> can only be done at mysql-query level.

    Bert> To test wether your datasource supports the transactions, do a
test and look
    Bert> at the InnoDB-logfiles, it should
    Bert> indicate some thing like SET AUTOCOMMIT=0 and COMMIT.

Ok, I determined that innodb wasn't being initialized because I didn't have
"innodb_data_file_path" set in "my.ini".  I added the following line to
"my.ini" in mysqladmin:

    innodb_data_file_path = ibdata1:30M:autoextend

After I restarted the service and created some tables (not adding any rows
yet), I noticed the following files in the data"
subdirectory:

---------------
total 41004
drwxr-xr-x    2 dmkarr   None         8192 Jul  1 15:01 mysql/
-rw-r--r--    1 dmkarr   None         2461 Jul  1 14:59 mysql.err
-rw-r--r--    1 dmkarr   None      5242880 Jul  1 14:59 ib_logfile0
-rw-r--r--    1 dmkarr   None     31457280 Jul  1 14:59 ibdata1
drwxr-xr-x    4 dmkarr   None         4096 Jul  1 14:59 ./
-rw-r--r--    1 dmkarr   None        25088 Jul  1 14:59
ib_arch_log_0000000000
-rw-r--r--    1 dmkarr   None      5242880 Jul  1 14:59 ib_logfile1
drwxr-xr-x   11 dmkarr   None         4096 Jun 29 11:30 ../
drwxr-xr-x    2 dmkarr   None            0 Jun 29 11:07 test/
---------------

However, I don't know how to check the log files for those strings, as they
appear to be binary.  A simple grep didn't find anything.  Is there a
special
viewer for mysql log files?

-- 
===================================================================
David M. Karr          ; Java/J2EE/XML/Unix/C++
[EMAIL PROTECTED]


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
<[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to