OCOMC ECE DC Cartridge Fails to Move or Write Response when the Output Path is a Network File System
(Doc ID 2689981.1)
Last updated on JULY 28, 2020
Applies to:Oracle Communications Offline Mediation Controller - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
In Oracle Communications Offline Mediation Controller (OCOMC) setup, Elastic Charging Engine Distribution Cartridge (ECE DC) fails to move the Network Accounting Record (NAR) (Oracle’s proprietary format) file from scratch folder to output/success or other folders when the folder is linked to a network file system mount point.
- In the OCOMC setup, several ECE DC cartridges serving different services and multiple nodes on each server. All the success or responses from all the cartridges are pointed to one single folder so that it is a consolidated view. However, during setting up the instance in the cloud infrastructure tried to have these responses pointed to network file system storage. ECE DC fails to place on the linked file system storage and the NAR file stays in scratch folder.
1. ECE DC cartridge output folder
pin@HOSTNAME [nodeId]$ pwd
- Each sub folder is linked to a network file system path where DATA is a mount point to NFS. (When link is not provided to NFS and when its local FS, ECE DC works fine)
pin@HOSTNAME [nodeId]$ ll
lrwxrwxrwx. 1 pin pin 56 Dec 13 14:47 delayedresponse -> /opt/Oracle/OCOMC/DATA/ECE_OUTPUT/delayedresponse
lrwxrwxrwx. 1 pin pin 50 Dec 13 14:47 duplicate -> /opt/Oracle/OCOMC/DATA/ECE_OUTPUT/duplicate
lrwxrwxrwx. 1 pin pin 51 Dec 13 14:47 noresponse -> /opt/Oracle/OCOMC/DATA/ECE_OUTPUT/noresponse
lrwxrwxrwx. 1 pin pin 48 Dec 18 14:40 success -> /opt/Oracle/OCOMC/DATA/ECE_OUTPUT/success
Question: Assuming this is a problem with the Java method "renameTo()". Need fix to Link the directories in OCOMC?
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