FNCI 2019.R1 - "MySQL New Character Set Default is utf8mb4" and /etc/my.cnf settings.

lpopescu · ‎Apr 17, 2019

MySQL server running on CentOS 7.

I upgraded my core/scan server from FNCI 2018.R4 to 2019.R1

In the FNCI-RN-2019R1.pdf file, page 8 states the new character set: "MySQL New Character Set Default is utf8mb4"

"For upgraded instances, the character set will be automatically updated for every existing table
and column when you first star the application after the upgrade. No additional action is required
for utf8mb4 support."

In my /etc/my.cnf file I have an entry "character-set-server = utf8". Should the "character-set-server = utf8" be changed to "character-set-server = utf8mb4"?

Any other changes required to the /etc/my.cnf file?

(see /etc/my.cnf file below)

-----------------------------------------------------------------------------------------------------

[mysqld]
####### FlexNetCodeInsight #######
default-storage-engine=INNODB
character-set-server = utf8
collation-server=utf8_general_ci
innodb_buffer_pool_size=12G
innodb_log_file_size=8G
innodb_log_buffer_size=12G
max_allowed_packet=100MB
innodb_fast_shutdown=0
##################################

datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

# Recommended in standard MySQL setup
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

-----------------------------------------------------------------------------------------------------

Thanks,

LP

jwilliams · ‎Apr 18, 2019

Hi @lpopescu ,

Leaving the my.cnf set to UTF-8 will be fine. You do not need to perform these changes as these are handled for you by the product. I can also confirm that no further changes to the my.cnf file are required.

Kind Regards,

Jon