What about upgrading to even higher version? I see that the DB version would change so maybe we could force it this way?
> On 24. Apr 2019, at 20:33, Reif, Douglas <[email protected]> wrote: > > This is a difficult position. Since the DB was already upgraded to 57, the > installer won’t upgrade it again; nor will it perform the imports that > typically would have occurred after the DB was upgraded and arserver > restarted. > And there is not a way to downgrade the DB. > A “secondary” server is any server that is installing after the db was > upgraded. > The “primary” server is the first one to run the install while the DB is > still the original version. > Without a backup, I don’t know how you are going to get the installer to do > what you want. > An alternative is to simply manually import everything. > As you may be aware, there’s a lot of stuff to import. And this is not > technically a supported method. > BMC wants you to always have a DB backup or restore point you can use. > If you do decide to import manually, most everything is going to be in the > ‘Installforms’ directory. > But I am not going to make an official recommendation that you do that. You > can try it and see where it takes you. Test, Test, Test > > Doug > > > From: ARSList [mailto:[email protected]] On Behalf Of Thomas > Miskiewicz > Sent: Wednesday, April 24, 2019 11:23 AM > To: ARSList <[email protected]> > Subject: [EXTERNAL] Re: Installer is performing a secondary server > install/upgrade, No forms will be imported. > > Hi Doug, > > and thank you for the prompt reaction! > > The currdbversion version is indeed 57 however we don’t have a db we can > revert to... > > So the questions remain: > > - how does the installer recognize whether it’s dealing primary vs secondary > server > > or > > - how can we convince it to think of this server as primary server. > > Is a secondary server secondary forever? No right? > > > > Thomas > > > > On Wed 24. Apr 2019 at 20:17, Reif, Douglas <[email protected]> wrote: > Thomas, > We often see this problem after a prior install failed but had already > updated the database. > You run the next install and it checks the dbversion from the control table. > See https://communities.bmc.com/docs/DOC-37267. This shows that for 9104 the > currdbversion would be 57. > So my assumption is that if you checked the control table, you would see > this, meaning the DB was upgraded. > > The solution for this is to rollback the DB to prior to the upgrade that > failed. > The upgrades do not rollback the database automatically. It’s a lot of work > to undo some of the things the installers does because decisions are made > dynamically based on the environment. It’s a lot easier to make a db backup > or restore point and if the install fails, just revert to that. > > DougR > > > From: ARSList [mailto:[email protected]] On Behalf Of Thomas > Miskiewicz > Sent: Wednesday, April 24, 2019 10:01 AM > To: ARSList <[email protected]> > Subject: [EXTERNAL] Installer is performing a secondary server > install/upgrade, No forms will be imported. > > Hi All, > > we upgraded one single 7.6.04 server to 9.1.04 and got this at the end: > Installer is performing a secondary server install/upgrade, No forms will be > imported > > Same situation when we try to re-run the installer. Does anyone know where > does Remedy store the info or how it recognises which type of server > (primary/secondary)? > (Definitely not via ARSystemInstallationConfiguration as the parameter > BMC_IS_SECONDARY_SERVER is set to false.) > > BMC Support doesn’t know how to solve this… > > > > Thomas > -- > ARSList mailing list > [email protected] > https://mailman.rrr.se/cgi/listinfo/arslist > -- > ARSList mailing list > [email protected] > https://mailman.rrr.se/cgi/listinfo/arslist
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
