Installing CTM R9.0.0.690.2
---------------------------

This readme describes how to download and install CTM R9.0.0.690.2, which inherits all fixes and device support from
previous patches. 

The CTM R9.0.0.690.2 patch provides support for the following:
- Oracle 10.2.0.4 Patch (see CSCtj72796)
- Critical Oracle Patches 9352164 and 9952234 (see CSCtj72766)

The following caveats are fixed in CTM R9.0.0.690.2: 

CSCtb55127: Exceptions are displayed and logged when NE services start up.   
CSCtd56250: CTC cannot be launched from CTM.
CSCti13296: The Performance Monitoring (PM) service log file consumes all available space in the /tmp directory. When the /tmp directory 
            is full, some operating system services are disrupted and Oracle sessions shut down, causing general application instability.
CSCtj72766: CTM must support the latest critical Oracle security patches. See "Installing the CTM-Supported Critical Oracle
	    Patches 9352164 and 9952234."
CSCtj72796: CTM must support the Oracle 10.2.0.4 patch. See "Installing the CTM-Supported Oracle 10.2.0.4 Patch."
CSCtj90800: A CTC-based network element never completes discovery.
CSCtj92364: The Alarm Log reports a database timeout error. 
CSCtk13431: High CPU usage after bulk circuit creation.
CSCtk13453: PM data is not retrieved when using GateWay/CORBA APIs on some layer rates.
CSCtk99910: Sometimes, a CTC library deadlock occurs when CTM manages a large number of nodes. NE connectivity 
            is lost and no longer visible in CTM.
CSCtl83275: The CTM client freezes after some time. 
CSCtn62500: Need ability to enable Jacorb logging without restarting the network service.

The following caveats are fixed in CTM R9.0.0.680.3:

CSCtb33156: Oracle undo and temp tablespaces consume all of the free space in the /db01 partition.
CSCti80797: The getCTMHistoryPMData API returns a PM data file with no data when layer rate 15 (LR_STS3c_and_AU4_VC4)
	    or 14 (LR_STS1_and_AU3_High_Order_VC3) are used.
CSCti90949: The CTM server intermittently restarts after an overwhelming number of events are received from network
	    services. The server eventually crashes because it cannot manage the event load.
CSCtj88343: CTM must support Cisco Edge Craft Release 2.2.2.
CSCtj88384: The getAllSubnetworkConnections API does not work.
CSCtk81770: CTM does not start because the inode limit has been reached in the /opt directory.
CSCtl06435: The network admin user cannot modify or delete OCHNC circuits. An access violation error is shown.

The following caveats are fixed in CTM R9.0.0.670.5:

CSCsf96351: After the CTM server restarts, SONET NEs do not come up.
CSCsv45598: Sometimes, when launching the L2 Topology table, the following error message appears: 
	    "EID-333: A database timeout occurred."
CSCsx52287: Event notification is not audible.
CSCta42487: The SM service disconnects during a JMOCO hello message, and the CTM server restarts.
CSCta69019: The ctms-stop and ctms-abort scripts do not work when Oracle is down.
CSCtb25595: Alarm icons display incorrect information in the Domain Explorer tree.
CSCtb72630: Network discovery hangs when the LINK_TABLE database table is empty.
CSCtb81830: Multiple initial poll jobs are created for the same NE.
CSCtb83002: The CTM client freezes and does not respond to user commands. 
CSCtc10514: CTM does not receive alarms from ONS 15305 R2.0 NEs.
CSCte98243: Cannot clear PM counters for Ethernet real-time PM data on CE-MR-10 cards.
CSCth05616: The NE Explorer does not display 32WSS optical channel parameters. 
	    The Optical Channel tab is blank for 32WSS cards.
CSCth53325: ONS 15216 NEs disconnect from CTM and cannot be reconnected.
CSCth69497: The NE service does not respond promptly to commands sent from CTM clients.
CSCti30435: Navigating within the CTM client is slow, and the client freezes. If you launch a new CTM 
	    client, the following error is displayed:
	    EID-382: The CTM server is initializing. Please try again later.
CSCti61844: The Create Layer 2 Topology wizard or the Add/Remove Card wizard freezes 
	    for several minutes, and then proceeds correctly.
CSCti72327: L2 topology resynchronization takes too long when there are many VLANs.
CSCtj21034: The remote debug console (RDC) has no commands for Layer 2 cache management.

The following caveats are fixed in CTM R9.0.0.650.4:

