| Author |
Message
|
| demarial |
 Posted: Wed Jun 01, 2005 3:42 am Post subject: |
 |
|
Newbie
Joined: 31 May 2005
Posts: 9
|
| No, I can not. If I try to select the BDBT database, I get an error FMC33920E telling me to check the @fmczbt.log. This log has no additional information from what I displayed earlier. |
|
| Back to top |
|
 |
| kotha |
| Posted: Wed Jun 01, 2005 5:08 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| Try creating another buildtime configuration. Give the buildtime database name different than you used before. Let us see what happens. If the new configuration buildtime working gud then something wrong with your old configuration. Do some reverse engineering. |
|
| Back to top |
|
|
| demarial |
| Posted: Wed Jun 01, 2005 5:42 am Post subject: |
|
|
Newbie
Joined: 31 May 2005
Posts: 9
|
Same error when creating MQWF buildtime environment.
@fmczbt.log
6/1/2005 9:38:13 AM FMC33110I The database manager is already active.
6/1/2005 9:38:14 AM FMC33115I Creating the database - MQWF
6/1/2005 9:38:14 AM FMC33116I Please wait... This may take a while.
6/1/2005 9:40:07 AM FMC33118I Database MQWF has been created on node DB2.
6/1/2005 9:40:07 AM FMC33120I Updating the database configuration.
6/1/2005 9:40:07 AM FMC33003I SQL1482W The BUFFPAGE parameter will only be used if one of the buffer pools
is defined with a size of -1.
6/1/2005 9:40:11 AM FMC33124I Creating a tablespace that is managed by system.
6/1/2005 9:40:11 AM FMC33125I Creating a table that is managed by system.
6/1/2005 9:41:22 AM FMC33140I Setup of DB2 completed successfully. |
|
| Back to top |
|
|
| kotha |
| Posted: Wed Jun 01, 2005 5:52 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
If it urgent requirement, try uninstall from the exisitng folder and install in different folder. and make sure you follow the guidlines given the documentation and also do the following:
After uninstalling, check wether the Workflow folder is still there. If it is, delete it.
delete the DBs created by workflow in the database. |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Jun 01, 2005 6:36 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Did you try using MSAccess Like I suggested above?
If that works this is some type of a DB2 issue, if you have the same problem with Access, then it is something in MQWF config.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| demarial |
| Posted: Wed Jun 01, 2005 11:17 am Post subject: |
|
|
Newbie
Joined: 31 May 2005
Posts: 9
|
I tried using MS Access, but received the same error message. The only difference, nothing was written to the log even though the error message said to check the @fmczbt.log.
I uninstalled the MQWF application and re-installed. Same issues. There is nothing in my event logs to indicate any issues either. I was hoping that someone else had the same issue and was able to resolve it. |
|
| Back to top |
|
|
| kotha |
| Posted: Wed Jun 01, 2005 11:26 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| demarial wrote: |
| I uninstalled the MQWF application and re-installed. Same issues. There is nothing in my event logs to indicate any issues either. I was hoping that someone else had the same issue and was able to resolve it. |
That is strange!!!. I had issues when I installed but solved somehow. I think you need some expert advise. meanwhile check the logfiles and read the documentation. youmight get an idea.
Better luck |
|
| Back to top |
|
|
| demarial |
| Posted: Tue Jun 28, 2005 9:37 am Post subject: error while configuring buildtime |
|
|
Newbie
Joined: 31 May 2005
Posts: 9
|
I have resolved the issue of not being able to create the buildtime environment.
I ran a trace using the following commands:
1. fmczchk -c inst:m,FMC_SIMPLE_TRACE_ONLY,YES -y<Cfgd>
2. fmczchk -dc trc:99 -y<Config id>
3. Stop workflow executable/script
4. Re-start workflow executable/script
5. Recreate problem.
6. fmczchk -c inst:m,FMC_SIMPLE_TRACE_ONLY,-y<Cfg id>
7. fmczchk -c trc:0 -y<Config id>
8. Stop the workflow executable/script
9. Restart the workflow executable/script
10. Send the fmctrc.log file to us for analysis
(fmctrc.log is the default trace file name)
After reviewing the trace, I found that the Registration of ODBC Data Source failed.
It turned out that I had a corrupt DB2CLI.DLL and I could not use the IBM DB2 ODBC DRIVER.
To resolve, I uninstalled DB2 and MQ WF. Manually cleaned up remaining registry entries and files which were not removed during the uninstall.
After reinstalling DB2, I validated that I could register an ODBC data source manually and that the correct driver was registered.
All is well now and I am happily creating workflows using my buildtime environment. |
|
| Back to top |
|
|
|
|
