Skip to main content

Posts

Showing posts from June, 2023

Understanding the Power of Oracle DataGuard: Ensuring High Availability and Data Protection

Understanding the Power of Oracle DataGuard: Ensuring High Availability and Data Protection In today's digital world, businesses rely heavily on the uninterrupted availability of their critical data. Downtime and data loss can lead to significant financial and reputational consequences. To mitigate these risks, enterprises seek robust solutions that provide both high availability and data protection. This is where Oracle DataGuard comes into play, offering a comprehensive disaster recovery solution for Oracle databases. In this blog post, we will explore the key features and benefits of Oracle DataGuard, highlighting its ability to ensure uninterrupted data accessibility and protection. 1. Unleashing the Power of Oracle DataGuard: Oracle DataGuard is a powerful feature built into Oracle Database Enterprise Edition, designed to protect critical data against various forms of outages, including human errors, hardware failures, natural disasters, or system glitches. It leverages real-t...

ORA-20100: Temporary file creation for FND_FILE failed

ORA-20100: Temporary file creation for FND_FILE failed In 19c database for EBS R12.2 , we are getting below error while run jobs or creating files. ORACLE error 20100 in FDPSTP Cause: FDPSTP failed due to ORA-20100: ORA-20100: Temporary file creation for FND_FILE failed. The ORA-20100 error in Oracle E-Business Suite indicates that the temporary file creation for FND_FILE has failed. Solution: 1) Make sure UTL file dir is setup correctly as below Click Here 2) First value from below SQL should match to value of $APPLPTMP environment parameter. select value from apps.v$parameter where name = 'utl_file_dir'; 3) Event 10946 should be set at Container Database (CDB) level, as explained in Note 2525754.1: alter system set events '10946 trace name context forever, level 8454144'; alter system set event='10946 trace name context forever, level 8454144' scope=spfile;   4) Bounce application and database after setting the event. 5) Provide grant by executing below comman...

Cannot access gvfs Transport endpoint is not connected

Cannot access gvfs Transport endpoint is not connected While doing df -h getting below error: df -h df: â/run/user/0/gvfsâ: Transport endpoint is not connected Filesystem Size Used Avail Use% Mounted on /dev/mapper/ol-root 40G 6.7G 34G 17% / devtmpfs 3.8G 0 3.8G 0% /dev tmpfs 3.8G 172K 3.8G 1% /dev/shm tmpfs 3.8G 494M 3.3G 13% /run Solutions: The error message "ls: cannot access 'gvfs': Transport endpoint is not connected" typically occurs when there is an issue with the GVFS (GNOME Virtual File System) service in Linux. GVFS is responsible for providing a virtual file system layer that allows applications to access files and folders Solution 1: cd /run/user/0 fusermount -zu gvfs For me this solution fixed the problem Solution 2: Restart the GVFS service: Restarting the GVFS service may resolve the problem. You can do this by restarting the corresponding service using the following command: systemctl --user restart gvfs-goa-volume-monitor.service Solution 3: gvfsd --k...

ORA-20001: Unabled to call fnd_ldap_wrapper.create_user When Creating A New User In EBS with SSO

ORA-20001: Unabled to call fnd_ldap_wrapper.create_user When Creating A New User In EBS with SSO When trying to create a new user in E-Business Suite from forms after integration for SSO, the following error occurs: Error: Unabled to call fnd_ldap_wrapper.create_user due to the following reason: ORA-20001: Unabled to call fnd_ldap_wrapper.create_user due to the following reason: Oracle Internet Directory is not registered correctly. Please contact your System Administrator.. (USER_NAME=DUMMYUSER).(USER_NAME=DUMMYUSER) Solution: Please disable the below Profile  in EBS at site level: APPS_SSO_LDAP_SYNC Applications SSO LDAP Synchronization should be set Disabled (APPS_SSO_LDAP_SYNC) This profile determines whether provisioning is enabled for a particular FND_USER account. User information associated with an FND_USER account will be provisioned with Oracle Internet Directory only if the APPS_SSO_LDAP_SYNC profile of the user is set to ‘Y’. If you like please follow and comment

Shell script to perform a Health Check of the Linux Server

Shell script to perform a Health Check of the Linux Server In this post, I am sharing a shell script which will create a HTML output for a Linux OEL server health check. You can change and Modify as per your needs. The script will generate a file named as server_health_report.html [root@standby ~]# ls -ltr total 8 -rw-r--r--. 1 root root 1177 Jun 22 04:25 health.sh -rw-r--r--. 1 root root 3262 Jun 22 04:25 server_health_report.html Script: #!/bin/bash # Output file for the health check report OUTPUT_FILE="server_health_report.html" # Function to generate formatted HTML report generate_report() {   echo "<html>   <head>     <title>Server Health Check Report</title>     <style>       body {         font-family: Arial, sans-serif;         margin: 20px;       }       h1, h2, h3 {         color: #333;       } ...

Shell Script to remove old kernels from Oracle Linux OEL