CSCsr65306: The migration scripts fail with a Java exception.
CSCsv00207: A cleared alarm disappears from the Alarm Browser.
CSCsy84624: UPSR/SNCP switch selectors are missing from the Circuit trace.
CSCsz71168: A database import causes incorrect index error messages.
CSCsz75781: The Error Log contains meaningless DWDM error messages.
CSCsz79773: Daily backups automatically scheduled from CTM are canceled.
CSCta23414: Installing CTM R9.0.0.600.7 shows security_config.sql script errors.
CSCta30560: Circuit Wizard fails when the back button is used after changing destinations.
CSCta30985: In locked state, there is a C server memory leak due to zombie LWPs.
CSCta31966: Memory usage for the ooemc process increases over a period of time.
CSCta35142: CTM restarts and the core_pmon.log file reports an Oracle error.
CSCtb55280: EQPT_INFO_TABLE is filled incorrectly by the MGX NE service.
CSCtb59923: Several exceptions appear in the CTM network service log.
CSCtb98230: The CTM Alarm Browser does not display an alarm when the system uptime of service modules exceeds the threshold.
CSCtc35552: CTM client writes NEDiscovery state on DB.
CSCtc49087: CTM shows MGX 88xx chassis serial no. as N/A in Inventory table.
CSCtc67375: OCHCC circuits are not shown when the Circuit Table is launched from a link.
CSCtc73082: Adding a preprovisioned MGX node to a CTM server results in high CPU usage.
CSCte39776: The CTM NE Description field does not match the NE description in CTC. 
CSCte65495: Server memory usage for the ooemc process increases over a period of time with every MGX NE resync.
CSCtf78021: After upgrading from CTM R8.5 to CTM R9.0, the CTM Config database table shows discrepancies.
CSCtf78039: After upgrading from CTM R8.5 to CTM R9.0, the initCTM.ora file is not updated correctly.
CSCtg56522: Cannot add CTC-based NEs to a CTC-based network service.
CSCtg92011: Customer request to change minimum length of CTM username to 3 characters.
CSCth21611: Loss of communication alarm storms occur periodically on CTC-based network services.
CSCth40549: A confirmation message appears for no reason in the Domain Explorer.
CSCth48038: CTX Transciever tab is blank for Cisco ONS 15310 MA SDH nodes.
CSCth71367: Navigating within the CTM client is slow, and the client freezes.
CSCth92179: CTM loses NE connectivity and the Garbage Collector usage is high.
CSCti10246: CTC-based network services can restart when short of stack memory.

The following caveats are fixed in CTM R9.0.0.648.1:

CSCth21611: Loss of communication (LOC) alarm storms occur periodically on CTC-based network services.
CSCth71367: Navigating within the CTM client is slow, and the client freezes.
CSCth92179: CTM loses NE connectivity and the garbage collector usage is high.

The following caveats are fixed in CTM R9.0.0.645.3:

CSCta69424: The CTM client freezes if the NE service manages pre-9.0 NEs.
CSCtc20162: When a single ONS 15305 NE service manages than one hundred ONS 15305 NEs, the
	    ONS 15305 NE service restarts.
CSCtd49099: Ethernet PM data is not collected for 15-minute and 1-day intervals.
CSCtd50557: Cannot install the CTM client patch if the install directory contains a blank space.
CSCtd52681: CTM R9.0 must add support for the ONS 15305 R2.0.4.
CSCte35831: CTM R9.0 must add support for the ONS 15454 SONET and ONS 15454 SDH R9.0.2.
CSCtf06220: In a high availability, single-node, geographical redundancy setup, the database migration
	    hangs when archivelog mode is enabled. The /db05 filesystem fills up, and the migration hangs.
CSCtf06511: If you upgrade CTM on a week day (not on a weekend), the following error occurs:
 	    ORA-27366: job "SYS.GATHER_STATS_CTM_JOB" is not running
CSCtf27628: The database upgrade finishes without errors; however, the initCTM.ora file does not update.
	    This issue causes problems with Oracle statistics management and node connectivity.

The following caveats are fixed in CTM R9.0.0.620.5:

CSCsl26108: CTM performs slowly while connecting, discovering, and resynchronizing CTC-based 
	    devices such as the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.
CSCsu90217: Continuous 15 min and 1 day PM lost bucket alarms occur and do not clear.
CSCsz83568: A DB WriterWorker NPE appears in the pmservice.log file for MRC-12 cards.
CSCta29948: Alarms in the CTM Alarm Browser do not clear or synchronize with CTC.
CSCta33231: The number of alarms displayed on the dashboard and NE Explorer is wrong. However, the 
	    alarm count is shown correctly in the Alarm Browser.
