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/07 09:38:18 UTC
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
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
*************************************************************
Vijender
Devakari/ext/dbcom
To
06/03/2011 04:28 derby-user@db.apache.org
PM cc
Subject
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: AW: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by dvijender <vi...@db.com>.
Hi,
Pls find the thread dump below.
[MBC] 09 Jun 2011 18:13:16,922:[SCHED:BATCH:OTHERS:TP:THREAD-1] [FATAL]
com.topgear.executer.impl.St
dJobExecutionShell - Unable to process. Reverting to old state.
201008281400651757103
Full thread dump Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode):
"TP-Monitor" daemon prio=6 tid=0x47a72e28 nid=0x1aa8 in Object.wait()
[0x48dbf000..0x48dbfce8]
at java.lang.Object.wait(Native Method)
- waiting on <0x154c5028> (a
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
at
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:561)
- locked <0x154c5028> (a
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor4" daemon prio=6 tid=0x475bf708 nid=0x1f14 runnable
[0x48bff000..0x48bffa68]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x154c5058> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:306)
at
org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:660)
at
org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:870)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor3" daemon prio=6 tid=0x4749cbd8 nid=0x1714 in Object.wait()
[0x489ff000..0x489ffd68]
at java.lang.Object.wait(Native Method)
- waiting on <0x154c51f0> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:658)
- locked <0x154c51f0> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor2" daemon prio=6 tid=0x47359ef8 nid=0x1060 in Object.wait()
[0x486ff000..0x486ffae8]
at java.lang.Object.wait(Native Method)
- waiting on <0x154c5210> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:658)
- locked <0x154c5210> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor1" daemon prio=6 tid=0x47a28418 nid=0x1284 in Object.wait()
[0x4863f000..0x4863f9e8]
at java.lang.Object.wait(Native Method)
- waiting on <0x154c5230> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:658)
- locked <0x154c5230> (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)
"http-443-Acceptor-0" daemon prio=6 tid=0x476baeb0 nid=0x1240 runnable
[0x485bf000..0x485bfb68]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x07c7c790> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at
com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:259)
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket(JSSESocketFactory.java:147
)
at
org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:310)
at java.lang.Thread.run(Thread.java:595)
"http-8080-Acceptor-0" daemon prio=6 tid=0x47dd0c88 nid=0x167c runnable
[0x4853f000..0x4853fbe8]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x07ca7f98> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFac
tory.java:61)
at
org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:310)
at java.lang.Thread.run(Thread.java:595)
"ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon prio=6
tid=0x475eba28 nid=0x830 wait
ing on condition [0x4847f000..0x4847fc68]
at java.lang.Thread.sleep(Native Method)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.jav
a:1579)
at java.lang.Thread.run(Thread.java:595)
"DRDAConnThread_21" daemon prio=6 tid=0x47a54730 nid=0xe08 runnable
[0x4927f000..0x4927fce8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_20" daemon prio=6 tid=0x47dd8838 nid=0x155c runnable
[0x4923f000..0x4923fd68]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_19" daemon prio=6 tid=0x47f6d320 nid=0x15ac runnable
[0x491ff000..0x491ff9e8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_18" daemon prio=6 tid=0x47f06b88 nid=0x1858 runnable
[0x491bf000..0x491bfa68]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_17" daemon prio=6 tid=0x47dc7cf8 nid=0x16c8 runnable
[0x4917e000..0x4917fae8]
at java.io.RandomAccessFile.writeBytes(Native Method)
at java.io.RandomAccessFile.write(RandomAccessFile.java:456)
at
org.apache.derby.impl.store.raw.data.RAFContainer.privBackupContainer(Unknown
Source)
at org.apache.derby.impl.store.raw.data.RAFContainer.run(Unknown
Source)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.derby.impl.store.raw.data.RAFContainer.backupContainer(Unknown
Source)
at
org.apache.derby.impl.store.raw.data.BaseContainerHandle.backupContainer(Unknown
Source)
at
org.apache.derby.impl.store.raw.data.BaseDataFileFactory.backupDataFiles(Unknown
Source)
at org.apache.derby.impl.store.raw.RawStore.backup(Unknown Source)
- locked <0x0bd91fa8> (a org.apache.derby.impl.store.raw.RawStore)
at org.apache.derby.impl.store.raw.RawStore.backup(Unknown Source)
at
org.apache.derby.impl.store.access.RAMAccessManager.backup(Unknown Source)
at org.apache.derby.impl.db.BasicDatabase.backup(Unknown Source)
at
org.apache.derby.catalog.SystemProcedures.SYSCS_BACKUP_DATABASE(Unknown
Source)
at
org.apache.derby.exe.ace0b94027x0130x752dx1145x00001d654aa84.g0(Unknown
Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.derby.impl.services.reflect.ReflectMethod.invoke(Unknown Source)
at
org.apache.derby.impl.sql.execute.CallStatementResultSet.open(Unknown
Source)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
- locked <0x12c7e7b0> (a
org.apache.derby.impl.jdbc.EmbedConnection30)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown
Source)
at
org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown
Source)
- locked <0x12c7e7b0> (a
org.apache.derby.impl.jdbc.EmbedConnection30)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown
Source)
at org.apache.derby.impl.drda.DRDAStatement.execute(Unknown Source)
at
org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTTobjects(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTT(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_16" daemon prio=6 tid=0x00cccdf0 nid=0x1864 runnable
[0x4913f000..0x4913fb68]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_15" daemon prio=6 tid=0x47d77c48 nid=0x5cc runnable
[0x490ff000..0x490ffbe8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_14" daemon prio=6 tid=0x47a20480 nid=0x1080 runnable
[0x490bf000..0x490bfc68]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_13" daemon prio=6 tid=0x47d8e4a8 nid=0x19c0 runnable
[0x4907f000..0x4907fce8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_12" daemon prio=6 tid=0x00ccd618 nid=0x1c1c runnable
[0x4903f000..0x4903fd68]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_11" daemon prio=6 tid=0x47d55968 nid=0x1cd4 runnable
[0x48fff000..0x48fff9e8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_10" daemon prio=6 tid=0x47b44558 nid=0x104 runnable
[0x48fbf000..0x48fbfa68]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_9" daemon prio=6 tid=0x4779fb98 nid=0x191c runnable
[0x48f7f000..0x48f7fae8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"DRDAConnThread_8" daemon prio=6 tid=0x4758f960 nid=0x1064 runnable
[0x48f3f000..0x48f3fb68]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"Timer-2" prio=6 tid=0x4736f570 nid=0x1330 in Object.wait()
[0x48eff000..0x48effbe8]
at java.lang.Object.wait(Native Method)
- waiting on <0x12c73c50> (a java.util.TaskQueue)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked <0x12c73c50> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"SCHED:BATCH:DBOPERATIONS:TP:THREAD-0" prio=6 tid=0x474a2498 nid=0x1db0
runnable [0x48ebf000..0x48eb
fce8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.client.net.Reply.fill(Unknown Source)
at
org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown Source)
at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source)
at org.apache.derby.client.net.Reply.startSameIdChainParse(Unknown
Source)
at
org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown
Source)
at
org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown
Source)
at org.apache.derby.client.am.Statement.readExecuteCall(Unknown
Source)
at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown
Source)
at org.apache.derby.client.am.PreparedStatement.executeX(Unknown
Source)
at org.apache.derby.client.am.PreparedStatement.execute(Unknown
Source)
- locked <0x12a65ff0> (a org.apache.derby.client.net.NetConnection)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.j
ava:168)
at
com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:151)
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)
a
"SCHED:BATCH:DBOPERATIONS:MONITOR" prio=6 tid=0x47640a18 nid=0x1620 waiting
on condition [0x48e7f000
..0x48e7fc68]
at java.lang.Thread.sleep(Native Method)
at
com.topgear.executer.impl.StdHeartBeatMonitor.run(StdHeartBeatMonitor.java:129)
at java.lang.Thread.run(Thread.java:595)
"SCHED:BATCH:DBOPERATIONS:MAIN" prio=6 tid=0x474c5500 nid=0xed0 in
Object.wait() [0x48e3f000..0x48e3
fd68]
at java.lang.Object.wait(Native Method)
- waiting on <0x120b2ce8> (a [I)
at
com.topgear.executer.impl.StdJobExecuterSignal.signalWait(StdJobExecuterSignal.java:104)
- locked <0x120b2ce8> (a [I)
at
com.topgear.executer.impl.StdJobExecuterThread.runProtected(StdJobExecuterThread.java:199
)
at
com.topgear.executer.impl.StdJobExecuterThread.run(StdJobExecuterThread.java:128)
at java.lang.Thread.run(Thread.java:595)
"DRDAConnThread_6" daemon prio=6 tid=0x47b23938 nid=0x1f50 runnable
[0x48bbf000..0x48bbfae8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"SCHED:BATCH:ORHANDLE" prio=6 tid=0x47af1d90 nid=0xa4 waiting on condition
[0x483ff000..0x483ff9e8]
at java.lang.Thread.sleep(Native Method)
at
com.topgear.executer.impl.OrphanJobHandler.run(OrphanJobHandler.java:154)
at java.lang.Thread.run(Thread.java:595)
"Store
com.db.mbc.base.service.security.ssoauthentication.SAML_RESPONSE_CACHE Spool
Thread" daemon p
rio=2 tid=0x47a2c458 nid=0xc54 waiting on condition [0x483bf000..0x483bfa68]
at java.lang.Thread.sleep(Native Method)
at
net.sf.ehcache.store.DiskStore.spoolAndExpiryThreadMain(DiskStore.java:573)
at net.sf.ehcache.store.DiskStore.access$800(DiskStore.java:65)
at
net.sf.ehcache.store.DiskStore$SpoolAndExpiryThread.run(DiskStore.java:1057)
"derby.rawStoreDaemon" daemon prio=6 tid=0x47af4e78 nid=0x1c44 in
Object.wait() [0x4837f000..0x4837f
ae8]
at java.lang.Object.wait(Native Method)
- waiting on <0x0bc03f28> (a
org.apache.derby.impl.services.daemon.BasicDaemon)
at org.apache.derby.impl.services.daemon.BasicDaemon.rest(Unknown
Source)
- locked <0x0bc03f28> (a
org.apache.derby.impl.services.daemon.BasicDaemon)
at org.apache.derby.impl.services.daemon.BasicDaemon.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)
"DRDAConnThread_5" daemon prio=6 tid=0x47d010d8 nid=0x1d50 runnable
[0x4833f000..0x4833fbe8]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.derby.impl.drda.DDMReader.fill(Unknown Source)
at
org.apache.derby.impl.drda.DDMReader.ensureALayerDataInBuffer(Unknown
Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown
Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
"Timer-1" daemon prio=6 tid=0x47abba88 nid=0x1fd4 in Object.wait()
[0x482ff000..0x482ffc68]
at java.lang.Object.wait(Native Method)
- waiting on <0x0b84dfe0> (a java.util.TaskQueue)
at java.lang.Object.wait(Object.java:474)
at java.util.TimerThread.mainLoop(Timer.java:483)
- locked <0x0b84dfe0> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"NetworkServerThread_3" daemon prio=6 tid=0x47648b40 nid=0x1e78 runnable
[0x482bf000..0x482bfce8]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x08a7bfc8> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at org.apache.derby.impl.drda.ClientThread$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.derby.impl.drda.ClientThread.run(Unknown Source)
"derby.NetworkServerStarter" daemon prio=6 tid=0x47733d50 nid=0x1c90 in
Object.wait() [0x4827f000..0
x4827fd68]
at java.lang.Object.wait(Native Method)
- waiting on <0x08a7c218> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart(Unknown
Source)
- locked <0x08a7c218> (a java.lang.Object)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.derby.iapi.jdbc.DRDAServerStarter.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
"Timer-0" daemon prio=6 tid=0x47d22cb0 nid=0x484 in Object.wait()
[0x4823f000..0x4823f9e8]
at java.lang.Object.wait(Native Method)
- waiting on <0x08a7c328> (a java.util.TaskQueue)
at java.lang.Object.wait(Object.java:474)
at java.util.TimerThread.mainLoop(Timer.java:483)
- locked <0x08a7c328> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"derby.antiGC" daemon prio=2 tid=0x4766d990 nid=0x228 in Object.wait()
[0x481ff000..0x481ffa68]
at java.lang.Object.wait(Native Method)
- waiting on <0x08a7c338> (a
org.apache.derby.impl.services.monitor.AntiGC)
at java.lang.Object.wait(Object.java:474)
at org.apache.derby.impl.services.monitor.AntiGC.run(Unknown Source)
- locked <0x08a7c338> (a
org.apache.derby.impl.services.monitor.AntiGC)
at java.lang.Thread.run(Thread.java:595)
"Store com.db.mbc.cache.service.METHOD_CACHE Spool Thread" daemon prio=2
tid=0x478a0f30 nid=0x89c wa
iting on condition [0x481bf000..0x481bfae8]
at java.lang.Thread.sleep(Native Method)
at
net.sf.ehcache.store.DiskStore.spoolAndExpiryThreadMain(DiskStore.java:573)
at net.sf.ehcache.store.DiskStore.access$800(DiskStore.java:65)
at
net.sf.ehcache.store.DiskStore$SpoolAndExpiryThread.run(DiskStore.java:1057)
"Low Memory Detector" daemon prio=6 tid=0x00cbfd78 nid=0x12c runnable
[0x00000000..0x00000000]
"CompilerThread0" daemon prio=10 tid=0x00cbe4e8 nid=0x16bc waiting on
condition [0x00000000..0x472bf
948]
"Signal Dispatcher" daemon prio=10 tid=0x00cbd6e0 nid=0x1878 waiting on
condition [0x00000000..0x000
00000]
"JDWP Event Helper Thread" daemon prio=6 tid=0x00cbc468 nid=0xf38 runnable
[0x00000000..0x00000000]
"JDWP Transport Listener: dt_socket" daemon prio=6 tid=0x003d90f8 nid=0x9c8
runnable [0x00000000..0x
00000000]
"Finalizer" daemon prio=8 tid=0x00cabd40 nid=0x1588 in Object.wait()
[0x4713f000..0x4713fa68]
at java.lang.Object.wait(Native Method)
- waiting on <0x07bb0370> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x07bb0370> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x00caa8d0 nid=0x1658 in
Object.wait() [0x00bef000..0x00befae
8]
at java.lang.Object.wait(Native Method)
- waiting on <0x07bb0390> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x07bb0390> (a java.lang.ref.Reference$Lock)
"main" prio=6 tid=0x003d8898 nid=0xb60 runnable [0x0007f000..0x0007fc3c]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x05090e10> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at
org.apache.catalina.core.StandardServer.await(StandardServer.java:389)
at org.apache.catalina.startup.Catalina.await(Catalina.java:630)
at org.apache.catalina.startup.Catalina.start(Catalina.java:590)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
"VM Thread" prio=10 tid=0x003d6108 nid=0x143c runnable
"VM Periodic Task Thread" prio=10 tid=0x00cdaa98 nid=0x820 waiting on
condition
dvijender wrote:
>
>
> 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: <Fl...@sungard.com>
>> To: <de...@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 <vi...@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
>>>>>> <vi...@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-tp31789732p31840664.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: AW: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by dvijender <vi...@db.com>.
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: <Fl...@sungard.com>
> To: <de...@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 <vi...@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 <vi...@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.
AW: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by Fl...@sungard.com.
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: <Fl...@sungard.com>
To: <de...@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 <vi...@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 <vi...@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.
>
>
>
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by "dev@xx" <de...@proxiflex.fr>.
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: <Fl...@sungard.com>
To: <de...@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 <vi...@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 <vi...@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.
>
>
>
AW: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by Fl...@sungard.com.
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 <vi...@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 <vi...@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.
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by dvijender <vi...@db.com>.
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 <vi...@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 <vi...@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.
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by Kristian Waagan <kr...@oracle.com>.
On 09.06.11 09:27, Brett Wooldridge 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
You may also be able to use jstack.
On another matter, are there any relevant error messages in derby.log -
the Derby log on the server side?
Regards,
--
Kristian
>
> Regards,
> Brett
>
>
> On Thu, Jun 9, 2011 at 4:01 PM, dvijender<vi...@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<vi...@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.
>>
>>
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by Brett Wooldridge <br...@gmail.com>.
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 <vi...@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 <vi...@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.
>
>
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by dvijender <vi...@db.com>.
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 <vi...@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.
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by Brett Wooldridge <br...@gmail.com>.
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 <vi...@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.
Re: SYSCS_UTIL.SYSCS_BACKUP_DATABASE failing-urgent
Posted by Bryan Pendleton <bp...@gmail.com>.
On 06/07/2011 12:38 AM, Vijender Devakari wrote:
> Hi,
>
> Can you respond to this as this is very urgent.
Mike replied:
http://mail-archives.apache.org/mod_mbox/db-derby-user/201106.mbox/%3C4DE90F37.2040307@sbcglobal.net%3E