**** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with server **** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with server **** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with server **** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with server **** **** -- no connection **** Report from: stdb_conn_dbms, Status: STDB_ERR ****No server is available for connection **** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with serverIf you can't find a solution, report to CDS and insert into your message the following details:
.errorfile=/tmp/VR1359940.err (2025-07-13T01:21:33) -2 -source=J/AJ/161/277/table3 -ref=VIZ68730a1e14c044