Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7587

ERROR 1064 (42000) when trying to restore a mysqldump in mariadb 10.0.16 - wheezy-1

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not a Bug
    • 10.0.16
    • N/A
    • Admin statements
    • None
    • debian wheezy 7.8

    Description

      server1:~# mysql
      Welcome to the MariaDB monitor. Commands end with ; or \g.
      Your MariaDB connection id is 6085
      Server version: 10.0.16-MariaDB-1~wheezy-log mariadb.org binary distribution

      Copyright (c) 2000, 2014, Oracle, MariaDB Corporation Ab and others.

      Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

      MariaDB [(none)]> mysql -e "source /data/disk/arch/sql/server1.domain.biz-150209-0008/xnlasocitgyabcom.sql.gz" xnlas
      ocitgyabc_0 ;
      ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server ve
      rsion for the right syntax to use near 'mysql -e "source /data/disk/arch/sql/server1.domain.biz-150209-0008/xnlasoci
      tgy' at line 1
      MariaDB [(none)]> mysql xnlasocitygyabc_0 < /data/disk/arch/sql/server1.domain.biz-150209-0008/xnlasocitgyabcom.sql.
      gz
      -> ;
      ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server ve
      rsion for the right syntax to use near 'mysql xnlasocitygyabc_0 < /data/disk/arch/sql/server1.domain.biz-150209-0008
      /xn' at line 1
      MariaDB [(none)]>

      Attachments

        Activity

          People

            Unassigned Unassigned
            EdNett Ed Jackson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.