| Author | 
		  Message
		 | 
		
		  | Duschwolf | 
		  
		    
			  
				 Posted: Fri May 03, 2002 2:18 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 01 May 2002 Posts: 15
  
  | 
		  
		    
			  
				I've got a problem with the Configuration of MQ Workflow (Win2000, Stand alone 
 
server). 
 
After installing DB2, MQSeries and MQSeries Workflow like described in the Installation Guide) without any problems, the Configuration Tool creates the Runtime database. At the attempt to create the Buildtime Database I get a message, that the Database was created successful but hasn't been integrated into the LDAP directory. In the logfile there I get the error message "SQL3274", and "SQL3282". 
 
The user data is correct. 
 
I hope anyone can help me, greetings from Germany. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | vedbhat | 
		  
		    
			  
				 Posted: Sun May 05, 2002 6:09 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 19 Mar 2002 Posts: 186 Location: Singapore 
  | 
		  
		    
			  
				Hi,
 
 
1) Looking at the SQL Code SQL3274 - It looks like the database is not catalogued in LDAP. Use "db2 Catalog database ..." command. For more information refer to db2 information Center.
 
 
2) SQL code SQL3282 - User credentials not correct. Please check the Userid and Password. Note - Password is case sensitive.
 
 
Cheers
 
Ved
 
 
_________________
 
IBM Certified Solutions Expert - MQSeries Workflow
 
 
[ This Message was edited by: vedbhat on 2002-05-05 22:09 ] | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Duschwolf | 
		  
		    
			  
				 Posted: Tue May 07, 2002 3:12 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 01 May 2002 Posts: 15
  
  | 
		  
		    
			  
				I've tried to catalogue the database with this command,
 
but it failed.
 
I get the message SQL1005N - the alias of my database
 
is already present.
 
My Userdata is 100% correct, so I don't know why this 
 
happens, because I've installed Workflow before without
 
any problems. This time I've failed already the third time. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Duschwolf | 
		  
		    
			  
				 Posted: Tue May 07, 2002 3:13 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 01 May 2002 Posts: 15
  
  | 
		  
		    
			  
				In DB2 "Client Configuration", I can see the databases I've tried
 
to configure with Workflow, but they haven't got an 
 
ODBC-Name because they aren't registered.
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | vedbhat | 
		  
		    
			  
				 Posted: Tue May 07, 2002 5:39 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 19 Mar 2002 Posts: 186 Location: Singapore 
  | 
		  
		    
			  
				Hi,
 
 
Inorder to register the database, From Client Configuration Assistant click Properties. This will open a Database Register window.
 
 
Check the box saying Register this database for ODBC and click OK.
 
 
This should register your database.
 
 
I guess it is not the problem with Register, Please check the "db2 catalog databse <DatabaseName>" command. There is something wrong with the catalog. Once you catalog trying testing the connection from the Client Configuration Assistant
 
or
 
From the MQWF COnfiguration utility, Remove the configuration with data and re-create again.
 
 
Cheers
 
Ved
 
 
 _________________ IBM Certified Solutions Expert - MQSeries Workflow
 
IBM Certified Specialist - MQSeries | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | murli | 
		  
		    
			  
				 Posted: Wed Jun 19, 2002 9:49 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Newbie
 
 Joined: 19 Jun 2002 Posts: 1
  
  | 
		  
		    
			  
				set 
 
 
the parameter 
 
 
DB2_ENABLE_LDAP as NO.
 
 
For this go to the command prompt and do
 
 
C:\>DB2SET DB2_ENABLE_LDAP=NO
 
 
This should work out | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |