# Handling Alarms

# Resolving 2.2 Style Alarms

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.

## 103827/1034 SLEE: Transaction limit violated

### Severity

Warning

### Description

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.

### What to do

Informational only.

## 103833/1035 SLEE: Transaction limit reached 95% of the allowed value

### Severity

Minor

### Description

The number of transactions has exceeded 95% of limit defined by Oracle Communications Services Gatekeeper management procedures.

### What to do

Informational only.

## 103900/1100 SLEE charging: Charging data storage failed

### Severity

Critical

### Description

The SLEE charging service has failed to write charging data to the database.

Possible reasons:

- The database is not running
- There is a network communication problem between the SLEE and the databases.

### What to do

Check the database.

## 103901/1101 SLEE charging: Charging service initialization failed

### Severity

Critical

#### Description

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.

### What to do

Start the database before Oracle Communications Services Gatekeeper at system installation or restart.

## 103902/1102 SLEE charging: Charging table creation failed

### Severity

Critical

### Description

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

### What to do

Start database before Oracle Communications Services Gatekeeper at system installation or restart.

## 104000/1600 SLEE EDR service: 2.2 Listener execution time exceeded

### Severity

Minor

### Description

A 2.2 style EDR listener has exceeded the maximum notify execution time when receiving a batch of EDRs.

### What to do

Make sure the 2.2 EDR listeners keep the notify execution time as short as possible.

## 104001/1601 SLEE EDR service: 2.2 style EDR listener removed

### Severity

Major

### Description

A 2.2 style EDR listener has been removed because it has exceeded the maximum notify execution time too many times.

### What to do

Make sure the EDR listeners keep the notify execution time as short as possible

## 104100/7001 SLEE statistics: Failed to store statistics data

### Severity

Minor

### Description

Failed to store statistics data.

### What to do

Check the status of the database and check if the disk is full.

## 102700/22000 Plug-in OSA access: OSA gateway authentication failed

### Severity

Major

### Description

The OSA access plug-in failed to authenticate with the OSA gateway.

### What to do

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.

## 102701/22001 Plug-in OSA access: OSA gateway service manager unreachable

### Severity

Major

### Description

The OSA manager object obtained from the OSA gateway is considered dead. Might be a network problem.

### What to do

The OSA gateway plug-in will automatically try to authenticate the OSA gateway at next service request.

## 102702/22002 Plug-in OSA access: OSA gateway unreachable

### Severity

Major

### Description

The OSA access plug-in could not reach any of the connected OSA gateways (OSA frameworks) defined. Might be a network problem.

### What to do

Verify the network connection.

## 102703/22003 Plug-in OSA access: No mapping available

### Severity

Major

### Description

The application requesting a service from the OSA gateway does not have a valid mapping towards the requested OSA service.

### What to do

Verify the current mapping. If no mapping exists, create a mapping according to the information in Managing Accounts and SLAs.

## 102704/22004 Plug-in OSA access: Internal error when handling event

### Severity

Major

### Description

An unexpected internal error has occurred.

### What to do

Contact Oracle Support

## 102800/3002 Policy service: Parsing of service-specific rule file failed

### Severity

Major

### Description

The rule engine cannot parse the service-specific rule file.

### What to do

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.

## 3003 Policy service: Various Policy Denials

### Severity

Major

### Description

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.

### What to do

Make sure the relevant SLA is available and loaded and that it is up to date.

## 102802/3005 Policy service: Request denied

### Severity

Minor

### Description

The policy service denied a service request.

### What to do

-

## 102803/3006 Policy service: Runtime exception in policy rule

### Severity

Major

### Description

The policy service encountered a run-time exception.

### What to do

Contact Oracle Support.

## 102804/3007 Service Provider Group SLA Added

### Severity

Minor

### Description

Informational. The operator has added a Service Provider Group SLA.

### What to do

-

## 102805/3008 Service Provider Group SLA Deleted

### Severity

Major

### Description

Informational. The operator has deleted a Service Provider Group SLA.

### What to do

-

## 102806/3009 Service Provider Group SLA Updated

### Severity

Minor

### Description

Informational. The operator has updated a Service Provider Group SLA.

### What to do

-

## 102807/3010 Application Group SLA Added

### Severity

Major

### Description

Informational. The operator has added an Application Group SLA.

### What to do

-

## 102808/3011 Policy service: Application Group SLA deleted

### Severity

Major

### Description

Informational. The operator has deleted an Application Group SLA.

### What to do

-

## 102810/3013 Policy service: Node SP SLA added

### Severity

Major

### Description

Informational. The operator has added a Node Service Provider SLA.

### What to do

-

## 102811/3014 Policy service: Node SP SLA deleted

### Severity

Major

### Description

Informational. The operator has deleted a Node Service Provider SLA.

### What to do

-

## 102812/3015 Policy service: Node SP SLA updated

### Severity

Major

### Description

Informational. The operator has updated a Node Service Provider SLA

### What to do

-

## 102813/3016 Policy service: Node SLA added

### Severity

Major

### Description

Informational. The operator has added a Node SLA

### What to do

-

## 102814/3017 Policy service: Node SLA deleted

### Severity

Major

### Description

Informational. The operator has deleted a Node SLA

### What to do

-

## 102815/3018 Policy service: Node SLA updated when raised by Policy. Fail to find transaction number when raised by ESPA_messaging

### Severity

Major

### Description

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.

### What to do

If the condition (ESPA_messaging) repeats frequently contact Oracle support.

## 102816/3019 Policy service: Application rules updated

### Severity

Major

### Description

Informational. The operator has updated Application rules.

### What to do

-

## 102817/3020 Policy service: Node rules updated

### Severity

Major

### Description

Informational. The operator has updated Node rules.

### What to do

-

## 102818/3021 Policy service: Service Provider rules updated

### Severity

Major

### Description

Informational. The operator has updated the Service Provider rules.

### What to do

-

## 102819/3022 Policy service: Application rules deleted

### Severity

Major

### Description

Informational. The operator has deleted Application rules.

### What to do

-

## 102820/3023 Policy service: Node rules deleted

### Severity

Major

### Description

Informational. The operator has deleted Node rules.

### What to do

-

## 102821/3024 Policy service: Service Provider rules deleted

### Severity

Major

### Description

Informational. The operator has deleted Service Provider rules.

### What to do

-

## 102822/3025 Policy service: Service Provider/Application quota limit exceeded

### Severity

Major

### Description

Quota limit defined in SLA has been exceeded by a specific service provider or application.

### What to do

Contact service provider to reduce traffic or increase the limits.

## 102823/3026 Policy service: Service Provider/Application request limit exceeded

### Severity

Major

### Description

Request limit defined in SLA has been exceeded by a specific service provider or application.

### What to do

Contact service provider to reduce traffic or increase the limits.

## 102824/3027 Policy service: Global/SP NODE request limit exceeded

### Severity

Major

### Description

Request limit defined in Node SLAs has been exceeded by a specific service provider or application.

### What to do

Contact service provider to reduce traffic or increase the limits.

## 102825/3028 Policy service: Global or SP node service contract is missing or out of date

### Severity

Major

### Description

Node SLA is missing or out of date.

### What to do

Update the SLA.