CSCta39574: When opening the Circuit table from an ONS 15454 node, circuits are not retrieved and a timeout 
	    error is displayed.
	    Note: If a timeout occurs again, increase the client database timeout period. Refer to section K.6.2,
	    "Database Timeout Occurs" in Appendix K of the Cisco Transport Manager Release 9.0 User Guide.
CSCta69923: Cleared alarms are not removed from the Alarm Browser.
CSCta73923: ONS 15216 EDFA3 nodes lose connectivity with CTM.
CSCtb05738: CTM event dispatcher threads are not distributed effectively. Events that arrive from CTC 
	    are assigned to a queue based on the value of the NE node ID. Because the node ID often has 
	    an even value, only queues with an even ID are used to process events. Consequently, half of 
	    the threads are instantiated but are never used to process events.
CSCtb13395: The Alarm Browser does not display some cleared alarms. CTC shows the cleared alarms, but the 
	    same alarms are missing from the CTM Alarm Browser.
CSCtb21147: CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails 
	    to report major DS1 alarms.
CSCtb30304: An error message (EID-315) appears after selecting Edit > Find to search for a circuit.
CSCtb31787: CTM R9.0 raises incomplete critical alarms.
CSCtb59547: CTM GateWay/CORBA reports incorrect physical location information.
CSCtb65065: In the NE Explorer for the ONS 15310 MA orthe ONS 15454 MSPP, the first time you select an 
	    optical card, the Transceiver tab is blank.
CSCtb73160: The Circuit table does not display port names for ONS 15454 ANSI DS1_E1_56 and OC192_XFP cards.
CSCtb78977: The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.
CSCtb83164: After device provision configurations, the following APIs are not updated: getEquipment, 
	    getAllEquipment, and getAllEquipmentName.
CSCtc19328: The CTM Domain Explorer window freezes and you are unable to select other NEs.
CSCtc70085: From the CTM client, you cannot launch CTC on release 9.0.x ENEs.
CSCtd03803: ENE/GNE configuration changes on the network and node connectivity issues cause the NE to remain
	    in Sync_Config state.
CSCtd31222: Circuits without a destination are not displayed in the Circuit table.

The following caveats are fixed in CTM R9.0.0.604.2:

CSCsz63889: Memory backups fail occasionally for CTC-based release 6.0.1 NEs.
CSCtb01411: The network services and network service instances cannot be stopped or started from the Control Panel. 
	    The SMService-0-<timestamp>.log file shows the following error message: 
	    EID-5016: Exception: %01 occurred while launching service process.java.io.IO
	    Exception: Too many open files
CSCtb88190: CTM displays GNEs with release 9.0.x as ENEs. Also, the corresponding GNEs are displayed as LNEs 
	    with an Unavailable status.
CSCtb85880: After performing NE software upgrades, the SMService restarts NEServices.
CSCtc20552: Missing jvm parameter in jnet.

The following caveats are fixed in CTM R9.0.0.600.8:

CSCsq26342: The getHistoryPMData API takes longer than 15 minutes to return data.
CSCsr48358: The prune_ne_ipaddress script does not work with IPv6 addresses.
CSCsu68317: The northbound CORBA interface returns incorrect cross-connect table information.
	    The getAllCrossConnections API returns a CTP name retrieved by a VC-12 circuit in the format
	    /sts3c_au4-j=62/vt2_tu12-k=0-l=0-m=0.
CSCsv12810: An MGX is added to a CTM server, but is not included in the Auto Backup process.
CSCsv33266: If you perform a span switch from the Link Utilization table, the switch does not work for all
	    circuits listed in the table.
CSCsw22308: VT1.5 PM information is displayed incorrectly for DS3XM-12 cards. The VT PM information is shown with 
	    incorrect numbers, making it impossible to tell which VT the PM data is for.
CSCsw68952: A database export fails with the following error: "ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier."
CSCsw72207: The Protection panel shows the wrong name for an OTU2_XP card.
CSCsw91974: In a large network of GNEs and ENEs, CTM fails to collect PM data.
CSCsx22431: For OCHNC circuits, CTM reports a nonexistent value of 59.98 as the wavelength value. CTC reports
	    the correct wavelength value.
CSCsx23360: An alert about a security violation on granting EXECUTE privileges on UTL_FILE packages appears in the Oracle
            Enterprise Manager or the Alert Log.
CSCsx26527: The CTM Link table shows valid and active phantom links, but the corresponding links in the NCP CTM layer
	    do not exist.
CSCsx38325: The first database export from the CTM GUI fails.
CSCsx44115: The CTM server does not send SNMP traps or get IPv6 destinations. The following problems occur:
	    - CTM does not retrieve Ethernet CoS PM data on ML cards from IPv6 NEs.
	    - The SNMP gateway does not forward traps to IPv6 hosts.
