Upgrade SAP B1 v10 2208 to v10 2402 still has issues with table indices

[Pipalia1]

As advised, I upgraded from v9.3 to v10 2208 first and had no issues or warnings. But the moment I upgrade to 2402, I get the same error with table indices as last time.

Here is the attached log snippet (it's comparing against SAP metadata, where can I find this meta data or what are the steps to resolve this issue):

Desc: (9) Check if all SAP Business One table indices in the database are consistent with SAP Business One metadata. For more information, see SAP Note 2128874. # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:08.734664 StpWiz Note I Tec Begin time: 20240404 155402 # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec AEK1: Index #0 [PRIMARY] is different; unique, should be: # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec #0 , alias: AbsEntry # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec #1 , alias: LineNum # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec #2 , alias: LogInstanc # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec #3 , alias: VatCatgory # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec AEK1: Index #0 [PRIMARY] is: # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec #0 , alias: AbsEntry # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec #1 , alias: LineNum # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:15.922199 StpWiz Note I Tec #2 , alias: LogInstanc # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:16.937833 StpWiz Note I Tec Table CINF has different number of indexes than expected; 1, should be 2 # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.140967 StpWiz Note I Tec EBK1: Index #0 [PRIMARY] is different; unique, should be: # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.140967 StpWiz Note I Tec #0 , alias: AbsEntry # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.140967 StpWiz Note I Tec #1 , alias: LineNum # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.140967 StpWiz Note I Tec #2 , alias: VatCatgory # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.140967 StpWiz Note I Tec EBK1: Index #0 [PRIMARY] is: # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.140967 StpWiz Note I Tec #0 , alias: AbsEntry # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.140967 StpWiz Note I Tec #1 , alias: LineNum # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.172217 StpWiz Note I Tec ECM6: Index #0 [PRIMARY] is different; unique, should be: # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.172217 StpWiz Note I Tec #0 , alias: CodeStr # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.172217 StpWiz Note I Tec ECM6: Index #0 [PRIMARY] is: # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:18.172217 StpWiz Note I Tec #0 , alias: Code # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:19.453479 StpWiz Note I Tec Table OBNK has different number of indexes than expected; 3, should be 2 # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:20.078490 StpWiz Note I Tec Table ODRN has different number of indexes than expected; 1, should be 2 # # TID=4344 Logger.cpp 132 Customized=0
2024-04-04 15:54:25.344168 StpWiz Note I Tec End time: 20240404 155418 # # TID=4344 Logger.cpp 132 Customized=0

[ANKIT_CHAUHAN · Accepted solution]

Hi Pipalia1,

It is asking to refer to SAP Note 2128874.

Have you checked the SAP Note?

Kind regards,

ANKIT CHAUHAN

SAP Business One Support

[Pipalia1 · Accepted solution]

Hi Ankit, yes I have, so are we then advised to accept it even if we haven't modified the indexes and the upgrade will fix itself? "During the upgrade process, detected illegal changes to the database indexes will be overwritten according to the database structure template. As result, these changes will be lost."

[ANKIT_CHAUHAN · Accepted solution]

Hi Pipalia1,

As you are confirming that there is nothing done from your end, it is better to confirm it and proceed further with the upgrade.

Kind regards,

ANKIT CHAUHAN

SAP Business One Support