You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <ji...@apache.org> on 2012/09/14 17:59:08 UTC

[jira] [Updated] (DERBY-5859) ERROR XSAI2: The conglomerate (1,232) requested does not exist.

     [ https://issues.apache.org/jira/browse/DERBY-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali updated DERBY-5859:
----------------------------------

    Labels: derby_triage10_10  (was: )

triaged for 10.10

Without more information as requested not much else can be done.   If there is no more input on this
issue suggest it get closed as can't repro.
                
> ERROR XSAI2: The conglomerate (1,232) requested does not exist.
> ---------------------------------------------------------------
>
>                 Key: DERBY-5859
>                 URL: https://issues.apache.org/jira/browse/DERBY-5859
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Services, Store
>    Affects Versions: 10.9.1.0
>         Environment: Mac OSX 10.7.4, Java 1.7.0_05-b05 JDK
>            Reporter: Lawrence Winkler
>              Labels: derby_triage10_10
>
> First discovered attempting to drop, and create table in NetBean 7.2 rc1. Attempted to drop table using ij. Same error. Other tables and views remain functional with data.
> Running in embedded mode in both NetBeans and IJ applications. 
> From sysconglomerates table for the affect table:
> 48d7402a-0138-4ef7-749d-ffff84f6b395|48d7402a-0138-4ef7-749d-ffff84f6b395                                                                                            |1232                |20e1c02b-0138-4ef7-749d-ffff84f6b395
> 48d7402a-0138-4ef7-749d-ffff84f6b395|SQL120703184604760                                                                                                              |1249                |38c30028-0138-4ef7-749d-ffff84f6b395

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira