Upgrade SnapCreator 4.1.0 from 4.1.0c fails

SVOLLRAT1 — Thu, 05 Jun 2025 05:44:26 GMT

Hi Everybody

I just upgraded a Test-Server from 4.1.0c to 4.1.0.

Worked well so far until I tried to start a new Backup Job.

Each Job I try fails immediately with Update-Errors in the Database.

Does anybody have any clues on how to fix that? Ideas on what might have gone wrong while upgrading?

Below the ServerLog copied from the Console (Server started interactive)

Starting Derby Server

Starting Jetty Server on port: 8443

2014-01-29 15:09:01.556:INFO:oejs.Server:jetty-8.1.12.v20130726

2014-01-29 15:09:01.586:INFO:oejdp.ScanningAppProvider:Deployment monitor /usr/local/scServer4.1.0/engine/wars at interval 1

2014-01-29 15:09:01.591:INFO:oejd.DeploymentManager:Deployable added: /usr/local/scServer4.1.0/engine/wars/ui.war

2014-01-29 15:09:04.311:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for /ui, did not find org.apache.jasper.servlet.JspServlet

2014-01-29 15:09:04.362:INFO:oejd.DeploymentManager:Deployable added: /usr/local/scServer4.1.0/engine/wars/services.war

2014-01-29 15:09:06.406:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for /services, did not find org.apache.jasper.servlet.JspServlet

2014-01-29 15:09:06.430:INFO:services:Initializing Spring root WebApplicationContext

15:09:17,421 ERROR SchemaUpdate:235 - HHH000388: Unsuccessful: create sequence hibernate_sequence start with 1 increment by 1

15:09:17,423 ERROR SchemaUpdate:236 - Sequence 'HIBERNATE_SEQUENCE' already exists.

Property file changed, updating property object.

2014-01-29 15:09:29.786:INFO:oejus.SslContextFactory:Enabled Protocols [SSLv2Hello, SSLv3, TLSv1] of [SSLv2Hello, SSLv3, TLSv1]

2014-01-29 15:09:29.797:INFO:oejs.AbstractConnector:Started SslSocketConnector@0.0.0.0:8443

Jetty Server started on port: 8443

Jan 29, 2014 3:09:53 PM com.google.gwt.logging.server.RemoteLoggingServiceUtil logOnServer

SEVERE: Uncaught exception

java.lang.Throwable: (TypeError)

number: -2146823281

description: 'children' is null or not an object: 'children' is null or not an object

Jan 29, 2014 3:10:14 PM com.google.gwt.logging.server.RemoteLoggingServiceUtil logOnServer

SEVERE: Uncaught exception

java.lang.Throwable: (TypeError)

number: -2146823281

description: 'children' is null or not an object: 'children' is null or not an object

15:10:29,520 ERROR SqlExceptionHelper:144 - The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL131217141803620' defined on 'EXTENDED_REPO'.

com.netapp.snapcreator.workflow.exception.WorkFlowException: Couldn't create catalog entry

at com.netapp.snapcreator.workflow.catalog.ExtendedRepositoryHelper.<init>(ExtendedRepositoryHelper.java:99)

at com.netapp.snapcreator.workflow.impl.WorkflowEngineImpl.createCatalog(WorkflowEngineImpl.java:197)

at com.netapp.snapcreator.workflow.impl.WorkflowEngineImpl.setupWorkflow(WorkflowEngineImpl.java:183)

at com.netapp.snapcreator.workflow.impl.WorkflowEngineImpl.generateWorkflow(WorkflowEngineImpl.java:176)

at com.netapp.snapcreator.workflow.impl.WorkflowEngineImpl.submitAsync(WorkflowEngineImpl.java:76)

at com.netapp.snapcreator.engine.EngineCoreImpl.dispatchAction(EngineCoreImpl.java:173)

at com.netapp.snapcreator.engine.EngineCoreImpl.backupCreate(EngineCoreImpl.java:60)

at com.netapp.snapcreator.engine.EngineImpl.startBackup(EngineImpl.java:257)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:616)

at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)

at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)

at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSMethodInvoker.java:178)

at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:68)

at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:75)

at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)

at java.util.concurrent.FutureTask.run(FutureTask.java:166)

at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)

at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)

at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)

at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)

at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)

at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)

at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)

at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)

at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:167)

at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)

at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)

at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)

at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)

at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)

at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)

at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)

at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)

at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)

at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)

at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)

at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)

at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)

at org.eclipse.jetty.server.Server.handle(Server.java:370)

at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)

at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53)

at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)

at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021)

at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)

at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)

at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72)

at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264)

at org.eclipse.jetty.server.ssl.SslSocketConnector$SslConnectorEndPoint.run(SslSocketConnector.java:670)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)

at java.lang.Thread.run(Thread.java:679)

Re: Upgrade SnapCreator 4.1.0 from 4.1.0c fails

ktenzer — Wed, 29 Jan 2014 14:27:20 GMT

Hi Stefan,

I apologize for this but we dont support the upgrade from community release to NGS release yet. We hope to do this but havent been able to so far. We have made vast improvements in the upgrade code but it still isnt quite there to handle this complexity. The problem is that between community release and NGS release we had schema changes and thus the community release would require upgrade handling which we dont have in place. Typically we try not to make schema changes between community release and NGS but in this case we had to as some issues arose later than expected in our test cycles.

I have brought this issue up to database guys so lets see if they can think of a solution. We aren't giving up on this just because we dont support it however there is a possibility we arent able to provide solution...stay tuned.

Moving forward we would recommend you only use community release as a beta or to play around / test with until a time where we can support direct upgrade between community and NGS release.

Regards,

Keith

Re: Upgrade SnapCreator 4.1.0 from 4.1.0c fails

SVOLLRAT1 — Wed, 29 Jan 2014 14:35:48 GMT

Hi Keith

Thanks for the fast reply.

A pity that this little but important fact is not mentioned in ReleaseNotes nor in Install-Guide.

Not even the Upgrade-Command complained, would have been nice to at least there have something "attention you are doing something unsupported".

Hope the DB-Guys come up with something.

Regards

Stefan

topic Re: Upgrade SnapCreator 4.1.0 from 4.1.0c fails in Data Protection

Upgrade SnapCreator 4.1.0 from 4.1.0c fails

Re: Upgrade SnapCreator 4.1.0 from 4.1.0c fails

Re: Upgrade SnapCreator 4.1.0 from 4.1.0c fails