<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: upgrade hive schema failed in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/upgrade-hive-schema-failed/m-p/51241#M5925</link>
    <description>Try this out. I think you need to use the version for which you are trying to upgrade to, but you can only do that if the parcel for it has been pushed to all of the nodes already. This may help you get the exact Hive version needed for the next command.&lt;BR /&gt;&lt;BR /&gt;schematool -dbType mysql -info.&lt;BR /&gt;&lt;BR /&gt;This will generate the upgrade scripts that the wizard is running. What I would try to do is create a copy of your metastore db and then manually run scripts to see exactly were it hits the error.&lt;BR /&gt;&lt;BR /&gt;schematool -dbType mysql -upgradeSchemaFrom &amp;lt;old-hive-version&amp;gt; -dryRun&lt;BR /&gt;&lt;BR /&gt;It just hit me, the DB was changed but not the tables. They will keep the original charset they were created with. Once you have the problematic table(s) you can changes those with this command.&lt;BR /&gt;&lt;BR /&gt;I tried finding any thing for Cloudera on if you should be making a smaller jump as that is the case sometimes but I couldn't find anything. You could try that as well, see if you can upgrade to something lower like CDH 5.5.x and then going to CDH 5.10.x.&lt;BR /&gt;&lt;BR /&gt;ALTER TABLE tbl_name&lt;BR /&gt;[[DEFAULT] CHARACTER SET charset_name]&lt;BR /&gt;[COLLATE collation_name]</description>
    <pubDate>Tue, 21 Feb 2017 16:36:45 GMT</pubDate>
    <dc:creator>mbigelow</dc:creator>
    <dc:date>2017-02-21T16:36:45Z</dc:date>
  </channel>
</rss>

