MWS Migration Issue 10.15

Hi,

I am planning to upgrade MWS from 10.5 to 10.15 and gonna use migration utility.

I’ve installed MWS 10.15 with fixes and have given cloned database URL of old version.

Have migrated cloned database component to latest version using db configurator.

But MWS 10.15 is not coming Up with cloned database.

I’ve observed MWS 10.15 is coming up by creating new database component.

Can I use new database component to make MWS up and provide cloned database URL during running custom migration utility to migrate the old version instance?

Im not sure I understand what you mean with the above?
You can use a new DB for newly created instance or use cloned DB for migrations. What is the error you get when you run the migrated MWS against the cloned and migrated DB.

Hi Meglena,

I’ve used cloned MWS database for 10.15 MWS and migrated the cloned MWS database to latest version using db configurator.

MWS is not able to come up and coming below error

2023-06-29 10:35:33 BST (c.w.r.u.Debug:INFO) [Start Level: Equinox Container: 8acfe507-16f0-4805-a184-23e642fedb30] - Started sending JDK log messages to Log4J
2023-06-29 10:35:33 BST (c.w.r.l.LoggingUtils:INFO) [Thread-9] - Logging configuration loading took: 15ms
2023-06-29 10:35:33 BST (c.s.p.j.e.i.LoginModuleBundleTracker:INFO) [Start Level: Equinox Container: 8acfe507-16f0-4805-a184-23e642fedb30] - Processing bundle com.webMethods.caf.server(10.15.0.0000-0385)
2023-06-29 10:35:33 BST (c.w.r.u.FileUtil:INFO) [MWS Startup-1] - Cleaning up temp files matching ^jetty.* from directory D:/SoftwareAG1015/MWS/server/default/temp/
2023-06-29 10:35:33 BST (c.w.p.s.i.i.ClusterPhaseProvider:INFO) [MWS Startup-1] - Obtained cluster bootstrap lock
2023-06-29 10:35:33 BST (c.w.p.s.b.StartupManager:INFO) [MWS Startup-1] - Current DB component level is v10.11
2023-06-29 10:35:33 BST (c.w.p.s.i.BuildVersion:INFO) [MWS Startup-1] - MWS BuildVersion: 10.5.0.0010-0189
2023-06-29 10:35:33 BST (c.w.p.s.i.BuildVersion:INFO) [MWS Startup-1] - MWS InstalledVersion: 10.15.0.0000-0385
2023-06-29 10:35:33 BST (c.w.p.PortalException:INFO) [MWS Startup-1] - No registered exception delegate
2023-06-29 10:35:33 BST (c.w.p.s.i.i.ClusterPhaseProvider:INFO) [MWS Startup-1] - Released cluster bootstrap lock
2023-06-29 10:35:33 BST (c.w.p.s.PortalSystem:ERROR) [MWS Startup-1] - null
com.webMethods.portal.system.init.InitializationException: null
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializePhases(ClusterPhaseProvider.java:230) ~[?:?]
at com.webMethods.portal.system.init.impl.PartitionPhaseProvider.initializePhases(PartitionPhaseProvider.java:46) ~[?:?]
at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:1324) ~[com.webMethods.caf.server.common_10.15.0.0000-0385.jar:10.15.0.0000-0385]
at com.webMethods.portal.system.impl.PortalSystemInit.init(PortalSystemInit.java:100) ~[?:?]
at com.webMethods.portal.system.PortalSystem.doStartup(PortalSystem.java:1232) [com.webMethods.caf.server.common_10.15.0.0000-0385.jar:10.15.0.0000-0385]
at com.webMethods.portal.system.impl.PortalSystemActivator$StartupWorker.call(PortalSystemActivator.java:177) [com.webMethods.caf.server_10.15.0.0000-0385.jar:10.15.0.0000-0385]
at com.webMethods.portal.system.impl.PortalSystemActivator$StartupWorker.call(PortalSystemActivator.java:162) [com.webMethods.caf.server_10.15.0.0000-0385.jar:10.15.0.0000-0385]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: com.webMethods.portal.system.init.InitializationException
at com.webMethods.portal.system.boot.StartupManager.verifyDbComponentLevel(StartupManager.java:95) ~[?:?]
at com.webMethods.portal.system.boot.StartupManager.init(StartupManager.java:63) ~[?:?]
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.checkDBComponentLevel(ClusterPhaseProvider.java:264) ~[?:?]
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializePhases(ClusterPhaseProvider.java:211) ~[?:?]
… 10 more
2023-06-29 10:35:33 BST (c.w.r.p.ShutdownManager:INFO) [Thread-10] - Shutdown Manager running all shutdown hooks

Did you shutdown MWS before running the migration scripts? Make sure you shut everything down (IS and MWS and possibly Optimize, basically everything that has access to the cloned db) before running the migration scripts. Also check the clusters from mws and make sure the old installation and new installations are not in a cluster and edit cluster.xml file and deploy it back it they are clustered with old installation.

