DbEnv::rep_set_limit API Ref

#include <db_cxx.h>

int DbEnv::rep_set_limit(u_int32_t gbytes, u_int32_t bytes);

int DbEnv::rep_get_limit(u_int32_t *gbytesp, u_int32_t *bytesp);


Description: DbEnv::rep_set_limit

The DbEnv::rep_set_limit method sets a byte-count limit on the amount of data that will be transmitted from a site in response to a single message processed by the DbEnv::rep_process_message method. The limit is not a hard limit, and the record that exceeds the limit is the last record to be sent.

Record transmission throttling is turned on by default with a limit of 10MB.

If the values passed to the DbEnv::rep_set_limit method are both zero, then the transmission limit is turned off.

The database environment's replication subsystem may also be configured using the environment's DB_CONFIG file. The syntax of the entry in that file is a single line with the string "rep_set_limit", one or more whitespace characters, and the limit specified in two parts: the gigabytes and the bytes parameters. For example, "rep_set_limit 0 1048576" sets a 1 megabyte limit. Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

The DbEnv::rep_set_limit method configures a database environment, not only operations performed using the specified DbEnv handle.

The DbEnv::rep_set_limit method may be called at any time during the life of the application.

The DbEnv::rep_set_limit method either returns a non-zero error value or throws an exception that encapsulates a non-zero error value on failure, and returns 0 on success.

Parameters
bytes gbytes

Description: rep_get_limit

The DbEnv::rep_get_limit method may be called at any time during the life of the application.

The DbEnv::rep_get_limit method either returns a non-zero error value or throws an exception that encapsulates a non-zero error value on failure, and returns 0 on success.

Parameters
bytesp gbytesp


Class DbEnv
See Also Replication and Related Methods

APIRef

Copyright (c) 1996,2008 Oracle. All rights reserved.