10-28-2016 08:59 AM - edited 03-19-2019 11:45 AM
Hi all,
I'm experiencing an issue trying to upgrade time zone on Cisco Unity connection subscriber version 9.1.2.10000-28.
I did a mistake in the upgrade proceedure as I installed the cop files first on the subscriber and after on the publisher.
Anyway on the publisher everything works fine and the cop has been sucessfully installed.
The I tried to:
1. Reboot the publisher
2. Reboot the subscriber
3 Tried to install .cop again on the subscriber but I always retrieved error attached below.
Do you have any ideas?
Thanks in advance for help.
BR
Francesco
******************************
[Capture] --------------------------------xxxxxxx---------------------------------
[Capture]
[Capture] There were no SDKs found to patch in this system.
[Capture] --------------------------------xxxxxxx---------------------------------
[Capture] Updating IBM JTZU env file to patch the discovered IBM JREs.
[Capture] Executing IBM JTZU to update IBM JREs time zone data.
[Capture] IBM Time Zone Update Utility for Java (JTZU) Version 1.7.16d
[Capture] JTZU Home: /common/download/ciscocm.dst-tzdata-2016d-el5/IBM_JTZU_tmp
[Capture] Set the variables using the script /common/download/ciscocm.dst-tzdata-2016d-el5/IBM_JTZU_tmp/runjtzuenv.sh
[Capture] Launching the Java Time Zone Updater Tool.
[Capture]
[Capture]
[Capture] *********** Command-Line 'Patch' Mode Started ***********
[Capture] 'Patch' Mode:
[Capture] In this mode, the tool patches each of the Java installations listed in SDKList.txt with the new time zone information.
[Capture]
[Capture] *********** WARNING MESSAGE ***********
[Capture] Warning - Applying IBM product maintenance which contains down level time zone data will remove the updates applied by this tool. In such cases you will need to re-run this tool to restore the time zone data to the latest level. Updates made to the Java time zone data by this tool are not managed by any of the formal change control mechanisms for servicing IBM software products.
[Capture]
[Capture] The SDKList.txt file doesn't exist. Please re-run the tool with -Ddiscoveronly=true option to generate the list of SDKs.
[Capture]
[Capture] --------------------------------xxxxxxx---------------------------------
[Capture] Removing the IBM JTZU temp directory
OS execution complete
Executing Product component
[Capture] Copying the necessary patches and files to the system
[Capture] Creating file backup
[Capture] Backing up /usr/local/cm/jar//typetables.jar
[Capture] Copying files
[Capture] Copying product releated files
[Capture] Copying - ./ciscocm.dst-tzdata-2016d-el5/typetables.jar
[Capture] Updating TFTP files
[Capture] cp: cannot create regular file `/usr/local/cm/tftp/': Is a directory
[Capture] Error in copying JAR
[Capture] ./ciscocm.dst-tzdata-2016d-el5/dst_tz_ep_updater.sh: line 80: /usr/local/cm/tftp/tzupdater.ver: No such file or directory
[Capture] Error in copying ver
[Capture] cp: cannot create regular file `/usr/local/cm/tftp/': Is a directory
[Capture] Error in copying csv
[Capture] cp: cannot create regular file `/usr/local/cm/tftp/': Is a directory
[Capture] Error in copying j9-JAR
Component execution failed
Execution failed. Please see the log file.
Rolling back the changes
Rolling back OS component
[Capture] Restoring SUN JRE files
[Capture] Restored SUN JRE time zone directory
[Capture] Deleted SUN JRE time zone update directory
[Capture] Checking upgraded tzdata rpm
[Capture] New RPM Is installed - trying to roll back to old RPM
[Capture] Could not restore tzdata-2016d-1.el5, /common/rpm-archive/9.1.2.10000-28/RPMS/tzdata-2016d-1.el5.i386.rpm does not exist
[Capture] Rolling back IBM tz changes
[Capture] Restoring backup file /usr/local/bin/base_scripts//tzupdater.jar _backup
[Capture] Restoring backup file /usr/local/bin/base_scripts//IBMjtzu.zip _backup
[Capture] Restoring backup file /usr/local/bin/base_scripts//j9-tzdata.jar _backup
[Capture] Restoring backup file /usr/local/platform/tzdata//OlsonTzData.tar.gz _backup
[Capture] Restoring backup file /usr/local/platform/tzdata//TzDataCSV.csv _backup
[Capture] Restoring backup file /usr/local/platform/bin//getTzDataVersion.sh _backup
OS rollback complete
Rolling back Product component
[Capture] Restoring backup file /usr/local/cm/jar//typetables.jar _backup
[Capture] Product time zone changes cannot be rolled back
Component rollback complete
Rollback completed
Unsuccessfully installed ciscocm.dst-updater-tzdata-2016d-el5-9.1.2.cop
[16/10/28_17:57:56] locale_install.sh: ERROR: Copstart script of /common/download//ciscocm.dst-updater.2016d-el5-00.9.1.2.cop failed
Installation of ciscocm.dst-updater.2016d-el5-00.9.1.2.cop.sgn failed
Copstart script of /common/download//ciscocm.dst-updater.2016d-el5-00.9.1.2.cop failed
A system reboot is required when the upgrade process completes or is canceled. This will ensure services affected by the upgrade process are functioning properly.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide