What's New
Function Overview
Product Bulletin
- Product Notice
- Version Support Notes
Service Overview
- GaussDB(DWS) Infographics
- What Is GaussDB(DWS)?
- Data Warehouse Types
- Data Warehouse Flavors
- Advantages
- Application Scenarios
- Functions
- Concepts
- Related Services
- Security
- GaussDB(DWS) Permissions Management
- GaussDB(DWS) Access
- Restrictions
- Technical Support
- Service Quotas
- GaussDB(DWS) Technical Specifications
Billing
- GaussDB(DWS) Billing Overview
- Billing Modes
- Item
- Billing Examples
- Billing Mode Change
- Renewal
  - Overview
  - Manual Renewal
- Bills
- Arrears
- Stopping Billing
- Cost Management
- Billing FAQs
Getting Started
- Checkpoint Vehicle Analysis
- Supply Chain Requirement Analysis of a Company
- Operations Status Analysis of a Retail Department Store
- Creating a Time Series Table
- Best Practices of Hot and Cold Data Management
- Best Practices for Automatic Partition Management
- Creating a Cluster and Connecting to It
- Using CDM to Migrate MySQL Data to the GaussDB(DWS) Cluster
- Using DLI Flink Jobs to Write Kafka Data to GaussDB(DWS) in Real Time
- Basic SQL Operations
- Database Quick Start
- Getting Started with Common Practices
User Guide
- Using GaussDB(DWS)
- Preparations
- Creating a GaussDB(DWS) Cluster
- Connecting to a GaussDB(DWS) Cluster
- Creating a GaussDB(DWS) Database and User
- Migrating Service Data to a GaussDB(DWS) Cluster
  - Migrating Data to a GaussDB(DWS) Cluster Using GDS-Kafka
  - Data Source Management
- GaussDB(DWS) Cluster Data Security and Encryption
- GaussDB(DWS) Cluster Management
- GaussDB(DWS) Cluster O&M
Best Practices
- Import and Export
- Data Migration
- Data Analytics
- Decoupled Storage and Compute
  - DWS 3.0 Decoupled Storage and Compute Usage Suggestions and Performance Optimization
- Data Development
- Database Management
- Performance Tuning
  - Optimizing Table Structure Design to Enhance GaussDB(DWS) Query Performance
  - Analyzing SQL Statements That Are Being Executed to Handle GaussDB(DWS) Performance Issues
- Cluster Management
  - Binding Different Resource Pools to Two Types of Jobs to Balance Load for GaussDB(DWS)
  - Scaling Options for GaussDB(DWS) with a Coupled Storage-Compute Architecture
Data Migration and Synchronization
- Data Migration to GaussDB(DWS)
- Importing Data
- Full Database Migration
  - Using CDM to Migrate Data to GaussDB(DWS)
  - Using DSC to Migrate SQL Scripts
- Real-time Import
  - Using DRS to Import Data to GaussDB(DWS)
  - Real-time Data Import From Kafka GaussDB(DWS)
- Metadata Migration
  - Using gs_dump and gs_dumpall to Export Metadata
  - Using gs_restore to Import Data
