Creating a Manifest File | Native Object Store ( NOS ) | Teradata Vantage - 17.10 - Creating a Manifest File Without Writing Separate Objects to the Object Storage - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Native Object Store Getting Started Guide

Advanced SQL Engine
Teradata Database
Release Number
Release Date
July 2021
Content Type
Programming Reference
Publication ID
English (United States)

The following examples show how to use WRITE_NOS to create a manifest file.

When Write_NOS is done creating objects on external object storage it can create a manifest file with the names of the objects created. If there is a crash, abort, or error while writing objects, the manifest file is not created.

  • The first example shows how to create the manifest file if a WRITE_NOS operation aborts before all the objects have been written out.
  • The second example shows how to overwrite a manifest file.
  • The third example shows how to create a manifest file using READ_NOS with RETURNTYPE('NOSREAD_KEYS') as input to writing the manifest file.
In these examples only the manifest file is written, not the actual objects the manifest file identifies.


  1. If not already done, set up or obtain access to the external object storage where you want to write data. Follow the instructions from your external storage vendor.
  2. If not already done, set up an authorization to access external object storage that has the credential to the bucket. See Controlling Foreign Table Access with an AUTHORIZATION Object.
  3. Create A Manifest Table in the Database

  4. Create a database table to store the manifest file entries:
    CREATE TABLE ManifestTbl 
      ObjectSize BIGINT