Messages related to not being able to find .OLR file are informational. The reason why your instance comes down is due to the following error:
2009-10-12-11.21.02.974000+330 E1311678H963 LEVEL: Severe
PID : 2584 TID : 2884 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : CCA
APPHDL : 0-8752 APPID: 192.168.10.12.64009.09101205451
AUTHID : CCACCAD
EDUID : 2884 EDUNAME: db2agent (CCA)
FUNCTION: DB2 UDB, oper system services, sqloEDUExceptionFilter, probe:55
MESSAGE : ADM0501C A stack overflow exception has occurred. The DB2 instance
has terminated abnormally. To remedy this problem, you may increase
the default stack size for db2syscs.exe using the db2hdr utility as
follows: db2hdr \sqllib\bin\db2syscs.exe /s:<stackreserve>[,
<stackcommit>] Note that increasing the default stack size will
consume virtual memory space and may reduce the maximum number of
concurrent connections. Contact IBM Support for further assistance.
You had reported this problem before:
DB2 9.5c Express Fix Pack
This stack overflow can be due to:
IBM IZ33027: DB2 instance may abend due to stack overflow (instead of dumping SQL0973N) while processing a very large predicate - United States
But if you're still using Express-C, you can't install fixpaks unless you purchase FTL (as explained by Marcus in your prior post).