CSCsx50126: Due to security issues, CTM must support Apache web server version 2.2.11.
CSCsx50161: The Apache Tomcat software should be disabled to avoid potential security issues.
CSCsx52433: From the MGX Voice Gateway Configuration Center, the Circuit Identifier field is blank for DS1 and SONET
	    lines on a VXSM card. Also, utilization counters are not enabled in the Diagnostics Center > Resource Control tab.
CSCsx55667: The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an exception with the
	    message "no rows from db."
CSCsx56687: The SPAN_BS_TABLE database table displays incorrect working and protected values.
CSCsx64513: A warning message of a possible traffic impact appears when reconfiguring circuits. This warning message 
	    should not appear, because reconfiguring circuits does not affect traffic. 
CSCsx81985: During intensive database usage, Archive Log pruning does not efficiently remove files from the /db05
	    directory.
CSCsx93323: CTM displays a "Media Gateway Link state, pendingIs" alarm with a severity set to Warning. 
	    In other Element Managers, this type of alarm has a severity set to Major.
CSCsy14909: A VLAN range cannot be added on a 10GE_XP/GE_XP card.
CSCsy29600: CTM does not receive data from managed MGX devices.
CSCsy56348: Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
CSCsy83061: From the NE Explorer > SVLAN tab, GE_XP SVLAN configuration settings are not always applied for release 8.0 NEs.
CSCsz33838: Cannot add drops on GT3 cards configured in Automatic mode.
CSCsz53477: The Error Log contains multiple errors that are similar to the following:
	    CTMError : Got Exception in CerentObject::getShelfForEntities for CTC Index : 70290  
CSCsz58653: Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit wizard.
CSCta30577: The CTM server aborts automatically because the Implementation Repository (IMR) service is not running. 
CSCta69422: The ONS 15305 NE Service hangs, and if you try to mark NEs as In Service or Out of Service, CTM returns the 
            following error message: "EID-542: Database error: Cannot modify the NE state."
	    (Related caveat ID: CSCta27875)
CSCta69424: If NE releases earlier than 9.0 are present in the selection context during SVLAN discovery process, the 
	    CTM client freezes.

For detailed caveat information, see the Release Notes for Cisco Transport Manager R9.0 at
http://cisco.com/en/US/products/sw/opticsw/ps2204/prod_release_notes_list.html.

Alternately, if you have a Cisco.com account and a Cisco service contract, you can use the Bug Toolkit to reference 
and monitor all caveats recorded against this product, including those recorded subsequent to the publication of this 
document. To access the Bug Toolkit, visit http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.

CTM R9.0.0.690.2 is intended for customers who are currently using one of the following:

- CTM R9.0.0.507
- CTM R9.0.0.580
- CTM R9.0.0.581
- CTM R9.0.0.600
- CTM R9.0.0.604
- CTM R9.0.0.620
- CTM R9.0.0.645
- CTM R9.0.0.646
- CTM R9.0.0.648
- CTM R9.0.0.649
- CTM R9.0.0.650
- CTM R9.0.0.670
- CTM R9.0.0.680

Note: Install CTM R9.0.0.690.2 only in a non-high availability setup. If you are using a high availability
setup, contact your Cisco account representative before installing CTM R9.0.0.690.2.

Complete the following procedures to upgrade to CTM R9.0.0.690.2.


Determining What CTM Release Is Currently Installed in the CTM System
---------------------------------------------------------------------

To check your current CTM release, log into the CTM server as the root user and enter the
following command:

showctm

The first line of the output shows the release number. Before proceeding, make sure that the 
output results to one of the following:

- Cisco Transport Manager Server Version: 9.0 Build: 507
- Cisco Transport Manager Server Version: 9.0 Build: 580
- Cisco Transport Manager Server Version: 9.0 Build: 581
- Cisco Transport Manager Server Version: 9.0 Build: 600
- Cisco Transport Manager Server Version: 9.0 Build: 604
- Cisco Transport Manager Server Version: 9.0 Build: 620
- Cisco Transport Manager Server Version: 9.0 Build: 645
- Cisco Transport Manager Server Version: 9.0 Build: 646
- Cisco Transport Manager Server Version: 9.0 Build: 648
- Cisco Transport Manager Server Version: 9.0 Build: 649
- Cisco Transport Manager Server Version: 9.0 Build: 650
- Cisco Transport Manager Server Version: 9.0 Build: 670
- Cisco Transport Manager Server Version: 9.0 Build: 680


Backing Up the CTM Database Before Installing CTM R9.0.0.690.2
--------------------------------------------------------------

