[
https://issues.apache.org/jira/browse/DERBY-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047464#comment-13047464
]
Mike Matrigali commented on DERBY-5266:
---------------------------------------
without seeing the database there is not much I can help with, other than the
previous posts. The more you can tell us about
the db, the more likely someone will be able to help. If you can't post the
db, can you post a full directory listing of the log and
seg0 directories including modify times and sizes of the files. ls -l does
this if you have unix compatible tools.
I still think you have a problem in the database and backup just happens to be
finding it. Unfortunately the conisistency checker
is not complete. It is strange that you got the error on a different container
this time. Did you change the database since posting
the original error? This time the error is on container 562448, page 5478.
The hex dump shows that it is completely 0's, which
is not a valid page for Derby. It would be interesting to tell if this page is
at end of the file or not. The other issue I mentioned
above describes a method for getting that information.
If you run the backup twice in a row do you get the same container/page number
with the error? Is there any disk problem
going on? Is there anything unusual about the disk you are copying from?
If it really is a problem in the db, and not a backup problem or an I/O problem
on your machine - then one possible workaround
would be to run offline compress on every table in your database. This may
fail though, so I would execute this on a copy
of the db, keeping your original. If the problem is a free page, rather than a
used page then offline compress will likely
work. If the problem is on some real page in a base table that the consistency
checker does not look at, like a clob overflow
chain then you will likely get a similar error. But determining this would
also prove/disprove that backup is the issue or not.
Running offline compress also will rebuild all your indexes so if there was a
problem there, it will fix it. Unfortunately container
562448 is a base table and not an index.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
