Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 2 May 2012 13:18:51 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1389107657.16987.1335964731735.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2052864642.6596.1307620618840.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (DERBY-5266) Derby Database stored procedure is
 failing SYSCS_UTIL.SYSCS_BACKUP_DATABASE -urgent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas closed DERBY-5266.
--------------------------------

    Resolution: Cannot Reproduce

I am closing this issue as not reproducible. This issue has been dormant for almost a year now. We can re-open it if more information becomes available.
                
> Derby Database stored procedure is failing SYSCS_UTIL.SYSCS_BACKUP_DATABASE -urgent
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-5266
>                 URL: https://issues.apache.org/jira/browse/DERBY-5266
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.5.3.0
>         Environment: We are using Windows 2003 server, Windows XP and Windows 7
>            Reporter: Jayaprakash Kumar
>            Priority: Blocker
>              Labels: Backup, Database, Derby, issue
>
> We are facing the problem with derby Backup Database procedure function SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?) and 
> this function failed to take the backup of the database and throws below error message.
> Below is the java code logic calling the procedure function.
> 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] 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira