My Oracle Support Banner

Submitting a Change Fails with Error: " Get Invalid Name Pattern: AGILE.NUMBER" (Doc ID 1933651.1)

Last updated on JUNE 21, 2018

Applies to:

Oracle Agile PLM Framework - Version 9.3.2.0 and later
Information in this document applies to any platform.

Symptoms

On : 9.3.2.0 version, Web client (CS)

When attempting to Submit a Change (MCO, ECO) , Agile gives an "invalid name pattern: AGILE.NUMBER" error and cannot Submit
the following error occurs: "invalid name pattern: AGILE.NUMBER"

The issue can be reproduced at will with the following steps:
1. Existing MCO or newly created ECO
2. At Pending, if Pass Audit is set to yes, changing status from Pending to Submit fails with invalid name pattern: AGILE.NUMBER
3. At Pending, if Pass Audit is set to No, change (ECO/MCO) can be moved all the way to CCB
4. At CCB, regardless of Pass Audit value, cannot change status, fails with invalid name pattern: AGILE.NUMBER

DataLoad was used to load data

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
Cause
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.