Patch Name: PHSS_28293 Patch Description: s700_800 11.X OV SA1.02 FMS Patch-6 Creation Date: 02/12/12 Post Date: 02/12/13 Hardware Platforms - OS Releases: s700: 11.00 11.11 s800: 11.00 11.11 Products: OpenView Service Assurance 1.02 FMS Filesets: OVCA_fmsRT.OVCAFMS-RUN,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP Automatic Reboot?: No Status: General Release Critical: No Category Tags: defect_repair general_release Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28293 Symptoms: PHSS_28293: Cumulative Consolidated Patch PHSS_28286: PTSfc01157: If the license file is corrupted, NSM exits without logging any error message either in NSM log or in syslog. PTSfc01718: If the outage is created for an NE which already has alrams associated to it, and if the NE's object status is observed after the outage, it will be NORMAL in the Map presenter whether it receives alarms during outage or not. PTSfc02529: When fmsmhexport is used to export a topology tree beginning with an fdn which contains spaces in it, then the export operation fails. Example FDN for which the export was failing: /cellnet-id="cellnet"/nokiamsc-id="test msc". PTSfc02806: ovfmpmdimdd dumps core sometimes, when receiving alarms containing additional text. PTSfc02932: fmsprobsvr sometimes dumps core, when the rate of alarms coming into the FMS sub-system is high. PTSfc02889: MO manager dumps core in case of managed object identifier size less than three for managed object scope in filter file. PTSfc02972 fmsprobsvr stops processing alarms causing build-up of data in pipes under $FMSVAR/pipes/, subsequently leading to a stoppage of alarm processing by the OVC/Assurance system as a whole. PTSfc02195 In some cases (when own of a problem is tried as soon as the problem arrives or is updated), while trying to own a problem an error "Fail to retrieve alarm data from alarm table" is displayed. If the operation of owning the problem is tried again, the error message "Problem Already owned" is displayed. PTSfc02997 ovfmpevcd process dumps core at startup. PTSfc03012: Standard(M3100) local probable cause values in integer form are being displayed as in the problem presenter. PHSS_27492: Consolidated Patch PHSS_27485: PTSfc02828: Configuration of OVC/Assurance 1.02 with patch-4 fails giving the following error message, "ORACLE_HOME is not set or Unknown ORACLE Version", inspite of the ORACLE_HOME being set correctly and the underlying Oracle being one of the supported versions, 8.1.7 or 8.0.6. PTSfc02622: When the Oracle database becomes full, the 'fmsprobsvr' begins to drop new problems received from then on and the following error messages are seen in the 'alert_fmsdb.log' file: ORA-1654: unable to extend index by in tablespace " PTSfc02768: When an MO is deleted, the problem presenter still shows the active problems associated with it. Also if the MO had pending or active outages before it's deletion, recreation of the same MO and subsequent submittal of outages for that MO fails. PTSfc02872: Alarms created or modified by the ECS circuits are only seen in the existing Problem Presenters. New Problem Presenters does not have these new alarms. In addition, during an alarm storm, some alarms are not seen in the Problem Presenter. PHSS_26437: Consolidated Patch PHSS_26429: PTSfc02533: OVC/Assurance is not supported with ORACLE 8.1.7 on HP-UX 11.00 and HP-UX 11.11. PTSfc02532: Outage creation fails in a machine with ORACLE 8.1.7 PTSfc02479: During an alarm storm or restart of MD, FMS receivs duplicate alarms. PTSfc02329: Second or subsequent transient object creation doesn't propagate its status to its parent. PTSfc02379: The fmsmhimport of object with RDN value lenght greater than 60 characters fails. PTSfc02460: The object with indeterminant severity is shown as normal object in the Map. PTSfc02228: Alarm on Transient objects are propagated with 'wrong' alarm status.Transient objects are not disappearing after discharging all the problems associated with it. PTSfc02250: fmsmhimport fails with core dump of oemfmoihndlr while deleting an NE node. PTSfc02546: get_problem_data_by_filter() IDL operation of Problem manager takes more than expected time PTSfc02554: The MOManager IDL opertaions get_mo_data_by_name() and get_mo_data_by_filter() do not return transient objects' data. PHSS_25806: Consolidated Patch PHSS_25800: PTSfc02267: problem.sql.create has been modified to create additional index tables. The initial extent values have been set to a higher value as a result of which running fmssysconfig may fail if default values are chosen. PTSfc02257: After installing TGF patch 17, fmsmhpdbimport dumps core. The log file /var/opt/OEMF/V5.0/FMS/share/log/ oemfmhtgferr.log points to an unresolved symbol in /opt/OEMF/V5.0/ilog/tgf/lib/ libiltoracl.sl. PTSfc01873: fmsopfix and fmsopcfg does not startup after a fmsopcfg session failure. This happens after importing a topology file with group domains in the file. PTSfc02275: The files under the directory $FMSETC/share/ newconf/ will be copied, even though the files are empty, to $FMSETC/share/conf while running the command fmscfgsync -conf -l all PTSfc02293: MOIs containing colon(":") are not handled properly by the IMDD process. Only a portion of the string after the colon (":") character in the MOI gets logged into the database. PTSfc02274: Inconsistency between NSM data base and Problem database for each MO (non-transient) in terms of the number of active problems. PHSS_25335: Consolidated Patch PHSS_25327: PTSfc01665: Problem server core dumps on exit PTSfc01804: Status Propagation based on Ownership failed to work.if a problemCondition that is owned, is updated with a new event, then the status of that event is propagated. The only way to get the status of the map object back to 'Clear', is to disown and own that particular problemCondition. PTSfc01812: GUI alarm window shows transient and related alarms when choosing the show related option. PTSfc01853: Doing a fmsmhexport fails after several hours with the following error and no export file is created: NOTE : Exporting OEMF full topology info to /var/opt/OEMF/V5.0/FMS/export/ManagedObject/oemfdb.expor t file... It will take a while. Please be patient... NOTE : Export of OEMF tree topology failed. Please check the OV Error Log file. No export has succeeded after loading 125000 managed objects. oracleguidb process takes more CPU than oemfmoihndlr. PTSfc02014: PM crashed atleast twice at Vodacom. Initial investigation suggests that the crash happened while doing swapout of the problems PTSfc02015: delete/add operation improvement PTSfc02036: Problem manager dumps core after a memory growth equals MAX_DSIZ complaining alarm not found.To be done later on PTSfc02037: The FMS Alarmbackup script is not working any more. See details: Please enter the number of days and hit enter. For default value, only hit enter. Days: 1 FMS ALARM BACKUP It seems that last backing up was not successful. Begin check/rectify ... Completed successfully The data between 19-06-2001-00:00:00 and 24-07-2001- 00:00:00 is going to be backed up. Are you going to proceed? (y/n) y Begin backing data for period 19-06-2001-00:00:00 to 20-06- 2001-00:00:00 to file /var/opt/OEMF/V5.0/FMS/backup/alarms/BACK19-06-2001- 1.dmp ... SQL> SQL> 2 3 4 5 6 7 8 9 10 11 12 13 14 Error Number : -1555 Error Message: ORA-01555: snapshot too old: rollback segment number 2 with name Oracle error occurred This happensfor all subsequent backups PTSfc02057: The defect occurs when a FMS machine in a multi-site installation is down for more than 10 minutes. When the machine is brought back online other machines in the installation appear to hang. PTSfc02058: Defect only occurs in installations with more than 1 FMS. If one machine in the installation is down for more than 10 minutes than notification filters can be leaked when the machine is brought back online. PTSfc02092: AV time format is not configurable, default is confusing. The fomat that the Update Time, Create Time, and other times from the database are presented in the Web Alarm Viewer is confusing. It is a 12-hour time without any AM or PM entries. The date is also in MM/DD/YYYY format, which is not useful internationally.The best solution would be to allow the time format to be configured or to default to the localization options of the WAV server. If this cannot be done, then the time should default to a 24-hour format with the date presented as dd-MMM-yyyy (01- JAN-2001) PHSS_24597: PTSfc01455: ICE Client generates the following error when calling registerNotif: ORBMaster/InvalidConstraint:OpenView LOCAL_MINOR, Message> >|2001:07:18:18:47:41:652:265|ORBMa ster/InfrastructureError/OpenView|LOCAL_MAJOR|OpenView|vodf ms1|id:(1776819767:6377768)|link:(1776819767:6377767) |fmsprobsvr|>