View Single Post

   
  #2 (permalink)  
Old 02-26-2008, 06:20 PM
JS
 
Posts: n/a
Default Re: SQL22205C - DAS problems

udbguru@netscape.net (SEH) wrote in message news:<32dea954.0406091030.47428f90@posting.google. com>...
> I have (2) 8.1 (fp5) Linux installs.
> Both are almost exactly the same, with the same DB installed.
> I have an XP client running admclt fp5
>
> One machine works fine using the Control Center & Rep. Center.
>
> The other machine keeps giving me an SQL22205C when I do things that
> seem to interact with the DAS, (doing a "discovery" operation does it
> every time.
>
> I have dropped the DB, and the DAS instance multiple times.
>
> When I look in the db2dasdiag.log I see:
>
> ---------------
> 2004-06-09-10.59.07.912496 pid:28400 tid:303111 level:2
> DB2 tools - DB2 administration server - db2dasGetInstanceInfo()
> probe:10
> data #1 (77 bytes)
> Warning: DB2 instance db2sds is not enabled for DAS multiple release
> support.
>
> 2004-06-09-10.59.08.151369 pid:28402 tid:1024 level:2
> DB2 tools - DB2 administration server - dasCoreStmLauncher_main()
> probe:60
> data #1 (66 bytes)
> Error: db2dasstml encountered an internal error. Error code -7033.
>
> 2004-06-09-10.59.08.253181 pid:28400 tid:303111 level:2
> DB2 tools - DB2 administration server - createSession() probe:30
> data #1 (4 bytes)
> 0
>
> 2004-06-09-10.59.08.253453 pid:28400 tid:303111 level:2
> DB2 tools - DB2 administration server - handleStmRequest() probe:90
> data #1 (4 bytes)
> -4010
>
> 2004-06-09-10.59.08.253491 pid:28400 tid:303111 level:2
> DB2 tools - DB2 administration server - handleStmRequest() probe:150
> data #1 (4 bytes)
> -4010
>
> 2004-06-09-10.59.08.253952 pid:28399 tid:4098 level:2
> DB2 tools - DB2 administration server - db2dasKnownDscv() probe:40
> data #1 (4 bytes)
> 4294945091
> -----------
>
> What does "Warning: DB2 instance db2sds is not enabled for DAS
> multiple release support." mean???
>
> I have googled for SQL22205c and nothing constructive comes up.
>
> Any ideas would be much appreciated.
>
> -Stephen


execute: db2set -all, check to make sure the DB2ADMINSERVER variable
is set correctly.
Reply With Quote