|
|
The following pages describe 2.2 style alarms that are processed by the 3.0 alarm-handling mechanisms and what can be done to respond to them. The first digit indicates the 3.0 alarm ID, whereas the second digit indicates the previously assigned 2.2 style ID. These alarms are belong to backwards compatible services, and contain slightly different information than 3.0 style alarms.
The number of transactions has exceeded a limit defined using Oracle Communications Services Gatekeeper management procedures. The alarm contains information on busy hour start time and end time -including date-, average busy-hour transactions per second and the defined limit.
The number of transactions has exceeded 95% of limit defined by Oracle Communications Services Gatekeeper management procedures.
The SLEE charging service has failed to write charging data to the database.
The alarm is raised if the charging service is activated before the database. That is, at installation or system restart, the database has to be started before Oracle Communications Services Gatekeeper.
Start the database before Oracle Communications Services Gatekeeper at system installation or restart.
An error occurred when trying to create the charging table in the database. The error occurs if the charging service is started before the database. That is, at installation or system restart, the database has to be started before Oracle Communications Services Gatekeeper
Start database before Oracle Communications Services Gatekeeper at system installation or restart.
A 2.2 style EDR listener has exceeded the maximum notify execution time when receiving a batch of EDRs.
Make sure the 2.2 EDR listeners keep the notify execution time as short as possible.
A 2.2 style EDR listener has been removed because it has exceeded the maximum notify execution time too many times.
Make sure the EDR listeners keep the notify execution time as short as possible
Failed to store statistics data.
Check the status of the database and check if the disk is full.
The OSA access plug-in failed to authenticate with the OSA gateway.
Verify the OSA gateway connection data with the OSA gateway operator. Verify that the user certificate is still valid. For more information, see System Administrator’s Guide.
The OSA manager object obtained from the OSA gateway is considered dead. Might be a network problem.
The OSA gateway plug-in will automatically try to authenticate the OSA gateway at next service request.
The OSA access plug-in could not reach any of the connected OSA gateways (OSA frameworks) defined. Might be a network problem.
Verify the network connection.
The application requesting a service from the OSA gateway does not have a valid mapping towards the requested OSA service.
Verify the current mapping. If no mapping exists, create a mapping according to the information in Managing Accounts and SLAs.
An unexpected internal error has occurred.
The rule engine cannot parse the service-specific rule file.
Verify that the rule file exists and that the path to the rule is correct.
Verify that the syntax in the rule file is correct. See the log file for the policy service (policy.log) for information on the error.
A number of different conditions can produce this alarm. The additional_info field describes specifically what the problem is, but in each case a request has been denied because the request attempts to use a method for which it is not authorized or has included a value for a request parameter is that not acceptable or because the relevant SLA cannot be found or is out of date.
Make sure the relevant SLA is available and loaded and that it is up to date.
The policy service denied a service request.
The policy service encountered a run-time exception.
Informational. The operator has added a Service Provider Group SLA.
Informational. The operator has deleted a Service Provider Group SLA.
Informational. The operator has updated a Service Provider Group SLA.
Informational. The operator has added an Application Group SLA.
Informational. The operator has deleted an Application Group SLA.
Informational. The operator has added a Node Service Provider SLA.
Informational. The operator has deleted a Node Service Provider SLA.
Informational. The operator has updated a Node Service Provider SLA
Informational. The operator has added a Node SLA
Informational. The operator has deleted a Node SLA
When raised by Policy, operator has updated Node SLA. When raised by ESPA_messaging it means that there was an error processing the result of a previously sent message. Information regarding the request and CDRs may not be available.
If the condition (ESPA_messaging) repeats frequently contact Oracle support.
Informational. The operator has updated Application rules.
Informational. The operator has updated Node rules.
Informational. The operator has updated the Service Provider rules.
Informational. The operator has deleted Application rules.
Informational. The operator has deleted Node rules.
Informational. The operator has deleted Service Provider rules.
Quota limit defined in SLA has been exceeded by a specific service provider or application.
Contact service provider to reduce traffic or increase the limits.
Request limit defined in SLA has been exceeded by a specific service provider or application.
Contact service provider to reduce traffic or increase the limits.
Request limit defined in Node SLAs has been exceeded by a specific service provider or application.
Contact service provider to reduce traffic or increase the limits.
Node SLA is missing or out of date.
|