db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-7043) DROP SCHEMA results in ERROR XSAI2
Date Fri, 03 May 2019 00:36:00 GMT

    [ https://issues.apache.org/jira/browse/DERBY-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832128#comment-16832128

Bryan Pendleton commented on DERBY-7043:

Do you have any backups of the database? Perhaps you can set up a separate environment, and
restore a backup, and see if sys.syssequences is OK in that backup? And, if so, whether the
problem can be reproduced?

> ----------------------------------
>                 Key: DERBY-7043
>                 URL: https://issues.apache.org/jira/browse/DERBY-7043
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>         Environment: OS/400
>            Reporter: Rick Cook
>            Priority: Minor
> DROP SCHEMA schemaname RESTRICT results in:
>     *{color:#d04437}ERROR XSAI2: The conglomerate (1,024) requested does not exist.{color}*
> Prior to DROP SCHEMA, I did drop all tables in that schema.
> I realize that 1,024 conglomerate number translates into c400.dat file in Derby seq0
directory, and that c400.dat file is indeed missing, and I neither know why nor for how long.
> I ran consistency checks on database using SQL commands from [https://wiki.apache.org/db-derby/DatabaseConsistencyCheck] to
find the bad table(s):
>     *{color:#14892c}I isolated the 1,024 conglomerate error to the SYS.SYSSEQUENCES
> And I used the following SQL to identify the conglomerate name:  {color:#654982}*SYSSEQUENCES_HEAP*{color}
C, sys.sysschemas s  WHERE CONGLOMERATENUMBER = 1024 AND s.schemaid = C.schemaid
> In fact, I cannot even SQL SELECT on SYS.SYSSEQUENCES table without getting the same
conglomerate error as the DROP SCHEMA schemaname RESTRICT command.
> In other words, I cannot DROP SCHEMA schemaname RESTRICT until SYS.SYSSEQUENCES corruption
is resolved.
> I was wondering if anyone knew how to resolve this easily with either SQL command(s)
or any UNIX style java commands.
> P.S.  Keep in mind, that I am not an IJ expert, as I have been using a simple front-end
Derby tool created by our manufacturer to run SQL statements on Derby DB, without all the
complexity of using IJ and setting up IJ with environment variables, classpaths, etc.

This message was sent by Atlassian JIRA

View raw message