<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Changing JDBC connector jar can affect migration?</title>
  <link rel="self" href="https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=121492916" />
  <subtitle>Changing JDBC connector jar can affect migration?</subtitle>
  <id>https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=121492916</id>
  <updated>2026-04-03T19:08:04Z</updated>
  <dc:date>2026-04-03T19:08:04Z</dc:date>
  <entry>
    <title>RE: Changing JDBC connector jar can affect migration?</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121494846" />
    <author>
      <name>Olaf Kock</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121494846</id>
    <updated>2022-08-14T11:09:05Z</updated>
    <published>2022-08-14T11:09:05Z</published>
    <summary type="html">&lt;p&gt;Hard to say: Anything can happen with software that's that old. Is
  the JDBC driver compatible to your environment (namely the JDK)? And
  if the upgrade is running with the standard JDBC driver: Why bother
  running it with another one? I'd assume that the compatibility was
  tested with the stock driver available at that time, and does not
  necessarily hold for any third party (or newer) driver.&lt;/p&gt;</summary>
    <dc:creator>Olaf Kock</dc:creator>
    <dc:date>2022-08-14T11:09:05Z</dc:date>
  </entry>
  <entry>
    <title>Changing JDBC connector jar can affect migration?</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121492915" />
    <author>
      <name>Kaushal Karande</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=121492915</id>
    <updated>2022-08-10T15:12:05Z</updated>
    <published>2022-08-09T16:32:36Z</published>
    <summary type="html">&lt;p&gt;Hi, I have Liferay 6.0.5 version which is connected with PostgreSQL
  version 11.8. As per compatibility matrix of 6.0 liferay is compatible
  with PostgreSQL 8.4, but I changed the JDBC connector jar inside sever
  lib folder. I am able to populate database with liferay 6.0.5 tables
  without any error. Similarly I have Liferay 6.2 in which I had updated
  the JDBC connector jar. &lt;/p&gt;
&lt;p&gt;Now I am trying to Migrate from Liferay 6.0.5 to 6.2. While Migrating
  I am getting error as (&lt;strong&gt;Could&lt;/strong&gt;
  &lt;strong&gt;not&lt;/strong&gt;
  &lt;strong&gt;find&lt;/strong&gt;
  &lt;strong&gt;MediaLib&lt;/strong&gt;
  &lt;strong&gt;Accelerator&lt;/strong&gt;
  &lt;strong&gt;Wrapper&lt;/strong&gt;). And my liferay migration got stuck. Same
  Migration I carried using PostgreSQL 8.4 as a database and Liferay
  bundled postgres jar, I didn't face any error. &lt;/p&gt;
&lt;p&gt;So my question is do changing JDBC connector jars impact Liferay
  Migration process?&lt;/p&gt;
&lt;p&gt;Note: I am using Liferay 6.0.5 bundled with JBoss, Liferay 6.2
  bundled with JBoss, JDK 1.6.45 and PostgreSQL 11.8.&lt;/p&gt;</summary>
    <dc:creator>Kaushal Karande</dc:creator>
    <dc:date>2022-08-09T16:32:36Z</dc:date>
  </entry>
</feed>
