Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5266

Derby Database stored procedure is failing SYSCS_UTIL.SYSCS_BACKUP_DATABASE -urgent

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Cannot Reproduce
    • 10.5.3.0
    • None
    • Services
    • We are using Windows 2003 server, Windows XP and Windows 7
    • Normal
    • Repro attached
    • Data corruption, Seen in production

    Description

      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]

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            jayaprakashkumar Jayaprakash Kumar
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment