PI89529: CONTENT STORE CONNECTION TO SQL SERVER MULTI-SUBNET LISTENER FAILS WHEN CLUSTER NOT RUNNING ON PRIMARY IP

APAR status

• Closed as fixed if next.

Error description

• When testing in Cognos Configuration:
  
  "Content manager is unable to connect to the content store.
  Verify that the database connection properties in the
  configuration tool are correct and that when you test the
  connection, the test was successful."
  
  In cogconfigipf.log:
  
  10.207.31.187:9300        5216     2017-09-07 13:10:32.040
  +10
  Thread-11          CM            6          1
  Audit.cms.CM                                       Success
  <parameters><item name="msgText"><![CDATA[DB connection string:
  jdbc:sqlserver://<listener
  DNS>:99999;databaseName=CM;integratedSecurity=true;applicationNa
  me=IBM_C11_CM]]></item><item
  name="msgLocation"><![CDATA[com.cognos.cm.dbstore.CMDbConnection
  Parameters.<init>]]></item></parameters>
  

Local fix

• Option 1: append ";multiSubnetFailover=true" to the Content
  Store Database Name
  Option 2: Modify the "RegisterAllProvidersIP" and
  "HostRecordTTL" parameters in the multi-subnet listener to
  values of "0" and "10" respectively, so that only the current
  cluster IP is registered in DNS, and any change is registered
  quickly enough for failover to be seamless.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Users                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IBM Cognos Analytics 11.1.3                       *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels