Fabrizio, I don't know about Probl.#1 and I'm looking in what I know to come back to you. Probl. #2 seems to be linked with communications. I rn into something like this on V7.1 FP3 last week. I tlooks like the instance is not finding it's tcpip port number to listen on. The way I solved it after looking in db2diag.log (which I know you can't), is to set the service name and make the corresponding entry in the services file. I hadn't and I thought it would default to port 50004 (it was the 3rd instance) but it did not. I set it and it worked fine. HTH, Pierre.
"Napolitano, Fabrizio" wrote: > Hi, > > I got the SQL0290N message a lot of time and always got out of it but this > time I'm in trouble one of the shops I sometimes assists called me because > they cannot even connect to their DB and even doing the restart of the DB > they got the SQL0290N. > > The platform is AIX 4.3.3 with DB2 UDB EE v7.1 fp 3 > > The Situation (as explained) is: > > The system crashed and now there are some tablespaces left in a pending > state . No connection are allowed with code SQL0290N and for some "strange" > reason the db2diag.log permit was set to root and so no log was written > since 23 of october. > Now at the moment I can't access the system (I'm working as telephone > support) in any case the people on site assured me that they didn't get any > problem with the disk subsystem and that all the containers are accessibles > and with the right permissions! > My First question if something got wrong on some tablespaces shouldn't be > allowed the connection to the db and only those tablespaces being offline?? > Second and obvious question there is any way to be able to connect to the db > and so get the list of tablespaces offline or in load or restore pending > state and trying to fix them??? > Not knowing wich tbs is troubled I told them to run a db2dart in Inspect > mode to get the situation. But then??? The only action that I can think of > is a restart db putting the damaged tablespaces in drop pending state, is > there any less painfull action???? > Is this possible to use the db2dart for a repair action or should I push > them to call IBM Support?? > > Second question I don't think connected to the first but I don't know... and > 'cos I'm here... > Starting the istance they get the error: > SQL5043N Support for one or more communications protocols failed to start > successfully. However, core database manager functionality started > successfully. > Well tried stopping again the istance , running a ps and killing all the > defunct or hung db2 process, ipcs and again after everything is clean and > nice at the next start got again the same error... where to start to look > for a clue?? > Is it possible that there are contentions with DAS or other instances??? > > Thanks in advance to all of you > Fabrizio > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** You are subscribed to [EMAIL PROTECTED] > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
begin:vcard n:Saint-Jacques;Pierre tel;cell:514-233-8679 tel;fax:514-737-1268 tel;work:514-737-4515 x-mozilla-html:FALSE org:SES Consultants Inc. adr:;;233 Simcoe Cr.;Mount-Royal;QC;H3P 1X1;Canada version:2.1 email;internet:[EMAIL PROTECTED] title:President fn:Pierre Saint-Jacques end:vcard
