Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Create table error on start up - postgreSQL

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Create table error on start up - postgreSQL

Last Update:

Sep 26, 2023 3:04:08 AM

Updated By:

Sonja_Bauernfeind

Created date:

Apr 10, 2019 11:29:58 AM

When PostgreSQL restart and error message is logged in the windows event logs. Error message:

The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following informatin was included with the event: 

ERROR:  relation "nodes" already exists

STATEMENT:  CREATE TABLE nodes (

        hash BYTEA PRIMARY KEY,

        refs INT NOT NULL,

        value BYTEA,

        value_string TEXT,

        datatype TEXT,

        language TEXT,

        iri BOOLEAN,

        bnode BOOLEAN,

        value_int BIGINT,

        value_bool BOOLEAN,

        value_float double precision,

        value_time timestamp with time zone

    );

This is working by design and a harmless error message. Whenever precedents service starts up, it re-runs the appropriate database initialization request. This is to ensure the required tables exist before it starts using those tables. 

 

Environment:

Qlik Sense Enterprise on Windows 

Labels (1)
Comments
Raju_6952
Creator
Creator

Hi @Sonja,

 

We are not able to use qlik sense anymore after getting this error also restarted all the qlik services multiple times.

 

Any clues would be highly appreciated.

 

Ps: we are using June 2019 version of qlik sense 

 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @Raju_6952 

This is not an error you need to worry about. As stated:

This is working by design and a harmless error message. Whenever precedents service starts up, it re-runs the appropriate database initialization request. This is to ensure the required tables exist before it starts using those tables. 

If you are "unable to use Qlik Sense anymore", the root cause would be something else and you would need to review additional log files to find it. Check error message you are seeing when accessing the QMC or HUB against our knowledge base and community to make progress. But please note that June 2019 is out of support and that I cannot provide you with additional assistance here.

You are welcome to post about the issue in our Deployment and Management forum though.

All the best,
Sonja

Contributors
Version history
Last update:
‎2023-09-26 03:04 AM
Updated by: