Prasanna Raj <[EMAIL PROTECTED]> wrote:

Gotit Thnx ;)

You have set innodb_force_recovery to 3 which means , do not run transaction 
rollbacks after recovery.


http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
1 (SRV_FORCE_IGNORE_CORRUPT) 2 (SRV_FORCE_NO_BACKGROUND) 3 (SRV_FORCE_NO_TRX_UNDO) 4 (SRV_FORCE_NO_IBUF_MERGE) 5 (SRV_FORCE_NO_UNDO_LOG_SCAN) 6 (SRV_FORCE_NO_LOG_REDO)


I remove innodb_force_recovery from my.cnf file, it works very good.



Thanks your valuable help.


Just try removing the innodb_force_recovery from my.cnf file or change the value
More info : http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html

--Praj



On Wed, 5 Apr 2006 14:02:06 +0700
"Truong Tan Son" <[EMAIL PROTECTED]> wrote:

Prasanna Raj <[EMAIL PROTECTED]> wrote:

> Can you through us more lights on error ? where does this occur ?

**ERROR:

InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.


Please teach me "raw".

**/etc/my.cnf:

# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/var) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password = your_password
port  = 3306
socket  = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
init_connect='SET AUTOCOMMIT=0'
innodb_force_recovery = 3
port  = 3306
socket  = /tmp/mysql.sock
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# #skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Point the following paths to different dedicated disks
#tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /usr/local/mysql/var/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /usr/local/mysql/var/
innodb_log_arch_dir = /usr/local/mysql/var/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
[EMAIL PROTECTED] var]#




> -bash-2.05b$ perror 10 30
> OS error code  10:  No child processes
> OS error code  30:  Read-only file system
> -bash-2.05b$
> > -Praj > > On Wed, 5 Apr 2006 08:48:08 +0700
> "Truong Tan Son" <[EMAIL PROTECTED]> wrote:
> >> [S] Dhandapani wrote: >> >> >> > mysql> show global variables like '%innodb%';
>> > +---------------------------------+------------------------+
>> > | Variable_name                   | Value                  |
>> > +---------------------------------+------------------------+
>> > | have_innodb                     | YES
>> >> >> OK, all thing is let default setting. >> >> >> > mysql> *|SET AUTOCOMMIT=0;|*
>> > Query OK, 0 rows affected (0.00 sec)
>> > >> > mysql> *|INSERT INTO CUSTOMER VALUES (15, 'John');|*
>> > Query OK, 1 row affected (0.00 sec)
>> >> >> ERROR 1030 (HY000): Got error -1 from storage engine >> >> >> What is error ? >> >> I follow Document: http://dev.mysql.com/doc/refman/5.0/en/innodb-transactions-with-different-apis.html >> >> The error is same. >> >> >> Please teach me. >> >> >> Best regards, >> >> -- >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > mysql> *|ROLLBACK;|*
>> > Query OK, 0 rows affected (0.00 sec)
>> > >> > mysql> *|SELECT * FROM CUSTOMER;|* >> > >> > +------+--------+ >> > >> > | A | B |
>> > +------+--------+
>> > |    |  |
>> > +------+--------+
>> > >> > the inset stattement has been rollbacked. >> > >> > Reference
>> > 
http://dev.mysql.com/doc/refman/5.0/en/innodb-transactions-with-different-apis.html
>> > >> > Regards,
>> > Dhandapani
>> > Dba Sify Limited.
>> > >> > >> > Truong Tan Son wrote: >> > >> >> Dear Sir,
>> >>
>> >> I install MySQL 5.0.18 on RH EL4, but do not know how to use InnoDB >> >> for "ROLLBACK".
>> >>
>> >> ./configure --prefix=/usr/local/mysql \
>> >> --exec-prefix=/usr/local/mysql \
>> >> --with-innodb
>> >> make && make install
>> >>
>> >> **/etc/my.cnf:
>> >> # Uncomment the following if you are using InnoDB tables
>> >> innodb_data_home_dir = /usr/local/mysql/var/
>> >> innodb_data_file_path = ibdata1:10M:autoextend
>> >> innodb_log_group_home_dir = /usr/local/mysql/var/
>> >> innodb_log_arch_dir = /usr/local/mysql/var/
>> >> # You can set .._buffer_pool_size up to 50 - 80 %
>> >> # of RAM but beware of setting memory usage too high
>> >> innodb_buffer_pool_size = 16M
>> >> innodb_additional_mem_pool_size = 2M
>> >> # Set .._log_file_size to 25 % of buffer pool size
>> >> innodb_log_file_size = 5M
>> >> innodb_log_buffer_size = 8M
>> >> innodb_flush_log_at_trx_commit = 1
>> >> innodb_lock_wait_timeout = 50
>> >>
>> >> with setting above, I could not use InnoDB.
>> >>
>> >>
>> >> How to know InnoDB is installed, and start it ?
>> >>
>> >>
>> >> Thanks you and best regards,
>> >> -- >> >> >> > >> > ********** DISCLAIMER ********** >> > Information contained and transmitted by this E-MAIL is proprietary to >> > Sify Limited and is intended for use only by the individual or entity to >> > which it is addressed, and may contain information that is privileged, >> > confidential or exempt from disclosure under applicable law. If this is a >> > forwarded message, the content of this E-MAIL may not have been sent with >> > the authority of the Company. If you are not the intended recipient, an >> > agent of the intended recipient or a person responsible for delivering the >> > information to the named recipient, you are notified that any use, >> > distribution, transmission, printing, copying or dissemination of this >> > information in any way or in any manner is strictly prohibited. If you have >> > received this communication in error, please delete this mail & notify us >> > immediately at [EMAIL PROTECTED] >> > >> > www.sify.com - your homepage on the internet for news, sports, finance,
>> > astrology, movies, entertainment, food, languages etc
>> >
>> > > -- > MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]
>



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


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

Reply via email to