Introdução
Neste post faremos a instalação dos softwares Oracle Grid Infrastructure e Oracle Database em um novo servidor chamado lab01, que tem apenas o sistema operacional e os pacotes de pré-install do Oracle Database 19c. O servidor também já tem um disco formatado com asmlib e com o nome DATA1. Ao final, também é demonstrado um exemplo de provisionamento do Oracle Database Software em um servidor com FPP Client configurado.
Cada instalação realizada com Fleet Patching & Provisioning é chamada de Working Copy, uma Working Copy é um Oracle Home gerenciado pelo FPP Server e ele mantém a informação de cada Working Copy em seu catálogo, isso simplifica futuras ações do FPP, como criar Database, aplicar patches e realizar upgrades.
Provisionando Grid Infrastructure Software
Para criarmos uma Working Copy (provisionar uma nova instalação de software Oracle), usamos o comando rhpctl add workincopy.
Verificação inicial do servidor lab01 (FPP Target)
Vejam que não há nenhuma instância no ar, não existe o /etc/oratab e não temos nada no /u01.
[root@lab01 ~]# ps -ef | grep pmon root 2154 2123 0 20:10 pts/0 00:00:00 grep --color=auto pmon [root@lab01 ~]# [root@lab01 ~]# cat /etc/oratab cat: /etc/oratab: No such file or directory [root@lab01 ~]# [root@lab01 ~]# [root@lab01 ~]# ls -lrt /u01/ total 0 [root@lab01 ~]#
Disco DATA1 já formatado com asmlib:
[root@lab01 ~]# oracleasm querydisk DATA1 Disk "DATA1" is a valid ASM disk [[root@lab01 ~]# oracleasm querydisk DATA1 Disk "DATA1" is a valid ASM disk [root@lab01 ~]# [root@lab01 ~]# ls -l /dev/oracleasm/disks/DATA1 brw-rw---- 1 grid asmadmin 8, 33 Jul 15 17:08 /dev/oracleasm/disks/DATA1
Para provisionar o Grid Infrastructure com FPP Server, precisamos de um Response File contendo as informações básicas para a instalação e configuração do Oracle Restart (ou do Oracle Clusterware quando for Cluster).
Abaixo o response file utilizado:
[grid@fppserver01 ~]$ cat /tmp/response_gi19c.rsp oracle.install.responseFileVersion=/oracle/install/rspfmt_crsinstall_response_schema_v19.0.0 INVENTORY_LOCATION=/u01/app/oraInventory oracle.install.option=HA_CONFIG ORACLE_BASE=/u01/app/grid oracle.install.asm.OSDBA=oinstall oracle.install.asm.OSOPER=oinstall oracle.install.asm.OSASM=oinstall oracle.install.asm.SYSASMPassword=Dibiei@123 oracle.install.asm.diskGroup.name=DATA oracle.install.asm.diskGroup.redundancy=EXTERNAL oracle.install.asm.diskGroup.AUSize=4 oracle.install.asm.diskGroup.disks=/dev/oracleasm/disks/DATA1 oracle.install.asm.diskGroup.diskDiscoveryString=/dev/oracleasm/disks/* oracle.install.asm.monitorPassword=Dibiei@123
Note que não tem nada de especial nesse response file, é o mesmo utilizado para instalação em Silent Mode com Oracle Universal Installer (que é o que o Fleet Patching & Provisioning faz por baixo dos panos).
Verificando as Gold Images disponíveis no repositório do FPP Server:
[grid@fppserver01 ~]$ rhpctl query image fppserver01.dibiei.com: Audit ID: 45 Image name: gi19cR11 Image name: db19cR11 Image name: db12cR1 Image name: db19cR3
Vamos usar a gi19cR11:
[grid@fppserver01 ~]$ rhpctl query image -image gi19cR11 fppserver01.dibiei.com: Audit ID: 46 Image name: gi19cR11 Owner: grid@fppserver Site: fppserver Access control: USER:grid@fppserver Access control: ROLE:OTHER Access control: ROLE:GH_IMG_PUBLISH Access control: ROLE:GH_IMG_ADMIN Access control: ROLE:GH_IMG_VISIBILITY Parent Image: Software home path: /fpp_images/images/igi19cR11439597/.ACFS/snaps/igi19cR11/swhome Image state: PUBLISHED Image size: 10403 Megabytes Image Type: ORACLEGISOFTWARE Image Version: 19.0.0.0.0:19.11.0.0.0 Groups configured in the image: OSDBA=asmdba,OSASM=asmadmin,OSBACKUP=asmadmin,OSDG=asmadmin,OSKM=asmadmin,OSRAC=asmadmin Image platform: Linux_AMD64 Interim patches installed: 32585572,32584670,32579761,32576499,32545013 Contains a non-rolling patch: FALSE Complete: TRUE [grid@fppserver01 ~]$
Comando utilizado neste exemplo:
rhpctl add workingcopy -workingcopy wc_lab01_gi19cR11 -image gi19cR11 -targetnode lab01 -root -path /u01/app/product/19.11.0.0/grid -oraclebase /u01/app/grid -responsefile /tmp/response_gi19c.rsp -ignoreprereq
- –workingcopy – Especifica o nome da nova Working Copy sendo criada
- –image: Especifica o nome da Gold Image existente sendo usada como base para instalar o software (Grid)
- –targetnode: Nome do servidor onde estamos realizando a instalação do software
- –root: Especifica que o acesso SSH do FPP Server para o FPP Target (lab01) será realizado com usuário root
- –path: Indica o caminho completo onde o software será instalado (ORACLE_HOME)
- –oraclebase: Indica qual será o caminho do ORACLE_BASE
- –reponsefile: Indica o caminho do response file contendo os detalhes da instalação (esse arquivo fica no FPP Server)
Fazendo o deploy do Grid Infrastructure 19cR11 no servidor lab01:
[grid@fppserver01 ~]$ rhpctl add workingcopy -workingcopy wc_lab01_gi19cR11 -image gi19cR11 -targetnode lab01 -root -path /u01/app/product/19.11.0.0/grid -oraclebase /u01/app/grid -responsefile /tmp/response_gi19c.rsp -ignoreprereq Enter user "root" password: fppserver01.dibiei.com: Audit ID: 54 fppserver01.dibiei.com: Storing metadata in repository for working copy "wc_lab01_gi19cR11" ... fppserver01.dibiei.com: Creating snapshot "tmpgi19cR11wc_lab01_gi19cR11" ... fppserver01.dibiei.com: Changing the home ownership to user grid... fppserver01.dibiei.com: Copying software contents to Local File System ... fppserver01.dibiei.com: Starting clone operation... lab01: lab01: lab01: [INFO] [INS-32183] Use of clone.pl is deprecated in this release. Clone operation is equivalent to performing a Software Only installation from the image. lab01: You must use /u01/app/product/19.11.0.0/grid/gridSetup.sh script available to perform the Software Only install. For more details on image based installation, refer to help documentation. lab01: lab01: Starting Oracle Universal Installer... lab01: lab01: .................................................. 5% Done. lab01: .................................................. 10% Done. lab01: .................................................. 15% Done. lab01: .................................................. 20% Done. lab01: .................................................. 25% Done. lab01: .................................................. 30% Done. lab01: .................................................. 35% Done. lab01: .................................................. 40% Done. lab01: .................................................. 45% Done. lab01: .................................................. 50% Done. lab01: .................................................. 55% Done. lab01: .................................................. 60% Done. lab01: .................................................. 65% Done. lab01: .................................................. 70% Done. lab01: .................................................. 75% Done. lab01: .................................................. 80% Done. lab01: .................................................. 85% Done. lab01: .......... lab01: Copy files in progress. lab01: lab01: Copy files successful. lab01: lab01: Link binaries in progress. lab01: .......... lab01: Link binaries successful. lab01: lab01: Setup files in progress. lab01: .......... lab01: Setup files successful. lab01: lab01: Setup Inventory in progress. lab01: lab01: Setup Inventory successful. lab01: .......... lab01: Finish Setup successful. lab01: The cloning of wc_lab01_gi19cR11 was successful. lab01: Please check '/u01/app/oraInventory/logs/cloneActions2021-07-15_09-19-08PM.log' for more details. lab01: lab01: Setup Oracle Base in progress. lab01: lab01: Setup Oracle Base successful. lab01: .................................................. 95% Done. lab01: lab01: As a root user, execute the following script(s): lab01: 1. /u01/app/oraInventory/orainstRoot.sh lab01: 2. /u01/app/product/19.11.0.0/grid/root.sh lab01: lab01: lab01: lab01: .................................................. 100% Done. fppserver01.dibiei.com: Successfully executed clone operation. fppserver01.dibiei.com: Executing root script on nodes [lab01]. lab01: Changing permissions of /u01/app/oraInventory. lab01: Adding read,write permissions for group. lab01: Removing read,write,execute permissions for world. lab01: lab01: Changing groupname of /u01/app/oraInventory to oinstall. lab01: The execution of the script is complete. fppserver01.dibiei.com: Successfully executed root script on nodes [lab01]. fppserver01.dibiei.com: Executing configuration script on nodes [lab01] fppserver01.dibiei.com: Successfully executed configuration script on nodes [lab01] fppserver01.dibiei.com: Executing root script on nodes [lab01]. lab01: Check /u01/app/product/19.11.0.0/grid/install/root_lab01_2021-07-15_21-20-14-374354666.log for the output of root script fppserver01.dibiei.com: Successfully executed root script on nodes [lab01]. fppserver01.dibiei.com: Executing post configuration script on nodes [lab01] fppserver01.dibiei.com: Successfully executed post configuration script on nodes [lab01] fppserver01.dibiei.com: Oracle home provisioned. fppserver01.dibiei.com: Working copy creation completed.
Verificando a Instalação no Servidor lab01
Temos uma instância ASM no ar:
[grid@lab01 ~]$ ps -ef | grep pmon grid 24527 1 0 21:22 ? 00:00:00 asm_pmon_+ASM grid 27063 27370 0 21:54 pts/0 00:00:00 grep --color=auto pmon
Diskgroup DATA criado:
[grid@lab01 ~]$ asmcmd lsattr -G DATA -ml Group_Name Name Value RO Sys DATA access_control.enabled FALSE N Y DATA access_control.umask 066 N Y DATA appliance._partnering_type GENERIC Y Y DATA ate_conversion_done true Y Y DATA au_size 4194304 Y Y DATA cell.smart_scan_capable FALSE N N DATA cell.sparse_dg allnonsparse N N DATA compatible.advm 19.0.0.0.0 N Y DATA compatible.asm 19.0.0.0.0 N Y DATA compatible.rdbms 10.1.0.0.0 N Y DATA content.check FALSE N Y DATA content.type data N Y DATA content_hardcheck.enabled FALSE N Y DATA disk_repair_time 12.0h N Y DATA failgroup_repair_time 24.0h N Y DATA idp.boundary auto N Y DATA idp.type dynamic N Y DATA logical_sector_size 512 N Y DATA maxblkdump_content.check 3 N Y DATA maxdump_content.check 64 N Y DATA maxerr_content.check 1024 N Y DATA phys_meta_replicated true Y Y DATA preferred_read.enabled FALSE N Y DATA scrub_async_limit 1 N Y DATA scrub_metadata.enabled TRUE N Y DATA sector_size 512 N Y DATA thin_provisioned FALSE N Y DATA vam_migration_done false Y Y
Status dos recursos do Grid Infrastructure:
[grid@lab01 ~]$ crsctl stat res -t
--------------------------------------------------------------------------------
Name Target State Server State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
ONLINE ONLINE lab01 STABLE
ora.LISTENER.lsnr
ONLINE ONLINE lab01 STABLE
ora.asm
ONLINE ONLINE lab01 Started,STABLE
ora.ons
OFFLINE OFFLINE lab01 STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
1 ONLINE ONLINE lab01 STABLE
ora.diskmon
1 OFFLINE OFFLINE STABLE
ora.evmd
1 ONLINE ONLINE lab01 STABLE
--------------------------------------------------------------------------------
[grid@lab01 ~]$
Patches aplicados no Grid Home:
[grid@lab01 ~]$ $ORACLE_HOME/OPatch/opatch lspatches 32585572;DBWLM RELEASE UPDATE 19.0.0.0.0 (32585572) 32584670;TOMCAT RELEASE UPDATE 19.0.0.0.0 (32584670) 32579761;OCW RELEASE UPDATE 19.11.0.0.0 (32579761) 32576499;ACFS RELEASE UPDATE 19.11.0.0.0 (32576499) 32545013;Database Release Update : 19.11.0.0.210420 (32545013) OPatch succeeded. [grid@lab01 ~]$
Então concluímos que o Grid foi instalado e configurado com sucesso no servidor lab01.
Pesquisando a Working Copy no repositório do FPP Server. O comando “rhpctl query workincopy” lista todas as workingcopy criadas pelo FPP Server:
[grid@fppserver01 ~]$ rhpctl query workingcopy fppserver01.dibiei.com: Audit ID: 55 Working copy name: wc_lab01_gi19cR11
Usando a opção -workingcopy e passando o nome da nossa Working Copy, temos os detalhes da mesma:
[grid@fppserver01 ~]$ rhpctl query workingcopy -workingcopy wc_lab01_gi19cR11 fppserver01.dibiei.com: Audit ID: 56 Working copy name: wc_lab01_gi19cR11 Image name: gi19cR11 Groups configured in the working copy: OSDBA=oinstall,OSOPER=oinstall,OSASM=oinstall Owner: grid@ORACLERESTART_lab01 Site: ORACLERESTART_lab01 Access control: USER:grid@ORACLERESTART_lab01 Access control: USER:grid@fppserver Access control: ROLE:GH_WC_ADMIN Software home path: /u01/app/product/19.11.0.0/grid Storage type: LOCAL Image Type: ORACLEGISOFTWARE Software only: false Gold image path: Work path: Cluster Name: ORACLERESTART_lab01 Cluster Type: Cluster Mode: Cluster Class: Cluster Nodes: All patches available in this home: Additional patches compared to the image: Additional bug fixes that are not in the image: Complete: TRUE
Provisionando Oracle Database Software
Para provisionar uma instalação do Oracle Database, usamos um comando similiar ao que utilizamos para provisionar o Grid, com algumas diferenças:
- Não utilizamos a opção -responsefile
- Usamos a opção -user para indicar o usuário de SO que será owner da instalação do Database
O comando utilizado neste exemplo:
rhpctl add workingcopy -workingcopy wc_lab01_db19cR11 -image db19cR11 -targetnode lab01 -root -path /u01/app/oracle/product/19.11.0.0/db_1 -user oracle -oraclebase /u01/app/oracle
Fazendo o deploy do Oracle Database 19c11 no servidor lab01:
[grid@fppserver01 ~]$ rhpctl add workingcopy -workingcopy wc_lab01_db19cR11 -image db19cR11 -targetnode lab01 -root -path /u01/app/oracle/product/19.11.0.0/db_1 -user oracle -oraclebase /u01/app/oracle Enter user "root" password: fppserver01.dibiei.com: Audit ID: 59 fppserver01.dibiei.com: Option storagetype is set to the following default value: LOCAL. fppserver01.dibiei.com: Storing metadata in repository for working copy "wc_lab01_db19cR11" ... fppserver01.dibiei.com: Connecting to node lab01 ... fppserver01.dibiei.com: Starting transfer for remote copy ... fppserver01.dibiei.com: Starting clone operation... fppserver01.dibiei.com: Using inventory file /etc/oraInst.loc to clone ... lab01: lab01: lab01: [INFO] [INS-32183] Use of clone.pl is deprecated in this release. Clone operation is equivalent to performing a Software Only installation from the image. lab01: You must use /u01/app/oracle/product/19.11.0.0/db_1/runInstaller script available to perform the Software Only install. For more details on image based installation, refer to help documentation. lab01: lab01: Starting Oracle Universal Installer... lab01: lab01: You can find the log of this install session at: lab01: /u01/app/oraInventory/logs/cloneActions2021-07-15_11-21-40PM.log lab01: .................................................. 5% Done. lab01: .................................................. 10% Done. lab01: .................................................. 15% Done. lab01: .................................................. 20% Done. lab01: .................................................. 25% Done. lab01: .................................................. 30% Done. lab01: .................................................. 35% Done. lab01: .................................................. 40% Done. lab01: .................................................. 45% Done. lab01: .................................................. 50% Done. lab01: .................................................. 55% Done. lab01: .................................................. 60% Done. lab01: .................................................. 65% Done. lab01: .................................................. 70% Done. lab01: .................................................. 75% Done. lab01: .................................................. 80% Done. lab01: .................................................. 85% Done. lab01: .......... lab01: Copy files in progress. lab01: lab01: Copy files successful. lab01: lab01: Link binaries in progress. lab01: .......... lab01: Link binaries successful. lab01: lab01: Setup files in progress. lab01: .......... lab01: Setup files successful. lab01: lab01: Setup Inventory in progress. lab01: lab01: Setup Inventory successful. lab01: .......... lab01: Finish Setup successful. lab01: The cloning of wc_lab01_db19cR11 was successful. lab01: Please check '/u01/app/oraInventory/logs/cloneActions2021-07-15_11-21-40PM.log' for more details. lab01: lab01: Setup Oracle Base in progress. lab01: lab01: Setup Oracle Base successful. lab01: .................................................. 95% Done. lab01: lab01: As a root user, execute the following script(s): lab01: 1. /u01/app/oracle/product/19.11.0.0/db_1/root.sh lab01: lab01: lab01: lab01: .................................................. 100% Done. fppserver01.dibiei.com: Successfully executed clone operation. fppserver01.dibiei.com: Executing root script on nodes lab01. lab01: Check /u01/app/oracle/product/19.11.0.0/db_1/install/root_lab01_2021-07-15_23-22-42-749632257.log for the output of root script fppserver01.dibiei.com: Successfully executed root script on nodes lab01. fppserver01.dibiei.com: Working copy creation completed. [grid@fppserver01 ~]$
Após concluir o procedimento no FPP Server, podemos validar algumas informações no servidor lab01.
Patches aplicados no novo DB Home:
[oracle@lab01 ~]$ /u01/app/oracle/product/19.11.0.0/db_1/OPatch/opatch lspatches 32579761;OCW RELEASE UPDATE 19.11.0.0.0 (32579761) 32545013;Database Release Update : 19.11.0.0.210420 (32545013) OPatch succeeded. [oracle@lab01 ~]$
Consultando o Oracle Inventory no servidor lab01, vejam que o nome da Working Copy também é utilizado para identificar o Oracle Home dentro do Oracle Inventory:
[oracle@lab01 ~]$ cat /u01/app/oraInventory/ContentsXML/inventory.xml <?xml version="1.0" standalone="yes" ?> <!-- Copyright (c) 1999, 2021, Oracle and/or its affiliates. All rights reserved. --> <!-- Do not modify the contents of this file by hand. --> <INVENTORY> <VERSION_INFO> <SAVED_WITH>12.2.0.7.0</SAVED_WITH> <MINIMUM_VER>2.1.0.6.0</MINIMUM_VER> </VERSION_INFO> <HOME_LIST> <HOME NAME="wc_lab01_gi19cR11" LOC="/u01/app/product/19.11.0.0/grid" TYPE="O" IDX="1" CRS="true"/> <HOME NAME="wc_lab01_db19cR11" LOC="/u01/app/oracle/product/19.11.0.0/db_1" TYPE="O" IDX="2"/> </HOME_LIST> <COMPOSITEHOME_LIST> </COMPOSITEHOME_LIST> </INVENTORY> [oracle@lab01 ~]$
Especificando os Grupos de SO para a Instalação do Database Software
Pesquisando detalhes de Gold Image db19cR3:
[grid@fppserver01 ~]$ rhpctl query image -image db19cR3 fppserver01.dibiei.com: Audit ID: 61 Image name: db19cR3 Owner: grid@fppserver Site: fppserver Access control: USER:grid@fppserver Access control: ROLE:OTHER Access control: ROLE:GH_IMG_PUBLISH Access control: ROLE:GH_IMG_ADMIN Access control: ROLE:GH_IMG_VISIBILITY Parent Image: Software home path: /fpp_images/images/idb19cR3850023/.ACFS/snaps/idb19cR3/swhome Image state: PUBLISHED Image size: 6536 Megabytes Image Type: ORACLEDBSOFTWARE Image Version: 19.0.0.0.0:19.3.0.0.0 Groups configured in the image: OSDBA=dba,OSOPER=oper,OSBACKUP=backupdba,OSDG=dgdba,OSKM=kmdba,OSRAC=racdba Image platform: Linux_AMD64 Interim patches installed: 29585399,29517242 Contains a non-rolling patch: FALSE Complete: TRUE
Essa Gold Image está pré configurada com grupos do sistema operacional, porém não temos todos esses grupos criados no servidor lab01, então podemos sobreescrever essa configuração ao criar uma nova Working Copy a partir desta Gold Image.
No comando abaixo estou configurando todos os grupos como “dba”:
rhpctl add workingcopy -workingcopy lab01_wc_db19cR3 -image db19cR3 -targetnode lab01 -root -path /u01/app/oracle/product/19.3.0.0/db_1 -oraclebase /u01/app/oracle -user oracle -groups "OSDBA=dba,OSOPER=dba,OSBACKUP=dba,OSDG=dba,OSKM=dba,OSRAC=dba"
Provisionando o Oracle Database 19c com Release Update 3 no servidor lab01 e definindo os grupos do sistema operacional manualmente para a nova instalação:
[grid@fppserver01 ~]$ rhpctl add workingcopy -workingcopy lab01_wc_db19cR3 -image db19cR3 -targetnode lab01 -root -path /u01/app/oracle/product/19.3.0.0/db_1 -oraclebase /u01/app/oracle -user oracle -groups "OSDBA=dba,OSOPER=dba,OSBACKUP=dba,OSDG=dba,OSKM=dba,OSRAC=dba" Enter user "root" password: fppserver01.dibiei.com: Audit ID: 63 fppserver01.dibiei.com: Option storagetype is set to the following default value: LOCAL. fppserver01.dibiei.com: Storing metadata in repository for working copy "lab01_wc_db19cR3" ... fppserver01.dibiei.com: Connecting to node lab01 ... fppserver01.dibiei.com: Starting transfer for remote copy ... fppserver01.dibiei.com: Starting clone operation... fppserver01.dibiei.com: Using inventory file /etc/oraInst.loc to clone ... lab01: lab01: lab01: [INFO] [INS-32183] Use of clone.pl is deprecated in this release. Clone operation is equivalent to performing a Software Only installation from the image. lab01: You must use /u01/app/oracle/product/19.3.0.0/db_1/runInstaller script available to perform the Software Only install. For more details on image based installation, refer to help documentation. lab01: lab01: Starting Oracle Universal Installer... lab01: lab01: You can find the log of this install session at: lab01: /u01/app/oraInventory/logs/cloneActions2021-07-18_08-27-55PM.log lab01: .................................................. 5% Done. lab01: .................................................. 10% Done. lab01: .................................................. 15% Done. lab01: .................................................. 20% Done. lab01: .................................................. 25% Done. lab01: .................................................. 30% Done. lab01: .................................................. 35% Done. lab01: .................................................. 40% Done. lab01: .................................................. 45% Done. lab01: .................................................. 50% Done. lab01: .................................................. 55% Done. lab01: .................................................. 60% Done. lab01: .................................................. 65% Done. lab01: .................................................. 70% Done. lab01: .................................................. 75% Done. lab01: .................................................. 80% Done. lab01: .................................................. 85% Done. lab01: .......... lab01: Copy files in progress. lab01: lab01: Copy files successful. lab01: lab01: Link binaries in progress. lab01: .......... lab01: Link binaries successful. lab01: lab01: Setup files in progress. lab01: .......... lab01: Setup files successful. lab01: lab01: Setup Inventory in progress. lab01: lab01: Setup Inventory successful. lab01: .......... lab01: Finish Setup successful. lab01: The cloning of lab01_wc_db19cR3 was successful. lab01: Please check '/u01/app/oraInventory/logs/cloneActions2021-07-18_08-27-55PM.log' for more details. lab01: lab01: Setup Oracle Base in progress. lab01: lab01: Setup Oracle Base successful. lab01: .................................................. 95% Done. lab01: lab01: As a root user, execute the following script(s): lab01: 1. /u01/app/oracle/product/19.3.0.0/db_1/root.sh lab01: lab01: lab01: lab01: .................................................. 100% Done. fppserver01.dibiei.com: Successfully executed clone operation. fppserver01.dibiei.com: Executing root script on nodes lab01. lab01: Check /u01/app/oracle/product/19.3.0.0/db_1/install/root_lab01_2021-07-18_20-28-47-548402726.log for the output of root script fppserver01.dibiei.com: Successfully executed root script on nodes lab01. fppserver01.dibiei.com: Working copy creation completed.
Provisionando em FPP Target com FPP Client Configurado
Conforme demonstrado em posts anteriores, quando temos um FPP Client configurado, não precisamos informar os dados de acesso SSH, informamos apenas o nome do cluster no qual o FPP Client foi configurado. Mas outra possibilidade quando temos um FPP Client é executar os comandos diretamente do servidor com FPP Client configurado (ao invés de ter que acessar o FPP Server), conforme veremos no próximo exemplo.
Conectado no servidor lab03, verificamos o status do FPP Client:
[grid@lab03 ~]$ srvctl status rhpclient Rapid Home Provisioning Client is enabled Rapid Home Provisioning Client is running on node lab03
A partir do FPP Client podemos executar os mesmos comandos que executamos no FPP Server, o FPP Client consulta o repositório do FPP Server. Abaixo estamos verificando as Gold Images disponíveis no FPP Server:
[grid@lab03 ~]$ rhpctl query image fppserver01.dibiei.com: Audit ID: 84 Image name: gi19cR11 Image name: db19cR11 Image name: db12cR1 Image name: db19cR3
Obtendo detalhes da Gold Image db12cR1:
[grid@lab03 ~]$ rhpctl query image -image db12cR1 fppserver01.dibiei.com: Audit ID: 85 Image name: db12cR1 Owner: grid@fppserver Site: fppserver Access control: USER:grid@fppserver Access control: ROLE:OTHER Access control: ROLE:GH_IMG_PUBLISH Access control: ROLE:GH_IMG_ADMIN Access control: ROLE:GH_IMG_VISIBILITY Parent Image: Software home path: /fpp_images/images/idb12cR1992231/swhome Image state: PUBLISHED Image size: 10677 Megabytes Image Type: ORACLEDBSOFTWARE Image Version: 12.1.0.2.0 Groups configured in the image: OSDBA=dba,OSBACKUP=dba,OSDG=dba,OSKM=dba Image platform: Linux_AMD64 Interim patches installed: 23285312 Contains a non-rolling patch: FALSE Complete: TRUE
Provisionando o Oracle Database Software 12cR1 no servidor lab03.
[grid@lab03 ~]$ rhpctl add workingcopy -workingcopy lab03_wc_db12cR1 -image db12cR1 -path /u01/app/oracle/product/12.1.0.2/db_1 -user oracle -oraclebase /u01/app/oracle
fppserver01.dibiei.com: Audit ID: 81
lab03.dibiei.com: Option storagetype is set to the following default value: LOCAL.
lab03.dibiei.com: Starting server-side action for 'add workingcopy'...
fppserver01.dibiei.com: Adding storage for working copy ...
fppserver01.dibiei.com: Storing metadata in repository for working copy "lab03_wc_db12cR1" ...
lab03.dibiei.com: Server-side action completed.
lab03.dibiei.com: Making a local copy ...
lab03.dibiei.com: Changing the home ownership to user oracle and group oinstall...
lab03.dibiei.com: Starting clone operation...
========================================
lab03.dibiei.com:
./runInstaller -clone -waitForCompletion -force "ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/db_1" "ORACLE_HOME_NAME="lab03_wc_db12cR1"" "ORACLE_BASE="/u01/app/oracle"" "CLUSTER_NODES={lab03}" "oracle_install_OSDBA=dba" "oracle_install_OSOPER=" "oracle_install_OSBKP=dba" "oracle_install_OSDGD=dba" "oracle_install_OSKMT=dba" -silent -paramFile /u01/app/oracle/product/12.1.0.2/db_1/clone/clone_oraparam.ini
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 500 MB. Actual 2315 MB Passed
Checking swap space: must be greater than 500 MB. Actual 2047 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2021-07-18_09-43-22PM. Please wait ...You can find the log of this install session at:
/u01/app/oraInventory/logs/cloneActions2021-07-18_09-43-22PM.log
.................................................. 5% Done.
.................................................. 10% Done.
.................................................. 15% Done.
.................................................. 20% Done.
.................................................. 25% Done.
.................................................. 30% Done.
.................................................. 35% Done.
.................................................. 40% Done.
.................................................. 45% Done.
.................................................. 50% Done.
.................................................. 55% Done.
.................................................. 60% Done.
.................................................. 65% Done.
.................................................. 70% Done.
.................................................. 75% Done.
.................................................. 80% Done.
.................................................. 85% Done.
..........
Copy files in progress.
Copy files successful.
Link binaries in progress.
Link binaries successful.
Setup files in progress.
Setup files successful.
Setup Inventory in progress.
Setup Inventory successful.
Finish Setup successful.
The cloning of lab03_wc_db12cR1 was successful.
Please check '/u01/app/oraInventory/logs/cloneActions2021-07-18_09-43-22PM.log' for more details.
Setup Oracle Base in progress.
Setup Oracle Base successful.
.................................................. 95% Done.
As a root user, execute the following script(s):
1. /u01/app/oracle/product/12.1.0.2/db_1/root.sh
Execute /u01/app/oracle/product/12.1.0.2/db_1/root.sh on the following nodes:
[lab03]
.................................................. 100% Done.
lab03.dibiei.com: Successfully executed clone operation.
lab03.dibiei.com: Executing root script on nodes lab03.
lab03.dibiei.com: Successfully executed root script on nodes lab03.
lab03.dibiei.com: Working copy creation completed.
Conclusão
Este post apresentou exemplos de como utilizar as Gold Images criadas no Fleet Patching & Provisioning para criar novas instalações do Oracle Grid Infrastructure e Oracle Database, abordando desde de a instalação em um novo servidor, até exemplo com FPP Client previamente configurado.
No próximo post demonstrarei como criar Databases, aplicar patch e realizar upgrades do Oracle Database com Fleet Patching and Provisioning.