Hello,
I am trying to install RSA7.1 on a new server with the intention to deploy both Local Database and ACM on the same box.
I have ensured all pre-requisites have been met yet the installation is failing.
I believe its asking for sqlplus before its even configured. Also the variable $ORACLE_CLIENT_HOME is not populated yet being used.
Anyone tried to install the new version of IG&L?
Hello Najeeb,
I am running it on :Red Hat Enterprise Linux Server release 6.9 (Santiago)
Linux hc4t05718 2.6.32-696.10.3.el6.x86_64 #1 SMP Thu Sep 21 12:12:50 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
Error:
The installer install the oracle software and the grid. But has trouble installing the AVDB schema. Wondering if the following message is causing the installer to fail
Install Oracle Grid Software...
Waiting for Oracle install log
Oracle will install with ORACLE_GRID_HOME as /u01/app/12.1.0/grid
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 415 MB. Actual 1839 MB Passed
Checking swap space: must be greater than 150 MB. Actual 16385 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2018-03-12_07-52-48PM. Please wait ...[WARNING] [INS-41808] Possible invalid choice for OSASM Group.
CAUSE: The name of the group you selected for the OSASM group is commonly used to grant other system privileges (For example: asmdba, asmoper, dba, oper).
ACTION: Oracle recommends that you designate asmadmin as the OSASM group.
[WARNING] [INS-13014] Target environment does not meet some optional requirements.
CAUSE: Some of the optional prerequisites are not met. See logs for details. /tmp/OraInstall2018-03-12_07-52-48PM/installActions2018-03-12_07-52-48PM.log
ACTION: Identify the list of failed prerequisite checks from the log: /tmp/OraInstall2018-03-12_07-52-48PM/installActions2018-03-12_07-52-48PM.log. Then either from the log file or from installation manual find the appropriate configuration to meet the prerequisites and fix it manually.
You can find the log of this install session at:
/u01/app/12.1.0/grid/oraInventory/logs/installActions2018-03-12_07-52-48PM.log
The installation of Oracle Grid Infrastructure 12c was successful.
Please check '/u01/app/12.1.0/grid/oraInventory/logs/silentInstall2018-03-12_07-52-48PM.log' for more details.
As a root user, execute the following script(s):
1. /u01/app/12.1.0/grid/oraInventory/orainstRoot.sh
2. /u01/app/12.1.0/grid/root.sh
I see similar logs on SLES (I haven't tried to install on RHEL), but the installation continued and was successful.
Assuming this is your test env, can you please post the full 'aveksa-install.log' and '/u01/app/12.1.0/grid/oraInventory/logs/silentInstall2018-03-12_07-52-48PM.log'?
Hi Najeeb,
Please find attached the log and also the output from install.
Note: I have enabled lot of logging so you will see many more lines then needed.
At present, the DB gets installed correctly but load the ear gives problem. Looks like a path issue running the Check_InstanceRunning and cliAveksa.sh files.
How do i attach a file here?
When replying, you should see 'Use advanced editor' option in the top right corner of reply window. Click 'Use advanced editor', then you should see an option "Attach" in the lower left corner.
PFA
Some more installation trials later. I am getting this in the aveksa-install.log before the installer crashes
Repackage aveksa.ear to /tmp/repackaged_ear_dir
Deploying aveksa.ear...
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {"Services that were unable to start:" => ["jboss.deployment.subunit.\"aveksa.ear\".\"acmSubscriber.jar\".PARSE","jboss.deployment.subunit.\"aveksa.ear\".\"aveksa.war\".PARSE","jboss.deployment.subunit.\"aveksa.ear\".\"wpConsole.war\".PARSE","jboss.deployment.subunit.\"aveksa.ear\".\"wpServices.war\".PARSE","jboss.deployment.unit.\"aveksa.ear\".PARSE"],"Services that may be the cause:" => ["jboss.http-upgrade-registry.default","jboss.naming.context.java.JmsXA","jboss.remoting.remotingConnectorInfoService.http-remoting-connector"]}}}}
Failed to deploy aveksa.ear
Fresh install failed..
Looks like the original reported problem is no longer occurring (perhaps it was due to some environment issue?).
For the latest issue, please open a Support Case (if not already done) for further investigation/assistance. Thank you!
When you open a case, please also provide stdout and stderr.log from /home/oracle/wildfly/standalone/log (assuming this is an Appliance).
I have opened a case # 01136656: RSA 7.1 installation failing
I had attached the installation logs earlier. I will now attach the stdout.log too. There is no stderr.log.
Note: I am running a Software Bundle Installation on RedHat 6.9 with Wildfly and Oracle combination.
Thanks
Sunita
Just want to give update on my installation effort.
The issue was that installation files are built for IPV6. This is not mentioned in the documentation. Had to get a work-around for IPV4.
The data-purging scheduler gave trouble during the aveksa_server startup. Had to put a work around there as well.
Thanks to Mike Candon for helping.
Hello,
care to elaborate on the work-around for IPv4? I get the same problem while deploying aveksa.ear
Before running the installation,
1.Find the file 'aveksa_server' file under ....staging/deploy.... folder
Inside this file there were three entries for Java_opt.
added an additional attribute for IPV4 for each of the entries.
JAVA_OPTS="-Xms${WILDFLY_HEAP_MEM}m -Xmx${WILDFLY_HEAP_MEM}m -XX:MaxMetaspaceSize=${WILDFLY_PERM_META_MEM}m -XX:InitiatingHeapOccupancyPercent=10 -Djava.net.preferIPv4Stack=true"
2. Find the file 'domain.xml' under ...staging/deploy folder
Look for Java setting xml and add the IPV4 option
<server-groups>
<server-group name="img-server-group" profile="full-ha">
<jvm name="default">
<heap size="${jboss.memory.max.heap.size}" max-size="${jboss.memory.max.heap.size}"/>
<jvm-options>
<option value="-server"/>
<option value="-XX:MaxMetaspaceSize=${jboss.memory.max.permgen.size}"/>
<option value="-Djava.net.preferIPv4Stack=true"/>
<option value="-XX:+UseG1GC"/>
<option value="-XX:+ExplicitGCInvokesConcurrent"/>
<option value="-XX:+ParallelRefProcEnabled"/>
<option value="-XX:+AlwaysPreTouch"/>
<option value="-XX:+UseStringDeduplication"/>
<option value="-XX:InitiatingHeapOccupancyPercent=10"/>
<option value="-XX:+HeapDumpOnOutOfMemoryError"/>
<option value=" -XX:HeapDumpPath=/home/oracle/wildfly/domain/log/"/>
</jvm-options>
</jvm>
<socket-binding-group ref="full-ha-sockets"/>
<deployments>
<deployment name="aveksa.ear" runtime-name="aveksa.ear"/>
<deployment name="aveksaWFArchitect.ear" runtime-name="aveksaWFArchitect.ear"/>
</deployments>
</server-group>
</server-groups>
Thank you! That did the trick
What is the OS and version? Can you share the exact message or logs that you see at the point of failure?
FYI, there's a known issue where IGL 7.1 installation on SLES 12 with local database may fail due to not finding the following packages (even though those should not be needed as the database is local and OS is not RHEL):
instantclient-basiclite-linux.x64-12.1.0.2.0.zip
instantclient-sqlplus-linux.x64-12.1.0.2.0.zip
redhat-release-6Server-1.noarch.rpm
If you are seeing a message/error about the above missing packages, a workaround is to just copy those packages from installation distribution to the folder /tmp/aveksa/packages, and retry the installation.