掲示板

Liferay 5.1.4 EE update to 6.0 EE SP1 problem

thumbnail
13年前 に Jaakko Yli-Koivisto によって更新されました。

Liferay 5.1.4 EE update to 6.0 EE SP1 problem

New Member 投稿: 4 参加年月日: 08/12/01 最新の投稿
Hi!

I'm having some difficulties updating Liferay 5.1.4 EE to 6.0 EE SP1.

I've tried to do the update as instructed:

5.1.4 => 5.1 SP5 => 5.2 SP4 => 6.0 SP1 and it all goes well until I finally try to start 6.0 SP1 where Liferay does not even finish the update because of this error:

Caused by: javax.jcr.RepositoryException: Cannot instantiate persistence manager org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager
at org.apache.jackrabbit.core.RepositoryImpl.createPersistenceManager(RepositoryImpl.java:1433)
at org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(RepositoryImpl.java:502)
at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:355)
at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:673)
at org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:231)
at org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:279)
at org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:375)
at com.liferay.portal.jcr.jackrabbit.JCRFactoryImpl.createSession(JCRFactoryImpl.java:67)
at com.liferay.portal.jcr.JCRFactoryUtil.createSession(JCRFactoryUtil.java:43)
at com.liferay.portal.jcr.JCRFactoryUtil.createSession(JCRFactoryUtil.java:47)
at com.liferay.documentlibrary.util.JCRHook.updateFile(JCRHook.java:771)
... 63 more
Caused by: java.sql.SQLException: Schema generation error: Issuing statement: create table J_V_PM_REFS (NODE_ID raw(16) not null, REFS_DATA blob not null)
at org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager.checkSchema(BundleDbPersistenceManager.java:486)
at org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager.init(BundleDbPersistenceManager.java:603)
at org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager.init(OraclePersistenceManager.java:102)
at org.apache.jackrabbit.core.RepositoryImpl.createPersistenceManager(RepositoryImpl.java:1429)
... 73 more
Caused by: java.sql.SQLException: ORA-00955: name is already used by an existing object
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)

I have Jackrabbit configured to use Oracle 11g and it works fine with 5.1.4 and 5.2 SP4 (and SP5). Here is my Jackrabbit configuration:


<!--?xml version="1.0"?-->
<repository>
       <filesystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem">
            <param name="driver" value="oracle.jdbc.driver.OracleDriver">
			<param name="url" value="jdbc:oracle:thin:@localhost:1521:test">
			<param name="user" value="test">
			<param name="password" value="test">
            <param name="schemaObjectPrefix" value="JRREP_">
        </filesystem>

	<security appname="Jackrabbit">
		<accessmanager class="org.apache.jackrabbit.core.security.SimpleAccessManager" />
		<loginmodule class="org.apache.jackrabbit.core.security.SimpleLoginModule">
			<param name="anonymousId" value="anonymous">
		</loginmodule>
	</security>
	<workspaces rootPath="${rep.home}/workspaces" defaultWorkspace="liferay" />
	<workspace name="${wsp.name}">
             <filesystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem">
                     <param name="driver" value="oracle.jdbc.driver.OracleDriver">
					<param name="url" value="jdbc:oracle:thin:@localhost:1521:test">
					<param name="user" value="test">
					<param name="password" value="test">
                     <param name="schemaObjectPrefix" value="J_FS_${wsp.name}_">
             </filesystem>

              <persistencemanager class="org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager">
                   <param name="driver" value="oracle.jdbc.driver.OracleDriver">
                   <param name="url" value="jdbc:oracle:thin:@localhost:1521:test">
                   <param name="user" value="test">
                   <param name="password" value="test">				   
                   <param name="schemaObjectPrefix" value="J_PM_${wsp.name}_">
                   <param name="externalBLOBs" value="false">
              </persistencemanager>

	</workspace>
	<versioning rootpath="${rep.home}/version">
               <filesystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem">
            <param name="driver" value="oracle.jdbc.driver.OracleDriver">
			<param name="url" value="jdbc:oracle:thin:@localhost:1521:test">
			<param name="user" value="test">
			<param name="password" value="test">
            <param name="schemaObjectPrefix" value="J_V_FS_">
              </filesystem>

		 <persistencemanager class="org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager">
                   <param name="url" value="jdbc:oracle:thin:@localhost:1521:test">
                   <param name="driver" value="oracle.jdbc.driver.OracleDriver">
                   <param name="user" value="test">
                   <param name="password" value="test">				   
                   <param name="schemaObjectPrefix" value="J_V_PM_">
                   <param name="externalBLOBs" value="false">
               </persistencemanager>
	</versioning>
    <cluster id="node_1" syncdelay="5">
		<journal class="org.apache.jackrabbit.core.journal.OracleDatabaseJournal">
			<param name="revision" value="${rep.home}/revision">			
			<param name="driver" value="oracle.jdbc.driver.OracleDriver">
			<param name="url" value="jdbc:oracle:thin:@localhost:1521:test">
			<param name="user" value="test">
			<param name="password" value="test">
		</journal>
    </cluster>
