MogDB
Ecological Tools
Doc Menu

GAUSS-00501 – GAUSS-00600


GAUSS-00501 – GAUSS-00510


GAUSS-00501: "template database '%s' does not exist"

SQLSTATE: 3D000

Description: The template database template1 does not exist.

Solution: The template1 database is lost due to a database system exception. Restart the database or manually create the template1 database.

GAUSS-00502: "permission denied to copy database '%s'"

SQLSTATE: 42501

Description: In the syntax for creating a database, if the original database is not a template database, the user role does not have permission to create a database.

Solution: In the syntax for creating a database, if the original database is not a template database, only users who have the CREATEDB permission or the system administrator can create a database. Ensure that the user has the required permission.

GAUSS-00503: "invalid server encoding %d"

SQLSTATE: 42809

Description: In the syntax for creating a database, the specified encoding format is invalid.

Solution: Ensure that the encoding format must be GBK, UTF8, or Latin1.

GAUSS-00504: "invalid locale name: '%s'"

SQLSTATE: 42809

Description: When you create a database, the specified database character set is invalid.

Solution: In the syntax for creating a database, ensure that the character set specified for the new database must match that of the template database. Use the show lc_collate; command to query the character set of the template database.

GAUSS-00505: "new encoding (%s) is incompatible with the encoding of the template database (%s)"

SQLSTATE: 22023

Description: In the syntax for creating a database, the character encoding specified for the new database does not match that of the template database template0.

Solution: In the syntax for creating a database, ensure that the character encoding specified for the new database must match that of the template database template0. Use show server_encoding; to query the character encoding of the template database template0. Then, modify the character encoding specified for the created database.

GAUSS-00506: "new collation (%s) is incompatible with the collation of the template database (%s)"

SQLSTATE: 22023

Description: In the syntax for creating a database, the character set specified for the new database does not match that of the template database template0.

Solution: In the syntax for creating a database, ensure that the character set specified for the new database must match that of the template database template0. Use the show lc_collate; command to query the character set of the template database template0. Then, modify the character set specified for the created database.

GAUSS-00507: "new LC_CTYPE (%s) is incompatible with the LC_CTYPE of the template database (%s)"

SQLSTATE: 22023

Description: In the syntax for creating a database, the character type specified for the new database does not match that of the template database template0.

Solution: In the syntax for creating a database, ensure that the character type specified for the new database must match that of the template database template0. Use the show lc_ctype; command to query the character type of the template database template0. Then, modify the character type specified for the created database.

GAUSS-00508: "pg_global cannot be used as default tablespace"

SQLSTATE: 22023

Description: In the syntax for creating a database, the default tablespace specified for the new database is pg_global.

Solution: In the syntax for creating a database, ensure that the default tablespace specified for the new database is not pg_global. Currently, only the default tablespace is supported.

GAUSS-00509: "cannot assign new default tablespace '%s'"

SQLSTATE: 0A000

Description: In the syntax for creating a database, the default tablespace specified for the new database is pg_global.

Solution: In the syntax for creating a database, ensure that the directory for the tablespace is valid when specifying a tablespace other than the default tablespace and the global tablespace for the new tablespace. If the directory is invalid, create a valid directory.

GAUSS-00510: "database '%s' already exists"

SQLSTATE: 42P04

Description: The database name already exists.

Solution: Use the \l command to check whether the database name exists. If yes, rename the database.


GAUSS-00511 – GAUSS-00520


GAUSS-00511: "source database '%s' is being accessed by other users"

SQLSTATE: 55006

Description: The database is being accessed by other users.

Solution: If it is accessed by other users, data is inconsistent. In this case, deny access by other users and log in to the database again.

GAUSS-00512: "encoding '%s' does not match locale '%s'"

SQLSTATE: 22023

Description: The character encoding specified by the currently created database does not match that obtained from a specified character type.

Solution: Ensure that the character encoding specified by the currently created database matches that obtained from a specified character type. If they are inconsistent, specify them to be the same when creating data again.

GAUSS-00513: "database '%s' does not exist"

SQLSTATE: 3D000

Description: When the DROP DATABASE syntax is used to delete a database, this database does not exist or is invalid.

Solution: Ensure that the deleted database is a valid one.

GAUSS-00514: "cannot drop a template database"

SQLSTATE: 42809

Description: Attempting to delete the template database template0 or template1 is an invalid operation.

