AnsweredAssumed Answered

XOG Errors during 13 Upgrade?

Question asked by Chris_Shaffer_hcsc on Feb 8, 2012
Latest reply on Mar 19, 2012 by Chris_Shaffer_hcsc
We are upgrading from 12.0.6 to 13. The install worked great and upgraded to 12.1 first and did all of the database stuff. After a nice hour long analyze database command it moved on to the 13 upgrade. Everything was chugging along until it got to the part where it performed xogs of the seeded data (All out of the box install stuff, no tweaking). And BOOM!

Have any of you experienced this? Keep in mind that the other xogs prior to this executed just fine.

I hate to post the data but in an effort of education and hopefully resolving it I will. Yes we have a ticket open but wanted to see what the community thought as well.

INSTALL.LOG entry where it blew up.
2/07/12 11:40 AM (ExecTask) Created dir: /userapps/niku/clarity13/logs/xog-seeddata/out/projmgr
2/07/12 11:40 AM (ExecTask) 
Applying assgn_pool_type_lookup.xml
2/07/12 11:40 AM (ExecTask) 
Applying booking_configurable_notification.xml
2/07/12 11:40 AM (ExecTask) Error Applying XOG: Failure occurred while applying booking_configurable_notification.xml
2/07/12 11:40 AM (ExecTask)  Check /userapps/niku/clarity13/logs/xog-seeddata/out/projmgr/booking_configurable_notification_out.xml for errors
2/07/12 11:40 AM (ExecTask) /userapps/niku/clarity13/.setup/scripts/db.xml:1674: The following error occurred while executing this line:
The BOOKING_CONFIGURATION_NOTIFICATION_OUT.xml looks a little like this.
 <Severity>FATAL</Severity>
<Description>Exception getting BusinessProcessEventManager 
java.lang.RuntimeException: Exception getting BusinessProcessEventManager
at com.niku.union.bpm.BusinessProcessFactory.getBusinessProcessEventManager(BusinessProcessFactory.java:132)
...... 24 more
Caused by: com.niku.union.config.ConfigurationException: Messenger init failed. This could be due to an incorrect 'preferIpv4Stack' setting that is currently set to 'true' .
... 29 more
Caused by: org.jgroups.ChannelException: failed to start protocol stack
... 34 more
Caused by: java.lang.Exception: problem creating sockets (bind_addr=/10.130.135.130, mcast_addr=ff0e:0:0:0:0:0:e600:de02:9091)
... 37 more
Caused by: java.net.SocketException: The socket name is not available on this system.
... 39 more
</Description>
</ErrorInformation>

Outcomes