Operations Wiki Entries (Handling Stuck Run Types)
Sections:
List of Operations:
DB_MONITOR_ALL
: Monitors the entire database system for errors and resource bottlenecks.PROC_RESTART [process_name]
: Restarts specific database processes.LOG_FETCH [process_id]
: Fetches logs for a particular process to diagnose issues.SUBSCRIBER_LIST
: Lists registered subscribers for application processes.COMP_START
andCOMP_STOP
: Start and stop application components.
Failure Investigation Processes:
Run Diagnostic Tool:
UseRUN_TYPE_DIAG [run_type_id]
to diagnose issues with run types. This identifies whether the issue is related to resource bottlenecks, network failure, or component errors.Investigate Logs:
Fetch logs usingLOG_FETCH [run_type_id]
to identify detailed error messages.Check Resource Utilization:
UseRES_CHECK
to monitor CPU and memory utilization during process execution.Process Restart:
ExecutePROC_RESTART [process_id]
to restart stuck processes.
Operational Commands for Monitoring:
MONITOR_RUN_TYPE [run_type_id]
: Monitor a specific run type for status and logs.HEALTH_CHECK
: Runs a full system health check to identify problem areas.
Operational Commands for Starting and Stopping Components:
START_PROCESS [component_name]
: Starts a specific application component.STOP_PROCESS [component_name]
: Stops a specific application component.
Operational Commands for Restarting Components Following Failure:
PROC_RESTART [component_name]
: Restarts a failed component.SYSTEM_RESTART
: Restarts all processes in the application, including DB connections.
Appendix:
Application Timeslices: Instructions on how to handle time slice errors:
TIMESLICE_ADJUST [time]
: Adjusts timeslice allocation for processes.
Subscriber Lists: Run
SUBSCRIBER_LIST
to display subscribers for key processes.Data Source Management: Run
SOURCE_RELOAD
to reload data sources without a restart.