Before installing CTM R9.0.0.690.2, it is strongly recommended that you back up the existing database.
To back up the CTM database, refer to the following sections in Chapter 4 of the Cisco Transport Manager
Release 9.0 User Guide:

- Backing Up the CTM Database from the CTM GUI
- Backing Up the CTM Database from the CLI


Downloading CTM R9.0.0.690.2
----------------------------

Step 1: Go to http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875317.

Step 2: At the Select a Product screen, expand Cisco Transport Manager.

Step 3: Click Cisco Transport Manager 9.0.

Step 4: At the Log In screen, enter your registered Cisco.com username and password; then, click Log In.

Note: If you do not have a Cisco.com username and password, you can register for them at
http://tools.cisco.com/RPF/register/register.do.

Step 5: At the Select a Release screen, click Expand all and click 9.0.0.690.2.

Step 6: In the right pane, click Download Now.

Step 7: At the Download Image screen, click Proceed With Download.

Step 8: At the License Agreement screen, read the terms of the license agreement and click Agree.

Step 9: At the Select a download option screen, select one of the following options:

- Download Manager Option: If you have Java version 1.4.2.xx installed on your computer.

- Non Java Download Option: If you do not have Java installed on your computer.

Step 10: Download the CTM9.0.0.690.2.patch.zip file to a temporary directory (such as /temp) on the CTM server.

Step 11: In Solaris, enter the following commands to extract the file to the temporary directory:

cd /<directory_name>
unzip CTM9.0.0.690.2.patch.zip

For example, to extract the file to the /temp directory, enter:

cd /temp
unzip CTM9.0.0.690.2.patch.zip

This creates a directory called 690, which contains all CTM R9.0.0.690.2 files.

Step 12: Enter the following command to enter the directory:

cd 690

Step 13: In Windows, download the CTM9.0.0.690.2.patch.zip file to the client workstation. Extract the file using a 
tool such as WinZip, as follows:

a. Open the CTM9.0.0.690.2.patch.zip file in WinZip.

b. Click the Extract button.

c. Verify that the Use folder names check box is checked.

d. In the Extract to drop-down list, select the location where you want to extract the files.

e. Click Extract.


Installing CTM R9.0.0.690.2 on the Server
-----------------------------------------

To apply CTM R9.0.0.690.2 to the server, complete the following steps:

Step 1: Connect to the CTM database as an oracle user.

Step 2: To verify the required Oracle patch is installed, enter the following command:

$ORACLE_HOME/OPatch/opatch lsinventory | grep 7291739

If the output lists the 7291739 patch as one of the patches installed, go to Step 3.
If the output does not list the patch, you must install the Oracle 7291739 patch. See the 
"Installing the CTM-Supported Oracle Patch 7291739" section in the Release Notes for 
Cisco Transport Manager Release 9.0.

Step 3: If you are installing CTM R9.0.0.690.2 and Oracle on separate workstations, you must enable the 
remote shell (rsh) on the server. Complete the following substeps:

a. Enter the following command to verify that the rsh is enabled:

rsh <database_workstation_IP_address> ls

b. If an error is returned, open a shell on the database workstation and edit the /.rhosts file. 
As the root user, enter the following commands to modify the /.rhosts file:

# cat >> /.rhosts << EOF
<CTM_server_workstation_name> root
EOF

where <CTM_server_workstation_name> is the hostname of the CTM server workstation.

Step 2: Notify all CTM users before shutting down the CTM server:

a. In the Domain Explorer window, choose File > Notify Users. The Notify Users dialog box opens.

b. In the Message Targets area, click the All CTM Users radio button.

c. Type the message in the Message area. Customize the message as appropriate for your organization; for example:

The CTM server will be shut down in 5 minutes. Please log out of the CTM client before then.

d. Click Send.

e. Wait an appropriate amount of time for the CTM users to log out.

Step 3: At the end of the grace period, log out all CTM clients:

a. Log into the CTM server using an account with SuperUser privileges.

b. In the Domain Explorer window, choose Administration > CTM Users.

c. In the CTM Users table, choose Administration > Logged In CTM Users.

d. In the Logged In CTM Users table, select a user and choose Administration > Log Out User (or click the Log Out User tool).

Note: This menu option is disabled if you selected your own session.

e. Click Yes at the following prompt:

This operation will log out the selected CTM user. The process will take approximately 1 minute and this CTM client 
will be unusable until then. Do you wish to continue?

Wait until the CTM server completes the operation. The CTM GUI is frozen for approximately 1 minute until the
request is complete. Log out all users listed in the Logged In CTM Users table to make sure that all user
sessions are terminated.

Step 4: As the root user, enter the following command at the UNIX prompt to stop the CTM server:

