<?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>topic Re: force upgrade db schema 4.2a in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/force-upgrade-db-schema-4-2a/m-p/275985#M229115</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I got this error when locally upgrading from 4.0.0 to 4.1.2 because I had done the following:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;* Built and started 4.1.2 locally, which created alf_tenant tables in my local database&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;* Executed a remote cold backup (from 4.0.0) and local restore into my local database, but &lt;/SPAN&gt;&lt;EM&gt;didn't delete the existing alfresco database before importing&lt;/EM&gt;&lt;BR /&gt;&lt;SPAN&gt;* Tried to start 4.1.2, displaying the same error&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem was that the data thought it was running pre-4.1.2, but the database had a table schema of 4.1.2 (such as a new alf_tenant table). The cold backup process only drops existing tables, not new tables that didn't exist before.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;By deleting the existing database and executing the cold backup restore again, the database upgrade process continued as expected.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Jan 2013 22:27:51 GMT</pubDate>
    <dc:creator>jevon</dc:creator>
    <dc:date>2013-01-14T22:27:51Z</dc:date>
    <item>
      <title>force upgrade db schema 4.2a</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/force-upgrade-db-schema-4-2a/m-p/275984#M229114</link>
      <description>I am trying to upgrade to 4.2a. I have succefully upgraded one but my second server does not want to upgradeit keeps barking the followingINFO: ProcessEngine default created2012-10-25 07:59:57,007&amp;nbsp; INFO&amp;nbsp; [extensions.webscripts.TemplateProcessorRegistry] [localhost-startStop-1] Registered template pr</description>
      <pubDate>Thu, 25 Oct 2012 13:08:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/force-upgrade-db-schema-4-2a/m-p/275984#M229114</guid>
      <dc:creator>sharifu</dc:creator>
      <dc:date>2012-10-25T13:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: force upgrade db schema 4.2a</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/force-upgrade-db-schema-4-2a/m-p/275985#M229115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I got this error when locally upgrading from 4.0.0 to 4.1.2 because I had done the following:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;* Built and started 4.1.2 locally, which created alf_tenant tables in my local database&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;* Executed a remote cold backup (from 4.0.0) and local restore into my local database, but &lt;/SPAN&gt;&lt;EM&gt;didn't delete the existing alfresco database before importing&lt;/EM&gt;&lt;BR /&gt;&lt;SPAN&gt;* Tried to start 4.1.2, displaying the same error&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem was that the data thought it was running pre-4.1.2, but the database had a table schema of 4.1.2 (such as a new alf_tenant table). The cold backup process only drops existing tables, not new tables that didn't exist before.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;By deleting the existing database and executing the cold backup restore again, the database upgrade process continued as expected.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jan 2013 22:27:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/force-upgrade-db-schema-4-2a/m-p/275985#M229115</guid>
      <dc:creator>jevon</dc:creator>
      <dc:date>2013-01-14T22:27:51Z</dc:date>
    </item>
  </channel>
</rss>

