Sometimes while loading via Relational load you might stumble upon the following error:
Cannot load data into table XXX: ERROR: portal “C_1” does not exist(load New Relational load)
Although I am not sure for the real reason of this error, it is worth of looking and Fetch Modes for PostgreSQL.
For a PostgreSQL database, you can adjust the fetch mode as follows: Buffered (default): the query result is returned with buffering. In this case, no parallel queries to the same PostgreSQL Server are possible. Full: PostgreSQL returns the query result in one block. This is potentially slower, with higher memory consumption. It should only be set if the connection is used in several components that are processed in parallel during a load, e.g. several PostgreSQL extracts that are joined in a transform, an extract, and a load on the same PostgreSQL connection or when using parallel jobs. (Note that in those cases, if the fetch mode is not set to “full” this might lead to an error message: “postgresql portal <x> does not exist”.) |
and there is a solution lays Buffered is usually in default mode during the load – so the solution will be to change the mode to full!