domingo, 12 de febrero de 2023

Check this week's agenda with upcoming events from Oracle and the DBA Community!

 By GREPORA EXPERTISE

What's up this week?


Check this week's agenda with upcoming events
from Oracle and the DBA Community!

15/02

RMOUG Training Days 2023
#Community #online #InPerson

We’re excited to announce our Training Days 2023 Conference Agendas are packed with over 130 Technical Sessions, and 11 Workshops covering a wide range of topics, including Analytics, Big Data, Application Development, Cloud, Database Administration, and more.

See more!


Migrate Oracle Databases to on-premises and cloud with a Safety Net using Migration Workbench

#Community #AIOUG #online

Join this live demo session and Learn how to migrate databases to Exadata on-premises, to Exadata Database Service (Shared, Dedicated, or Cloud@Customer), to Autonomous, and to Base Database Service (SI, RAC, BM, or VM). Find out how SQL queries of migrated databases are automatically validated for high performance along with recommendations leveraging integrated SQL Performance Analyzer (SPA), thus ensuring your business applications continue to perform as per your requirements.

See more!

16/02

Next Level Oracle Monitoring | Options, Features, Deep-Dive
#community #UKOUG #online

Performance and availability, and moreover, Oracle observability, are the hot topics for the next decade. Get a guided tour on advanced Oracle monitoring based on Microsoft System Center Operations Manager, run by the NiCE Product Experts. The NiCE Oracle Management Pack, in conjunction with one of the big players in IT Operations Management, easily enables end-to-end Oracle observability and thus helps reduce risk and downtime.

See more!

17/02

Oracle Analytics Cloud and the No Code Predictive Analytics
#Community #AIOUG #online

Are you naive when it comes to making predictions using Machine learning models? Well, Oracle Analytics, with its robust Machine Learning capabilities, is here to your rescue. Without a single line of code written, here is your chance to experience OAC’s power to predict valuable results to derive meaningful insights that are critical to business.

See more!


OATUG TECH SIG TALK: PATCHING TIPS AND TRICKS PANEL

#Community #OATUG #online

Online patching has changed many things in the life of an EBS DBA. Please join our panel as we pass on some of the things we do to as part of using online patching on our EBS environments. After sharing tips and tricks, the panel will answer questions from the attendees.

See more!


martes, 7 de febrero de 2023

Planned Maintenance to My Oracle Support Portal on Friday February 10, 2023

Planned Maintenance to My Oracle Support Portal on Friday February 10, 2023

My Oracle Support Portal (MOS) will be undergoing maintenance from Friday Feb 10, 2023, 7:00 PM PST to Saturday Feb 11, 2023, 7:30 AM PST.

During the maintenance period you will not be able to create, view, or update SRs through our Customer Support portals. Oracle Support Services will continue to be available and can be reached via telephone for any critical issues that need immediate attention. In addition, access to Oracle Knowledge Base will be available from https://support-lite.oracle.com and you will be able to use MOS Communities at https://community.oracle.com. If you are using Oracle monitoring services like ASR and Platinum, these will continue to monitor your systems. However, the creation and update of Service Requests will occur after the planned maintenance if required.

You can find the telephone numbers for your location at Oracle Support Center.

miércoles, 1 de febrero de 2023

Historial de acciones sobre los PDBs de un Contenedor de Base de Datos

Cada acción que se realiza sobre un PDB en un contenedor de base de datos, deja huella registrada.

Con la siguiente consulta en el contenedor de la base de datos, puedes obtener el historial de dichas acciones.

SQL> @fecha_pdbs.sql

DB_NAME    CON_ID PDB_NAME        OPERATION        OP_TIMESTA CLONED_FROM_PDB
---------- ------ --------------- ---------------- ---------- ---------------
G6486           3 PDB$SEED        UNPLUG           09-JAN-20
G6486           4 PDB$SEED        UNPLUG           09-JAN-20
G6486           5 PDB$SEED        UNPLUG           09-JAN-20
G6486           6 PDB$SEED        UNPLUG           09-JAN-20
G6486           7 PDB$SEED        UNPLUG           09-JAN-20
DBMIGRA         3 PDB$SEED        PLUG             04-FEB-21  PDB$SEED
DBMIGRA         4 PDB$SEED        PLUG             04-FEB-21  PDB$SEED
DBMIGRA         5 PDB$SEED        PLUG             04-FEB-21  PDB$SEED
DBMIGRA         6 PDB$SEED        PLUG             04-FEB-21  PDB$SEED
DBMIGRA         7 PDB$SEED        PLUG             04-FEB-21  PDB$SEED
DBMIGRA         3 PDB1            CREATE           04-FEB-21  PDB$SEED
DBMIGRA         4 FCUBSUAT        CREATE           14-DEC-22  PDB$SEED
DBMIGRA         5 OBDXUAT         CREATE           14-DEC-22  PDB$SEED
DBMIGRA         6 OBBRNUAT        CREATE           14-DEC-22  PDB$SEED
DBMIGRA         7 FISERESUAT      CREATE           14-DEC-22  PDB$SEED

15 rows selected.


SQL> host more fecha_pdbs.sql
set pagesize 20
COLUMN DB_NAME FORMAT A10
COLUMN CON_ID FORMAT 999
COLUMN PDB_NAME FORMAT A15
COLUMN OPERATION FORMAT A16
COLUMN OP_TIMESTAMP FORMAT A10
COLUMN CLONED_FROM_PDB_NAME FORMAT A15

SELECT DB_NAME, CON_ID, PDB_NAME, OPERATION, OP_TIMESTAMP, CLONED_FROM_PDB_NAME
FROM CDB_PDB_HISTORY
WHERE CON_ID > 2
ORDER BY OP_TIMESTAMP,CON_ID
/



OCI Oracle Linux: SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptable' ...

He notado en algunos de mis servicios con Oracle Linux en la nube un error particular en el estado del servicio del FIREWALL.

Cuando reviso el estado, el mismo me arroja una serie de mensajes incómodos de "WARNINGS" como se muestra a continuación:

[root@SRV-AUDIT yum.repos.d]# systemctl status firewalld

? firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2022-11-01 08:16:42 CST; 4s ago
Docs: man:firewalld(1)
Main PID: 29173 (firewalld)
Tasks: 2
CGroup: /system.slice/firewalld.service
+-29173 /usr/bin/python2 -Es /usr/sbin/firewalld --nofork --nopid


Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --destination 192.168.122.0/24 --o...at chain?).

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --source 192.168.122.0/24 --in-int...at chain?).

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --in-interface virbr0 --out-interf...at chain?).

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --out-interface virbr0 --jump REJE... that name.

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --in-interface virbr0 --jump REJEC... that name.

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete INPUT --in-interface virbr0 --protocol udp...at chain?).

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete INPUT --in-interface virbr0 --protocol tcp...at chain?).

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete OUTPUT --out-interface virbr0 --protocol u...at chain?).

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete INPUT --in-interface virbr0 --protocol udp...at chain?).

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete INPUT --in-interface virbr0 --protocol tcp...at chain?).

Hint: Some lines were ellipsized, use -l to show in full.

Investigando un poco encontre que deshabilitando el "libvirtd" se soluciona el problema. Como pueden comprobar a continuación, una vez deshabilitado y reiniciado el servicio del FIREWALL, ya no tenemos el mensaje de precaución.

[root@SRV-AUDIT yum.repos.d]# systemctl stop libvirtd
[root@SRV-AUDIT yum.repos.d]# systemctl disable libvirtd

Removed symlink /etc/systemd/system/multi-user.target.wants/libvirtd.service.
Removed symlink /etc/systemd/system/sockets.target.wants/virtlogd.socket.
Removed symlink /etc/systemd/system/sockets.target.wants/virtlockd.socket.

[root@SRV-AUDIT yum.repos.d]# systemctl status firewalld
? firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2022-11-01 08:16:42 CST; 2min 48s ago
Docs: man:firewalld(1)
Main PID: 29173 (firewalld)
CGroup: /system.slice/firewalld.service

