Oracle 5.0 Reference Manual page 1472

Replication and Binary Logging Options and Variables
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
Normally, a slave does not log to its own binary log any updates that are received from a master
server. This option tells the slave to log the updates performed by its SQL thread to its own binary
log. For this option to have any effect, the slave must also be started with the
option to enable binary logging.
chain replication servers. For example, you might want to set up replication servers using this
arrangement:
A -> B -> C
Here, serves as the master for the slave B, and
A
work, must be both a master and a slave. You must start both
B
to enable binary logging, and
received from are logged by
A
•
--log-warnings[=level]
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
Disabled by
This option causes a server to print more messages to the error log about what it is doing. With
respect to replication, the server generates warnings that it succeeded in reconnecting after a
network/connection failure, and informs you as to how each slave thread started. This option is
enabled by default; to disable it, use
logged to the error log unless the value is greater than 1.
Note that the effects of this option are not limited to replication. It produces warnings across a
spectrum of server activities.
--log-slave-updates
log-slave-updates
Yes,
log_slave_updates
log_slave_updates
Global
No
Permitted Values
Type
boolean
Default
FALSE
--log-slave-updates
B
with the
B --log-slave-updates
to its binary log.
B
[414]
--log-warnings[=#]
-W [#]
log-warnings
Yes, [464]
log_warnings
log_warnings
Global, Session
Yes
skip-log-warnings
Permitted Values
Platform
64
Bit Size
Type
numeric
Default
1
Range
0 .. 18446744073709547520
--skip-log-warnings
1452
[1471]
[1451] is used when you want to
serves as the master for the slave C. For this to
and with
A B
[1451] option so that updates
[414]. Aborted connections are not
[1467]
--log-bin
[1467]
--log-bin