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

Cannot showing procedure after minor upgrade

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.1
    • N/A
    • OTHER
    • CentOS

    Description

      Hi all, today i upgraded minor version from 10.1.21 to 10.1.31 (also 10.1.33) with step below

      • stopping mariadb
      • remove mariadb
      • delete all datafiles
      • delete configuration files
      • install newest mariadb
      • do mysql_upgrade
      • do mysql_secure_installation
      • join galera cluster

      but after upgrade, i saw a weird error that either the procedure and function cannot be shown (see #error1).

      It says "column length too big for column '(null)' (max = 65532); use BLOB or TEXT instead."

      i thought that my db tool (toad for mysql) is error or something, but i tried upgrade toad for mysql to the newest version it still same. Also i try another db tool like dbeaver and heidisql are the same

      i try to query directly by shell (see #error2) and facing same error.

      i am sure every step i did was so true and nothing error happen, especially do mysql_upgrade.

      FYI : i create new procedure then i run it, it was success but not for showing

      *UPDATE : try to 'show procedure status' it went normal, but 'show function status' is not

      Attachments

        1. error#1.jpg
          error#1.jpg
          75 kB
        2. error#2.jpg
          error#2.jpg
          35 kB
        3. error#3.JPG
          error#3.JPG
          65 kB

        Activity

          People

            Unassigned Unassigned
            pramudyapp Pramudya Aditya
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.