35
Hi all,
I have an issue where we put upgraded SL 2011 DBs on the same server as the original 6.5 DBs. Posting in GL stopped working so we went to Database Maintenance to Synchronize (the fix in the tech note) and we found that it is now trying to use CD835... instead of CD735.. in 6.5 version of DB Maintenance. Does anybody know where this is stored?
Thanks
*This post is locked for comments
I actually figured it out (a lot of time later). I had both SL 2011 and SL 6.5 databases on the same server (as described above.) In one of the processes (still not sure which one) several triggers were added to acct_xref, acctsub_xref, etc. tables in the 6.5 system DB that were connected to the newer 2011 databases. I still am not sure if I selected something wrong or if there was an error in one of the scripts that I ran but long story short, the system was looking for the user CD835... to run the triggers and that user did not exist. Once I deleted the triggers (they were obviously incorrect) everything was good.
At the end of the day I'm not sure what caused it (which is what scares me the most), but after the change I am able to run both versions without issue. Sounds like you may have had the same issue and the restore prior to the triggers getting created fixed it (just a thought)
Years ago, I had a similar problem when we installed SL 7 on the same server as our live SL 6.5. It was a mess, but I got us back up and running by saving off the system database to a different name, restoring the system database from a point before our SL 7 experiment, and then modifying records in the system db tables as needed so there was no data loss.
It was a godawful mess that I put forward only because no one else has answered. I hope you have found an easier solution elsewhere.
#1
André Arnaud de Cal...
291,711
Super User 2024 Season 2
#2
Martin Dráb
230,458
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
