Ray Actually we do not have any transaction logging in place... Eveyone here assumed we had everything turned off and were not using any king of transaction logging...
Then I go testing some simple triggers and I get the error on this thread... That's when I determined that our TXMODE flag in the config file is set to a '1'. I assumedif we were not doing any actual transaction logging we would have TXMODE set to a 0, and we would not be running the logging services daemon.. If we did have transaction logging in place we would have TXMODE set to a 1, and we would have the logging service demon running. I am not sure if that is correct but that is my assumption.. ;) Therefore I am thinking we simply need to change TXMODE to 0, to alleviate the error I am getting when trying to process my triggers.. Make sense? Ray Wurlod wrote: > > Yes the problem is with transaction logging, but don't switch it off > completely. Find out why things can't be logged. For example are the > logs all in a FULL state? Is the system-wide state of transaction logging > preventing logging? > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > > -- View this message in context: http://www.nabble.com/Universe-trigger-errors---log-daemon-issue-tp19391955p19415042.html Sent from the U2 - Users mailing list archive at Nabble.com. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
