ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » DB CHAR(1) field populates message field with 4 characters

Post new topic  Reply to topic
 DB CHAR(1) field populates message field with 4 characters « View previous topic :: View next topic » 
Author Message
sat_in_field
PostPosted: Fri Feb 20, 2009 7:08 am    Post subject: DB CHAR(1) field populates message field with 4 characters Reply with quote

Novice

Joined: 23 Jan 2003
Posts: 20

This query is executed via a passthru by WMB6.0 on new oracle (10.2.4) RAC DB instance TCID11

SELECT D.SYS_CD_DMD,
D.DSN_INT_CD_DMD,
D.DMD_REFORMAT_IN,
D.TPT_CD_DMD,
D.DMD_REPAIR_IND,
D.DMD_IFO_CD,
D.DSM_CD_DMD,
D.DMD_ACCT_VALIDATION
FROM TPI_DBA.DEFAULT_MSG_DEST D
WHERE D.DSN_EXT_CD_DMD='O_DEFAULT'
AND D.MST_CD_DMD='MT304'
AND D.SYS_CD_DMD= 'FCNYUS33MX4'
AND D.TPT_CD_DMD='FCNYUS33MX4'
AND D.DSN_INT_CD_DMD='IL';

Each of the selected values is then placed into the Environment.Outbound[1].

However in every test so far the 5th item in the select list is being returned and populated in the message tree with a length of 4 characters. The column that is being read is CHAR(1) and contains only the character Y. The returned order is correct - none of the other Y values returned have a length longer than 1 on the DB or in returned values. Whats going on?

As this info is then inserted into another table where the column again is a CHAR(1) it is causing the statement to fail as 4 does not go into 1. Why is it being padded.

This is not happening on the old non RAC DB.

Cheers
Steve

2009-02-19 17:09:40.571808 26 UserTrace BIP2544I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Executing database SQL statement ''SELECT D.SYS_CD_DMD, D.DSN_INT_CD_DMD, D.DMD_REFORMAT_IN, D.TPT_CD_DMD, D.DMD_REPAIR_IND, D.DMD_IFO_CD, D.DSM_CD_DMD, D.DMD_ACCT_VALIDATION FROM TPI_DBA.DEFAULT_MSG_DEST D WHERE (((((D.DSN_EXT_CD_DMD)=('O_DEFAULT'))AND((D.MST_CD_DMD)=(?)))AND((D.SYS_CD_DMD)=(?)))AND((D.TPT_CD_DMD)=(?)))AND((D.DSN_INT_CD_DMD)=(?))'' derived from ('', '1.1'); expressions ''TRIMBOTH(BOTH FROM InputBody.MXData.DestinationDetails.MessageType), TRIMBOTH(BOTH FROM InputBody.MXData.DestinationDetails.PartnerBIC), TRIMBOTH(BOTH FROM InputBody.MXData.DestinationDetails.PartnerBIC), TRIMBOTH(BOTH FROM InputBody.MXData.DestinationDetails.DestinationSystem)''; resulting parameter values '''MT304', 'NYUS33', 'NYUS33', 'IL'''.
2009-02-19 17:09:40.577224 26 UserTrace BIP2539I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Evaluating expression ''DATABASE(, TRIMBOTH(BOTH FROM InputBody.MXData.DestinationDetails.MessageType), TRIMBOTH(BOTH FROM InputBody.MXData.DestinationDetails.PartnerBIC), TRIMBOTH(BOTH FROM InputBody.MXData.DestinationDetails.PartnerBIC), TRIMBOTH(BOTH FROM InputBody.MXData.DestinationDetails.DestinationSystem))'' at ('', '1.1'). This resolved to ''SELECT D.SYS_CD_DMD, D.DSN_INT_CD_DMD, D.DMD_REFORMAT_IN, D.TPT_CD_DMD, D.DMD_REPAIR_IND, D.DMD_IFO_CD, D.DSM_CD_DMD, D.DMD_ACCT_VALIDATION FROM TPI_DBA.DEFAULT_MSG_DEST D WHERE (((((D.DSN_EXT_CD_DMD)=('O_DEFAULT'))AND((D.MST_CD_DMD)=(?)))AND((D.SYS_CD_DMD)=(?)))AND((D.TPT_CD_DMD)=(?)))AND((D.DSN_INT_CD_DMD)=(?))''. The result was ''Complex result''.
2009-02-19 17:09:40.580592 26 UserTrace BIP2562I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning a list to ''Environment.Outbound[]''.
2009-02-19 17:09:40.580652 26 UserTrace BIP2566I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning value '''NYUS33''' to field / variable ''Environment.Outbound[1]''.
2009-02-19 17:09:40.580912 26 UserTrace BIP2566I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning value '''IL''' to field / variable ''Environment.Outbound[1]''.
2009-02-19 17:09:40.581024 26 UserTrace BIP2566I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning value '''Y''' to field / variable ''Environment.Outbound[1]''.
2009-02-19 17:09:40.581044 26 UserTrace BIP2566I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning value '''NYUS''' to field / variable ''Environment.Outbound[1]''.
2009-02-19 17:09:40.581064 26 UserTrace BIP2566I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning value '''Y ''' to field / variable ''Environment.Outbound[1]''.
2009-02-19 17:09:40.581084 26 UserTrace BIP2566I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning value '''MX''' to field / variable ''Environment.Outbound[1]''.
2009-02-19 17:09:40.581104 26 UserTrace BIP2566I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning value '''SWIFT''' to field / variable ''Environment.Outbound[1]''.
2009-02-19 17:09:40.581124 26 UserTrace BIP2566I: Node 'TPCI_TPARD_INTERFACE_FLOW.TPCI_TPARD_INTERFACE_DEST_DETAILS.Get Default Values': Assigning value '''Y''' to field / variable ''Environment.Outbound[1]''.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » DB CHAR(1) field populates message field with 4 characters
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.