Use DBMS_METADATA to extract the complete DDL (metadata) of an Oracle user, including system, object and role grants. This is handy when cloning a user or migrating it to another database. 1. User DDL set long 999999 select dbms_metadata.get_ddl('USER','<username>') from dual; 2. System privilege grants select dbms_metadata.get_granted_ddl('SYSTEM_GRANT','<username>') from dual; 3. Object grants select dbms_metadata.get_granted_ddl('OBJECT_GRANT','<username>') from dual; 4. Role grants select dbms_metadata.get_granted_ddl('ROLE_GRANT','<username>') from dual; Tip: run set long 999999 and set pagesize 0 first so the output isn't truncated. If a grant type has no rows, you'll get ORA-31608; that just means the user has none of that type.
This procedure covers OS, Grid and RDBMS home patching for Oracle Cloud Infrastructure (OCI) DB systems using the dbcli utility. Run every step as root . Advantages of dbcli patching Simple command line, with no manual patch download or copy to the nodes. Patches are downloaded automatically if the service gateway can reach Oracle Object Storage and the YUM repos. Applied in a rolling fashion, so no downtime is needed. Disadvantages You can't choose the patch version; the latest available in OCI is applied. Rollback isn't possible from the console, and dbcli support is limited (see the note at the end). Steps 1. Backup Make sure a recent full backup exists before patching. 2. Blackout Create a blackout for both nodes (console or emctl ) to avoid unnecessary alerts. 3. Check patch availability # dbcli describe-component 4. Pre-checks Grid home: # dbcli update-server -p # dbcli describe-job -i <jobId> RDBMS home: # dbcli list-dbhomes...