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 TS_Notification records and values of TS_Type field
TS_Notification records and values of TS_Type field
CMS-XML When you delete a report that is set as a scheduled report the corresponding entry in ts_notifications and ts_notificationevents stays
When you delete a report that is set as a scheduled report the corresponding entry in ts_notifications and ts_notificationevents stays
CMS-XML Scheduled reports upgraded to 11.0 cannot be removed
This is because the TS_SHELLTYPE is NULL in TS_NOTIFICATIONS . If you update this field to "ae" or "swc" backend in the database then you can remove this report successfully.
CMS-XML What does the ts_sendtype column in TS_NOTIFICATIONEVENTS and TS_NOTIFICATIONS tables do?
What does the ts_sendtype column in TS_NOTIFICATIONEVENTS and TS_NOTIFICATIONS tables do?
CMS-XML Existing escalations not sending after upgrade from TeamTrack to SBM
update TS_NOTIFICATIONEVENTS set TS_NOTIFICATIONEVENTS.TS_SENDTYPE = (select TS_NOTIFICATIONS.TS_SENDTYPE from TS_NOTIFICATIONS where TS_NOTIFICATIONEVENTS.TS_NOTIFICATIONID = TS_NOTIFICATIONS.TS_ID) where exists (select TS_NOTIFICATIONS.TS_SENDTYPE from TS_NOTIFICATIONS where TS_NOTIFICATIONEVENTS.TS_NOTIFICATIONID = TS_NOTIFICATIONS.TS_ID);
CMS-XML SBM: Scheduled LDAP Sync jobs are not running, also impacts scheduled reports
select * from TS_NOTIFICATIONEVENTS e left join TS_NOTIFICATIONS n on e.TS_NOTIFICATIONID = n.TS_ID left join TS_USERS u on n.TS_AUTHORID = u.TS_ID
CMS-XML Scheduled reports stop working in case if unexpected error occurs inside CronJobServiceImpl.process() for loop
This SQL can be used to clear or problems with scheduled reports. SQL> delete from TS_NOTIFICATIONS where TS_SENDTYPE=256 and TS_REPORTID not in (select TS_ID from TS_REPORTS); SQL> delete from TS_NOTIFICATIONS where TS_SENDTYPE=256 and TS_ID not in (select TS_NOTIFICATIONID from TS_NOTIFICATIONEVENTS where TS_SENDTYPE=256);
CMS-XML Scheduled reports are not running
It is also possible for this problem to occur if there are events in the TS_NotificationEvents table that refers to a NotificationID in the TS_Notifications table that does not exist. To purge any of these possible orphaned events, run this query:
CMS-XML Notification server crashes periodically
e.TS_NAME AS "Escl Name", ew.TS_NAME AS "Escl Workflow" FROM TS_NOTIFICATIONS n, TS_NOTIFICATIONCONDITIONS c, TS_WORKFLOWS w, TS_NOTIFICATIONS e, TS_NOTIFICATIONCONDITIONS ec, TS_WORKFLOWS ew
CMS-XML When you open the Notifications area in your settings while in Work Center you may see an error "No row with the given identifier exists" com.serena.sbm.data.Notification#XXX
If you get results from the following query this means you have Notifications with users subscribed that don't exist in the system: select * from TS_NOTIFICATIONSUBSCRIPTIONS where TS_NOTIFICATIONID not in (SELECT TS_ID from TS_NOTIFICATIONS ) If those queries came back with results run the following queries to fix the issue.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs