full-path-to-pkglibdir/SAS
directory that contains the SAS
Formats Library and the SAS Embedded Process.
full-path-to-pkglibdir
directory.pg_config --pkglibdir
If
you did not perform the Greenplum install, you cannot run the pg_config
--pkglibdir
command. The pg_config --pkglibdir
command
must be run by the person who performed the Greenplum installation.
/SAS/SASTKInDatabaseServerForGreenplum
directory
and all its contents from each database host node.
path_to_sh_file
directory
where you copied the tkindbsrv-9.4_M2-n_lax.sh
self-extracting archive file.
\timing
off
in your .psqlrc file before running this script.
full-path-to-pkglibdir/SAS/
.
full-path-to-pkglibdir
directory.pg_config --pkglibdir
If
you did not perform the Greenplum install, you cannot run the pg_config
--pkglibdir
command. The pg_config --pkglibdir
command
must be run by the person who performed the Greenplum install.
SAS-installation-directory/SASFormatsLibraryforGreenplum/3.1/GreenplumonLinux64/
directory.
./accelgplmfmt-3.1-n_lax.sh
/path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/bin/ InstallAccelGplmFmt.sh /path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/bin/ CopySASFiles.sh /path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/lib/ SAS_CompileUDF.so /path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/lib/ libjazxfbrs.so
./path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/bin/ CopySASFiles.sh
\timing
off
in your .psqlrc file before running this script.
full-path-to-pkglibdir/SAS
. The files are copied to the master
node and each of the segment nodes.
full-path-to-pkglibdir
directory:pg_config --pkglibdirIf you did not perform the Greenplum install, you cannot run the
pg_config
--pkglibdir
command. The pg_config --pkglibdir
command
must be run by the person who performed the Greenplum install.
full-path-to-pkglibdir/SAS
directory
to the new nodes using a method of your choice such as scp
/SAS
. The binary files include SAS_CompileUDF.so, libjazxfbrs.so,
and the binary files for the already published functions.
SAS-installation-directory/SASTKInDatabaseServer/9.4/GreenplumonLinux64
directory.
./tkindbsrv-9.4_M2-n_lax.sh
/path_to_sh_file/InstallSASEPFiles.sh /path_to_sh_file/UninstallSASEPFiles.sh /path_to_sh_file/StartupSASEP.sh /path_to_sh_file/ShutdownSASEP.sh /path_to_sh_file/ShowSASEPStatus.sh /path_to_sh_file/SAS/SASTKInDatabaseServerForGreenplum/9.4_M2/admin /path_to_sh_file/SAS/SASTKInDatabaseServerForGreenplum/9.4_M2/bin /path_to_sh_file/SAS/SASTKInDatabaseServerForGreenplum/9.4_M2/logs /path_to_sh_file/SAS/SASTKInDatabaseServerForGreenplum/9.4_M2/misc /path_to_sh_file/SAS/SASTKInDatabaseServerForGreenplum/9.4_M2/sasexe /path_to_sh_file/SAS/SASTKInDatabaseServerForGreenplum/9.4_M2/utilities
/path_to_sh_file/
directory,
all of the .sh files are also placed in the /path_to_sh_file/SAS/SASTKInDatabaseServerForGreenplum/9.4_M2/admin
directory.
\timing
off
in your .psqlrc file before running this script.
cd /path_to_sh_file/
./InstallSASEPFiles.sh <-quiet>
full-path-to-pkglibdir/SAS
directory.
This directory is created on the master node and each host node.
full-path-to-pkglibdir/SAS/SASTKInDatabaseServerForGreenplum
directory
should look similar to these.full-path-to-pkglibdir/SAS/SASTKInDatabaseServerForGreenplum/ 9.4_M2/admin full-path-to-pkglibdir/SAS/SASTKInDatabaseServerForGreenplum/ 9.4_M2/bin full-path-to-pkglibdir/SAS/SASTKInDatabaseServerForGreenplum/ 9.4_M2/logs full-path-to-pkglibdir/SAS/SASTKInDatabaseServerForGreenplum/ 9.4_M2/misc full-path-to-pkglibdir/SAS/SASTKInDatabaseServerForGreenplum/ 9.4_M2/sasexe full-path-to-pkglibdir/SAS/SASTKInDatabaseServerForGreenplum/ 9.4_M2/utilities
full-path-to-pkglibdir
directory:pg_config --pkglibdirIf you did not perform the Greenplum install, you cannot run the
pg_config
--pkglibdir
command. The pg_config --pkglibdir
command
must be run by the person who performed the Greenplum install.
usr/local/greenplum-db-4.2.3.0/lib/postgresql/SAS
full-path-to-pkglibdir/SAS
directory.
All the SAS object files are stored under full-path-to-pkglibdir/SAS
.
full-path-to-pkglibdir
directory:pg_config --pkglibdirIf you did not perform the Greenplum install, you cannot run the
pg_config
--pkglibdir
command. The pg_config --pkglibdir
command
must be run by the person who performed the Greenplum install.
full-path-to-pkglibdir/SAS
path
on the whole database array including the master and all segments.
%let indconn = user=youruserid password=yourpwd dsn=yourdsn; /* You can use server=yourserver database=yourdb instead of dsn=yourdsn */
specifies the Greenplum user name (also called the user ID) that is used to connect to the database. If the user name contains spaces or nonalphanumeric characters, enclose the user name in quotation marks.
specifies the password that is associated with your Greenplum user ID. If the password contains spaces or nonalphabetic characters, enclose the password in quotation marks.
Tip | Use only PASSWORD=, PASS=, or PW= for the password argument. PWD= is not supported and causes an error. |
specifies the configured Greenplum ODBC data source to which you want to connect. If the DSN name contains spaces or nonalphabetic characters, enclose the DSN name in quotation marks.
Requirement | You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable. |
specifies the Greenplum server name or the IP address of the server host. If the server name contains spaces or nonalphanumeric characters, enclose the server name in quotation marks.
Requirement | You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable. |
specifies the Greenplum database that contains the tables and views that you want to access. If the database name contains spaces or nonalphanumeric characters, enclose the database name in quotation marks.
Requirement | You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable. |
specifies the psql port number.
Default | 5432 |
Requirement | The server-side installer uses psql, and psql default port is 5432. If you want to use another port, you must have the UNIX or database administrator change the psql port. |
specifies the parent directory where all the object files are stored.
Tip | The full-path-to-pkglibdir directory was created during installation
of the self-extracting archive file. You can use the following command
to determine the full-path-to-pkglibdir directory:pg_config --pkglibdirIf you did not perform the Greenplum install, you cannot run the pg_config
--pkglibdir command. The pg_config --pkglibdir command
must be run by the person who performed the Greenplum install.
|
specifies the name of a Greenplum database to which the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions are published.
Restriction | If you specify DSN= in the INDCONN macro variable, do not use the DATABASE argument. |
specifies that the macro performs one of the following actions:
creates a new SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF function.
overwrites the current SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions, if a function by the same name is already registered, or creates a new SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF function if one is not registered.
Requirement | If you are upgrading from or reinstalling the SAS Formats Library, run the %INDGP_PUBLISH_COMPILEUDF macro with ACTION=REPLACE. The CopySASFiles.sh install script replaces existing versions of most files. However, you need to replace the existing SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions after you run the CopySASFiles.sh install script. For more information, see Upgrading from or Reinstalling a Previous Version and Moving and Installing the SAS Formats Library and Binary Files. |
causes the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions to be dropped from the Greenplum database.
Default | CREATE |
Tip | If the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions were published previously and you specify ACTION=CREATE, you receive warning messages that the functions already exist and you are prompted to use REPLACE. If the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions were published previously and you specify ACTION=REPLACE, no warnings are issued. |
specifies a directory that contains diagnostic files.
Tip | Files that are produced include an event log that contains detailed information about the success or failure of the publishing process. |
%let indconn = user=youruserid password=yourpwd dsn=yourdsn <schema=yourschema>; /* You can use server=yourserver database=yourdb instead of dsn=yourdsn */
specifies the Greenplum user name (also called the user ID) that is used to connect to the database. If the user name contains spaces or nonalphanumeric characters, enclose the user name in quotation marks.
specifies the password that is associated with your Greenplum user ID. If the password contains spaces or nonalphabetic characters, enclose the password in quotation marks.
Tip | Use only PASSWORD=, PASS=, or PW= for the password argument. PWD= is not supported and causes an error. |
specifies the configured Greenplum ODBC data source to which you want to connect. If the DSN name contains spaces or nonalphabetic characters, enclose the DSN name in quotation marks.
Requirement | You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable. |
specifies the Greenplum server name or the IP address of the server host. If the server name contains spaces or nonalphanumeric characters, enclose the server name in quotation marks.
Requirement | You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable. |
specifies the Greenplum database that contains the tables and views that you want to access. If the database name contains spaces or nonalphanumeric characters, enclose the database name in quotation marks.
Requirement | You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable. |
specifies the name of the schema where the SAS_EP function is defined.
Default | SASLIB |
Requirements | You must create the schema in the database before you run the %INDGP_PUBLISH_COMPILEUDF_EP macro. |
You must publish the SAS_EP function to a schema that is in your schema search path. |
specifies the psql port number.
Default | 5432 |
Requirement | The server-side installer uses psql, and psql default port is 5432. If you want to use another port, you must have the UNIX or database administrator change the psql port. |
specifies the parent directory where all the object files are stored.
Tip | The full-path-to-pkglibdir directory was created during installation
of the InstallSASEP.sh self-extracting archive file. You can use the
following command to determine the full-path-to-pkglibdir directory:pg_config --pkglibdirIf you did not perform the Greenplum install, you cannot run the pg_config
--pkglibdir command. The pg_config --pkglibdir command
must be run by the person who performed the Greenplum install.
|
specifies the name of a Greenplum database where the SAS_EP function is defined.
Restriction | If you specify DSN= in the INDCONN macro variable, do not use the DATABASE argument. |
specifies that the macro performs one of the following actions:
creates a new SAS_EP function.
overwrites the current SAS_EP function, if a function by the same name is already registered, or creates a new SAS_EP function if one is not registered.
Requirement | If you are upgrading from or reinstalling the SAS Embedded Process, run the %INDGP_PUBLISH_COMPILEUDF_EP macro with ACTION=REPLACE. The InstallSASEPFiles.sh install script replaces existing versions of most files. However, you need to replace the existing SAS_EP function after you run the InstallSASEPFiles.sh install script. For more information, see Upgrading from or Reinstalling a Previous Version and Moving and Installing the SAS Embedded Process. |
causes the SAS_EP function to be dropped from the Greenplum database.
Default | CREATE |
Tip | If the SAS_EP function was defined previously and you specify ACTION=CREATE, you receive warning messages that the functions already exist and you are prompted to use REPLACE. If the SAS_EP function was defined previously and you specify ACTION=REPLACE, no warnings are issued. |
specifies a directory that contains diagnostic files.
Tip | Files that are produced include an event log that contains detailed information about the success or failure of the publishing process. |