+-29173 /usr/bin/python2 -Es /usr/sbin/firewalld --nofork --nopid


Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --destination 192.168.122.0/24 --o...at chain?).
Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --source 192.168.122.0/24 --in-int...at chain?).
Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --in-interface virbr0 --out-interf...at chain?).
Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete FORWARD --out-interface virbr0 --jump REJE... that name.
....
Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete INPUT --in-interface virbr0 --protocol udp...at chain?).

Nov 01 08:16:43 SRV-AUDIT firewalld[29173]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --delete INPUT --in-interface virbr0 --protocol tcp...at chain?).

Hint: Some lines were ellipsized, use -l to show in full.

[root@SRV-AUDIT yum.repos.d]# systemctl restart firewalld

[root@SRV-AUDIT yum.repos.d]# systemctl status firewalld
? firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)

Active: active (running) since Tue 2022-11-01 08:20:02 CST; 4s ago
Docs: man:firewalld(1)
Main PID: 5063 (firewalld)
Tasks: 2
CGroup: /system.slice/firewalld.service
+-5063 /usr/bin/python2 -Es /usr/sbin/firewalld --nofork --nopid

Nov 01 08:20:02 SRV-AUDIT systemd[1]: Starting firewalld - dynamic firewall daemon...
Nov 01 08:20:02 SRV-AUDIT systemd[1]: Started firewalld - dynamic firewall daemon.
[root@SRV-AUDIT yum.repos.d]# systemctl status firewalld

? firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2022-11-01 08:20:02 CST; 12s ago
Docs: man:firewalld(1)
Main PID: 5063 (firewalld)
Tasks: 2
CGroup: /system.slice/firewalld.service
+-5063 /usr/bin/python2 -Es /usr/sbin/firewalld --nofork --nopid

Nov 01 08:20:02 SRV-AUDIT systemd[1]: Starting firewalld - dynamic firewall daemon...
Nov 01 08:20:02 SRV-AUDIT systemd[1]: Started firewalld - dynamic firewall daemon.
[root@SRV-AUDIT yum.repos.d]#

El programa libvirtd es el componente daemon del lado del servidor del sistema de administración de virtualización libvirt. 

Este demonio se ejecuta en servidores host y realiza las tareas de administración requeridas para invitados virtualizados. Esto incluye actividades como iniciar, detener y migrar invitados entre servidores host, configurar y manipular redes y administrar el almacenamiento para uso de los invitados. 

Las bibliotecas y utilidades del cliente libvirt se conectan a este daemon para ejecutar tareas y recopilar información sobre la configuración y los recursos del sistema host y los invitados.

Según la documentación, el LIBVIRT Daemon, se ejecuta como un servicio SYSTEMD monolítico en Oracle Linux 7 y Oracle Linux 8.  Mientras que en Oracle Linux 9, el servicio se divide en múltiples sockets de servicios funcionales para un mayor control atómico y registro de cada componenente de virtualización.

En Oracle Linux 9

Los componentes o controladores funcionales individuales se modularizan en demonios separados que se exponen mediante tres sockets systemd para cada controlador.

Los siguientes demonios systemd están definidos para controladores individuales libvirt específicamente para KVM:
  • virtqemud: es el demonio de gestión de QEMU, para ejecutar máquinas virtuales en KVM.
  • virtnetworkd: es el demonio de gestión de red virtual.
  • virtnodedevd: es el daemon de administración de dispositivos físicos del host.
  • virtnwfilterd: es el demonio de gestión del cortafuegos del host.
  • virtsecretd: es el demonio de gestión de secretos del host.
  • virtstoraged: es el demonio de administración de almacenamiento del host.
  • virtinterfaced: es el demonio de administración de la tarjeta de interfaz de red (NIC) del host.
Todos los demonios de virtualización deben estar ejecutándose para exponer la funcionalidad de virtualización completa disponible en libvirt.



Todos los Sábados a las 8:00PM

Optimismo para una vida Mejor

Optimismo para una vida Mejor
Noticias buenas que comentar