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 » IIB9: Mapping Node, Invalid Column Type

Post new topic  Reply to topic
 IIB9: Mapping Node, Invalid Column Type « View previous topic :: View next topic » 
Author Message
akil
PostPosted: Thu Mar 05, 2015 11:51 pm    Post subject: IIB9: Mapping Node, Invalid Column Type Reply with quote

Partisan

Joined: 27 May 2014
Posts: 338
Location: Mumbai

Hi

I've a mapping node that's raising an exception - Invalid Data Type 3 times in a production environment..

The table has a lot of columns, and unfortunately it does not seem to specify which of the columns is the culprit ..

What would be the way to figure out what's the issue?

Code:

2015-03-06 12:27:05.021143    15111   UserTrace   BIP3959I: The Mapping node is traversing the input tree by using the nodetest ''element(entityID)'' and the relationship ''child''. The number of matching elements is ''1''.
                                       The Mapping node is traversing the input tree as part of the processing of the current transform.
                                       Check the following messages to see the progression of the mapping process.
2015-03-06 12:27:05.024441    15111   UserTrace   BIP3950I: The Mapping node is about to run an SQL statement ''select GUFA.CENTERS.ID, GUFA.CENTERS.EXTERNAL_ID, GUFA.CENTERS.CENTER_NAME, GUFA.CENTERS.FORMATION_DATE, GUFA.CENTERS.SERVICING_AGENT, GUFA.CENTERS.MAXIMUM_INDIVIDUALS, GUFA.CENTERS.MEETING_TIME, GUFA.CENTERS.ADDRESS_LINE1, GUFA.CENTERS.ADDRESS_LINE2, GUFA.CENTERS.ADDRESS_LINE3, GUFA.CENTERS.CITY_CODE, GUFA.CENTERS.STATE_CODE, GUFA.CENTERS.PIN, GUFA.CENTERS.OPERATING_REGION_CODE, GUFA.CENTERS.BRANCH_CODE, GUFA.CENTERS.DESCRIPTION, GUFA.CENTERS.PHONE_NO, GUFA.CENTERS.CREATED_BY, GUFA.CENTERS.CREATED_AT, GUFA.CENTERS.STATUS, GUFA.CENTERS.INTERNAL_ID, GUFA.CENTERS.ERROR_DESCRIPTION, GUFA.CENTERS.UPDATED_AT, GUFA.CENTERS.RECORD_ERRORS, GUFA.CENTERS.INCOMING_FILE_ID, GUFA.CENTERS.UDF1, GUFA.CENTERS.UDF2, GUFA.CENTERS.UDF3, GUFA.CENTERS.UDF4, GUFA.CENTERS.UDF5, GUFA.CENTERS.UDF6, GUFA.CENTERS.UDF7, GUFA.CENTERS.UDF8, GUFA.CENTERS.UDF9, GUFA.CENTERS.UDF10, GUFA.CENTERS.UDF11, GUFA.CENTERS.UDF12, GUFA.CENTERS.UDF13, GUFA.CENTERS.UDF14, GUFA.CENTERS.UDF15, GUFA.CENTERS.UDF16, GUFA.CENTERS.UDF17, GUFA.CENTERS.UDF18, GUFA.CENTERS.UDF19, GUFA.CENTERS.UDF20, GUFA.CENTERS.UDF21, GUFA.CENTERS.UDF22, GUFA.CENTERS.UDF23, GUFA.CENTERS.UDF24, GUFA.CENTERS.UDF25, GUFA.CENTERS.UDF26, GUFA.CENTERS.UDF27, GUFA.CENTERS.UDF28, GUFA.CENTERS.UDF29, GUFA.CENTERS.UDF30 from GUFA.CENTERS where GUFA.CENTERS.ID =   ?  '' on DataSource ''GUFA''.
                                       The Mapping node is about to invoke an SQL statement through one of the Database transforms.
                                       Check the following messages to see the results of this SQL statement.
2015-03-06 12:27:05.029121    15111   UserTrace   BIP6261I: Loading the JDBC driver class for node: 'Broker 'IB9NODE'; Execution Group 'GUFA'; Message Flow 'startJob'; Node 'moveCenterToStaging'; Node Type 'Mapping'.
                                       The JDBC driver class named ''oracle.jdbc.OracleDriver'' was loaded, with major number version ''11'' and minor number version ''2''. The driver is a genuine JDBC Compliant driver: 'true'.
                                       No user action required.
2015-03-06 12:27:05.142699     4473   Error       BIP4361W: Java node warning: 'GUFA Invalid column type'.
                                       Warning message generated by user Java node.
                                       Contact the node provider for further details.
2015-03-06 12:27:05.143051     4473   Error       BIP4361W: Java node warning: 'GUFA Invalid column type'.
                                       Warning message generated by user Java node.
                                       Contact the node provider for further details.
2015-03-06 12:27:05.143323    15111   Error       BIP4361W: Java node warning: 'GUFA Invalid column type'.
                                       Warning message generated by user Java node.
                                       Contact the node provider for further details.
