5.6 Panics

This topic has 4 replies, 4 voices, and was last updated 16 years, 9 months ago by Bill Marsch.

Creator

Topic
March 11, 2008 at 7:57 pm #49899
Max Drown (Infor)
Keymaster
I upgraded the OS to AIX 5.3 and Cloverleaf from 5.2.1 to 5.6. So far, I’ve had to processes panic. I have no idea why, but I need to figure it out before I upgrade the production box to 5.6.

This is from the log

Code: “bn12.log.old” 1323L, 46981C evStrDesc : evSocket : 0 evMsgQue : 0 evTid : 8 evState : 0 evPtMsg : 0x0 evUserData : 0x225fe3f8 evCallBack : 0x200d0450 evCbShutdown : 0x0 evRecurFreq : 5.0000 —– Polled Events —– el: 0x224bd548 elCount : 1 elHead: 0x226a3858 elTail: 0x226a3858 ele: 0x226a3858 — POLLED event: 0x226a3818 —– Ready Events —– el: 0x224bd568 elCount : 0 elHead: 0x0 elTail: 0x0 —– Outstanding Pthread Ctrl Msgs —– pmq: 0x224bd588 Count : 0 Head : 0x0 Tail : 0x0 —– Outstanding Pthread User Ctrl Msgs —– pmq: 0x224bd5a8 Count : 0 Head : 0x0 Tail : 0x0 —– Outstanding Pthread User Data Msgs —– pmq: 0x224bd5c8 Count : 0 Head : 0x0 Tail : 0x0 PANIC: Calling “dbi shutdown” for thread bn12_cmd PANIC: Calling “dbi shutdown” for thread bn12_xlate PANIC: Calling “dbi shutdown” for thread bn12ms4_in PANIC: Calling “dbi shutdown” for thread bn12mq_out PANIC: Calling “dbi shutdown” for thread bn12hemod_out PANIC: Calling “dbi shutdown” for thread bn12chartl_out PANIC: Calling “dbi shutdown” for thread bn12ipath_out PANIC: Calling “dbi shutdown” for thread bn12ms4i_out PANIC: Calling “dbi shutdown” for thread bn12mdmgr_out PANIC: Calling “dbi shutdown” for thread bn12ipath_out [dbi :dbi :WARN/0:bn12ipath_out:03/11/2008 14:48:48] NULL DTD when closing DBI PANIC: Calling “dbi shutdown” for thread bn12ipath_out [dbi :dbi :WARN/0:bn12ipath_out:03/11/2008 14:48:48] NULL DTD when closing DBI PANIC: Thread panic—engine going down PANIC: assertion ‘(ptd)->ptd_msg_delivered_ok == ((Message *) 0)’ failed at protocolThread.cpp/825 WARNING: Message [0.0.367111] is in the RDB and was left bound into Tcl

hcidbdump -r -U max -m 367111

Code: 14:46:54 [0.0.367111] P D N 8193 14 231 bn12ipath_out bn12ipath_out

hcidbdump -r -U max -m 367111 -L

Code: msg: 0x3000003c msgType : DATA msgClass : PROTOCOL msgState : OB delivered OK (14) msgPriority : 8193 msgRecoveryDbState: 3 msgFlags : 0x8006 msgMid : [0.0.367111] msgSrcMid : [0.0.326909] msgSrcMidGroup : midNULL msgOrigSrcThread : bn12ipath_out msgOrigDestThread : bn12ipath_out msgSrcThread : bn12ipath_out msgDestThread : bn12ipath_out msgXlateThread : msgSkipXlate : 0 msgSepChars : msgNumRetries : 0 msgGroupId : 0 msgDriverControl : msgRecordFormat : msgRoutes : msgUserData : msgStaticIsDirty : 0 msgVariableIsDirty: 0 msgTimeStartIb : 1205264814.144 msgTimeStartOb : 1205161554.825 msgTimeCurQueStart: 0.000 msgTimeTotalQue : 12049.476 msgTimeRecovery : 1205264814.152 msgEoConfig : 0x0 msgData (BO) : 0x30000120 message : ‘MSH|^~&|CLOVERLEAF|BHC|ORMIS|BHC|20080310100551||ADT^A28|00000000001769256|P|2.3x0dEVN|A28|20080310100547|||BOMS4TESTx0dPID|1|000738897|445066||TESTPATIENT^ALICE^L||19280527|F||W|40042 HWY 5^^GLASGOW^MO^65254^^^HOWARD|||||M|NON||496261185x0d’

-- Max Drown (Infor)
Creator

Topic

Viewing 3 reply threads

Author

Replies
- March 11, 2008 at 8:05 pm #64037
  Max Drown (Infor)
  Keymaster
  This is from the log of the receiving app.
  
  Code: Looks like the ADTs we’re getting have bad data in them according to Oracle. connection from host 10.128.17.28, port 45108, socket 8 ORACLE error detected: ORA-01843: not a valid month connection from host 10.128.17.28, port 45171, socket 8 ORACLE error detected: ORA-01843: not a valid month bind(): Address already in use connection from host 10.128.17.28, port 46824, socket 8 ORACLE error detected: ORA-01843: not a valid month bind(): Address already in use connection from host 10.128.17.28, port 48403, socket 8 ORACLE error detected: ORA-01843: not a valid month
  
  -- Max Drown (Infor)
- March 11, 2008 at 9:31 pm #64038
  John Hamilton
  Participant
  I would start by looking at the database.
  
  It seems to be where the issue is.
  
  Check to make sure there is only one state 14 message. I think with 5.6 there are different states based on how you configure you outbound procs or the newly built in recover resend processes.
  
  If that is ok. I would just clear out the database and reset the region remove the shared memory and all that good stuff.
  
  Then try again.
  
  If all that fails your going to have to call support. It is hard without having my hands on your box to really resolve the issue.
- March 11, 2008 at 11:35 pm #64039
  Michael Hertel
  Participant
  See this post: https://usspvlclovertch2.infor.com/viewtopic.php?t=2572&highlight=ptdmsgdeliveredok
- March 12, 2008 at 2:03 pm #64040
  Bill Marsch
  Participant
  If you followed that link at the end form the posting before me you will see that we are having the smae problem and panic abend. Mary Kobis is the person that I work with. we have forwarded our condition to support. I am here in dallas attending a class at quovadx. I am hoping that if you forward your informattion to support we may be able to have quovadx resolve this issue that appears to be in 5.6
Author

Replies

Viewing 3 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.