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 SBM 11.0 Beta - ORA-00001: unique constraint for CL
After the upgrade , customers need to run following script and restart server: drop table CL_CONFIG; drop table CL_SETTING;
CMS-XML Upgrading SBM with oracle database from 10.1.3 GA:"TS_ID": invalid identifier in swc tables
ORA - 00001 : unique constraint (SAMPLE.TKTS_TABLES) violated
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 SBM 11.3 upgrade fails with ORA-04080 error
ORA -04080: trigger 'TRG_CP_TO_REL_CHANGEACTIONS' does not exist The AE upgrade will expect the following SQL to succeed: drop trigger TRG_CP_TO_REL_CHANGEACTIONS
CMS-XML Oracle database upgrade error from TT 6.6.1 to 2009 R4 - "Number of bound columns exceeds the number of result columns"
Oracle database upgrade error from TT 6.6.1 to 2009 R4 - "Number of bound columns exceeds the number of result columns"
CMS-XML EM_* tables are not correctly upgraded for Oracle on and then deploy of Event Map fails
EM_* tables are not correctly upgraded for Oracle on and then deploy of Event Map fails
CMS-XML Upgrade DB to SBM 10.1.4 from TT 661 on Oracle fails
If you have such a problem when upgrading a TeamTrack database on Oracle , then the steps to be followed are these : Remove 10.1.4 completely from the system Install 10.1.2.2
CMS-XML Application Engine upgrade could not access the DBMS_CRYPTO library
Oracle Error: --> Error at line 1 --> ORA -00904: invalid identifier
CMS-XML Application Engine database log contains "ORA-00904: "DBMS_CRYPTO"."HASH": invalid identifier" message
The Application Engine upgrade could not access the DBMS_CRYPTO library to add SHA-1 hashes for resource files to the TS_BLOBS table. This is not an error, as these hashes are eventually created at runtime if they are not added now. However, some upgrade steps, deploy steps, and IIS startup may be temporarily slower until the Application Engine creates these hashes.
CMS-XML Trend report may not work after upgrade to 11.0+ - error begins with - Database exception in CReportExecTrend::ExecuteDataCollection() using SQL:
ORA -00904: "TSM_INCIDENTS"."TS_ID": invalid identifier
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs