Greenplum Database 4.3.12.0 includes these s3 protocol enhancements

• The external table s3 protocol can access an Amazon S3 compatible service that is supported by Greenplum Database as an external data store. Greenplum Database supports the Amazon S3 compatible service Dell EMC Elastic Cloud Storage (ECS).

  You configure the s3 protocol to access an S3 compatible service.

  • In the s3 configuration file, set the version parameter to 2. The parameter controls whether you can specify an S3 compatible service in the CREATE EXTERNAL TABLE command.
  • Specify the location and region of the S3 compatible service in the LOCATION clause of the CREATE EXTERNAL TABLE command. When you define the service in the LOCATION clause, you specify the service location in the URL and specify the service region in the region parameter.
  This is an example LOCATION clause that contains a region parameter and specifies an S3 compatible service.

  LOCATION ('s3://test.company.com/s3test.company.io/ds1/normal/ region=us-west
        config=/home/gpadmin/aws_s3/s3.conf')

  Note: If the s3 configuration file version parameter is 2, you can also specify an Amazon S3 location. This example specifies an Amazon S3 location.

  LOCATION ('s3://s3-us-west-2.amazonaws.com/s3test.pivotal.io/ds1/normal/ region=us-west-2
        config=/home/gpadmin/aws_s3/s3.conf')

• The s3 configuration file supports these new parameters that control connections to S3 data sources.

  • verifycert - Controls how authentication is performed when establishing encrypted communication between a client and an S3 data store over HTTPS.
    • verifycert=false enables the use of a self-signed SSL certificate.
    • verifycert=true requires an SSL certificate signed by a certificate authority (CA).
  • version - Enables support of the region parameter in LOCATION clause of CREATE EXTERNAL TABLE command. If the value is 1, the LOCATION clause supports the Amazon S3 URL and does not contain the region parameter. If the value is 2, the LOCATION clause supports S3 compatible services that are supported by Greenplum Database, the REGION parameter is required in the LOCATION clause. The region parameter specifies the S3 data source region.

For information about the CREATE EXTERNAL TABLE command, see the Greenplum Database Reference Guide. For information about the s3 protocol, see the Greenplum Database Administrator Guide.

For Greenplum Database 4.3.12.0, the Greenplum Database utility gpconfig includes the --file option.

If you specify the --file option with the -s option to display the value of a server configuration parameter, the utility shows the value from the postgresql.conf file on all instances (master and segments) in the Greenplum Database system. If there is a difference in a parameter value among the instances, the utility displays a message.

For example, the server configuration parameter statement_mem is set to 64MB for a user with the ALTER ROLE command, and the value in the postgresql.conf file is 128MB. Running the command gpconfig -s statement_mem --file displays 128MB. The command gpconfig -s statement_mem run by the user displays 64MB.

For Greenplum Database 4.3.12.0, the new server configuration parameter pljava_classpath_insecure controls the ability of normal database users to set the server configuration parameter pljava_classpath. Greenplum Database uses the list of jar files or directories containing jar files specified by pljava_classpath when running PL/Java functions. When pljava_classpath_insecure is enabled, Greenplum Database developers who are working on PL/Java functions do not have to be database superusers to change pljava_classpath. In previous releases, only database superusers could change pljava_classpath.

For information about the pljava_classpath_insecure parameter, see New Parameter. For information about the PL/Java procedural language, see the Greenplum Database Reference Guide.

Greenplum Database 4.3.12.0 includes new server configuration parameters.

• pljava_classpath_insecure

For information about Greenplum Database server configuration parameters, see the Greenplum Database Reference Guide.

The description of the pljava_classpath server configuration parameter includes information about the pljava_classpath_insecure server configuration parameter.

For information about Greenplum Database server configuration parameters, see the Greenplum Database Reference Guide.

The following notes describe platform support for Greenplum Database. Please send any questions or comments to Pivotal Support at https://support.pivotal.io.

• The only file system supported for running Greenplum Database is the XFS file system. All other file systems are explicitly not supported by Pivotal.
• Greenplum Database is supported on all 1U and 2U commodity servers with local storage. Special purpose hardware that is not commodity may be supported at the full discretion of Pivotal Product Management based on the general similarity of the hardware to commodity servers.
• Greenplum Database is supported on network or shared storage if the shared storage is presented as a block device to the servers running Greenplum Database and the XFS file system is mounted on the block device. Network file systems are not supported. When using network or shared storage, Greenplum Database mirroring must be used in the same way as with local storage, and no modifications may be made to the mirroring scheme or the recovery scheme of the segments. Other features of the shared storage such as de-duplication and/or replication are not directly supported by Pivotal Greenplum Database, but may be used with support of the storage vendor as long as they do not interfere with the expected operation of Greenplum Database at the discretion of Pivotal.
• Greenplum Database is supported when running on virtualized systems, as long as the storage is presented as block devices and the XFS file system is mounted for the storage of the segment directories.
• A minimum of 10-gigabit network is required for a system configuration to be supported by Pivotal.
• Greenplum Database is supported on Amazon Web Services (AWS) servers using either Amazon instance store (Amazon uses the volume names ephemeral[0-20]) or Amazon Elastic Block Store (Amazon EBS) storage. If using Amazon EBS storage the storage should be RAID of Amazon EBS volumes and mounted with the XFS file system for it to be a supported configuration.
• For Red Hat Enterprise Linux 7.2 or CentOS 7.2, the default systemd setting RemoveIPC=yes removes IPC connections when non-system users logout. This causes the Greenplum Database utility gpinitsystem to fail with semaphore errors. To avoid this issue, see "Setting the Greenplum Recommended OS Parameters" in the Greenplum Database Installation Guide.

An upgrade from 4.3.x to 4.3.12.0 involves stopping Greenplum Database, updating the Greenplum Database software binaries, upgrading and restarting Greenplum Database. If you are using Greenplum Extension packages, you must install and use Greenplum Database 4.3.5.0 or later extension packages. If you are using custom modules with the extensions, you must also use modules that were built for use with Greenplum Database 4.3.5.0 or later.

1. Log in to your Greenplum Database master host as the Greenplum administrative user:

   $ su - gpadmin

2. Uninstall the Greenplum Database gNet extension package if it is installed.

   The gNet extension package contains the software for the gphdfs protocol. For Greenplum Database 4.3.1 and later releases, the extension is bundled with Greenplum Database. The files for gphdfs are installed in $GPHOME/lib/hadoop.

3. Perform a smart shutdown of your current Greenplum Database 4.3.x system (there can be no active connections to the database). This example uses the -a option to disable confirmation prompts:

   $ gpstop -a

4. Run the installer for 4.3.12.0 on the Greenplum Database master host.
   When prompted, choose an installation location in the same base directory as your current installation. For example:

   /usr/local/greenplum-db-4.3.12.0

5. If your Greenplum Database deployment uses LDAP authentication, manually edit the /usr/local/greenplum-db/greenplum_path.sh file to add the line:

   export LDAPCONF=/etc/openldap/ldap.conf

6. Edit the environment of the Greenplum Database superuser (gpadmin) and make sure you are sourcing the greenplum_path.sh file for the new installation. For example change the following line in .bashrc or your chosen profile file:

   source /usr/local/greenplum-db-4.3.0.0/greenplum_path.sh

   to:

   source /usr/local/greenplum-db-4.3.12.0/greenplum_path.sh

   Or if you are sourcing a symbolic link (/usr/local/greenplum-db) in your profile files, update the link to point to the newly installed version. For example:

   $ rm /usr/local/greenplum-db
   $ ln -s /usr/local/greenplum-db-4.3.12.0 /usr/local/greenplum-db

7. Source the environment file you just edited. For example:

   $ source ~/.bashrc

8. Run the gpseginstall utility to install the 4.3.12.0 binaries on all the segment hosts specified in the hostfile. For example:

   $ gpseginstall -f hostfile

9. Rebuild any modules that were built against the provided C language header files for use with Greenplum Database 4.3.5.0 or later (for example, any shared library files for user-defined functions in $GPHOME/lib). See your operating system documentation and your system administrator for information about rebuilding and compiling modules such as shared libraries.
10. Use the Greenplum Database gppkg utility to install Greenplum Database extensions. If you were previously using any Greenplum Database extensions such as pgcrypto, PL/R, PL/Java, PL/Perl, and PostGIS, download the corresponding packages from Pivotal Network, and install using this utility. See the Greenplum Database 4.3 Utility Guide for gppkg usage details.
11. After all segment hosts have been upgraded, you can log in as the gpadmin user and restart your Greenplum Database system:

    # su - gpadmin
    $ gpstart

12. If you are upgrading a version of Greenplum Database between 4.3.0 and 4.3.2, check your Greenplum Database for inconsistencies due to an incorrect conversion of 4.2.x append-only tables to 4.3.x append-optimized tables.
    Important: The Greenplum Database system must be started but should not be running any SQL commands while the utility is running.
    1. Run the fix_ao_upgrade.py utility with the option --report. The following is an example.

       $ $GPHOME/share/postgresql/upgrade/fix_ao_upgrade.py --host=mdw --port=5432 --report

    2. If the utility displays a list of inconsistencies, fix them by running the fix_ao_upgrade.py utility without the --report option.

       $ $GPHOME/share/postgresql/upgrade/fix_ao_upgrade.py --host=mdw --port=5432

    3. (optional) Run the fix_ao_upgrade.py utility with the option --report again. No inconsistencies should be reported.
13. For databases that contain append-optimized tables that were created from Greenplum Database 4.2.x append-only tables, run the fix_visimap_owner.sql script. The script resolves an issue associated with relations associated with append-optimized tables. For example, this command runs the script on the database testdb.

    $ psql -d testdb1 -f $GPHOME/share/postgresql/upgrade/fix_visimap_owner.sql

    The script displays this prompt that allows you to display changes to the affected relations without performing the operation.

    Dry run, without making any modifications (y/n)?

    • Enter y to list ownership changes that would have been made. The owner of the relation is not changed.
    • Enter n make the ownership changes and display the changes to relation ownership.
    Note: Pivotal recommends that you run the script during low activity period. Heavy workloads do not affect database functionality but might affect performance.
14. If you are utilizing Data Domain Boost, you have to re-enter your DD Boost credentials after upgrading from Greenplum Database 4.3.x to 4.3.12.0 as follows:

    gpcrondump --ddboost-host ddboost_hostname --ddboost-user ddboost_user
      --ddboost-backupdir backup_directory

$GPHOME/share/postgresql/upgrade/fix_visimap_owner.sql

Dry run, without making any modifications (y/n)?

fix_ao_upgrade.py {-h master_host | --host=master_host}
     {-p master_port | --port=master_port}
     [-u user | --user=user ]
     [--report] [-v | --verbose] [--help]

$GPHOME/share/postgresql/upgrade/fix_orphan_segment_tables.py

$GPHOME/share/postgresql/upgrade/fix_orphan_segment_tables.py -p port

$GPHOME/share/postgresql/upgrade/fix_orphan_segment_tables.py -p port -f orphan_tables_file_timestamp 

Upgrading Greenplum Database from 4.3.x to 4.3.12.0 on a Pivotal DCA system involves stopping Greenplum Database, updating the Greenplum Database software binaries, and restarting Greenplum Database. If you are using Greenplum Extension packages, you must install and use Greenplum Database 4.3.5.0 or later extension packages. If you are using custom modules with the extensions, you must also use modules that were built for use with Greenplum Database 4.3.5.0 or later.

1. Log in to your Greenplum Database master host as the Greenplum administrative user (gpadmin):

   # su - gpadmin

2. Download or copy the installer file to the Greenplum Database master host.
3. Uninstall the Greenplum Database gNet extension package if it is installed. For information about uninstalling a Greenplum Database extension package, see gppkg in the Greenplum Database Utility Guide.

   The gNet extension package contains the software for the gphdfs protocol. For Greenplum Database 4.3.1 and later releases, the extension is bundled with Greenplum Database. The files for gphdfs are installed in $GPHOME/lib/hadoop.

4. Perform a smart shutdown of your current Greenplum Database 4.3.x system (there can be no active connections to the database). This example uses the -a option to disable confirmation prompts:

   $ gpstop -a

5. As root, run the Pivotal DCA installer for 4.3.12.0 on the Greenplum Database master host and specify the file hostfile that lists all hosts in the cluster. If necessary, copy hostfile to the directory containing the installer before running the installer.

   This example command runs the installer for Greenplum Database 4.3.12.0 for Redhat Enterprise Linux 5.x.

   # ./greenplum-db-appliance-4.3.12.0-build-1-RHEL5-x86_64.bin hostfile

   The file hostfile is a text file that lists all hosts in the cluster, one host name per line.

6. Install Greenplum Database extension packages. For information about installing a Greenplum Database extension package, see gppkg in the Greenplum Database Utility Guide.
   Important: Rebuild any modules that were built against the provided C language header files for use with Greenplum Database 4.3.5.0 or later (for example, any shared library files for user-defined functions in $GPHOME/lib). See your operating system documentation and your system administrator for information about rebuilding and compiling modules such as shared libraries.
7. After all segment hosts have been upgraded, you can log in as the gpadmin user and restart your Greenplum Database system:

   # su - gpadmin
   $ gpstart

8. If you are upgrading a version of Greenplum Database between 4.3.0 and 4.3.2, check your Greenplum Database for inconsistencies due to an incorrect conversion of 4.2.x append-only tables to 4.3.x append-optimized tables.
   Important: The Greenplum Database system must be started but should not be running any SQL commands while the utility is running.
   1. Run the fix_ao_upgrade.py utility with the option --report. The following is an example.

      $ $GPHOME/share/postgresql/upgrade/fix_ao_upgrade.py --host=mdw --port=5432 --report

   2. If the utility displays a list of inconsistencies, fix them by running the fix_ao_upgrade.py utility without the --report option.

      $ $GPHOME/share/postgresql/upgrade/fix_ao_upgrade.py --host=mdw --port=5432

   3. (optional) Run the fix_ao_upgrade.py utility with the option --report again. No inconsistencies should be reported.
9. If you are utilizing Data Domain Boost, you have to re-enter your DD Boost credentials after upgrading from Greenplum Database 4.3.x to 4.3.12.0 as follows:

   gpcrondump --ddboost-host ddboost_hostname --ddboost-user ddboost_user
     --ddboost-backupdir backup_directory

This section describes how you can upgrade from Greenplum Database 4.2.x.x or later to Greenplum Database 4.3.12.0. For users running versions prior to 4.2.x.x of Greenplum Database, see the following:

• For Users Running Greenplum Database 4.1.x.x
• For Users Running Greenplum Database 4.0.x.x
• For Users Running Greenplum Database 3.3.x.x

Users on a release prior to 4.1.x.x cannot upgrade directly to 4.3.12.0.

1. Upgrade from your current release to 4.2.x.x (follow the upgrade instructions in the latest Greenplum Database 4.2.x.x release notes available at Pivotal Documentation).
2. Follow the upgrade instructions in these release notes for Upgrading from 4.2.x.x to 4.3.12.0.

Users on a release prior to 4.1.x.x cannot upgrade directly to 4.3.12.0.

1. Upgrade from your current release to 4.1.x.x (follow the upgrade instructions in the latest Greenplum Database 4.1.x.x release notes available on Dell EMC Support Zone).
2. Upgrade from the current release to 4.2.x.x (follow the upgrade instructions in the latest Greenplum Database 4.2.x.x release notes available at Pivotal Documentation).
3. Follow the upgrade instructions in these release notes for Upgrading from 4.2.x.x to 4.3.12.0.

Users on a release prior to 4.0.x.x cannot upgrade directly to 4.3.12.0.

1. Upgrade from your current release to the latest 4.0.x.x release (follow the upgrade instructions in the latest Greenplum Database 4.0.x.x release notes available on Dell EMC Support Zone).
2. Upgrade the 4.0.x.x release to the latest 4.1.x.x release (follow the upgrade instructions in the latest Greenplum Database 4.1.x.x release notes available on Dell EMC Support Zone).
3. Upgrade from the 4.1.1 release to the latest 4.2.x.x release (follow the upgrade instructions in the latest Greenplum Database 4.2.x.x release notes available at Pivotal Documentation).
4. Follow the upgrade instructions in these release notes for Upgrading from 4.2.x.x to 4.3.12.0.

If you experience issues during the migration process and have active entitlements for Greenplum Database that were purchased through Pivotal, contact Pivotal Support. Information for contacting Pivotal Support is at https://support.pivotal.io.

Be prepared to provide the following information:

• A completed Upgrade Procedure.
• Log output from gpmigrator_mirror and gpcheckcat (located in ~/gpAdminLogs)

Greenplum releases a number of client tool packages on various platforms that can be used to connect to Greenplum Database and the Greenplum Command Center management tool. The following table describes the compatibility of these packages with this Greenplum Database release.

Tool packages are available from Pivotal Network.

The Greenplum Database Client Tools, Load Tools, and Connectivity Tools are supported on the following platforms:

• AIX 5.3L (32-bit)
• AIX 5.3L and AIX 6.1 (64-bit)
• Apple OS X on Intel processors (32-bit)
• HP-UX 11i v3 (B.11.31) Intel Itanium (Client and Load Tools only)
• Red Hat Enterprise Linux i386 (RHEL 5)
• Red Hat Enterprise Linux x86_64 6.x (RHEL 6)
• Red Hat Enterprise Linux x86_64 (RHEL 5)
• SuSE Linux Enterprise Server x86_64 SLES 11
• Solaris 10 SPARC32
• Solaris 10 SPARC64
• Solaris 10 i386
• Solaris 10 x86_64
• Windows 7 (32-bit and 64-bit)
• Windows Server 2003 R2 (32-bit and 64-bit)
• Windows Server 2008 R2 (64-bit)
• Windows XP (32-bit and 64-bit)

For Greenplum Database 4.3, this is the package file naming format.

pkgname-ver_pvpkg-version_gpdbrel-OS-version-arch.gppkg

This example is the package name for a postGIS package.

postgis-ossv2.0.3_pv2.0.1_gpdb4.3-rhel5-x86_64.gppkg

pkgname-ver - The package name and optional version of the software that was used to create the package extension. If the package is based on open source software, the version has format ossvversion. The version is the version of the open source software that the package is based on. For the postGIS package, ossv2.0.3 specifies that the package is based on postGIS version 2.0.3.

pvpkg-version - The package version. The version of the Greenplum Database package. For the postGIS package, pv2.0.1 specifies that the Greenplum Database package version is 2.0.1.

gpdbrel-OS-version-arch - The compatible Greenplum Database release. For the postGIS package, gpdb4.3-rhel5-x86_64 specifies that package is compatible with Greenplum Database 4.3 on Red Hat Enterprise Linux version 5.x, x86 64-bit architecture.