Oracle 5.0 Reference Manual page 1479

Replication and Binary Logging Options and Variables
Tells the slave to translate the default database (that is, the one selected by USE) to
was on the master. Only statements involving tables are affected (not statements such
from_name
as
CREATE DATABASE,
default database on the master. This does not work for cross-database updates. To specify multiple
rewrites, use this option multiple times. The server uses the first one with a
matches. The database name translation is done before the
If you use this option on the command line and the ">" character is special to your command
interpreter, quote the option value. For example:
shell> mysqld --replicate-rewrite-db="olddb->newdb"
•
--replicate-same-server-id
Version Introduced
Command-Line Format
Option-File Format
To be used on slave servers. Usually you should use the default setting of 0, to prevent infinite
loops caused by circular replication. If set to 1, the slave does not skip events having its own
server ID. Normally, this is useful only in rare configurations. Cannot be set to 1 if
[1451] is used. By default, the slave I/O thread does not write binary log events to the
updates
relay log if they have the slave's server ID (this optimization helps save disk usage). If you want to
use
--replicate-same-server-id
make the slave read its own events that you want the slave SQL thread to execute.
•
--replicate-wild-do-table=db_name.tbl_name
Command-Line Format
Option-File Format
Tells the slave thread to restrict replication to statements where any of the updated tables match
the specified database and table name patterns. Patterns can contain the "%" and "_" wildcard
characters, which have the same meaning as for the
specify more than one table, use this option multiple times, once for each table. This works for cross-
database updates. See
This option applies to tables, views, and triggers. It does not apply to stored procedures and
functions. To filter statements operating on the latter objects, use one or more of the
options.
*-db
Example:
--replicate-wild-do-table=foo%.bar%
table where the database name starts with
If the table name pattern is %, it matches any table name and the option also applies to database-
level statements (CREATE
if you use
--replicate-wild-do-table=foo%.%
replicated if the database name matches the pattern foo%.
To include literal wildcard characters in the database or table name patterns, escape them with a
backslash. For example, to replicate all tables of a database that is named my_own%db, but not
DATABASE, and
DROP
[1459]
5.0.1
--replicate-same-server-id
replicate-same-server-id
Permitted Values
Type
boolean
Default
FALSE
[1459], be sure to start the slave with this option before you
--replicate-wild-do-table=name
replicate-wild-do-table
Permitted Values
Type
string
Section 16.2.3, "How Servers Evaluate Replication Filtering
foo
DATABASE, and
DATABASE, DROP
1459
DATABASE), and only if
ALTER
--replicate-*
[1459]
[896] pattern-matching operator. To
LIKE
[1459] replicates only updates that use a
and the table name starts with bar.
ALTER
[1459], database-level statements are
to_name
is the
from_name
value that
from_name
rules are tested.
--log-slave-
Rules".
--replicate-
DATABASE). For example,
if it