I have a customer (unfortunately with confidential data) who has a Derby
database with corruption. I'm not sure of the details - somehow an
eSata disk was powered off, and perhaps it had write-caching enabled,
I'm not sure.
I've read on some Derby docs online that:
"In some cases one may rec
Hi there,
I just started on Derby. The date funtion does not seem to be functioning
correctly. For example,
ij> select col1, date('09/30/2009') from table1;
COL1 |2
--
9 |2009-09-30
as compared to
ij> select col1, date('09/31/2009') from table1;
ERROR 22008:
AliasTech wrote (2009-06-10 05:12:25):
>
> Hi there,
>
> I just started on Derby. The date funtion does not seem to be functioning
> correctly. For example,
>
> ij> select col1, date('09/30/2009') from table1;
> COL1 |2
> --
> 9 |2009-09-30
>
> as
Bernt M. Johnsen wrote:
>
> AliasTech wrote (2009-06-10 05:12:25):
>>
>> Hi there,
>>
>> I just started on Derby. The date funtion does not seem to be functioning
>> correctly. For example,
>>
>> ij> select col1, date('09/30/2009') from table1;
>> COL1 |2
>> ---
Unfortunately the problem you have is during redo recovery, so not only
is the page bad that you see in the log you don't have access to the
database to find out what else is bad. Also since redo recovery is
failing there is more work after that record that is not being done to
get your databas
Mike Matrigali wrote:
Then you could figure out how important container 1105
is. The best case is if 1105 is an index then one need only drop the
index and recreate it. From the conglomerate id I think it is an
index:
Once you get your database in a bootable state you can identify the
contain
hi,
I have attached a little test program that shows what I'm trying to do,
namely to rename programmatically a DB.
as far as I can see there is no derby command to accomplish that. however, I
found out that just renaming the folder of the DB files will do the trick.
of course the db shoul
Kathey Marsden wrote:
Mike Matrigali wrote:
Then you could figure out how important container 1105
is. The best case is if 1105 is an index then one need only drop the
index and recreate it. From the conglomerate id I think it is an
index:
Once you get your database in a bootable state you ca
