Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
mike_se Contributor.

PPM Support Tip: Very large Request Type ID's cause error when enabling Notes History for a Field

A new KCS article was published: KM00664454.

"When Request Type ID's are over seven digits, enabling Notes History triggers causes an unknown error due to 30 character trigger name limitation"

Whenever updating any Request Type, getting an error:
"The session with poolID [XXX] is no longer available"

Followed by a GUID error:  
"An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number: GUID=XXXXXX"

Issue is caused when enabling Notes History for a Field.

Defect QCCR1L53049

Request Types (RT) had seven-digit ID's. Due to this, an Oracle limitation is encountered when the audit-trigger is refreshed upon RT save. The audit trigger has a hard coded string plus the RT-id in the name. Due to an Oracle limitations, this complete trigger string may not exceed 30 characters. With the long RT-id, the name was over the limit and fails.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
Labels (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.