You are viewing limited content. For full access, please sign in.

Question

Question

Error Message: Could not create new version or undo automatic check out

asked on February 6, 2017 Show version history

Hola, estamos en proceso de migración del Laserfiche a la versión 10 y tenemos un problema con el versionado de contenidos, el error que da es:
Error Code: 9008
Error Message: Could not create new version or undo automatic check out.
General database error. [9008]

Hemos revisado información en el Support de Laserfiche pero refiere a bases de datos anteriores a la nuestra, la versión actual de nuestra base de datos es Oracle 11.1.0.7, Laserfiche 10.1.0.151 y del servidor Windows Server 2012 R2 Standard.

En el log de eventos del servidor Windows emite el siguiente evento:
Database statement execution error encountered.  Session ID: 65380; Dialog ID: 956198; Repository: 'DESARROLLO'; CLI routine: SysEntryCheckIn; Message: ORA-00600: internal error code, arguments: [kkqjpdGetContext:1], [], [], [], [], [], [], [], [], [], [], []
; SQL Statement: 'insert into vhist_propval (tocid, version, prop_id, pos, pos2, prop_pos, prop_group_id, str_val, num_val, date_val, bin_val, status) select pv.tocid, :ver1<int>, pv.prop_id, pv.pos, pv.pos2, (select prop_pos from pset_props psp join toc on psp.pset_id = toc.pset_id where tocid = pv.tocid and prop_id = pv.prop_id), nvl((select group_id from pset_props psp join toc on psp.pset_id = toc.pset_id where tocid = pv.tocid and prop_id = pv.prop_id),0), pv.str_val, pv.num_val, pv.date_val, pv.bin_val, 2 from propval pv where pv.tocid = :id<int> and (exists (select vpv.prop_id, vpv.pos from (select * from vhist_propval vpvi where vpvi.tocid = :id2<int> and (status=1 or status=2) and version = (select max(version) from vhist_propval where prop_id = vpvi.prop_id and tocid = vpvi.tocid and (status=1 or status=2))) vpv full join (select * from propval where propval.tocid = :id3<int>) pv2 on vpv.prop_id = pv2.prop_id and vpv.pos = pv2.pos and vpv.tocid = pv2.tocid where (vpv.prop_id = pv.prop_id or pv2.prop_id = pv.prop_id) and ((vpv.pos2 <> pv2.pos2) or (vpv.num_val is not null and pv2.num_val is not null and vpv.num_val <> pv2.num_val) or (vpv.num_val is null and pv2.num_val is not null) or (vpv.num_val is not null and pv2.num_val is null) or (vpv.date_val is not null and pv2.date_val is not null and vpv.date_val <> pv2.date_val) or (vpv.date_val is null and pv2.date_val is not null) or (vpv.date_val is not null and pv2.date_val is null) or (vpv.str_val is not null and pv2.str_val is not null and vpv.str_val <> pv2.str_val) or (vpv.str_val is null and pv2.str_val is not null) or (vpv.str_val is not null and pv2.str_val is null) or (vpv.bin_val is not null and pv2.bin_val is not null and dbms_lob.getlength(vpv.bin_val) <> dbms_lob.getlength(pv2.bin_val)) or (vpv.bin_val is null and pv2.bin_val is not null) or (vpv.bin_val is not null and pv2.bin_val is null))))'; SQL variable: ''; SQL State: .

Gracias anticipadamente por el apoyo.

 

Nueva información: encontré este enlace pero tampoco me da información que solucione el problema.

https://community.oracle.com/thread/3986453

0 0

Answer

SELECTED ANSWER
replied on February 7, 2017

Solución:

Se aplicó el workaround según lo indicado en el  Doc ID 14347248.8  encontrado en la web de Soporte Oracle.

Copio el documento mencionado

 

Bug 14347248 - ORA-600 [kkqjpdGetContext:1] parsing SQL with subquery (Doc ID 14347248.8)

Bug 14347248  ORA-600 [kkqjpdGetContext:1] parsing SQL with subquery

 This note gives a brief overview of bug 14347248. 
 The content was last updated on: 21-SEP-2015
 Click here for details of each of the sections below.

Affects:

Product (Component)

Oracle Server (Rdbms)

Range of versions believed to be affected

(Not specified)

Versions confirmed as being affected

Platforms affected

Generic (all / most platforms affected)

Fixed:

The fix for 14347248 is first included in


Interim patches may be available for earlier versions - click here to check.

Symptoms:

Related To:

  • Optimizer
  • _optimizer_unnest_disjunctive_subq

Description

ORA-600 ican occur optimizing a SQL that as a  subuery containing disjunctive 
correlated predicates.
Workaround
 alter session set "_optimizer_unnest_disjunctive_subq"= FALSE;

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.

 

References

Bug:14347248 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

4 0

Replies

replied on February 7, 2017

Otra manera de solucionar el problema sin modificar el parámetro que se aplica a todo la BD, es que en la sentencia se emplee un hint según se ve en la sentencia más abajo.

Pero esta es una tarea que deberá aplicarse en el código de Laserfiche.


Bug 14347248 ORA-600 [kkqjpdGetContext:1] parsing SQL with subquery is supposed to be fixed 
in version 11.2.0.4 which you are using. 

Setting _optimizer_unnest_disjunctive_subq to false forthe entire database could possibly change other execution plans 

You can however use it as a hint so only the problem query is affected 

insert /*+ OPT_PARAM('_optimizer_unnest_disjunctive_subq' 'FALSE') */ into vhist_propval (tocid, version, prop_id, pos, pos2, prop_pos, prop_group_id, str_val, num_val, date_val, bin_val, status) select pv.tocid, :ver11, pv.prop_id, pv.pos, pv.pos2, (select prop_pos from pset_props 

4 0
You are not allowed to follow up in this post.

Sign in to reply to this post.