Mind if I ask the version of Java and where it's installed? On Wed, Oct 11, 2017, 9:07 AM Grooms, Frederick W <[email protected]> wrote:
> ** > > It is not crucial for the install. I have installed new hardware (empty > directories) pointing to an existing database (Granted this was 8.1 on > Linux) with no issues. > > When you start up on 8.1 are there any errors in the logs? > > > > I did have an issue in one environment where 9.1 would not start. It > would give errors like Error creating bean… The issue had to do with > missing permissions for the user and role in the Oracle db. > > > > Fred > > > > *From:* Action Request System discussion list(ARSList) [ > mailto:[email protected] <[email protected]>] *On Behalf Of *Thomas > Miskiewicz > *Sent:* Wednesday, October 11, 2017 1:17 AM > > > *To:* [email protected] > *Subject:* Re: Second try --> Upgrade 8.1.00 to 9.1.03 Failed > > > > ** > > Abhijeet, > > > > if ARSystemInstalledConfiguration.xml so crucial for the installation why > wouldn’t the pre-check routine tell me that but continues with the > installation instead? > > > > Where in the BMC documentation do I read that the > ARSystemInstalledConfiguration.xml needs to be there and what it should > contain for a successful upgrade? > > > > Last week I took the ARSystemInstalledConfiguration.xml that was created > by the failed installation and started a new try using it. Same errors. > > > > In the meantime the BMC Support keeps silent… > > > > > > Thomas > > On 10. Oct 2017, at 19:03, Gadgil, Abhijeet wrote: > > > > ** > > Looked the logs that were mentioned at the start of this email thread. > > We see a couple of issues within the logs and calling these out in reverse > chronological order: > > 1. SEVERE error regarding server not starting up – this is a result > of database changes themselves not going thru correctly in the first place. > > 2. While making database changes, there is a ORA-02437 error > > a. (Oct 06 2017 02:52:22.617 PM > +0200),WARNING,com.bmc.install.product.arsuitekit.platforms.arsystemservers.arserver.ARServerManageUpgradeJDBCWriterErrorHandler, > > LOG EVENT {Description=[Failed to create primary key when running sql: > ALTER TABLE ARADMIN.FILTER_PUSH ADD PRIMARY KEY ( filterId, actionIndex, > fieldId, overlayGroup ). Upgrade will continue, but upon completion > database should be manually corrected to ensure product performs as > designed.],Detail=[ORA-02437: cannot validate (ARADMIN.SYS_C0062062) - > primary key violated > > 3. Even with just this error, we would expect only some of the > imports for FILTERs to fail. But, there are a lot many failures related to > duplicate inserts. > > > > Looking at the log in detail, we see that database changes didn’t go > through correctly. This is evident from the log of > ARServerPriorToServerJDatabaseUpgradeTask class, really missing logs from > this class tell us this class didn’t go through and inserts are failing > with index violation error. > > > > Why did this class not execute – really either of the 2 conditions: > > a. Either the server being upgraded is secondary server – this is > not the case and it’s confirmed in the logs. > > b. Or it did not find “*featureARServer*” product ID and version in > *ARSystemInstalledConfiguration.xml* that existed in the install > directory before starting the upgrade – this seems to be true in this case > as Thomas mentioned in the mail below “ARSystemInstalledConfiguration.xml > didn’t exist but it was created after the first failed installation. In > there it says, server is NOT server group member. So does ar.conf”. > > > > We have seen similar issue in the past due to corrupt/incomplete or > missing ARSystemInstalledConfiguration.xml file. > > Now why this file does not exist before upgrade is the real root cause, > which you can check based on audit enabled on OS. > > > > > > Fix for this issue: > > · Revert the system completely back to 8.1 clean state including > database and file system. > > · Ensure file system has correct > ARSystemInstalledConfiguration.xml file with lines such as this: > > o <productFeature backupOnUpgrade="false" id="featureARServer" > independentOfChildren="true" > parent="featureARSystemServers" rebootRequiredOnInstall="false" > rebootRequiredOnUninstall="false" rebootRequiredOnUpgrade="false" > requiredDiskSpaceMode="default.windows" state="INSTALLED" visible="true"> > > <version majorVersion="1" minorVersion="00" releaseVersion="8"/> > … > > · Ensure there are no duplicates in FILTER_PUSH table. Use this > query to find if there are duplicates before upgrade: > > o select filterId, actionIndex, fieldId, count(*) from filter_push > group by filterId, actionIndex, fieldId having count(*) > 1 > > o If above query finds duplicates, that needs to be fixed before > starting the upgrade. Clearly there seem to be corrupt entries related to > overlays of those filters. Don’t see how it will happen via the product. > > > > Then start upgrade with 9.1.03 and this time it should succeed once > database is upgraded successfully. > > > > Regards, > > Abhijeet > > > > > > *From:* Action Request System discussion list(ARSList) [ > mailto:[email protected] <[email protected]>] *On Behalf Of *Thomas > Miskiewicz > > > *Sent:* 10 October 2017 15:55 > *To:* [email protected] > *Subject:* Re: Second try --> Upgrade 8.1.00 to 9.1.03 Failed > > > > ** > > I didn’t try and I won’t. I have 24 servers to upgrade!!! > > On 10. Oct 2017, at 16:51, Brian Pancia wrote: > > > > ** > > Have you tried to upgrade one sp/version at a time instead of going > directly to 9.1.03. I've done countless upgrades and never had a lot of > luck with going from one version (ie 8.x to 9.x). In that case I've always > did a clean install and migrate data. RRRChive does an excellent job at > moving data. I've seen installers go through stating successful only to > find out things were missing on the back end. I would recommend trying an > incremental upgrade first and if you're spinning your tires do a clean > install and migrate data. It might be quicker then troubleshooting the > install. > > > > Brian > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) < > [email protected]> on behalf of Thomas Miskiewicz > > *Sent:* Tuesday, October 10, 2017 8:14:40 AM > *To:* [email protected] > *Subject:* Re: Second try --> Upgrade 8.1.00 to 9.1.03 Failed > > ** > > No, the issue is that the installer updates the binaries and then cannot > start the server and gives up. I also feel like giving up after the BMC > support cannot tell us what their product does. > > > > Thomas > > > On 10. Oct 2017, at 14:08, Saji Philip wrote: > > ** > > Is this an upgrade in place? Does the installer hang (never finishes and > no errors). We had a similar issue and the 9..x would fail ARS because we > had a custom AL guide and it would error out on tha arcontainer table. > Taking a backup and deleting this AL guide allowed ARS to install. Then we > had problems with Atrium in that it didn't like our overlay on the > BMC.Elements form. But that would error out. We just deleted the > overlay. But the weirdest part is that ITSM would hang in installation. > Putting the server to Allow queries to be true, even though the prechecker > said otherwise, allowed the ITSM to go through... > > 8.1.02 going to 9.1.03 > > > > On 6 Oct 2017 6:29 pm, "Thomas Miskiewicz" wrote: > > > > ** > > Hi, > > > > the dbVersion is 54. > > > > Server is not part of the server group, still the stupid installer says: > server is NOT server group member, server IS server group member, server is > NOT server group member … why? > > > > (Oct 06 2017 02:29:12.122 PM > +0200),CONFIG,com.bmc.install.task.InstallationPropertiesHelper, > > LOG EVENT {Description=[SET PROPERTY > BMC_AR_SERVER_GROUP_MEMBER],Detail=[F]} > > > > [className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Num-Preload-Schema-Segments, , 25, searchKEYandREPLACEvalue]], > [className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Num-Preload-Threads, , 10, searchKEYandREPLACEvalue]], > [className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Application-Enable, F, T, setCFGentry]], > [className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Large-Result-Logging-Threshold, , 1000000, setCFGentry]], > [className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Max-Log-History, , 8, setCFGentry]], > [className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Max-Log-File-Size, , 134217728, setCFGentry]]]], [level=Database Only > Server Group > Configuration,commands=[[className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Server-Group-Member, , F, searchKEYandREPLACEvalue]]]], [level=AR Server > Group > Configuration,commands=[[className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Server-Group-Member, , T, searchKEYandREPLACEvalue]]]], [level=Configure > JMX,commands=[[className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Jmx-port, , 61500, searchKEYandREPLACEvalue]]]], [level=Configure > JMS,commands=[[className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Default-messaging-port, , 61617, searchKEYandREPLACEvalue]]]], [level=AR > Server Atrium SSO Configurati > > > > > > > > (Oct 06 2017 02:47:07.676 PM > +0200),INFO,com.bmc.smbu.install.common.rule.engine.StageGroup, > > LOG EVENT {Description=[Skipping execution of > stage],Detail=[[level=Database Only Server Group > Configuration,commands=[[className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Server-Group-Member, , F, searchKEYandREPLACEvalue]]]]]} > > (Oct 06 2017 02:47:07.676 PM > +0200),INFO,com.bmc.smbu.install.common.rule.engine.Stage, > > LOG EVENT {Description=[Executing stage [level=AR Server Group > Configuration,commands=[[className=com.bmc.install.product.arsuitekit.platforms.arsystemservers.task.ARServerUpdateConfigurationEntry,arguments=[/ESP/usr/ar/ARSE1/conf/ar.conf, > Server-Group-Member, , T, searchKEYandREPLACEvalue]]]]]} > > (Oct 06 2017 02:47:07.676 PM > +0200),INFO,com.bmc.smbu.install.common.rule.engine.extension.ExtensionCommand, > > LOG EVENT {Description=[Executing extension Command]} > > > > etc. > > > > arsystem_install_log.txt attached > > > > ARSystemInstalledConfiguration.xml didn’t exist but it was created after > the first failed installation. In there is say, server is NOT server group > member. So does ar.conf > > > > I’m on Solaris in this case. > > > > arerror.log has a few hundreds entries complaining that he couldn’t import > forms: > > > > Fr Okt 06 15:26:28.836 2017 Import failed for AR System Administration: > Add Or Remove Licenses: > > Fr Okt 06 15:26:28.953 2017 Import failed for AR System Administration: > Display Form To Collect User Decisions: > > Fr Okt 06 15:26:29.225 2017 Import failed for AR System License: Save > Produse Attachment: > > Fr Okt 06 15:26:29.530 2017 Import failed for AR System Licenses Console: > > Fr Okt 06 15:26:29.688 2017 Import failed for AR System: Generate License > Usage Report: > > Fr Okt 06 15:26:29.986 2017 Import failed for AR System Licenses Audit: > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
