This checklist can be applied to GPDB versions: 5.x, 6.x.
1. No operations (Truncate, Analyze , Vacuum etc.) are performed after this issue arises, as these operations alter the state of relation and may loose the artifacts needed.
2. Collect SQL artifacts using the "with header" clause for a better reading experience.
For example, copy select oid, relname, reltype from pg_class limit 2 to '/tmp/pg_class.out' with header;.
select * from gp_transaction_log ; select * from gp_distributed_log ;
select xmin, xmax,cmin,cmax,ctid,* from pg_aoseg.pg_aoseg_<oid>; select xmin, xmax,cmin,cmax,ctid,* from pg_aoseg.pg_aocsseg_<oid>; Select xmin,xmax,cmin,cmax,ctid,* from pg_appendonly; select * from gp_toolkit.__gp_aocsseg(<oid>); [From master and affected segment for AOCO table] select xmin,xmax,cmin,cmax,ctid,* from gp_relation_node ; select ctid, * from gp_persistent_relation_node ; [visible only] select xmin,xmax,cmin,cmax,ctid,oid,* from pg_class ; select xmin,xmax,cmin,cmax,ctid,* from pg_stat_last_operation;[Master only]
ls -l base/<database_directory>
ls -l base/<database_directory>/<relfilenode>*
Note: Make sure a copy of the file or relation exists on your system in case it can not be provided to Tanzu Support before this issue surfaces. This is required to gather information needed to perform a RCA for this issue.