| Author | 
		  Message
		 | 
		
		  | giridhararm | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:27 am    Post subject: request urgent BIP 2393 E | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 22 Apr 2009 Posts: 28
  
  | 
		  
		    
			  
				HI there 
 
 
i installed db2 mQ AND MB8 IN VMWARE 
 
 
AM GETTING BELOW ERROR 
 
 
( MB8BROKER.X ) Message backed out to a queue; node 'ESQL_Create_Customer_Account.ESQL_BOOKSTORE_CCA_IN'.   
 
 
Node 'ESQL_Create_Customer_Account.ESQL_BOOKSTORE_CCA_IN' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.   
 
 
Examine previous messages and the message flow to determine why the message is being backed out.  Correct this situation if possible.  
 
 
( MB8BROKER.X ) Message backed out to a queue; node 'ESQL_Create_Customer_Account.ESQL_BOOKSTORE_CCA_IN'.   
 
 
Node 'ESQL_Create_Customer_Account.ESQL_BOOKSTORE_CCA_IN' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.   
 
 
Examine previous messages and the message flow to determine why the message is being backed out.  Correct this situation if possible.  
 
 
 MB8BROKER.X ) Database error: ODBC return code '-1' from data source ''BSTOREDB'' using ODBC driver manager ''odbc32.dll''.   
 
 
The broker received an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error.   
 
 
Use the following messages to determine the cause of the error. Typical problems are an incorrect data source, or table names. Correct either the database or the broker configuration.  
 
 
( MB8BROKER.X ) Error detected whilst processing a message in node 'ESQL_Create_Customer_Account.Database'.   
 
 
The message broker detected an error whilst processing a message in node 'ESQL_Create_Customer_Account.Database'. An exception has been thrown to cut short the processing of the message.   
 
 
See the following messages for details of the error.  
 
 
 
( MB8BROKER.X ) Exception condition detected on input node 'ESQL_Create_Customer_Account.ESQL_BOOKSTORE_CCA_IN'.   
 
 
The input node 'ESQL_Create_Customer_Account.ESQL_BOOKSTORE_CCA_IN' detected an error whilst processing a message.  The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again.  Following messages will indicate the cause of this exception. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smdavies99 | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:34 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Council
 
 Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land. 
  | 
		  
		    
			  
				
   
	| Code: | 
   
  
	
 
MB8BROKER.X ) Database error: ODBC return code '-1' from data source ''BSTOREDB'' using ODBC driver manager ''odbc32.dll''.
 
 
The broker received an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error. 
 
 | 
   
 
 
 
So have you looked at all the numerous other posts in this forum that has this very same error?
 
 
If you have, have you checked that you have configured it all correctly? _________________ WMQ User since 1999
 
MQSI/WBI/WMB/'Thingy' User since 2002
 
Linux user since 1995
 
 
 
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:34 am    Post subject: Re: request urgent BIP 2393 E | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| giridhararm wrote: | 
   
  
	| i installed db2 mQ AND MB8 IN VMWARE  | 
   
 
 
 
Congratulations. What versions of WMQ & DB2?
 
 
   
	| giridhararm wrote: | 
   
  
	|  MB8BROKER.X ) Database error: ODBC return code '-1' from data source ''BSTOREDB'' using ODBC driver manager ''odbc32.dll''. | 
   
 
 
 
I'd check that the ODBC is working through non-WMB tools, then think about an ODBC trace to trap any additional details. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giridhararm | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:44 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 22 Apr 2009 Posts: 28
  
  | 
		  
		    
			  
				AM NEW TO MB
 
 
I ISNTALLED DB2 9 AND MB8 and i used defualt configuration
 
 
i run all this commands i dont know where going wrong 
 
 
mqsireload MB8BROKER -e x
 
 
 
mqsicvp MB8BROKER -n BSTREDB  
 
 
 
mqsicvp MB8BROKER  –n BSTREDB   –u db2admin –p db2admin
 
 
 
mqsiservice MB8BROKER  -r DataSourceName=BSTREDB | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giridhararm | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:45 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 22 Apr 2009 Posts: 28
  
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smdavies99 | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:52 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Council
 
 Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land. 
  | 
		  
		    
			  
				Why did you use a 
 
 
mqsisetdbparms
 
 
command?
 
 
Methinks you might need some training perhaps? _________________ WMQ User since 1999
 
MQSI/WBI/WMB/'Thingy' User since 2002
 
Linux user since 1995
 
 
 
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:53 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| giridhararm wrote: | 
   
  
	mqsicvp MB8BROKER -n BSTREDB  
 
 
 
mqsicvp MB8BROKER  –n BSTREDB   –u db2admin –p db2admin | 
   
 
 
 
What were the results of these commands? If they worked you need an ODBC trace to work out what's wrong with the query the ESQL is using. If the first one didn't but the second one did you need an mqsisetdbparms command as well. I'll hazard a guess (if both worked) that it's one of the sample flows & the database you're using is incorrectly set up.
 
 
   
	| giridhararm wrote: | 
   
  
	| mqsiservice MB8BROKER  -r DataSourceName=BSTREDB | 
   
 
 
 
Why this? That could break something that was working. _________________ Honesty is the best policy.
 
Insanity is the best defence.
  Last edited by Vitor on Tue Feb 21, 2012 9:55 am; edited 1 time in total | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giridhararm | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:53 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 22 Apr 2009 Posts: 28
  
  | 
		  
		    
			  
				| yes i am learning on by own pls help me | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giridhararm | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 9:55 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 22 Apr 2009 Posts: 28
  
  | 
		  
		    
			  
				SWORD                      512 
 
		SWORD *             0x0012F0EC
 
 
mqsicvp MB8BROK a00-c18	EXIT  SQLErrorW  with return code 0 (SQL_SUCCESS)
 
		HENV                00000000
 
		HDBC                00C115E8
 
		HSTMT               00000000
 
		WCHAR *             0x0012ED48 (NYI) 
 
 		SDWORD *            0x0012F148 (0)
 
		WCHAR *             0x0012E948 [      91] "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
 
		SWORD                      512 
 
		SWORD *             0x0012F0EC (91) | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 10:02 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| giridhararm wrote: | 
   
  
	| yes i am learning on by own pls help me | 
   
 
 
 
That's a road filled with pain, suffering and misery. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 10:03 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| giridhararm wrote: | 
   
  
	| [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified" | 
   
 
 
 
That would appear to be the problem.
 
 
Check where & how you've defined the ODBC connection. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giridhararm | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 10:19 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 22 Apr 2009 Posts: 28
  
  | 
		  
		    
			  
				thks all 
 
 
i found it solved the issue its odbc problem | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | lancelotlinc | 
		  
		    
			  
				 Posted: Tue Feb 21, 2012 11:01 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA 
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |