db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dvijender <vijender.devak...@db.com>
Subject Re: AW: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Date Mon, 13 Jun 2011 08:22:12 GMT


Folder is creating itself (proc is creating), but when I inspect the folder
it is empty, just hanging.


Florin.Herinean wrote:
> 
> Maybe the documentation is correct and the problem relies on the "
> d:/db/backup/test" path. Does that folder exist ? Does the user running
> the db have rights to access it ? Does this user have rights to write to
> it ? To create files and subfolders ?
> 
> Best Regards,
> 
> Florin
> 
> -----Urspr√ľngliche Nachricht-----
> Von: dev@xx [mailto:dev@proxiflex.fr] 
> Gesendet: Donnerstag, 9. Juni 2011 11:03
> An: Derby Discussion
> Betreff: Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
> 
> Hi,
> 
> Well documentation doesn't say that...
> 
> SYSCS_UTIL.SYSCS_BACKUP_DATABASE system procedure
> 
> The SYSCS_UTIL.SYSCS_BACKUP_DATABASE system procedure backs up the
> 
> database to a specified backup directory.
> 
> Syntax
> 
> SYSCS_UTIL.SYSCS_BACKUP_DATABASE(IN BACKUPDIR VARCHAR())
> 
> No result is returned from the procedure.
> 
> BACKUPDIR
> 
> An input argument of type VARCHAR(32672) that specifies the path to a 
> directory,
> 
> where the backup should be stored. Relative paths are resolved based on
> the 
> current
> 
> user directory, user.dir, of the JVM where the database backup is
> occurring.
> 
> Relative paths are not resolved based on the derby home directory. To
> avoid
> 
> confusion, use the absolute path.
> 
> JDBC example
> 
> The following example backs up the database to the c:/backupdir directory:
> 
> CallableStatement cs = conn.prepareCall
> 
> ("CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)");
> 
> cs.setString(1, "c:/backupdir");
> 
> cs.execute();
> 
> cs.close();
> 
> SQL example
> 
> The following example backs up the database to the c:/backupdir directory:
> 
> CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE('c:/backupdir');
> 
> 
> 
> 
> Is the documentation wrong ??
> 
> Regards,
> 
> Jean-Yves
> 
> 
> 
> ----- Original Message ----- 
> From: <Florin.Herinean@sungard.com>
> To: <derby-user@db.apache.org>
> Sent: Thursday, June 09, 2011 10:49 AM
> Subject: AW: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
> 
> 
>> Hi,
>>
>> Although I have *no knowledge* of internal derby implementation (I have
>> no 
>> sources), I do have some basic java knowledge, and from the messages in 
>> the dump I can tell you that the stored procedure you're invoking is 
>> expecting a URL.
>>
>> That means your "backupdirectory" parameter should be a valid URL and not 
>> a file path, i.e. it should be:
>>
>> file:/d:/db/backup/test
>>
>> By passing the file path with forward slashes, the device letter "d:" was 
>> taken to be the protocol part of the URL, and since there is no
>> registered 
>> handlers for a "d" protocol you got the error below:
>>
>> <parameter><dirLocator>d:/db/backup/test</dirLocator></parameter>,
DBBP]
>> Error in performing backup database :A network protocol error was
>> encountered and the connection has been terminated: the requested command
>> encountered an unarchitected and implementation-specific condition for 
>> which
>> there was no architected message
>>
>> Cheers,
>>
>> Florin
>>
>> -----Urspr√ľngliche Nachricht-----
>> Von: dvijender [mailto:vijender.devakari@db.com]
>> Gesendet: Donnerstag, 9. Juni 2011 09:45
>> An: derby-user@db.apache.org
>> Betreff: Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
>>
>>
>> Hi,
>>
>> This is the thread dump which was thrown by SQL Exception
>>
>> This the logic we are using to backup the database.
>>
>> Connection conn = dataSource.getConnection();
>>            backupdirectory = dirLocation + "/" + DateUtils.formatDate(new
>> Date(), DATE_FORMAT);
>>            CallableStatement stmt = conn.prepareCall("CALL
>> SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)");
>>            stmt.setString(1, backupdirectory);
>>            stmt.execute();
>>            stmt.close();
>>        } catch (SQLException exp) {
>>            log.error("Error in performing backup database :" +
>> exp.getMessage());
>>       }
>>
>> Pls see the Threaddump below.
>>
>> Job logger created for job 20110426115633543103
>> Job execution started. Job program:
>> [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501,
>> 1942, 2011-04-26, 11:54:00,
>> <parameter><dirLocator>d:/db/backup/test</dirLocator></parameter>,
DBBP]
>> Job Executer Signalling is not running...
>> Job Executer Signalling is not running...
>> Job Executer Signalling is not running...
>> Job Executer Signalling is not running...
>> Job Executer Signalling is not running...
>> Job Executer Signalling is not running...
>> Error in performing backup database :A network protocol error was
>> encountered and the connection has been terminated: the requested command
>> encountered an unarchitected and implementation-specific condition for 
>> which
>> there was no architected message
>> Error in performing backup database :A network protocol error was
>> encountered and the connection has been terminated: the requested command
>> encountered an unarchitected and implementation-specific condition for 
>> which
>> there was no architected message
>> com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing 
>> backup
>> database :A network protocol error was encountered and the connection has
>> been terminated: the requested command encountered an unarchitected and
>> implementation-specific condition for which there was no architected 
>> message
>> at
>> com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155)
>> at
>> com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88)
>> at
>> com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97)
>> at
>> com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73)
>> at
>> com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207)
>> at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168)
>> at java.lang.Thread.run(Thread.java:595)
>> Job execution COMPLETED with result [true]
>> Job logger created for job 20110426115633543103
>> Job execution started. Job program:
>> [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501,
>> 1942, 2011-04-26, 11:54:00,
>> <parameter><dirLocator>d:/db/backup/test</dirLocator></parameter>,
DBBP]
>> Error in performing backup database :A network protocol error was
>> encountered and the connection has been terminated: the requested command
>> encountered an unarchitected and implementation-specific condition for 
>> which
>> there was no architected message
>> Error in performing backup database :A network protocol error was
>> encountered and the connection has been terminated: the requested command
>> encountered an unarchitected and implementation-specific condition for 
>> which
>> there was no architected message
>> com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing 
>> backup
>> database :A network protocol error was encountered and the connection has
>> been terminated: the requested command encountered an unarchitected and
>> implementation-specific condition for which there was no architected 
>> message
>> at
>> com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155)
>> at
>> com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88)
>> at
>> com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97)
>> at
>> com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73)
>> at
>> com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207)
>> at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168)
>> at java.lang.Thread.run(Thread.java:595)
>> Job execution COMPLETED with result [true]
>> Job logger created for job 20110426115633543103
>> Job execution started. Job program:
>> [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501,
>> 1942, 2011-04-26, 11:54:00,
>> <parameter><dirLocator>d:/db/backup/test</dirLocator></parameter>,
DBBP]
>> Error in performing backup database :A network protocol error was
>> encountered and the connection has been terminated: the requested command
>> encountered an unarchitected and implementation-specific condition for 
>> which
>> there was no architected message
>> Error in performing backup database :A network protocol error was
>> encountered and the connection has been terminated: the requested command
>> encountered an unarchitected and implementation-specific condition for 
>> which
>> there was no architected message
>> com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing 
>> backup
>> database :A network protocol error was encountered and the connection has
>> been terminated: the requested command encountered an unarchitected and
>> implementation-specific condition for which there was no architected 
>> message
>> at
>> com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155)
>> at
>> com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88)
>> at
>> com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97)
>> at
>> com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73)
>> at
>> com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207)
>> at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168)
>> at java.lang.Thread.run(Thread.java:595)
>> Job execution COMPLETED with result [true]
>> Job logger created for job 20110426115633543103
>> Job execution started. Job program:
>> [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501,
>> 1942, 2011-04-26, 11:54:00,
>> <parameter><dirLocator>d:/db/backup/test</dirLocator></parameter>,
DBBP]
>>
>>
>>
>>
>> Brett Wooldridge-2 wrote:
>>>
>>> Sorry I wasn't clearer.  A thead dump is a snapshot of all running
>>> threads in the system, not a stacktrace of failures.
>>>
>>> You can generate a threaddump on Windows by running your server from
>>> the command line, and when the hang occurs during backup, pressing
>>> CTRL-Break (CTRL key and Break key at the same time).  This will
>>> produce a threaddump in your console (cmd.exe) window.  Copy/paste the
>>> threaddump somewhere we can take a look at it.
>>>
>>> If you are on Linux, you can produce a threaddump by sending the
>>> process a QUIT signal:
>>>
>>> kill -QUIT process_id
>>>
>>> Regards,
>>> Brett
>>>
>>>
>>> On Thu, Jun 9, 2011 at 4:01 PM, dvijender <vijender.devakari@db.com>
>>> wrote:
>>>>
>>>> Hi Mike, Brett,
>>>>
>>>> Attached thread dump. Here the database size is 20 GB.
>>>>
>>>>
>>>> Brett Wooldridge-2 wrote:
>>>>>
>>>>> Do you have a thread dump during the hang? What
>>>>> OS are you running on?
>>>>>
>>>>> Brett
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On Jun 7, 2011, at 16:38, Vijender Devakari <vijender.devakari@db.com>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Can you respond to this as this is very urgent.
>>>>>
>>>>> 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
>>>>> *************************************************************
>>>>>
>>>>> <graycol.gif>Vijender Devakari/ext/dbcom
>>>>>
>>>>>
>>>>>
>>>>> *Vijender Devakari/ext/dbcom*
>>>>>
>>>>> 06/03/2011 04:28 PM
>>>>>
>>>>> <ecblank.gif>
>>>>> To
>>>>> <ecblank.gif>
>>>>> derby-user@db.apache.org <ecblank.gif>
>>>>> cc
>>>>> <ecblank.gif>
>>>>> <ecblank.gif>
>>>>> Subject
>>>>> <ecblank.gif>
>>>>> SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing <ecblank.gif><ecblank.gif>
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/p31806974/Logs.zip Logs.zip
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Re%3A-SYSCS_UTIL.SYSCS_BACKUP_DATABASE-failing-urgent-tp31789732p31806974.html
>>>> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>
>> -- 
>> View this message in context: 
>> http://old.nabble.com/Re%3A-SYSCS_UTIL.SYSCS_BACKUP_DATABASE-failing-urgent-tp31789732p31807191.html
>> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>>
>>
>> 
> 
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/Re%3A-SYSCS_UTIL.SYSCS_BACKUP_DATABASE-failing-urgent-tp31789732p31832984.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.


Mime
View raw message