I'm following the "Quick Beginnings" manual and trying to verify the
installation, but am running into the following error messages:
[root@lab1:/root]$ /usr/IBMdb2/V6.1/bin/db2 connect to sample
SQL10007N Message "-1390" could not be retrieved. Reason code: "5".
...checking to see if the database itself is created by trying to create
it again:
[root@lab1:/root]$ /usr/IBMdb2/V6.1/bin/db2 db2sampl
SQL10007N Message "-1390" could not be retrieved. Reason code: "5".
The instructions on page 24 of the PDF (letter format) "Quick
Beginnings" guide refer to starting the database with the "db2start"
command. "db2 db2start" doesn't appear to work, and there is no
instance of a "db2start" executable on my search path or under the
/usr/IBMdb2/ installation tree.
- Am I missing something? If so, what?
- How is this command invoked -- from the command line as "db2start",
or with a DB2 system prefix such as "db2 db2start".
TIA.
--
Karsten M. Self (kms...@ix.netcom.com)
What part of "Gestalt" don't you understand?
Scope out Scoop: http://scoop.kuro5hin.org/
Nothin' rusty about Kuro5hin: http://www.kuro5hin.org/
Followup to Self.
Ok, logging in as db2inst1, I've got "db2start" to work as:
[db2inst1@lab1:db2inst1]$ db2 db2start
DB20000I The DB2START command completed successfully.
However:
[db2inst1@lab1:db2inst1]$ db2 db2sampl
DB21034E The command was processed as an SQL statement because it
was not a valid Command Line Processor command. During SQL processing
it returned:
SQL1024N A database connection does not exist. SQLSTATE=08003
[db2inst1@lab1:db2inst1]$ db2 connect to db2sampl
SQL1031N The database directory cannot be found on the indicated
file system.
SQLSTATE=58031
...what now?
kar...@ix.netcom.com wrote:
> I've just installed db2 V6.1 for Linux on an intel RedHat 6.1 box.
>
> I'm following the "Quick Beginnings" manual and trying to verify the
> installation, but am running into the following error messages:
>
> [root@lab1:/root]$ /usr/IBMdb2/V6.1/bin/db2 connect to sample
> SQL10007N Message "-1390" could not be retrieved. Reason code: "5".
>
> ...checking to see if the database itself is created by trying to create
> it again:
>
> [root@lab1:/root]$ /usr/IBMdb2/V6.1/bin/db2 db2sampl
> SQL10007N Message "-1390" could not be retrieved. Reason code: "5".
>
> The instructions on page 24 of the PDF (letter format) "Quick
> Beginnings" guide refer to starting the database with the "db2start"
> command. "db2 db2start" doesn't appear to work, and there is no
> instance of a "db2start" executable on my search path or under the
> /usr/IBMdb2/ installation tree.
>
> - Am I missing something? If so, what?
>
> - How is this command invoked -- from the command line as "db2start",
> or with a DB2 system prefix such as "db2 db2start".
>
> TIA.
>
> You are messing up commands executed by the db2 command line processor
> and plain executables.
I thought I might be. However this isn't clearly differentiated in the
documentation, though it's referenced. In particular the direction:
Log on to the system as a user with System Administrative
(SYSADM) authority. For more information, see <Working with the
System Administrative Group> on page 33.
...where it is entirely unclear whether the "system" is the OS or DB2,
and whether SYSADM is root user, or equivalent, or a DB2 administrative
account.
The instructions on page 33 don't help much:
By default, System Administrative (SYSADM) authority is granted
to any valid DB2 username that belongs to the primary group of the
instance owner's username.
For information on how to change the default SYSADM settings and
how to assign this authority to a different user or set of users,
refer to the Administration Guide.
...though this seems to refer to DB2 users rather than OS users.
[Both citations refer to "Quick Beginnings", Version 6, IBM DB2
Universal Database Personal Edition for Linux, PDF, US letter format].
> If you enter db2sampl it will create the sample db, it isn't created yet.
> Chapter 1 of The Command Reference describes the system commands (
> db2sampl etc.), chapter 3 contains descriptions about the CLP commands.
Again, there is no executable 'db2sampl' I can find on my installation
using OS system search tools ("locate" and "find"). Where it its default
installed location under Linux?
> Hope this helps,
> Gert van der Kooij
Hi,
On NT 'db2sampl.exe' is in the bin directory which is in the install
directory. If you can't find it on your system db2 isn't completely
installed.
About users etc.
On AIX (with db2 version 2) I had to install db2 with user root, create
an AIX user (8 or less characters) in a group (also 8 or less characters)
and use the 'db2icrt' command to create an instance with the same name as
the just created AIX user, which becomes the instance owner. The group
this user belonges to is automatically assigned the SYSADM authority,
which is a db2 authorization level.
( Check the Administration Guide (chapter 6) for a complete description
of db2 security)
After that you can su to the instance user, check to see if the
db2profile is executed in your .profile and create the sample database.
But don't forget what Blair mentioned in his reply, download at least
fixpack 2 before creating an instance and creating the sample db.
[...]
>> > You are messing up commands executed by the db2 command line processor
>> > and plain executables.
>>
>> I thought I might be. However this isn't clearly differentiated in the
>> documentation, though it's referenced. In particular the direction:
>>
>> Log on to the system as a user with System Administrative
>> (SYSADM) authority. For more information, see <Working with the
>> System Administrative Group> on page 33.
>>
>> ...where it is entirely unclear whether the "system" is the OS or DB2,
>> and whether SYSADM is root user, or equivalent, or a DB2 administrative
>> account.
>>
>> The instructions on page 33 don't help much:
>>
>> By default, System Administrative (SYSADM) authority is granted
>> to any valid DB2 username that belongs to the primary group of the
>> instance owner's username.
>>
> Hi,
> On NT 'db2sampl.exe' is in the bin directory which is in the install
> directory. If you can't find it on your system db2 isn't completely
> installed.
I'm running Linux, noted above.
> About users etc.
> On AIX (with db2 version 2) I had to install db2 with user root, create
> an AIX user (8 or less characters) in a group (also 8 or less characters)
> and use the 'db2icrt' command to create an instance with the same name as
> the just created AIX user, which becomes the instance owner. The group
> this user belonges to is automatically assigned the SYSADM authority,
> which is a db2 authorization level.
> ( Check the Administration Guide (chapter 6) for a complete description
> of db2 security)
> After that you can su to the instance user, check to see if the
> db2profile is executed in your .profile and create the sample database.
> But don't forget what Blair mentioned in his reply, download at least
> fixpack 2 before creating an instance and creating the sample db.
Where can I find this? Searching "db2 fixpack" turned up references to
fixpack 3 but not 2. Are these inclusive?
I'm thinking of re-doing the installation yet again to try to get it
clean.
> Hope this helps,
> Gert van der Kooij
--
>Gert van der Kooij <ge...@wanadoo.nl> wrote:
>> In article <metua8...@nntp.ix.netcom.com>, kar...@ix.netcom.com
>> says...
>>> kar...@ix.netcom.com wrote:
>>> > I've just installed db2 V6.1 for Linux on an intel RedHat 6.1 box.
>>>
>>> Followup to Self.
>>>
>>> Ok, logging in as db2inst1, I've got "db2start" to work as:
>>>
>>> [db2inst1@lab1:db2inst1]$ db2 db2start
>>> DB20000I The DB2START command completed successfully.
As pointed out, 'db2start' is also a command in and of itself.
>I thought I might be. However this isn't clearly differentiated in the
>documentation, though it's referenced. In particular the direction:
>
> Log on to the system as a user with System Administrative
> (SYSADM) authority. For more information, see <Working with the
> System Administrative Group> on page 33.
>
>....where it is entirely unclear whether the "system" is the OS or DB2,
>and whether SYSADM is root user, or equivalent, or a DB2 administrative
>account.
Logging on to the system and to DB2 are one in the same. "Log on" usually
connotes "authenticate with". Which means answering the "Login:" prompt of
your OS. DB2 merely uses the OS's authentication, thus making them the same
- the only way to authenticate with DB2 is to authenticate with the OS.
>The instructions on page 33 don't help much:
>
> By default, System Administrative (SYSADM) authority is granted
> to any valid DB2 username that belongs to the primary group of the
> instance owner's username.
>
> For information on how to change the default SYSADM settings and
> how to assign this authority to a different user or set of users,
> refer to the Administration Guide.
>
>....though this seems to refer to DB2 users rather than OS users.
Both DB2 users and OS users are the same thing.
>[Both citations refer to "Quick Beginnings", Version 6, IBM DB2
>Universal Database Personal Edition for Linux, PDF, US letter format].
>
>> If you enter db2sampl it will create the sample db, it isn't created yet.
>> Chapter 1 of The Command Reference describes the system commands (
>> db2sampl etc.), chapter 3 contains descriptions about the CLP commands.
>
>Again, there is no executable 'db2sampl' I can find on my installation
>using OS system search tools ("locate" and "find"). Where it its default
>installed location under Linux?
~db2inst1/sqllib/bin or ~db2inst1/sqllib/adm. For db2sampl and db2 (the
CLP), these are both in ~db2inst1/sqllib/bin. If you installed them at all.
(You always have to have db2, but may not have db2sampl since it's part of
the engine, not the base client.)
If 'rpm -q db2engn61' does not return 'package db2engn61 is not installed',
then you should have db2sampl. It's properly located in
/usr/IBMdb2/V6.1/bin, but this whole directory is linked from
~<inst>/sqllib/bin (the latter is the link, of course). If you're in your
instance, PATH should include the sqllib/bin and sqllib/adm directories. (If
not, source sqllib/db2profile or sqllib/db2cshrc, depending on your shell.)
HTH
Ok, I'm attempting a clean reinstallation. The installer has been
hanging for the past hour or so with a dialog similar to:
| | -------------------+--- Configuring... -------+ | |
| | | | | |
| | Fenced User | DB2 Sample Database | | |
| | | | | |
| | Create new user n| [ Cancel ] | | |
| | User Name +--------------------------+ db2fenc1 | |
Any idea what gives?
>Where can I find this? Searching "db2 fixpack" turned up references to
>fixpack 3 but not 2. Are these inclusive?
Yes. Fixpak n includes everything in fixpak n-1 which includes everything in
fixpak n-2 which ... (There are exceptions, but so far I only know of fixpak
6 on version 5 being a new baseline for fixpaks since that's the level of
code for version 5.2. I really highly doubt v6 will have any such issues.)
>kar...@ix.netcom.com wrote:
>> I've just installed db2 V6.1 for Linux on an intel RedHat 6.1 box.
>
>Ok, I'm attempting a clean reinstallation. The installer has been
>hanging for the past hour or so with a dialog similar to:
Yup - you need to:
A) Install without creating instances
B) Download and apply fixpak 2 or higher
After this, you can create your instances. You may use db2setup
(/usr/IBMdb2/V6.1/install/db2setup) if you wish (I generally try to stick to
db2setup when creating instances myself).
I've got a successful install of DB2. It has been verified
with the following commands. Log in as or su to root initially.
[root@lab1:/root]$ su - db2inst1
[db2inst1@lab1:db2inst1]$ db2 connect to sample
Database Connection Information
Database server = DB2/LINUX 6.1.0
SQL authorization ID = DB2INST1
Local database alias = SAMPLE
[db2inst1@lab1:db2inst1]$ db2 "select * from staff where dept = 20"
ID NAME DEPT JOB YEARS SALARY COMM
------ --------- ------ ----- ------ --------- ---------
10 Sanders 20 Mgr 7 18357.50 -
20 Pernal 20 Sales 8 18171.25 612.45
80 James 20 Clerk - 13504.60 128.20
190 Sneider 20 Clerk 8 14252.75 126.50
4 record(s) selected.
[db2inst1@lab1:db2inst1]$
:-)
The installation sequence, abbreviated, is as follows, on RH 6.1, using
a DB2 Universal Database Personal Edition for Linux CD-ROM distribution:
- Install the pdksh RPM from an appropriate source. This supplies the
public domain Korn shell, required by DB2 and the DB2 installer. A
source is:
Server: ftp.varesearch.com
Path: /pub/mirrors/redhat/redhat/current/i386/RedHat/RPMS/
File: pdksh-5.2.14-1.i386.rpm
- Obtain the Red Hat DB2 patches, required for RH 6.1.
Server: ftp.software.ibm.com
Path: /ps/products/db2/fixes/english-us/db2linuxv61/FP3_IP21905/
File: IP21905/IP21905.tar
- Install and mount the distribution CD-ROM. Default location is
/mnt/cdrom.
- Install the RH 6.1 patches, obtained above.
- Following instructions in the RH 6.1 patches, change to the /tmp/fixdb2
or appropriate directory, and complete the installation with
./db2setup. In the products screen, select "DB2 Administration
Client" and "DB2 UDB Personal Edition", generally following the
instructions in either Paul Zikopoulous's _Linux Journal_ article
"IBM's Universal Database", or the "Quick Beginnings" guide for Linux.
Select all of the optional configuration options (Java Support,
Replication, Control Center). I did not select any options under
"DB2 Product Messages" or "DB2 Product Library".
Do *NOT* create the sample database yet.
- Install fixpack 2, following all setup, installation, and
post-installation steps carefully.
- Create your sample DB and test it, as per directions in Zikopoulos's
article or the "Quick Beginnings" manual. Test results should appear
as above.
networking up and running, but the DB should support local host
connections for the moment.