webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

TN migration from 6.1 to 7.1 disaster

  • 1.  TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 12:00 AM

    Hi all,
    We followed all the steps on webMethods upgrade guide verion 7.1.x pdf on page 36-37-38.
    After migration was done , when we started up our 6.1 IS the TN crashed with the following error:

    cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)

    This is a disaster situation for us as our only test is down.
    Any ideas what might fix this
    please help


    2008-08-04 16:43:52 CDT WMERROR 6df329c0626e11dda9d2e3255c5e28a2NULL 6df329c0626e11dda9d2e3255c5e28a21217886232559 testeb2s.usaa.com:5575 com.wm.app.tn.err.EXMLException:

    wm.tn.doctype:update

    com.wm.app.tn.db.DatastoreException
    Database error updating type 53o4h200vdg0qt9400000022: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)
    (0) java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)
    (1) java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)

    java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)
    java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”."ACTIVITYLcom.wm.app.tn.err.EXMLException:

    wm.tn.doctype:update

    com.wm.app.tn.db.DatastoreException
    Database error updating type 53o4h200vdg0qt9400000022: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)
    (0) java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)
    (1) java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)

    java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)
    java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)
    java.sql.SQLException: [wm-cjdbc34-0089][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“webMethods”.“ACTIVITYLOG”.“ACTIVITYLOGID”)
    at com.wm.dd.jdbc.base.BaseExceptions.createException(Unknown Source)
    at com.wm.dd.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.wm.dd.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
    at com.wm.dd.jdbc.base.BaseStatement.commonExecute(Unknown Source)
    at com.wm.dd.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
    at com.wm.dd.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
    at com.wm.app.tn.db.EventOperations.log(EventOperations.java:124)
    at com.wm.app.tn.db.BDTypeOperations.update(BDTypeOperations.java:202)
    at com.wm.app.tn.db.BizDocTypeStore.update(BizDocTypeStore.java:312)
    at wm.tn.doctype.update(doctype.java:240)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.rewm.tn.doctype:update
    2008-08-04 16:43:54 CDT WMERROR 6f82f180626e11dda9fce3255c5e28a2NULL 6f82f180626e11dda9fce3255c5e28a21217886234905 testeb2s.usaa.com:5575 com.wm.app.b2b.client.ServiceException com.wm.app.b2b.client.ServiceException
    at wm.server.remote.invoke(remote.java:417)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:294)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:229)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:199)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:408)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:503)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:367)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:100)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:584)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:499)
    at pub.remoteimpl.invoke(remoteimpl.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:294)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcesswm.server.remote:invoke
    2008-08-04 16:43:54 CDT WMERROR 6f82f180626e11dda9fce3255c5e28a2NULL 6f82f180626e11dda9fce3255c5e28a21217886234917 testeb2s.usaa.com:5575 com.wm.app.b2b.client.ServiceException com.wm.app.b2b.client.ServiceException
    at wm.server.remote.invoke(remote.java:417)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:294)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:229)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:199)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:408)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:503)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:367)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:100)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:584)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:499)
    at pub.remoteimpl.invoke(remoteimpl.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:294)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcesspub.remote:invoke
    2008-08-04 16:43:54 CDT WMERROR 6f82f180626e11dda9fce3255c5e28a2NULL 6f82f180626e11dda9fce3255c5e28a21217886234941 testeb2s.usaa.com:5575 com.wm.app.b2b.client.ServiceException com.wm.app.b2b.client.ServiceException
    at wm.server.remote.invoke(remote.java:417)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:294)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:229)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:199)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:408)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:503)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:367)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:100)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:584)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:499)
    at pub.remoteimpl.invoke(remoteimpl.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:294)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcesswm.server.remote:invoke
    2008-08-04 16:43:54 CDT WMERROR 6f82f180626e11dda9fce3255c5e28a2NULL 6f82f180626e11dda9fce3255c5e28a21217886234953 testeb2s.usaa.com:5575 com.wm.app.b2b.client.ServiceException com.wm.app.b2b.client.ServiceException
    at wm.server.remote.invoke(remote.java:417)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:294)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:587)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:229)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:199)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:408)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:503)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java


    #webMethods
    #webMethods-General
    #webMethods-Upgrade
    #Integration-Server-and-ESB


  • 2.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 03:28 PM


  • 3.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 04:24 PM

    Jesus I believe you ran the scripts and they didn’t run successfully. I remember facing this kind of problem with one of the client and webMethods SR was opened for that, after some research they asked to delete the ActivityID, After deleting that everything went fine.


    #Integration-Server-and-ESB
    #webMethods-Upgrade
    #webMethods-General
    #webMethods


  • 4.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 06:07 PM

    But did all the TN data migrate to 7.1.1 successfully after you ran the scripts?Did you see all the data in your 7.1 TN Console? A lot is missing from ours.

    We had to restore our DB schemas used for 6.1 last night.
    Now my question is what exactly went wrong.
    I strictly followed the instructions in the Migration Guide PDF.

    Thank you so soo much for your help Talha…I appreciate ou guiding me through this issue


    #webMethods-Upgrade
    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods


  • 5.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 07:07 PM

    Jesus,

    The problem we faced was with the scripts, when we were running those scripts they were giving exceptions. In other words we couldn’t even run the scripts successfully. I would suggest to open a SR with webMethods immediately since this looks like a bug or something which isn’t mentioned in migration guide.


    #webMethods
    #webMethods-Upgrade
    #Integration-Server-and-ESB
    #webMethods-General


  • 6.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 07:42 PM

    “After migration was done , when we started up our 6.1 IS the TN…”

    I’m confused. Did you try to start a 6.1 instance against a 7.1.x DB?


    #webMethods-Upgrade
    #webMethods
    #Integration-Server-and-ESB
    #webMethods-General


  • 7.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 08:34 PM

    No Rob,

    6.1 is on a separate DB and 7.1 is on a different DB.

    I just ran the dbconfigurator commands on 7.1 and used the 6.1 db’s URL & credentials as required in the commands.


    #Integration-Server-and-ESB
    #webMethods-General
    #webMethods
    #webMethods-Upgrade


  • 8.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 08:35 PM

    Im sorry , As for your question , since some applications are still testing on 6.1 so just out of curiosity i restarted the 6.1 instance to see if everything is OK and it bombed.!

    Currently we have 6.1 & 7.1 running side by side .
    Once migration is complete we wiill retire 6.1.
    Any ideas Rob where i messed up?


    #webMethods-General
    #webMethods
    #Integration-Server-and-ESB
    #webMethods-Upgrade


  • 9.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Tue August 05, 2008 09:24 PM

    Hmm. Odd that the migration pooched the DB. I’m with Talha on this one, opening an SR with wM tech support seems like the best bet.


    #webMethods-Upgrade
    #webMethods-General
    #webMethods
    #Integration-Server-and-ESB


  • 10.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Wed August 06, 2008 07:23 PM

    Ric,

    We are also in the same process of migrating TN61 to TN711 db,we are still thinking the migration steps explained in the doc will result success or not…Taking the tech support help is the way but it might be slow…

    BTW,are you migrating/cloning 61 db instance to 71db instance?? that is what doc explains…

    I dont have any updated info at this moment with the issue you are facing.

    HTH,
    RMg


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-General
    #webMethods-Upgrade


  • 11.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Wed August 06, 2008 11:16 PM

    Ricardo,
    We are also trying to migrate from 6.1 to 7.1.1.
    My migration failed where all the components were not migrated. and our DB crashed.
    A suggestion before you try this again:
    Try this again on a mirror image of our test DB.So i dont mutilate our test db.

    My question is can anyone tell me why do i need to create the storage/tablespaces?
    The PDF doesnt really doesnt explain the steps much.
    And if i try migration with the dbConfiguratorUI.sh (GUI) where do i enter the source db (6.1) and the target db(7.1) since there is just one DB URL/UID/Password.

    Any help would be monumentally appreciated.
    Scoobydoo


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Upgrade
    #webMethods-General


  • 12.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Fri August 08, 2008 04:20 AM

    Are you following the same steps that explained in this guide…ie 6.1 to 7.1.x??

    webMethods_Upgrade_Guide_7_1_x

    HTH,
    RMG


    #webMethods-Upgrade
    #webMethods
    #Integration-Server-and-ESB
    #webMethods-General


  • 13.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Fri August 08, 2008 06:11 AM

    yes RMG , i did.
    I tried the exact same steps in the guide and our 6.1 db bombed.
    So now i am looking at alternatives.

    What do you think about exporting TN data from 6.1 and importing all of them in to 7.1.1 from TNC ?
    Any ideas?
    Thank RMG for the help !


    #webMethods-Upgrade
    #webMethods-General
    #webMethods
    #Integration-Server-and-ESB


  • 14.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Fri August 08, 2008 05:09 PM

    I haven’t tried this…Yoy may try with one TP stuff and see how it works…

    HTH,
    RMG


    #webMethods-General
    #webMethods
    #webMethods-Upgrade
    #Integration-Server-and-ESB


  • 15.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Fri August 22, 2008 01:18 AM

    The way to approach might be to take an export of the entire Trading networks database including any of the triggers and indexes to a different schema. Following which to run the scripts as a user with DBA privileges. Do check that the DB scripts ran fine. Once that is done to run the migrate utility. Both of these should come clean. However any exceptional case may be due to application of patches on the 6.1 trading networks. You might have to check if the patches included database scripts.
    HTH
    ~jk


    #webMethods
    #Integration-Server-and-ESB
    #webMethods-Upgrade
    #webMethods-General


  • 16.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Fri August 22, 2008 08:01 PM

    Jerry,

    Thanks for your quick tip…really its a must note for anyone doing TN 6.1 to 711 migration…

    Thanks,
    -RMG


    #Integration-Server-and-ESB
    #webMethods-Upgrade
    #webMethods
    #webMethods-General


  • 17.  RE: TN migration from 6.1 to 7.1 disaster

    Posted Wed November 12, 2008 10:51 PM

    I hope they(wM) kept that in mind when writing the migration procedures.


    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods-Upgrade
    #webMethods