Hi Jack,
I thought I had answered to this, but apparently not. We have X3 and X4, and we
are not likely to get any more. They disappoint.
Not in grunt or daily use, not at all. They do exactly what you would expect
from two 2-socket 24-thread CPU/256GB RAM servers with a shared storage shelf.
And that is the problem, really, that storage shelf. Oracle promised that there
was a possibility to extend the storage by buying a second shelf. Some months
ago we decided to get a new shelf, but even though the X4 just last month
turned 1 year old, Oracle no longer sells the expansion shelves. They suggest
that we buy an X6 instead... yeah...
Add to that the patching. Yesterday, and the day before, I applied the
12.1.2.6.0 patch to the X3. Took me more than 24 hours in total, much of it
spent waiting for Oracle engineers to sort out what went wrong. Turns out that
the boot partition, which is only 100MB in size must have more than 50MB free
in order for the patch to succeed. The prepatch check scripts check for space
on / and /u01, but not for the critical /boot partition.
In my case, there were 2 kernels there, as the upgrades always leave the old
kernel - that is best practice. The last two kernels in 5.11 together took up
>55MB, leaving only 44MB for the patch. On reboot, the kernel panics because
the new initramfs is truncated and the X3 is configured to reboot on a panic. Fun..
Also for me the infra patch attempted to reboot before the JDK patch was
applied. This happened on both nodes, although the second time round I did make
sure there was enough space on /boot for the initramfs, so that was not the
cause. Perhaps some interaction with script? The support engineer did not seem
to think so, though..
I had to run oakcli update -clean and restart the update to finish the patch in
both nodes.
Apparently my predecessor also had a direct line with Oracle Support to get the
patches installed. Perhaps the X3 just was not that good.
I hope patching the X4 is going to be less eventful ;) First I've got the .7
patch on the X3 to do...
Cheers,
Tony
On 16/07/16 05:49, Jack Applewhite wrote:
Tony,
Yes, apart from LDAP getting nuked, going to OL 6.7 was painless. That's been
on two different X4s. My associate did that last .6 patch on the other X4
today. I'm doing the .5 patch on the first of two X5s. Besides some problems
with my home WiFi and our VPN, it's going well. Got the Infra patch done and
now waiting on the GI patch, which I'm running in a screen session (a truly
wonderful utility) so network hiccups don't mess me up. When we do the .6 patch
on an X5 I'll let you know how it went.
Do you have X4s, 5s, or a mix?
----
Jack C. Applewhite - Database Administrator
Austin I.S.D. - MIS Department
512.414.9250 (wk)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*From:* De DBA <dedba@xxxxxxxxxx>
*Sent:* Friday, July 15, 2016 6:31:40 AM
*To:* Jack Applewhite
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: ODA update to 12.1.2.5.0 node 2 hostname reset
Hi Jack,
Thanks for the heads-up. I've got to apply .6 and .7 as well. Luckily we
haven't implemented AD authentication yet, that's also scheduled soonish.. I
guess that's better left to last then :)
I must admit that the OEL upgrade to 6.7 scares me witless. I've tried
upgrading linux installations in the past, with little joy. RedHat does not
support in-place upgrades until RH6, and even then they suggest to perform a
new install instead (to upgrade to RHEL7), and OEL is based on that. I
understand that your ODAs did weather it and continue to live? Apart from ldap,
that is...
Cheers,
Tony
On 15/07/16 05:42, Jack Applewhite wrote:
Wait! How could I forget the big problem that the .6 patch did cause us?
Because it upgrades from OEL 5.11 to 6.7 it wiped out our whole LDAP setup,
which is based on Active Directory. That caused a lot of pain for a while until
the MOS tech and our SysAdmin worked out how to re-setup the whole thing.
If you need to know how, contact me off-list and I'll send you the log of their
SR communications and what steps worked.
----
Jack C. Applewhite - Database Administrator
Austin I.S.D. - MIS Department
512.414.9250 (wk)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf of
Jack Applewhite <jack.applewhite@xxxxxxxxxxxxx>
*Sent:* Thursday, July 14, 2016 12:34 PM
*To:* oracle-l@xxxxxxxxxxxxx; dedba@xxxxxxxxxx
*Subject:* Re: ODA update to 12.1.2.5.0 node 2 hostname reset
Wish I'd seen you first email, though I couldn't have provided a solution.
We've got two X4s and two X5s and just went through the 12.1.2.2.0 to
12.1.2.5.0 upgrade on the X4s. We didn't have your problem though we had some
of our own on one of the X4s. That involved having to restore the older (pre
.2) patch repos, but it took Oracle Support a long time to figure it out. There
aren't many of them that know ODAs very well.
The "good" X4 had no problems with the 12.1.2.5.0 patch and only minor problems
(had to remove a few disallowed RPMs) with the 12.1.2.6.0 patch. We're applying the .6
patch to the other X4 tomorrow and expect no issues besides the disallowed RPMs.
Actually, we did have a problem with the .5 patch - the DB part did not upgrade the
11.2.0.4.5 homes and DBs to 11.2.0.4.8. No errors, just nothing happened. However, the .6
patch did upgrade the 11.2.0.4.5 homes and DBs to 11.2.0.4.160119.
We'll apply the .5 patch to one of the X5s in the next few days, followed by
the .6 patch. Later the other X5 will get both patches. It's sure hard to get
downtime scheduled, even here at a School District over the summer.
Anyway, good to know there's another ODA-er out there. We'll keep in touch.
BTW, we have a VM environment setup with no RAC at all.
----
Jack C. Applewhite - Database Administrator
Austin I.S.D. - MIS Department
512.414.9250 (wk)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf of De
DBA <dedba@xxxxxxxxxx>
*Sent:* Thursday, July 14, 2016 12:59 AM
*To:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: ODA update to 12.1.2.5.0 node 2 hostname reset
I guess either ODAs are not very popular, or I have all the luck in the world,
finding arcane bugs..
Just to document it in case anyone needs it in the future: somehow the hostname
was changed in /etc/sysconfig/network. Changing it back and a reboot solved the
problem. Simple on hindsight, but it just took Oracle more than 6 hours of
pouring over logs to come up with the solution.
Cudos to the MOS support guy who was very diligent and helpful! Should happen
more often.
Cheers,
Tony
On 13/07/16 21:15, De DBA wrote:
> G'day
>
> I'm in the process of patching the least significant of a number of ODAs from
OAK 12.1.2.2.0 to 12.1.2.5.0. Everything seemed to go swimmingly until the reboot,
some 80 minutes after starting the first stage (INFRA).
>
> The first node came back up perfectly, CRS and ASM started normally - no
errors. However, somehow the host name on one node (node 2) was reset to 'oak2'
and nothing besides the OS and oakd started. Has anyone seen this before?
>
> OHASD complains that the autorun file is missing. I admit that I haven't a
lot of experience with CRS and OHASD, but I wonder if that can be reduced back to
the changed hostname? Provided that nothing else was destroyed by the update,
would changing the hostname back to what it should be allow OHASD to start?
>
> Cheers,
> Tony
> --
> //www.freelists.org/webpage/oracle-l ;
<//www.freelists.org/webpage/oracle-l>
oracle-l mailing list - freelists.org
<//www.freelists.org/webpage/oracle-l>
www.freelists.org
Welcome to Oracle-L@xxxxxxxxxxxxx An unmoderated forum for the discussion of
anything to do with using Oracle databases. Maintain your subscription:
>
>
>
--
//www.freelists.org/webpage/oracle-l
Confidentiality Notice: This email message, including all attachments, is for the
sole use of the intended recipient(s) and may contain confidential student and/or
employee information. Unauthorized use of disclosure is prohibited under the
federal Family Educational Rights & Privacy Act (20 U.S.C. §1232g, 34 CFR Part
99, 19 TAC 247.2, Gov’t Code 552.023, Educ. Code 21.355, 29 CFR 1630.14(b)(c)). If
you are not the intended recipient, you may not use, disclose, copy or disseminate
this information. Please call the sender immediately or reply by email and destroy
all copies of the original message, including attachments.
Confidentiality Notice: This email message, including all attachments, is for the sole use of the intended recipient(s) and may contain confidential student and/or employee information. Unauthorized use of disclosure is prohibited under the federal Family Educational Rights & Privacy Act (20 U.S.C. §1232g, 34 CFR Part 99, 19 TAC 247.2, Gov’t Code 552.023, Educ. Code 21.355, 29 CFR 1630.14(b)(c)). If you are not the intended recipient, you may not use, disclose, copy or disseminate this information. Please call the sender immediately or reply by email and destroy all copies of the original message, including attachments.
Confidentiality Notice: This email message, including all attachments, is for the sole use of the intended recipient(s) and may contain confidential student and/or employee information. Unauthorized use of disclosure is prohibited under the federal Family Educational Rights & Privacy Act (20 U.S.C. §1232g, 34 CFR Part 99, 19 TAC 247.2, Gov’t Code 552.023, Educ. Code 21.355, 29 CFR 1630.14(b)(c)). If you are not the intended recipient, you may not use, disclose, copy or disseminate this information. Please call the sender immediately or reply by email and destroy all copies of the original message, including attachments.