REPARENTED_ON_DROP

Lists re-parenting events of objects that were dropped from their original owner but still remain in Vertica.

Lists re-parenting events of objects that were dropped from their original owner but still remain in Vertica. For example, a user may leave the organization and need to be removed from the database. When the database administrator drops the user from the database, that user's objects are re-parented to another user.

In some cases, a Vertica user's objects are reassigned based on the GlobalHeirUsername parameter. In this case, a user's objects are re-parented to the user indicated by this parameter.

Column Name	Data Type	Description
`REPARENT_TIMESTAMP`	TIMESTAMP	The time the re-parenting event occurred.
`NODE_NAME`	VARCHAR	The name of the node or nodes on which the re-parenting occurred.
`SESSION_ID`	VARCHAR	The identification number of the re-parenting event.
`USER_ID`	INTEGER	The unique, system-generated user identification number.
`USER_NAME`	VARCHAR	The name of the user that caused the re-parenting event. For example, a dbadmin user may have dropped a user thus re-parenting that user's objects.
`TRANSACTION_ID`	INTEGER	The system-generated transaction identification number. Is NULL if a transaction id does not exist.
`OLD_OWNER_NAME`	VARCHAR	The the name of the dropped user who used to own the re-parented object.
`OLD_OWNER_OID`	INTEGER	The unique identification number of the user who used to own the re-parented object.
`NEW_OWNER_NAME`	VARCHAR	The name of the user who now owns the re-parented objects.
`NEW_OWNER_OID`	INTEGER	The unique identification number of the user who now owns the re-parented objects.
`OBJ_NAME`	VARCHAR	The name of the object being re-parented.
`OBJ_OID`	INTEGER	The unique identification number of the object being re-parented.
`SCHEMA_NAME`	VARCHAR	The name of the schema in which the object resides.
`SCHEMA_OID`	INTEGER	The unique identification number of the schema in which the re-parented object resides.