Preparing to run the Netezza collector
Pre-requisites for running the collector
Make sure that the machine from where you are running the collector meets the following hardware and software requirements.
Item | Requirement |
---|---|
Hardware (for on-premise runs only) | |
RAM | 8 GB |
CPU | 2 Ghz processor |
Software (for on-premise runs only) | |
Docker | Click here to get Docker. |
Driver | Obtained the Netezza JDBC driver from IBM. |
data.world specific objects (for both cloud and on-premise runs) | |
Dataset | You must have a ddw-catalogs (or other) dataset set up to hold your catalog files when you are done running the collector. If you are using Catalog Toolkit , follow these instructions to prepare the datasets for collectors. |
Setting up authentication for Netezza
The user you are using to run the collector needs at least LIST ON DATABASE permission to access the database. Users need additional GRANT LIST permissions to collect schemas, tables, views, materialized views, functions, stored procedures, columns, and column-level lineage from view and stored procedures. See the Netezza documentation for details about permissions.
To create a user and set the permissions:
Create a new user.
CREATE USER <USERNAME> WITH PASSWORD ‘<PASSWORD>’;
Grant the user list permission on <DATABASE_NAME>. This will give the user permission to connect to the database.
GRANT LIST ON <DATABASE_NAME> TO <USERNAME>;
To enable harvesting of catalog resources such as tables, views, materialized views, functions, stored procedures, and columns, grant list permission on additional objects. This also allows harvesting of column-level lineage from views, materialized views, and stored procedures.
GRANT LIST ON <DATABASE_NAME>.all.schema TO <USERNAME>; GRANT LIST ON <DATABASE_NAME>.all.table TO <USERNAME>; GRANT LIST ON <DATABASE_NAME>.all.view TO <USERNAME>; GRANT LIST ON <DATABASE_NAME>.all.procedure TO <USERNAME>; GRANT LIST ON <DATABASE_NAME>.all.function TO <USERNAME>;