Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Fix Log for version 5.7.0
IP address being picked up by License Other- Server not deleting temporary vcs* files when they are not needed Other- Approval/Rejection Comments Entered Via ECP Are Not Updating In Database Other- Branch of frozen release causes an error: [ Oracle ][ODBC][ Ora ] ORA - 00001 : unique constraint (SERENA.DEPEND_KEY)
CMS-XML Dim cm 14.4: patch 14.4.0.22 for Windows and Linux server
DEF313553: Max UID in columns in table JOB_QUEUE - PRES_LOG_ITEM_UID and PRES_LOG_WSET_UID contain invalid values DEF312013: ORA - 00001 : unique constraint (SA.VRS_2_PIC_PK) violated running CRB 3 COPYRIGHT, TRADEMARKS AND ACKNOWLEDGMENTS
CMS-XML Upgrade to SBM 11.0 and above with Oracle Database gives error- Error: ORA-00904: : invalid identifier
when matched then update set b.TS_HASH=r.h'. Error: ORA -00904: : invalid identifier
CMS-XML Minimum privileges required for the Oracle user connecting to an SBM schema
The following privileges are required for creating a new SBM database or upgrading an existing one. Caution:
CMS-XML Clarification of Oracle requirements for ChangeMan DS 5.7.0
Note: Oracle 10g is supported with new installations only, not with upgrades . Clarification is needed on the note.
HTML Serena® Collage® Version 5.1.3 Release Notes
1.5 Database (ENH104624) To improve deployment performance with Oracle, the "Analyze" query in the GatherTableStatistics stored procedure should be replaced with the dbms_stats package. (DEF115818) When upgrading to Collage 5.1.2 on Oracle , the database cannot be upgraded and an error like the following appears: STS 2007/06/21 08:09:11 PDT-- Connection: Upgrading database ....v242 to v243
CMS-XML Readme for SBM 10.1.1.1 as of 12th April 2012
Important: The underlying driver used in the "Oracle for SBM" DSN that ships with SBM has changed in SBM as of version 10.1. If you currently use the Mashup2009 DSN with SBM, you do not need to do anything. If you created your own custom DSN with the " Oracle for SBM" driver prior to upgrading to SBM 10.1 or later, then you must recreate the DSN and use the new " Oracle for SBM" driver that ships with SBM after the upgrade is finished.
CMS-XML Readme for SBM 10.1 as of 9th February 2012
Important: The underlying driver used in the "Oracle for SBM" DSN that ships with SBM has changed in SBM 10.1. If you currently use the Mashup2009 DSN with SBM, you do not need to do anything. If you created your own custom DSN with the " Oracle for SBM" driver prior to upgrading to SBM 10.1, you must recreate the DSN and use the new " Oracle for SBM" driver that ships with SBM 10.1.
PDF Serena Collage Installation and Setup Guide
If you upgraded an existing installation of Collage, and you are now using your own installation of Oracle or Microsoft SQL as your database server instead of the bundled Sybase server, you must migrate your existing projects from Sybase format to Oracle or Microsoft SQL format. When you migrate a project, Collage copies all of your project data to the new database format, so that you can continue to use your existing projects on the new database server.
CMS-XML ORA - 04030 out of memory when trying to allocate
ORA - 04030 out of memory when trying to allocate
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs