Required Privileges - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905
JSON_SHRED_BATCH resides in the SYSLIB database. The user executing the JSON_SHRED_BATCH procedure must have the following privileges:
  • EXECUTE PROCEDURE on SYSLIB
  • SELECT privilege on the source table
  • GRANT ALL (insert/update/delete/upsert) on the target table

The database where the procedure is running must have all privileges on SYSUDTLIB, SYSLIB, and the database where the target table exists and EXECUTE PROCEDURE on SYSLIB.

SYSLIB must have all privileges on the database which is executing the procedure.

For example, if the database where the procedure is running and where the target table exists is called JSONShred, the following statements assign the required privileges:

GRANT ALL ON SYSUDTLIB TO JSONShred;
GRANT ALL ON SYSLIB TO JSONShred;
GRANT EXECUTE PROCEDURE ON SYSLIB TO JSONShred;
GRANT ALL ON JSONShred TO JSONShred;
GRANT ALL ON JSONShred TO SYSLIB;
The following three privileges are required:
  • GRANT ALL ON SYSLIB TO JSONShred;
  • GRANT EXECUTE PROCEDURE ON SYSLIB TO JSONShred;
  • GRANT ALL ON JSONShred TO JSONShred;
If the logon user is jsonshred and the target table is targetDB, then the following privileges are required:
GRANT EXECUTE PROCEDURE ON SYSLIB TO jsonshred;
GRANT ALL ON targetDB TO jsonshred;
If the source table, sourceDB, is different from targetDB, then the following privilege is also required:
GRANT SELECT ON sourceDB TO jsonshred;