|
Description and Workaround or Solution
|
|
|
|
If you stop one AT server and one NT server in a multi-cluster domain and then restart only the AT server, application-initiated requests sent to that server may result in the following error with the message: “Failed to invoke end component <component name>”. In the reverse case, network-triggered requests may fail.
Dependent on Oracle WebLogic Server CR384639.
Make sure you start both servers.
Contact Oracle support for a patch on this issue.
|
|
|
|
On the first start-up after domain configuration, if 2 or more NT servers are started at the same time, the servers may throw LDAP exception. An equivalent failure may occur on deploying applications.
Restart the servers. If the problem persists, start one server first, and then the others
Retry deploying the application. If the problem persists, redeploy the application when the servers are not running.
|
|
|
|
Before geo-redundancy is set up, you may sometimes get null pointer exception in geo-storage module. This is benign and may be ignored.
|
|
|
|
Setting StatisticsServiceMbean::StoreInterval to 0 can produce negative data in the transactions field of the slee_statistics_data table.
Don’t set StoreInterval to 0
|
|
|
|
When OCSG is first used, the database is initialized. If two NT servers are started up at the same time, they may both try to initialize the database, causing a Service Deployment Exception and one server failing to start up.
Make sure the servers are started one at a time.
Restart the failed server.
|
|
|
|
Some Diameter requests may be dropped during patching, redeployment, or upgrade of the CDR to Diameter module.
Check the database for the time period during which the transition took place. All CDRs are stored in the database.
|
|
|
|
If the credit control interceptor fails to connect to the Diameter server, the isConnected attribute will show incorrect state.
Run traffic to check whether the interceptor is connected.
|
|
|
|
The Native SMPP Communication Service does not support hitless upgrades. Upgrades cannot be performed without traffic service interruption.
Perform a rolling upgrade instead.
|
|
|
|
The Parlay X 2.1Short Messaging/SMPP plug-in does not support in-production upgrade after upgrading from 4.0.
Before you do a rolling upgrade to the servers, undeploy the EAR file for this communication service. After all upgrades are complete, redeploy the EAR.
This does not affect fresh installations of 4.1.
Note: |
A mandatory patch will be released to correct this error. Please contact your Oracle service representative about acquiring this patch when it comes out. |
|
|
|
|
The Plug-in Manager reports that plugin_sms_smpp state is connected even when it is not.
Use the ActiveStatus attribute of the SMPP MBean to check connection status
|
|
|
|
When running the Legacy SMPP communication service, you may receive the following exception from your NT servers.
ERROR com.bea.wlcp.wlng.legacy.smpp.connector.SmppChannelProcessor - Could not find request for received response
This exception can be ignored.
|
|
|
|
Due to incompatible class changes to the stored blob data, old application data (notifications, etc.) in SIP call notification and presence plug-ins will NOT be usable after the upgrade. Exceptions will be thrown during the upgrade when the old application data is accessed.
Contact Oracle support for migration scripts.
|
|
|
|
There is an error in the data migration scripts that causes the old SP SLA not to be changed.
Necessary script updates can be found in
“Upgrading Oracle Communications Services Gatekeeper” in Installation Guide, a separate document in this set.
|
|
|
|
PRM service provider users and operator users can not be given access to a restricted set of JMX interfaces exposed by Oracle Communications Services Gatekeeper.
Dependent on Oracle WebLogic Server CR 382906.
|
|
|
|
The SOAP to SOAP generation does not support all WSDLs.
The WSDL defining the application-facing interface must adhere to the following:
- Attribute name in <wsdl:service> must include the suffix Service.
- Attribute name in <wsdl:port> must be the same as the name attribute in
- <wsdl:service>, excluding the suffix Service.
Dependent on Oracle WebLogic Server CR 384278.
|
|
|
|
The Native SMPP communication service does not actively disconnect applications if the SMSC connection is down.
The communication service sends an OK response to enqure link requests in this case.
|
|
|