ctms-stop

Step 5: Enter the following command in the directory where CTM R9.0.0.690.2 was extracted:

./server_patch.sh

Note: Depending on the size of the database, the script might take a while to complete. Do not interrupt 
the script before it finishes.

Step 6: As the root user, enter the following command at the UNIX prompt on the CTM server workstation to 
start the CTM server:

ctms-start

Step 7: As the root user, enter the following command at the UNIX prompt on the CTM server workstation to 
verify the CTM R9.0.0.690.2 installation:

showctm

You should see the following version string in the first line of output for the preceding command:

Cisco Transport Manager Server Version: 9.0 Build: 690 Patches: 2


Installing CTM R9.0.0.690.2 on a Microsoft Windows Client
---------------------------------------------------------

Note: If you want to install the CTM client with Cisco Edge Craft 2.2.2, you must install the CTM client from the 
CTM R9.0.0.680.3 patch before installing CTM R9.0.690.2. To download the CTM R9.0.0.680.3 patch, go to 
http://www.cisco.com/cisco/software/navigator.html?mdfid=278875317&i=rp. For installation instructions, see the 
Readme for the CTM R9.0.680.3 Patch on http://www.cisco.com/en/US/products/sw/opticsw/ps2204/prod_release_notes_list.html. 

The following steps describe how to patch a CTM client installation in Windows. Before proceeding,
make sure that there are no instances of the client running in the system. To shut down a running client,
choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.

Step 1: Locate the 690 directory that was extracted with the WinZip utility.

Note: If the CTM client is installed on Windows Vista, launch the command prompt as an administrator:

a. Choose Start > All Programs > Accessories.

b. Right-click the Command Prompt icon and choose "Run as administrator."

Step 2: Using the command prompt, go to the directory where CTM R9.0.0.690.2 was extracted,locate the 
client_patch.bat file, and enter the following command:

client_patch

You can also use the Windows Explorer folder view to access the directory where the CTM R9.0.0.690.2 files 
were extracted and double-click the client_patch.bat file. If the CTM client is installed on Windows Vista, 
right-click the client_patch.bat file and choose "Run as Administrator."

Step 3: Double-click the CTM R9.0 desktop icon or choose the CTM R9.0 Start menu shortcut to start the client.

Step 4: To verify the CTM R9.0.0.690.2 installation on the CTM client, do one of the following:

- Choose Help > About Cisco Transport Manager in the Domain Explorer. You should see the following version string 
in the About Cisco Transport Manager dialog box; then, click OK:

Client: 9.0 Build: 690 (client configuration size)

- (Available only on specific user account types) Choose Administration > Control Panel in the Domain Explorer. 
In the Control Panel, click CTM to open the CTM Properties pane. Click the Client Configuration tab. The Version 
field indicates the CTM client version number, which should read:

9.0 [9.0.0.690]


Installing the CTM R9.0.0.690.2 Client Patch on Sun Solaris
-----------------------------------------------------------

Note: If you want to install the CTM client with Cisco Edge Craft 2.2.2, you must install the CTM client from the 
CTM R9.0.0.680.3 patch before installing CTM R9.0.690.2. To download the CTM R9.0.0.680.3 patch, go to 
http://www.cisco.com/cisco/software/navigator.html?mdfid=278875317&i=rp. For installation instructions, see the 
Readme for the CTM R9.0.680.3 Patch on http://www.cisco.com/en/US/products/sw/opticsw/ps2204/prod_release_notes_list.html. 

The following steps describe how to patch a CTM client installation in Solaris. Before proceeding,
make sure that there are no instances of the client running in the system. To shut down a running client,
choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.

Step 1: Go to the 690 directory where the CTM R9.0.0.690.2 files were extracted with the unzip command.

Step 2: Enter the following command:

./client_patch.sh

Step 3: Enter the following command to start the CTM client:

ctmc-start

Step 4: To verify the CTM R9.0.0.690.2 installation on the CTM client, do one of the following:

- Choose Help > About Cisco Transport Manager in the Domain Explorer. You should see the following version string 
in the About Cisco Transport Manager dialog box; then, click OK:

Client: 9.0 Build: 690 (client configuration size)

- (Available only on specific user account types) Choose Administration > Control Panel in the Domain Explorer. 
In the Control Panel, click CTM to open the CTM Properties pane. Click the Client Configuration tab. The Version 
field indicates the CTM client version number, which should read:

9.0 [9.0.0.690]


Installing the CTM-Supported Oracle 10.2.0.4 Patch
--------------------------------------------------

