ORA-20177: Subvar in alias name cannot be resolved."jobid=12345 chain=EXAMPLE_PROCESS_FLOW alias name=AliasName_{#2} contains subvar#2 with login

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When Requesting a Process Flow, the below error is thrown and the Process Flow does not enter the Backlog:

ORA-20177: Subvar in alias name cannot be resolved."jobid=12345 chain=EXAMPLE_PROCESS_FLOW alias name=AliasName_{#2} contains subvar#2 with login.
ORA-06512: at "APPWORX.AWAPI2", line 4369
ORA-06512: at "APPWORX.AWAPI2", line 487
ORA-06512: at "APPWORX.SCHEDULING", line 765
ORA-06512: at "APPWORX.SCHEDULING", line 765
ORA-06512: at "APPWORX.SCHEDULING", line 1201
ORA-06512: at "APPWORX.AWAPI2", line 4283
ORA-06512: at "APPWORX.AWOP_API", line 732
ORA-06512: at "APPWORX.AW_WEB_API2", line 36
ORA-06512: at line 1

The main considerations are the bolded text, which indicates that a Subvar cannot be resolved. That subvar is set in the Process Flow Component's Alias name.

Note that the 2 in the error message "AliasName_{#2} contains subvar#2 with login" can be replaced with any number (e.g. 1, 3, 4, etc)

Cause

Instead of resolving or replacing {#2} with the Process Flow's number 2 prompt, there is an substitution variable with the name #2.

Resolution

There are 2 resolutions to this issue:

• Delete the Substitution Variable with the name #2. This is an illegal subvar name. If you create a new subvar, you will notice that subvar names beginning with a number is not allowed. This is because this type of value such as #2, is reserved for Process Flow prompts.
  
  
• If deleting subvar is not an option, edit subvar #2 and make sure that there is no Login value assigned in the Login field of the subvar, and Apply/OK