Find Answers

Filter Search Results
All Operating Systems:
All Windows (2)
All Products:
Release Manager (88)
All Solution Types:
Documentation Update (1)
Error Message (5)
Installation & Customization (4)
Product Tips & Advice (2)
Source:
Defects (79)
Solutions (9)
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML SBM 11.3 upgrade fails with ORA-04080 error
SBM 11.3 upgrade fails with ORA -04080 error
CMS-XML Notification Server log contains ORA-01795: maximum number of expressions in a list is 1000
Notification Server log contains ORA -01795: maximum number of expressions in a list is 1000
CMS-XML TBI errors out with "ORA-00001: unique constraint violated"
TBI errors out with " ORA -00001: unique constraint violated"
CMS-XML 2009R2 : Promote/deploy request fails with db error: ORA-00942: table or view does not exist
2009R2 : Promote/deploy request fails with db error: ORA -00942: table or view does not exist
CMS-XML ORA-28040: No matching authentication protocol
ORA -28040: No matching authentication protocol
CMS-XML KM-Dim10: Reported Defects DEF113979: querying published view error date type null value not handled ORA-01843: not a valid month
KM-Dim10: Reported Defects DEF113979: querying published view error date type null value not handled ORA -01843: not a valid month
CMS-XML Dim CM 2009 R2: Upgrade from Dimensions CM 10.1.x to 2009 R2 fails with "ORA-00936: missing expression" error
Dim CM 2009 R2: Upgrade from Dimensions CM 10.1.x to 2009 R2 fails with " ORA -00936: missing expression" error
CMS-XML DIM2009R2 - Error viewing Secondary catalogue - SQL-904(02A59398) ORA-00904: "CMPRJSPECS"."PROJ_SPEC": invalid identifier
DIM2009R2 - Error viewing Secondary catalogue - SQL-904(02A59398) ORA -00904: "CMPRJSPECS"."PROJ_SPEC": invalid identifier
CMS-XML Unsuccessful Alter Table SWC_ ... referential constraint already exists. After an upgrade ORA-02275
Unsuccessful Alter Table SWC_ ... referential constraint already exists. After an upgrade ORA -02275
CMS-XML Long ts_internalname and/or ts_name doesn't work with AppScript with Oracle db
When referencing ts_name or ts_internalname in ts_states with an app script, if either is over 30 characters, it fails with " ORA -00972:Identifier is too long" which is due to an Oracle limitation. It appears we accommodate this limitation in other areas in Composer when creating names/internal names, States can still be created with long names/internal names.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs