| Author |
Message
|
| vennela |
 Posted: Wed Dec 15, 2004 10:09 am Post subject: [SOLVED]Creating buildtime database on AIX MQWF 3.5 |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Has anyone been successful in creating the buildtime DB on AIX (for that matter any of the UNIX/LINUX platforms).
I tried creating it using both the GUI and fmczutil and it doesn't work.
This is the error I am getting
FMC33920E Error occurred
Thanks |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed Dec 15, 2004 12:08 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Vennela:
You might want to turn on the full trace and have a look and see if there are any hints you can pick up in the trace file. We had a real devil of a time with a Remote Runtime DB install, and it had to do with having a bad entry in I believe the db2 configuration. There was an database entry for the db2 instance that had no name, or some such, I was not directly involved. But we did get the big hint to solve the problem when we ran fmczutil with the full trace on.
I know it's not Buildtime, but maybe this will help.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Dec 15, 2004 1:40 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I tried the full tracing on ans this is where it is failing
| Code: |
| fmcbdcdb -yFMC1 -c"/var/fmc/bt_db/db2inst1/FMCBTDB" -dFMCBTDB -elocal7 -ms -l"/var/fmc/bt_db/db2inst1/FMCBTDB" -o=ca -t2 -udb2inst8 -p******** rc = 191 |
John:
I remember you mentioning that you will create BTDB's with just the bootstrap. If I am not wrong, you will be using the above command to do that right.
How do you do it.
Create database first and use the above utility to create tabalspaces and tables?
Or create the DB also using the utility? |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Dec 15, 2004 2:36 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Vennela:
What I do all the time is create MS Access BTDB's. I may have mentioned the bootstrap FDL before, but I have never created the database myself.
However, what I would guess is that upon successful completion of the command you are failing on, what would happen next is the import of the bootstrap db.
What I want to know is what is the rc=191? I have looked though all of my notes and can not find any such error. Have you had a look at the db2diag.log file? If the database is remote, I would look at both the Local and Remote locations to see if there is any hint in that log file.
Sorry to not be of more help.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Dec 15, 2004 2:53 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
No hint in the db2diag.log anywhere (on the client and server)
It is not creating the database in the first place. |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Dec 15, 2004 3:06 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
The only other thing I can think of, is there are 3 or 4 commands that you have to run prior to running fmczutil when you install on unix (at least for runtime). The command fmczddba sticks in my head, and I think there are 2 or 3 others, that do something with the MQWF profile or some such.
I don't really do a lot of installs on UNIX, I only get involved after the fact, so the above information may be useless. 
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Dec 15, 2004 3:11 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| The command fmczddba sticks in my head |
That I believe is for authorizations that are to be granted for the workflow admin on runtime DB.
Most of the other stuff is for AIX only kind.
I have had no problem with 3.3.2 or 3.4. It is only giving a problem with 3.5 |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Dec 15, 2004 3:17 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Vennela:
I did not understand that this was a 3.5 only issue.... I would definitely open a PMR on this, since you can proove that it works on 3.4.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Dec 15, 2004 4:21 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I already did
I did that a week back.
I think I have to change the severity |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Dec 16, 2004 5:44 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I am not sure if it helps.
I think it may be related to authorizations.
My build time is installed on my local Win200 machine, whenever I had to connect, I used to logoff from Network and logon with my local ID. I have added my Network ID to have database authorizations and now I can connect to my local database without having to logon using my local ID. |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Dec 16, 2004 12:09 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
It turned out to be a problem with DB2 client version. I was using DB2 Client 7.2 and DB2 Server 8.2.
Once I had the same versions of client and server I was able to create the database.
However, now that I have the database created, I could use DB2 7.2 client to talk to the remote buildtime DB at 8.2 and use the buildtime with no problems. |
|
| Back to top |
|
|
|
|
