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 DIM10: Upgrade to Dimensions CM 10, now gets error when browsing change requests: SQL-24812(4207) ORA-24812: character set conversion to or from UCS2 failed
If this problem seems to be related only to change requests , the possible workaround may help. It has worked for some customers.
CMS-XML KM-Dim9: Creating Change Document get error: 1019, ORA-00001 unique contraint on CM_IMPACTS_PK and 1226
NOTE: On the 2 nd line below, replace "INTERMEDIATE" with the name of the base database with which you are having the problem. dmdba system/<password>@<dsn> SYSTEM> connect INTERMEDIATE
CMS-XML KM-Dim7: PDIFF returns error when used with Dump Change Documents: 1019-DBIO: ORACLE Error occurred SQL-0438(4120) ORA-01841: (full) year must be between -4713 and 9999, and not be 0
2 . Check the regional options setting of your environment (this should be set to (ENGLISH) United Kingdom) 3. Prior to running the PDIFF you must set the variable NLS_DATE_LANGUAGE to AMERICAN from the prompt command e.g. set NLS_DATE_LANGUAGE=AMERICAN
CMS-XML KM-Dim10: During Create Change Document get ORA-00904: "I_SITE_NO": invalid identifier
2 ) Determine which sequence number should be used going forward. Substitute the correct product ID and change document type into the following query. Each time run, this will produce 1 or 2 numbers, just note the higher of the two numbers for each change document type.
CMS-XML KM-Dim9: Error: ORA-00001: Unique constraint (.CM_DBFILES_K1) violated
This problem is caused by two users accessing the same change document at the same time. Usually one user has actioned the document while the other is adding an action description. The resulting problem is caused by inconsistent values in tables CM_DBFILES and CM_CATALOGUE.
CMS-XML KM-Dim7: Error: ORA-02292: integrity constraint violated - child record found
SQL> exit 2 Move the change document 3 enable the constraint using the following
CMS-XML Dim10: Error ORA-00001 when creating a request
- slide 2 : now assume we give twice the role TEAM_LEADER to user USER2 one time with capability PRIMARY and other time with capaibility SECONDARY in REAL type - slide 3 : after logging with user 2 to intermediate, we create a CR request and then we get the ORA -0001 error - slide 4 : we go back to the admin console and we remove one role of the two
CMS-XML DimCM: 14.5.x: DBI4502374E SQL-2289(39826) ORA-02289: sequence does not exist
CR Type "QLARIUS:CR", Curr Seq 35. CR Type "QLARIUS:MRG", Curr Seq 2 . CR Type "QLARIUS:TASK", Curr Seq 17.
PDF Serena Release Manager Installation and Configuration Guide
dashboard configuring 72 reports 73 databases MySQL, for Nolio 43 Nolio 43 Oracle , for Nolio 43 requirements, Nolio 12 Serena Release Automation 43 SQL Server, for Nolio 43 default owners for SBM projects 31 deployment history 104 log files 105 results 104 deployment unit provider specifying 44 deployment units Dimensions CM, filtering 45 implementing provider for 92 Serena Release Vault, filtering 45 specifying providers for 44 development change request provider specifying 44 dialogs configuring 76 reports 76 Dimensions CM deployment units, filtering 45 installation 19 on shared server 20 port, Serena Common ...
CMS-XML KM-Dim10: After upgrading to Dimensions 10.1.1 desktop client gives error when browsing change requests: DBIO004527E DBIO: Database I/O error occured. SQL-904(83081) ORA-00904: "A"."IS_TIP_REVISION": invalid identifier
KM-Dim10: After upgrading to Dimensions 10.1.1 desktop client gives error when browsing change requests : DBIO004527E DBIO: Database I/O error occured. SQL-904(83081) ORA-00904: "A"."IS_TIP_REVISION": invalid identifier
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs