Checking GUC Parameters
GaussDB provides many GUC parameters to manage behaviors of the database system. UGO converts SQL syntax based on a group of GUC parameters that are compatible with the source database. Set GUC parameters as prompted during the object migration pre-check. Otherwise, the success rate and availability of the final object migration may be affected.
- The GUC parameter check is performed based on the target database version you selected during evaluation project creation, instead of the target database version that is actually connected.
- If the target database type is GaussDB Centralized (M-compatible mode), GUC parameters cannot be checked.
- For details about how to set the GaussDB GUC parameters, see the check item prompt on the pre-check page or see How Do I Set GaussDB GUC Parameters?
Source DB Type |
Target DB Version |
Check Item |
---|---|---|
MySQL |
GaussDB Centralized V2.0-3.1 Enterprise Edition |
- |
GaussDB Centralized V2.0-3.2 Enterprise Edition |
b_format_behavior_compat_options |
|
GaussDB Distributed V2.0-3.2 Enterprise Edition |
- |
|
GaussDB Centralized V2.0-8.0 Enterprise Edition |
b_format_version, b_format_dev_version |
|
GaussDB Distributed V2.0-8.0 Enterprise Edition |
b_format_version, b_format_dev_version |
|
GaussDB Centralized V2.0-8.100 Enterprise Edition |
b_format_version, b_format_dev_version |
|
GaussDB Distributed V2.0-8.100 Enterprise Edition |
b_format_version, b_format_dev_version |
|
GaussDB Centralized (M-compatible mode) V2.0-8.100 Enterprise Edition |
m_format_behavior_compat_options, m_format_dev_version |
|
GaussDB Centralized (M-compatible mode) V2.0-8.200 Enterprise Edition |
m_format_behavior_compat_options, m_format_dev_version |
|
GaussDB Centralized (M-compatible mode) V2.0-9.0 Enterprise Edition |
m_format_behavior_compat_options, m_format_dev_version |
|
Oracle |
GaussDB Centralized V2.0-3.1 Enterprise Edition |
behavior_compat_options, sql_beta_feature, a_format_version, a_format_dev_version |
GaussDB Centralized V2.0-3.2 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-3.2 Enterprise Edition |
behavior_compat_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Centralized V2.0-3.3 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, IntervalStyle, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-3.3 Enterprise Edition |
behavior_compat_options, sql_beta_feature, IntervalStyle, a_format_version, a_format_dev_version |
|
GaussDB Centralized V2.0-8.0 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, IntervalStyle, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-8.0 Enterprise Edition |
behavior_compat_options, sql_beta_feature, IntervalStyle, a_format_version, a_format_dev_version |
|
GaussDB Centralized V2.0-8.100 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, IntervalStyle, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-8.100 Enterprise Edition |
behavior_compat_options, sql_beta_feature, IntervalStyle, a_format_version, a_format_dev_version |
|
GaussDB Centralized V2.0-8.200 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, IntervalStyle, a_format_version, a_format_dev_version, a_format_date_timestamp |
|
GaussDB Distributed V2.0-8.200 Enterprise Edition |
behavior_compat_options, sql_beta_feature, IntervalStyle, a_format_version, a_format_dev_version, a_format_date_timestamp |
|
GaussDB Centralized V2.0-9.0 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, IntervalStyle, mapping_date_to_datea, a_format_version, a_format_dev_version, a_format_date_timestamp |
|
GaussDB Distributed V2.0-9.0 Enterprise Edition |
behavior_compat_options, sql_beta_feature, IntervalStyle, mapping_date_to_datea, a_format_version, a_format_dev_version, a_format_date_timestamp |
|
Microsoft SQL Server |
GaussDB Centralized V2.0-3.1 Enterprise Edition |
behavior_compat_options, sql_beta_feature, a_format_version, a_format_dev_version |
GaussDB Centralized V2.0-3.2 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-3.2 Enterprise Edition |
behavior_compat_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Centralized V2.0-8.0 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-8.0 Enterprise Edition |
behavior_compat_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Centralized V2.0-8.100 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-8.100 Enterprise Edition |
behavior_compat_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Centralized V2.0-8.200 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-8.200 Enterprise Edition |
behavior_compat_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Centralized V2.0-9.0 Enterprise Edition |
behavior_compat_options, plsql_compile_check_options, sql_beta_feature, a_format_version, a_format_dev_version |
|
GaussDB Distributed V2.0-9.0 Enterprise Edition |
behavior_compat_options, sql_beta_feature, a_format_version, a_format_dev_version |
The plsql_compile_check_options parameter of GaussDB Centralized is used to verify all statements in functions, procedures, and packages. If there are undefined objects in the statements, an alarm is reported. To avoid false alarms in the production environment, this parameter is recommended only in the test environment.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot