Profile Adapter Data Error Log Contains Numerous "has An Invalid Zone ()" Errors
(Doc ID 2595444.1)
Last updated on JULY 29, 2020
Applies to:
Oracle Utilities Network Management System - Version 2.3.0.2.0 and laterOracle Network Management for Utilities - DMS - Version 2.3.0.2.0 and later
Information in this document applies to any platform.
Symptoms
On : 2.3.0.2.0 version, Installation
Profile Adapter Data Error Log - "has an invalid zone ()"
Troubleshooting ProfileAdapter implementation.
$OPERATIONS_MOEL/load_profiles/log/LP_Data_Errors_*.log has over 19,000 errors of this format:
nmsadmin@<SERVER>:$NMS_HOME/data/load_profiles/log> head -5 LP_Data_Errors_20190816_010443.log
Profile Adapter Data Error Log - 20190816_010443
01:05:05 LP-011: Transformer<DEVICE_ID or PTAG>.<FEEDER_NAME> has an invalid zone (), check configuration in table pf_weather_zone.
01:05:05 LP-011: Transformer<DEVICE_ID or PTAG>.<FEEDER_NAME> has an invalid zone (), check configuration in table pf_weather_zone.
01:05:05 LP-011: Transformer<DEVICE_ID or PTAG>.<FEEDER_NAME> has an invalid zone (), check configuration in table pf_weather_zone.
nmsadmin@<SERVER>:$NMS_HOME/data/mp> grep 1010000013169803 V1532-10262.mp
ATTRIBUTE[transformer.PTAG]="1010000013169803";
And also in the MB file:
nmsadmin@<SERVER>:$NMS_HOME/data/patches/done> grep 1010000013169803 FEEDER_NAME.mb
ATTRIBUTE[device_id] = "<DEVICE_ID>";
ALIAS[CID] = "<DEVICE_ID>";
ATTRIBUTE[load_name] = "<DEVICE_ID>";
ATTRIBUTE[ptag] = "<DEVICE_ID>";
ATTRIBUTE[xfmr_name] = "<DEVICE_ID>";
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |