Posts

Showing posts with the label 12C

Deinstall or Uninstall Oracle home in RAC environment

 In this blog, we will list down the steps to uninstall oracle database binary.  Step 1) Login as Oracle binary owner. <Oracle home>/oui/bin/runInstaller -detachHome -local ORACLE_HOME=<Oracle home> Step 2) Make sure Home get deleted from Inventory. <Oracle Home>/OPatch/optach lsinv |grep -i <Oracle Home> Step 3) Remove Binaries  cd <Base directory for Oracle Home> ls -lrt <version> rm -rf <version> ls -lrt <version> You can learn more about oracle RAC using below books: Oracle Database 12c Release 2 Real Application Clusters Handbook: Concepts, Administration, Tuning & Troubleshooting Expert Oracle RAC 12c  ==========================================================      Please check our other blogs for Oracle                        

Oracle GoldenGate Logical Architecture

Image
 In this blog, we will show G logical architecture and brief about GG processes. Manager The Manager process must be running on both the source as well as target systems before the Extract or Replicat process can be started and performs a number of functions including monitoring and starting other GoldenGate processes, managing the trail files and also reporting. Extract The Extract process runs on the source system and is the data caoture mechanism of GoldenGate. It can be configured both for initial loading of the source data as well as to synchronize the changed data on the source with the target. This can be configued to also propagate any DDL changes on those databases where DDL change support is available. Replicat The Replicat process runs on the target system and reads transactional data changes as well as DDL changes and replicates then to the target database. Like the Extract process, the Replicat process can also be configured for Initial Load as well as Change Synchroni...

Oracle Goldengate General recommendations

 In this blog, We are going to show some general recommendation for Goldengate. DBLOGREADER   A new DBLOGREADER option was added to TRANLOGOPTIONS to enable Extract to use a newer API for capturing from an Oracle instance using ASM storage. This feature is available as of Oracle 10.2.0.5. The API enables extract to use a read buffer size of up to 4 MB in size and uses the database server to access the redo and archive logs, so that the extract doesn’t have to access the logs via ASM. A larger buffer may improve the performance of extract when redo rate is high. You can use the new DBLOGREADERBUFSIZE option of TRANLOGOPTIONS to specify a buffer size.  Supplemental Logging  To extract the committed transactions from the source Oracle database's online redo logs, as a minimum the database must be configured for supplemental logging on Primary Key columns. Enabling Supplemental logging at the source database side at the table level is required to ensure tha...

Setup of EMAIL/Script Notification Alerts from OMS

Image
In order to get the alert from the OMS/OEM, DBA need to enable alert notification. In this blog, we will discuss steps to perform the same. => Create the Notification Method           =>  Click on the “Setup” à “Notifications” à “Notification Method” => Click on “Go”. We are using the shell scripts to generate an email notification     => Enter these details and Click on the “ok” => Create the Rules to get the EMAIL Alerts          =>   Click on the Setup à Incidents à Incident Rules => Click on “ Create Rule Set ” => Give a name to this Rule Click on the Target tab and Radio button “ All Targets of types ” and select the  targets => Click on the tab - Rules     =>Click on “ Create ”   =      => Select the Radio button “ All new incidents and updated incidents ” and Click “ Next ”     =>  Click on the “ Add ”      ...

Manual Method of Installation of OEM Agent 12C

Image
  DBAs need to install OEM agent on daily basic in order to promote/discover target server or related targets.       (1)     Login to the OEM 12C server and follow the below steps -      (A) Setup the “.profile_oms” it will setup the environment variables for the OEM 12C      (B) Login to the sysman account with the “emcli” utility      (C) Synchronized the OMS 12C       (D) Verify the Supported Versions in our OMS 12C.We can configure other Agents as well like Hp UNIX etc but in our Cummins environment, we are only using the Solaris, LINUX, AIX and Windows. With this reason, these Agents are configured on the OMS 12C.            (1)   To install the OEM 12C, we have to download the software from the OEM 12C console with the help of “emcli” utility              (2)   SCP this file “ 12.1.0.2.0_AgentCore_23.z...