Shell Script to remove old kernels from Oracle Linux OEL I am sharing script to remove old linux kernels on RHEL/OEL Script: #!/bin/bash # Define the number of kernels to keep (excluding the current kernel) NUM_KERNELS_TO_KEEP=2 # Get the list of installed kernel packages KERNEL_PACKAGES=$(rpm -q kernel | awk '{print $1}') # Get the number of installed kernels NUM_KERNELS=$(echo "$KERNEL_PACKAGES" | wc -l) # Check if the number of kernels is greater than the number to keep if [ $NUM_KERNELS -gt $NUM_KERNELS_TO_KEEP ]; then   # Get the list of kernels to remove   KERNELS_TO_REMOVE=$(echo "$KERNEL_PACKAGES" | tail -n +$(($NUM_KERNELS_TO_KEEP + 1)))   # Loop through the kernels and remove them   for KERNEL in $KERNELS_TO_REMOVE; do     echo "Removing kernel $KERNEL..."     yum remove -y $KERNEL   done else   echo "No old kernels found or the number of kernels is within the limit." fi Set the value of the NUM_KERNELS_TO_KEEP variable to the ...

Understanding the Difference Between RMAN Redundancy and Recovery Windows

Understanding the Difference Between RMAN Redundancy and Recovery Windows When it comes to Oracle database backups and recovery, two important concepts to understand are RMAN redundancy and recovery windows. These concepts play a crucial role in ensuring data availability and protection against data loss. In this post, I will explain the difference between RMAN redundancy and recovery windows, and provide examples of RMAN scripts to illustrate their usage. RMAN Redundancy: RMAN redundancy refers to the number of copies of backups that are retained in the backup catalog. It determines the level of data protection and allows for recovery in case of backup failures or media corruption. By specifying the redundancy level, RMAN ensures that a certain number of valid backups are available at all times. Example RMAN Script for Setting Redundancy: The following RMAN script demonstrates how to set the backup redundancy level to two copies: RUN {   CONFIGURE RETENTION POLICY TO REDUNDANCY 2;...

How to Stop and Start the Oracle Management Service (OMS) and Oracle Enterprise Manager(OEM) agent services

How to Stop and Start the Oracle Management Service (OMS) and Oracle Enterprise Manager(OEM) agent services In this post I am sharing how to start and stop the services on OMS server for OEM 12c/13c Stopping the Services 1. Stop the OMS. #Go to the OMS HOME location stop with emctl command $OMS_HOME/bin/emctl stop oms -all 2. Stop the Agent. #Go to the AGENT HOME location stop with emctl command $AGENT_HOME/bin/emctl stop agent 3. Stop the Management Repository database. #Source Oracle Home to Management Repository Oracle database export ORACLE_HOME=/u01/oracle/app/db/12.1.0 #Source SID to Management repository database export ORACLE_SID=BEE122 sqlplus / as sysdba Shutdown immediate; 4. Stop the Listener. $ORACLE_HOME/bin/lsnrctl stop Starting the Services 1. Set the Oracle home for Management Repository. #Source Oracle Home to Management Repository Oracle database export ORACLE_HOME=/u01/oracle/app/db/12.1.0 #Source SID to Management repository database export ORACLE_SID=BEE122 2. Sta...

In WebLogic 12c Managed Server Does Not Start with error The server xxxx is in an incompatible state

In WebLogic 12c Managed Server Does Not Start with error The server xxxx is in an incompatible state Error: Trying to start managed server using the node manager showing following error: "The server xxxx is in an incompatible state" Solution: Check that the instance is not running using ps -ef. If it is, use kill -9 <pid> to stop the running instance. Remove the state file: If the managed server name is “Server-Name”  oacore_server1 , then go to the managed server machine, delete the following: $DOMAIN_HOME/servers/<Server-Name>/data/nodemanage/<Server-Name>.state <Server-Name>.state is the node manager file containing instance information and status. After deleting this file, the managed server can be remotely started from the Admin Console. If you like please follow and comment

How to start physical standby database in Readonly state in Active dataguard

How to start physical standby database in Readonly state in Active dataguard Steps 1. Check the status of physical standby select name,open_mode from v$database; NAME      OPEN_MODE --------- -------------- ORCL      Mounted Make sure the primary and standby are in sync before performing the next action plan. 2. Cancel the media recovery on Standby database: In case of RAC it should be done from node where MRP is running. alter database recover managed standby database cancel; 3. Open the database in READONLY MODE: Note: Database should already in Mount state.  ALTER DATABASE OPEN READ ONLY; 4. Start media recovery with real-time log apply on Standby Database: alter database recover managed standby database using current logfile disconnect from session; 5. Verify the Standby database status: select name,open_mode from v$database; NAME      OPEN_MODE --------- -------------------- ORCL      READ ONLY WITH APPLY If you like ...

Oracle Database 19c Table Space Point in Time Recovery for Pluggable Database

Oracle Database 19c Table Space Point in Time Recovery for Pluggable Database In this post I am creating a scenario for table space point in time recovery. RMAN automatic Tablespace Point-In-Time Recovery ( TSPITR) enables you to quickly recover one or more tablespaces in an Oracle database to an earlier time, without affecting the state of the rest of the tablespaces and other objects in the database. Prerequisites :- 1) Enable Database in Archive mode. 2) Take a full database backup 3) Make sure the table space is not default permanent table space Change it as below alter database default tablespace system; Steps: 1) Lets connect to my pluggable database ORCLPDB and create few objects. First I  am creating a user in my PDB database. [oracle@dbserver arch]$ sqlplus '/as sysdba' SQL*Plus: Release 19.0.0.0.0 - Production on Sat Jun 10 07:02:23 2023 Version 19.14.0.0.0 Copyright (c) 1982, 2021, Oracle.  All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Re...