Caveats and Limitations

Oracle Communications Session Delivery Manager

A hot backup of the Oracle Communications Session Delivery Manager database is not supported in Oracle Communications Session Delivery Manager Release 8.0.
Workaround: Shut down the SDM server(s) and do a cold backup of the SDM database. Refer to the Session Delivery Manager Server Database Maintenance chapter of the Oracle Communications Session Delivery Manager Administration Guide for more information about performing a cold backup.
We recommend that the name of your SBC device does not have an underscore character (_). This character may cause information to not appear correctly for an SBC device in SDM product applications. Also, the historical data record (HDR) data detection feature does not work on an SBC device if its name has an underscore.
If the plug-in is replaced or upgraded, any previously uploaded XSD work spaces are removed.

Workaround: Reapply the XSD work spaces once the plug-in is installed.
When a user installs a plug-in on a cluster node that supports new functionality, other users that are logged in may not see this new functionality.
Workaround: The user can use click Refresh in Device manager or log out of their SDM GUI session and then log back in to see the change.
A Multi-NIC environment has the following limitations:
- An IPv4 address is supported only for the default NIC for SDM cluster server-to-server communication. When you perform the Custom installation in the SDM ./setup.sh application to configure an SDM cluster, you must enter an IPv4 address for the default eth0 NIC only for each member added to the cluster. See the Verify the Required SDM_localhost Entry in the Hosts File section in the Oracle Communications Session Delivery Manager Installation Guide for configuration information. After starting the SDM server(s), you cannot change the IP address for cluster communication.
- When you use the SDM setup process to create a self-signed certificate for SDM northbound WebServer HTTPS communication, a single DNS name can be used only because SDM supports one northbound HTTPS interface.
- When you use the SDM setup process to create an entity certificate to facilitate mutual authentication for SDM southbound (ACP), a single DNS name can be used only because the SDM supports one southbound ACP over TLS interface.
In the Element Manager Plugins table (Tools > Plugin Management), you cannot sort the Status, Server, and Date Modified columns in ascending or descending order.
If you implement an SDM cluster, one server only must be started successfully and operational before other servers in the cluster can be started.
When connecting an SDM to an SBC with the Admin Security ACP feature enabled, you must have the security, admin-security, enable-login-banner configuration parameter set to disabled.

Oracle Communications Session Element Manager

In the event of an unexpected server shutdown, the incremental save operation may be incorrectly reported as being successful if it is associated with a offline configuration update.
When entering a single quote in an attribute value, use the backslash symbol "\" to escape.
A CXF (SOAP) client may have its connection closed by the server for long duration transactions.
The ability to use an offline configuration to provision network function (NF) device clusters is not available for the Acme Packet 9200 platform.

Oracle Communications Report Manager

If you are upgrading Oracle Communications Session Report Manager from a previous version, BI Publisher and Oracle database (Listener and Listener 2) need to be running and properly connected when you use the Oracle Communications Session Delivery Manager setup installation process, during which these databases are migrated. See the Prepare for a Report Manager Upgrade section in the Pre-Installation Tasks chapter of the Oracle Communications Session Report Manager Installation Guide for more information.
The charts in a canned BI Publisher report are inter-linked. The filter for a time value displayed for the X-axis does not work in this release. If the user clicks on a data point in one chart, the other charts display No Data Available.
By default, the nncentral user password for the Oracle reporting database expires in 6 months. Once the password expires, the nightly backup and restore capability for reporting fails. You must change the password for the nncentral user and go to the Register BI Publisher screen to change the Oracle database password.
Note:
This limitation applies to Report Manager users who have installed an Oracle database on the same server as SDM only.
You must use alphanumeric characters only because Report Manager does not support the use of special characters in the ocsremdw password.
Report Manager does not support data gathering or the TscfStats group for SBC devices with ScZ7.40 and ScZ7.4.0p1 releases. This problem will be fixed in the ScZ7.4.0p2 release.
For most SBC releases, Report Manager does not support starting collection on individual HDR groups. If individual selection of these groups is required, the user must log into the device(s) and run the start collection group.
With the introduction of SDM, Release 8.0, there is a single secure sockets layer (SSL) keystore that includes BI Publisher certificates. Any BI Publisher certificates that were previously imported into the keystore before Release 8.0 are lost.
- Ensure that the BI Publisher certificate is in the desired directory on the SDM server. If the BI Publisher certificate is not on the server you must transfer it to server. See the Save and Transfer the BI Publisher Certificate to Session Delivery Manager section in the Register Oracle BI Publisher chapter of the Oracle Communications Report Manager Installation Guide for more information.
- Ensure that the BI Publisher Certificate is added to the keystore either through the SDM server setup program (setup.sh) or upload it through the SDM GUI.
  
  Note:
  If you are using the SDM server setup program to upload a BI Publisher certificate, you must run the setup program on each SDM server cluster node to upload the BI Publisher certificate on each node. If you perform this task through the SDM GUI, the BI Publisher certificate is replicated to all SDM server cluster nodes.
  - See the Configure Southbound Interface Transport Layer Security section in the Custom Installation chapter of the Oracle Communications Session Delivery Manager Installation Guide for more information about loading the BI Publisher certificate through the SDM server setup program.
  - See the Manage Certificates for Southbound Authentication chapter in the Oracle Communications Session Delivery Manager Administration Guide for more information about loading the BI Publisher certificate through the SDM GUI.
In SDM, Release 8.0, Report Manager is supported on Oracle Linux 6.5, 6.6, 6.7, 6.8 only. Also, Oracle Database 11g Standard Edition One, and Oracle Business Intelligence (BI) Publisher 11g are supported only.
In SDM, Release 8.0, Report Manager does not support device clustering.