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 Notifications are not being fired, since upgrade to SBM 10.1 or later, when populating TS_NOTIFICATIONEVENTS programmatically
Since upgrade to SBM 10.1 there is going to be a change needed if you are writing to TS_NOTIFICATIONEVENTS by some external means. There is a new field TS_ACTIONSTAMP in this table and if this is NULL then you will get the following error in the ns.log and the event will not be processed by the Notification Server :
CMS-XML State Change History is Missing After Running Data Imports
SELECT COUNT(*) AS Expr1 FROM TS_CHANGES WHERE ( TS_ACTIONSTAMP NOT IN (SELECT TS_ID FROM TS_CHANGEACTIONS));
CMS-XML Errors in ns.log - An error occurred while adding an event to the Events table ... Nested exception: org.springframework.dao.DataIntegrityViolationException: could not insert ... Caused by: org.hibernate.exception.ConstraintViolationException ... Violatio
SQL [insert into TS_NOTIFICATIONEVENTS (TS_TABLEID, TS_CASEID, TS_WORKFLOWID, TS_NOTIFICATIONID, TS_PRIORITY, TS_STARTDATE, TS_TIME, TS_WAITSTATUS, TS_RECIPIENTID, TS_LASTCHANGEDATE, TS_ELAPSEDCYCLES, TS_THREADID, TS_SENDTYPE, TS_ACTIONSTAMP , TS_CRONEXP, TS_LASTCRTRIGGEREDDATE, TS_DELAYED
CMS-XML Process the 10.x notification server uses to configure the database from a previous version of SBM/TT
create sequence ns_sequence; ALTER TABLE TS_NOTIFICATIONMESSAGES ADD TS_ACTIONSTAMP number(10,0); ALTER TABLE TS_NOTIFICATIONMESSAGES ADD TS_THREADID VARCHAR2(100) NULL;
CMS-XML Indexes in Serena Business Mashups
TI_ACTIONSTAMP_CHANGES TS_ACTIONSTAMP TS_CHANGETEXT
PDF TeamTrack Database Schema
TS_CALENDARDENORM TI_CALID_CALENDARDENORM_SD_ED_ET TS_CALENDARID TS_STARTDATE TS_ENDDATE TS_ELAPSEDTIME TS_CHANGEACTIONS TI_ITEMID_CHANGEACTIONS TS_ITEMID TS_CHANGEACTIONS TI_TIME_CHANGEACTIONS TS_TIME TS_CHANGES TI_CASEID_CHANGES TS_CASEID TS_CHANGES TI_CASEID_CHANGES TS_FLDID TS_CHANGES TI_TIME_CHANGES TS_TIME TS_CHANGES TI_ACTIONSTAMP_CHANGES TS_ACTIONSTAMP 35
PDF Microsoft Word - schema.doc
Because of the way the trend report algorithm works, the system also stores one row per field when an issue or incident is submitted. Change History records are generated for any tables that use variable fields. All changes for a particular user action can be grouped by the TS_ACTIONSTAMP , which references the record in TS_CHANGEACTIONS.
PDF TeamTrack Database Schema
Because of the way the trend report algorithm works, the system also stores one row per field when an issue or incident is submitted. Change History records are generated for any tables that use variable fields. All changes for a particular user action can be grouped by the TS_ACTIONSTAMP , which references the record in TS_CHANGEACTIONS.
PDF TeamTrack Database Schema
... TS_CHANGEACTIONS TI_TIME_CHANGEACTIONS TS_TIME TS_CHANGES TI_CASEID_CHANGES TS_CASEID TS_CHANGES TI_CASEID_CHANGES TS_FLDID TS_CHANGES TI_TIME_CHANGES TS_TIME TS_CHANGES TI_ACTIONSTAMP_CHANGES TS_ACTIONSTAMP TS_CHANGETEXT TI_CHANGEDETAILID_CHANGETEXT TS_CHANGEDETAILID
PDF TeamTrack Database Schema
TS_CALENDARID TS_STARTDATE TS_ENDDATE TS_ELAPSEDTIME TS_CHANGEACTIONS TI_ITEMID_CHANGEACTIONS TS_ITEMID TS_CHANGEACTIONS TI_TIME_CHANGEACTIONS TS_TIME TS_CHANGES TI_CASEID_CHANGES TS_CASEID TS_CHANGES TI_CASEID_CHANGES TS_FLDID TS_CHANGES TI_TIME_CHANGES TS_TIME TS_CHANGES TI_ACTIONSTAMP_CHANGES TS_ACTIONSTAMP TS_CHANGETEXT TI_CHANGEDETAILID_CHANGETEXT TS_CHANGEDETAILID 26 Table Index Attributes/Note
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs