AIX fp4 upgrade to 8.5.0 arsdb fails to initialize

[wwwalton]

Anyone ever see this sequence:
8.5.0.0 runs fine.
Shut everything down
apply fp4, add the ARS_ORIGINAL_CODEPAGE in the ars.cfg
su - archive
run:  arsdb -gv
Result:  arsdb:  Unable to initialize environment. The return code is 1

Yet, starting DB2 separately can be done and can connect via a db2 client.
???
-walt

[demaya]

I had this before. Did you try to find any open arssockd process via
ps -ef | grep arssockd
?

Maybe kill some zombie processes and start the instance via
arssockd <INSTANCENAME>
again.

Cheers

[Justin Derrick]

Hi Walt.

Two things...

I've always used arsdb -gkv as my command to start the database, and leave it 'activated', that is, ready for connections.  Maybe try adding the k to your command.

For more diagnostic information, run this command as root:
swcons `tty`
(Those are backticks, not quotes - it's to the left of my '1' key on my keyboard.)
Then try running arsdb -gkv again -- this time, any diagnostic output will be directed to your screen.  Show us that output and we might be able to help.

-JD.

[wwwalton]

I also issue arsdb -gkv  but IBM pointed out a technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21206602
QuestionWhen I run arsdb -gkv, I receive the following error:

> arsdb -gkv
Starting the DB2 ARCHIVE database instance
Activating the DB2 ARCHIVE database
Unable to activate database ARCHIVE. SQLCODE = -1031

CauseThe arsdb -k command issues an activate database DB2 CLI call to DB2. Starting in DB2 version 6 or 7, DB2 automatically activates and de-activates all databases upon db2start and db2stop.

AnswerThe -k parameter is unnecessary now, since arsdb -g issues the DB2 equivalent of a db2start, therefore omit the -k parameter when running arsdb.

----  Now the above being said, I'm going around with level 1 on this because what happens (I'm at 8.5.0.5 now), is if I issue a db2start, the db comes up, then I issue arssockd start  and everything is fine.  But if I shut it all down, then issue arsdb -gv or arsdb -gkv, I get the same error:
oddevsb:/usr/lpp/ars/bin>arsdb -gkv
arsdb:  Unable to initialize environment. The return code is 1

This error is what originally drove the PMR I opened.
-walt

[wwwalton]

From IBM:
Development identified it's a defect. APAR PM62725 opened. Work around for customer is to use db2start and db2stop. Fix will be in the next release. Thanks.

-walt