I have been working for a number of weeks getting the following configuration running:
1 x SLES 12 SP2 iSCSI Target (serving OCR2 / ASM Disks)
2 x SLES 12 SP2 HOSTS (NODE 1 / NODE 2) running SLES HA, with Oracle 11gR2 Grid.
all within VMWare Workstation 14.
This was basically a practise installation before attempting this on the real hardware. The HA Cluster is up and running and the disks are accessible with no issues.
I’ve followed various tutorials from both SuSE and Oracle and the installation always fails just after the ASM disks are created (running the root.sh script):
ASM created and started successfully.
Disk Group DATA created successfully.
PROT-1: Failed to initialize ocrconfig
PROC-26: Error while accessing the physical storage
ORA-12547: TNS:lost contact
Failed to create Oracle Cluster Registry configuration, rc 255
Oracle Grid Infrastructure Repository configuration failed at /home/oracleRDBMS/grid/11.2/db/crs/install/crsconfig_lib.pm line 6919.
/home/oracleRDBMS/grid/11.2/db/perl/bin/perl -I/home/oracleRDBMS/grid/11.2/db/perl/lib -I/home/oracleRDBMS/grid/11.2/db/crs/install /home/oracleRDBMS/grid/11.2/db/crs/install/rootcrs.pl execution failed
I have an Oracle SR open for this and have just spent 4 hours in a WebEx with them, but the issue is still outstanding.
Has anyone managed to get a similar configuration running on SLES that can point out what I (and now Oracle) are missing?
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:
Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot…
This is still an outstanding issue for us and I’m still working with Oracle support to resolve, but so far no progress.
I’ve read various SuSE generated HowTo installs, all of which end with a successful installation(!)
We have a valid SuSE support contract, using that, is this something we can get some advice on? (Or will I just be turned away and told its an Oracle problem)
We have a valid SuSE support contract, using that, is this something
we can get some advice on? (Or will I just be turned away and told
its an Oracle problem)[/color]
Hi Kevin,
I see it’s been a couple of weeks since your initial post and no one
has responded. This is a pretty good indication that none of us have
encountered this issue and are unable to offer any suggestions.
Since you have a support contract, my advice is to open a Service
Request with SUSE and see what help they are able to provide. It can’t
hurt.
You may want to provide SUSE with your Oracle SR number. It may help
the two organisations coordinate a solution.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
have you tried to install SOFTWARE ONLY and first patch than configure your installation ?
In the past we see something like this with missing kernel modules and after patching the software only installation with the latest patch set the root.sh runs
without error. May you hit a undocumented bug.
Of all the hardware swaps and changes I made while trying to track this down, the one that was in common on all the machines, except for one old laptop where I managed to get the installation working was the processor.
Hardware Lock Elision is not my friend. Added the work around and everything burst into life.
I am going to document the installation steps for SLES 12 SP3 (moved up a SP while all of this was going on), / Oracle 11.2.0.4 (and I understand this still affects Oracle 12c) with ASM under VMWare (and yes VMWare it is possible to do this under Workstation, not just vSphere). It is not a straightforward process and there are lots of pitfalls.
We appreciate your feedback.Hopefully it will save others a lot of
grief!
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.