DB2 fails

nelapsi · #1 (**permalink**) 12-10-04, 07:59

preambula %)

Quote:

[db2inst1@nelapsi sql]$ db2level
DB21085I Instance "db2inst1" uses DB2 code release "SQL07020" with level
identifier "03010105" and informational tokens "DB2 v7.1.0.40", "s010415" and
"U475381".

[db2inst1@nelapsi sql]$ db2licm -l
Product Name = "DB2 Enterprise Edition"
Product Password = "DB2UDBEE"
Version Information = "7.2"
Expiry Date = "Permanent"
Concurrent Connect User Policy = "Disabled"
Registered Connect User Policy = "Disabled"
Enforcement Policy = "Soft Stop"
Number of processors = "1"
Number of licensed processors = "1"
Annotation = ""
Other information = ""

Product Name = "DB2 Connect Enterprise Edition"
Product Password = "DB2CONEE"
Version Information = "7.2"
Expiry Date = "Expired"
Measured usage license policy = "Disabled"
Concurrent Connect User Policy = "Disabled"
Registered Connect User Policy = "Disabled"
Enforcement Policy = "Soft Stop"
Annotation = ""
Other information = ""

[db2inst1@nelapsi sql]$ db2start
SQL8008N The product "DB2 Connect Enterprise Edition" does not have a valid
license key installed and the evaluation period has expired. Functions
specific to this product are not enabled.
SQL1063N DB2START processing was successful.

problem :

Quote:

[db2inst1@nelapsi sql]$ db2
(c) Copyright IBM Corporation 1993,2001
Command Line Processor for DB2 SDK 7.2.0

You can issue database manager commands and SQL statements from the command
prompt. For example:
db2 => connect to sample
db2 => bind sample.bnd

For general help, type: ?.
For command help, type: ? command, where command can be
the first few keywords of a database manager command. For example:
? CATALOG DATABASE for help on the CATALOG DATABASE command
? CATALOG for help on all of the CATALOG commands.

To exit db2 interactive mode, type QUIT at the command prompt. Outside
interactive mode, all commands must be prefixed with 'db2'.
To list the current command option settings, type LIST COMMAND OPTIONS.

For more detailed help, refer to the Online Reference Manual.

db2 => connect to test

Database Connection Information

Database server = DB2/LINUX 7.2.0
SQL authorization ID = DB2INST1
Local database alias = TEST

db2 => create sequence seq2
DB20000I The SQL command completed successfully.
db2 => values(nextval for seq2)

1
-----------
1

1 record(s) selected.

SQL1224N A database agent could not be started to service a request, or was
terminated as a result of a database system shutdown or a force command.
SQLSTATE=55032

after this i need to run db2start again to connect to DB
somebody know, why it fails?

J Petruk · #2 (**permalink**) 12-10-04, 09:55

You have two different problems there... the licensing problem is the easiest, you've installed the DB2 Connect component which requires a license. Either remove it or install a license.

The second problem, you'll need to check the db2diag.log to see what's going on, but often when the instance is crashing it's going to require IBM support to diagnose. You're not doing anything wrong from what I can see, seems to be a db2 bug (most likely).

nelapsi · #3 (**permalink**) 12-10-04, 10:06

Quote:

Originally Posted by J Petruk

You have two different problems there... the licensing problem is the easiest, you've installed the DB2 Connect component which requires a license. Either remove it or install a license.

The second problem, you'll need to check the db2diag.log to see what's going on, but often when the instance is crashing it's going to require IBM support to diagnose. You're not doing anything wrong from what I can see, seems to be a db2 bug (most likely).

where can i find this "db2diag.log" :?
If I'll uninstall DB2 Connect - can I use unixODBC after this?

J Petruk · #4 (**permalink**) 12-10-04, 10:15

Quote:

Originally Posted by nelapsi

where can i find this "db2diag.log" :?
If I'll uninstall DB2 Connect - can I use unixODBC after this?

db2diag.log will be in sqllib/db2dump in the instance owner's home directory.

DB2 Connect is for host connectivity, ie. mainframes or AS400. If you're not connecting to those kind of systems you don't need it.

nelapsi · #5 (**permalink**) 12-10-04, 14:35

Quote:

Originally Posted by J Petruk

db2diag.log will be in sqllib/db2dump in the instance owner's home directory.

DB2 Connect is for host connectivity, ie. mainframes or AS400. If you're not connecting to those kind of systems you don't need it.

Tnx...
I'll look this at next monday

nelapsi · #6 (**permalink**) 12-10-04, 14:49

Quote:

Originally Posted by J Petruk

db2diag.log will be in sqllib/db2dump in the instance owner's home directory.

DB2 Connect is for host connectivity, ie. mainframes or AS400. If you're not connecting to those kind of systems you don't need it.

Tnx...
I'll look this at next monday

Internet Services

Web Development

Digital Marketing

Consumer Tech