statistics to the statistics collector, but the collector was not running because the mirror was not in hot standby mode. 31082 - Server: Execution : Resolved an issue where the planner generated an incorrect resolves these issues: n/a : The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect 194 30844 - gpreload : gpreload returned the error more than one row returned when attempting to reload a table and a view with the same name exists in a different schema in the database. This issue is

statistics to the statistics collector, but the collector was not running because the mirror was not in hot standby mode. 31082 - Server: Execution : Resolved an issue where the planner generated an incorrect resolves these issues: n/a : The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect 186 30844 - gpreload : gpreload returned the error more than one row returned when attempting to reload a table and a view with the same name exists in a different schema in the database. This issue is

statistics to the statistics collector, but the collector was not running because the mirror was not in hot standby mode. 31082 - Server: Execution : Resolved an issue where the planner generated an incorrect resolves these issues: n/a : The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect 191 30844 - gpreload : gpreload returned the error more than one row returned when attempting to reload a table and a view with the same name exists in a different schema in the database. This issue is

according to your specific situation and setup. Set the parameters in the /etc/sysctl.conf file and reload with sysctl -p: # kernel.shmall = _PHYS_PAGES / 2 # See Shared Memory Pages kernel.shmall = 197951838 to 24 disks. Use RAID 1, 5, or 6 so that the disk array can tolerate a failed disk. Configure a hot spare in the disk array to allow rebuild to begin automatically when disk failure is detected. Protect segment. For tables with a large number of columns consider columnar storage for data often accessed (hot) and row-oriented storage for data not often accessed (cold). 4. Storage options should be set at

statistics to the statistics collector, but the collector was not running because the mirror was not in hot standby mode. 31082 - Server: Execution Resolved an issue where the planner generated an incorrect resolves these issues: n/a The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect resolved. 30844 - gpreload gpreload returned the error more than one row returned when attempting to reload a table and a view with the same name exists in a different schema in the database. This issue is

Server. VMware Greenplum 6 Documentation VMware, Inc. 214 running because the mirror was not in hot standby mode. 31082 - Server: Execution Resolved an issue where the planner generated an incorrect resolves these issues: n/a The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect resolved. 30844 - gpreload gpreload returned the error more than one row returned when attempting to reload a table and a view with the same name exists in a different schema in the database. This issue is

statistics to the statistics collector, but the collector was not running because the mirror was not in hot standby mode. 31082 - Server: Execution Resolved an issue where the planner generated an incorrect resolves these issues: n/a The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect resolved. 30844 - gpreload gpreload returned the error more than one row returned when attempting to reload a table and a view with the same name exists in a different schema in the database. This issue is

according to your specific situation and setup. Set the parameters in the /etc/sysctl.conf file and reload with sysctl -p: # kernel.shmall = _PHYS_PAGES / 2 # See Shared Memory Pages kernel.shmall = 197951838 main server process receives a SIGHUP signal. If you edit the file on an active system, you must reload the file using this command: $ gpstop -u CAUTION: For a more secure system, remove records for It verifies entries before you save them, keeps a version history of the file so that you can reload a previous version of the file, and reloads the file into Greenplum Database. VMware Greenplum

statistics to the statistics collector, but the collector was not running because the mirror was not in hot standby mode. 31082 - Server: Execution Resolved an issue where the planner generated an incorrect resolves these issues: n/a The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect resolved. 30844 - gpreload gpreload returned the error more than one row returned when attempting to reload a table and a view with the same name exists in a different schema in the database. This issue is

VMware Tanzu Greenplum 6 Documentation VMware, Inc. 185 running because the mirror was not in hot standby mode. 31082 - Server: Execution Resolved an issue where the planner generated an incorrect resolves these issues: n/a The DataDirect ODBC Drivers were updated to version 7.16.359 to incorporate hot fix changes and certify compatibility with SUSE Linux Enterprise Server 15 clients. See the DataDirect resolved. 30844 - gpreload gpreload returned the error more than one row returned when attempting to reload a table and a view with the same name exists in a different schema in the database. This issue is