Sadan's Oracle dba Blog

 # -*- mode: ruby -*- # vi: set ft=ruby : Vagrant.configure("2") do |config|   config.vm.provider "virtualbox" do |v|   v.memory = 2048   v.cpus = 2   end         # Every Vagrant virtual environment requires a box to build off of.   config.vm.box = "almalinux/9"   #config.vm.box_version = "20251010.1.3"   #config.disksize.size = '25GB'   #config.vm.disk :disk, size: "25GB", primary: true   #config.vm.provision "shell", path: "disk-extend.sh"   #config.vm.provision "file", source: "~/.ssh/id_rsa.pub", destination: "~/.ssh/id_rsa.pub"   #config.ssh.insert_key = false   #config.ssh.private_key_path = "~/.vagrant.d/insecure_private_key"     # Boot with a GUI so you can see the screen. (Default is headless)   #config.vm.boot_mode = :gui   #   # Targets   #   config.vm.define :pgnode1 do |target_config|     target_config.vm.host_name = 'pgnode1'     ...

To install postgres software  --------------------------------------------  sudo dnf install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-9-x86_64/pgdg-redhat-repo-latest.noarch.rpm PS C:\Users\user\Desktop\vagrant> cd E:\vagrant PS E:\vagrant> vagrant status Current machine states: pgnode1                   running (virtualbox) pgnode2                   running (virtualbox) pgnode3                   running (virtualbox) pgnode4                   running (virtualbox) This environment represents multiple VMs. The VMs are all listed above with their current state. For more information about a specific VM, run `vagrant status NAME`. PS E:\vagrant> PS E:\vagrant> vagrant up S E:\vagrant> vagrant status To login to machine  --------------------------...

  yum install -y oracle-database-preinstall-19c groupadd asmadmin groupadd asmdba groupadd asmoper useradd -g oinstall -G asmadmin,asmdba,asmoper grid usermod -G asmdba -a oracle systemctl stop avahi-daemon.service systemctl stop avahi-daemon.socket systemctl disable avahi-daemon.service systemctl disable avahi-daemon.socket mkdir -p /u01/app/oraInventory chown grid:oinstall /u01/app/oraInventory chmod 775 /u01/app/oraInventory mkdir -p /u01/app/grid chown grid:oinstall /u01/app/grid chmod 775 /u01/app/grid mkdir -p /u01/app/21.1.0/grid chown grid:oinstall /u01/app/21.1.0/grid mkdir -p /u01/gridtmp chown grid:oinstall /u01/gridtmp chmod 775 /u01/app/21.1.0/grid mkdir -p /u01/app/oracle chown oracle:oinstall /u01/app/oracle mkdir -p /u01/oratmp chown oracle:oinstall /u01/oratmp chmod 775 /u01/app/oracle mkdir -p /u01/app/oracle/product/21.1.0/dbhome_1 chown -R oracle:oinstall /u01/app/oracle/product/21.1.0/dbhome_1 chmod -R 775 /u01/app/oracle/product/21.0.0/dbhome_1 mkdir -p /u01/s...

  Oracle OEM Holistic Patch  The Concept Starting with Oracle Enterprise Manager (OEM) 13.5 RU24 (October 2024), Oracle introduced the Holistic Patch for OEM — a unified patching model that consolidates several separate updates into a single coordinated package. Previously, administrators had to patch: * The OMS and Agents with the quarterly Release Update (RU). * OEM Application via the System Patch Bundle (SPB). * WebLogic CPU and JDK manually. There was an element of complication because of the need to keep the solution homogeneous. With the Holistic Patch, the last two steps are merged into a single patch bundle. Now we have a new Holistic patch for OEM that is released with each new OMS Release Update. Prerequisites Apply RU 24 Patch  PATCH 36761595  /later on all OMSes before applying Oct Holistic Patch   PATCH 37305292             (OR) Apply RU 25 Patch  PATCH 37057635  /later on all OMSes before applying ...

https://www.dbamaster.com/2025/03/oracle-database-19c-performance-tunning.html https://www.dbamaster.com/p/postgresql_31.html https://www.dbamaster.com/p/mysql_31.html

  REPLICATION 1.replication prerequisites: 1. Verify connectivity between publisher, distributor and subscriber. Ifyou are unable to access then have your network team to open firewall ruleso that these servers can communicate. 2. You need to be sysadmin in order to setup replication. 3. Primary Key for each table. That should be fine anyway as it alreadyhas replication setup. 4. Allocate enough space for Transaction log 5. Do not use explicit transactions in trigger at the subscriber if you currently have because that can raise error sometimes. 2. Replication Agents Behaviour? Replication Agents The following are the replication agents and let us discuss each one of those in detail. *  Snapshot Agent  – It is used for creating and propagating the snapshots used in snapshot replication. Each Published database has its own Snapshot Agent that runs on the distributor and connects to the publisher and takes a snapshot of the objects. It then updates the information in the di...

AlwaysOn Availability Groups - FAQ     1. Which SQL Server Editions include AlwaysOn Availability Group functionality?     SQL Server Enterprise Edition   2. Do I need to use a specific Windows Server edition with AlwaysOn Availability        Groups?     You need to use Windows Server Enterprise above         3. What are the prerequisites for AlwaysOn Availability Groups? More information can be found here  http://msdn.microsoft.com/en-us/library/ff878487.aspx   4. How many replicas can I have in an AlwaysOn Availability Group? 5 total – 1 primary and up to 4 secondaries   5. How many databases can participate in an AlwaysOn Availability Group? Up to 100 is the recommendation, but it’s not enforced   6. How many AlwaysOn Availability Groups can I have on an instance? Up to 10 availability groups is the recommen...