Please see inlile On Tue, Aug 1, 2017 at 12:30 AM, Tom Wagner <t...@snarkboojum.com> wrote: > Hi Maxim, > > Finally back with this issue, which I tabled as I didn't want to poke around > a working install just before a series of webinars. =-O > > Apparently during the upgrade, the old persistence.xlm specifying mySQL as > the database was overwritten with the Derby default. Then I blithely > restored my configs and data from backup, which got read into the new Derby > instance and left the mySQL instance orphaned. > > I'm thinking that all I need to do to correct this is make a backup of the > current conf/data, change my persistence.xml, and restore. Any gotchas you > have for me before I try this?
Correct. > > Also thinking that I need the following protocol for upgrades: > > take OM backup && update OM && edit/restore overwritten persistence.xml && > restore OM backup. > > If this proves to be the case, can/shall I add this advice to update how-to > documentation. I would love to get documentation clarification I'm not native speaker > > Cheers, > > =tew= > > ________________________________ > On 06/13/2017 10:59 PM, Tom Wagner wrote: > > Thank you, Maxim. > > Looks like it's time to expand the limits of my understanding of mySQL. I > did wonder if I had somehow acquired another database process, perhaps in > the upgrade(s), but I could only find one mysql instance in the system > process list. > > I'm not familiar with the terms "DB nodes" and "active persistence.xml", > but I will research them. I certainly didn't intentionally create them if I > do in fact have them, but the OM server is definitely running--quite happily > it appears--on some other set of tables that I can't see when logged in as > root. > > Thanks for these clues. I will go away and perhaps be back with better > questions, or post my resolution. It's certainly not on your plate to teach > me advanced mySQL admin. :-) > > Best, > > =tew= > > > On 06/13/2017 10:44 PM, Maxim Solodovnik wrote: > > Hello Tom, > > Nothing has changed (I'm using "raw DB access" to check things. > Maybe you have several DB nodes? Could you check using your active > persistence.xml? > > On Tue, Jun 13, 2017 at 12:04 AM, Tom Wagner <t...@snarkboojum.com> wrote: >> >> Has something changed radically in the way OM stores data. >> >> Previously I could log into mySQL (MariaDB) on the server (localhost) as >> root with the web admin tool phpMyAdmin and browse/query data---like the >> conferencelog (for attendance verification) and the invitations table (for >> hashes to mail merge into prettier reminders for our attendees). >> >> Now however, I see no records beyond a dated prior to the upgrade from >> 3.0. Very, very strange---as the server performs normally, calendars and >> hosts conferences, and records new user entries as expected according to the >> web GUI. >> >> For example, I've entered a number of new users this year who show in the >> web GUI, and can participate normally in conferences. But when I browse the >> om_users table, they are nowhere to be seen and the latest record was >> inserted on 2015-07-15. !! >> >> Any light you can shed / what have I missed? >> >> -Tom Wagner, Jackson Orthopedic Foundation IT > > > > > -- > WBR > Maxim aka solomax > > > -- WBR Maxim aka solomax
