This patch contains changes to the upgrade process for upgrading from previous versions of SmartCloud Cost Management. It is strongly advised that this patch is applied before running a database upgrade. Please note that the Summary and Detail tables are both updated as part of the upgrade to the latest version of SmartCloud Cost Management. As these tables can be very large, please ensure before running the database upgrade that the following database configuration parameters have been set appropriately: For DB2, the database parameters: Log file size (LOGFILSIZ) Number of primary log files (LOGPRIMARY) Number of secondary log files (LOGSECOND) For Oracle, please ensure there is enough temporary and undo space available For SQL Server, please ensure that the tempdb system database has been configured and sized appropriately. The patch updates the tables approximately 10,000 records at a time until both tables have been fully updated. If you would like to update more rows within each transaction, run the the following SQL statement in the database, replacing NumberOfRows with your preferred number of rows: Insert into CIMSCONFIGOPTIONS (PROPERTYNAME,PROPERTYVALUE,PROPERTYTYPE,SEQUENCE,PROPERTYDESCRIPTION) values ('RowCommitRate','NumberOfRows',1,0,'Commit Rate for Large Updates'); For example, if you want to update 50,000 rows at a time, then run the following statement: Insert into CIMSCONFIGOPTIONS (PROPERTYNAME,PROPERTYVALUE,PROPERTYTYPE,SEQUENCE,PROPERTYDESCRIPTION) values ('RowCommitRate','50000',1,0,'Commit Rate for Large Updates'); Note: When upgrading from Tivoli Usage and Accounting Manager Fix Pack 4 (Database Version 001.028), two upgrades are applied to migrate to the latest version of SmartCloud Cost Management. How to install the SCCM 2.1 IFIX001 patch Use the following instructions to installing the SCCM 2.1 IFIX001 patch: 1) Stop the Application Server a) On the command-line interface, change to the \bin\ directory. b) Stop the Application Server using one of the following options: For Windows - click the stopServer.bat file. For UNIX / Linux - run the following command: ./stopServer.sh -username tipadmin -password mypassword Where tipadmin is the administrator user ID and mypassword is the administrator password. Attention: On Windows systems, you do not need to provide -username and -password arguments to the stopServer command. For more information see http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rxml_stopserver.html c) Wait a moment for the server to completely shut down. 2) Unzip the SCCM2100-IFIX0001.zip file into a temporary directory. 3) Navigate to the folder where the SCCM2100-IFIX0001.zip file was unzipped and run the following command: For Windows – run the following command: applyFix.bat For UNIX / Linux - run the following command: ./applyFix.sh . 4) Start the Application Server: * For Windows - click the startServer.bat file. * For UNIX / Linux - run the following command: ./startServer.sh -username tipadmin -password mypassword Where tipadmin is the administrator user ID and mypassword is the administrator password. How to uninstall the SCCM 2.1 IFIX001 patch Use the following instructions to uninstall the SCCM 2.1 IFIX001 patch: 1) Stop the Application Server a) On the command-line interface, change to the \bin\ directory. b) Stop the Application Server using one of the following options: For Windows - click the stopServer.bat file. For UNIX / Linux - run the following command: ./stopServer.sh -username tipadmin -password mypassword Where tipadmin is the administrator user ID and mypassword is the administrator password. Attention: On Windows systems, you do not need to provide -username and -password arguments to the stopServer command. For more information see http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rxml_stopserver.html c) Wait a moment for the server to completely shut down. 2) Navigate to the folder the SCCM2100-IFIX0001.zip file was unzipped and run the following commands: For Windows – run the following command: undoFix.bat For UNIX / Linux - run the following command: ./undoFix.sh . 3) Start the Application Server: * For Windows - click the startServer.bat file. * For UNIX / Linux - run the following command: ./startServer.sh -username tipadmin -password mypassword Where tipadmin is the administrator user ID and mypassword is the administrator password. Known Issues When running the upgrade, the update to the Summary and Detail tables is performed as part of the 002.001 script. If the database parameters mentioned above are not set correctly, then the updates may fail with the following errors: DB2: DB2 SQL error: SQLCODE: -964, SQLSTATE: 57011, SQLERRMC: null Oracle: ORA-01652: unable to extend temp segment by string in tablespace string SQL Server: Error Messages 1101, 3967, 1105 If this occurs, then the upgrade will show the errors above and show the current version as 001.029. To fix this, increase the relevant database configuration parameters mentioned above and then rerun the upgrade process until the current version is shown as 002.001. If this cannot be increased then the number of rows updated within each transaction can be reduced. To do this, update the RowCommitRate entry in the CIMSCONFIGOPTIONS table by running the following statement in the database: UPDATE cimsconfigoptions SET propertyvalue = 'NumberOfRows' WHERE propertyname = 'RowCommitRate'; Where NumberOfRows is the number of rows you want to update in a transaction. Note: This record is inserted into the CIMSCONFIGOPTIONS if it does not already exist when the 001.029 script is run.