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.
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.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”