Starting from CTM R9.0.0.690.2, the Oracle 10.2.0.4 patch (see CSCtj72796) is supported. To install the
Oracle 10.2.0.4 patch, complete the following steps.

Note: In a dual-server setup, install the patch on the database workstation.

Step 1: Verify that your server has enough RAM available for your CTM network size. See the Cisco Transport
Manager Release 9.0 Installation Guide, section "Server Specifications" for details.

Step 2: Enter the following command to verify that the CTM R9.1 server is running:

showctm

Step 3: If the CTM server is running, enter the following command to stop it:

ctms-stop

Step 4: Log into the CTM database workstation.

Step 5: As the oracle user, enter the following commands to shut down Oracle:

su - oracle
sqlplus /nolog
SQL> connect / as sysdba
SQL> shutdown immediate
SQL> quit
lsnrctl stop

Step 6: Complete the following substeps to download and install the Oracle 10g 10.2.0.4 patch for Solaris
(patch number 6810189):

a. Go to http://metalink.oracle.com and click Login to MetaLink. Enter your Oracle MetaLink
username and password.

b. Extract the 316900.1 document.

c. Click Advanced at the top of the Oracle MetaLink page.

d. Enter 316900.1 in the Document ID field; then, click Submit. The 316900.1 document provides the
following information:

- System requirements
- Lists of resolved bugs
- List of known issues

e. Click Patches.

f. Click Simple Searches.

g. Enter 6810189 in the Search by Patch Number(s) field.

h. Choose Solaris Operating System (SPARC 64-bit) from the Platform or Language list box.

i. Click Go.

j. Click Download to download the p6810189_10204_Solaris-64.zip file.

k. Enter the following command to log into the Oracle workstation as the oracle user:

su - oracle

l. Save the patch to the /oracle directory.

m. As the oracle user, copy the response file in the /oracle directory.

If you are installing the Oracle 10.2.0.4 patch with 64-bit Oracle Enterprise Edition or 64-bit
Oracle Standard Edition, enter:

cp /<mount_point>/400/config/400/patchset_64bit_10204.rsp /oracle

n. Enter the following command to extract the patch files:

Unzip p6810189_10204_Solaris-64.zip

A directory named Disk1 is created automatically.

o. Remove the p6810189_10204_Solaris-64.zip file from the /oracle directory.

p. Enter the following commands to install the patch:

cd Disk1
./runInstaller -silent -responseFile /oracle/patchset_64bit_10204.rsp

q. At the prompt to run the root.sh script, log into another terminal window as the root user and enter
the following command:

/oracle/product/10.2.0/root.sh

r. At the prompt for the local bin directory, enter the following path in the root.sh script:

/oracle/product/10.2.0/local/bin

Note: You are prompted to overwrite some files. Reply yes to all of the prompts.

s. Enter the following commands to remove the patch installation files:

cd /oracle
rm -rf /oracle/Disk1

Step 7: Complete the following postinstallation steps for the Oracle 10g 10.2.0.4 patch for Solaris
(patch number 6810189):

a. Enter the following command to log into the database workstation as the oracle user:

su - oracle

b. Enter the following command to start the Oracle listener:

lsnrctl start

c. For single-instance installations, enter the following commands to use SQL*Plus to log into the
database as the SYS user with SYSDBA privileges:

$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA

d. Enter the following commands:

SQL> STARTUP UPGRADE
SQL> SPOOL /temp/patch.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> SPOOL OFF

This step might take several minutes to complete.

e. Using another terminal window, check whether the /temp/patch.log report contains any errors. If
errors exist, correct them; then, rerun the catupgrd.sql script.

f. Enter the following commands to restart the database:

SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP

g. Enter the following command to run the utlrp.sql script and recompile all invalid PL/SQL packages
now instead of when the packages are accessed for the first time. This step is optional but
recommended.

SQL> @?/rdbms/admin/utlrp.sql

h. Enter the following command to check the status of all components after the upgrade:

SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;

In the command output, all components should have a status of VALID for a successful upgrade.

Step 8: Complete the following substeps to recompile database views after installing the Oracle 10g 10.2.0.4
patch for Solaris (patch number 6810189):

a. Enter the following commands to verify that the view recompilation has been performed:

su - oracle
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> SELECT * FROM registry$history WHERE ID='6452863';
SQL> QUIT

If the view recompilation has been performed, the preceding commands return one or more rows. If
the view recompilation has not been performed, the commands return no rows.

b. If it is necessary to recompile the views in the database, enter the following commands to run the
precheck script, which reports the maximum number of views and objects that can be recompiled:

cd $ORACLE_HOME/cpu/view_recompile
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @recompile_precheck_jan2008cpu.sql
SQL> QUIT

