var sidebar_align = 'right';
var content_container_margin = parseInt('290px');
var sidebar_width = parseInt('270px');
Answered: diag log error "ECF_GENREG_ERROR_PATH_NOT_SET The registry path is not set"
We recently migrated DB2 9.7 server to new data center, after the migration i have noticed below diaglog error.
But nothing was reported from application team and testers as of now.
can some one suggest what might be this error
2016-07-15-20.00.52.545671+120 I235827431A1338 LEVEL: Error
PID : 28770496 TID : 19327 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : ECPE2
APPHDL : 0-19492 APPID: 0A8D034C.D553.160716002858
AUTHID : wcdbna
EDUID : 19327 EDUNAME: db2agent (ECPE2) 0
FUNCTION: DB2 Common, Generic Registry, GenRegFile::OpenScan, probe:5
MESSAGE : ECF=0x900001BA=-1879047750=ECF_GENREG_ERROR_PATH_NOT_SET
The registry path is not set
CALLED : DB2 Common, OSSe, OSSHFile: pen
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
 0x090000000F32C7E8 pdOSSeLoggingCallback + 0x34
 0x090000000ED28AC4 oss_log__FP9OSSLogFacUiN32UlN26iPPc + 0x1C4
 0x090000000ED28E50 ossLogRC + 0x70
 0x090000000F125B94 OpenScan__10GenRegFileFv + 0x4F4
 0x09000000101AC7A4 @69@EnvGprfRefresh__FP11SEnvProfile + 0x664
 0x09000000101AD6F0 @69@EnvPrfOpen__FPCciPP11SEnvProfile + 0x128
 0x09000000101B4A80 sqloGetEnvUnCached + 0x130
 0x09000000101C6010 sqlrr_initialize_sp_cb__FP8sqlrr_cb + 0x160C
 0x0900000010227228 sqlrr_appl_init__FP8sqeAgentP5sqlca + 0x504
 0x0900000010259B0C InitEngineComponents__14sqeApplicationFcP8sqeAgent P8SQLE_BWAP5sqlcaP22SQLESRSU_STATUS_VECTORT1 + 0x3D0
DB2 V9.7 FP7 , AIX 7,
Do you have the following registry set:
DB2AUTH=OSAUTHDB is set.
on DB2 9.7 fp7 we have 7 servers.
But we are getting this error only on one server. Is that because of some particular reason, in which only this DB is handling some task, is causing this error ?
As of now nothing reported as failed on this server. So if i want to suggest to my management for FP upgrade i don't think they will accept.
And one of my friend suggested for instance update. will it work ? don't think so .
I'd suggest you to open a PMR with IBM support. They can confirm or deny the root cause of the problem using deeper analysis.
It's hard to say exactly what happens looking at the db2diag.log entries only.
Thanks Mark for your valuable time
Tags for this Thread