Description

An error may occur when performing data subsetting or Synthetic Data Masking (SDM) for MySQL databases. No data will be inserted into the destination database when the following error is received.


Loading local data is disabled; this must be enabled on both the 
client and server side
Generic


In This Article


Troubleshooting Options

Users can try one of the following: 

  1. Manually set the "local_infile" option to "true" for the MySQL client and server within their configuration file (.ini. or .cnf). 
  2. Manually set the "local_infile" option to "true" from the command line.
  3. Explicitly set the option to "true" within the config.properties file. 


How to Manually Set to "True" from Command Line

  1. Log into the MySQL Server and set the Global local_infile option to "1".

    SET GLOBAL local_infile=1;
    Generic


  2. Then use the quit command to log off.

    quit
    Generic

  3. Include --local-infile=1 as part of the login command to set this option for the user's session. 

    mysql --local-infile=1 -u root -p
    Generic


Example

mysql> SET GLOBAL local_infile=1;
Query OK, 0 rows affected (0.00 sec)

mysql>quit
bye

mysql> mysql --local-infile=1 -u root -p
Generic


To test, rerun the G-Migration+ command and check the database to see if the data migration completes. 

Use <Database Name>;
Generic
select * from <table name>;
Generic

If the option was set to "true" correctly, then the data should appear within the destination database. If not, try including the option in the configuration file(s), as discussed in the next section. 


How to Explicitly Set to "True" in the Config.Properties File

When included in the config.properties file, it will set the option to "true" when the data is migrated, which allows the data to be inserted into the destination (i.e., target) database. 


To do this, users will need to add allowLoadLocalInfile=true to the url line in the config.properties file (as shown below):