‎TSM reporting errors using EBA 3.1 with TSM server v5.5 | DELL Technologies

Start a Conversation

wcollign

updated

15 years ago

Solved!

wcollign

3 Posts

0

816

October 24th, 2011 08:00

TSM reporting errors using EBA 3.1 with TSM server v5.5

With the understanding I am running a dated version of EPA/DPA I am getting the following errors in the EBA collector.log file.

ANR2914E SQL identifer token 'PATHS.DESTINATION_NAME' is too long; name or component exceeds 18 characters.

I am working on getting the upgrade to DPA 5.8 planned and approved. In the meantime is there a resolution/workaround for this issue?

Will this occur in DPA 5.8?

W
wcollign
3 Posts
147
0
Posted November 8th, 2011 09:00
For anyone who experienced the same issue I did the problem was a bug in TSM at v5.5. The solution is in APAR IC71586. Need to apply fix pack and get to v5.5.5.2.

For those interested in know how long it takes to upgrade EBA 3.1 to DPA 5.0 It took me about 5 hours running on a VM Windows 2003 with a 18 GB SQL database.

The upgrade from DPA 5.0 o 5.8 took about less than an hour.
W
wcollign
3 Posts
147
0
Posted November 3rd, 2011 12:00
I have upgraded to 5.0 then to 5.8 and I am still getting the following error. Has any had this issue? Any thoughts on how to resolve.

ANR2914E SQL identifier token 'STGPOOLS.STGPOOL_NAME' is too long; name or component exceeds 18 characters.