Install and setup questions 
Author Message
 Install and setup questions

Subject: Install and setup questions

We are just beginning our first installation of DB2 7.1 on an NT
platform.  Two of us are working on this project -- one coming from an
Oracle NT background, the other from DB2-MVS.

We completed installation of the DBMS on the server and created the
SAMPLE database.  Next we installed the Admin Client on one of our
desktops.  The Control Center comes up, but is painfully slow in
responding to any user input.  Command Center won't come up at all.
When we start it we get the splash screen, then an outline of its
operating window, then everything just stops.  The NT Task Manager
shows it is running (as opposed to "not responding") but even after 10
or 15 minutes we're still waiting for it to finish initializing.

Something that may or may not be related . . .  before we installed
the DBMS on the server, we created a local user DB2INSTALL, put this
user in the local admin group, and gave him the following advanced
user rights:  
- Act as part of the operating system
- Create token object
- Increase quotas
- replace a process level token

We then logged on to the server as DB2INSTALL and ran the product
installation.  The only hiccup was a pop-up telling us that if we
needed OLE DB support we would need to install MS MDAC 2.5

When we installed the Admin Client on the desktop, we used our normal
domain logon, and did nothing with advanced user rights.

I know this isn't much to go on, but has anyone seen anything like
this before?

--
Ed Stevens
(Opinions expressed do not necessarily represent those of my employer.)



Sat, 23 Aug 2003 04:00:56 GMT
 Install and setup questions

Hi,
Seen it before, but don't know the exact cause.  One of my coworkers has
it, I don't.

I recommend you apply fixpack1 or fixpack 2.
One thing you would quickly discover is the Control Centre uses heaps of
memory.  If you are running your admin client on just 64 or 128M, I'd
recommend a RAM upgrade.

--greg

Quote:

> Subject: Install and setup questions

> We are just beginning our first installation of DB2 7.1 on an NT
> platform.  Two of us are working on this project -- one coming from an
> Oracle NT background, the other from DB2-MVS.

> We completed installation of the DBMS on the server and created the
> SAMPLE database.  Next we installed the Admin Client on one of our
> desktops.  The Control Center comes up, but is painfully slow in
> responding to any user input.  Command Center won't come up at all.
> When we start it we get the splash screen, then an outline of its
> operating window, then everything just stops.  The NT Task Manager
> shows it is running (as opposed to "not responding") but even after 10
> or 15 minutes we're still waiting for it to finish initializing.

> Something that may or may not be related . . .  before we installed
> the DBMS on the server, we created a local user DB2INSTALL, put this
> user in the local admin group, and gave him the following advanced
> user rights:
> - Act as part of the operating system
> - Create token object
> - Increase quotas
> - replace a process level token

> We then logged on to the server as DB2INSTALL and ran the product
> installation.  The only hiccup was a pop-up telling us that if we
> needed OLE DB support we would need to install MS MDAC 2.5

> When we installed the Admin Client on the desktop, we used our normal
> domain logon, and did nothing with advanced user rights.

> I know this isn't much to go on, but has anyone seen anything like
> this before?

> --
> Ed Stevens
> (Opinions expressed do not necessarily represent those of my employer.)



Sat, 23 Aug 2003 05:18:08 GMT
 Install and setup questions
Ed,

In terms of the performance of the control center, I agree that you must
have enough RAM. In addition, I also have seen the symptom you describe
with the command center. Although I have to tell you that I can't remember
exactly what the resolution was, it had something to do with corruption of
two files: db2tools.prf and db2cchis.prf. We renamed both, rebooted, and
were able to get the command center to work. I'd recommend opening up a PMR
though, with IBM support ... you shouldn't be modifying these files without
their guidance.

Also, there were some known problems with the command center, so I'd also
recommend application of fp2.

Quote:

> Subject: Install and setup questions

> We are just beginning our first installation of DB2 7.1 on an NT
> platform.  Two of us are working on this project -- one coming from an
> Oracle NT background, the other from DB2-MVS.

> We completed installation of the DBMS on the server and created the
> SAMPLE database.  Next we installed the Admin Client on one of our
> desktops.  The Control Center comes up, but is painfully slow in
> responding to any user input.  Command Center won't come up at all.
> When we start it we get the splash screen, then an outline of its
> operating window, then everything just stops.  The NT Task Manager
> shows it is running (as opposed to "not responding") but even after 10
> or 15 minutes we're still waiting for it to finish initializing.

