Installing an Aster Analytics Function Package - Aster Analytics

Teradata AsterĀ® Analytics Foundation User GuideUpdate 2

Product
Aster Analytics
Release Number
7.00.02
Published
September 2017
Language
English (United States)
Last Update
2018-04-17
dita:mapPath
uce1497542673292.ditamap
dita:ditavalPath
AA-notempfilter_pdf_output.ditaval
dita:id
B700-1022
lifecycle
previous
Product Category
Software
This procedure installs a package for the first time. If you are updating installed functions to a newer version, follow the instructions in Updating an Aster Analytics Function Package.
  • Aster Database does not share functions (or any other database objects) across databases.
  • When you expand a cluster by adding worker nodes, all installed Aster Analytics functions on your cluster are automatically added to the new nodes.
  1. Download an Aster Function package.
  2. Get the install and uninstall scripts. Each Aster Analytics function package has SQL scripts that install and uninstall the package, for the PUBLIC schema and a specified schema. Teradata recommends installing the Aster Analytics functions only in the PUBLIC schema, but you can install them on other schemas.
    Driver functions look for the functions that they call internally in the PUBLIC schema. Therefore, driver functions might work incorrectly if you install all the functions to a schema other than PUBLIC.
  3. Verify that you have the necessary access privileges for installing the Aster Analytics functions in the desired schema.
  4. Go to the directory where the functions from the package are. For example: cd /opt/teradata/AsterAnalytics_Foundation/AA_7.00
  5. Run the SQL script that installs the package. For example: install_aster_analytics.sql

    or:

    install_ASTER_ANALYTICS_to_SCHEMANAME.sql
  6. Check the version numbers of the newly installed functions, using the instructions in Finding Function Version Numbers.
  7. For each user of the installed or updated functions, verify that the schema in which the functions are installed (typically PUBLIC) is the default schema in the search path.
  8. Set permissions to allow users to run functions.
  9. Test the functions.