Solution: Specify a database to be deleted again because the default template database template0 or template1 cannot be deleted.

GAUSS-00515: "cannot drop the currently open database"

SQLSTATE: 55006

Description: The database to be deleted is being accessed by other users and cannot be deleted.

Solution: Ensure that the database to be deleted is not being accessed by other users and instruct the users to log out of the database and then delete the database again.

GAUSS-00516: "cannot drop the default database"

SQLSTATE: 42809

Description: Invalid operation to delete the default database postgres.

Solution: Do not delete the default database postgres.

GAUSS-00517: "database '%s' is being accessed by other users"

SQLSTATE: 55006

Description: The database is being accessed by other users.

Solution: If it is accessed by other users, data is inconsistent. In this case, deny access by other users and delete the database again.

GAUSS-00519: "permission denied to rename database"

SQLSTATE: 42501

Description: You do not have permission to change the database name.

Solution: Change the database name as a database owner or an administrator user.

GAUSS-00520: "current database cannot be renamed"

SQLSTATE: 0A000

Description: The name of a database in use cannot be changed.

Solution: Do not change the name of the database in use.


GAUSS-00521 – GAUSS-00530


GAUSS-00521: "cannot change the tablespace of the currently open database"

SQLSTATE: 55006

Description: When a database is being accessed by other users, its tablespace cannot be modified using the ALTER DATABASE SET TABLESPACE syntax.

Solution: Ensure that other users are not accessing the database when modifying the database tablespace. If the database has been accessed by other users, log out of the database and attempt to modify the tablespace of the database again.

GAUSS-00522: "some relations of database '%s' are already in tablespace '%s'"

SQLSTATE: 55000

Description: If relationship objects, such as tables, indexes, and views, exist in the tablespace directory of a database, its tablespace cannot be modified using the ALTER DATABASE SET TABLESPACE syntax.

Solution: Ensure that no relationship objects, such as tables, indexes, and views, exist in a database when modifying the database tablespace. If such relationship objects exist, delete them and then attempt to modify the tablespace again.

GAUSS-00523: "could not remove directory '%s': %m"

SQLSTATE: XX000

Description:Internal system error.

Solution:Contact technical support.

GAUSS-00524: "permission denied to change owner of database"

SQLSTATE: 42501

Description: You do not have permission to modify the database owner using the ALTER DATABASE name OWNER TO newowner syntax.

Solution: Modify the database owner as a database owner or an administrator user using the ALTER DATABASE name OWNER TO newowner syntax.

GAUSS-00526: "could not create directory '%s': %m"

SQLSTATE: XX000

Description: When a database tablespace is being created, the following exceptions may occur in the directory of this tablespace: 1. The current user is not an administrator user and does not have permission to access this directory. 2. The file system is read-only. 3. This directory already exists. 4. Disk space is insufficient for creating a directory. 5. Hardware faults result in I/O errors. 6. An internal error occurs in MogDB. "

Solution: Perform the following operations to resolve the problems: 1. Ensure that the current user is an administrator user or has the database creation permission. 2. Change the file system permissions to read and write permissions if the file system is read-only. 3. Do not create a tablespace if the tablespace directory exists.

GAUSS-00527: "could not stat directory '%s': %m"

SQLSTATE: XX000

Description: The directory of a database tablespace to be created does not exist or the directory name is invalid.

Solution: Ensure that the directory of a database tablespace to be created is valid.

GAUSS-00528: "'%s' exists but is not a directory"

SQLSTATE: 42809

Description: The directory of a database tablespace to be created is incorrect.

Solution: Ensure that the directory of a database tablespace to be created is valid.

GAUSS-00529: "Permission denied to create tablespace '%s'."

SQLSTATE: 42501

Description: You do not have permission to create a tablespace in the database.

Solution: Create a tablespace in the database as a system administrator.

GAUSS-00530: "tablespace location cannot contain single quotes"

SQLSTATE: 42602

