DWH Load Fails - Errors: "Get Record Counts - Unexpected error" / "FATAL: terminating connection..."

book

Article ID: 212334

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

DWH Incremental Load failure with the following errors seen in the Data Warehouse (DWH) Load Log in TEST (or other environment)

Excerpt: FATAL: terminating connection due to administrator command

Full error:

Get Record Counts - Unexpected error

Get Record Counts - org.pentaho.di.core.exception.KettleDatabaseException:

An error occurred executing SQL:

select

                    (case when (src_record_count = dwh_record_count) then 0 else 1 end) as HAS_DELETED_RECORDS

from

                    (

                                         select

                                                             (

                                                                                 SELECT COUNT(1) FROM

                                                                                 (

                                                                                                      select distinct

                                                                                                                          STATUS_REPORT_KEY as key_col, 1 as lang_col

                                                                                                      from

                                                                                                                          DWH_COP_PRJ_STATUSRPT_V

                                                                                 ) srctab

                                                             ) as src_record_count,                                                          

                                                             (

                                                                                 SELECT COUNT(1) FROM

                                                                                 (

                                                                                                      select distinct

                                                                                                                          STATUS_REPORT_KEY as key_col, 1 as lang_col

                                                                                                      from

                                                                                                                          DWH_INV_STATUS_REPORT

                                                                                 ) dwhtab

                                                             ) as dwh_record_count

                                         from

                                                             dwh_cfg_settings --just as a dummy table, because it always has one record

                    ) t

                   

FATAL: terminating connection due to administrator command

 

                    at org.pentaho.di.core.database.Database.openQuery(Database.java:1641)

                    at org.pentaho.di.trans.steps.tableinput.TableInput.doQuery(TableInput.java:233)

                    at org.pentaho.di.trans.steps.tableinput.TableInput.processRow(TableInput.java:143)

                    at

dwh_dim_has_records - Errors detected!

User Defined Java Class - Unexpected error

User Defined Java Class - java.lang.RuntimeException: ERROR: THERE WERE ERRORS DURING DIMENSION JOB EXECUTION FOR THE TABLE - DWH_INV_STATUS_REPORT

                    at Processor.processRow(Processor.java:64)

                    at org.pentaho.di.trans.steps.userdefinedjavaclass.UserDefinedJavaClass.processRow(UserDefinedJavaClass.java:1181)

                    at org.pentaho.di.trans.step.RunThread.run(RunThread.java:60)

                    at java.base/java.lang.Thread.run(Thread.java:834)

Environment

Release : 15.9.1

Component : CA PPM SAAS DATA WAREHOUSE

Resolution

The error indicates that Postgres killed the query as it was not getting a response from the BG server.

Determine why the bg server was unresponsive (support review of  bg-* logs).

Additional Information

See also: