Find Answers

Filter Search Results
All Operating Systems:
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Cross-Site Scripting (XSS) vulnerability in Version Manager Web Client (VM I-Net)
We have released a HotFix for VM 8.4.6 and VM 8.5.0 to mitigate these issues. If you are running VM 8.5.0, please download the patch from KB article P2710 . If you are running VM 8.4.6, please download the patch from KB article P2709 .
CMS-XML HP-UX patch breaks Version Manager running in setuid mode
The short term workaround is to roll back the offending patches (also see HP's e-mail). The long term solution is to install one of two new patches from HP, once they become generally available:
CMS-XML StarBat: Runtime EXEC parameter PARM='RC=0' no longer supported
has been enhanced to allow user customization. By customizing the new StarBat Return Code Table, users can tailor StarBat return code processing both globally throughout StarBat and locally on a function -by- function basis. With this return code table, the StarBat runtime EXEC parameter PARM='RC=0'
CMS-XML Required maintenance for ZMF customers running ZMF 7.1.x.
Required maintenance for ZMF customers running ZMF 7.1.x.
CMS-XML ZMF 5.6.x: Potential for incomplete restore when running CMNBKRST with recovery records.
ZMF 5.6.x: Potential for incomplete restore when running CMNBKRST with recovery records.
CMS-XML VM 8.2.0.x - Running Show Differences on a workfile may cause the workfile to get deleted
VM 8.2.0.x - Running Show Differences on a workfile may cause the workfile to get deleted
CMS-XML Scripts may get truncated on upgrade from TT 6.6.1 to SBM 2.03, 2.04 or 2.05
Scripts may get truncated on upgrade from TT 6.6.1 to SBM 2.03, 2.04 or 2.05
CMS-XML Do NOT Run vsplit -u (unsplit) on Archive Paths that Contain Double-Byte Characters on pre-8.1.3.1 releases
Do NOT Run vsplit -u (unsplit) on Archive Paths that Contain Double-Byte Characters on pre-8.1.3.1 releases
CMS-XML ALERT - possible Oracle data loss if upgrading from TeamTrack directly to SBM 2008 2.03, 2.04, 2.05 or 2009 R1
then it is likely that you will experience data loss on the database upgrade. Workaround: When upgrading from TeamTrack the Unicode Upgrade Utility is a one-off utility run so to avoid this issue upgrade your database to 2008 R2 first and only then apply the patch or upgrade to 2009 R1(first GA build - no longer available for download).
CMS-XML KM-Dim: Serena Dimensions Oracle Patch Upgrade Policy
In Serena's experience, it is unlikely for any Oracle security patch to break or hinder an existing application relying upon that Oracle. If problems are encountered, the Oracle DBA would be expected to already have a backup/recovery strategy planned in the event that a critical business application no longer operates successfully.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs