My Oracle Support Banner

Preprocessor Parser Is Failing When A String In The MP File Ends With A Double Backslash (Doc ID 2292293.1)

Last updated on MARCH 20, 2019

Applies to:

Oracle Utilities Network Management System - Version 2.3.0.0.0 to 2.3.0.1.0 [Release 2.3]
Oracle Network Management for Utilities - DMS - Version 2.3.0.0.0 to 2.3.0.1.0 [Release 2.3]
Information in this document applies to any platform.

Symptoms

**Examples provided in this article do not represent real life personal/confidential information**

**Disclaimer:** This KM article may include the following abbreviations:

NMS - Oracle Network Management System
DMS - Oracle Network Management for Utilities
MP - Model Preprocessor

Preprocessor parser is failing when a string in the MP file ends with a double backslash

The preprocessor parser is failing on the following string...
  ATTRIBUTE[e!transformer_oh_bank.location_description]="125 ORACLE AV \\";

If you put a space after the double backslash and before the end " the parser works without issue and an MP file is created.

ERROR
ERROR: Unmatched delimiter on record at line 97261
FATAL: Could not load MP file: /scratch/users/lge1/data/mp/FDR_90.mp

STEPS
The issue can be reproduced at will with the following steps:
1. Add a double backslash to the end of an attribute string in an MP file.
2. Attempt to build the map.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.