- Exporting Data
- Other Operations
Developer Guide
- Standard data warehouse (9.1.0.x)
- Standard data warehouse (8.1.3.x)
- Hybrid Data Warehouse (9.1.0.x）
- Hybrid Data Warehouse (8.1.3.x）
- Historical Versions
SQL Syntax Reference
- SQL Syntax Reference (9.1.0.x)
- SQL Syntax Reference (8.1.3.x)
- Historical Versions
Performance Tuning
- Overview of Query Performance Optimization
- Query Execution Process
- SQL Execution Plan
- SQL Optimization Guide
- Optimization Cases
- SQL Execution Troubleshooting
- query_band Load Identification
- Common Performance Parameter Optimization Design
Tool Guide
- Overview
- Downloading Related Tools
- gsql
- Data Studio
- GDS
- DSC
- DataCheck
- DWS-Connector
- Server Tool
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- API Description
- Application Cases
  - Using Postman to Call the API for Creating a Cluster
  - Using Postman to Call the API for Creating a Snapshot
- Introduction
- Appendix
SDK Reference
- SDK Overview
FAQs
- Top FAQs
- Product Consulting
- Database Connections
- Data Migration
- Database Usage
- Cluster Management
- Account Permissions
- Database Performance
- Backup and Restoration
  1. Why Does It Take a Long Time to Create an Automated Snapshot in GaussDB(DWS)?
  2. Does a GaussDB(DWS) Snapshot Have the Same Function as an EVS Snapshot?
Troubleshooting
- Database Connections
- JDBC/ODBC
- Data Import and Export
- Database Parameter Modification
- Account/Permission/Password
- Cluster Performance
- Cluster Exceptions
  - The Disk Usage Alarm Is Frequently Generated
- Database Use
Videos
Performance White Paper
- Overview
- Test Result
  - TPC-H Single Query Test
  - TPC-DS Single Query Test
- Test Methods
- Appendixes
  - TPC-H Test Sets
  - TPC-DS Test Sets
Technical White Paper
- GaussDB(DWS)
- Platforms and Technical Specifications Supported by GaussDB(DWS)
  - Technical Specifications
- GaussDB(DWS) Core Technologies
- GaussDB(DWS) Tools
  - Client Tools
  - Database Monitoring Tool
- External APIs
Error Code Reference
- 8.2.0 and earlier versions
  - Management Console Error Code
  - Data Warehouse Service Error Codes
- 8.2.1 or later versions
Glossary
More Documents
- User Guide
- API Reference (ME-Abu Dhabi Region)
- Developer Guide (ME-Abu Dhabi Region)
- SQL Syntax Reference (ME-Abu Dhabi Region)
- Tool Guide (ME-Abu Dhabi Region)
- Error Code Reference (ME-Abu Dhabi Region)
  - Management Console Error Code
- User Guide (Paris Region)
- API Reference (Paris Region)
- Developer Guide (Paris Region)
- SQL Syntax Reference (Paris Region)
- Tool Guide (Paris Region)
- Error Code Reference (Paris Region)
  - Management Console Error Code
- User Guide (Kuala Lumpur Region)
- API Reference (Kuala Lumpur Region)
- Developer Guide (Kuala Lumpur Region)
- SQL Syntax Reference (Kuala Lumpur Region)
- Tool Guide (Kuala Lumpur Region)
- Error Code Reference (Kuala Lumpur Region)
  - Management Console Error Code
General Reference
- Glossary
- Service Level Agreement
- White Papers
- Endpoints
- Permissions

On this page

Show all

Help Center/ GaussDB(DWS)/ Troubleshooting/ Account/Permission/Password/ A User Cannot Be Deleted Due to Its Dependencies

A User Cannot Be Deleted Due to Its Dependencies

Updated on 2025-01-06 GMT+08:00

View PDF

Symptom

When a user is no longer used or the role of the user changes, the user account needs to be deregistered and the permission needs to be revoked. However, when the user is deleted, an error message similar to role "u1" cannot be dropped because some objects depend on it is displayed.

For example, if you want to delete user u1, the following information is displayed:

    
       testdb=# DROP USER u1;
ERROR:  role "u1" cannot be dropped because some objects depend on it 
DETAIL:  owner of database testdb 
3 objects in database gaussdb

Possible Causes

If the permissions of a user or role are complex and have many dependencies, an error message is displayed when you delete the user or role, indicating that the user or role has dependencies and cannot be deleted. Obtain the following information based on the error information:

The user to be deleted is the owner of database testdb.
It has three dependent objects are in the GaussDB database.

Handling Procedure

If a user to be deleted is the owner of a database. You need to reassign the object ownerships to another user. Use either of the following methods:

Method 1: Transfer the database ownership to another user. For example, run the ALTER statement to change the owner user u1 of the testdb database to u2.

       
          testdb=# ALTER DATABASE testdb OWNER to u2;
ALTER DATABASE
testdb=# \l 
                                   List of databases    
   Name    |   Owner  | Encoding |   Collate   |    Ctype    |    Access privileges 
-----------+----------+----------+-------------+-------------+------------------------- 
 testdb    | u2       | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
(4 rows)

After the command for deleting the u1 user is executed, the message "owner of database testdb" is not displayed.

       
          testdb=# DROP USER u1;
ERROR:  role "u1" cannot be dropped because some objects depend on it 
DETAIL:  3 objects in database gaussdb

Method 2: If the testdb database is no longer required, delete it. Change the owners of all database objects owned by u1 to u2.

       
          testdb=# REASSIGN OWNED BY u1 TO u2;
REASSIGN OWNED

Clear objects whose owner is u1. Exercise caution when running this command. Schemas with the same name will also be deleted.

      
         testdb=# DROP OWNED by u1;
DROP OWNED

If the user to be deleted has dependencies. You need to remove the dependencies before you delete it. The method is as follows:

Identify dependencies. According to the error information "3 objects in database gaussdb", three objects in the GaussDB database depend on u1. Due to the system catalog dependency in the database, detailed information about dependent objects is not printed in other databases, but is printed in the GaussDB database when DROP USER is executed in GaussDB database.

Run the following command to connect to the GaussDB database:

        
           gaussdb=# DROP USER u1;
ERROR:  role "u1" cannot be dropped because some objects depend on it
DETAIL:  privileges for table pg_class
privileges for schema u2

The obtained dependency details are as follows:

privileges for table pg_class: permissions of user u1 on pg_class.
Permission of user u1 on schema u2.

Revoke the permissions on dependent objects.

        
           gaussdb=# SELECT relname,relacl FROM pg_class WHERE relname = 'pg_class';
 relname  |              relacl
----------+----------------------------------
 pg_class | {=r/Ruby,u1=r/Ruby}
(1 row)

gaussdb=#SELECT nspname,nspacl FROM pg_namespace WHERE nspname = 'u2';
 nspname |           nspacl
---------+-----------------------------
 u2      | {u2=UC/u2,u2=LP/u2,u1=U/u2}

gaussdb=# REVOKE SELECT ON TABLE pg_class FROM u1;
REVOKE
gaussdb=# REVOKE USAGE ON SCHEMA u2 FROM u1;
REVOKE

Delete the user again. The user can be deleted successfully, and the message indicating that dependencies exist is not displayed.
1 2

gaussdb=# DROP USER u1; DROP USER

In some scenarios, the dependent objects of the user to be deleted are unknown, but the deletion still fails. The following uses a constructed case to demonstrate how to handle this situation. Create user u3 and assign the SELECT permission to user u2.

     
        testdb2=# DROP USER u3;
ERROR:  role "u3" cannot be dropped because some objects depend on it
DETAIL:  2 objects in database gaussdb

The pg_shdepend system catalog records the OIDs of dependent objects and their dependencies. Obtain the OID of the user, and then search the system catalogs for the corresponding dependency records.

       
          testdb2=# SELECT oid ,rolname FROM pg_roles WHERE rolname = 'u3';
    oid     | rolname
------------+---------
 2147484573 | u3
(1 row)

gaussdb=# SELECT * FROM pg_shdepend WHERE refobjid = 2147484573;
 dbid  | classid |   objid    | objsubid | refclassid |  refobjid  | deptype | objfile
-------+---------+------------+----------+------------+------------+---------+---------
 16073 |    2615 | 2147484575 |        0 |       1260 | 2147484573 | o       |
 16073 |    2615 | 2147484025 |        0 |       1260 | 2147484573 | a       |
(2 rows)

The values of dependType may be different. There are two records. One indicates permission dependency (a), and the other indicates that the object is the owner of another object.

classid indicates the ID of the record table that records the object that depends on the user. You can use the classid to find the dependency in pg_class.

       
          gaussdb=# SELECT relname,relacl FROM pg_class WHERE oid = 2615;
   relname    |     relacl
--------------+----------------
 pg_namespace | {=r/role23}
(1 row)

The query result shows that the record table is pg_namespace. It can be concluded that the object depends on the user is a schema. In pg_namespace, query the objid obtained in 1 to determine the specific object.

       
          gaussdb=# SELECT nspname,nspacl FROM pg_namespace WHERE oid in (2147484575,2147484025);
 nspname |                         nspacl
---------+---------------------------------------------------------
 u3      |
 u2      | {u2=UC/u2,u2=LP/u2,u3=U/u2}
(2 rows)

There are two schemas. u3 is the schema with the same name as the user, and u2 is the schema to which the permission is granted. Revoke the permission on the schema.

       
          gaussdb=# REVOKE USAGE ON SCHEMA u2 FROM u3;
REVOKE

Delete user u3. The deletion is successful.
1 2

gaussdb=# DROP USER u3; DROP USER

Parent topic: Account/Permission/Password

Previous topic: An Error Message Is Reported During Statement Execution, Indicating that the User Does Not Have the Required Permission

Next topic: Cluster Performance

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot