Hi Jason,
This came through a little while back in the IBM forum and the comment was this:
PS. After following those steps I still ran into an issue with the Initial Refresh token being to large: java.sql.SQLException: ORA-12899: value too large for column "MAXIMO"."INBOUNDCOMMCFG"."OAUTHACCESSTOKEN" (actual: 2032, maximum: 2000).
IBM advised the following, which worked for me: "There is a limitation on Oracle where crypto fields cannot be expanded beyond 2000. The access token is transitory and doesn't need to be persistent. Re-create the fields as non-persistent and expand it, fixing the issue you are observing."
Here is the url from the forum:
https://community.ibm.com/community/user/asset-facilities/communities/community-home/digestviewer/viewthread?MessageKey=6b5e36fd-2b8a-4a34-819f-71c28525f2b6&CommunityKey=3d7261ae-48f7-481d-b675-a40eb407e0fd&tab=digestviewer#bm6b5e36fd-2b8a-4a34-819f-71c28525f2b6
------------------------------
Jeff Tippett
MGI Maintenance Group Inc.
------------------------------
Original Message:
Sent: 04-26-2024 08:27
From: Jason Hankins
Subject: Email Listener and OFF365 problems
I have tried to setup the email listener the OFF365 using IBM's recommendations from article
Email Listener OAuth Configuration with Office 365 (ibm.com).
Our error : Caused by: oracle.jdbc.OracleDatabaseException: ORA-12899: value too large for column "MAXIMO"."INBOUNDCOMMCFG"."OAUTHACCESSTOKEN" (actual: 2208, maximum: 2000)
note: if I just use an IMAP account with OFF365 the listener would work

IBM WebSphere Application Server 9.0.5.15
Tivoli's process automation engine 7.6.1.3-IFIX20221121-1310 Build 20220823-0909
Oracle 19.1 (Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production Version 19.21.0.0.0)
Is there a patch or workaround?
Any help would be much appreciated.
#Administration
#Integrations
#MaximoUserGroups
------------------------------
Jason Hankins
City of Cambridge
------------------------------