Upgrade from 11.3.6 to 11.3.6 SP1 fails due to incorrect tablespace

Document created by JeanPaulLucas Employee on Oct 3, 2015
Version 1Show Document
  • View in full screen mode

During an upgrade from CA WAAE 11.3.6 to 11.3.6 SP1,  the database upgrade  fails because the CA WAAE installer detects a wrong tablespace for the index.

 

From file install_aedb.log

 

Upgrading the database tables where required.

/sma/au/p1/bin/waae/JRE_WA/bin/java -Dfile.encoding=UTF-8 -Xmx256m -cp ../buildadb.jar com.ca.ewa.BuildADB -dbvendor Oracle -infile ../pre_upgrade.adb -outfile /tmp/ora_upgradeaedb_pri/tmp.sql -oradataspace TBS_AEDB_D -oraindexspace TBSAEDB_X -baseVersion 11.3.6

sqlplus aedbadmin/******@AUPROD1 @ /tmp/ora_upgradeaedb_pri/tmp.sql 2>&1

 

In this specific case: -oradataspace was OK with TBS_AEDB_D but not -oraindexspace with TBSAEDB_X

 

Where can we find this information to correct it?

 

If the tablespace found by the installer no longer corresponds with the current tablespace in Oracle, you have to go to this directory tree /opt/CA/SharedComponents/installer/administration/admi/CAWorkloadAutomationAE/11.3.6.437

and  open file CAWorkloadAutomationAE.@prm

 

In this file you can find the name of the tablespaces:

 

#parameter: $ASI_DATA_TBLSPC_NAME , TBS_AEDB_D , Defined Oracle tablespace data name - Primary DB , 0 ;

#parameter: $ASI_INDEX_TBLSPC_NAME , TBSAEDB_X , Defined Oracle tablespace index name - Second DB , 0 ;

 

Update this file with the right information for your installation ( for example here TBS_AEDB_X ) then rerun the setup and select the 'Repair' option

 

#parameter: $ASI_DATA_TBLSPC_NAME , TBS_AEDB_D , Defined Oracle tablespace data name - Primary DB , 0 ;

#parameter: $ASI_INDEX_TBLSPC_NAME , TBS_AEDB_X , Defined Oracle tablespace index name - Second DB , 0 ;

Attachments

    Outcomes