1. Release Notes
  2. Caveats, Known Issues, and Limitations
  3. Known Issues

Known Issues

The following table lists Known Issues and provides the Service Request ID number, a description of the issue, any workaround, when the issue occurred, and when Oracle fixed the issue. This table includes issues from previous releases that either remain open or are resolved in this release. Issues from previous releases that do not appear here do not apply to this release. You can also find information about resolved issues in the Build Notes for this release.

ID Number Description Found In
32928940 When invalid values are configured in SA attributes, verify-config errors are not observed.

Ensure your configuration values are valid.

 PCZ3.3.0p3

29582306

The Dial pattern's "Delete All" function does not work properly, causing system disruption including system reboot.

Work-around: Delete the entire plan using the "Delete Dial Plan" function and recreate your Dial plan with the appropriate Dial patterns.

PCZ3.2.0

30509697

An OECB configured with 1 million user database entries stops accepting new calls for ~90 seconds after performing a save and activate.

Work-around: Configure systems with user databases that approach 1 million entries during a maintenance window.

In addition, Oracle recommends using the OECB's ACLI paste-config command or the automatic CSV import feature to perform uploads of these large user databases and avoid system interruption. 		PCZ3.2.0
30298150 Synced data is not removed after OECB sync is turned off. PCZ3.2.0
No ID number

If you want to establish a High Availability pair that uses IP addresses other than the defaults, perform the following procedure. Use this procedure regardless of whether the ECBs run on virtual or physical systems.

Procedure

  1. Perform the standard HA setup with the run setup command. Allow both systems to come up as an HA pair.
  2. Logon to the Active machine's GUI.
  3. Navigate to Configuration > General Settings > Redundancy Config.
  4. Update the Primary and Secondary peers with the destinations 169.254.1.1 and 169.254.1.2 to the primary and secondary sip-interface addresses respectively.
  5. Navigate to Configuration > Network > Network Settings.
  6. Update the network interface “wancom1” with Pri Utility Addr, Sec Utility Addr and Netmask to the sip-interface values.

    Note:

    The GUI does not display the network interface name in Network Settings. Choose the network interface that has the default values of:
    • Primary —169.254.1.1
    • Secondary —169.254.1.2
    • Netmask—255.255.255.252
  7. Update that network interface with the primary, secondary and netmask values of the sip-interface respectively.
  8. Save and activate your changes.

    After the save and activate on the Active machine is complete, both the and active and standby machines become Active machines.

  9. Reboot your target primary, and then your secondary ECB’s. After boot, the systems come up as an HA pair with the sip-interface values.

The IP addresses you use must be available and valid in your network. If not, you must directly connect the two ECBs before performing this procedure to establish the HA pair initially.

PCZ3.0.0