I had faced issue at customer after upgrade DB2 LUW extension to 2.3.0.
One of instances failed to connect with errors in AG log (Message: Connection timeout). Admins informed that db2 instances with no connections turns itself off. Until admin manually accessed that instance (and wakes up instance), extension failed to connect, probably because it has too short timeout setting to wait for db2 instance wake up.
DB2 LUW extension should have timeout configurable for described reason.
Alanata a.s.
