- Time is running out to save up to $660 on COLLABORATE 18 – IOUG Forum! Remember: when you register with your team of four or more, everyone receives an additional group rate discount of $250. There’s no better price for a week packed with Oracle training – plan to connect with product experts and like-minded users in April, and register for the best savings! http://collaborate.ioug.org/register#
- Hope to see you in Las Vegas
Its gonna be a busy 2nd quarter as i I am privileged and honored to speak at Collaborate – #C18LV in Las Vegas, Great Lakes Oracle Conference – #GLOC18 in Cleveland and ODTUG KSCOPE18 – #ODTUG in Orlando
I will be presenting at Collaborate(Papers Posted at Collaborate and This site).
Migration of data to the Cloud – #1169 – Jasmine E => Tue, Apr 24, 2018 (01:15 PM – 02:15 PM)
Upgrading to the Cloud – tales from the battlefield – #1170 – Jasmine F => Mon, Apr 23, 2018 (11:00 AM – 12:00 PM)
A Case Study of Oracle Database Upgrade and Consolidation – #1435 – Banyan C => Wed, Apr 25, 2018 (02:30 PM – 03:30 PM)
Great Lakes Oracle Conference (GLOC) –
To CDB or not to CDB, That is the question ? Multitenet option explained…
Thanks to all the conference organizers for allowing me to present these topics and share my experiences.
Note – Both presentations will be online in first part of April.
Come join Oracle ACE Directors, Charles Kim and Rich Niemiec as he speaks about his favorite new features on Oracle Database 12c Release 2 (12cR2), 18c. Oracle professionals fret about their future and the state of direction for the industry. Learn how you can prepare to evolve and adapt to the Changing Role of the DBA with Oracle 12cR2 and 18c as we discuss pertinent new features to help innovate at a time when companies must change to survive. Through this half-day, interactive deep-dive, you will learn upgrade approaches, methods, and best practices for a successful upgrade to Oracle 12cR2 as 11gR2 is going off of error-correction support in 2018. Happy Hour to follow from 5:00pm-7:00pm
TO REGISTER – http://tips.viscosityna.com/techdaydetroit/
Here is my updated presentation for upgrading to 12.2. Please contact me with any questions.
I was privileged to be a speaker at the Rocky Mountain training days #td17 on the topic of “Automagically” Deploying EM12c Agents and Mass promotion of targets once the hosts have been added.
The presentation is attached, but in a nut shell, using EM12C’s RPM generation and using Puppet we are able to push out agents, the moment the machines are built and validated.
The first step is to log into the OMS machine and generate the RPM using EMCLI (After logging into emcli )
> emcli get_supported_platforms <== This will get the information for building the RPM’s
> emcli get_agentimage_rpm -destination=/tmp -platform=”Linux x86-64″ -version=”220.127.116.11.0″
This last command will generate a RPM in the /tmp directory called: “oracle-agt-18.104.22.168.0-1.0.x86_64.rpm” << notice the version # and platform in the name
Now that the RPM is ready, we use Puppet to copy and to install the RPM on new machines.
A few notes about puppet installs with RPMS
- We use a standard location / directory
- Only run if the standard location is NOT in place
- Only run if “emwd.pl” is not in place
- Verifies the correct ownership of the directories
- Uses oraInventory for location
There are 2 steps for the puppet process
- apply RPM – >> rpm -ivh oracle-agt-22.214.171.124.0-1.0.x86_64.rpm
- create agent.properties file – With host name, default password, etc.
- run – /etc/init.d/oracle-agt RESPONSE_FILE=/usr/lib/oracle/agent/agent.properties
- When Step 3 finishes, there should be a new OMS entry for that host and connected to the OMS.
Last step – Just added recently – (Not part of presentation) is to perform a mass promotion of non-host targets like databases, listeners, etc.
Mass Promote code is in GIT Hub – https://github.com/harry2040/OEM12cMassPromote
Thanks again to #td17 for a great conference and the opportunity.
How many people have received letters from Oracle that have stated that partitioning and / or Fine-grained auditing were turned on for Oracle 12C and they had to remove it otherwise pay a higher license fee or penalties. Well if you haven’t, your lucky as many customers have received this kind of letter, recently.
Well many have received the notice and then recompiled/de-installed the partitioning and/or fine grain auditing option on the databases that have contained a RMAN catalog user/schema.
When they removed the partition and/or the fine grain auditing and tried to upgrade the RMAN Catalog for the new Oracle 12c databases you will get this error:
Recovery Manager: Release 126.96.36.199.0 - Production on Thu May 26 13:08:02 2016 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. RMAN> connect catalog catalog_user/PW@Database; connected to recovery catalog database PL/SQL package catalog_user.DBMS_BA version 12.01.00.02 in RCVCAT database is too old RMAN> upgrade catalog recovery catalog owner is catalog_user enter UPGRADE CATALOG command again to confirm catalog upgrade RMAN> upgrade catalog error creating create_deleted_object_seq RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-06004: ORACLE error from recovery catalog database: ORA-00439: feature not enabled: Partitioning RMAN-06004: ORACLE error from recovery catalog database: ORA-00439: feature not enabled: Fine-grained access control RMAN>
Well if you have received this error, I hope you have a backup of the database, as this will corrupt you RMAN catalog. Well at least it corrupted our RMAN catalog and many others.
New RMAN catalog – Oracle 188.8.131.52 requires Partitioning, fine-grained auditing and other Enterprise edition options. Per Mike Dietrich’s BLOG, Going forward with Oracle 12c, you need to use Enterprise Edition for RMAN or Infrastructure databases:
“A separate single instance Oracle Database can be installed and used as an infrastructure repository for RMAN, Oracle Enterprise Manager Cloud Control, Automatic Workload Repository (AWR) Warehouse, Global Data Services Catalog, and Grid Infrastructure Management Repository without additional license requirements, provided that all the targets are correctly licensed. It may not be used or deployed for other uses.”
#1 – the RMAN catalog must be in its OWN Oracle 184.108.40.206 EE database – no other applications – Partitions need to be included
#2 – DBMS_LOB and UTTL_HTTP Must be present
#3 – Execute this script before upgrading the catalog: SQL> @$ORACLE_HOME/rdbms/admin/dbmsrmansys.sql
#4 – no Partitioning license required
#5 – Make sure you have a backup
#6 – p20432873_121020_Generic.zip – is a patch to fix the corrupted RMAN catalog due to Oracle 12c requirement – basically its a different recover.bsq script to fix the corruption. – This is only if its currently corrupted. One of the few bugs, that i was able to create an actually see a patch created for it – thank you Oracle.
#7 – See MOS Note:1927265.1 – this has more information
Please review Mike Dietrich’s Blog above regarding licenses and more information – https://blogs.oracle.com/UPGRADE/entry/rman_catalog_requires_ee_in
Hope this helps. Again, please backup your rman catalog before upgrading .