Instalación de Oracle Clusterware y Oracle RDBMS 19c en modo Silent

#OracleACEAssociate

#OracleTIPSSV

10 de Agosto de 2023

Raúl Antonio Molina Alvarenga

El objetivo de este articulo no es preparar todos los pasos previos para instalar un cluster, en realidad lo enfoque solo los comandos importantes en la instalación siguiendo el modo que mas me provoca al momento de instalar: MODO NO INTERACTIVO o MODO SILENT.

Procedamos con una hojeada al concepto de Modo Silencioso.

Todos conocemos el famoso instalador de los productos Oracle, el OUI u Oracle Universal Installer, un Software integrado construido en JAVA y con un complemento de scripts en otras lenguajes de programación que Oracle ocupa que permite instalar los productos Oracle en cualquier plataforma; este software permite realizar dicha tarea en forma interactiva.

Ese Instalador puede considerarse pesado o lento en algunas circunstancias, como por ejemplo usarlo via VPN , desde sitios remotos.

La alternativa a dichas situaciones o escenarios, el modo No Interactivo o Silencioso, este modo utiliza el mismo Instalador, solo que no de forma interactivo si no que requiere que se provean todas las respuestas que el programa requiere.

Las respuestas pueden ser puestas en lote en la linea de comandos (lo cual no recomiendo), o usando un archivo de respuesta, o responseFile ( recomendado).

El archivo de respuesta puede obtenerse de 2 formas, el propio instalador tiene algunas plantillas ya incluidas, por ejemplo propio OUI, DBCA, NETCA.

Otra forma es generarlo ejecutando el propio instalador y guardarlo como se muestra en la imagen:

Nuestro archivo de respuesta quedaría de la siguiente forma:

oracle.install.responseFileVersion=/oracle/install/rspfmt_crsinstall_response_schema_v19.0.0

INVENTORY_LOCATION=/u01/app/oraInventory

oracle.install.option=CRS_CONFIG

ORACLE_BASE=/u01/app/grid

oracle.install.asm.OSDBA=oinstall

oracle.install.asm.OSOPER=

oracle.install.asm.OSASM=asmadmin

oracle.install.crs.config.scanType=LOCAL_SCAN

oracle.install.crs.config.gpnp.scanName=rac-scan

oracle.install.crs.config.gpnp.scanPort=1521

oracle.install.crs.config.ClusterConfiguration=STANDALONE

oracle.install.crs.config.configureAsExtendedCluster=false

oracle.install.crs.config.clusterName=rac-cluster

oracle.install.crs.config.gpnp.configureGNS=false

oracle.install.crs.config.autoConfigureClusterNodeVIP=false

oracle.install.crs.config.clusterNodes=nodo1:nodo1-vip,nodo2:nodo2-vip

oracle.install.crs.config.networkInterfaceList=eno16780032:192.168.51.0:1,eno33559296:10.20.0.0:5

oracle.install.crs.configureGIMR=false

oracle.install.asm.configureGIMRDataDG=false

oracle.install.crs.config.storageOption=FLEX_ASM_STORAGE

oracle.install.asm.SYSASMPassword=Oracle123

oracle.install.asm.diskGroup.name=OCR

oracle.install.asm.diskGroup.redundancy=NORMAL

oracle.install.asm.diskGroup.AUSize=4

oracle.install.asm.diskGroup.disksWithFailureGroupNames=ORCL:ASM1,,ORCL:ASM2,,ORCL:ASM3,

oracle.install.asm.diskGroup.disks=ORCL:ASM1,ORCL:ASM2,ORCL:ASM3

oracle.install.asm.diskGroup.diskDiscoveryString=ORCL:*

oracle.install.asm.monitorPassword=Oracle123

oracle.install.asm.gimrDG.AUSize=1

oracle.install.asm.configureAFD=false

oracle.install.crs.configureRHPS=false

oracle.install.crs.config.ignoreDownNodes=false

oracle.install.config.managementOption=NONE

oracle.install.crs.rootconfig.executeRootScript=false

Una vez tenemos definido su contenido, podemos preparar la equivalencia de usuarios en una capa o dos , si vamos a tener Separación de usuarios ( Role Separation Duties).

./sshUserSetup.sh -user grid -hosts “nodo1 nodo2” -noPromptPassphrase

./sshUserSetup.sh -user oracle -hosts “nodo1 nodo2” -noPromptPassphrase

Para ejecutar el instalador:

./gridSetup.sh -silent -waitForCompletion -ignorePrereqFailure -ignoreInternalDriverError -responseFile /home/grid/gi.rsp

Luego hay que estar atentos a las salidas, archivos de logs, salida en pantalla , etc etc.

Después prosigue instalar la capa de rdbms ( Proceder solo si la capa de GI fue satisfactoria).

La muestra de nuestro archivo de respuesta:

oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v19.0.0

oracle.install.option=INSTALL_DB_SWONLY

UNIX_GROUP_NAME=oinstall

INVENTORY_LOCATION=/u01/app/oraInventory

ORACLE_HOME=/u01/app/oracle/product/19.0.0/db_1

ORACLE_BASE=/u01/app/oracle

oracle.install.db.InstallEdition=EE

oracle.install.db.OSDBA_GROUP=oinstall

oracle.install.db.OSOPER_GROUP=oinstall

oracle.install.db.OSBACKUPDBA_GROUP=oinstall

oracle.install.db.OSDGDBA_GROUP=oinstall

oracle.install.db.OSKMDBA_GROUP=oinstall

oracle.install.db.OSRACDBA_GROUP=oinstall

oracle.install.db.rootconfig.executeRootScript=false

oracle.install.db.CLUSTER_NODES=nodo1,nodo2

Y como ultimo paso el lanzamiento del instalador:

./runInstaller  -silent -ignoreInternalDriverError -ignorePrereqFailure -responseFile /home/oracle/db_install.rsp 

Espero les sea de Utilidad.

Saludos!!

Mover Agente de Cloud (OH) de un folder a otro ( o Filesystem).

Raúl Antonio Molina Alvarenga

07 de Agosto de 2023

#OracleACEAssociate

Hola, un día me enfrente a la siguiente situación: Instale un agente de Cloud Control en la ruta equivocada.

Y se nos viene la idea, fácil, lo remueve y lo reinstalo.

Esto podrá ser fácil, pero si puede complicarse si la red es lenta, es un sitio remoto, etc etc.

Y si existe una forma mas fácil, porque no la ejecutamos?, bueno aquí veremos algo que para mi criterio resulta, más fácil.

Usaremos el DOCID:

Que nos provee el script:

ConvertToStandalone.pl

Hay que tener algunas consideraciones con la nota, hay que definir estas 2 variables de SO:

El Home no es el agent_inst es el $OH/core/Version12c
export OLD_AGENT_HOME=/oracle/agent12c/core/12.1.0.5.0
export ORACLE_HOME=/oracle/agent12c/core/12.1.0.5.0

Generamos el plugin list

$OLD_AGENT_HOME/perl/bin/perl /tfs/oracle/agent12c/core/12.1.0.5.0/sysman/install/create_plugin_list.pl -instancehome /tfs/oracle/agent12c/core/12.1.0.5.0

The agent Base Dir is /oracle/agent12c

 Creating file : /oracle/agent12c/rwFile

Removed the /oracle/agent12c/rwFile file.

oracle.sysman.xa|12.1.0.6.0||discoveryPlugin

oracle.sysman.db|12.1.0.8.0||discoveryPlugin

oracle.sysman.emas|12.1.0.8.0||discoveryPlugin

oracle.sysman.oh|12.1.0.5.0||discoveryPlugin

oracle.sysman.oh|12.1.0.5.0||agentPlugin
oracle.sysman.db|12.1.0.8.0||agentPlugin
/oracle/agent12c/plugins.txt
[oracle@nodo ~]$ 

Cambiar archivo agent12c/agentimage.properties  la ultima  linea

SBIN_MODIFIED_VERSION=12.1.0.5.0

$OLD_AGENT_HOME/perl/bin/perl  ConvertToStandalone.pl -instanceHome /oracle/agent12c/agent_inst -newAgentBaseDir /export/home/oracle/agent12c

OUTPUT

Migrating the agent home to different home

Validating the arguments

The log file is /oracle/agent12c/agent_inst/install/logs/convert/convertingtostandalone_2023-07-05_16-29-55.log

The agent image file Exists : /oracle/agent12c/agentimage.properties. Check for value of : VERSION

The current home is /oracle/agent12c/core/12.1.0.5.0Software only install of the agent bits

Home : /home/oracle/agent12c/core/12.1.0.5.0 already exist. Do you want to overwrite the home? Confirm (y/n)y

User confirmed for overwrite.

 The command is cp -r /oracle/agent12c/core /oracle/agent12c/plugins /oracle/agent12c/agentimage.properties /oracle/agent12c/plugins.txt /home/oracle/agent12c 

The command exitcode 0

The command is cp -r /oracle/agent12c/sbin /home/oracle/agent12c 

cp: cannot open ‘/oracle/agent12c/sbin/nmo’ for reading: Permission denied

cp: cannot open ‘/oracle/agent12c/sbin/nmhs’ for reading: Permission denied

cp: cannot open ‘/oracle/agent12c/sbin/nmb’ for reading: Permission denied

The command exitcode 256

Copying of /oracle/agent12c/sbinto /home/oracle/agent12c Failed

The command is /home/oracle/agent12c/core/12.1.0.5.0/oui/bin/runInstaller -clone -forceClone -silent -waitForCompletion -nowait ORACLE_HOME=/home/oracle/agent12c/core/12.1.0.5.0 -noconfig -force EM_PROTOCOL=https ORACLE_HOME_NAME=agent12c -invPtrLoc /oracle/agent12c/core/12.1.0.5.0/oraInst.loc AGENT_BASE_DIR=/home/oracle/agent12c 

The command exitcode 0

The command is /home/oracle/agent12c/core/12.1.0.5.0/oui/bin/runInstaller -attachHome -force -silent ORACLE_HOME=/home/oracle/agent12c/sbin ORACLE_HOME_NAME=sbin12c -waitForCompletion -invPtrLoc /oracle/agent12c/core/12.1.0.5.0/oraInst.loc 

The command exitcode 0

The command is /home/oracle/agent12c/core/12.1.0.5.0/oui/bin/runInstaller -updateHomeDeps -waitForCompletion HOME_DEPENDENCY_LIST={/home/oracle/agent12c/sbin:/home/oracle/agent12c/core/12.1.0.5.0} -invPtrLoc /oracle/agent12c/core/12.1.0.5.0/oraInst.loc  

The command exitcode 0

Converting the agent to standalone

The command is /oracle/agent12c/agent_inst/bin/emctl start blackout AGT_CNT_BLK_OUT -nodeLevel 

The command exitcode 0

The command is /oracle/agent12c/agent_inst/bin/emctl stop agent 

The command exitcode 0

