Inconsistent Datatype Error on Tomcat 7 with Oracle 10g

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: No Longer Reproducible
Affects Version/s: 6.1.X EE, 6.2.0 CE M2
Fix Version/s: 6.1.X EE
Component/s: Infrastructure, Infrastructure > DBs, Upgrades
Labels:
None
Environment:
Tomcat 7.0. + Oracle 10. Portal 6.1.x EE GIT ID: 0194e5337a7371291163a76a24d98f2417adaa27.
Tomcat 7.0. + Oracle 10. Portal 6.2.x GIT ID: e8ab3317581dbeea86bd69bf8965bd898de5b282.

Similar Issues:

Show 5 results

Description

1. Config oracle in ext.properties in 5.2.8:
permissions.user.check.algorithm=5

jdbc.default.driverClassName=oracle.jdbc.driver.OracleDriver
jdbc.default.url=jdbc:oracle:thin:@localhost:1521:xe
jdbc.default.username=lportal
jdbc.default.password=password

jdbc.default.acquireIncrement=5
jdbc.default.maxPoolSize=100
jdbc.default.minPoolSize=10
jdbc.default.numHelperThreads=10

liferay.home=d:/home

2. Add 2 Asset Publishers to a page, one as the default view, another with Title View
3. Add a Web Content so the Asset Publishers have something to display.
4. Shutdown 5.2.8
5. Config oracle in ext.properties in 6.1.x or trunk:

permissions.user.check.algorithm=5

jdbc.default.driverClassName=oracle.jdbc.driver.OracleDriver
jdbc.default.url=jdbc:oracle:thin:@localhost:1521:xe
jdbc.default.username=lportal
jdbc.default.password=password

jdbc.default.acquireIncrement=5
jdbc.default.maxPoolSize=100
jdbc.default.minPoolSize=10
jdbc.default.numHelperThreads=10

liferay.home=d:/home

6. Upgrade to 6.1.x or trunk

Console error message:

03:19:47,585 ERROR [MainServlet:205] com.liferay.portal.kernel.events.ActionException: com.liferay.portal.verify.VerifyException: com.liferay.portal.v
erify.VerifyException: java.sql.SQLException: ORA-01735: 鏃犳晥鐨?ALTER TABLE 閫夐」

com.liferay.portal.kernel.events.ActionException: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: java.sql.SQLEx
ception: ORA-01735: 鏃犳晥鐨?ALTER TABLE 閫夐」

        at com.liferay.portal.events.StartupAction.run(StartupAction.java:58)
        at com.liferay.portal.servlet.MainServlet.processStartupEvents(MainServlet.java:1465)
        at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:202)
        at javax.servlet.GenericServlet.init(GenericServlet.java:160)
        at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5015)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5302)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:897)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:873)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1581)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
Caused by: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: java.sql.SQLException: ORA-01735: 鏃犳晥鐨?ALTER TABL
E 閫夐」

        at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:82)
        at com.liferay.portal.verify.VerifyProcessUtil._verifyProcess(VerifyProcessUtil.java:117)
        at com.liferay.portal.verify.VerifyProcessUtil._verifyProcess(VerifyProcessUtil.java:78)
        at com.liferay.portal.verify.VerifyProcessUtil.verifyProcess(VerifyProcessUtil.java:46)
        at com.liferay.portal.events.StartupHelper.verifyProcess(StartupHelper.java:137)
        at com.liferay.portal.events.StartupHelperUtil.verifyProcess(StartupHelperUtil.java:52)
        at com.liferay.portal.tools.DBUpgrader.verify(DBUpgrader.java:210)
        at com.liferay.portal.events.StartupAction.doRun(StartupAction.java:182)
        at com.liferay.portal.events.StartupAction.run(StartupAction.java:52)
        ... 20 more
Caused by: com.liferay.portal.verify.VerifyException: java.sql.SQLException: ORA-01735: 鏃犳晥鐨?ALTER TABLE 閫夐」

        at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:82)
        at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:89)
        at com.liferay.portal.verify.VerifyProcessSuite.doVerify(VerifyProcessSuite.java:28)
        at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:79)
        ... 28 more
Caused by: java.sql.SQLException: ORA-01735: 鏃犳晥鐨?ALTER TABLE 閫夐」

        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)
        at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
        at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
        at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:961)
        at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190)
        at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1657)
        at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1626)
        at com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:64)
        at com.liferay.portal.dao.db.BaseDB.runSQL(BaseDB.java:264)
        at com.liferay.portal.dao.db.BaseDB.runSQL(BaseDB.java:284)
        at com.liferay.portal.dao.db.BaseDB.runSQL(BaseDB.java:277)
        at com.liferay.portal.verify.VerifyProcess.runSQL(VerifyProcess.java:48)
        at com.liferay.portal.verify.VerifyOracle.doVerify(VerifyOracle.java:69)
        at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:79)
        ... 31 more
Stopping the server due to unexpected startup errors

D:\Git\Liferay-6.1.x\liferay-portal-6.1.x1\tomcat-7.0.25\bin>

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Joerg Larbig added a comment - 06/Aug/12 5:52 AM

