DB2 Stop automatically invoked after ADM7009E

DB2 Stop automatically invoked after ADM7009E

 

  

We did not crash, but db2 database manager stopped automatically on us....
What would cause this? I hope there is a fix...The scenario appears to be

1. ADM7009E messages
2. THe database manager is stopped
3. More ADM7009E messages.

DB2Level Follows:
db2level
DB21085I Instance "db2inst1" uses "64" bits and DB2 code release
"SQL08022"
with level identifier "03030106".
Informational tokens are "DB2 v8.1.0.89", "OD_14086", "U800790_14086", and
FixPak "9".
Product is installed at "/opt/IBM/db2/V8.1".

Diag Log Follows. It goes in time ascending order:

2008-03-12-17.44.43.301387-240 E325196A421 LEVEL: Error
PID : 17185 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol
support.
A possible cause is that the maximum number of agents has been
exceeded.

2008-03-12-17.44.43.305096-240 I325618A386 LEVEL: Error
PID : 17185 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126
MESSAGE : Return code from sqleGetAgent =
DATA #1 : Hexdump, 4 bytes
0xFFFFFFFF7FFF8574 : FFFF E86C ...l

2008-03-12-17.44.43.599705-240 I326005A406 LEVEL: Event
PID : 7615 TID : 1 PROC : db2stop2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:230
DATA #1 : String, 49 bytes
Deactivate phase is completed, preparing to stop.
DATA #2 : Hexdump, 4 bytes
0xFFFFFFFF7FFFF750 : 0000 0001 ....

2008-03-12-17.44.43.604150-240 I326412A287 LEVEL: Event
PID : 7615 TID : 1 PROC : db2stop2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240
DATA #1 : String, 26 bytes
Stop phase is in progress.

2008-03-12-17.44.43.607764-240 I326700A302 LEVEL: Event
PID : 7615 TID : 1 PROC : db2stop2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250
DATA #1 : String, 41 bytes
Requesting system controller termination.

2008-03-12-17.44.44.530100-240 E327003A421 LEVEL: Error
PID : 17186 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol
support.
A possible cause is that the maximum number of agents has been
exceeded.

2008-03-12-17.44.44.539481-240 I327425A386 LEVEL: Error
PID : 17186 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126
MESSAGE : Return code from sqleGetAgent =
DATA #1 : Hexdump, 4 bytes
0xFFFFFFFF7FFF8574 : FFFF E86C ...l

2008-03-12-17.44.44.761642-240 E327812A421 LEVEL: Error
PID : 17186 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol
support.
A possible cause is that the maximum number of agents has been
exceeded.




"DANIEL CALLAHAN
"
<db2udbdba-ezmlms To
hield-x13562745.x "LazyDBA Discussion"
[Email Address Removed] <[Email address protected]
a.com> cc

03/06/2008 07:48 Subject
AM Re: -904 and -407 troubling










Is this a user package?

SQL0407N Assignment of a NULL value to a NOT NULL column
"<name>" is not allowed.

Explanation:

One of the following occurred:

o The update or insert value was NULL, but the object column
was declared as NOT NULL in the table definition.
Consequently:

- NULL values cannot be inserted into that column.

- An update cannot set values in that column to NULL.

- A SET transition-variable statement in a trigger cannot set
values in that column to NULL.

o The update or insert value was DEFAULT, but the object column
was declared as NOT NULL without WITH DEFAULT in the table
definition. Consequently:

- A default value of NULL cannot be inserted into that
column.

- An update cannot set default values of NULL in that column.

- A SET transition-variable statement in a trigger cannot set
default values of NULL in that column.

o The column name list for the INSERT statement omits a column
declared NOT NULL and without WITH DEFAULT in the table
definition.

o The view for the INSERT statement omits a column declared NOT
NULL and without WITH DEFAULT in the base table definition.

o An alter table statement attempted to alter the column with
SET NOT NULL, but the existing table data contained a row
with the NULL value.



If the value for "<name>" is of the form "TBSPACEID=n1,
TABLEID=n2, COLNO=n3", then the column name from the SQL
statement was not available when the error was issued. The values
provided identify the tablespace, table, and column number of the
base table that does not allow NULL value.

Federated system users: this situation can be detected by the
federated server or by the data source. Some data sources do not
provide the appropriate values for "<name>". In these cases the
message token will have the following format: "<data
source>:UNKNOWN", indicating that the actual value for the
specified data source is unknown.

The statement cannot be processed.

Note: Under some circumstances, the token "<name>" may not be
filled in (sqlerrmc field of the SQLCA not filled in).

User Response:

Correct the SQL statement after examining the object table
definition to determine which columns of the table have the NOT
NULL attribute and do not have the WITH DEFAULT attribute.

If the value for "<name>" is of the form "TBSPACEID=n1,
TABLEID=n2, COLNO=n3", you can determine the table name and
column name using the following query:


SELECT C.TABSCHEMA, C.TABNAME,
C.COLNAME
FROM SYSCAT.TABLES AS T,
SYSCAT.COLUMNS AS C
WHERE T.TBSPACEID = n1
AND T.TABLEID = n2
AND C.COLNO = n3
AND C.TABSCHEMA = T.TABSCHEMA
AND C.TABNAME = T.TABNAME


The table and column identified by this query may be the base
table of a view for which the SQL statement failed.

If the error is returned as part of an alter table statement,
when setting a column to NOT NULL, modify any row data for the
column that contains the NULL value, and retry the statement.

Federated system users: if the reason is unknown, isolate the
problem to the data source failing the request (see the problem
determination guide for procedures to follow to identify the
failing data source) and examine the object definition for that
data source. Remember that the defaults (NULL and NOT NULL) are
not necessarily the same between data sources.

sqlcode : -407

sqlstate : 23502


C:\Documents and Settings\Administrator>


































"Patel Santosh "
<db2udbdba-ezmlmshield-x33408101.[Email address protected]
03/06/2008 05:58 AM

To
"LazyDBA Discussion" <[Email address protected]
cc

Subject
-904 and -407 troubling






Hi Guru's,

When I am trying to execute one of my Job I am getting -904 error
message and the reason is REASON 00E30305, Type of resource - 00000801

After going through the details about the package which is some how
become Invalid, I tried REBIND on the same package, But again I am
getting an error message
SQLCODE = -407, SQLSTATE=23502.

Could some one suggest some thing on this ?????

Thanks,
Santosh


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html




---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html





This message is intended for the recipient only and is not meant to be forwarded or distributed in any other format. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument, or security, or as an official confirmation of any transaction. Putnam does not accept purchase or redemptions of securities, instructions, or authorizations that are sent via e-mail. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of Putnam Investments, LLC (DBA Putnam Investments) and its subsidiaries and affiliates. If you are not the intended recipient of this e-mail, please delete the e-mail.

DB2 & UDB email list listserv db2-l LazyDBA home page