You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2018/11/06 10:29:05 UTC
[jira] [Closed] (OAK-7855) rdbmk: Invalid SplitDocType when run on
non-upgraded DB
[ https://issues.apache.org/jira/browse/OAK-7855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella closed OAK-7855.
---------------------------------
Bulk close 1.9.10
> rdbmk: Invalid SplitDocType when run on non-upgraded DB
> -------------------------------------------------------
>
> Key: OAK-7855
> URL: https://issues.apache.org/jira/browse/OAK-7855
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk, rdbmk
> Affects Versions: 1.8.0
> Reporter: Marcel Reutegger
> Assignee: Julian Reschke
> Priority: Major
> Fix For: 1.10, 1.8.9, 1.9.10
>
> Attachments: OAK-7855-2.diff, OAK-7855-3.patch, OAK-7855.diff
>
>
> After upgrading a repository from 1.8.2 to 1.8.7 on RDB the background update thread started to log warnings that complain about invalid SplitDocType:
> {noformat}
> java.lang.IllegalArgumentException: Not a valid SplitDocType :0
> {noformat}
> It is also worth noting that the automatic database schema upgrade fails on that repository with:
> {noformat}
> org.apache.jackrabbit.oak.plugins.document.rdb.RDBDocumentStore Attempted to upgrade NODES to DB level 2 using 'alter table NODES add SDTYPE smallint', but failed - will continue without.
> com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=Q1D18T05;ALTER TABLE;G031.NODES, DRIVER=4.23.42
> {noformat}
> and
> {noformat}
> org.apache.jackrabbit.oak.plugins.document.rdb.RDBDocumentStore Attempted to upgrade NODES to DB level 2 using 'create index NODES_SDT on NODES (SDTYPE) exclude null keys', but failed - will continue without.
> com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-205, SQLSTATE=42703, SQLERRMC=SDTYPE;G031.NODES, DRIVER=4.23.42
> {noformat}
> It turns out this is unrelated to the update from 1.8.2 to 1.8.7. The issue also occurs with 1.8.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)