Hi,
General error: "java.lang.RuntimeException: page[1238] data leaf table:21
>> ISSUE entries:3 parent:488 keys:[27863, 27864, 27866] offsets:[1861, 1674,
>> 1479] parent 488 expected 693"; SQL statement:
>> SELECT * FROM ISSUE [50000-172] HY000/50000
>>
>
This looks like a database corruption. The error code 50000-172 means you
are using H2 version 1.3.172, which is quite recent, so I can't explain the
corruption. If you want to find out, below is a list of questions you would
need to answer.
The strange thing is that when I look at the database there are a number of
>> new tables created:
>>
>> ISSUE_COPY_10_2
>> ISSUE_COPY_12_4
>> ISSUE_COPY_15_3
>>
>
I believe those are intermediate / temporary tables that are created when
you alter a table (for example, add a column). Of course you should not
have that many such tables (you should not have any such table in fact).
Did you use "alter table"? If yes, how? (Maybe the problem is reproducible.)
List of questions for corrupt databases:
- What is your database URL?
- Did you use LOG=0 or LOG=1? Did you read the FAQ about it?
- Did the system ever run out of disk space?
- Could you send the full stack trace of the exception including message
text?
- Did you use SHUTDOWN DEFRAG or the database setting DEFRAG_ALWAYS with H2
version 1.3.159 or older?
- How many connections does your application use concurrently?
- Do you use temporary tables?
- With which version of H2 was this database created?
You can find it out using:
select * from information_schema.settings where name='CREATE_BUILD'
or have a look in the SQL script created by the recover tool.
- Did the application run out of memory (once, or multiple times)?
- Do you use any settings or special features (for example cache settings,
two phase commit, linked tables)?
- Do you use any H2-specific system properties?
- Is the application multi-threaded?
- What operating system, file system, and virtual machine
(java -version) do you use?
- How did you start the Java process (java -Xmx... and so on)?
- Is it (or was it at some point) a networked file system?
- How big is the database (file sizes)?
- How much heap memory does the Java process have?
- Is the database usually closed normally, or is process terminated
forcefully or the computer switched off?
- Is it possible to reproduce this problem using a fresh database
(sometimes, or always)?
- Are there any other exceptions (maybe in the .trace.db file)?
Could you send them please?
- Do you still have any .trace.db files, and if yes could you send them?
- Could you send the .h2.db file where this exception occurs?
Regards,
Thomas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