> Something that may or may not be related . . .  before we installed
> the DBMS on the server, we created a local user DB2INSTALL, put this
> user in the local admin group, and gave him the following advanced
> user rights:
> - Act as part of the operating system
> - Create token object
> - Increase quotas
> - replace a process level token

> We then logged on to the server as DB2INSTALL and ran the product
> installation.  The only hiccup was a pop-up telling us that if we
> needed OLE DB support we would need to install MS MDAC 2.5

> When we installed the Admin Client on the desktop, we used our normal
> domain logon, and did nothing with advanced user rights.

> I know this isn't much to go on, but has anyone seen anything like
> this before?

> --
> Ed Stevens
> (Opinions expressed do not necessarily represent those of my employer.)



Sat, 23 Aug 2003 07:57:58 GMT
 Install and setup questions

Quote:

>Ed,

>In terms of the performance of the control center, I agree that you must
>have enough RAM. In addition, I also have seen the symptom you describe
>with the command center. Although I have to tell you that I can't remember
>exactly what the resolution was, it had something to do with corruption of
>two files: db2tools.prf and db2cchis.prf. We renamed both, rebooted, and
>were able to get the command center to work. I'd recommend opening up a PMR
>though, with IBM support ... you shouldn't be modifying these files without
>their guidance.

>Also, there were some known problems with the command center, so I'd also
>recommend application of fp2.

<snip>

Thanks for the leads.  We renamed the 2 .prf files and and Command
Center came up once.  We looked again at the 2 .prf files and saw that
db2tools.prf had a length of 0k bytes.  We deleted that one file and
again, Command Center came up once.

We're trying to track down a copy of fp2.

--
Ed Stevens
(Opinions expressed do not necessarily represent those of my employer.)



Sun, 24 Aug 2003 03:21:47 GMT
 Install and setup questions
First thing, the user name should not be greater than 8 chars long for the
installation.

