PI17966: ORACLE SETUP; UNEXPECTED VALIDATED OF USERS TABLESPACE.

Rational Insight Fix Pack 5 (1.1.1.5) for 1.1.1
Rational Insight Fix Pack 6 (1.1.1.6) for 1.1.1
Rational Insight Fix Pack 7 (1.1.1.7) for 1.1.1

APAR status

• Closed as program error.

Error description

• In a upgrade process on a product that has been working for
  certain amount of time, if the USERS tablespace does not exist
  and the product is functioning without problem, it is safe to
  assume the USERS tablespace is not being used. The RICM has been
  assigned schemas with non-default tablespaces.
  
  In some prod env. the USERS tablespace is often the target of
  database management policies that remove the default Oracle
  users tablespaces, which lead to the following error while
  upgrading the product.
  
  CRRRA0077E: An error happened when validating the database.
  'com.ibm.rational.rrdi.setup.db.common.RRDIDBException: ERROR:
  ORA-00959: tablespace 'USERS' does not exist '.
  
  Work around is to add the USERS tablespace temporarily.    In
  tightly controlled environment the flexibility to use this work
  around is very be limited.
  
  If validation is required it is possible to find the tablespace
  associated to oracle schemas by a simply query:
  
  **********
  SQL> select DEFAULT_TABLESPACE, TEMPORARY_TABLESPACE from
  dba_users where username = 'CTUSR';
  
  DEFAULT_TABLESPACE             TEMPORARY_TABLESPACE
  ------------------------------ ------------------------------
  TB_CTUSR                       TB_CTTMPUSR
  
  SQL>
  *********
  
  Any validation should be Identifying the tablespace associated
  to a schema.
  
  A second option of to provide a java property that would bypass
  the validation.  For example the DW has such a property:
  com.ibm.team.datawarehouse.db.automatic.setup = false
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * RRDI setup raised ERROR                                      *
  * com.ibm.rational.rrdi.setup.steps.EnterpriseContentStoreStep *
  * Service : javax.net.ssl.SSLPeerUnverifiedException: peer not *
  * authenticated                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * 05/08/2014 15:25:04,417 INFO                                 *
  * com.ibm.rational.rrdi.setup.resources.ResourceService :      *
  * CRRRA0137I: Loading the model                                *
  * 05/08/2014 15:25:04,418 INFO                                 *
  * com.ibm.rational.rrdi.setup.resources.ResourceService :      *
  * CRRRA0139I: Loaded the model                                 *
  * 05/08/2014 15:25:04,419 INFO                                 *
  * com.ibm.rational.rrdi.setup.resources.ResourceService :      *
  * CRRRA0115I: No DBMS is found.                                *
  * 05/08/2014 15:28:01,002 INFO                                 *
  * com.ibm.rational.rrdi.setup.steps.EnterpriseContentStoreStep *
  * Service : CRRRA0068I: Start to validate the database.        *
  * 05/08/2014 15:28:01,009 ERROR                                *
  * com.ibm.rational.rrdi.setup.steps.EnterpriseContentStoreStep *
  * Service : javax.net.ssl.SSLPeerUnverifiedException: peer not *
  * authenticated                                                *
  * javax.net.ssl.SSLPeerUnverifiedException: peer not           *
  * authenticated                                                *
  *     at                                                       *
  * com.ibm.jsse2.SSLSessionImpl.getPeerCertificates(SSLSessionI *
  * mpl.java:39)                                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Adding the USERS tablespace to address the issue
  fixed in 5.0
  

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 COMMON REP

• Fixed component ID

  RATLRCR00

Applicable component levels

• R206 PSY

     UP