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"
Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Communications Network Charging and Control - Version: 4.0.0
Information in this document applies to any platform.
cmnPushFiles ERROR: Remote end sent error condition: -ERROR Could not rename /IN/service_packages/CCS/logs/ccsNotificationRead//.RECEIVING.ccsNotification_13938_20110203015044.txt to /IN/service_packages/CCS/logs/ccsNotificationRead//ccsNotification_13938_20110203015044.txt: No such file or directory
In order to verify that this is the issue that you are having, you can perform the following test.
Always perform such tests on a test environment in order not to disturb sending notification on the live system
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:
scswitch –F –g CcsNotificationBatch-sarg
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"
mv /IN/service_packages/CCS/logs/ccsNotificationRead//ccsNotification_13938_20110203015044.txt /IN/service_packages/CCS/logs/ccsNotificationRead//.RECEIVING.ccsNotification_13938_20110203015044.txt
Step 4: Start ccsNotificationBatch
Startup ccsNotificationBatch, either by:
using the scswitch command for the clustered configuration:
scswitch -z -g CcsNotificationBatch-sarg
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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms