Note – MySQL is supported as a Target by Repstance Advanced Edition only (see Supported Database Requirements).
These parameters are used by prepare, validate and remove with database=target dbtype=mysql (see Prepare Target Database, Validate Database and Remove Repstance Objects from Database). The login that is given in user needs the privileges that are described in Database Privileges. The page applies to MySQL, Aurora MySQL and MariaDB.
| Parameter | Description |
|---|---|
| database | target. Required. |
| dbtype | mysql. Required. |
| generatesql | 1 makes prepare return the SQL script and change nothing. The default is 0: prepare creates the objects. validate does not use the parameter, and remove removes the objects whatever its value. |
| server | The host name or the IP address of the MySQL server. Required. |
| port | The TCP port of the MySQL server, usually 3306. Required. |
| user | The login that Repstance connects with. Required. |
| password | The password of the login. Required. |
| dbname | The database to connect to. It is optional and does not decide where the objects go: prepare always creates them in a database that is named repi. |
Return the script instead of running it. No connection is made. The procedures contain semicolons, so the script changes the delimiter: run it with the mysql client:
repcli prepare database=target dbtype=mysql server=mysql-tgt.example.com port=3306 dbname=testDB user=repuser password=Passw0rd123 generatesql=1
[Completed]:
---- SQL ----
create database if not exists repi;
create table if not exists repi.apply_ckpt(
apply_id int primary key,
file_sequence int not null,
md_sequence int not null,
position bigint not null,
first_lsn char(22) not null,
ckpt_lsn char(22) not null,
...The form “Database Settings” of an Apply Process for MySQL has the fields “Server”, “Port”, “Username”, “Password” and “Database Name”. The buttons that prepare the database are shown in Prepare Target Database:
Prev page:
PostgreSQL as TargetNext page:
Snowflake as Target