c. As the oracle user, enter the following commands to run the view recompilation script, if necessary.
Note that this script is run with the database in upgrade mode, which restricts connections as
SYSDBA:

cd $ORACLE_HOME/cpu/view_recompile
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP UPGRADE
SQL> @view_recompile_jan2008cpu.sql
SQL> SHUTDOWN;
SQL> STARTUP;
SQL> QUIT

d. Check for any errors in the vcomp_SID_timestamp.log file in the current directory.

e. If any invalid objects were reported, enter the following commands to run the utlrp.sql script:

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
SQL> QUIT

f. Manually recompile any invalid objects. For example:

SQL> alter package schemaname.packagename compile;

Step 9: Complete the following substeps to download and install the OPatch (patch number 6880880):

a. Go to http://metalink.oracle.com and click Login to MetaLink. Enter your Oracle MetaLink
username and password.

b. Select Patch from the menu and search for the 6880880 patch.

c. Choose Solaris Operating System (SPARC 64-bit) from the Platform or Language list box.

d. Click Go.

e. Click Download to download the p6880880_112000_SOLARIS64.zip file to your local
workstation.

f. Enter the following command to log into the Oracle workstation as the oracle user:

su - oracle

g. Save the patch to the $ORACLE_HOME directory.

h. Enter the following commands to unzip p6880880_112000_SOLARIS64.zip to your Oracle home directory:

cd $ORACLE_HOME
unzip p6880880_112000_SOLARIS64.zip

i. At the prompt asking if you want to replace all files, choose Replace All.

Patch 6880880 is now installed.

j. To verify that you have the Opatch utility installed, enter the following command as the oracle user:

$ORACLE_HOME/OPatch/opatch version
The following messages appear:
Invoking OPatch 11.2.0.1.0
OPatch version: 11.2.0.1.0
OPatch succeeded.

Note: The OPatch version (11.2.0.1.0 or later) is different from the Oracle software version
(10.2.0.4), because they are separate products.

k. Enter the following command to remove the temporary .zip file:

rm $ORACLE_HOME/p6880880_112000_SOLARIS64.zip

Step 10: Enter the following commands to shut down Oracle and the listener:

su - oracle
lsnrctl stop
sqlplus /nolog
SQL> connect / as sysdba
SQL> shutdown immediate
SQL> quit


Installing the CTM-Supported Critical Oracle Patches 9352164 and 9952234
------------------------------------------------------------------------

CTM R9.0.0.690.2 has been tested with the latest critical Oracle patches (see CSCtj72766). To install
the Oracle patches 9352164 and 9952234, complete the following steps:

Step 1: Go to http://metalink.oracle.com and click Login to MetaLink. Enter your Oracle MetaLink username
and password.

Step 2: Select Patch from the menu and search for and download patches 9352164 and 9952234.

Step 3: Extract the README.html file from the Oracle PSU patch .zip file. As you read the README.html file,
note that the CTM database has the following setup:

- Oracle environment: Non-RAC.
- Data Guard Physical Standby database: Not implemented.
- Job Scheduling system: Used.
- ASM instance: Not implemented.
- Initial setup: Oracle 10.2.0.4.0 and CTM R9.0 installed.

Step 4: Refer to the README.html file as you complete the following substeps:

a. Install the PSU patch 10.2.0.4.4. (See the "Patch Installation Instructions" paragraph in the
README.html file. The PSU patch number is 9352164.)

b. As the root user, enter the following command:

sh psu_root.sh

Note: If ORACLE_HOME is not set, the psu_root.sh script fails. By default, the
$ORACLE_HOME directory is /oracle/product/10.2.0.

c. Check for any one-off patch conflicts with the PSU patch 10.2.0.4.6. (See the "One-Off Patch
Conflict Detection and Resolution" paragraph in the README.html file.)

d. Install the PSU patch 10.2.0.4.6. (See the "Patch Installation Instructions" paragraph in the
README.html file. The PSU patch number is 9952234.)

e. Enter the following command to load the modified SQL files into the database. (See the "Loading
Modified SQL Files into the Database" paragraph in the README.html file.)

catbundle.sql psu apply

f. Enter the following commands to recompile views in the database. (See the "Recompiling Views in
the Database Instructions" paragraph in the README.html file.)

recompile_precheck_jan2008cpu.sql
view_recompile_jan2008cpu.sql
utlrp.sql

- (Available only on specific user account types) Choose Administration > Control Panel in the Domain Explorer.
In the Control Panel, click CTM to open the CTM Properties pane. Click the Client Configuration tab.
The Version field indicates the CTM client version number, which should read:

9.0 [9.0.0.690]