The command is cp -r /oracle/agent12c/agent_inst/* /home/oracle/agent12c/agent_inst 

The command exitcode 0

The command is /home/oracle/agent12c/core/12.1.0.5.0/jdk/bin/java -jar /home/oracle/agent12c/core/12.1.0.5.0/jlib/updateStateDirectory.jar -migrateBase -emStateDir /home/oracle/agent12c/agent_inst -oldAgentHome /oracle/agent12c/core/12.1.0.5.0 -newAgentHome /home/oracle/agent12c/core/12.1.0.5.0 -oldAgentBase /oracle/agent12c -newAgentBase /home/oracle/agent12c 

The command exitcode 0

The command is /home/oracle/agent12c/agent_inst/bin/emctl setproperty agent -name agentStateDir -value /home/oracle/agent12c/agent_inst 

The command exitcode 0

The command is /home/oracle/agent12c/core/12.1.0.5.0/perl/bin/perl /home/oracle/agent12c/core/12.1.0.5.0/bin/AgentPluginDeploy.pl -oracleHome /home/oracle/agent12c/core/12.1.0.5.0 -agentDir /home/oracle/agent12c -pluginIdsInfoFile /home/oracle/agent12c/plugins.txt -action upgrade -emStateDir /home/oracle/agent12c/agent_inst -ignoreUnzip -dont_restart   

The command exitcode 0

The command is /home/oracle/agent12c/agent_inst/bin/emctl update_inventory plugin 

The command exitcode 0

The command is /home/oracle/agent12c/core/12.1.0.5.0/jdk/bin/java -jar /home/oracle/agent12c/core/12.1.0.5.0/jlib/upgradeCollections.jar -emStateDir /home/oracle/agent12c/agent_inst -newPluginXml /home/oracle/agent12c/core/12.1.0.5.0/sysman/admin/agentLib.xml -oldPluginXml /oracle/agent12c/core/12.1.0.5.0/sysman/admin/agentLib.xml 

log4j:ERROR No appenders could be found for category (oracle.sysman.gcagent.util.logging.ODLLogging).

log4j:ERROR Please initialize the log4j system properly.

The command exitcode 0

The command is /home/oracle/agent12c/agent_inst/bin/emctl start agent 

The command exitcode 0

The command is /home/oracle/agent12c/agent_inst/bin/emctl stop blackout AGT_CNT_BLK_OUT  

The command exitcode 0

The command is mv /oracle/agent12c/agent_inst/bin/emctl /oracle/agent12c/agent_inst/bin/emctl_converted 

The command exitcode 0

Move of File :  /oracle/agent12c/agent_inst/bin/emctl to File : /oracle/agent12c/agent_inst/bin/emctl_converted is successfully done

Modifying the oragchomelist to include the current agent home with the instancehome

The migration is completed Successfully. Run /home/oracle/agent12c/core/12.1.0.5.0/root.sh as root user manually.

Deinstall agent home /oracle/agent12c/core/12.1.0.5.0 manually.

[oracle@nodo ~]$ exit

logout

Ejecutamos el script de root de nuevo:

[root@nodo ~]# /home/oracle/agent12c/core/12.1.0.5.0/root.sh

Con esto el agente de movio de folder a un nuevo directorio.

Espero les sea de Utilidad

Saludos

Adenda de despliegue, cuando se debe forzar el HOSTNAME

EM 12c: Agent installation reports failure for Hostname pre-requisite check – “The host name specified for the installation or retrieved from the system is incorrect” (Doc ID 1488737.1)
/agentDeploy.sh AGENT_BASE_DIR=<Agent Base Directory Path> OMS_HOST=<OMS Host Name> EM_UPLOAD_PORT=<OMS Upload Port> ORACLE_HOSTNAME=mypc.oracle.com

Agregar o desplegar agente de Cloud Control desde el servidor destino.

#OracleACEAssociate

#OracleTipsSV

Raul Antonio Molina Alvarenga

1 de Agosto de 2023.

 

En una situación normal, el despliegue de un agente de Cloud Control 12c o 13c, se realiza desde la propia consola, desde donde comúnmente se realiza dicha tarea , inclusive para despliegues masivos.

Varias situaciones puede complicar dicho proceso,

  • No tener el password del usuario destino dueño del software a monitorear, o dueño del software del agente
  • No tener habilitado la regla de comunicación al puerto ssh del servidor destino
  • y algunas mas que se les ocurra

El procedimiento es como se observa en la figura, y se describe como método PUSH.

Installing Oracle Management Agent - 12c Release 2 (12.1.0.2)

Si esto no es posible, eso existe otra alternativa para desplegar el agente e incorporarlo a la infraestructura de Cloud Control 12c: Generación de Imagen e Instalación desde el destino.

Generación

Como generar la imagen de agente para instalación  en silent mode desde el propio destino.

Conectarse al emcli con credenciales , y sincronizar , hay que proporcionar el password de sysman.

emcli login -username=sysman

emcli sync

Consultar si se cuenta con la imagen de software de la respectiva plataforma cargada a la biblioteca de software del Cloud Control (SWLIB).

emcli get_supported_platforms

Mostrara algo como:

Si la version de imagen no existe, debemos descargarla de MyOracleSupport con el procedimiento estándar para dicha actividad ( Podemos hacer un video para documentar dicho proceso).

Identificando la version de la y la plataforma  procedemos a generar el ZIP de instalación desatendida.

emcli get_agentimage -destination=/tmp/agentinstaller -platform="Linux x86-64" -version="12.1.0.4.0" 

Trasladar la imagen en zip y desempacar en el target

Instalación de agentes usando metodo

En el cloud agregar en el /etc/hosts  el host e ip del target de BD(HOST) ( pude lograrse mediante DNS).

En el target debemos agregar el HOST del cloud nuevo asi:

#Nuevo OEM

OMSIP OEMHOSTNAME

Debemos generar el archivo de respuesta asi:

respuesta.rsp

OMS_HOST=OMSIP

EM_UPLOAD_PORT=4899

AGENT_REGISTRATION_PASSWORD=PASS

AGENT_PORT=3872

Ejecutamos luego el script agentDeploy.sh, así:

/export/home/oracle/agente/agentDeploy.sh AGENT_BASE_DIR=/export/home/oracle/agent12c RESPONSE_FILE=/export/home/oracle/agente/respuesta.rsp PROPERTIES_FILE=/export/home/oracle/agente/agentimage.properties -ignorePrereqs

Update home dependency completed successfully.

Executing command: /oracle/agent12c/core/12.1.0.5.0/oui/bin/runConfig.sh ORACLE_HOME=/oracle/agent12c/core/12.1.0.5.0 RESPONSE_FILE=/oracle/agent12c/core/12.1.0.5.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true

ERROR: Agent Configuration Failed SEVERE:emctl secure agent command has failed with status=1SEVERE:emctl secure agent command has failed with status=1SEVERE:emctl secure agent command has failed with status=1

Agent Deploy Log Location:/oracle/agent12c/core/12.1.0.5.0/cfgtoollogs/agentDeploy/agentDeploy_2023-06-16_16-00-42-PM.log

Si da error el aseguramiento, 

se corrige el error probable el hosts, puede seguirse los pasos sin error y el siguiente apartado no sera necesario:

emctl secure agent

bash-3.2$ /oracle/agent12c/agent_inst/bin/emctl secure agent

Oracle Enterprise Manager Cloud Control 12c Release 5  

Copyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.

Agent is already stopped...   Done.

Securing agent...   Started.

Enter Agent Registration Password : 

Securing agent...   Successful.

emctl upload 


Ejecutamos el paso de configuracion interna( solo si fallo el aseguramiento en el párrafo anterior)

emctl config  agent addinternaltargets

luego

emctl status agent 

emctl upload agent

bash-3.2$ /oracle/agent12c/agent_inst/bin/emctl status agent

Oracle Enterprise Manager Cloud Control 12c Release 5  

Copyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.

---------------------------------------------------------------

Agent Version          : 12.1.0.5.0

OMS Version            : 12.1.0.5.0

Protocol Version       : 12.1.0.1.0

Agent Home             : /oracle/agent12c/agent_inst

Agent Log Directory    : /oracle/agent12c/agent_inst/sysman/log

Agent Binaries         : /oracle/agent12c/core/12.1.0.5.0

Agent Process ID       : 13929

Parent Process ID      : 13833

Agent URL              : https://TARGET:3882/emd/main/

Local Agent URL in NAT : https://TARGET:3882/emd/main/

Repository URL         : https://OMSHOSTNAME:4899/empbs/upload

Started at             : 2023-06-16 17:20:48

Started by user        : oracle

Operating System       : SunOS version 5.10 (sparcv9)

Last Reload            : (none)

Last successful upload                       : 2023-06-16 17:22:33

Last attempted upload                        : 2023-06-16 17:22:33

Total Megabytes of XML files uploaded so far : 0.07

Number of XML files pending upload           : 0

Size of XML files pending upload(MB)         : 0

Available disk space on upload filesystem    : 22.42%

Collection Status                            : Collections enabled

Heartbeat Status                             : Ok

Last attempted heartbeat to OMS              : 2023-06-16 17:21:56

Last successful heartbeat to OMS             : 2023-06-16 17:21:56

Next scheduled heartbeat to OMS              : 2023-06-16 17:22:56

---------------------------------------------------------------

Agent is Running and Ready

bash-3.2$ 

Y con eso tendremos un agente instalado de forma correcta, no olvidar ejecutar el script de root.sh dentro del OracleHOME del agente, descubrir los demás componentes en el HOST y a poder usar el agente totalmente funcional

Espero les sea de utilidad

saludos.

Aplicar parche OneOff en Agente de Cloud

27 de Julio de 2023

Raúl Antonio Molina Alvarenga

#OracleACEAssociate

Si alguna vez se ven en la necesidad de aplicar un  Parche para una falla especifica (OneOff), o solventar un tema particular, aqui esta como deben realizarlo.

Parche  de correccion de auto inicio de agenter 12c (12.1.0.5)  en solaris  sparc

p21779343_121050_SOLARIS64.zip

 

Si el agente esta encendido , apagarlo

ORACLE_HOME  agentHOME/core/12.1.0.5.0  o su equivalente

export ORACLE_HOME=/export/home/oracle/agent12c/core/12.1.0.5.0

export PATH=$ORACLE_HOME/OPatch:$PATH

unzip p21779343_121050_SOLARIS64.zip

cd 21779343

opatch apply

luego, encender el agente.

#############

Espero les sea de Utilidad

Saludos

Inicio de la Historia

Noviembre 2020: Bienvenidos a este interesante Mundo de la Tecnología de Oracle Por aquí veremos tips, consejos, soluciones y toda clase de ayuda para ustedes, aceptando sugerencias de cualquier. Update Septimbre 2022:  Ahora soy Oracle ACE Associate Update Julio 2023: Continuo siendo Oracle ACE Associate   Update Julio 2024: Progreso o mejora, ACE Pro

Instalación Oracle Cloud Control 13c en Modo Silencioso

24 de Julio de 2023

Raúl Antonio Molina Alvarenga

#OracleACEAssociate

#Oracletipssv

Me pareció interesante publicar una entrada de articulo respecto a la instalación de un Cloud control completamente en modo silencioso o completamente desatendido.

Digo interesante porque, para mi lo es, dado que usualmente estamos acostumbrados a usar pantallas de un asistente que responden a nuestra interacción.

 

El Cloud Control  es una arquitectura de Software Empresaria muy robusta que permite al menos el monitoreo de otros componentes  Oracle, entre base de datos, Servidores de aplicaciones, Servidores físicos, Virtuales, un diagrama que presenta la solución:

Cloud Control Introduction

Usaremos Rutas estándar de producto, como por ejemplo el GI HOME:

/u01/app/19.0.0/grid

Algunas configuraciones no serán tomadas en detalle pues no es el foco del guion.

Configuraciones del Sistema Operativo

Limites

oracle soft nofile 1024
oracle hard nofile 65536
oracle soft nproc 16384
oracle hard nproc 16384
oracle soft stack 10240
oracle hard stack 32768
oracle hard memlock 134217728
oracle soft memlock 134217728
grid soft nofile 1024
grid hard nofile 65536
grid soft nproc 16384
grid hard nproc 16384
grid soft stack 10240
grid hard stack 32768
grid hard memlock 134217728
grid soft memlock 134217728

Lo escencial es configurar con el RPM de Preinstall RDBMS:

https://yum.oracle.com/repo/OracleLinux/OL8/latest/x86_64/getPackage/oracle-database-preinstall-19c-1.0-1.el7.x86_64.rpm
Download el RPM del public :
http://public-yum.oracle.com/repo/OracleLinux/OL8/baseos/latest/x86_64/getPackage/oracle-database-preinstall-19c-1.0-1.el8.x86_64.rpm

GI

Y luego instalar el GI

./gridSetup.sh -silent -responseFile /u01/app/19.0.0/grid/install/response/gridsetup.rsp

Si se presenta problema hacer dicho workaround:

Solution

To solve INS-08101 ‘supportedOSCheck’, we trick OUI to think the operating system is release 7.8 by using an environment variable CV_ASSUME_DISTID, either temporarily or permanently.
1. Temporarily

At runtime, we can export the variable.
[oracle@ora19c dbhome_1]$ export CV_ASSUME_DISTID=OEL8.1

RDBMS

Una vez se ha configurado el GI, procedemos con el RDBMS:

./runInstaller -ignorePrereq -waitforcompletion -silent \
-responseFile /u01/app/oracle/product/19.0.0/db_1/install/response/db_install.rsp \
oracle.install.option=INSTALL_DB_SWONLY \
ORACLE_HOSTNAME=PLVORAGRID \
UNIX_GROUP_NAME=oinstall \
INVENTORY_LOCATION=/u01/app/oraInventory \
SELECTED_LANGUAGES=en,en_GB \
ORACLE_HOME=/u01/app/oracle/product/19.0.0/db_1 \
ORACLE_BASE=/u02/app/oracle \
oracle.install.db.InstallEdition=EE \
oracle.install.db.OSDBA_GROUP=dba \
oracle.install.db.OSBACKUPDBA_GROUP=dba \
oracle.install.db.OSDGDBA_GROUP=dba \
oracle.install.db.OSKMDBA_GROUP=dba \
oracle.install.db.OSRACDBA_GROUP=dba \
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false \
DECLINE_SECURITY_UPDATES=true

Creamos la BD que albergara el REPO del componente de OMR

dbca -silent -createDatabase \
-templateName General_Purpose.dbc \
-gdbname emcdb -sid emcdb -responseFile NO_VALUE \
-characterSet AL32UTF8 \
-sysPassword SysPassword1 \
-systemPassword SysPassword1 \
-createAsContainerDatabase true \
-numberOfPDBs 1 \
-pdbName emrep \
-pdbAdminPassword SysPassword1 \
-databaseType MULTIPURPOSE \
-memoryMgmtType auto_sga \
-totalMemory 2048 \
-storageType ASM \
-diskGroupName +DATA \
-redoLogFileSize 600 \
-emConfiguration NONE \
-ignorePreReqs

Aplicamos un RU en ambas capas

opatchauto apply /installMedia/32126842/32067171

 

Host:plvoragrid
SIHA Home:/u01/app/19.0.0/grid
Version:19.0.0.0.0
Summary:

==Following patches were SUCCESSFULLY applied:

Patch: /installMedia/32126842/32067171
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-02-09_13-44-06PM_1.log

 

OPatchauto session completed at Tue Feb 9 13:47:37 2021
Time taken to complete the session 6 minutes, 5 seconds
[root@PLVORAGRID 32067171]#

32067171;OJVM RELEASE UPDATE: 19.10.0.0.210119 (32067171)
29585399;OCW RELEASE UPDATE 19.3.0.0.0 (29585399)
29517242;Database Release Update : 19.3.0.0.190416 (29517242)

OPatch succeeded.


La configuración de la maquina quedaría así con el HAS:

crsctl stat res -t
--------------------------------------------------------------------------------
Name Target State Server State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
ONLINE ONLINE plvoragrid STABLE
ora.LISTENER.lsnr
ONLINE ONLINE plvoragrid STABLE
ora.asm
ONLINE ONLINE plvoragrid Started,STABLE
ora.ons
OFFLINE OFFLINE plvoragrid STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
1 ONLINE ONLINE plvoragrid STABLE
ora.diskmon
1 OFFLINE OFFLINE STABLE
ora.emcdb.db
1 ONLINE ONLINE plvoragrid Open,HOME=/u01/app/o
racle/product/19.0.0
/db_1,STABLE
ora.evmd
1 ONLINE ONLINE plvoragrid STABLE
--------------------------------------------------------------------------------
[grid@PLVORAGRID ~]$ asmcmd lsdg
State Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED EXTERN N 512 512 4096 4194304 307188 301880 0 301880 0 N DATA/

 

A la base de datos, hay que ajustarle algunas configuraciones :

alter system set db_create_file_dest='${DATA_DIR}';
alter pluggable database ${PDB_NAME} save state;

-- Recommended minimum settings.
alter system set "_allow_insert_with_update_check"=true scope=both;
alter system set session_cached_cursors=200 scope=spfile;

-- Recommended: processes=600
alter system set processes=600 scope=spfile;

-- Recommended: pga_aggregate_target=1G
alter system set pga_aggregate_target=450M scope=spfile;

-- Recommended: sga_target=3G
alter system set sga_target=800M scope=spfile;

-- Recommended: shared_pool_size=600M
--alter system set shared_pool_size=600M scope=spfile;

-- For 12.1.0.2 set the following.
--alter system set optimizer_adaptive_features=false scope=both;

-- Should not be needed for 19c, but installer fails without them.
alter system set "_optimizer_nlj_hj_adaptive_join"= FALSE scope=both sid='*';
alter system set "_optimizer_strans_adaptive_pruning" = FALSE scope=both sid='*';
alter system set "_px_adaptive_dist_method" = OFF scope=both sid='*';
alter system set "_sql_plan_directive_mgmt_control" = 0 scope=both sid='*';
alter system set "_optimizer_dsdir_usage_control" = 0 scope=both sid='*';
alter system set "_optimizer_use_feedback" = FALSE scope=both sid='*';
alter system set "_optimizer_gather_feedback" = FALSE scope=both sid='*';
alter system set "_optimizer_performance_feedback" = OFF scope=both sid='*';

SHUTDOWN IMMEDIATE;
STARTUP;

 

Instalación del Cloud Control

Parametros para response file de Cloud Control

# Set parameters.
ORACLE_BASE=/u02/app/oracle
UNIX_GROUP_NAME=oinstall
ORA_INVENTORY=/u01/app/oraInventory
MW_HOME=/u01/app/oracle/middleware
ORACLE_HOSTNAME=${HOSTNAME}
AGENT_BASE=/u01/app/oracle/agent
WLS_USERNAME=weblogic
WLS_PASSWORD=Welcome1
GC_INST=${ORACLE_BASE}/gc_inst
SOFTWARE_LIBRARY=/u02/app/oracle/swlib
DATABASE_HOSTNAME=${HOSTNAME}
LISTENER_PORT=1521
PDB_NAME=emrep
SYS_PASSWORD=SysPassword1
AGENT_PASSWORD=${WLS_PASSWORD}
ORACLE_SID=emcdb
DATA_DIR=+DATA
OMS_HOME=${MW_HOME}
SYSMAN_PASSWORD=${WLS_PASSWORD}
SOFTWARE_DIR=/installMedia/
cat > /tmp/install.rsp <<EOF
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME=${UNIX_GROUP_NAME}
INVENTORY_LOCATION=${ORA_INVENTORY}
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=true
INSTALL_UPDATES_SELECTION=skip
ORACLE_MIDDLEWARE_HOME_LOCATION=${MW_HOME}
ORACLE_HOSTNAME=${ORACLE_HOSTNAME}
AGENT_BASE_DIR=${AGENT_BASE}
WLS_ADMIN_SERVER_USERNAME=${WLS_USERNAME}
WLS_ADMIN_SERVER_PASSWORD=${WLS_PASSWORD}
WLS_ADMIN_SERVER_CONFIRM_PASSWORD=${WLS_PASSWORD}
NODE_MANAGER_PASSWORD=${WLS_PASSWORD}
NODE_MANAGER_CONFIRM_PASSWORD=${WLS_PASSWORD}
ORACLE_INSTANCE_HOME_LOCATION=${GC_INST}
CONFIGURE_ORACLE_SOFTWARE_LIBRARY=true
SOFTWARE_LIBRARY_LOCATION=${SOFTWARE_LIBRARY}
DATABASE_HOSTNAME=${DATABASE_HOSTNAME}
LISTENER_PORT=${LISTENER_PORT}
SERVICENAME_OR_SID=${PDB_NAME}
SYS_PASSWORD=${SYS_PASSWORD}
SYSMAN_PASSWORD=${SYSMAN_PASSWORD}
SYSMAN_CONFIRM_PASSWORD=${SYSMAN_PASSWORD}
DEPLOYMENT_SIZE=SMALL
AGENT_REGISTRATION_PASSWORD=${AGENT_PASSWORD}
AGENT_REGISTRATION_CONFIRM_PASSWORD=${AGENT_PASSWORD}
PLUGIN_SELECTION={}
b_upgrade=false
EM_INSTALL_TYPE=NOSEED
CONFIGURATION_TYPE=LATER
CONFIGURE_SHARED_LOCATION_BIP=false
MANAGEMENT_TABLESPACE_LOCATION=${DATA_DIR}/${ORACLE_SID^^}/${PDB_NAME}/mgmt.dbf
CONFIGURATION_DATA_TABLESPACE_LOCATION=${DATA_DIR}/${ORACLE_SID^^}/${PDB_NAME}/mgmt_ecm_depot1.dbf
JVM_DIAGNOSTICS_TABLESPACE_LOCATION=${DATA_DIR}/${ORACLE_SID^^}/${PDB_NAME}/mgmt_deepdive.dbf
EOF

Lanzamos el instalador para que despliegue el Software completo, mas no realizara configuración, prefiero que se haga así , por si hay algún error podemos corregirlo, no esta de mas que indique que si se puede realizar un backup de BD  (o un punto de restauración con garantía)  que permita revertir la BD completa a un punto en el tiempo, seria prudente.

./em13400_linux64.bin -silent -responseFile /tmp/install.rsp -J-Djava.io.tmpdir=/u02/tmp/

Una vez el instalador termine, podemos lanzar otro punto de control o reversion de estado de la BD completa, y lanzar el asistente de configuracion del Cloud Control 13c.

 

Al final adjunto los logs de ambos procesos.

cat > /tmp/config.rsp <<EOF
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME=${UNIX_GROUP_NAME}
INVENTORY_LOCATION=${ORA_INVENTORY}
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=true
INSTALL_UPDATES_SELECTION=skip
ORACLE_MIDDLEWARE_HOME_LOCATION=${MW_HOME}
ORACLE_HOSTNAME=${ORACLE_HOSTNAME}
AGENT_BASE_DIR=${AGENT_BASE}
WLS_ADMIN_SERVER_USERNAME=${WLS_USERNAME}
WLS_ADMIN_SERVER_PASSWORD=${WLS_PASSWORD}
WLS_ADMIN_SERVER_CONFIRM_PASSWORD=${WLS_PASSWORD}
NODE_MANAGER_PASSWORD=${WLS_PASSWORD}
NODE_MANAGER_CONFIRM_PASSWORD=${WLS_PASSWORD}
ORACLE_INSTANCE_HOME_LOCATION=${GC_INST}
CONFIGURE_ORACLE_SOFTWARE_LIBRARY=true
SOFTWARE_LIBRARY_LOCATION=${SOFTWARE_LIBRARY}
DATABASE_HOSTNAME=${DATABASE_HOSTNAME}
LISTENER_PORT=${LISTENER_PORT}
SERVICENAME_OR_SID=${PDB_NAME}
SYS_PASSWORD=${SYS_PASSWORD}
SYSMAN_PASSWORD=${SYSMAN_PASSWORD}
SYSMAN_CONFIRM_PASSWORD=${SYSMAN_PASSWORD}
DEPLOYMENT_SIZE=SMALL
AGENT_REGISTRATION_PASSWORD=${AGENT_PASSWORD}
AGENT_REGISTRATION_CONFIRM_PASSWORD=${AGENT_PASSWORD}
PLUGIN_SELECTION={}
b_upgrade=false
EM_INSTALL_TYPE=NOSEED
CONFIGURATION_TYPE=ADVANCED
CONFIGURE_SHARED_LOCATION_BIP=false
MANAGEMENT_TABLESPACE_LOCATION=${DATA_DIR}/${ORACLE_SID^^}/${PDB_NAME}/mgmt.dbf
CONFIGURATION_DATA_TABLESPACE_LOCATION=${DATA_DIR}/${ORACLE_SID^^}/${PDB_NAME}/mgmt_ecm_depot1.dbf
JVM_DIAGNOSTICS_TABLESPACE_LOCATION=${DATA_DIR}/${ORACLE_SID^^}/${PDB_NAME}/mgmt_deepdive.dbf
EOF





./sysman/install/ConfigureGC.sh -silent -responseFile /tmp/config.rsp

Al finalizar, tendremos un producto Cloud Control 13c correctamente instalado.

Espero les sea de Utilidad.

Saludos

Logs

Launcher log file is /tmp/OraInstall2021-02-09_05-15-05PM/launcher2021-02-09_05-15-05PM.log.
Extracting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Done
Checking swap space: must be greater than 512 MB. Actual 16383 MB Passed
Checking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required)
Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2021-02-09_05-15-05PM
====Prereq Config Location main===
/tmp/OraInstall2021-02-09_05-15-05PM/stage/prereq
EMGCInstaller args -scratchPath
EMGCInstaller args /tmp/OraInstall2021-02-09_05-15-05PM
EMGCInstaller args -sourceType
EMGCInstaller args network
EMGCInstaller args -timestamp
EMGCInstaller args 2021-02-09_05-15-05PM
EMGCInstaller args -paramFile
EMGCInstaller args /tmp/sfx_okyBMq/Disk1/install/linux64/oraparam.ini
EMGCInstaller args -silent
EMGCInstaller args -responseFile
EMGCInstaller args /tmp/install.rsp
EMGCInstaller args -nocleanUpOnExit
DiskLoc inside SourceLoc/tmp
EMFileLoc:/tmp/OraInstall2021-02-09_05-15-05PM/oui/em/
ScratchPathValue :/tmp/OraInstall2021-02-09_05-15-05PM
EMGCInstallUpdatesInfoOnNext:: calling actionOnClickofNext
Now in EMGCInstallUpdatesInfoOnNext.actionsOnClickofNext
EMGCInstallUpdatesInfoOnNext:: End of actionOnClickofNext
Some recommended prerequisites checks failed. You might encounter errors during installation. Fix those prerequisites and start the installation again.
Unable to copy the logs to the permanent location: The permanent log directory is unknown (null)..

The log(s) can be found here: /tmp/OraInstall2021-02-09_05-15-05PM.
<eFile /tmp/install.rsp -J-Djava.io.tmpdir=/u02/tmp/
ERROR: Cannot create the extract directory in /u02/tmp (Permission denied).
ERROR: Cannot setup the extract directory /u02/tmp/sfx_kOG195 (-1).
<eFile /tmp/install.rsp -J-Djava.io.tmpdir=/u02/tmp/
Launcher log file is /u02/tmp/OraInstall2021-02-09_05-18-26PM/launcher2021-02-09_05-18-26PM.log.
Extracting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . Done
Checking swap space: must be greater than 512 MB. Actual 16383 MB Passed
Checking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required)
Preparing to launch the Oracle Universal Installer from /u02/tmp/OraInstall2021-02-09_05-18-26PM
====Prereq Config Location main===
/u02/tmp/OraInstall2021-02-09_05-18-26PM/stage/prereq
EMGCInstaller args -scratchPath
EMGCInstaller args /u02/tmp/OraInstall2021-02-09_05-18-26PM
EMGCInstaller args -sourceType
EMGCInstaller args network
EMGCInstaller args -timestamp
EMGCInstaller args 2021-02-09_05-18-26PM
EMGCInstaller args -paramFile
EMGCInstaller args /u02/tmp/sfx_vCLaNi/Disk1/install/linux64/oraparam.ini
EMGCInstaller args -silent
EMGCInstaller args -responseFile
EMGCInstaller args /tmp/install.rsp
EMGCInstaller args -nocleanUpOnExit
DiskLoc inside SourceLoc/u02/tmp
EMFileLoc:/u02/tmp/OraInstall2021-02-09_05-18-26PM/oui/em/
ScratchPathValue :/u02/tmp/OraInstall2021-02-09_05-18-26PM
EMGCInstallUpdatesInfoOnNext:: calling actionOnClickofNext
Now in EMGCInstallUpdatesInfoOnNext.actionsOnClickofNext
EMGCInstallUpdatesInfoOnNext:: End of actionOnClickofNext
The installer detected the host name as PLVORAGRID, but you have changed it to PLVORAGRID
Session log file is /u02/tmp/OraInstall2021-02-09_05-18-26PM/install2021-02-09_05-18-26PM.log
Installation in progress

Install successful
Linking in progress

Link successful
Setup in progress

Setup successful
Session log file is /u02/tmp/OraInstall2021-02-09_05-18-26PM/install2021-02-09_05-18-26PM.log
Installation in progress

Install successful
Linking in progress

Link successful
Setup in progress

Setup successful
Agent OracleHome :/u01/app/oracle/agent/agent_13.4.0.0.0
OMS OracleHome :/u01/app/oracle/middleware

13NGCHEKAGGREGATE : oracle.sysman.top.agent
13NGCHEKAGGREGATE : OuiConfigVariables
13NGCHEKAGGREGATE : oracle.sysman.top.oms
13NGCHEKAGGREGATE : encap_oms
13NGCHEKAGGREGATE : OuiConfigVariables
Prompt for the allroot.sh

Warning: You must run the following configuration scripts as the "root" user.
/u01/app/oracle/middleware/allroot.sh
To execute the configuration scripts:
1. Open a new terminal window.
2. Login in as "root".
3. Run the scripts.

Successfully installed Enterprise Manager Cloud Control.
Logs successfully copied to /u01/app/oraInventory/logs.


[oracle@PLVORAGRID installMedia]$
[oracle@PLVORAGRID installMedia]$

 

4 2021-02-10 08:48:19 history
<onfigureGC.sh -silent -responseFile /tmp/config.rsp
====Prereq Config Location main===
null
EMGCInstaller args -onlyconfig
EMGCInstaller args -oh
EMGCInstaller args /u01/app/oracle/middleware
EMGCInstaller args -scratchPath
EMGCInstaller args /u01/app/oracle/middleware
EMGCInstaller args -sourceLoc
EMGCInstaller args /u01/app/oracle/middleware
EMGCInstaller args INSTALL_SWONLY_WITH_PLUGINS=false
EMGCInstaller args -silent
EMGCInstaller args -responseFile
EMGCInstaller args /tmp/config.rsp
DiskLoc inside SourceLoc/u01/app/
EMFileLoc:/u01/app/oracle/middleware/oui/em/
ScratchPathValue :/u01/app/oracle/middleware
Error Messages:
----------------------------------------------------
* Invalid option(s): sourceLoc
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
List file is unreadable
Oracle strongly recommends using the AL32UTF8 character set for EM repository. AL32UTF8 is Oracle's name for the standard Unicode encoding UTF-8, which enables universal support of virtually all languages of the world.

The following prerequisite check failed because the Oracle Database, where the Management Repository will be configured, does not meet the configuration requirements. These failures do not impact the installation, but you may encounter performance issues with the product later. You can either click Cancel, fix the issue manually now, based on the recommendation offered for this prerequisite, and click Next, or you can click OK to fix it after the installation ends. For more details check the logs: /u01/app/oracle/middleware/cfgtoollogs/oui/emdbprereqs
Prereq Name Recommendation
Check the pga_aggregate_target instance parameter value. The pga_aggregate_target instance parameter should be set to at least 1000000000 bytes.
Check the sga_target instance parameter value. The sga_target instance parameter should be set to at least 3000000000 bytes.
Check the shared_pool_size instance parameter value. The shared_pool_size instance parameter should be set to at least 600000000 bytes or roughly one third of the sga_target size.
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

..................................................................................................
Installation in progress (Wednesday, February 10, 2021 8:48:42 AM PET)
98% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:48:43 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:48:43 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:48:43 AM PET)

Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:48:54 AM PET)
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

............................................................... 18% Done.
............................................................... 37% Done.
............................................................... 56% Done.
............................................................... 75% Done.
............................................................... 94% Done.
...............
Installation in progress (Wednesday, February 10, 2021 8:49:15 AM PET)
98% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:49:15 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:49:15 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:49:15 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:49:25 AM PET)
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

..................................................................................................
Installation in progress (Wednesday, February 10, 2021 8:49:34 AM PET)
98% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:49:35 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:49:35 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:49:35 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:49:44 AM PET)
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

............................................................... 23% Done.
............................................................... 46% Done.
............................................................... 70% Done.
............................................................... 93% Done.
...............
Installation in progress (Wednesday, February 10, 2021 8:50:03 AM PET)
98% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:50:03 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:50:03 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:50:03 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:50:13 AM PET)
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

..................................................................................................................
Installation in progress (Wednesday, February 10, 2021 8:50:30 AM PET)
98% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:50:31 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:50:31 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:50:31 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:50:40 AM PET)
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.emas/13.4.1.0.0/oracle.sysman.emas.agent.plugin-13.4.1.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

..................................................................................................
Installation in progress (Wednesday, February 10, 2021 8:50:46 AM PET)
98% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:50:46 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:50:46 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:50:46 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:50:57 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.emrep/13.4.0.0.0/oracle.sysman.emrep.agent.plugin-13.4.0.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

.......................................................................................
Installation in progress (Wednesday, February 10, 2021 8:50:59 AM PET)
87% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:50:59 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:50:59 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:50:59 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:51:10 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.beacon/13.4.0.0.0/oracle.sysman.beacon.agent.plugin-13.4.0.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

..................................................................................................
Installation in progress (Wednesday, February 10, 2021 8:51:13 AM PET)
98% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:51:13 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:51:13 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:51:13 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:51:24 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.oh/13.4.0.0.0/oracle.sysman.oh.agent.plugin-13.4.0.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

.................................................................................................
Installation in progress (Wednesday, February 10, 2021 8:51:26 AM PET)
97% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:51:26 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:51:26 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:51:26 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:51:37 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.csa/13.4.0.0.0/oracle.sysman.csa.agent.plugin-13.4.0.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

.......................................................................
Installation in progress (Wednesday, February 10, 2021 8:51:38 AM PET)
71% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:51:38 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:51:38 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:51:38 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:51:49 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.csa/13.4.0.0.0/oracle.sysman.csa.discovery.plugin-13.4.0.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

..............................................................................................
Installation in progress (Wednesday, February 10, 2021 8:51:51 AM PET)
93% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:51:51 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:51:51 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:51:51 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:52:02 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.oh/13.4.0.0.0/oracle.sysman.oh.discovery.plugin-13.4.0.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

..........................................................................
Installation in progress (Wednesday, February 10, 2021 8:52:04 AM PET)
74% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:52:04 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:52:04 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:52:04 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:52:14 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.db/13.4.1.0.0/oracle.sysman.db.discovery.plugin-13.4.1.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

............................................................................................
Installation in progress (Wednesday, February 10, 2021 8:52:16 AM PET)
92% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:52:16 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:52:16 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:52:16 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:52:27 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.xa/13.4.1.0.0/oracle.sysman.xa.discovery.plugin-13.4.1.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

.....................................................................................
Installation in progress (Wednesday, February 10, 2021 8:52:29 AM PET)
85% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:52:29 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:52:29 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:52:29 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:52:40 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.emas/13.4.1.0.0/oracle.sysman.emas.discovery.plugin-13.4.1.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

..................................................................................................
Installation in progress (Wednesday, February 10, 2021 8:52:42 AM PET)
98% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:52:42 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:52:42 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:52:42 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:52:53 AM PET)
List file is unreadable
List file is unreadable
&Decline License Agreement/u01/app/oracle/middleware/sysman/install/plugins/oracle.sysman.si/13.4.1.0.0/oracle.sysman.si.discovery.plugin-13.4.1.0.0.farb
Session log file is /tmp/OraInstall2021-02-10_08-48-30AM/nextgen2021-02-10_08-48-30AM.log

............................................................................
Installation in progress (Wednesday, February 10, 2021 8:52:54 AM PET)
76% Done.
Install successful

Linking in progress (Wednesday, February 10, 2021 8:52:54 AM PET)
Link successful

Setup in progress (Wednesday, February 10, 2021 8:52:54 AM PET)
Setup successful

Saving inventory (Wednesday, February 10, 2021 8:52:54 AM PET)
Saving inventory complete

End of install phases.(Wednesday, February 10, 2021 8:53:06 AM PET)
List file is unreadable
13NGCHEKAGGREGATE : oracle.sysman.top.agent
13NGCHEKAGGREGATE : OuiConfigVariables
13NGCHEKAGGREGATE : oracle.sysman.top.oms
13NGCHEKAGGREGATE : encap_oms
13NGCHEKAGGREGATE : OuiConfigVariables
2021-02-10_08-53-09AM: Configuration Assistant "Plugins Prerequisites Check" is in progress.

2021-02-10_08-53-17AM: Configuration Assistant "Plugins Prerequisites Check" has Succeeded.

2021-02-10_08-53-17AM: Configuration Assistant "Repository Configuration" is in progress.

Setting the value of EMPREREQKIT_RESULTDIR /u01/app/oracle/middleware/.gcinstall_temp
Calling the EMSCHEMA MANAGER: CREATE

Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
Repository Creation Utility - Create
Repository Create in progress.




Check the Repository Configuration Assistant logs at: /u01/app/oracle/middleware/sysman/log/schemamanager










TNS Test Inserted Successfully
Successfully Added TNS Query Descriptors

******** ORACLE_HOME is /u01/app/oracle/middleware
test properties path: /u01/app/oracle/middleware/sysman/admin/emdrep/prop/imap.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :imap_host
PropertyName :imap_port
PropertyName :imap_user_name
PropertyName :imap_password
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: IMAP , generic_service , 1.0
Enabled test for: IMAP , aggregate_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/middleware




Wed Feb 10 09:41:17.353 PET 2021 rcu:Extracted SQL Statement: [BEGIN
DECLARE
l_core_ver MGMT_VERSIONS.version%TYPE;
l_error VARCHAR2(100) ;
l_error_count NUMBER := 0 ;
l_database_role VARCHAR2(32);
BEGIN
-- Check to see if this database is in logical standby mode. If it is
-- we need to exit this script because logical standby doesn't support
-- DBMS_JOBS.
BEGIN
SELECT database_role into l_database_role
from v$database where database_role like '%LOGICAL%';
RETURN;
-- Exit this script if this is a logical standby db.
EXCEPTION
WHEN NO_DATA_FOUND THEN
NULL;
-- Just continue normally if this is not a logical standby db.
END;

BEGIN
SELECT version INTO l_core_ver
FROM MGMT_VERSIONS
WHERE component_name = 'CORE';
EXCEPTION
WHEN OTHERS THEN
l_core_ver := '4.0.0.0.0';
END;

IF (l_core_ver = '4.0.0.0.0') THEN

-- For 4.0.0 repository, the maintenance package
-- does not have the remove_em_dbms_jobs function, so
-- have to remove the jobs created in 4.0.0
SAVEPOINT admin_remove_jobs_start ;
FOR crec IN (select job, what FROM user_jobs
where what in (
'EM_SLM_COMPUTATION.EXEC_SLM_COMPUTATION_JOB();',
'EM_SLM_CALENDAR.UPDATE_CALENDAR();',
'MGMT_GENSVC_AVAIL.EXEC_AVAIL_JOB();',
'EMD_COLLECTION.RUN_COLLECTIONS();',
'EMD_EVALUATION.EVALSQLMETRICS();',
'EMD_LOADER.ROLLUP();',
'EMD_NOTIFICATION.DELIVER_NOTIFICATIONS();',
'EM_PING.MARK_NODE_STATUS();',
'MGMT_JOB_ENGINE.apply_purge_policies();'
)
or what like 'emd_maintenance.analyze_emd_schema%'
)
LOOP
BEGIN
DBMS_JOB.REMOVE(crec.job);
EXCEPTION
WHEN OTHERS THEN
l_error_count := l_error_count + 1 ;
IF l_error IS NULL
THEN
l_error := SUBSTR(SQLERRM,1,100) ;
END IF ;
END;
END LOOP;
IF l_error_count > 0
THEN
ROLLBACK TO SAVEPOINT admin_remove_jobs_start ;
raise_application_error(MGMT_GLOBAL.UNEXPECTED_ERR,
l_error_count||' error(s) when dropping dbms_jobs '||
',first error='||l_error) ;
END IF ;
ELSE

-- This is done as dynamic SQL, so that this can be run against
-- EM 4.0.0 repositories also
EXECUTE IMMEDIATE 'begin EMD_MAINTENANCE.REMOVE_EM_DBMS_JOBS; end;';

END IF;

END;
END;
]
Wed Feb 10 09:41:17.353 PET 2021 rcu:Extracted Statement from File Name: '/u01/app/oracle/middleware/sysman/admin/emdrep/sql/core/latest/admin/admin_remove_dbms_jobs.sql'Line Number: 111
Wed Feb 10 09:41:17.353 PET 2021 rcu:Statement Type: 'BEGIN/END Anonymous Block'
Wed Feb 10 09:41:17.751 PET 2021 rcu:Extracted SQL Statement: [PROMPT Submitting DBMS jobs.]
Wed Feb 10 09:41:17.751 PET 2021 rcu:Extracted Statement from File Name: '/u01/app/oracle/middleware/sysman/admin/emdrep/sql/core/latest/admin/admin_submit_dbms_jobs.sql'Line Number: 29
Wed Feb 10 09:41:17.751 PET 2021 rcu:Statement Type: 'Debug Statement'
Wed Feb 10 09:41:17.751 PET 2021 rcu:Extracted SQL Statement: [DECLARE
l_database_role VARCHAR2(32);
BEGIN
-- Check to see if this database is in logical standby mode. If it is
-- we need to exit this script because logical standby doesn't support
-- DBMS_JOBS.
BEGIN
SELECT database_role into l_database_role
from v$database where database_role like '%LOGICAL%';
EXCEPTION
WHEN NO_DATA_FOUND THEN
EMD_MAINTENANCE.SUBMIT_EM_DBMS_JOBS;
COMMIT;
END;
END;
]
Wed Feb 10 09:41:17.751 PET 2021 rcu:Extracted Statement from File Name: '/u01/app/oracle/middleware/sysman/admin/emdrep/sql/core/latest/admin/admin_submit_dbms_jobs.sql'Line Number: 46
Wed Feb 10 09:41:17.751 PET 2021 rcu:Statement Type: 'BEGIN/END Anonymous Block'

Repository Creation Utility: Create - Completion Summary

Database details:
-----------------------------
Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PLVORAGRID)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep)))
Connected As : SYS
RCU Logfile : No log file specified

Component schemas created:
-----------------------------
Component Status Logfile

EM Repository Creation Configuration Success /u01/app/oracle/middleware/sysman/log/schemamanager/m_021021_0853_AM/m_021021_0853_AM.CREATE/RCU2021-02-10_08-53_876334194/logs/em_repos_config.log
EM Repository Init Configuration Success /u01/app/oracle/middleware/sysman/log/schemamanager/m_021021_0853_AM/m_021021_0853_AM.CREATE/RCU2021-02-10_08-53_876334194/logs/em_repos_init.log
EM Repository Common Success /u01/app/oracle/middleware/sysman/log/schemamanager/m_021021_0853_AM/m_021021_0853_AM.CREATE/RCU2021-02-10_08-53_876334194/logs/em_repos_common.log

Repository Creation Utility - Create : Operation Completed
The creation of Repository is completed now running the MOS

2021-02-10_09-41-51AM: Configuration Assistant "Repository Configuration" has Succeeded.

2021-02-10_09-41-51AM: Configuration Assistant "MDS Schema Configuration" is in progress.

Setting the value of EMPREREQKIT_RESULTDIR /u01/app/oracle/middleware/.gcinstall_temp
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
Repository Creation Utility - Create
Repository Create in progress.
Percent Complete: 30
Percent Complete: 65
Percent Complete: 65
Percent Complete: 70
Percent Complete: 70
Percent Complete: 75
Percent Complete: 75
Percent Complete: 95
Percent Complete: 100

Repository Creation Utility: Create - Completion Summary

Database details:
-----------------------------
Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PLVORAGRID)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep)))
Connected As : SYS
Prefix for (prefixable) Schema Owners : SYSMAN
RCU Logfile : No log file specified

Component schemas created:
-----------------------------
Component Status Logfile

Metadata Services Success /u01/app/oracle/middleware/sysman/log/schemamanager/m_021021_0853_AM/m_021021_0853_AM.CREATE/RCU2021-02-10_09-41_996616159/logs/mds.log

Repository Creation Utility - Create : Operation Completed
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
Repository Creation Utility - Create
Repository Create in progress.
Percent Complete: 50
Percent Complete: 55
Percent Complete: 65
Percent Complete: 65
Percent Complete: 80
Percent Complete: 90
Percent Complete: 95
Percent Complete: 95
Percent Complete: 97
Percent Complete: 100

Repository Creation Utility: Create - Completion Summary

Database details:
-----------------------------
Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PLVORAGRID)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep)))
Connected As : SYS
Prefix for (prefixable) Schema Owners : SYSMAN122130
RCU Logfile : No log file specified

Component schemas created:
-----------------------------
Component Status Logfile

Oracle Platform Security Services Success /u01/app/oracle/middleware/sysman/log/schemamanager/m_021021_0853_AM/m_021021_0853_AM.CREATE/RCU2021-02-10_09-41_996616159/logs/opss.log

Repository Creation Utility - Create : Operation Completed
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
Repository Creation Utility - Create
Repository Create in progress.
Percent Complete: 50
Percent Complete: 50
Percent Complete: 55
Percent Complete: 60
Percent Complete: 65
Percent Complete: 65
Percent Complete: 65
Percent Complete: 82
Percent Complete: 100

Repository Creation Utility: Create - Completion Summary

Database details:
-----------------------------
Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PLVORAGRID)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep)))
Connected As : SYS
Prefix for (prefixable) Schema Owners : SYSMAN
RCU Logfile : No log file specified

Component schemas created:
-----------------------------
Component Status Logfile

Common Infrastructure Services Success /u01/app/oracle/middleware/sysman/log/schemamanager/m_021021_0853_AM/m_021021_0853_AM.CREATE/RCU2021-02-10_09-41_996616159/logs/stb.log

Repository Creation Utility - Create : Operation Completed
2021-02-10_09-42-02AM: Configuration Assistant "MDS Schema Configuration" has Succeeded.

2021-02-10_09-42-02AM: Configuration Assistant "BI Publisher Schema Configuration" is in progress.

Setting the value of EMPREREQKIT_RESULTDIR /u01/app/oracle/middleware/.gcinstall_temp
Middleware home/u01/app/oracle/middleware
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : Oracle Home is /u01/app/oracle/middleware
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : Schema Oracle Home is /u01/app/oracle/middleware/bi
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : Setting RCU_HOME to /u01/app/oracle/middleware/oracle_common
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : Setting SCRIPT_HOME to /u01/app/oracle/middleware/oracle_common/common/sql
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : Setting RCU_LOG_LOCATION to /u01/app/oracle/middleware/cfgtoollogs/bip
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : Setting RCU_LOG_NAME to emBIPLATFORM.log
2021_02_10_AD_09_42_02_PET BIPLATFORM version is null
2021_02_10_AD_09_42_02_PET has BIPLATFORM user? false
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : Prepare to initialize RCU
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : RCU initialized with parameters : -silent -createRepository -compInfoXMLLocation /u01/app/oracle/middleware/sysman/emdrep/config/schemaext/ComponentInfo.xml -storageXMLLocation /u01/app/oracle/middleware/sysman/emdrep/config/schemaext/Storage.xml -connectString (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PLVORAGRID)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep))) -dbUser SYS -dbRole sysdba -schemaPrefix SYSMAN -component BIPLATFORM
2021_02_10_AD_09_42_02_PET BIPLATFORM EMSchemaManagerHelper: Info : Invoking RCU
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
Repository Creation Utility - Create
Repository Create in progress.
Percent Complete: 50
Percent Complete: 50
Percent Complete: 55
Percent Complete: 55
Percent Complete: 65
Percent Complete: 77
Percent Complete: 88
Percent Complete: 94
Percent Complete: 97
Percent Complete: 98
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 99
Percent Complete: 100

Repository Creation Utility: Create - Completion Summary

Database details:
-----------------------------
Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PLVORAGRID)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep)))
Connected As : SYS
Prefix for (prefixable) Schema Owners : SYSMAN
RCU Logfile : No log file specified

Component schemas created:
-----------------------------
Component Status Logfile

Business Intelligence Platform Success /u01/app/oracle/middleware/sysman/log/schemamanager/m_021021_0853_AM/m_021021_0853_AM.CREATE/RCU2021-02-10_09-42_1064729917/logs/biplatform.log

Repository Creation Utility - Create : Operation Completed
2021_02_10_AD_09_42_07_PET BIPLATFORM EMSchemaManagerHelper: Info : RCU Completed : COMPLETED
2021_02_10_AD_09_42_07_PET BIPLATFORM EMSchemaManagerHelper: Info : Asscociating profile
Unable to create logger...
2021_02_10_AD_09_42_07_PET BIPLATFORM EMSchemaManagerHelper: Info : profile associated
Successfully created SYSMAN_BIPLATFORM schema...
Recompiling Required BI Publisher Database views with invalid objects.
The SQL {0} execution is complete.
The SQL {0} execution is complete.
The SQL {0} execution is complete.
The SQL {0} execution is complete.
The SQL {0} execution is complete.
The SQL {0} execution is complete.
Verifying if the Required BI Publisher Database views do not contain invalid objects any longer.
Invalid Objects from BI Publisher Database views have been removed.
2021-02-10_09-42-07AM: Configuration Assistant "BI Publisher Schema Configuration" has Succeeded.

2021-02-10_09-42-07AM: Configuration Assistant "OMS Configuration" is in progress.

Executing the OMSCA command...

Check the log files of the OMS Configuration Assistant at: /u01/app/oracle/middleware/cfgtoollogs/omsca




OMS Configuration Assistant completed successfully.

2021-02-10_09-52-14AM: Configuration Assistant "OMS Configuration" has Succeeded.

2021-02-10_09-52-14AM: Configuration Assistant "Plugins Deployment and Configuration" is in progress.




2021-02-10_09-59-40AM: Configuration Assistant "Plugins Deployment and Configuration" has Succeeded.

2021-02-10_09-59-40AM: Configuration Assistant "BI Publisher Configuration" is in progress.

2021-02-10_10-07-06AM: Configuration Assistant "BI Publisher Configuration" has Succeeded.

2021-02-10_10-07-06AM: Configuration Assistant "Start Oracle Management Service" is in progress.

Starting OMS ...
Executing the command: /u01/app/oracle/middleware/bin/emctl start oms

Starting of OMS is successful.
Starting export oms config...
Executing command: /u01/app/oracle/middleware/bin/emctl exportconfig oms -dir /u02/app/oracle/gc_inst/em/EMGC_OMS1/sysman/backup

Export config of OMS is successful.

2021-02-10_10-11-53AM: Configuration Assistant "Start Oracle Management Service" has Succeeded.

2021-02-10_10-11-53AM: Configuration Assistant "Agent Configuration Assistant" is in progress.

AgentConfiguration:agent configuration has been started

The AgentFreshInstaller is starting now
Oraclehome : ../u01/app/oracle/agent/agent_13.4.0.0.0
InstanceHome : /u01/app/oracle/agent/agent_inst
Agent Base Directory : /u01/app/oracle/agent
The oraclehome /u01/app/oracle/agent/agent_13.4.0.0.0
startAgent is:true
seci is :true
startAgent is:true
seci is :true
log loction is setlog
Creating log directoyr :/u01/app/oracle/agent/agent_13.4.0.0.0/cfgtoollogs/agentDeploy
Writing the following contents into /u01/app/oracle/agent/agent_13.4.0.0.0/install/oragchomelist
/u01/app/oracle/agent/agent_13.4.0.0.0:/u01/app/oracle/agent/agent_inst
Creating directory /u01/app/oracle/agent/agent_13.4.0.0.0/install/tmp completed successfully.
File /etc/oragchomelist exists.
File /etc/oragchomelist is writable.
Index :-1 for line : /u01/app/oracle/middleware
Index :0 for line : /u01/app/oracle/agent/agent_13.4.0.0.0
Overwriting the contents since oracle home:/u01/app/oracle/agent/agent_13.4.0.0.0 entry already exists.
Agent Home is : {0}
The value of chainInstall : true forceConfigure : false skipValidation : false
Validated the oms host and port :- PLVORAGRID----4903
Logs Location is : {0}
Getting Inet Addresses for host PLVORAGRID
** Agent Port Check completed successfully.**
Validated the agent port :- ----3872
Executing command: {0}
shared agent value is :false

Setting system property CUSTOM_INVENTORY to {0}
chain install is :true

Cloning of agent home completed successfully
Agent Configuration completed successfully
The following configuration scripts need to be executed as the "root" user. Root script to run : /u01/app/oracle/agent/agent_13.4.0.0.0/root.sh
AgentConfiguration:agent configuration finished with status = true

2021-02-10_10-13-23AM: Configuration Assistant "Agent Configuration Assistant" has Succeeded.

*** The Installation was Successful. ***

This information is also available at:

/u01/app/oracle/middleware/install/setupinfo.txt

See the following for information pertaining to your Enterprise Manager installation:

Use the following URL to access:

1. Enterprise Manager Cloud Control URL: https://PLVORAGRID:7803/em
2. Admin Server URL: https://PLVORAGRID:7102/console
3. BI Publisher URL: https://PLVORAGRID:9803/xmlpserver/servlet/home

The following details need to be provided while installing an additional OMS:

1. Admin Server Host Name: PLVORAGRID
2. Admin Server Port: 7102

You can find the details on ports used by this deployment at : /u01/app/oracle/middleware/install/portlist.ini

NOTE:
An encryption key has been generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in the Repository becomes unusable.

A backup of the OMS configuration is available in /u02/app/oracle/gc_inst/em/EMGC_OMS1/sysman/backup on host PLVORAGRID. See Cloud Control Administrators Guide for details on how to back up and recover an OMS.

NOTE: This backup is valid only for the initial OMS configuration. For example, it will not reflect plug-ins installed later, topology changes like the addition of a load balancer, or changes to other properties made using emctl or emcli. Backups should be created on a regular basis to ensure they capture the current OMS configuration. Use the following command to backup the OMS configuration:
/u01/app/oracle/middleware/bin/emctl exportconfig oms -dir <backup dir>

Prompt for the allroot.sh
[oracle@PLVORAGRID install]$
[oracle@PLVORAGRID install]$

Como crear un HANFS en un Oracle RAC

Raúl Antonio Molina Alvarenga

04-05-2023

#OracleACE
#OracleTipsSV

Pasos para crear HANFS en un cluster
Se hace con root y los binarios crsctl y srvctl estan en:

/u01/app/19.0.0.0/grid/bin
1) Crear recurso havaip , es quien publica el nfs
Origen
/u01/app/19.0.0.0/grid/bin/srvctl add havip -id hrexports -address 20.2.1.92

2) crear el diskgroup y el ACFS

create diskgroup acfsdg NORMAL REDUNDANCY
DISK
'/dev/rdsk/disco*'
ATTRIBUTE 'content.type' = 'DATA',
'content.type' = 'DATA',
'AU_SIZE' = '4M',
'cell.smart_scan_capable'='TRUE',
'compatible.rdbms'='11.2.0.4',
'compatible.advm'='19.0.0.0',
'compatible.asm'='11.0.0.0';
---> Los discos usados fueron:
/dev/rdsk/disco1
/dev/rdsk/disco2
/dev/rdsk/disco3
/dev/rdsk/disco4

Volumen:

Diskgroup Name: acfsdg

Volume Name: volacfsdg
Volume Device: /dev/asm/vol_fsbcc1-20
State: ENABLED
Size (MB): 4194304
Resize Unit (MB): 64
Redundancy: MIRROR
Stripe Columns: 8
Stripe Width (K): 1024
Usage: ACFS
Mountpath: /origenfs
alter diskgroup acfsdg add volume volacfsdg size 8T;

 

3) Crear el FS
/u01/app/19.0.0.0/grid/bin/srvctl add filesystem -device /dev/asm/vol_fsbcc1-20 -volume VOLUME1 \
-diskgroup acfsdg -mountpath /origenfs
4) crear el export del acfs
origen
/u01/app/19.0.0.0/grid/bin/srvctl add exportfs -id hrexports -path /origenfs -name hrexport1 -options "rw,no_root_squash"
/u01/app/19.0.0.0/grid/bin/srvctl modify exportfs -name hrexport1 -options "rw,sync,no_wdelay,insecure,insecure_locks,no_root_squash"
4.1 ) encender nfs y rcpbind y dejarlos peremnes en los nodos del cluster que exporta el NFS
para redhat 7
systemctl start nfs
systemctl start rpcbind
--Para validar el status, debe indicar running en color verde.
systemctl status nfs
systemctl status rpcbind

5) encender el havip

/u01/app/19.0.0.0/grid/bin/srvctl start havip -id hrexports

6) Montar el NFS en un destino, para ejemplo destino:

Montar con /etc/fstab
20.2.1.92:/origenfs /origenfs nfs rw,bg,rsize=32768,wsize=32768

o montar manual:

mount -t nfs -o rw,bg,rsize=32768,wsize=32768 10.5.1.192:/origenfs /origenfs --> Linux

Espero les sea de utilidad.

Saludos.

Envío de Correos con PLSQL desde Base de Datos Oracle

Raúl Antonio Molina Alvarenga

26 de abril de 2023

#OracleTipsSV

#OracleACE

El envío de correos desde la base de Datos Oracle usando PLSQL es algo común, y en cierta medida necesario, mucha tarea o control de actividades puede desenvolverse con el envío de un correo oportuno orquestado desde la base de datos.

Vamos a comenzar indicando que prefiero usar un PLSQL que complicarme la existencia usando Java para esta tarea, siendo así, hay que indicar que los paquetes de BD  necesarios para el mismo antes en algunas versiones viejas era requerido instalarlos.

sqlplus /nolog

connect / as sysdba

@?/rdbms/admin/utlmail.sql

@?/rdbms/admin/prvtmail.plb

grant execute on utl_mail to public; --> puede ser o debería 
ser a un usuario particular

Debemos definir los datos de nuestro SMTP, y si la bd es 11.1 o superior, debemos configurar las reglas de salida o trafico de salida de la BD con las ACLs y si es 19c las ACE.

alter system set smtp_out_server = 'TuSMTP' scope=both;

select * from dba_network_acls;

Si hubieran borra los que hayan, si no ignora, 

BEGIN

DBMS_NETWORK_ACL_ADMIN.DROP_ACL(

acl => 'mail_access.xml');

END;

/

BEGIN

DBMS_NETWORK_ACL_ADMIN.CREATE_ACL (

acl          => 'mail_access.xml',

description  => 'Permissions to access e-mail server.',

principal    => 'PUBLIC',

is_grant     => TRUE,

privilege    => 'connect');

COMMIT;

END;

/

BEGIN

DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL (

acl          => 'mail_access.xml',

host         => 'TUSMTP'

);

COMMIT;

END;

/

 

Luego preparamos las unidades PLSQL que permitirán el envío de los correos, totalmente personalizables, permiten hasta envio de adjuntos,  formateo HTML para los visores de correo mas modernos, etc.

 

CREATE OR REPLACE PROCEDURE send_mail (p_to        IN VARCHAR2,

                                       p_from      IN VARCHAR2,

                                       p_subject   IN VARCHAR2,

                                       p_message   IN VARCHAR2,

                                       p_smtp_host IN VARCHAR2,

                                       p_smtp_port IN NUMBER DEFAULT 25)

AS

  l_mail_conn   UTL_SMTP.connection;

BEGIN

  l_mail_conn := UTL_SMTP.open_connection(p_smtp_host, p_smtp_port);

  UTL_SMTP.helo(l_mail_conn, p_smtp_host);

  UTL_SMTP.mail(l_mail_conn, p_from);

  UTL_SMTP.rcpt(l_mail_conn, p_to);

  UTL_SMTP.open_data(l_mail_conn);

  

  UTL_SMTP.write_data(l_mail_conn, 'Date: ' || TO_CHAR(SYSDATE, 'DD-MON-YYYY HH24:MI:SS') || UTL_TCP.crlf);

  UTL_SMTP.write_data(l_mail_conn, 'To: ' || p_to || UTL_TCP.crlf);

  UTL_SMTP.write_data(l_mail_conn, 'From: ' || p_from || UTL_TCP.crlf);

  UTL_SMTP.write_data(l_mail_conn, 'Subject: ' || p_subject || UTL_TCP.crlf);

  UTL_SMTP.write_data(l_mail_conn, 'Reply-To: ' || p_from || UTL_TCP.crlf || UTL_TCP.crlf);

  

  UTL_SMTP.write_data(l_mail_conn, p_message || UTL_TCP.crlf || UTL_TCP.crlf);

  UTL_SMTP.close_data(l_mail_conn);

  UTL_SMTP.quit(l_mail_conn);

END;

/

Ejemplo para probarlo con cualquier usuario,  por ejemplo enviando correos desde tu ID de correo.

 create user ssa identified by admin;

 grant connect,resource,dba to admin;

grant execute on sys.send_mail to admin;

BEGIN

  sys.send_mail(p_to        => 'correo@dominio',

            p_from      => 'correo1@dominio',

            p_subject   => 'Test Message',

            p_message   => 'This is a test message.',

            p_smtp_host => 'mail.ssasis.com');

END;

/

/  2    3    4    5    6    7    8  

PL/SQL procedure successfully completed.

Pudiendo tener resultados como el siguiente:

DR SYNC STATUS REPORT FOR DATABASE: db
INST_NAME LOG_ARCHIVED LOG_APPLIED TIME_APPLIED LOG_GAP
bd1 302281 302279 26-Apr, 05:49:20 2
bd2 300298 300297 26-Apr, 05:53:55 1
bd3 290118 290117 26-Apr, 05:53:53 1

 

Espero les sea de utilidad!!.

Saludos

Como agregar un nodo a un Cluster de Oracle Database, en modo silencioso.

Raúl Antonio Molina Alvarenga

23 de Abril de 2023

#OracleTipsSV

#OracleACEAssociate

Es de lo más común  en proyectos de Alta Disponibilidad de Oracle Database, que los Clusters  nazcan con la cantidad requerida de Nodos de computo que albergaran a las instancias de Base de Datos, es lo de más común; pero eso no significa, que ante la necesidad, no podamos agregar o remover un nodo de un cluster activo.

Hay una master Note de MOS que nos hace un resumen de dicho procedimiento para todas las versiones actuales y anteriores de Software Oracle, y es que aunque en las ultimas versiones el procedimental sea de lo mas parecido, debemos ser conscientes que la infraestructura interna del software las cosas si han cambiado bastante.

El DOCID:

How to Add Node/Instance or Remove Node/Instance with Oracle Clusterware and RAC (Doc ID 1332451.1)

Nos enfocaremos en la guia Oficial de 11.2:

https://docs.oracle.com/cd/E14795_01/doc/rac.112/e10717/adddelclusterware.htm#CHDFIAIE

Nuestro ambiente:

NOTA:Omito temas de configuraciones, así como salidas de comandos, en esencia la guía, muestra la sintaxis valida de los comandos para agregar un nodo.

Nodos: sa-nodo01, sa-nodo02

Nuestros pasos:

Debemos validar que la equivalencia de usuarios( oracle y grid si es que así lo hemos aplicado el role separation), esta correctamente configurado

./sshUserSetup.sh -user grid -hosts “sa-nodo01 sa-nodo02” -advanced -noPromptPassphrase

./sshUserSetup.sh -user oracle -hosts "sa-nodo01 sa-nodo02" -advanced -noPromptPassphrase

Debemos validar que contamos con todos los discos de preferencia con los mismos nombres de dispositivos:

ASMCMD [+] > lsdsk -G dggrid

/dev/rdsk/c1d12s0

/dev/rdsk/c1d13s0

/dev/rdsk/c1d14s0

ASMCMD [+] > lsdsk -G dgnada

/dev/rdsk/c1d10s0

/dev/rdsk/c1d11s0

/dev/rdsk/c1d4s0

/dev/rdsk/c1d5s0

/dev/rdsk/c1d6s0

/dev/rdsk/c1d7s0

/dev/rdsk/c1d8s0

/dev/rdsk/c1d9s0

ASMCMD [+] > lsdsk -G dgarch

/dev/rdsk/c1d18s0

/dev/rdsk/c1d19s0

/dev/rdsk/c1d20s0

mid

ASMCMD [+] > lsdsk -G dgarch

/dev/rdsk/c1d23s0

/dev/rdsk/c1d24s0

/dev/rdsk/c1d25s0 —> 

ASMCMD [+] > lsdsk -G dggrid

/dev/rdsk/c1d10s0

/dev/rdsk/c1d11s0

/dev/rdsk/c1d9s0

ASMCMD [+] > lsdsk -G dgnada

/dev/rdsk/c1d12s0

/dev/rdsk/c1d13s0

/dev/rdsk/c1d14s0

/dev/rdsk/c1d15s0

/dev/rdsk/c1d16s0

/dev/rdsk/c1d18s0

/dev/rdsk/c1d19s0

/dev/rdsk/c1d20s0

/dev/rdsk/c1d21s0

/dev/rdsk/c1d22s0

meta

ASMCMD [+] > lsdsk -G dgnada

/dev/rdsk/c1d10s0

/dev/rdsk/c1d11s0

/dev/rdsk/c1d7s0

/dev/rdsk/c1d8s0

/dev/rdsk/c1d9s0

ASMCMD [+] > lsdsk -G dggrid

/dev/rdsk/c1d4s0

/dev/rdsk/c1d5s0

/dev/rdsk/c1d6s0

ASMCMD [+] > lsdsk -G dgarch

/dev/rdsk/c1d12s0

/dev/rdsk/c1d13s0

/dev/rdsk/c1d14s0

ASMCMD [+] >

chmod 660 /dev/rdsk/c1d10s0

chmod 660 /dev/rdsk/c1d11s0

chmod 660 /dev/rdsk/c1d7s0

chmod 660 /dev/rdsk/c1d8s0

chmod 660 /dev/rdsk/c1d9s0

chmod 660 /dev/rdsk/c1d4s0

chmod 660 /dev/rdsk/c1d5s0

chmod 660 /dev/rdsk/c1d6s0

chmod 660 /dev/rdsk/c1d12s0

chmod 660 /dev/rdsk/c1d13s0

chmod 660 /dev/rdsk/c1d14s0

chown grid:asmadmin /dev/rdsk/c1d10s0

chown grid:asmadmin /dev/rdsk/c1d11s0

chown grid:asmadmin /dev/rdsk/c1d7s0

chown grid:asmadmin /dev/rdsk/c1d8s0

chown grid:asmadmin /dev/rdsk/c1d9s0

chown grid:asmadmin /dev/rdsk/c1d4s0

chown grid:asmadmin /dev/rdsk/c1d5s0

chown grid:asmadmin /dev/rdsk/c1d6s0

chown grid:asmadmin /dev/rdsk/c1d12s0

chown grid:asmadmin /dev/rdsk/c1d13s0

chown grid:asmadmin /dev/rdsk/c1d14s0

También debemos entender y  contemplar que la infraestructura de red este en correcto funcionamiento, podemos usar la siguiente DOCID de MOS:

How to Validate Network and Name Resolution Setup for the Clusterware and RAC (Doc ID 1054902.1)

Si cuando se instalo el o los nodos originales se ignoro alguna revision, y no sabemos dicho resultado, podemos de antemano, obviar dichas validaciones estableciendo esta variable de ambiente en Y:

export IGNORE_PREADDNODE_CHECKS=Y

Una vez todo esta revisado y validado procedemos a desplegar 
el nodo nuevo agregandolo a la capa de GI
cd $ORACLE_HOME/oui/bin

./addNode.sh -silent "CLUSTER_NEW_NODES={sa-nodo02}" "CLUSTER_NEW_VIRTUAL_HOSTNAMES={sa-nodo02-vip}"

Ahora, debemos agregar la capa de software del RDBMS, usualmente con el usuario oracle.

##oracle

cd $ORACLE_HOME/oui/bin

./addNode.sh -silent "CLUSTER_NEW_NODES={sa-nodo02}"

Ahora debemos agregar la siguiente instancia que se ejecutara en el nodo recién agregado, vamos a extender la BD o las BDs en 1 instancia adicional:

dbca -silent -addInstance -nodeList sa-nodo02 -gdbName osmdata -instanceName osmdata2 -sysDBAUserName sys -sysDBAPassword oracle11g

dbca -silent -addInstance -nodeList sa-nodo02 -gdbName ocpdb -instanceName ocpdb2 -sysDBAUserName sys -sysDBAPassword oracle11g

dbca -silent -addInstance -nodeList sa-nodo02 -gdbName cepdb -instanceName cepdb2 -sysDBAUserName sys -sysDBAPassword oracle11g

dbca -silent -addInstance -nodeList sa-nodo02 -gdbName osmdata -instanceName osmdata2 -sysDBAUserName sys -sysDBAPassword oracle11g

dbca -silent -addInstance -nodeList sa-nodo02 -gdbName load -instanceName load2 -sysDBAUserName sys -sysDBAPassword oracle11g

El resultado final, un cluster con 2 nodos:

grid@sa-nodo02:~$ crs_stat -t

Name           Type           Target    State     Host        

------------------------------------------------------------

ora.DGARCH.dg  ora....up.type ONLINE    ONLINE    sa-nodo01

ora.DGGRID.dg  ora....up.type ONLINE    ONLINE    sa-nodo01

ora.DGnada.dg  ora....up.type ONLINE    ONLINE    sa-nodo01

ora....ER.lsnr ora....er.type ONLINE    ONLINE    sa-nodo01

ora....N1.lsnr ora....er.type ONLINE    ONLINE    sa-nodo02

ora....N2.lsnr ora....er.type ONLINE    ONLINE    sa-nodo01

ora....N3.lsnr ora....er.type ONLINE    ONLINE    sa-nodo01

ora.asm        ora.asm.type   ONLINE    ONLINE    sa-nodo01

ora.cepdb.db   ora....se.type ONLINE    ONLINE    sa-nodo01

ora.cvu        ora.cvu.type   ONLINE    ONLINE    sa-nodo02

ora.esbdata.db ora....se.type ONLINE    ONLINE    sa-nodo01

ora.gsd        ora.gsd.type   OFFLINE   OFFLINE               

ora....network ora....rk.type ONLINE    ONLINE    sa-nodo01

ora.oc4j       ora.oc4j.type  ONLINE    ONLINE    sa-nodo02

ora.ocpdb.db   ora....se.type ONLINE    ONLINE    sa-nodo01

ora.ons        ora.ons.type   ONLINE    ONLINE    sa-nodo01

ora.osmdata.db ora....se.type ONLINE    ONLINE    sa-nodo01

ora....ry.acfs ora....fs.type ONLINE    ONLINE    sa-nodo01

ora....SM1.asm application    ONLINE    ONLINE    sa-nodo01

ora....01.lsnr application    ONLINE    ONLINE    sa-nodo01

ora....b01.gsd application    OFFLINE   OFFLINE               

ora....b01.ons application    ONLINE    ONLINE    sa-nodo01

ora....b01.vip ora....t1.type ONLINE    ONLINE    sa-nodo01

ora....SM2.asm application    ONLINE    ONLINE    sa-nodo02

ora....02.lsnr application    ONLINE    ONLINE    sa-nodo02

ora....b02.gsd application    OFFLINE   OFFLINE               

ora....b02.ons application    ONLINE    ONLINE    sa-nodo02

ora....b02.vip ora....t1.type ONLINE    ONLINE    sa-nodo02

ora.scan1.vip  ora....ip.type ONLINE    ONLINE    sa-nodo02

ora.scan2.vip  ora....ip.type ONLINE    ONLINE    sa-nodo01

ora.scan3.vip  ora....ip.type ONLINE    ONLINE    sa-nodo01

ps -fea | grep pmon

    grid 21207     1   0 21:47:06 ?           0:01 asm_pmon_+ASM2

  oracle  5566     1   0 22:25:00 ?           0:00 ora_pmon_osmdata2

  oracle  7364     1   0 22:29:42 ?           0:00 ora_pmon_ocpdb2

  oracle  9184     1   0 22:34:28 ?           0:00 ora_pmon_cepdb2

  oracle  9886     1   0 22:35:42 ?           0:00 ora_pmon_esbdata2

    grid 10189  9429   0 22:36:31 pts/1       0:00 grep pmon

grid@sa-nodo02:~$ crs_stat -t

Name           Type           Target    State     Host        

------------------------------------------------------------

ora.DGARCH.dg  ora....up.type ONLINE    ONLINE    sa-nodo01

ora.DGGRID.dg  ora....up.type ONLINE    ONLINE    sa-nodo01

ora.DGnada.dg  ora....up.type ONLINE    ONLINE    sa-nodo01

ora....ER.lsnr ora....er.type ONLINE    ONLINE    sa-nodo01

ora....N1.lsnr ora....er.type ONLINE    ONLINE    sa-nodo02

ora....N2.lsnr ora....er.type ONLINE    ONLINE    sa-nodo01

ora....N3.lsnr ora....er.type ONLINE    ONLINE    sa-nodo01

ora.asm        ora.asm.type   ONLINE    ONLINE    sa-nodo01

ora.cepdb.db   ora....se.type ONLINE    ONLINE    sa-nodo01

ora.cvu        ora.cvu.type   ONLINE    ONLINE    sa-nodo02

ora.esbdata.db ora....se.type ONLINE    ONLINE    sa-nodo01

ora.gsd        ora.gsd.type   OFFLINE   OFFLINE               

ora....network ora....rk.type ONLINE    ONLINE    sa-nodo01

ora.oc4j       ora.oc4j.type  ONLINE    ONLINE    sa-nodo02

ora.ocpdb.db   ora....se.type ONLINE    ONLINE    sa-nodo01

ora.ons        ora.ons.type   ONLINE    ONLINE    sa-nodo01

ora.osmdata.db ora....se.type ONLINE    ONLINE    sa-nodo01

ora....ry.acfs ora....fs.type ONLINE    ONLINE    sa-nodo01

ora....SM1.asm application    ONLINE    ONLINE    sa-nodo01

ora....01.lsnr application    ONLINE    ONLINE    sa-nodo01

ora....b01.gsd application    OFFLINE   OFFLINE               

ora....b01.ons application    ONLINE    ONLINE    sa-nodo01

ora....b01.vip ora....t1.type ONLINE    ONLINE    sa-nodo01

ora....SM2.asm application    ONLINE    ONLINE    sa-nodo02

ora....02.lsnr application    ONLINE    ONLINE    sa-nodo02

ora....b02.gsd application    OFFLINE   OFFLINE               

ora....b02.ons application    ONLINE    ONLINE    sa-nodo02

ora....b02.vip ora....t1.type ONLINE    ONLINE    sa-nodo02

ora.scan1.vip  ora....ip.type ONLINE    ONLINE    sa-nodo02

ora.scan2.vip  ora....ip.type ONLINE    ONLINE    sa-nodo01

ora.scan3.vip  ora....ip.type ONLINE    ONLINE    sa-nodo01

Espero les sea de utilidad.

Saludos!!

De la guia:

Adding a Cluster Node on Linux and UNIX Systems

This procedure describes how to add a node to your cluster. This procedure assumes that:

  • There is an existing cluster with a node named node1
  • You are adding a node named node2
  • You have successfully installed Oracle Clusterware on node1 in a nonshared home, where Grid_home represents the successfully installed home

To add a node:

  1. Ensure that you have successfully installed Oracle Clusterware on at least one node in your cluster environment. To perform the following procedure, Grid_home must identify your successfully installed Oracle Clusterware home.

    See Also:

    Oracle Grid Infrastructure Installation Guide for Oracle Clusterware installation instructions

  2. Verify the integrity of the cluster and node2:
    $ cluvfy stage -pre nodeadd -n node2 [-fixup [-fixupdir fixup_dir]] [-verbose]
    

    You can specify the -fixup option and a directory into which CVU prints instructions to fix the cluster or node if the verification fails.

  3. Navigate to the Grid_home/oui/bin directory on node1 and run the addNode.sh script using the following syntax, where node2 is the name of the node that you are adding and node2-vip is the VIP name for the node:If you are using Grid Naming Service (GNS):
    $ ./addNode.sh -silent "CLUSTER_NEW_NODES={node2,node3}"
    

    If you are not using GNS:

    $ ./addNode.sh -silent "CLUSTER_NEW_NODES={node2,node3}""CLUSTER_NEW_VIRTUAL_HOSTNAMES={node2-vip,node3-vip}" 
    

    Alternatively, you can specify the entries shown in Example 4-1 in a response file, where file_name is the name of the file, and run the addNode.sh script, as follows:

    $ addNode.sh -silent -responseFile file_name
    

    When prompted, run root.sh before the addNode.sh script completes.

 

Historial del Crecimiento del Tamaño de la Base de Datos Oracle

Raúl Antonio Molina Alvarenga

19 de Abril de 2023

#OracleACE

#OracleTipsSV

A veces nos hacen la pregunta, cuanto espacio debemos reservar para el crecimiento a futuro de la base de datos, o cuanto espacio hemos consumido en un año anterior.

Esa información de forma natural en la base de datos, sin precalcularlo es un poco complejo obtenerla, especialmente si no tenemos vistas históricas que se obtienen con EE y Packs de diagnóstico y tuneo.

Aquí un pequeño TIP para poder calcular dicha información y almacenarlo, no considera el UNDO  y TEMP, solo Información real de usuario.

Crear Tabla que almacenara la información histórica.

create table db_space_hist (

timestamp    date,

total_space  number(8),

used_space   number(8),

free_space   number(8),

        pct_inuse    number(5,2),

        num_db_files number(5)

);

 

Crear procedimiento de colección de Información:

CREATE OR REPLACE PROCEDURE db_space_history AS

BEGIN

   INSERT INTO db_space_hist 

SELECT SYSDATE, total_space,

        total_space-NVL(free_space,0) used_space,

        NVL(free_space,0) free_space,

        ((total_space - NVL(free_space,0)) / total_space)*100 pct_inuse,

        num_db_files

 FROM ( SELECT SUM(bytes)/1024/1024 free_space

        FROM   sys.DBA_FREE_SPACE WHERE tablespace_name NOT LIKE '%UNDO%') FREE,

      ( SELECT SUM(bytes)/1024/1024 total_space,

               COUNT(*) num_db_files

        FROM   sys.DBA_DATA_FILES WHERE tablespace_name NOT LIKE '%UNDO%') FULL;

   COMMIT;

END;

/

Crear el JOB que calculara la información, la Frecuencia puede ser la deseada, o necesitada, diaria, semanal , mensual.(Puede usarse o mejor dicho usar Scheduler JOBS).

DECLARE

  X NUMBER;

BEGIN

  SYS.DBMS_JOB.SUBMIT

    (

      job        => X

     ,what       => 'OBS.DB_SPACE_HISTORY;'

     ,next_date  => sysdate+1

     ,INTERVAL   => 'TRUNC(SYSDATE+7)'

     ,no_parse   => FALSE

    );

END;

La información se consulta asi:

select * from db_space_hist order by timestamp desc;

Espero les sea de Utilidad

Saludos.