ADM_AUDIT_STATEMENT
ADM_AUDIT_STATEMENT displays all grant and revoke audit trace entries. The audit information of GaussDB is mainly obtained through the pg_query_audit function. This view exists in both PG_CATALOG and SYS schema. Only users with the AUDITADMIN attribute can view audit information. The action_name column of GaussDB is different from that of the ORA database in terms of the audit actions. The type of the transactionid column is the same as that in the ORA database. In GaussDB, the sql_text column is the parsed SQL statement, which is not completely the same as the executed SQL statement.
Name |
Type |
Description |
---|---|---|
os_username |
character varying(255) |
Not supported. Its value is NULL. |
username |
character varying(128) |
Name of the user whose operation is audited, not the user ID. |
userhost |
character varying(128) |
Not supported. Its value is NULL. |
terminal |
character varying(255) |
Not supported. Its value is NULL. |
timestamp |
timestamp(0) without time zone |
Date and time when an audit trace entry is created in the local database session time zone (user login date and time of the entry created by the audit session). |
owner |
character varying(128) |
Creator of the object affected by the operation. |
obj_name |
character varying(128) |
Name of the object affected by the operation. |
action |
numeric |
Not supported. Its value is NULL. |
action_name |
character varying(28) |
Action type corresponding to the code in the action column. |
new_owner |
character varying(128) |
Not supported. Its value is NULL. |
new_name |
character varying(128) |
Not supported. Its value is NULL. |
obj_privilege |
character varying(32) |
Not supported. Its value is NULL. |
sys_privilege |
character varying(40) |
Not supported. Its value is NULL. |
admin_option |
character varying(1) |
Not supported. Its value is NULL. |
grantee |
character varying(128) |
Not supported. Its value is NULL. |
audit_option |
character varying(40) |
Not supported. Its value is NULL. |
ses_actions |
character varying(19) |
Not supported. Its value is NULL. |
logoff_time |
timestamp(0) without time zone |
Not supported. Its value is NULL. |
logoff_lread |
numeric |
Not supported. Its value is NULL. |
logoff_pread |
numeric |
Not supported. Its value is NULL. |
logoff_lwrite |
numeric |
Not supported. Its value is NULL. |
logoff_dlock |
character varying(40) |
Not supported. Its value is NULL. |
comment_text |
character varying(4000) |
Not supported. Its value is NULL. |
sessionid |
numeric |
Not supported. Its value is NULL. |
entryid |
numeric |
Not supported. Its value is NULL. |
statementid |
numeric |
Not supported. Its value is NULL. |
returncode |
numeric |
Not supported. Its value is NULL. |
priv_used |
character varying(40) |
Not supported. Its value is NULL. |
client_id |
character varying(128) |
Not supported. Its value is NULL. |
econtext_id |
character varying(64) |
Not supported. Its value is NULL. |
session_cpu |
numeric |
Not supported. Its value is NULL. |
extended_timestamp |
timestamp(6) with time zone |
Time zone of the timestamp when an audit trace entry is created (user login date and time of the entry created by the audit session in UTC). |
proxy_sessionid |
numeric |
Not supported. Its value is NULL. |
global_uid |
character varying(32) |
Not supported. Its value is NULL. |
instance_number |
numeric |
Not supported. Its value is NULL. |
os_process |
character varying(16) |
Not supported. Its value is NULL. |
transactionid |
text |
Identifier of the transaction that accesses or modifies an object. |
scn |
numeric |
Not supported. Its value is NULL. |
sql_bind |
nvarchar2(2000) |
Not supported. Its value is NULL. |
sql_text |
nvarchar2 |
SQL text of the query. |
obj_edition_name |
character varying(128) |
Not supported. Its value is NULL. |
dbid |
numeric |
Not supported. Its value is NULL. |
rls_info |
clob |
Not supported. Its value is NULL. |
current_user |
character varying(128) |
Not supported. Its value is NULL. |
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