You can run migration scripts again, they may have failed. When you run migration scripts again, please take a copy of the logs and share them here if the issue persists.

1 Like

I’m having the same issue of MWS shutting down automatically because of failure in db configuration. I tried shutting down MWS and then installing db migration scripts. However, the migration script for MWS keeps on failing with the output:

error: java.sql.SQLIntegrityConstraintViolationException: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“WEBM_COPY”.“COMPONENT_EVENT”.“COMPONENT_EVENT_ID”)

on {webMethods1015 dir}/common/db/MywebMethodsServer/MywebMethodsServer/scripts/10.5.fix1-10.7/oracle/migrate.sql

It seems to run fine on all the folders with names < 10.5. I’m trying to upgrade webMethods 10.5 to 10.15. Furthermore, the db configuration seems to work fine for TN, IS, Process Engine and Process Audit.

Here is a snippet from the log file with the error:

Runner # 93 | c.s.d.a.Runner . run | java.lang.RuntimeException: java.sql.SQLIntegrityConstraintViolationException: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“WEBM_COPY”.“COMPONENT_EVENT”.“COMPONENT_EVENT_ID”)

Runner # 93 | c.s.d.a.Runner . run | ex[0] : com.softwareag.dcc.comp.ExecScript.execute(ExecScript.java:34)
Runner # 93 | c.s.d.a.Runner . run | ex[1] : com.softwareag.dcc.comp.Script.execute(Script.java:25)
Runner # 93 | c.s.d.a.Runner . run | ex[2] : com.softwareag.dcc.comp.Component.executeScript(Component.java:219)
Runner # 93 | c.s.d.a.Runner . run | ex[3] : com.softwareag.dcc.comp.Component.executeScripts(Component.java:186)
Runner # 93 | c.s.d.a.Runner . run | ex[4] : com.softwareag.dcc.comp.Component.migrate(Component.java:285)
Runner # 93 | c.s.d.a.Runner . run | ex[5] : com.softwareag.dcc.exec.MigrateAction.processComponent(MigrateAction.java:31)
Runner # 93 | c.s.d.a.Runner . run | ex[6] : com.softwareag.dcc.exec.Action.process(Action.java:87)
Runner # 93 | c.s.d.a.Runner . run | ex[7] : com.softwareag.dcc.comp.ComponentSet.execute(ComponentSet.java:93)
Runner # 93 | c.s.d.a.Runner . run | ex[8] : com.softwareag.dcc.exec.Action.execute(Action.java:75)
Runner # 93 | c.s.d.a.Runner . run | ex[9] : com.softwareag.dcc.app.Runner.migrate(Runner.java:148)
Runner # 93 | c.s.d.a.Runner . run | ex[10] : com.softwareag.dcc.app.Runner.run(Runner.java:86)
Runner # 93 | c.s.d.a.Runner . run | ex[11] : com.softwareag.dcc.cli.Main.(Main.java:102)
Runner # 93 | c.s.d.a.Runner . run | ex[12] : com.softwareag.dcc.cli.Main.main(Main.java:148)
“” # 94 | “” . “” | ex.stack[0] : com.softwareag.dcc.comp.ExecScript.execute(ExecScript.java:34)
“” # 94 | “” . “” | ex.stack[1] : com.softwareag.dcc.comp.Script.execute(Script.java:25)
“” # 94 | “” . “” | ex.stack[2] : com.softwareag.dcc.comp.Component.executeScript(Component.java:219)
“” # 94 | “” . “” | ex.stack[3] : com.softwareag.dcc.comp.Component.executeScripts(Component.java:186)
“” # 94 | “” . “” | ex.stack[4] : com.softwareag.dcc.comp.Component.migrate(Component.java:285)
“” # 94 | “” . “” | ex.stack[5] : com.softwareag.dcc.exec.MigrateAction.processComponent(MigrateAction.java:31)
“” # 94 | “” . “” | ex.stack[6] : com.softwareag.dcc.exec.Action.process(Action.java:87)
“” # 94 | “” . “” | ex.stack[7] : com.softwareag.dcc.comp.ComponentSet.execute(ComponentSet.java:93)
“” # 94 | “” . “” | ex.stack[8] : com.softwareag.dcc.exec.Action.execute(Action.java:75)
“” # 94 | “” . “” | ex.stack[9] : com.softwareag.dcc.app.Runner.migrate(Runner.java:148)
“” # 94 | “” . “” | ex.stack[10] : com.softwareag.dcc.app.Runner.run(Runner.java:86)
“” # 94 | “” . “” | ex.stack[11] : com.softwareag.dcc.cli.Main.(Main.java:102)
“” # 94 | “” . “” | ex.stack[12] : com.softwareag.dcc.cli.Main.main(Main.java:148)

How do I fix this issue?