cmnPushFiles ERROR: "Remote end sent error condition: -ERROR Cannot rename <path>/.RECEIVING.ccsNotification_xxxx.txt to <path>/ccsNotification_xxx.txt No such file or directory"
(Doc ID 1327840.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.0.0 and later
Information in this document applies to any platform.
cmnPushFiles reports errors in its log file (usually /IN/service_packages/SMS/tmp/cmnPushFiles.log) like:
In order to verify that this is the issue that you are having, you can perform the following test.
Step 1: Stop ccsNotificationBatch:
This depends on how ccsNotificationBatch is configured. In case of a cluster configuration, you need to stop the relevant resource group using the command:
Otherwise, if ccsNotificationBatch is not configured as a cluster, you need to stop it from the init tab, by disabling the line containing the ccsNotificationBatch startup script:
and then forcing it to stop using the following command:
Step 2: Create a notification
Create a notification file, by making any action that generates a notification.
The notification will be created in the directory /IN/service_packages/CCS/logs/ccsNotificationWrite/ on the VWS (UBE). cmnPushFile will then send it to the SMS under the directory
Step 3: Wait until the notification is pushed to the SMS
When you see that the notification is pushed to the directory /IN/service_packages/CCS/logs/ccsNotificationRead/ on SMS, rename to prefix ".RECEIVING"
Step 4: Start ccsNotificationBatch
Startup ccsNotificationBatch, either by:
using the scswitch command for the clustered configuration:
or uncommenting the line commented in step 1 in case of a non-cluster configuration, then issuing the command:
If the ccsNotificationBatch processes the file, this means that you are most likely facing this issue described in this article
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document