Error purging PostgreSQL database. Reason: ERROR: syntax error at or near “exists”Position: 15












0















I am using PostgreSQL database with Tomcat Server. When I checked webpage today, it shows about mentioned alarm with following logs:



2018-11-05 01:06:05,628 [1AM Thread] DEBUG com.swhh.csta.d.c.k - Purging Devices
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] DEBUG com.swhh.cs.e.u - No lock folder to check yet
2018-11-05 01:06:05,628 [1AM Thread] INFO com.swhh.cs.uarchive.h - Purging and checking for historic archive runs
2018-11-05 01:06:05,628 [1AM Thread] INFO com.swhh.cs.uarchive.h - Purging archive \ip-addressarchive3
2018-11-05 01:06:05,643 [1AM Thread] INFO com.swhh.cs.e.au - Purging recordings (except those locked) prior to Nov 5, 2013 1:06:05 AM
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Retaining 0 contacts due to locked records from before purge point.
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Retaining 0 contacts due to locked records from before purge point and/or spanning the purge point.
2018-11-05 01:06:05,659 [1AM Thread] ERROR com.swhh.cs.a.p - Alarm raised err.database.purge [ERROR: syntax error at or near "exists"
Position: 15] [null]
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Daily House-keeping completed









share|improve this question
















bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 2





    edit your question (by clicking on the edit link below it) and show us the SQL statement that generates that error (edit your question do not post code in comments)

    – a_horse_with_no_name
    Nov 5 '18 at 7:34






  • 1





    Check the postgres logs, rather than the Tomcat logs.

    – jjanes
    Nov 5 '18 at 20:49
















0















I am using PostgreSQL database with Tomcat Server. When I checked webpage today, it shows about mentioned alarm with following logs:



2018-11-05 01:06:05,628 [1AM Thread] DEBUG com.swhh.csta.d.c.k - Purging Devices
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] DEBUG com.swhh.cs.e.u - No lock folder to check yet
2018-11-05 01:06:05,628 [1AM Thread] INFO com.swhh.cs.uarchive.h - Purging and checking for historic archive runs
2018-11-05 01:06:05,628 [1AM Thread] INFO com.swhh.cs.uarchive.h - Purging archive \ip-addressarchive3
2018-11-05 01:06:05,643 [1AM Thread] INFO com.swhh.cs.e.au - Purging recordings (except those locked) prior to Nov 5, 2013 1:06:05 AM
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Retaining 0 contacts due to locked records from before purge point.
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Retaining 0 contacts due to locked records from before purge point and/or spanning the purge point.
2018-11-05 01:06:05,659 [1AM Thread] ERROR com.swhh.cs.a.p - Alarm raised err.database.purge [ERROR: syntax error at or near "exists"
Position: 15] [null]
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Daily House-keeping completed









share|improve this question
















bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 2





    edit your question (by clicking on the edit link below it) and show us the SQL statement that generates that error (edit your question do not post code in comments)

    – a_horse_with_no_name
    Nov 5 '18 at 7:34






  • 1





    Check the postgres logs, rather than the Tomcat logs.

    – jjanes
    Nov 5 '18 at 20:49














0












0








0








I am using PostgreSQL database with Tomcat Server. When I checked webpage today, it shows about mentioned alarm with following logs:



2018-11-05 01:06:05,628 [1AM Thread] DEBUG com.swhh.csta.d.c.k - Purging Devices
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] DEBUG com.swhh.cs.e.u - No lock folder to check yet
2018-11-05 01:06:05,628 [1AM Thread] INFO com.swhh.cs.uarchive.h - Purging and checking for historic archive runs
2018-11-05 01:06:05,628 [1AM Thread] INFO com.swhh.cs.uarchive.h - Purging archive \ip-addressarchive3
2018-11-05 01:06:05,643 [1AM Thread] INFO com.swhh.cs.e.au - Purging recordings (except those locked) prior to Nov 5, 2013 1:06:05 AM
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Retaining 0 contacts due to locked records from before purge point.
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Retaining 0 contacts due to locked records from before purge point and/or spanning the purge point.
2018-11-05 01:06:05,659 [1AM Thread] ERROR com.swhh.cs.a.p - Alarm raised err.database.purge [ERROR: syntax error at or near "exists"
Position: 15] [null]
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Daily House-keeping completed