I got the same error and in my case the problem was that the upgrade process
tried to update tables in the oracle recycle bin (since the database has been used before the recycle bin was not empty).

After I changed the select statement to fetch the tables to update in com.liferay.portal.verify.VerifyOracle
not to receive tables from the recycle bin like

ps = con.prepareStatement(
"select table_name, column_name, data_length from " +
"user_tab_columns where data_type = 'VARCHAR2' and " +
"char_used = 'B' and table_name not like 'BIN$'");

everything works fine.

Show

Joerg Larbig added a comment - 06/Aug/12 5:52 AM I got the same error and in my case the problem was that the upgrade process tried to update tables in the oracle recycle bin (since the database has been used before the recycle bin was not empty). After I changed the select statement to fetch the tables to update in com.liferay.portal.verify.VerifyOracle not to receive tables from the recycle bin like ps = con.prepareStatement( "select table_name, column_name, data_length from " + "user_tab_columns where data_type = 'VARCHAR2' and " + "char_used = 'B' and table_name not like 'BIN$'"); everything works fine.

Hide

Permalink

Joerg Larbig added a comment - 09/Aug/12 2:36 AM

"select table_name, column_name, data_length from " +
"user_tab_columns where data_type = 'VARCHAR2' and " +
"char_used = 'B' and table_name not like 'BIN$%'");

Show

Joerg Larbig added a comment - 09/Aug/12 2:36 AM "select table_name, column_name, data_length from " + "user_tab_columns where data_type = 'VARCHAR2' and " + "char_used = 'B' and table_name not like 'BIN$%'");

Hide

Permalink

Paul Piao added a comment - 27/Aug/12 7:03 PM - edited

Reproduced on:
Tomcat 7.0. + Oracle 10. Portal 6.1.x EE GIT ID: 0194e5337a7371291163a76a24d98f2417adaa27.
Tomcat 7.0. + Oracle 10. Portal 6.2.x GIT ID: e8ab3317581dbeea86bd69bf8965bd898de5b282.

Inconsistent Datatype Error in console.

Show

Paul Piao added a comment - 27/Aug/12 7:03 PM - edited Reproduced on: Tomcat 7.0. + Oracle 10. Portal 6.1.x EE GIT ID: 0194e5337a7371291163a76a24d98f2417adaa27. Tomcat 7.0. + Oracle 10. Portal 6.2.x GIT ID: e8ab3317581dbeea86bd69bf8965bd898de5b282. Inconsistent Datatype Error in console.

Hide

Permalink

Ken Duenwald added a comment - 20/Dec/12 9:50 AM

No Longer Reproducible through Manual Testing following the steps in the description.

No Longer Reproducible on:
Tomcat 7.0.27 + MySQL 5. Portal 6.1.x EE GIT ID: 8d8cc30040901b325ce2e271d0ec18c9ac6a2bae.

If the steps are run with permissions.user.check.algorithm=5 included in portal-ext, there are no exceptions but the user cannot log in due to permission issues. However, if the steps are run with permissions.user.check.algorithm=5 removed from portal-ext, the upgrade process and login process work fine and I can see both AP portlets.

I'm unable to directly upgrade from 5.2.8 to 6.2.x due to the outdated permission algorithm and 6.2.x requiring permission algorithm 6 or above to start.

In all cases, I'm unable to view the original bug and exceptions so the ticket is being closed as a No Longer Reproducible. This ticket can be reopened if the bug is found again.

Show

Ken Duenwald added a comment - 20/Dec/12 9:50 AM No Longer Reproducible through Manual Testing following the steps in the description. No Longer Reproducible on: Tomcat 7.0.27 + MySQL 5. Portal 6.1.x EE GIT ID: 8d8cc30040901b325ce2e271d0ec18c9ac6a2bae. If the steps are run with permissions.user.check.algorithm=5 included in portal-ext, there are no exceptions but the user cannot log in due to permission issues. However, if the steps are run with permissions.user.check.algorithm=5 removed from portal-ext, the upgrade process and login process work fine and I can see both AP portlets. I'm unable to directly upgrade from 5.2.8 to 6.2.x due to the outdated permission algorithm and 6.2.x requiring permission algorithm 6 or above to start. In all cases, I'm unable to view the original bug and exceptions so the ticket is being closed as a No Longer Reproducible. This ticket can be reopened if the bug is found again.

People

Assignee:

Ken Duenwald

Reporter:

Paul Piao

Participants of an Issue:

Joerg Larbig, Ken Duenwald, Paul Piao

Vote (0)

Watch (4)

Dates

Created:

14/May/12 8:33 PM

Updated:

03/Apr/13 5:02 PM

Resolved:

20/Dec/12 3:17 AM

Days since last comment:

21 weeks, 5 days ago

Agile

View on Board

~~LPS-27043~~	Inconsistent Datatype Error using JNDI name on Weblogic 10.3.2 with Oracle 10g
~~LPS-34209~~	Unable to add long text to css in Oracle 10g
LPS-12684	liferay 6.0.4/6.05 and oracle 10G result in ORA-00907 error
~~LPS-13140~~	Kaleo workflow is not support for Oracle 10g
~~LPS-31833~~	Unable to add a wiki article or message board thread on Tomcat + Oracle 11