PI17080: [wi 111215]RAM setup application fails to proceed past 'Configur e Lifecycle Management' when complex database URL is used

Rational Asset Manager Fix Pack 1 (7.5.2.1) for 7.5.2
Rational Asset Manager Fix Pack 2 (7.5.2.2) for 7.5.2
Rational Asset Manager Fix Pack 3 (7.5.2.3) for 7.5.2
Rational Asset Manager Fix Pack 4 (7.5.2.4) for 7.5.2
Rational Asset Manager 7.5.3
Rational Asset Manager 7.5.3.1
Rational Asset Manager 7.5.3.2
Rational Asset Manager 7.5.3.3
Rational Asset Manager 7.5.4
Rational Asset Manager 7.5.4.1
Rational Asset Manager 7.5.4.2
Rational Asset Manager 7.5.4.3
Rational Asset Manager 7.5.4.4
Rational Asset Manager 7.5.4.5
Rational Asset Manager 7.5.4.6
Rational Asset Manager 7.5.4.7
Rational Asset Manager 7.5.4.9
Rational Asset Manager 7.5.4.8
Rational Asset Manager 7.5.4.10

APAR status

• Closed as program error.

Error description

• Abstract:
  
  Attempts to configure lifecycle management for RAM v7.5.2 server
  may fail if a complex database URL is specified in the RAM setup
  database configuration page.
  
  Error Description:
  
  In the RAM setup application, during database configuration,
  user has the option to configure the database information either
  with database detail information (server host, database name,
  user, password, etc) or by specifying a JDBC URL.
  
  If the user specifies JDBC URL that is complex (as in the case
  of configuration for Oracle RAC database), RAM setup will fail
  to retain the database type information, which will in turn
  cause setup to fail to proceed; this can occur at the configure
  lifecycle management page, where an attempt to connect to the
  database is made.
  
  WORKAROUND:
  There is no known workaround at this time.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * WAS7 and WAS8.                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * After restart server ,RAM can not get database type from     *
  * data source of WAS.                                          *
  *                                                              *
  * That because user is using complicated URL for Oracle RAC,   *
  * just like                                                    *
  * jdbc:oracle:thin:@(DESCRIPTION=(address_list=(load_balance=o *
  * n)(failover=on)(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=15210))(A *
  * DDRESS=(PROTOCOL=TCP)(HOST=)(PORT=15210))(ADDRESS=(PROTOCOL= *
  * TCP)(HOST=)(PORT=15210)))(CONNECT_DATA=(SERVER=dedicated)(SE *
  * RVICE_NAME=jtsdb)))                                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in
  https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.
  WorkItem/111215
  

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

  RATL ASSET MGR

• Fixed component ID

  5724R4200

Applicable component levels

• R752 PSY

     UP