Problems with upgrade from 6.7.3 (build 38370) to 7.9.6 (build 41879

[Colin]

Thanks.

As we (now) document in our requirements:

Only MAX_STRING_SIZE=STANDARD parameter is supported, not EXTENDED.

I think this wasn’t a concern when SonarQube 7.9 was released because the EXTENDED set

Ideally, you would be able to move your data to a databse where max_string_size is set to STANDARD – according to Oracle docs, it doesn’t seem that it’s possible to go the other way.

Although it might still be possible:

I can't analyse old projects after migration from 6.7.7 to 7.9.1: ORA-00600: internal error code

Hi, if it’s help someone: The problem was the parameter max_string_size in database. It was setup originally with the value EXTEND, but when it was set up with STANDARD, the problem did not appear. This thread can close it.

I suggest consulting with your Oracle DBAs.

@Zura_Pantskhava

I guess you cannot say that those indices are not necessary and won’t cause any problems in the future

You’re right. Having all required indicies, and a supported max_string_size are important as you upgrade across many SonarQube versions.