foalabs

RMAN-08120- Archive Logs Are Not Being Removed By RMAN Error: While deleting archive logs we are observing error as below RMAN-08120: warning: archived log not deleted, not yet applied by standby Solution: When I checked the Datagaurd was in sync with primary. But there was some old entry still pending which is no more in configuration. Please check Destinations that are marked DEFERRED (and valid_now='UNKNOWN')     SQL> SELECT * from v$archive_dest where (valid_now = 'UNKNOWN' AND status = 'DEFERRED') ; If the above query returns a row (rows), then you have some destinations that are marked DEFERRED. Disable the log archive destination   SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_N = '' SCOPE = BOTH;       'n' id the dest_id for the deferred destinations If you like please follow and comment

RMAN-08138: WARNING: archived log not deleted When trying to delete archive log we might see below error when archives are already applied to standby database. RMAN-08138: WARNING: archived log not deleted - must create more backups We do not need a backup of archived logs on standby site if backup is already configured on the primary database.Same error may come be returned on primary database as well while deleting archived logs without taking a backup. RMAN> delete archivelog logseq  12342; using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=1221 instance=gold device type=DISK RMAN-08138: WARNING: archived log not deleted - must create more backups Set the archived logs deletion policy to “APPLIED ON ALL STANDBY” only and it should not be configured to have at least one backup before it could be deleted. Current Policy RMAN> show archivelog deletion policy; RMAN configuration parameters for database with...

DCS-10045: Validation error encountered: Backup password is mandatory to take OSS backup for non-tde enabled database on Oracle Cloud DB backup I ssue: Post migration, Automatic Backup fails with the following error for non-TDE enabled migrated Oracle Database releases 11.2.0.4 and 12.1.0.2.   DCS-10045: Validation error encountered: Backup password is mandatory to take OSS backup for non-tde enabled database...   Solution:   Find the TDE wallet location. The Oracle Cloud Infrastructure provisioned database instance will have following entry in sqlnet.ora. ENCRYPTION_WALLET_LOCATION=(SOURCE=(METHOD=FILE) (METHOD_DATA=(DIRECTORY=/opt/oracle/dcs/commonstore/wallets/ tde/$ORACLE_UNQNAME))) Remove the cwallet.sso file from the wallet location. For example, /opt/oracle/dcs/commonstore/wallets/tde/$ORACLE_UNQNAME.   Oracle Database 11g Release 2, do the folowing steps. location.   Check the wallet status select * from v$encryption_wallet; WRL_TYPE --------------------...

OCI: Automatic Backup Failed With DCS-10013 :'OMF PARAMETERS' CONTAINS UNACCEPTABLE VALUE Error: When running the automatic backup from OCI, it was failing. When checked further below error was seen. "status" : "Failure", "message" : "DCS-10013:Input parameter 'OMF parameters' contains unacceptable value : {1} .OMF parameter value found as null in Database", "reports" : [ { More details can be captured from DBCS system below commands or dcs agent logs. # /opt/oracle/dcs/bin/dbcli list-jobs | grep 'Failure' #/opt/oracle/dcs/bin/dbcli describe-job -i 01279373-2649-499f-8d8]6-c5811221504 Reasons for Failure Check below parameters in database and make sure there values are set properly. Do show parameter and check these parameter values. SPFILE DB_CREATE_FILE_DEST DB_CREATE_ONLINE_LOG_DEST_1 DB_RECOVERY_FILE_DEST Solution: In my case the spfile was fine but other three I needed to set SQL> show parameter spfile NA...

Activate Standby Database when the Primary Database is not available My Primary database is not accessible and server is crashed so we can open the standby database for use. Steps:   1. Start the standby database in mount stage shut immediate; startup mount; 2. Check the standby database protection_mode and database_role SQL> SELECT OPEN_MODE,PROTECTION_MODE,DATABASE_ROLE FROM V$DATABASE; OPEN_MODE PROTECTION_MODE DATABASE_ROLE ---------- -------------------- ---------------- MOUNTED MAXIMUM PERFORMANCE PHYSICAL STANDBY NOTE: If protection_mode is other than maximum performance, then alter it as below. SQL> ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE; 3. Recover standby database SQL> RECOVER STANDBY DATABASE; Make sure all archives has been applied in this process and Put CANCEL 4. Finish the recovery process on standby SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH; Database altered 5. Activate the standby database: SQL> ALTER DATABASE A...

Discovery feature in Oracle EBS Cloud Manager to register Oracle E-Business Suite environments on OCI In this post I am sharing how we can use a discovery feature of Oracle EBS cloud Manager and check if we make a EBS environment compliant when manually migrating it to OCI. Source environments can be environments that result from one of the following operations. A manual migration from on-premises to OCI A platform migration from on-premises to OCI An environment initially deployed by Cloud Manager, where either EBS or Oracle Database were upgraded An environment initially deployed by Cloud Manager, where any of the following configuration changes were later made:Addition of a load balancer Addition or deletion of a node Resizing of block volume Pre-Req: EBS Cloud Manager is already setup High Level Discovery Process Meet All Prerequisites Prepare For Discovery Enable SSH Connectivity - SSH connectivity must be enabled from the Oracle E-Business Suite Cloud Manager insta...

Step by Step on how to create a physical standby database using RMAN DUPLICATE FROM ACTIVE DATABASE from On-premises to Oracle Cloud DBCS On Prem Database Name : BEE On Prem DB Version: 11.2.0.4 On Prem Primary db_unique_name : BEE On DBCS Standby db_unique_name : BEE_CL On DBCS DB Version: 11.2.0.4 Steps: 1) On the On-Prem Database Get size of DB col "Database Size" format a20 col "Free space" format a20 col "Used space" format a20 select round ( sum ( used . bytes ) / 1024 / 1024 / 1024 ) || ' GB' "Database Size" , round ( sum ( used . bytes ) / 1024 / 1024 / 1024 ) - round ( free . p / 1024 / 1024 / 1024 ) || ' GB' "Used space" , round ( free . p / 1024 / 1024 / 1024 ) || ' GB' "Free space" from ( select bytes from v$datafile union all select bytes from v$tempfile union all select bytes from v$log ) used , ( select sum ( bytes ) as p from dba_free_space...