(it is documented, i guess you missed this one.  "You can't use the user
Administrator")
You may have to change the user name that the service is using.

For naming conventions, refer to :
Installation and Configuration
Quick Beginnings
Appendix F. Naming Rules
Username, User ID, Group Name, and Instance Name Rules   (see also see
General Naming Rules. )
(On MVS, you may be limited to 5 instead of 8 chars)

Ensure the db2 services you need are running.
Services that look like : "DB2*"    (security, applet server, ...)

You may also have some networking stuff to do/correct

There may be other things

PM

Quote:

> Subject: Install and setup questions

> We are just beginning our first installation of DB2 7.1 on an NT
> platform.  Two of us are working on this project -- one coming from an
> Oracle NT background, the other from DB2-MVS.

> We completed installation of the DBMS on the server and created the
> SAMPLE database.  Next we installed the Admin Client on one of our
> desktops.  The Control Center comes up, but is painfully slow in
> responding to any user input.  Command Center won't come up at all.
> When we start it we get the splash screen, then an outline of its
> operating window, then everything just stops.  The NT Task Manager
> shows it is running (as opposed to "not responding") but even after 10
> or 15 minutes we're still waiting for it to finish initializing.

> Something that may or may not be related . . .  before we installed
> the DBMS on the server, we created a local user DB2INSTALL, put this
> user in the local admin group, and gave him the following advanced
> user rights:
> - Act as part of the operating system
> - Create token object
> - Increase quotas
> - replace a process level token

> We then logged on to the server as DB2INSTALL and ran the product
> installation.  The only hiccup was a pop-up telling us that if we
> needed OLE DB support we would need to install MS MDAC 2.5

> When we installed the Admin Client on the desktop, we used our normal
> domain logon, and did nothing with advanced user rights.

> I know this isn't much to go on, but has anyone seen anything like
> this before?

> --
> Ed Stevens
> (Opinions expressed do not necessarily represent those of my employer.)



Sat, 23 Aug 2003 13:53:58 GMT
 Install and setup questions
When you say the command center "came up once" do you mean that it wouldn't come
up when you tried it twice in a row?
Quote:


> >Ed,

> >In terms of the performance of the control center, I agree that you must
> >have enough RAM. In addition, I also have seen the symptom you describe
> >with the command center. Although I have to tell you that I can't remember
> >exactly what the resolution was, it had something to do with corruption of
> >two files: db2tools.prf and db2cchis.prf. We renamed both, rebooted, and
> >were able to get the command center to work. I'd recommend opening up a PMR
> >though, with IBM support ... you shouldn't be modifying these files without
> >their guidance.

> >Also, there were some known problems with the command center, so I'd also
> >recommend application of fp2.

> <snip>

> Thanks for the leads.  We renamed the 2 .prf files and and Command
> Center came up once.  We looked again at the 2 .prf files and saw that
> db2tools.prf had a length of 0k bytes.  We deleted that one file and
> again, Command Center came up once.

> We're trying to track down a copy of fp2.

> --
> Ed Stevens
> (Opinions expressed do not necessarily represent those of my employer.)



Sun, 24 Aug 2003 06:04:39 GMT
 Install and setup questions

Quote:

>When you say the command center "came up once" do you mean that it wouldn't come
>up when you tried it twice in a row?
><snip>

Yes, exactly. Here's the sequence:

1.  Delete db2tools.prf
2.  Launch Command Center.  It starts just fine.  
3.  Shut it down.  
4.  Launch Command Center;  we get the splash screen, then an outline
of a window for the Commnad Center, then it just hangs.
5.  Use task manager to kill it.
6.  Delete db2tools.prf.  
7.  Launch Command Center and it comes up fine.
8.  Shut it down.  
9.  Note that db2tools.prf has a length of 0k.  
10.  Predict that Command Center won't start.  
11.  Go to step 4.
--
Ed Stevens
(Opinions expressed do not necessarily represent those of my employer.)



Mon, 25 Aug 2003 00:04:23 GMT
 Install and setup questions
Suggest you report this to IBM service. Sorry I can't help more.
Quote:


> >When you say the command center "came up once" do you mean that it wouldn't come
> >up when you tried it twice in a row?
> ><snip>

> Yes, exactly. Here's the sequence:

> 1.  Delete db2tools.prf
> 2.  Launch Command Center.  It starts just fine.
> 3.  Shut it down.
> 4.  Launch Command Center;  we get the splash screen, then an outline
> of a window for the Commnad Center, then it just hangs.
> 5.  Use task manager to kill it.
> 6.  Delete db2tools.prf.
> 7.  Launch Command Center and it comes up fine.
> 8.  Shut it down.
> 9.  Note that db2tools.prf has a length of 0k.
> 10.  Predict that Command Center won't start.
> 11.  Go to step 4.
> --
> Ed Stevens
> (Opinions expressed do not necessarily represent those of my employer.)



Mon, 25 Aug 2003 03:54:41 GMT
 Install and setup questions
Fix Pack 2 fixed this problem for us.  Took us a while to find the FP,
took even longer to get it downloaded.  The zip file on the FTP site
was about 147mb and our downloads kept{*filter*} and timing out at about
140mb.  Finally got a clean download, unzipped it, applied the FP to
the server and the client machines, and all is well.  

Thanks for pointing us to the FP.

Quote:

>Suggest you report this to IBM service. Sorry I can't help more.



>> >When you say the command center "came up once" do you mean that it wouldn't come
>> >up when you tried it twice in a row?
>> ><snip>

>> Yes, exactly. Here's the sequence:

>> 1.  Delete db2tools.prf
>> 2.  Launch Command Center.  It starts just fine.
>> 3.  Shut it down.
>> 4.  Launch Command Center;  we get the splash screen, then an outline
>> of a window for the Commnad Center, then it just hangs.
>> 5.  Use task manager to kill it.
>> 6.  Delete db2tools.prf.
>> 7.  Launch Command Center and it comes up fine.
>> 8.  Shut it down.
>> 9.  Note that db2tools.prf has a length of 0k.
>> 10.  Predict that Command Center won't start.
>> 11.  Go to step 4.
>> --
>> Ed Stevens
>> (Opinions expressed do not necessarily represent those of my employer.)

--
Ed Stevens
(Opinions expressed do not necessarily represent those of my employer.)


Mon, 25 Aug 2003 21:22:02 GMT
 
 [ 9 post ] 

 Relevant Pages 

1. Setup & Install Question

2. Install - Re-install question

3. Need help to install and setup MS SQL Server 6.5

4. error 703 when install with setup.iss

5. please help - setup.exe won't install - i have the error log - thanks

6. Setup MSDE or SQL7 in a PC without network card installed

7. SQL Server 6.5 Setup does not install Network protocols correctly

8. SQL setup stops responding during install!

9. MSDE Installed by our Setup causing Event Warnings

10. SQL Server 2000 Setup Terminates Unexpectedly if You Install Chinese (Hong Kong)

11. Destop Setup Freezes when installing SQL 7.0 on Windows 98

12. Setup Fails to Install


 
Powered by phpBB® Forum Software