update MOLT Replicator doc & related

Author: taroface

src/current/_includes/molt/migration-prepare-database.md

@@ -1,6 +1,6 @@
 #### Create migration user on source database
 
-Create a dedicated migration user (e.g., `MIGRATION_USER`) on the source database. This user is responsible for reading data from source tables during the migration. You will pass this username in the [source connection string](#source-connection-string).
+Create a dedicated migration user (for example, `MIGRATION_USER`) on the source database. This user is responsible for reading data from source tables during the migration. You will pass this username in the [source connection string](#source-connection-string).
 
 <section class="filter-content" markdown="1" data-scope="postgres">
 {% include_cached copy-clipboard.html %}
@@ -12,11 +12,31 @@ Grant the user privileges to connect, view schema objects, and select the tables
 
 {% include_cached copy-clipboard.html %}
 ~~~ sql
-GRANT CONNECT ON DATABASE source_database TO MIGRATION_USER;
-GRANT USAGE ON SCHEMA migration_schema TO MIGRATION_USER;
-GRANT SELECT ON ALL TABLES IN SCHEMA migration_schema TO MIGRATION_USER;
-ALTER DEFAULT PRIVILEGES IN SCHEMA migration_schema GRANT SELECT ON TABLES TO MIGRATION_USER;
+GRANT CONNECT ON DATABASE source_database TO migration_user;
+GRANT USAGE ON SCHEMA migration_schema TO migration_user;
+GRANT SELECT ON ALL TABLES IN SCHEMA migration_schema TO migration_user;
+ALTER DEFAULT PRIVILEGES IN SCHEMA migration_schema GRANT SELECT ON TABLES TO migration_user;
 ~~~
+
+{% if page.name != "migrate-bulk-load.md" %}
+Grant the `SUPERUSER` role to the user (recommended for replication configuration):
+
+{% include_cached copy-clipboard.html %}
+~~~ sql
+ALTER USER migration_user WITH SUPERUSER;
+~~~
+
+Alternatively, grant the following permissions to create replication slots, access replication data, create publications, and add tables to publications:
+
+{% include_cached copy-clipboard.html %}
+~~~ sql
+ALTER USER migration_user WITH LOGIN REPLICATION;
+GRANT CREATE ON DATABASE source_database TO migration_user;
+ALTER TABLE migration_schema.table_name OWNER TO migration_user;
+~~~
+
+Run the `ALTER TABLE` command for each table to replicate.
+{% endif %}
 </section>
 
 <section class="filter-content" markdown="1" data-scope="mysql">
@@ -29,9 +49,19 @@ Grant the user privileges to select only the tables you migrate:
 
 {% include_cached copy-clipboard.html %}
 ~~~ sql
-GRANT SELECT ON source_database.* TO MIGRATION_USER@'%';
+GRANT SELECT ON source_database.* TO 'migration_user'@'%';
+FLUSH PRIVILEGES;
+~~~
+
+{% if page.name != "migrate-bulk-load.md" %}
+For replication, grant additional privileges for binlog access:
+
+{% include_cached copy-clipboard.html %}
+~~~ sql
+GRANT REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'migration_user'@'%';
 FLUSH PRIVILEGES;
 ~~~
+{% endif %}
 </section>
 
 <section class="filter-content" markdown="1" data-scope="oracle">

src/current/_includes/molt/molt-docker.md

@@ -1,11 +1,9 @@
-For details on pulling Docker images, refer to [Docker images](#docker-images).
-
-### Performance
+#### Performance
 
 MOLT Fetch, Verify, and Replicator are likely to run more slowly in a Docker container than on a local machine. To improve performance, increase the memory or compute resources, or both, on your Docker container.
 
 {% if page.name == "molt-fetch.md" %}
-### Authentication
+#### Authentication
 
 When using MOLT Fetch with [cloud storage](#bucket-path), it is necessary to specify volumes and environment variables, as described in the following sections for [Google Cloud Storage](#google-cloud-storage) and [Amazon S3](#amazon-s3). 
 
@@ -17,7 +15,7 @@ docker run -it cockroachdb/molt fetch ...
 
 For more information on `docker run`, see the [Docker documentation](https://docs.docker.com/reference/cli/docker/container/run/).
 
-#### Google Cloud Storage
+##### Google Cloud Storage
 
 If you are using [Google Cloud Storage](https://cloud.google.com/storage/docs/access-control) for [cloud storage](#bucket-path):
 
@@ -44,7 +42,7 @@ docker run \
 
 For details on Google Cloud Storage authentication, see [Application Default Credentials](https://cloud.google.com/docs/authentication/application-default-credentials).
 
-#### Amazon S3
+##### Amazon S3
 
 If you are using [Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/security-iam.html) for [cloud storage](#bucket-path):
 
@@ -61,7 +59,7 @@ docker run \
 ~~~
 {% endif %}
 
-### Local connection strings
+#### Local connection strings
 
 When testing locally, specify the host as follows:
 

src/current/_includes/molt/molt-install.md

@@ -15,7 +15,7 @@ The following binaries are included:
 - `replicator`
 
 {{site.data.alerts.callout_success}}
-For ease of use, keep both `molt` and `replicator` in your current **working directory**.
+For ease of use, keep both `molt` and `replicator` in your current working directory.
 {{site.data.alerts.end}}
 
 To display the current version of each binary, run `molt --version` and `replicator --version`.
@@ -71,6 +71,4 @@ To pull a specific version (for example, `v1.1.1`):
 ~~~ shell
 docker pull cockroachdb/replicator:v1.1.1
 ~~~
-{% endif %}
-
-{% if page.name != "molt.md" %}For details on running in Docker, refer to [Docker usage](#docker-usage).{% endif %}
+{% endif %}

src/current/_includes/molt/oracle-migration-prerequisites.md

@@ -23,52 +23,5 @@ Install Oracle Instant Client on the machine that will run `molt` and `replicato
 	~~~
 
 	{{site.data.alerts.callout_success}}
-	You can also download Oracle Instant Client directly	 from the Oracle site for [Linux ARM64](https://www.oracle.com/database/technologies/instant-client/linux-amd64-downloads.html) or [Linux x86-64](https://www.oracle.com/ca-en/database/technologies/instant-client/linux-x86-64-downloads.html).
-	{{site.data.alerts.end}}
-
-{% if page.name != "migrate-bulk-load.md" %}
-#### Enable `ARCHIVELOG`
-
-Enable `ARCHIVELOG` mode on the Oracle database. This is required for Oracle LogMiner, Oracle's built-in changefeed tool that captures DML events for replication.
-
-{% include_cached copy-clipboard.html %}
-~~~ sql
-SELECT log_mode FROM v$database;
-SHUTDOWN IMMEDIATE;
-STARTUP MOUNT;
-ALTER DATABASE ARCHIVELOG;
-ALTER DATABASE OPEN;
-SELECT log_mode FROM v$database;
-~~~
-
-~~~
-LOG_MODE
---------
-ARCHIVELOG
-
-1 row selected.
-~~~
-
-Enable supplemental primary key logging for logical replication:
-
-{% include_cached copy-clipboard.html %}
-~~~ sql
-ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS;
-SELECT supplemental_log_data_min, supplemental_log_data_pk FROM v$database;
-~~~
-
-~~~
-SUPPLEMENTAL_LOG_DATA_MIN SUPPLEMENTAL_LOG_DATA_PK
-------------------------- ------------------------
-IMPLICIT                  YES
-
-1 row selected.
-~~~
-
-Enable `FORCE_LOGGING` to ensure that all data changes are captured for the tables to migrate:
-
-{% include_cached copy-clipboard.html %}
-~~~ sql
-ALTER DATABASE FORCE LOGGING;
-~~~
-{% endif %}
+	You can also download Oracle Instant Client directly from the Oracle site for [Linux ARM64](https://www.oracle.com/database/technologies/instant-client/linux-amd64-downloads.html) or [Linux x86-64](https://www.oracle.com/ca-en/database/technologies/instant-client/linux-x86-64-downloads.html).
+	{{site.data.alerts.end}}

src/current/_includes/molt/replicator-flags-usage.md

@@ -63,7 +63,7 @@ When using `--table-filter`, you must also include `--userscript`. Refer to [Tab
 | `--tlsPrivateKey`  | Path to the server TLS private key for the webhook sink. Refer to [TLS certificate and key](#tls-certificate-and-key). |
 | `--metricsAddr`    | Enable Prometheus metrics at a specified `{host}:{port}`. Metrics are served at `http://{host}:{port}/_/varz`.                       |
 
-- Failback requires `--stagingSchema`, which specifies the staging database name used for replication checkpoints and metadata. The staging schema is first created with [`--stagingCreateSchema`]({% link molt/migrate-load-replicate.md %}). For details on the staging schema, refer to [Staging schema]({% link molt/molt-replicator.md %}#staging-schema).
+- Failback requires `--stagingSchema`, which specifies the staging database name used for replication checkpoints and metadata. The staging schema is first created with [`--stagingCreateSchema`]({% link molt/migrate-load-replicate.md %}). For details on the staging schema, refer to [Staging database]({% link molt/molt-replicator.md %}#staging-database).
 
 - When configuring a [secure changefeed](#tls-certificate-and-key) for failback, you **must** include `--tlsCertificate` and `--tlsPrivateKey`, which specify the paths to the server certificate and private key for the webhook sink connection.