Check Detail
1. Check the following parameter values of the source and target databases. If there is a difference in parameter values between the source and target databases, a verification warning will be prompted. The warning will not block the migration task, but it will have an impact on the business. Please assess and decide whether to modify by yourself.
2. TimeZone,lc_monetary,lc_numeric,array_nulls,server_encoding,DateStyle,extra_float_digits ,gin_fuzzy_search_limit,xmlbinary,constraint_exclusion.
The parameter is not set consistently. The specific impact is as follows.
TimeZone: Setting the time zone of an instance. If this parameter value is inconsistent, it may lead to data errors after migration.
lc_monetary: Setting the currency mode of an instance. If this parameter value is inconsistent, it may lead to incorrect currency numbers after migration.
lc_numeric: Setting the digital mode of an instance. If this parameter value is inconsistent, it may lead to data errors after migration.
array_nulls: Setting whether the array allows empty values. If this parameter value is inconsistent, it may lead to data inconsistency after migration, and some data may fail to migrate.
server_encoding: Setting the character set of an instance. If this parameter value is inconsistent, it may lead to garbled characters in data storage.
DateStyle: Setting the date display format. If this parameter value is inconsistent, it may fail to migrate data.
extra_float_digits: Setting the output precision of floating-point values. If this parameter value is inconsistent, it will affect data accuracy. In high-precision database usage scenarios, it can cause data inconsistency after migration.
gin_fuzzy_search_limit: Set the soft upper limit of the set size returned by the GIN index. If this parameter value is inconsistent, it can cause inconsistent data display results after migration.
xmlbinary: Setting the result issue of XML function transformation. If this parameter value is inconsistent, it may lead to inconsistent behavior when executing the corresponding function in the target database compared to the source database.
constraint_exclusion: Setting whether constraints take effect. If this parameter value is inconsistent, it may lead to data inconsistency after migration.
3. Check whether the character set settings of the source and target databases are inconsistent. If they are inconsistent, errors will be reported during the validation task. Change to the same setting.
Remediation Method
1. Log in to the source database using a superuser account.
2. Execute the following example statements to modify corresponding parameters:
Users can first select the parameter modification of the source database. If the corresponding parameter of the source database cannot be modified, then the corresponding parameter of the target database needs to be modified. For the modification of the target database, please seek online support. The server_encoding parameter cannot be modified in the source database. If this parameter is abnormal, please check whether it has been created in the target database. If it has been created and is inconsistent with the source database, you need to apply for a new instance. If it has not been created, please refer to the following methods for modification (currently, the cloud database instance only supports two character sets: UTF8 and LATIN).
alter system set timezone='<parameter value>';
alter system set lc_monetary='<parameter value>';
alter system set lc_numeric='<parameter value>';