8 Resolved and Known Bugs

This chapter lists the resolved and known bugs for this release. These bug lists are distributed to customers with a new software release at the time of General Availability (GA), and are updated for each maintenance release.

8.1 Severity Definitions

The problem report sections in this document refer to Bug severity levels. Definitions of these levels can be found in the publication, TL 9000 Quality Management System Measurement Handbook.

Problem Report: A report from a customer or on behalf of the customer concerning a product or process defect requesting an investigation of the issue and a resolution to remove the cause. The report may be issued via any medium. Problem reports are systemic deficiencies with hardware, software, documentation, delivery, billing, invoicing, servicing or any other process involved with the acquisition, operation, or performance of a product. An incident reported simply to request help to bring back the service or functionality to normal without the intent to investigate and provide a resolution to the cause of the incident is not a problem report.
  • Critical: Conditions that severely affect the primary functionality of the product and because of the business impact to the customer requires non-stop immediate corrective action, regardless of time of day or day of the week as viewed by a customer on discussion with the organization such as
    1. product inoperability (total or partial outage),
    2. a reduction in the capacity capability, that is, traffic/data handling capability, such that expected loads cannot be handled,
    3. any loss of emergency capability (for example, emergency 911 calls), or
    4. safety hazard or risk of security breach
  • Major: Product is usable, but a condition exists that seriously degrades the product operation, maintenance or administration, etc., and requires attention during pre-defined standard hours to resolve the situation. The urgency is less than in critical situations because of a lesser immediate or impending effect on product performance, customers and the customer's operation and revenue such as
    1. reduction in product's capacity (but still able to handle the expected load),
    2. any loss of administrative or maintenance visibility of the product and/or diagnostic capability,
    3. repeated degradation of an essential component or function, or
    4. degradation of the product's ability to provide any required notification of malfunction
  • Minor: Other problems of a lesser severity than 'critical' or 'major' such as conditions that have little or no impairment on the function of the system
  • Minor, No Loss of Service: Oracle severity beyond what is defined by TL 9000.

The numbered severity levels in the tables below correspond to these definitions:

  • 1 - Critical
  • 2 - Major
  • 3 - Minor
  • 4 - Minor, No Loss of Service

8.2 Resolved Bug List

The resolved bugs table shows an impact statement for severity 1 and 2 bugs as well as for severity 3 bugs that are associated with an SR.

EPAP Release 18.0.0.0.0-180.6.0

The following table lists the bugs resolved in EPAP build 18.0.0.0.0-180.6.0:

Table 8-1 EPAP Release 18.0.0.0.0-180.6.0 Resolved Bugs (June 2026)

Bug Number SR Severity Title Customer Impact
37417134 Y 3 Changes to be made in EPAP documentation for Automatic PDB/RTDB Backup Configuration section Without the documentation fix, customers would be unaware of the new behavior of automatic backup.
37759985 N 3 EPAP 17.0.6: Key exchange issue on 16.3.1  
37957769 N 3 EPAP 17.0.0.7.0: Installation/Upgrade documentation requires changes with respect to DIU files in the home folder time-taking impact  
38564661 Y 3 Disable Remote Restore During PDB Restore No practical impact to customers, as customers rarely, if ever, restore the remote PDB at the same time as the local PDB. The change is expected to be unnoticed by customers.
38638196 N 3 Eagle connection is lost sometimes when EPAP is rebooted  
36767606 N 4 Cisco Switch Configuration from platcfg menu  
38065680 N 4 EPAP 17.1: Server Authorized IP Issue  
38831843 N 4 Support APPD in EPAP  
38832011 N 4 Support DIU upgrade for APPD hardware in EPAP  
38942231 N 4 EPAP 18.0 - Update JQuery to latest available version  

8.3 Customer Known Bug List

EPAP Release 18.0 Customer Known Bugs

The following table lists the known bugs and associated customer impact statements.

Table 8-2 EPAP Release 18.0 Customer Known Bugs (June 2026)

Bug # SR Sev Title Customer Impact
39183325 Y 3 PDB Export takes longer after upgrade to EPAP 17 Customers will have to adjust expectations as the export takes longer.
39230573 N 3 Enabling watcher takes high amount of CPU Customers may encounter slow provisioning as CPU resource is limited.