Database With SanGa

1. Install Mail Packages    yum install postfix mailx cyrus-sasl cyrus-sasl-plain -y 2. Create GMail Account    a) Generate App Password 3. Edit sasl_password file and add gmail account details    vi /etc/postfix/sasl_passwd    [smtp.gmail.com]:587 <emailid>@gmail.com:********** 4. Generate DB file    postmap /etc/postfix/sasl_passwd 5. Edit main.cf    relayhost = [smtp.gmail.com]:587    myhostname = oracle-vm.com    # Enable SASL authentication for postfix    smtp_use_tls = yes                                                                                     smtp_sasl_auth_enable = yes       smtp_tls_security_level = encrypt    smtp_tls_CAfile = /et...

----------------------------------------------------------------------------------------------------------------------------- To increase the size limit of the Datafile, use the following SQL command: Increasing the Size Limit ALTER DATABASE DATAFILE '/U01/ORADATA/SANGA.DBF' AUTOEXTEND ON MAXSIZE 4096M; In this command, we are adjusting the maximum size of the Datafile to 4096MB (4GB). This change ensures that the Datafile can automatically extend its size up to the specified limit when it reaches capacity.   Removing the Size Limit In certain scenarios, you may want to remove the size limit altogether to allow the Datafile to grow without any restrictions. To achieve this, use the following SQL command in Oracle Database Enterprise Manager: ALTER DATABASE DATAFILE ‘/U01/ORADATA/SANGA.DBF’ AUTOEXTEND ON MAXSIZE UNLIMITED; With this command, the size limit on the Datafile is set to "UNLIMITED," allowing it to grow dynamically without any predefined rest...

  MySQL Cluster and MySQL Master-Slave replication are two different approaches to achieve high availability and scalability in a MySQL database environment. Table 1: Summary of MySQL Cluster vs MySQL Master-Slave   MySQL Cluster MySQL Master-Slave Architecture:   It is a distributed, shared-nothing architecture where multiple nodes (data nodes and management nodes) work together to provide high availability and data distribution. Data is automatically partitioned and replicated across nodes.   It follows a traditional master-slave replication model where one server acts as the master, handling both read and write operations, while one or more slave servers replicate data from the master to handle read operations.   High Availability:   Provides automatic data distribution, data redundancy, and built-in failover mechanisms, making it highly avail...

There was an issue regarding expired archives did not clear  at standby  as scheduled and following error was raise. RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of delete command at 07/09/2023 16:00:03 ORA-06540: PL/SQL: compilation error ORA-06553: PLS-252: reference to the wrong copy of package STANDARD Recovery Manager complete. SOLUTION: 1. Restart the standby database 2. Flush shared pool t o clear the whole shared pool you would issue the following command from a privileged user. ALTER SYSTEM FLUSH SHARED_POOL;

In my case I was tried to get RMAN full backup from my prod database. While connecting with RMAN Command window getting the following errors: RMAN-06438: error executing package DBMS_RCVMAN in TARGET database RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ============= RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed RMAN-06429: TARGET database is not compatible with this version of RMAN Cause “SYS.DBMS_RCVMAN” package has error which causing the problem. May be package is in-valid state. Solution 1. We tried to check in target database if it’s invalid. select OWNER, STATUS, substr(OBJECT_NAME,1,40), OBJECT_TYPE from DBA_OBJECTS where OBJECT_NAME IN ('DBMS_RCVMAN', 'DBMS_BACKUP_RESTORE' ) ; 2. Try to recompile it and check the status. @$ORACLE_HOME/rdbms/admin/utlrp.sql 3. If 2nd steps is not worki...

In my case there are two oracle homes. so when I schedule a cron job for archive clearing following error was raised. Recovery Manager: Release 11.2.0.4.0 - Production on Wed May 17 13:41:49 2023 Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved. RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed RMAN-03000: recovery manager compiler component initialization failed RMAN-06035: wrong version of recover.bsq, expecting 11.2.0.4, found 11.2.0.2 SOLUTION: I have added following line to the oraenv file.  export PATH=$ORACLE_HOME/bin:$PATH

STANDBY LOGS Get relevant details from primary side SQL> select GROUP#,BLOCKSIZE,THREAD# from v$standby_log;     GROUP#  BLOCKSIZE    THREAD# ---------- ---------- ----------          9        512          1         10        512          1         11        512          1         12        512          1         13        512          1         14        512          2         15        512          2         16        512          2   ...