Documentation Home
MySQL 5.6 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 31.4Mb
PDF (A4) - 31.5Mb
PDF (RPM) - 29.8Mb
HTML Download (TGZ) - 7.5Mb
HTML Download (Zip) - 7.5Mb
HTML Download (RPM) - 6.5Mb
Man Pages (TGZ) - 177.2Kb
Man Pages (Zip) - 287.6Kb
Info (Gzip) - 3.0Mb
Info (Zip) - 3.0Mb
Excerpts from this Manual

MySQL 5.6 Reference Manual  /  ...  /  ndb_move_data — NDB Data Copy Utility

18.4.15 ndb_move_data — NDB Data Copy Utility

ndb_move_data copies data from one NDB table to another.

Usage

The program is invoked with the names of the source and target tables; either or both of these may be qualified optionally with the database name. Both tables must use the NDB storage engine.

ndb_move_data options source target

The following table includes options that are specific to ndb_move_data. Additional descriptions follow the table. For options common to most NDB Cluster programs (including ndb_move_data), see Section 18.4.29, “Options Common to NDB Cluster Programs — Options Common to NDB Cluster Programs”.

Table 18.315 Command-line options for the ndb_move_data program

Format Description Added, Deprecated, or Removed

--abort-on-error

Dump core on permanent error (debug option)

All MySQL 5.6 based releases

--character-sets-dir=name

Directory where character sets are

All MySQL 5.6 based releases

--database=dbname,

-d

Name of the database in which the table is found

All MySQL 5.6 based releases

--drop-source

Drop source table after all rows have been moved

All MySQL 5.6 based releases

--error-insert

Insert random temporary errors (testing option)

All MySQL 5.6 based releases

--exclude-missing-columns

Ignore extra columns in source or target table

All MySQL 5.6 based releases

--lossy-conversions,

-l

Allow attribute data to be truncated when converted to a smaller type

All MySQL 5.6 based releases

--promote-attributes,

-A

Allow attribute data to be converted to a larger type

All MySQL 5.6 based releases

--staging-tries=x[,y[,z]]

Specify tries on temporary errors. Format is x[,y[,z]] where x=max tries (0=no limit), y=min delay (ms), z=max delay (ms)

All MySQL 5.6 based releases

--verbose

Enable verbose messages

All MySQL 5.6 based releases


  • --abort-on-error

    Property Value
    Command-Line Format --abort-on-error
    Type Boolean
    Default Value FALSE

    Dump core on permanent error (debug option).

  • --character-sets-dir=name

    Property Value
    Command-Line Format --character-sets-dir=name
    Type String
    Default Value [none]

    Directory where character sets are.

  • --database=dbname, -d

    Property Value
    Command-Line Format --database=dbname
    Type String
    Default Value TEST_DB

    Name of the database in which the table is found.

  • --drop-source

    Property Value
    Command-Line Format --drop-source
    Type Boolean
    Default Value FALSE

    Drop source table after all rows have been moved.

  • --error-insert

    Property Value
    Command-Line Format --error-insert
    Type Boolean
    Default Value FALSE

    Insert random temporary errors (testing option).

  • --exclude-missing-columns

    Property Value
    Command-Line Format --exclude-missing-columns
    Type Boolean
    Default Value FALSE

    Ignore extra columns in source or target table.

  • --lossy-conversions, -l

    Property Value
    Command-Line Format --lossy-conversions
    Type Boolean
    Default Value FALSE

    Allow attribute data to be truncated when converted to a smaller type.

  • --promote-attributes, -A

    Property Value
    Command-Line Format --promote-attributes
    Type Boolean
    Default Value FALSE

    Allow attribute data to be converted to a larger type.

  • --staging-tries=x[,y[,z]]

    Property Value
    Command-Line Format --staging-tries=x[,y[,z]]
    Type String
    Default Value 0,1000,60000

    Specify tries on temporary errors. Format is x[,y[,z]] where x=max tries (0=no limit), y=min delay (ms), z=max delay (ms).

  • --verbose

    Property Value
    Command-Line Format --verbose
    Type Boolean
    Default Value FALSE

    Enable verbose messages.


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.