Cannot initialize database
Issue 1:
During DB initialization, the error code -2000 is displayed and the following is recorded in the UC debug log.
java.sql.SQLSyntaxErrorException: Access denied; you need (at least one of) the SUPER privilege(s) for this operation
Cause 1:
Database administrator user does not have the root equivalent privileges.
Solution 1:
Use an administrator user with root equivalent privileges.
If that is not possible, use an administrator user with SUPER or SET_USER_ID privileges and set the following property in the advanced options.
com.brekeke.chat.ChatAdminMethod.CREATE_DATABASE_GLOBAL_VARIABLES={}
Issue 2:
During DB initialization, the error code -2000 is displayed and the following is recorded in the UC debug log.
java.sql.SQLException: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
Cause 2:
An environment where the database administrator user does not have root equivalent privileges, binary logging is enabled, and log_bin_trust_function_creators is 0.
Solution 2:
Temporarily change log_bin_trust_function_creators to 1 in your database product’s configuration.
After the initialization is completed, restore the original value.
Issue 3:
During DB initialization, the error code -2000 is displayed and the following is recorded in the UC debug log.
java.sql.SQLSyntaxErrorException: Access denied; you need (at least one of) the SUPER or SET_USER_ID privilege(s) for this operation
Cause 3:
Database administrator user does not have SET_USER_ID privilege.
Solution 3:
Use an admin user with the SET_USER_ID privilege.
If that is not possible, set the following property in advanced options.
However, with this setting, migrating dumps to other database servers is not supported.
com.brekeke.chat.ChatAdminMethod.CREATE_DATABASE_WITHOUT_DEFINER=true
Issue 4:
When initializing the DB, the following replication error occurs in the database configured for replication.
Error 'This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)' on query.
Cause 4:
log_bin_trust_function_creators is 0.
Solution 4:
Temporarily change log_bin_trust_function_creators to 1 in the database setting that is not directly accessed by the UC that performs the initialization process among the databases that configure replication.
After the initialization is completed, restore the original value.
Issue 5:
During DB initialization, the error code -2000 is displayed and the following is recorded in the UC debug log.
java.sql.SQLException: The server time zone value '????' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.
Cause 5:
A time zone recognized by Java is not set in the database product settings.
Solution 5:
First, check the time zone setting of the server where the database product is installed on, and if it is not set correctly, it may be solved just by setting it.
According to the setting of the server, set, for example, serverTimezone=Asia/Tokyo in the option column of the database initialization dialog.