You can use puppet if you are already using puppet for OS to install and patch
the Oracle database.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Tiwari, Yogesh (Redacted sender "Yogesh.Tiwari" for DMARC)
Sent: Friday, August 14, 2020 5:22 AM
To: frankagordon@xxxxxxxxx; dimensional.dba@xxxxxxxxxxx
Cc: nenad.noveljic@xxxxxxxxxxxx; ORACLE-L <oracle-l@xxxxxxxxxxxxx>; Tiwari,
Yogesh <Yogesh.Tiwari@xxxxxxxxxxxxxx>
Subject: Re: automating database creation
We have over 1000 dbs.
1. Shell scripts, ansible. I’d *not* suggest to use ansible to run
installer etc. Keep these in shell script. It saves time, if you have to
troubleshoot. Debugging in shell is comparatively 10 times less text(and easy)
than what you need to write in ansible.
2. We did it from scratch. Here are a few pointers that you may consider.
a. Use ansible only for root specific actions. User creation, filesystem
setup, package install etc
b. Call shell scripts that can run locally on the db hosts. And just use
their exit code to determine next course of action.
c. Create gold images of binaries.
d. Create gold image of database backup for each version. Saves everything
you do in step 3(to be done once at build engg time only).
e. Move to OEM agent gold image install
f. Register OEM targets for both DB, and GI at install time.
g. Use control M API to create smart folder, jobs etc. if you use control.
h. If you have CMDB, and it gives APIs. Use it to register stuff in it at
the build time. Or use OEM custom “udf” and info about DB/GI etc there.
i. If you also create standby as part of build. Consider roleswap testing
as part of it.
j. Standardize init params as part of build process.
k. Make features like unified audit, read-only oracle home part of build
process.
l. Use SRVCTL setenv feature
m. Use ADRCI as part of build setup for log Purge etc.
n. Do all of the above for Grid infrastructure(or RAC) install as well.
o. Create build categories like BRONZE, SILVER, GOLD etc and club capacity
and features together.
3. Ditch dbca. It installs load of stuff you wont need, and will
eventually to add to – patching requirements, component upgrades, longer db
upgrade times, comp specific bugs.
a. Strip to bare min. catalog.sql, catproc.sql, catblock.sql,
catblock.sql, pupbld.sql, hlpbld.sql
b. Anything more than this, should be a custom requirement for each
application.
Hope this helps.
Thanks,
Yogi
Disclaimer: The information transmitted is intended for the person or entity to
which it is addressed and may contain confidential, privileged or copyrighted
material or attorney work product. If you receive this in error, please contact
the sender and delete the material from any system. Any unauthorised copying,
disclosure or distribution of the material in this e-mail is strictly
forbidden. Any comments or statements made are not necessarily those of
Fidelity. All e-mails may be monitored or recorded.
From: <oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> >
on behalf of Frank Gordon <frankagordon@xxxxxxxxx
<mailto:frankagordon@xxxxxxxxx> >
Reply to: "frankagordon@xxxxxxxxx <mailto:frankagordon@xxxxxxxxx> "
<frankagordon@xxxxxxxxx <mailto:frankagordon@xxxxxxxxx> >
Date: Friday, 14 August 2020 at 2:58 PM
To: "dimensional.dba@xxxxxxxxxxx <mailto:dimensional.dba@xxxxxxxxxxx> "
<dimensional.dba@xxxxxxxxxxx <mailto:dimensional.dba@xxxxxxxxxxx> >
Cc: "nenad.noveljic@xxxxxxxxxxxx <mailto:nenad.noveljic@xxxxxxxxxxxx> "
<nenad.noveljic@xxxxxxxxxxxx <mailto:nenad.noveljic@xxxxxxxxxxxx> >, ORACLE-L
<oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> >
Subject: Re: automating database creation
~1,500 databases.
1. How did you automate database creation?
Shell scripts, bash and around 15 database tables. that allowed us to generate
the Control-M files for scheduling RMAN and the configuration files for TSM
2. What would you do differently if you‘d build the solution from scratch again?
Give a bit more flexability on the scheduling RMAN side.
3. If you use dbca, what kind of templates do you use?
General Purpose template
Regards,
Frank
On Thu, Aug 13, 2020 at 12:49 PM <dimensional.dba@xxxxxxxxxxx
<mailto:dimensional.dba@xxxxxxxxxxx> > wrote:
1. How did you automate database creation?
Custom perl, python, go, or automation frameworks puppet, chef, ansible and OEM
take your pick of your poison as to custom language or automation framework
2. What would you do differently if you‘d build the solution from scratch
again?
Would probably stick with less custom in building a framework along with the
automation and use the prebuilt frameworks.
3. If you use dbca, what kind of templates do you use?
Created custom templates matching company specific requirements or custom gold
images of a database when there was lots of internal packages to deploy.
From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> > On
Behalf Of Noveljic Nenad
Sent: Thursday, August 13, 2020 3:21 AM
To: ORACLE-L (oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> )
<oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> >
Subject: automating database creation
Questions to teams responsible for 100+ databases:
1. How did you automate database creation?
2. What would you do differently if you‘d build the solution from scratch
again?
3. If you use dbca, what kind of templates do you use?
Best regards,
Nenad
https://nenadnoveljic.com/blog/about/ ;
<https://urldefense.com/v3/__https:/nenadnoveljic.com/blog/about/__;!!GvC3Dl69FG1X3k3XzQ!KZ-YtPjOpVdKpz3XqsB6VQJHXbGyHr_h57YFQFFviDiZM22g94_c6JpozP7S4lBodw$>
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee you
should in particular not disseminate, distribute, modify or copy this e-mail.
Please notify the sender immediately by e-mail, if you have received this
message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall
prevail in any case, we take it as your authorization to correspond with you by
e-mail if you send us messages by e-mail. However, we reserve the right not to
execute orders and instructions transmitted by e-mail at any time and without
further explanation.
E-mail transmission may not be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of Vontobel
Holding Ltd. and any of its affiliates (hereinafter collectively referred to as
"Vontobel Group") for any damages resulting from e-mail use is excluded. You
are advised that urgent and time sensitive messages should not be sent by
e-mail and if verification is required please request a printed version. Please
note that all e-mail communications to and from the Vontobel Group are subject
to electronic storage and review by Vontobel Group. Unless stated to the
contrary and without prejudice to any contractual agreements between you and
Vontobel Group which shall prevail in any case, e-mail-communication is for
informational purposes only and is not intended as an offer or solicitation for
the purchase or sale of any financial instrument or as an official confirmation
of any transaction.
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your consent
to forward you commercial communications. You can exercise, at any time and
under the terms established under current regulation, your rights. If you
prefer not to receive any further communications, please contact your client
relationship manager if you are a client of Vontobel Group or notify the
sender. Please note for an exact reference to the affected group entity the
corporate e-mail signature. For further information about data privacy at
Vontobel Group please consult www.vontobel.com
<https://urldefense.com/v3/__https:/www.vontobel.com__;!!GvC3Dl69FG1X3k3XzQ!KZ-YtPjOpVdKpz3XqsB6VQJHXbGyHr_h57YFQFFviDiZM22g94_c6JpozP4nBSHPQg$>
.
--
+353-86-0695383