</repository>



Has anybody had similar problems with Liferay 6.0 EE- update and Jackrabbit?

I have also tried updating straight from 5.1.4 => 6.0 and then I get:


Caused by: org.apache.jackrabbit.core.cluster.ClusterException: Cluster initialization failed: org.apache.jackrabbit.core.cluster.ClusterNode@9d13b8
at org.apache.jackrabbit.core.cluster.ClusterNode.init(ClusterNode.java:209)
at org.apache.jackrabbit.core.cluster.ClusterNode.init(ClusterNode.java:190)
at org.apache.jackrabbit.core.RepositoryImpl.createClusterNode(RepositoryImpl.java:724)
... 72 more
Caused by: javax.jcr.RepositoryException: Journal initialization failed: org.apache.jackrabbit.core.journal.OracleDatabaseJournal@24b7c5
at org.apache.jackrabbit.core.config.RepositoryConfigurationParser$3.getJournal(RepositoryConfigurationParser.java:891)
at org.apache.jackrabbit.core.config.ClusterConfig.getJournal(ClusterConfig.java:86)
at org.apache.jackrabbit.core.cluster.ClusterNode.init(ClusterNode.java:204)
... 74 more
Caused by: org.apache.jackrabbit.core.journal.JournalException: Unable to create connection.
at org.apache.jackrabbit.core.journal.DatabaseJournal.init(DatabaseJournal.java:277)
at org.apache.jackrabbit.core.config.RepositoryConfigurationParser$3.getJournal(RepositoryConfigurationParser.java:888)
... 76 more
Caused by: java.sql.SQLException: ORA-00902: invalid datatype
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)

This also seems to be related to Jackrabbit... :-(
thumbnail
13年前 に Jaakko Yli-Koivisto によって更新されました。

RE: Liferay 5.1.4 EE update to 6.0 EE SP1 problem

New Member 投稿: 4 参加年月日: 08/12/01 最新の投稿
Just verified that this happens even using a fresh 5.2 SP5 update to 6.0 SP1 with a clean database. (Using Jackrabbit with Oracle 11g)

But if I use Jackrabbit with MySQL then the update is ok so this must be an Oracle & Jackrabbit issue...
12年前 に John Stamatis によって更新されました。

RE: Liferay 5.1.4 EE update to 6.0 EE SP1 problem

New Member 投稿: 2 参加年月日: 10/08/25 最新の投稿
I have the same problem while upgrading 5.2.3CE to 6.0EE SP2.
Did you find a solution for this problem ???

Thanks
thumbnail
11年前 に Jaakko Yli-Koivisto によって更新されました。

RE: Liferay 5.1.4 EE update to 6.0 EE SP1 problem

New Member 投稿: 4 参加年月日: 08/12/01 最新の投稿
John Stamatis:
I have the same problem while upgrading 5.2.3CE to 6.0EE SP2.
Did you find a solution for this problem ???

Thanks


Hi! Sorry for the late answer but the solution here for me was to migrate all the documents to disk (using AdvancedFileSystemHook) before the actual update...