Skip to main content

Posts

ORACLE FLASH RECOVERY AREA USAGE QUERY

FINDING ORACLE FLASH RECOVERY AREA USAGE SELECT NAME,        (SPACE_LIMIT / 1024 / 1024 / 1024) SPACE_LIMIT_GB,          ((SPACE_LIMIT - SPACE_USED + SPACE_RECLAIMABLE) / 1024 / 1024 / 1024) AS SPACE_AVAILABLE_GB,        ROUND((SPACE_USED - SPACE_RECLAIMABLE) / SPACE_LIMIT * 100, 1) AS PERCENT_FULL   FROM V$RECOVERY_FILE_DEST;

Unblock the agent in OEM 12C by performing an agent resync from the console

Unblock the agent in OEM 12 C  by performing an agent resync from the console I am using OEM 12 c. Today my EM page was showing that one of the agent in unreachable. So, first of all I tried to see the status of the agent and it showed me the agent is alright. [oracle@NODE4 bin]$ ./emctl status agent Oracle Enterprise Manager Cloud Control 12c Release 2 Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved. --------------------------------------------------------------- Agent Version     : 12.1.0.2.0 OMS Version       : (unknown) Protocol Version  : 12.1.0.1.0 Agent Home        : /home/dir/oemcc/agent_inst Agent Binaries    : /home/oracle/dir/core/12.1.0.2.0 Agent Process ID  : 5159 Parent Process ID : 5044 - - - - --------------------------------------------------------------- Agent is Running and Ready Then I tried to upload the agent and found the following error: [oracl...

How to delete/remove Management Agent from Oracle Enterprise Manager 12C

  1. Before you deinstall a Management Agent, do the following:     a. Stop the Agent using command from Management Agent home:                 cd /u01/oemcc_latest/core/12.1.0.2.0/bin/                 $ emctl stop agent     b. Wait for the Management Agent to go to the unreachable state in the Cloud Control console.     c. It is mandatory to delete the Management Agent and their monitored targets using any of the following methods: Remove the Agent target manually from the console: 1. Login to 12C Cloud Control 2. Navigate to Setup => Manage Cloud Control => Agents 3. Go to the Home page of the Agent that you want to remove 4. Expand the drop-down menu near the " Agent " 5. Expand the " Target Setup " option 6. Select " Remove Target "   ...

How to Create INCIDENT Package

How to Create INCIDENT Package You can create a logical package based on an incident number, a problem number, a problem key, or a time interval. Create a logical package such that it will be most useful to diagnose the error of your concern. Following are the method using which an incident package can be created : Creating package based on incident. Select correct incident if there are many incidents. adrci > SHOW INCIDENT adrci > IPS CREATE PACKAGE INCIDENT incident_number If there are multiple incident then add each of them using following command: adrci > IPS ADD INCIDENT incident_number PACKAGE package_number Once you have created a logical package using any methods, next step is to generate a physical package. adrci > IPS GENERATE PACKAGE package_number IN path Here path is the Hard disk location where the ZIP file will be generated. Note: Please see the metalink note 411.1 for further details.

ADRCI error - DIA-48448: This command does not support multiple ADR homes

ADRCI error - DIA-48448: This command does not support multiple ADR homes adrci> show control DIA-48448: This command does not support multiple ADR homes This error occurs due to multiple ADR home location. Solution is to set the ADRCI home for the instance you want to work. adrci> show homes ADR Homes:  diag/rdbms/DB1/DB1 diag/rdbms/DBISL/DBISL diag/rdbms/ultisl/ULTISL diag/tnslsnr/DCDBLIVE-3/listenerc diag/tnslsnr/DCDBLIVE-3/listeneri adrci> SET HOME  diag/rdbms/DB1/DB1 _________________________________________________________________________________

UDI-31623: operation generated ORACLE error 31623 / ORA-31623: a job is not attached to this session via the specified handle

UDI-31623: operation generated ORACLE error 31623 / ORA-31623: a job is not attached to this session via the specified handle While importing a dumpfile to a test server, the following error were raised. Through a tough time searching the solution, I discovered the solution from a post. My datapump command was like this: -bash-4.1$ impdp system/sys123 schemas=scott directory=db_pump dumpfile=BEF_EOD.dmp Import: Release 11.2.0.3.0 - Production on Mon Dec 31 03:30:01 2012 Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options UDI-31623: operation generated ORACLE error 31623 ORA-31623: a job is not attached to this session via the specified handle ORA-06512: at "SYS.DBMS_DATAPUMP", line 3326 ORA-06512: at "SYS.DBMS_DATAPUMP", line 4551 ORA-06512: at line 1 ...

Installing ORACLE 11g R2 on Linux 6.2

Installing ORACLE 11g R2 on Linux 6.2 Checking memory # grep MemTotal /proc/meminfo # grep SwapTotal /proc/meminfo # df -h /dev/shm/ # mount -t tmpfs tmpfs -o size=10000m /dev/shm # df -h /dev/shm/ Install All Packages Needed. Add entry in host file. #vi /etc/hosts Make entry like this: [IP]        [HOST_NAME] Open /etc/sysctl.conf and add the following lines: # Oracle settings fs.aio-max-nr = 1048576 fs.file-max = 6815744 kernel.shmall = 2097152 kernel.shmmni = 4096 kernel.sem = 250 32000 100 128 net.ipv4.ip_local_port_range = 9000 65500 net.core.rmem_default = 262144 net.core.rmem_max = 4194304 net.core.wmem_default = 262144 net.core.wmem_max = 1048586 net.ipv4.tcp_wmem = 262144 262144 262144 net.ipv4.tcp_rmem = 4194304 4194304 4194304 Refresh settings # /sbin/sysctl -p # /sbin/sysctl -q Open /etc/security/limits.conf and add these lines. oracle   ...