share|improve this question
















I am using PostgreSQL database with Tomcat Server. When I checked webpage today, it shows about mentioned alarm with following logs:



2018-11-05 01:06:05,628 [1AM Thread] DEBUG com.swhh.csta.d.c.k - Purging Devices
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] WARN com.swhh.csta.a.n - REFRESH: TSAPI service down.
2018-11-05 01:06:05,628 [1AM Thread] DEBUG com.swhh.cs.e.u - No lock folder to check yet
2018-11-05 01:06:05,628 [1AM Thread] INFO com.swhh.cs.uarchive.h - Purging and checking for historic archive runs
2018-11-05 01:06:05,628 [1AM Thread] INFO com.swhh.cs.uarchive.h - Purging archive \ip-addressarchive3
2018-11-05 01:06:05,643 [1AM Thread] INFO com.swhh.cs.e.au - Purging recordings (except those locked) prior to Nov 5, 2013 1:06:05 AM
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Retaining 0 contacts due to locked records from before purge point.
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Retaining 0 contacts due to locked records from before purge point and/or spanning the purge point.
2018-11-05 01:06:05,659 [1AM Thread] ERROR com.swhh.cs.a.p - Alarm raised err.database.purge [ERROR: syntax error at or near "exists"
Position: 15] [null]
2018-11-05 01:06:05,659 [1AM Thread] INFO com.swhh.cs.e.au - Daily House-keeping completed






postgresql






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 5 '18 at 7:33









a_horse_with_no_name

40.1k776112




40.1k776112










asked Nov 5 '18 at 7:26









Yatish BathlaYatish Bathla

1063




1063





bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 2





    edit your question (by clicking on the edit link below it) and show us the SQL statement that generates that error (edit your question do not post code in comments)

    – a_horse_with_no_name
    Nov 5 '18 at 7:34






  • 1





    Check the postgres logs, rather than the Tomcat logs.

    – jjanes
    Nov 5 '18 at 20:49














  • 2





    edit your question (by clicking on the edit link below it) and show us the SQL statement that generates that error (edit your question do not post code in comments)

    – a_horse_with_no_name
    Nov 5 '18 at 7:34






  • 1





    Check the postgres logs, rather than the Tomcat logs.

    – jjanes
    Nov 5 '18 at 20:49








2




2





edit your question (by clicking on the edit link below it) and show us the SQL statement that generates that error (edit your question do not post code in comments)

– a_horse_with_no_name
Nov 5 '18 at 7:34





edit your question (by clicking on the edit link below it) and show us the SQL statement that generates that error (edit your question do not post code in comments)

– a_horse_with_no_name
Nov 5 '18 at 7:34




1




1





Check the postgres logs, rather than the Tomcat logs.

– jjanes
Nov 5 '18 at 20:49





Check the postgres logs, rather than the Tomcat logs.

– jjanes
Nov 5 '18 at 20:49










1 Answer
1






active

oldest

votes


















0














After checking postgres logs, I update postgres version from 8 to 9.2 and everything works now.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f221782%2ferror-purging-postgresql-database-reason-error-syntax-error-at-or-near-exist%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    After checking postgres logs, I update postgres version from 8 to 9.2 and everything works now.






    share|improve this answer




























      0














      After checking postgres logs, I update postgres version from 8 to 9.2 and everything works now.






      share|improve this answer


























        0












        0








        0







        After checking postgres logs, I update postgres version from 8 to 9.2 and everything works now.






        share|improve this answer













        After checking postgres logs, I update postgres version from 8 to 9.2 and everything works now.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 7 '18 at 15:24









        Yatish BathlaYatish Bathla

        1063




        1063






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f221782%2ferror-purging-postgresql-database-reason-error-syntax-error-at-or-near-exist%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Liste der Baudenkmale in Friedland (Mecklenburg)

            Single-Malt-Whisky

            Czorneboh