Question3Replies33Views baigmirza Member since 2013 3 posts Federal Employee Program - Carefirst BlueCross BlueShield Posted: December 3, 2019Last activity: December 5, 2019 Closed Pega OOTB table has "NOT LOGGED INITIALLY" statusWe are working on a project for continuous delivery support and will be using QREP from the database (DB2 UDB version 10.5/11) side to achieve this.We have found that Pega for some reason uses “NOT LOGGED INITIALLY” status for its out of the box tables. This feature/flag is not supported by QREP.We need help in finding out if Pega has a way to turn off this flag or an upcoming version that has the ability to turn on/off this status. Low-Code App Development ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 11 months agoLONGJ PEGA replied to baigmirzaThe nologging option can be disabled for DB2 by adding this line to the setupdatabase.properties file. pega.override.enable.nologging=false As the application is already installed, you may need to make further Stored Procedure changes following https://community.pega.com/support/support-articles/not-logged-initially-option-used-db2 Posted: 11 months agobaigmirza Federal Employee Program - Carefirst BlueCross BlueShield replied to LONGJThanks LONGJ for your response. I believe this is helpful for a new Pega environment being set up. What do we do for the existing setup that's being used in Development, UAT and Production? Posted: 11 months agoLONGJ PEGA replied to baigmirzaI have updated my comments to include the link for the existing env. You could reach out to GCS for the updated Stored Procedures or make the suggested changes yourself following that link.