JR52455: JDBC TEST CONNECTION FAILS IN AN INFORMATION SERVER 11.3 WAS CLUSTER

IBM InfoSphere Information Server, Version 11.3.1.2 (Fix Pack 2)

APAR status

• Closed as program error.

Error description

• Information Server 11.3 installed with a WAS cluster - The test
  connetion button fails for 4 of the JDBC data sources. The error
  is:
  The test connection operation failed for data source ASB JDBC
  DataSource on server nodeagent at node <node name> with the
  following exception: java.sql.SQLException:
  [jcc][t4][10205][11234][3.66.46] Null userid is not supported.
  ERRORCODE=-4461, SQLSTATE=42815 DSRA0010E: SQL State = 42815,
  Error Code = -4,461
  
  This fails for the following JDBC data sources:
  ASB JDBC
  ASB JDBC XA
  ASB JDBC Staging XA
  JReport JDBC
  
  The issue is that the aliases for the J2C authentication data
  for these databases are not created.
  

Local fix

• 1. Go to Resources => JDBC => JDBC Providers and click ASB JDBC
  Provider
  2. Under Additional Properties click data sources
  3. Click ASB JDBC DataSource
  4. Under Security Settings, the Component-managed authentication
  alias and Container-managed authentication alias are set to ASB
  DB user but the problem is that does not exist under JAAS - J2C
  authentication data so it needs to be added.
  5. Under Related items (Still on the same page) click JAAS - J2C
  authentication data
  6. Click New
  7. The Alias field should be "ASB DB user". Those are spaces in
  between, no underscores.
  8. Put in the user name and password for the xmeta database.
  Click Apply and save.
  9. Sync the nodes
  10. Go back to the ASB JDBC DataSource and scroll down to the
  Security Settings and click the drop down for Component-managed
  authentication alias. You will now see nodename/ASB DB user.
  Select that user for both the Component-managed authentication
  alias and Container-managed authentication alias. When the new
  alias is added, WAS automatically appends the nodename to the
  front. Be sure to pick the newly created alias with the node
  name.
  11. Next go back to the ASB JDBC data sources and click the
  JReport JDBC DataSource. Scroll down to the Security Settings
  and pick the same new alias for Component-managed authentication
  alias and Container-managed authentication.
  12. Make sure all changes are applied and saved
  13. Go back to JDBC providers and click ASB XA JDBC Provider.
  14. Under Additional properties click data sources
  15. Click the ASB JDBC Staging XA DataSource. This data source
  well. Under Related items click JAAS - J2C authentication data
  16. Click New
  17. For the Alias name enter "imamJ2eeAuthAlias"
  18. Enter the user name and password for the xmetasr database.
  CLick Apply and Save.
  ***This user may be created at the same time as the ASB DB user
  19. Sync the nodes
  20. Go back to ASB JDBC Staging XA DataSource and change the
  Component-managed authentication alias and Container-managed
  authentication alias to both use nodename/imamJ2eeAuthAlias
  21. Apply and Save
  22. Next go back to the ASB XA JDBC Provider and click data
  sources and click on the ASB JDBC XA DataSource.
  23. Change Authentication alias for XA recovery,
  Component-managed authentication alias and Container-managed
  authentication alias to the nodename/ASB DB user alias. This one
  does NOT use the same user as the Staging data source.
  The IADB and QSSRDB Providers all work correctly.
  24. Restart the nodes, cluster and DMGR
  

Problem summary

• For InfoSphere Information Server 11.3 installed in a WebSphere
  cluster, the test connection button fails for the InfoSphere
  JDBC data sources. The error is
      'The test connection operation failed for data source "data
  source name" on server nodeagent at node "node name" with the
  following exception:
  java.sql.SQLException:"[jcc][t4][10205][11234][3.66.46] Null
  userid is not supported. ERRORCODE=-4461, SQLSTATE=42815
  DSRA0010E: SQL State = 42815, Error Code = -4,461
  
  This fails for the following JDBC data sources: "ASB JDBC, ASB
  JDBC XA, ASB JDBC Staging XA, JReport JDBC.
  The issue does not impact the application servers.
  

Problem conclusion

• The aliases for the J2C authentication data for these databases
  had not been created
  

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

• Fixed component name

  INFO SRVR PLATF

• Fixed component ID

  5724Q3612

Applicable component levels

• RB31 PSY

     UP