Description: When the CREATE TABLESPACE tablespace_name …LOCATION syntax is used to specify a tablespace directory, the location information strings are marked with single quotation marks (").

Solution: Mark location information strings with double quotation marks ("").


GAUSS-00531 – GAUSS-00540


GAUSS-00531: "tablespace location must be an absolute path"

SQLSTATE: 42P17

Description: When the CREATE TABLESPACE tablespace_name …LOCATION syntax is used to specify a tablespace directory, the location information strings indicate an incorrect path.

Solution: Specify an absolute path using the location information string.

GAUSS-00532: "tablespace location '%s' is too long"

SQLSTATE: 42P17

Description: When the CREATE TABLESPACE tablespace_name…LOCATION syntax is used to specify the length of a tablespace directory, the length value of the tablespace directory is greater than 1024.

Solution: Change the length value of the tablespace directory to a value less than or equal to 1024.

GAUSS-00533: "unacceptable tablespace name '%s'"

SQLSTATE: 42939

Description: When the CREATE TABLESPACE tablespace_name syntax is used to create a tablespace, the tablespace name is invalid.

Solution: Ensure that the tablespace name is unique in the database and does not start with pg which is used to name system tablespaces.

GAUSS-00534: "tablespace '%s' already exists"

SQLSTATE: 42710

Description: The tablespace name already exists.

Solution: Run \db to check whether the tablespace name exists. If yes, rename the tablespace.

GAUSS-00535: "tablespaces are not supported on this platform"

SQLSTATE: 0A000

Description: Tablespaces are not supported.

Solution: Do not use tablespaces.

GAUSS-00536: "Tablespace '%s' does not exist."

SQLSTATE: 42704

Description: The tablespace deleted using DROP TABLESPACE does not exist.

Solution: Run \db to check whether the tablespace name exists. Only tablespaces that exist in the database can be deleted.

GAUSS-00537: "tablespace '%s' is used by partitioned table '%s'"

SQLSTATE: 0A000

Description: Invalid operation to delete the tablespace used by a partitioned table.

Solution: Do not delete the tablespace that has been used by a partitioned table.

GAUSS-00538: "tablespace '%s' is not empty"

SQLSTATE: 55000

Description: The tablespace to be deleted is not empty.

Solution: Delete a tablespace only when it is empty.

GAUSS-00539: "directory '%s' does not exist"

SQLSTATE: 58P01

Description: When creating a tablespace, the tablespace directory $PGDATA/pg_tblspc/ does not exist.

Solution: Check whether the tablespace directory $PGDATA/pg_tblspc/ exists before creating a tablespace. If the directory does not exist, restart the database or a single node.

GAUSS-00540: "could not set permissions on directory '%s': %m"

SQLSTATE: XX000

Description: When creating a tablespace, read, write, and execute permissions failed to be set for the tablespace directory $PGDATA/pg_tblspc/.

Solution: Perform the following operations to resolve the problems:

  1. Ensure that the current user is an administrator user or has the database creation permission.
  2. Change the file system permissions to read and write permissions if the file system is read-only.
  3. Do not create a tablespace if the tablespace directory exists.

GAUSS-00541 – GAUSS-00550


GAUSS-00541: "directory '%s' already in use as a tablespace"

SQLSTATE: 55006

Description: The tablespace directory to be created exists.

Solution: Define the tablespace in another directory.

GAUSS-00542: "could not remove symbolic link '%s': %m"

SQLSTATE: XX000

Description: Failed to remove a sign-linking file.

Solution: Ensure that the symbol link points to a valid file.

GAUSS-00543: "could not create symbolic link '%s': %m"

SQLSTATE: XX000

Description: Failed to create a sign-linking file.

Solution: Check the error code to determine the error causes, such as no permission, insufficient disk space, and existed file. Then, handle the error based on the causes.

GAUSS-00544: "tablespace '%s' does not exist"

SQLSTATE: 42704

Description: The tablespace does not exist.

Solution: Ensure that the tablespace exists in the pg_tablespace system catalog.

GAUSS-00546: "could not create tablespace directory '%s': %m"

SQLSTATE: XX000

Description: Failed to create a tablespace.

Solution: Check the error code to determine the error causes, such as no permission, insufficient disk space, and existed file. Then, handle the error based on the causes.

GAUSS-00547: "could not access directory '%s': %m"

SQLSTATE: XX000

Description: Failed to access a tablespace directory.

Solution: Check the error code to determine the error causes, such as no permission, insufficient disk space, and existed file. Then, handle the error based on the causes.

GAUSS-00548: "tblspc_redo: unknown op code %u"

SQLSTATE: XX000

Description:Internal system error.

Solution:Contact technical support.

GAUSS-00549: "'%s' is an aggregate function"

SQLSTATE: 42809

Description: 1. Failed to delete an aggregate function using DROP FUNCTION. 2. Failed to modify an aggregate function using ALTER FUNCTION. 3. Failed to obtain the definition of an aggregate function using pg_get_functiondef.

Solution: Perform the following operations to resolve the problems: 1. Run DROP AGGREGATE to delete the aggregate function. 2. Run ALTER AGGREGATE to modify the aggregate function. 3. View the aggregate function in the pg_aggregate system catalog.

GAUSS-00550: "unexpected object type (%d)"

SQLSTATE: XX000

Description:Internal system error.

Solution:Contact technical support.


GAUSS-00551 – GAUSS-00560


GAUSS-00551: "could not determine which collation to use for view column '%s'"

SQLSTATE: 42P22

Description: The collation to be used by a view column cannot be determined.

Solution: Use the COLLATE clause to assign a collation to the column.

GAUSS-00552: "view must have at least one column"

SQLSTATE: 42P16

Description: The number of columns defining a view is smaller than 1.

Solution: Ensure that the number of columns defining a view is greater than or equal to 1.

GAUSS-00553: "'%s' is not a view"

SQLSTATE: 42809

Description: The object is not a view.

Solution: Ensure that the object is a view.

GAUSS-00554: "cannot drop columns from view"

SQLSTATE: 42P16

Description: Failed to delete columns from a view

Solution: Do not delete columns from a view.

GAUSS-00555: "cannot change name of view column '%s' to '%s'"

SQLSTATE: 42P16

Description: Failed to modify the columns in a view.

Solution: Do not modify the columns in a view.

GAUSS-00556: "cannot change data type of view column '%s' from %s to %s"

SQLSTATE: 42P16

Description: When CREATE OR REPLACE VIEW is used to define a view, the new view and the original view do not have the same column data type.

Solution: Ensure that the new view and the original view have the same column data type.

GAUSS-00557: "unexpected parse analysis result"

SQLSTATE: XX000

Description:Internal system error.

Solution:Contact technical support.

GAUSS-00559: "views must not contain data-modifying statements in WITH"

SQLSTATE: 0A000

Description: Statements used to define a view contain the WITH clause.

Solution: Ensure that a single SELECT statement is executed to query the results.

GAUSS-00560: "CREATE VIEW specifies more column names than columns"

SQLSTATE: 42601

Description: The number of columns defining a view is greater than that of columns in the returned results.

Solution: Ensure that the number of columns defining a view is not greater than that of columns in the returned results.


GAUSS-00561 – GAUSS-00570


GAUSS-00561: "views cannot be unlogged because they do not have storage"

SQLSTATE: 42601

Description: The view to be defined is set to UNLOGGED.

Solution: Do not set the view to be defined to UNLOGGED because it does not have actual storage.

GAUSS-00562: "unrecognized value for EXPLAIN option '%s': '%s'"

SQLSTATE: 22023

Description: The EXPLAIN FORMAT parameter cannot be recognized.

Solution: Ensure that the value of the EXPLAIN FORMAT parameter is TEXT, XML, JSON, or YAML.

GAUSS-00563: "unrecognized EXPLAIN option '%s'"

SQLSTATE: 42601

Description: The EXPLAIN parameter cannot be recognized.

Solution: Ensure that the value of the EXPLAIN parameter is ANALYZE, VERBOSE, COSTS, BUFFERS, NODES, NUM_NODES, TIMING, CPU, DETAIL, PERFORMANCE, or FORMAT.

GAUSS-00564: "EXPLAIN option BUFFERS requires ANALYZE"

SQLSTATE: 22023

Description:ANALYZE is not specified for EXPLAIN BUFFERS.

Solution: Specify ANALYZE for EXPLAIN BUFFERS.

GAUSS-00565: "EXPLAIN option CPU requires ANALYZE"

SQLSTATE: 22023

Description:ANALYZE is not specified for EXPLAIN CPU.

Solution: Specify ANALYZE for EXPLAIN CPU.

GAUSS-00566: "EXPLAIN option DETAIL requires ANALYZE"

SQLSTATE: 22023

Description:ANALYZE is not specified for EXPLAIN DETAIL.

Solution: Specify ANALYZE for EXPLAIN DETAIL.

GAUSS-00567: "EXPLAIN option TIMING requires ANALYZE"

SQLSTATE: 22023

Description:ANALYZE is not specified for EXPLAIN TIMING.

Solution: Specify ANALYZE for EXPLAIN TIMING.

GAUSS-00568: "EXPLAIN %s requires ANALYZE"

SQLSTATE: 22023

Description:ANALYZE is not specified for EXPLAIN CREATE TABLE AS SELECT or EXPLAIN SELECT INTO.

Solution: Specify ANALYZE for EXPLAIN CREATE TABLE AS SELECT or EXPLAIN SELECT INTO.

GAUSS-00569: "no tlist entry for key %d"

SQLSTATE: XX000

Description: Generated plan error.

Solution:Contact technical support.

GAUSS-00570: "cache lookup failed for index %u"

SQLSTATE: XX000

Description: Failed to find the index in the system catalog cache.

Solution: Ensure that the index name is correct.


GAUSS-00571 – GAUSS-00580


GAUSS-00571: "unrecognized DISCARD target: %d"

SQLSTATE: XX000

Description:Internal system error.

Solution:Contact technical support.

GAUSS-00572: "function '%s' was not called by trigger manager"

SQLSTATE: 39P01

Description: A function is not invoked by the trigger manager.

Solution: Ensure that the function is invoked as an AFTER row trigger.

GAUSS-00573: "function '%s' must be fired AFTER ROW"

SQLSTATE: 39P01

Description: A function is invoked before an AFTER row trigger is triggered.

Solution: Ensure that the function is invoked after the AFTER row trigger is triggered.

GAUSS-00574: "function '%s' must be fired for INSERT or UPDATE"

SQLSTATE: 39P01

Description: A trigger is not triggered by the INSERT/UPDATE statement.

Solution: Ensure that the trigger is triggered by the INSERT/UPDATE statement.

GAUSS-00575: "Permission denied to create role with option UNENCRYPTED."

SQLSTATE: XX000

Description: An error occurs when UNENCRYPTED is specified for CREATE ROLE.

Solution: Encrypt the password.

GAUSS-00579: "Permission denied to create role."

SQLSTATE: 42501

Description: You have no permission to create users.

Solution: Check user permissions. For permissions to create users, see en-us_topic_0237121098.html.

GAUSS-00580: "Separation of privileges is used,user can't be created because of too many privileges."

SQLSTATE: 42501

Description: The permissions specified for users exceed the limit during privilege separation.

Solution: Ensure that the permissions specified for users do not exceed the limit during privilege separation.


GAUSS-00581 – GAUSS-00590


GAUSS-00581: "role name '%s' is reserved"

SQLSTATE: 42939

Description: A username is a reserved keyword.

Solution: Ensure that the username is not the reserved keyword, for example, public or none.

GAUSS-00582: "role '%s' already exists"

SQLSTATE: 42710

Description: The username already exists.

Solution: Use a new username.

GAUSS-00584: "The password does not satisfy the complexity requirement"

SQLSTATE: XX000

Description: The password does not meet the complexity requirements.

Solution: 1. The password cannot be the same as the username. 2. The password contains at least eight characters and at least three of the following: uppercase characters (A to Z), lowercase characters (a to z), digits (0 to 9), and other characters (limited to ~!@#$%^&*()-_=+|[{}];:,<.>/?).

GAUSS-00588: "The password could not be NULL."

SQLSTATE: XX000

Description: The password is null.

Solution: Ensure that the password is not null.

GAUSS-00589: "unacceptable user name: fail to create same name schema for user '%s'"

SQLSTATE: 42939

Description: If the name of a user is invalid, a schema with the same name as the user cannot be created.

Solution: Ensure that the user name does not start with pg_ which is used to name system modes.

GAUSS-00590: "the relation pg_user_status is invalid"

SQLSTATE: XX000

Description:Internal system error.

Solution:Contact technical support.


GAUSS-00591 – GAUSS-00600


GAUSS-00591: "role '%s' does not exist"

SQLSTATE: 42704

Description: The user does not exist.

Solution: Check the user information in the system catalog pg_roles.

GAUSS-00593: "Permission denied to change privilege of the initial account."

SQLSTATE: 42501

Description: You have no permission to modify the rights of the initial user.

Solution: Query the system catalog to check whether you have that permission.

GAUSS-00594: "Permission denied to change password of the initial account."

SQLSTATE: 42501

Description: You have no permission to change the password of the initial user.

Solution: Query the system catalog to check whether you have that permission.