B.5 Database Event Management
Below listed shows database event management
B.5.1 Database Space Reached Specified Percent Threshold
When event insertion is resumed after being blocked, the following event is sent.
Table B-29 Database Event Management - Database Space Reached Specified Percent Threshold
|
Severity
|
0
|
|
Event Name
|
DbSpaceReachedPercentThrshld
|
|
Resource
|
Database
|
|
SubResource
|
Database
|
|
Message
|
Tablespace <string> has current size of <number> MB with a max size of <number> MB and has reached the percentage threshold of <number> % |
B.5.2 Database Space Reached Specified Time Threshold
When event insertion is resumed after being blocked, the following event is sent.
Table B-30 Database Event Management - Database Space Reached Specified Time Threshold
|
Severity
|
0
|
|
Event Name
|
DbSpaceReachedTimeThrshld
|
|
Resource
|
Database
|
|
SubResource
|
Database
|
|
Message
|
Tablespace <string> has <number> MB left and growing <number> bytes per second and will run out space within the time threshold specified <number> seconds |
B.5.3 Database Space Very Low
When event insertion is resumed after being blocked, the following event is sent.
Table B-31 Database Event Management - Database Space Very Low
|
Severity
|
5
|
|
Event Name
|
DbSpaceVeryLow
|
|
Resource
|
Database
|
|
SubResource
|
Database
|
|
Message
|
Tablespace <string> has current size of <number> MB and has reached the physical threshold of <number> MB |
B.5.4 Error inserting events
When inserting events into the database fails the following internal event is generated.
Table B-32 Database Event Management - Error inserting events
|
Severity
|
5
|
|
Event Name
|
InsertEventsFailed
|
|
Resource
|
EventSubsystem
|
|
SubResource
|
Events
|
|
Message
|
Error inserting events into the Database—the events might be permanently lost. Please check the Database and backend server logs<Exception> |
B.5.5 Error Moving Completed File
When an event file is completed it is moved to the output directory. If that move fails the following internal event is generated.
Table B-33 Database Event Management - Error Moving Completed File
|
Severity
|
3
|
|
Event Name
|
MoveArchiveFileFailed
|
|
Resource
|
<DAS name> |
|
SubResource
|
ArchiveFile
|
|
Message
|
Error moving completed archive file <fileName> to <directory> |
B.5.6 Error Processing Event Message
Table B-34 Database Event Management - Error Processing Event Message
|
Severity
|
|
|
Event Name
|
ErrorProcessingEventMessage
|
|
Resource
|
EventSubsystem
|
|
SubResource
|
EventStore
|
|
Message
|
Error processing event message, events may be lost; check the log file for more details: {0}
|
B.5.7 Error Saving Failed Events
Table B-35 Database Event Management - Error Saving Failed Events
|
Severity
|
|
|
Event Name
|
ErrorSavingFailedEvents
|
|
Resource
|
EventSubsystem
|
|
SubResource
|
EventStore
|
|
Message
|
Error inserting failed events to cache; {0} events may be permanently lost. Check the logs for more detail and correct the problem immediately: {1}
|
B.5.8 Event Insertion is blocked
If DAS is writing into the overflow partition and the user attempts to add partitions SDM will send a request to DAS to temporarily stop inserting events into the database. When this happens DAS will send internal events every time it attempts to insert events into the database.
Table B-36 Database Event Management - Event Insertion is blocked
|
Severity
|
4
|
|
Event Name
|
EventInsertionIsBlocked
|
|
Resource
|
EventSubSystem
|
|
SubResource
|
Events
|
|
Message
|
Event insertion is blocked, waiting <number> sec |
B.5.9 Event Insertion is resumed
When event insertion is resumed after being blocked, the following event is sent.
Table B-37 Database Event Management - Event Insertion is resumed
|
Severity
|
2
|
|
Event Name
|
EventInsertionResumed
|
|
Resource
|
EventSubSystem
|
|
SubResource
|
Events
|
|
Message
|
Event insertion has resumed after being blocked
|
B.5.10 Event Message Queue Overflow
Table B-38 Database Event Management - Event Message Queue Overflow
|
Severity
|
|
|
Event Name
|
EventMessageQueueOverflow
|
|
Resource
|
EventSubsystem
|
|
SubResource
|
EventStore
|
|
Message
|
In the previous {0}ms, failed to execute event store task for {1} events because task queue is full--Events were stored to file for later insertion. Check the log files and the database " "for more information. The error occurred {2} times in this time range: {3}";
|
B.5.11 Event Processing Failed
Table B-39 Database Event Management - Event Processing Failed
|
Severity
|
|
|
Event Name
|
EventProcessingFailed
|
|
Resource
|
EventSubsystem
|
|
SubResource
|
EventStore
|
|
Message
|
In the previous {0}ms, failed to process {1} events--Events were stored for later insertion. Check the log files and the database for more information. The error occurred {2} times in this time range: {3}, cause {4}";
|
B.5.12 No Space In The Database
Table B-40 Database Event Management - No Space In The Database
|
Severity
|
|
|
Event Name
|
DbNoSpace
|
|
Resource
|
DBSpace
|
|
SubResource
|
tableSpace
|
|
Message
|
|
B.5.13 Opening Archive File failed
When opening an archive file for storing the events for aggregation fails, the following internal event is generated.
Table B-41 Database Event Management - Opening Archive File failed
|
Severity
|
3
|
|
Event Name
|
OpenArchiveFileFailed
|
|
Resource
|
<Das name> |
|
SubResource
|
ArchiveFile
|
|
Message
|
Error opening archive file <fileName> in <directory> |
B.5.14 Partition Configuration
Table B-42 Database Event Management - Partition Configuration
|
Severity
|
|
|
Event Name
|
New/Update/Remove
|
|
Resource
|
|
|
SubResource
|
PartitionConfig
|
|
Message
|
ableName=<name> PartTimeUnit={1} PartTimeFactor={2} NumberOfUnits={3}
|
B.5.15 Writing to Archive File failed
When opening an archive file for storing the events for aggregation fails, the following internal event is generated.
Table B-43 Database Event Management - Writing to Archive File failed
|
Severity
|
3
|
|
Event Name
|
WriteArchiveFileFailed
|
|
Resource
|
<Das name> |
|
SubResource
|
ArchiveFile
|
|
Message
|
Error writing newly received events to aggregation archive file <fileName> |
B.5.16 Writing to the overflow partition (P_MAX)
An event is sent approximately every 5 minutes notifying the user when events are being written to the overflow partition (P_MAX). When this occurs, the administrator needs to use SDM and add more partitions otherwise performance will start degrading.
Table B-44 Database Event Management - Writing to the overflow partition (P_MAX)
|
Severity
|
5
|
|
Event Name
|
InsertIntoOverflowPartition
|
|
Resource
|
EventSubSystem
|
|
SubResource
|
Events
|
|
Message
|
Error: currently inserting into the overflow partitions (P_MAX), add more partitions
|