Discussion
Agent is going to Broken queue
Hi,
We have upgraded the application from 6.2 to 7.1.8. There is one agent which processes uploaded csv file and stores it into database. This agent is going to broken process but file upload through it is successful. There is no error in SMA also; not getting any error in tracer as well. In broken process reason for failure is saying as below
There was a problem getting a list: code: 972 SQLState: 42000 Message: ORA-00972: identifier is too long
Can you pls help resolving this issue.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
This looks like an oracle specific issue and oracle does not allow any object names more than 30 characters. As you are mentioning this issue is happening only after upgrade please check bot the list view queries in 6.2 and Pega 7 to see the differences and what is changed in Pega 7.
The following is one of the reason found in oracle forums.
Error:
ORA-00972: identifier is too long
Cause:
You tried to reference a table, cluster, view, index, synonym, tablespace, or username with a value that was longer than 30 characters.
Action:
The options to resolve this Oracle error are:
1.Names for tables, clusters, views, indexes, synonyms, tablespaces, and usernames must be 30 characters or less. You must shorten the name to no more than 30 characters for these objects.
After doing some analysis on the issue I found there is a listview which is referred in the agent activity. That listview gets list of operators for a given skill and accessgroup. Running that listview is giving error "There was a problem getting a list: code: 972 SQLState: 42000 Message: ORA-00972: identifier is too long". Though the same listview is running fine in 6.2. Please help