2015-03-06 12:27:05.143503    15111   UserTrace   BIP3953W: The Mapping node has run an SQL statement ''select GUFA.CENTERS.ID, GUFA.CENTERS.EXTERNAL_ID, GUFA.CENTERS.CENTER_NAME, GUFA.CENTERS.FORMATION_DATE, GUFA.CENTERS.SERVICING_AGENT, GUFA.CENTERS.MAXIMUM_INDIVIDUALS, GUFA.CENTERS.MEETING_TIME, GUFA.CENTERS.ADDRESS_LINE1, GUFA.CENTERS.ADDRESS_LINE2, GUFA.CENTERS.ADDRESS_LINE3, GUFA.CENTERS.CITY_CODE, GUFA.CENTERS.STATE_CODE, GUFA.CENTERS.PIN, GUFA.CENTERS.OPERATING_REGION_CODE, GUFA.CENTERS.BRANCH_CODE, GUFA.CENTERS.DESCRIPTION, GUFA.CENTERS.PHONE_NO, GUFA.CENTERS.CREATED_BY, GUFA.CENTERS.CREATED_AT, GUFA.CENTERS.STATUS, GUFA.CENTERS.INTERNAL_ID, GUFA.CENTERS.ERROR_DESCRIPTION, GUFA.CENTERS.UPDATED_AT, GUFA.CENTERS.RECORD_ERRORS, GUFA.CENTERS.INCOMING_FILE_ID, GUFA.CENTERS.UDF1, GUFA.CENTERS.UDF2, GUFA.CENTERS.UDF3, GUFA.CENTERS.UDF4, GUFA.CENTERS.UDF5, GUFA.CENTERS.UDF6, GUFA.CENTERS.UDF7, GUFA.CENTERS.UDF8, GUFA.CENTERS.UDF9, GUFA.CENTERS.UDF10, GUFA.CENTERS.UDF11, GUFA.CENTERS.UDF12, GUFA.CENTERS.UDF13, GUFA.CENTERS.UDF14, GUFA.CENTERS.UDF15, GUFA.CENTERS.UDF16, GUFA.CENTERS.UDF17, GUFA.CENTERS.UDF18, GUFA.CENTERS.UDF19, GUFA.CENTERS.UDF20, GUFA.CENTERS.UDF21, GUFA.CENTERS.UDF22, GUFA.CENTERS.UDF23, GUFA.CENTERS.UDF24, GUFA.CENTERS.UDF25, GUFA.CENTERS.UDF26, GUFA.CENTERS.UDF27, GUFA.CENTERS.UDF28, GUFA.CENTERS.UDF29, GUFA.CENTERS.UDF30 from GUFA.CENTERS where GUFA.CENTERS.ID =   ?  '', which has failed with the following exception: ''Invalid column type''. The map has not been configured to handle this exception, so the processing of the map will be stopped and the exception will be thrown upstream from this node.
                                       The Mapping node has run an SQL statement, which threw an exception. The processing of the map will stop.
                                       Review the contents of the exception and ensure that there is appropriate processing of the Failure transform in the map.
2015-03-06 12:27:05.943600    15111   UserTrace   BIP3146E: Error detected whilst processing a message 'startJob.HTTP Input'.
                                       The message broker detected an error whilst processing a message in node 'startJob.HTTP Input'. The message has been augmented with an exception list and has been propagated to the node's catch terminal for further processing.

_________________
Regards
Back to top
View user's profile Send private message Visit poster's website
fjb_saper
PostPosted: Fri Mar 06, 2015 5:38 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Well it looks as if the DB has changed since you built the map and at least one column type is not the same as in your data project...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
akil
PostPosted: Fri Mar 06, 2015 6:37 am    Post subject: Reply with quote

Partisan

Joined: 27 May 2014
Posts: 338
Location: Mumbai

The warning comes 3 times, not more, not less. Does that mean it is affecting 3 columns? I wish it would just say the column names, instead of the datasource name ...

Will revert once the columns are compared
_________________
Regards
Back to top
View user's profile Send private message Visit poster's website
akil
PostPosted: Fri Mar 06, 2015 10:52 pm    Post subject: Reply with quote

Partisan

Joined: 27 May 2014
Posts: 338
Location: Mumbai

Hi

The database columns haven't changed, but there's a peculiarity,

-- when the mapping node selects from the database and creates an output message , it works
-- when the mapping node selects from database 1 and inserts into database 2, it gives this error. Database 1 is Oracle, Database 2 is MSSQL.

I am aware that in ESQL, a node can access multiple databases of only a particular type (all oracle, all mssql), is this also a restriction in the mapping node?
_________________
Regards
Back to top
View user's profile Send private message Visit poster's website
fjb_saper
PostPosted: Fri Mar 06, 2015 11:49 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Does the MSSQL DB have a DBLink in Oracle? I would also imagine that not all oracle types are valid in MSSQL...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
akil
PostPosted: Sat Mar 07, 2015 12:47 am    Post subject: Reply with quote

Partisan

Joined: 27 May 2014
Posts: 338
Location: Mumbai

Hi

The mapping node has 2 database transforms,

the first is a database-select (reading from SQL server), this is mapped via a for-each, to an database-insert (inserting into Oracle).

The individual columns are copied via 'move' / 'cast' as the case may be.

This is the map that was giving an error, when we remove the 'insert' , and instead just create an output message (DFDL), it works..

No database links here..

( the map is reading from one database and inserting into another )

Regards
Akhilesh
_________________
Regards
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIB9: Mapping Node, Invalid Column Type
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.