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  
  Results
CMS-XML SBM: When a "no match found" event is logged in the ALFEventManager, a row is also added to EL_EVENT_PROCSNG_DATA table
SBM: When a "no match found" event is logged in the ALFEventManager, a row is also added to EL_EVENT_PROCSNG_DATA table
CMS-XML SBM: Event Manager purge fails when there are too many records in EL_EVENT_PROCESSING_DATA
* Run the following scripts: truncate table EL_EVENT_PROCSNG_DATA ; truncate table EL_EVENT;
CMS-XML Best Practice when maintaining SBM Environments. Copy database to another database.
Delete all entries in the EL_EVENT, EL_EVENT_LOG_MESSAGE, EL_EVENT_PROCSNG_DATA , EL_EVENT_SERVICE_FLOW, EL_EVENT_SRVC_FLW_PROCSNG_DATA tables, Event logger messages typically resides in the orchestration database. Install SBM in the Environment of not done already The assumptions for the install are as follows:
PDF TeamTrack Database Schema
 EL_*: Tables used by SBM Application Repository for event logging. EL_EVENT EL_EVENT_LOG_MESSAGE EL_EVENT_LOG_SETTING EL_EVENT_LOG_TEMPLATE EL_EVENT_PROCSNG_DATA EL_EVENT_SERVICE_FLOW EL_EVENT_SRVC_FLW_PROCSNG_DATA  OR_*: Tables used by SBM Application Repository for Object Repository. Described below.
PDF SBM Orchestration Guide
Deletes all records in the EL_EVENT, EL_EVENT_PROCSNG_DATA , EL_EVENT_SRVC_FLW_PROCSNG_DATA, EL_EVENT_SERVICE_FLOW and EL_EVENT_LOG_MESSAGE event log tables. If you have not purged the event log in some time and a large amount of records have accumulated, you might not be able to delete event log records using Application Repository. You can use this command to clear the event log tables in that scenario.

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs