You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Vijender Devakari <vi...@db.com> on 2011/06/03 10:28:41 UTC
SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing
Hi Team,
we are using below proc for backing up the database, but this call is hanging
when the Database is size more like 3GB, 4GB, ...
Can you let me know in which case we can use this and also what else we need
to use to backup database incase if the siz is more.
CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)
Best Regards,
Vijender D,
Deutsche Bank
Ph: +65 6423 8530
Mobile: +65 94517994
************************************************************
This mail is transmitted to you on behalf of [HCL].
Diese Post wird Ihnen im Namen der [HCL] ubermittelt
*************************************************************
---
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing
Posted by dvijender <vi...@db.com>.
yes, am sure it is hanging and also there is nothing in the destination
directory. Here the Database size is 20 GB and I have attached the log also,
pls check and let me know.
Mike Matrigali wrote:
>
> There should be no size limits to the backup database command other than
> those imposed by destination disk/filesystem.
>
> Are you sure it is "hanging", rather than going very slow? Basically is
> anything showing up on the destination disk.
>
> Is there anything in derby.log when you encounter the problem?
>
> Are you trying to backup the database while work is being done in
> the database? If so, derby does have to wait until current tranactions
> finish before it can get started.
>
> I would not be surprised if backup done by derby is slower than one
> would expect, it has not been optimized for very large databases. It
> is basic. The expectation is that if the solution is not fast enough
> then user can code their own backup and properly interact with derby
> by using method outlined in the documentation using freeze or unfreeze:
> http://db.apache.org/derby/docs/10.8/adminguide/cadminhubbkup98797.html
> http://db.apache.org/derby/docs/10.8/adminguide/cadminhubbkup75469.html
> Vijender Devakari wrote:
>> Hi Team,
>>
>> we are using below proc for backing up the database, but this call is
>> hanging when the Database is size more like 3GB, 4GB, ...
>>
>> Can you let me know in which case we can use this and also what else we
>> need to use to backup database incase if the siz is more.
>>
>> CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)
>>
>> Best Regards,
>>
>> Vijender D,
>> Deutsche Bank
>> Ph: +65 6423 8530
>> Mobile: +65 94517994
>>
>> ************************************************************
>> This mail is transmitted to you on behalf of [HCL].
>> Diese Post wird Ihnen im Namen der [HCL] ubermittelt
>> *************************************************************
>>
>> ---
>>
>> This e-mail may contain confidential and/or privileged information. If
>> you
>> are not the intended recipient (or have received this e-mail in error)
>> please notify the sender immediately and destroy this e-mail. Any
>> unauthorized copying, disclosure or distribution of the material in this
>> e-mail is strictly forbidden.
>>
>
>
>
http://old.nabble.com/file/p31806960/Logs.zip Logs.zip
--
View this message in context: http://old.nabble.com/SYSCS_UTIL.SYSCS_BACKUP_DATABASE-failing-tp31764436p31806960.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing
Posted by Mike Matrigali <mi...@sbcglobal.net>.
There should be no size limits to the backup database command other than
those imposed by destination disk/filesystem.
Are you sure it is "hanging", rather than going very slow? Basically is
anything showing up on the destination disk.
Is there anything in derby.log when you encounter the problem?
Are you trying to backup the database while work is being done in
the database? If so, derby does have to wait until current tranactions
finish before it can get started.
I would not be surprised if backup done by derby is slower than one
would expect, it has not been optimized for very large databases. It
is basic. The expectation is that if the solution is not fast enough
then user can code their own backup and properly interact with derby
by using method outlined in the documentation using freeze or unfreeze:
http://db.apache.org/derby/docs/10.8/adminguide/cadminhubbkup98797.html
http://db.apache.org/derby/docs/10.8/adminguide/cadminhubbkup75469.html
Vijender Devakari wrote:
> Hi Team,
>
> we are using below proc for backing up the database, but this call is
> hanging when the Database is size more like 3GB, 4GB, ...
>
> Can you let me know in which case we can use this and also what else we
> need to use to backup database incase if the siz is more.
>
> CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)
>
> Best Regards,
>
> Vijender D,
> Deutsche Bank
> Ph: +65 6423 8530
> Mobile: +65 94517994
>
> ************************************************************
> This mail is transmitted to you on behalf of [HCL].
> Diese Post wird Ihnen im Namen der [HCL] ubermittelt
> *************************************************************
>
> ---
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>