No, the
-RO parameter does not use buffers from the (-B) shared buffer pool.
When using the -RO parameter, buffers will be allocated within a
private buffer pool. This means no shared memory, database buffer pool, shared memory locks, lock table are touched.
If the -B parameter is specified with the binary dump session, provided -Bpmax allows the number of buffers and each concurrent binary dump session does not exceed 25% of the primary buffer pool (-B) value, private buffers are allocated from shared memory for the session.
For example: 2000 buffers will be allocated in a private buffer pool
$ proutil <dbname> -C dump <tablename> <destination-file> -RO -B 2000
Warning: another user is using this database in update mode.
Accessing the database with -RO may give unexpected results. (1531)
WARNING: Before-image file of database <name> is not truncated. (1552)
Using index <n> for dump of table <tablename>. (6101)
Dumped <n> records. (13932)
Binary Dump complete. (6254)
It is not recommended to use the -RO parameter when the database is running in multi-user mode with other users modifying data, as the blocks and records could change or be incomplete when the binary dump reads them, which can cause the process to fail and/or the output files to become corrupt.
