Symptom
You notice that the DB2COMM registry variable is not associated with the DB2_WORKLOAD aggregate registry variable. The 'db2set' command shows it with [0] rather than DB2_WORKLOAD:
db2set -all | grep DB2COMM
[i] DB2COMM=TCPIP [O]
It should look like this
db2set -all | grep DB2COMM
DB2COMM=TCPIP [DB2_WORKLOAD]
This is not a problematic situation and does not affect database functionality. However, the SAP standard registry settings initialized by the 'db6_update_db.sh script' call for this parameter (and others) to be associated with DB2_WORKLOAD=SAP. Reference SAP Note 1365982.
Read more...
Environment
DB2 LUW (DB6)
Product
Keywords
database udb global instance profile , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , BC-DB-DB6-UPG , Upgrade SAP System , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.