Master Note for Oracle Database Auditing (Doc ID 1299033.1)

Setting up and Managing the Oracle Database with Enterprise Manager 12c - Video Demonstrations (Doc ID1672202.1)

In this Document

PurposeScopeDetails GoalReferences

APPLIES TO:

Enterprise Manager for Oracle Database - Version 12.1.0.1.0 to 12.1.0.5.0 [Release 12.1]Information in this document applies to any platform.

PURPOSE

Enterprise Manager 12c Cloud Control is a GUI tool capable of managing the Oracle database target in various different areas (for example,Backup & Recovery/Performance/Dataguard/Streams/Security etc). For example, it's possible to use Enterprise Manager to set up andmanage dataguard, or carry out performance tuning without using any command line interface commands. It's also possible to configureEnterprise Manager to monitor the database. For example, to run jobs against the database or to send notification (email/snmp trap/osnotification method) when the database/ listener target is down, or when certain database metrics cross their thresholds. In order tomanage and monitor a database in Enterprise Manager in this way, certain things need to be setup. The purpose of this note is to gatheravailable video resources, that can be used by a DBA who is just getting started with Enterprise Manager to simplify the process of settingup Enterprise Manager in order to monitor a database and to link to a series of videos that explain how Enterprise Manager can be used tomanage specific database areas (eg. Performance/Tuning/Provisioning/Patching/Streams etc)

SCOPE

The purpose of this note is to collate a collection of videos that will be useful for a DBA in both setting up Enterprise Manager to monitor adatabase target, and in managing specific areas of the Oracle database.

DETAILS

GoalThe series of videos are broken up into two areas.

Setting up Cloud Control for Database ManagementManaging Oracle Database with Enterprise Manager

What is covered by 'Setting up Cloud Control for Database Management'?The videos in this area concentrate on topics related to monitoring a database target via EM. Eg. discovering the database target , settingtarget credentials, setting up metrics and thresholds, email and snmp notification, running jobs against the database and setting up incidentrules. This area is called 'setting up' because these are the things that need to be set up correctly in order for smooth monitoring of thetarget. For a new DBA these videos should be followed first, because they go through discovering(adding) the database and setting it upso that it's ready for usage.The complete list of videos and a break down of the topics covered are given in:-note:1615382.1 "Getting Started with Enterprise Manager for DBA's - Videos"What is covered by 'Managing Oracle Database with Enterprise Manager' ?The videos in this area, presume that EM is setup correctly. The focus of these videos is to perfom a specific database related tasks inEnterprise Manager. In many cases EM has become the main way to control many of the oracle products, so for example. the videos in thisseries can show how EM can be used to monitor Performance, work with Ash Analytics/Realtime ADDM, monitor TimesTen, perform Netadministration etc.

Document 1672202.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

1 of 2 3/4/2015 12:40 AM

The complete list of videos and a break down of the topics covered are given in:-Note:1675924.2 "Managing Oracle Database with Enterprise Manager -Videos"

REFERENCES

NOTE:1612019.1 - Database Discovery in 30 Mins (Enterprise Manager Cloud Control 12c) [Video]NOTE:1612010.1 - Understanding Enterprise Manager Administrators and Users in 12c Cloud Control [Video]NOTE:1604047.1 - Setting Database Credentials in Enterprise Manager 12c Cloud Control [Video]NOTE:1609677.1 - Setting Host Credentials in Enterprise Manager 12c Cloud Control [Video]NOTE:1612329.1 - Setting up the Email Notification Method in Enterprise Manager 12c [Video]NOTE:1615378.1 - Setting up the SNMP Trap Notification Method in Enterprise Manager 12c [Video]NOTE:1612675.1 - Testing the Job System in Enterprise Manager 12c for a Host and Database Target [Video]NOTE:1615379.1 - Managing Database Metrics in Enterprise Manager 12c [Video]NOTE:1615380.1 - Incident Rules for Oracle Database Metrics in Enterprise Manager 12c [Video]NOTE:1615382.1 - Getting Started with Enterprise Manager for DBA's - VideosNOTE:1675924.2 - Managing Oracle Database with Oracle Enterprise Manager 12c - Videos


2 of 2 3/4/2015 12:40 AM

Troubleshooting the Listener Status in Enterprise Manager 12c Cloud Control (Status Up or Down) (Doc ID1534401.1)

In this Document

PurposeTroubleshooting Steps About the Listener Availability Metric A) Where is the Listener Monitoring Configuration Info stored? B) Troubleshooting the Listener Up/down Status 1) Check to see if there is an error message associated with the down status. 2) check whether the listener name, listener directory and machine name 'monitoring configuration details' stored in CloudControl are correct. 3) Confirm that the ORACLE_HOME of the listener defined in the monitoring configuration is correct 4) Use the entries from targets.xml to double check the listener information 5) Is the machine name defined correctly? 6) Check whether the response metric is running 7) check whether the agent can currently evaluate the metric correctly. 8) Check the severity history of the target on the agent itself. 9) Manually run the metric collection. 10) Perform a clearstate on the agent 11) Run the lsnrresp.pl script manually C) Commonly hit scenarios which cause incorrect listener status i) The listener is down: tnsping not found in/bin.

ii) A listener process behaviour and identity is defined by not just the listening end-points (the 'Host' and 'Port'), but also by the"Listener Parameter File" (listener.ora) which was used to start the listener process. The "Listener Parameter File" definesparameters like, logging and tracing levels, log/trace directories etc. in addition to the listening end-points, and hence, its location isessential for EM to uniquely identify a "Listener Target".

iii) Listener is configured for TCPS. iv)Listener using IPC protocol shows as down. v) 9i Listener using a password shows as down. (TNS-01169: The listener has not recognized the password) vi) Symptom: Listener is down. Accompanying message is "Message files cannot be read The listener is down: Message 3509 notfound" vii) Symptom: Listener is down. Accompanying message is "Failed to run lsnrctl" Information to CollectReferences

APPLIES TO:

Enterprise Manager for Oracle Database - Version 12.1.0.1.0 and laterInformation in this document applies to any platform.Listener status Down in Enterprise Manager 12c

PURPOSE

To understand how the listener availability status is calculated. To provide steps to troubleshoot if the listener is showing incorrect status.To deal with issues such as listener status down in Enterprise Manager 12c

TROUBLESHOOTING STEPS

About the Listener Availability Metric


1 of 14 3/4/2015 12:41 AM

The availability status of the listener is obtained by the "Response" metric which is run on the remote listener target machine by the agent.After the agent has run the Response metric, the results of the metric are uploaded by the agent to the OMS. The default collectionschedule for the listener 'response' metric to run is every 5 minutes. The listener response metric runs an OS script called lsnrresp.pl whichis found in the /plugins/oracle.sysman.db.agent.plugin_/scripts. The lsnrresp.pl script performs a tnsping to the listener port on the listenermachine and confirms that the listener has been started with the 'correct' listener.ora file (the listener.ora file shown in "listener.ora location"(on the listener home page).Sometimes the listener status can be reflected incorrectly in the Cloud Control Console, for example, the Listener may incorrectly be showingas down (red arrow icon) when it is really up, or the Listener may incorrectly be showing as up (green arrow icon) when it is really down.For the listener to be considered as up, a listener.ora is required. It's not possible for EM to monitor a listener which has been starteddynamically (with no listener.ora). Also the listener which is displayed in Cloud Control is tied to a particular listener.ora file and directory(unlike previous versions of Enterprise Manager). This means that for example, a listener in $TNS_ADMIN and a listener in$ORACLE_HOME/network/admin cannot be swapped between. This is indicated by a warning message on the screen - eg."A listener process behaviour and identity is defined by not just the listening end-points (the 'Host' and 'Port'), but also by the "ListenerParameter File" (listener.ora) which was used to start the listener process. The "Listener Parameter File" defines parameters like, loggingand tracing levels, log/trace directories etc. in addition to the listening end-points, and hence, its location is essential for EM to uniquelyidentify a "Listener Target"."When a listener is reported as down, there will sometimes also be an accompanying error which can be viewed from:-

Listener Home page*/oracle listener/monitoring/incident manager

Sometimes this will be the generic message "The current status of the target is Down" but sometimes this will be accompanied by othererror messages

Tip*: The listener home page can be accessed by:-targets/all targets/Look under the "refine search" sectiontarget type/database/listenerclick on 'listener' should bring up the list of listenersclick on the problem listener nameThis loads the listener home page

A) Where is the Listener Monitoring Configuration Info stored?

Usually when the listener is showing the wrong status in the Cloud Control Console, it is because the listener has been discovered manuallyand something has been incorrectly entered in the listeners monitoring properties.

Note* There are different ways that a listener can be added in Cloud Control. It can either be found by auto-discovery/"run discoverynow". Or it may have been added manually (via guided processes/or by manually specifying monitoring properties).

After a listener has been added in cloud control, the configuration details of that listener are stored in the Cloud Control repository. Thesedetails are known as the "monitoring configuration" and can be displayed by:-

Listener home pageOracle listener (drop down menu)Target setupMonitoring configuration

This will be displaying the same information as the/agent_inst/sysman/emd/targets.xml. (on the agent machine where the problem listeneris located). For example:-


2 of 14 3/4/2015 12:41 AM

B) Troubleshooting the Listener Up/down Status

1) Check to see if there is an error message associated with the down status.

Listener Home pageOracle listener (drop down menu)MonitoringIncident manager

2) check whether the listener name, listener directory and machine name 'monitoring configuration details' stored in CloudControl are correct.

Note that this step only really needs to be done if this is a newly added target, or a target that constantly shows the wrong status. If thelistener target has existed for a while and the target status has previously shown correctly proceed to step 6 and come back to these firststeps, only if step 6 onwards does not help.Check what is currently defined in Cloud Control (from either monitoring configuration or the targets.xml as per step A) and compare to theoutput of lsnrctl status (on the machine where the problem listener is located) The only information needed to add a listener to cloudcontrol is:-

* Listener Name * Listener.ora Directory * Machine Name * Oracle Homeand TCP Port Number and password are optional.

Most of the above information can be found by running:-

lsnrctl status

For example:-

[oracle@machine1 admin]$ lsnrctl status listener11203LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 04-MAR-2013 09:51:55Copyright (c) 1991, 2011, Oracle. All rights reserved.Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=machine1.uk.oracle.com)(PORT=1522)))

Service "v11203" has 1 instance(s). Instance "v11203", status UNKNOWN, has 1 handler(s) for this service...The command completed successfully

So it can be seen that the above command shows the listener name - shown in ("alias")Listener.ora directory shown in "Listener Parameter file"Machine Name (shown in "Listener Endpoints Summary" and Connecting to....")and TCP Port number shown in "Connecting to"..and "LISTENER ENDPOINTS SUMMARY"However, note that the above command does not necessarily show the database oracle home. In this example, the listener is started usinga listener.ora in the databases oracle home, however if the listener had been started using a TNS_ADMIN directory, then the ORACLE_HOMEof the database would not necessarily be reflected in the output of this command.

3) Confirm that the ORACLE_HOME of the listener defined in the monitoring configuration is correct

a)The oracle home where the listener is running from can be found by the "ps -ef | grep tnslsnr" , if the listener is running. For example:-

ps -ef | grep tnslsnroracle 24682 1 0 Feb04 ? 00:05:39 /oracle/orabase/11203rdbms/bin/tnslsnr listener11203 -inherit

b) Or alternatively:-All Oracle Homes should be defined in oratab (/etc/oratab) or (/var/opt/oratab) eg.v11203:/oracle/orabase/11203rdbms:NHowever note that the same listener may be used for multiple databases of different versions. So it may not always be possible to tie in aparticular listener to an oracle home based on oratab entries.

4) Use the entries from targets.xml to double check the listener information

If everything looks ok, use the entries in the targets.xml to check if the listener is defined correctly. For example - targets.xml shows:-

In this above example, the ORACLE_HOME of the listener is shown as 'oracle/database/11203/rdbms"and the listener.ora directory is shown as "/oracle/orabase/11203rdbms/network/admin". This is the default directory for the listener.orawhen $TNS_ADMIN is not set (if $TNS_ADMIN is set, it takes precedence to $ORACLE_HOME/network/admin). The listener name is shownas '11203rdbms'So it should be possible to do the following:-cd to /oracle/database/11203/rdbmsexport ORACLE_HOME=/oracle/database/11203/rdbmsecho $TNS_ADMIN (check it is not set, if so set it to the location of the "ListenerOraDir" shown in targets.xml eg.exportTNS_ADMIN=$ORACLE_HOME/network/admin)cd $ORACLE_HOME/bin./lsnrctl status listener11203This should show a listener running on port 1522.If the listener (as defined in targets.xml) exits and is available and running, but the status is showing incorrectly, go to step 6If the listener does not exist or the above does not show a listener up and running, go to step 5.


4 of 14 3/4/2015 12:41 AM

5) Is the machine name defined correctly?

Does the 'machine name' defined in the listener monitoring configuration match with the real machine name, this can be checked from:-a) uname -a

uname -a

Linux machine1 2.6.32-300.10.1.el5uek #1 SMP Wed Feb 22 17:37:40 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

b) ping

PING machine1.uk.oracle.com (10.xxx.xxx.x8) 56(84) bytes of data.64 bytes from machine1.uk.oracle.com (10.xxx.xxx.x8): icmp_seq=1 ttl=64 time=0.020 ms

c) nslookup

nslookup 10.xxx.xxx.x8Server: ---------Address: ---------#53

-----.in-addr.arpa name = machine1.uk.oracle.com.

This should return the fully qualifed machine name.d) /sbin/ifconfig -a

eth0 Link encap:Ethernet HWaddr 18:03:73:BA:67:B8 inet addr:10.xxx.xxx.x8 Bcast:10.xxx.xxx.xxx Mask:xxx.xxx.xxx.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:172084044 errors:0 dropped:0 overruns:0 frame:0 TX packets:56523244 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:48246543546 (44.9 GiB) TX bytes:33151333402 (30.8 GiB) Interrupt:20 Memory:e1a00000-e1a20000

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:939943068 errors:0 dropped:0 overruns:0 frame:0 TX packets:939943068 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:306709243603 (285.6 GiB) TX bytes:306709243603 (285.6 GiB)

This will indicate all NICS on the machinee) netstat -an | grep. This is to check whether the listener is listening on all NICS, or a particular network card.

[oracle@machine1 test2]$ netstat -an | grep 1522tcp 0 0 0.0.0.0:1522 0.0.0.0:* LISTENtcp 0 0 10.xxx.xxx.x8:1522 10.xxx.xxx.x8:36748 ESTABLISHEDtcp 0 0 10.xxx.xxx.x8:58296 10.xxx.xxx.x8:1522 ESTABLISHEDtcp 0 0 10.xxx.xxx.x8:54544 10.xxx.xxx.x8:1522 ESTABLISHED

In this example, the output "0 0.0.0.0:1522 0.0.0.0:*" shows that the listener is listening on all NICS on port 1522, and the connection isestablished on the primary network card.f) view the /etc/hosts file

10.xxx.xxx.x8 machine1.uk.oracle.com machine1

and check that the information here appears correct according to the above networking tests.

6) Check whether the response metric is running


5 of 14 3/4/2015 12:41 AM

If the listener is running and the monitoring configuration matches the output from lsnrctl, check whether the Response metric is stillscheduled:-

emctl status agent scheduler | grep Response

If the listener Response metric is scheduled it will return a row like:-

2013-02-25 21:33:30.920 : oracle_listener:LISTENER11203_machine1.uk.oracle.com:Response

The metric may not be scheduled if the target has been marked as broken, or if the metric has become suspended. These situations oughtto cause a metric collection error, but it's possible on versions prior to 12.1.0.2 that this may not happen. It's also possible that the EMadministrator may have changed the schedule of the metric, this can be checked from

Cloud Control Consoletargets/all targetsrefine search:target type:listenerclick on the problem listener (takes to the listener home page)oracle listener drop down menumonitoring/metric and collection settings.

Confirm that the "collection schedule" is every 5 minutes for "Response" and that the collection is 'enabled'.

7) check whether the agent can currently evaluate the metric correctly.

This test is to check whether the agent is able to get the correct status of the listener at this current time. It may be that the agent isable to determine the correct status of the listener at the current moment in time, and that the correct status of the listener was sent tothe OMS but the OMS missed this for some reason. Testing whether the agent can evaluate the metric can be done in two ways:-a) Access the metrics browser. The metrics browser is automatically enabled in 12c Cloud Control. To use the metrics browser:-

1) Find out the URL of the agent which monitors the listener (showing the incorrect status). This can be shown inthe output of "emctl status agent" on the 'problem' machine eg.

Agent URL : https://machine1.uk.oracle.com:3840/emd/main/

2) Insert the word 'browser' between 'emd' and 'main' eg.

https://machine1.uk.oracle.com:3840/emd/browser/main/

3) Paste this into a browser. (notice that this metric browser URL of the agent which monitors the 'problem'listener, can be accessed from a browser on any machine it does not have to be accessed on the browser running onthe problem listener machine itself)

4) This will bring up the metric browser. It shows a 'target list' of targets, find the problematic listener,and click on it.

5) Then click on "Response". This will query the metric and return either an up or down status output.

If the listener is running, the metric browser will show:-

Metric=Response Target=(oracle_listener,LISTENER11203_machine1.uk.oracle.com)tnsPing Status oraerr0 1

tnsPing Status oraerr 0 TNS-12541: TNS:no listener

Response Status n/a CRITICAL Mon Mar 04 11:28:34 GMT 2013

perl lsnrresp.plDEBUG:has::Common::hasCheckForExecutableFile emcrsp is not present in cluster home /oracle/orabase/11203rdbms athas/HasCluster.pm line 2883.INFO:has::Common::hasGetScanInformation:This is a pre 11gR2 cluster, binary emcrsp is not found, no Scan information athas/HasCluster.pm line 7552.em_result=0|1|

The listener is down: The listener "listenertest1" is not running using the Listener parameter file:"/oracle/orabase/11203hometwo/network/admin/test/listener.ora/listener.ora" on Host: "machine1.uk.oracle.com" at Port: ""..

In this situation, the monitoring configuration property "Listener.ora directory" has been entered incorrectly. It includes the name"listener.ora"eg.Listener.ora directory:/oracle/orabase/11203hometwo/network/admin/test/listener.oraIt should be the location of the "listener.ora" file, and should not include the name "listener.ora"Action:change the monitoring properties "listener.ora directory" property to a directory location and do not include the words "listener.ora"eg.Listener.ora directory:/oracle/orabase/11203hometwo/network/admin/testNote that this error could also be seen if there are two listener's which are the same, but in different locations. Unlike previous releases ofEnterprise Manager, the same listener.ora needs to be used to start the listener at all times (for the listener to be considered as available)

iii) Listener is configured for TCPS.

Symptom:The listener is showing as down in the console. The listener is not using TCP. For example, the listener is configured with:-SECURE_PROTOCOL_LISTENER=(TCPS)Action: See note:1326902.1"How to monitor a secure listener (TCPS/SSL) and the underlying database with Enterprise Manager (GridControl/Cloud Control)". There is no support in EM for monitoring TCPS only listeners, there needs to be a TCP endpoint as well. See thenote for more information on this.

iv)Listener using IPC protocol shows as down.

Symptom: An ipc only listener is showing as down. Note that a listener using an IPC protocol will not be discovered automatically (eg. via"run discovery now") because the automatic discovery process only considers listeners with TCP end points. A listener using IPC protocolonly, needs to be added manually via setup/add targets/add targets manually/Add Non-Host Targets by Specifying Target MonitoringProperties/target type:oracle_listener. If an ipc only listener is showing as down, then it's likely that the Monitoring Configuration detailswhich were entered manually are not correct. Action: Check the monitoring properties. The following is an example of an IPC only listener:-

A) listener.oraSID_LIST_LISTENERTEST1 = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = rachel) (ORACLE_HOME = /oracle/orabase/11203hometwo) (SID_NAME = rach) ) )PASSWORDS_LISTENERTEST1= (9BD20802761D432E)SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENERTEST1 = OFFLISTENERTEST1 = (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(KEY = KEY_LISTENERTEST1)) )

B) status output:-LSNRCTL> status listenertest1Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=KEY_LISTENERTEST1)))STATUS of the LISTENER------------------------


10 of 14 3/4/2015 12:41 AM

Alias listenertest1Version TNSLSNR for Linux: Version 11.2.0.3.0 - ProductionStart Date 04-MAR-2013 11:55:45Uptime 1 days 3 hr. 8 min. 49 secTrace Level offSecurity ON: Password or Local OS AuthenticationSNMP OFFListener Parameter File /oracle/orabase/11203hometwo/network/admin/test/listener.oraListener Log File /oracle/orabase/11203hometwo/network/admin/test/listenertest1.logListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=KEY_LISTENERTEST1)))Services Summary...Service "rachel" has 1 instance(s). Instance "rach", status UNKNOWN, has 1 handler(s) for this service...The command completed successfully

LOG_FILE_LISTENERTEST1 = LISTENERTEST1.logADMIN_RESTRICTIONS_LISTENERTEST1 = ONLOG_DIRECTORY_LISTENERTEST1 = /oracle/orabase/11203hometwo/network/admin/test

C) targets.xml

v) 9i Listener using a password shows as down. (TNS-01169: The listener has not recognized the password)

Symptom:The listener is using a password, so the password needs to be entered in Cloud Control. The metrics browser shows the errormessage:-

TNS-01169: The listener has not recognized the password

Action : Enter the password for the listener in the "Listener Password" field of the 'monitoring configuration' screen. The "ListenerPassword" field is also available at target discovery time. If using 12.1.0.1:-

open the listener.ora and copy the encrypted passwordin Cloud Control, navigate to the listener home pageclick on oracle listener (drop down menu)click on target/setup/monitoring configurationpaste the encrypted listener password from the listener.ora file into the "Listener Password" section.

vi) Symptom: Listener is down. Accompanying message is "Message files cannot be read The listener is down: Message 3509not found"

Symptom: Listener is down. accompanying message is "Message files cannot be read The listener is down: Message 3509 not found"Action: Follow note:559236.1 "The Listener Is Down: Message 3509 not found; No message file for product=network, facility=TNS"

vii) Symptom: Listener is down. Accompanying message is "Failed to run lsnrctl"


11 of 14 3/4/2015 12:41 AM

Symptom: Listener shows as down in Enterprise Manager, but listener is up and running The emagent_perl.trc shows:-

lsnrresp.pl: Thu Dec 5 10:36:27 2013: DEBUG: LISTENER :: em_result=|0|Failed to run lsnrctl

In order to obtain the listener status, the following is run by the agent:-cd to $ORACLE_HOME/binlsnrctl status (ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=))This output, then needs to be written to a temporary file in the temp directory. This error can occur when either.

The agent user does not have the correct permissions on the lsnrctl executableThe agent user does not have the correct permissions on the TEMP directoryThe TEMP directory is full (or not writable)

If hitting this error message, it may be necessary to find out the location of the temp directory that the agent is trying to use. To do this thefollowing steps can be used:-1) go to \plugins\oracle.sysman.db.agent.plugin_12.1.0.5.0\scripts\db\net2) Take a copy of listenerUtil.pl (eg. listenerUtil.pl_original)3) After creating a backup, edit listenerUtil.pl and locate the following section:-

my $filename;my $fh;if ( $OSNAME eq 'WIN' ){my $TEMP = $ENV{SYSTEMDRIVE} . "\\TEMP";#A temp solution&mkDir_lst($TEMP);$filename = "$TEMP\\" . "net.$$";}else{( $fh, $filename ) = tempfile( UNLINK => 1 );}

4) Amend the section by adding a debug statement at the end of it - eg.

my $filename;my $fh;if ( $OSNAME eq 'WIN' ){my $TEMP = $ENV{SYSTEMDRIVE} . "\\TEMP";#A temp solution&mkDir_lst($TEMP);$filename = "$TEMP\\" . "net.$$";}else{( $fh, $filename ) = tempfile( UNLINK => 1 );}EMD_PERL_DEBUG(" listenerUtil.pl :: oracletestfilename == $filename");

5) save the changes


12 of 14 3/4/2015 12:41 AM

6) Set debug trace on the agent. To do this, edit the emd.properties in:-/sysman/config/emd.propertiesand add:-EMAGENT_PERL_TRACE_LEVEL=DEBUG7) Reload the agent for the changes to take effect:-emctl reload agent8) Force the agent to run the collection:-emctl control agent runCollection :oracle_listener Response9) Check the /sysman/log/emagent_perl.trc. Look for the word "oracletestfilename" for example:-

output on Windows:-lsnrresp.pl: Thu Dec 5 19:52:11 2013: DEBUG: listenerUtil.pl :: oracletestfilename == C:\TEMP\net.5224

emctl status agent target ,oracle_listener10) If the metrics browser/get metric does not show a '1'a) run the lsnrrreps.pl script manually as per point 11a.b) generate a DEBUG trace output as per point 11b.

REFERENCES

NOTE:559236.1 - The Listener Is Down: Message 3509 not found; No message file for product=network, facility=TNSNOTE:1534087.1 - How to manually run the lsnrresp.pl script to troubleshoot listener availability issues in Enterprise Manager 12c CloudControlNOTE:1326902.1 - How to monitor a secure listener (TCPS/SSL) and the underlying database with Enterprise Manager (Grid Control/CloudControl)


14 of 14 3/4/2015 12:41 AM

Understanding Database Discovery in Enterprise Manager 12c Cloud Control (Doc ID 1400463.1)

In this Document

PurposeScopeDetails A) Background Information Discovery Concepts Plugins Plugin Revisions Self Update B) Pre-requisites for database discovery 1) A 12c agent must be installed and running on the machine where the database target resides. 2) The database plugin which exists on the OMS must support the version of the database to be discovered C) Getting the Agent D) Discovering the Database (4 different ways to discover the database) 1) Database Discovery using 'Guided Process' 2) Database Discovery using 'Manual Discovery' 3) Database Discovery using 'Automatic Discovery of Database Targets' Where to find the automatically discovered Database Targets How to run "Run Discovery Now" How to Promote the Database How to configure the Auto Discovery Time Period Has the database been automatically discovered? 4) Database Discovery via EMCLI E) Discovery Algorithm F) Troubleshooting Discovery Issues Online Documentation ReferencesReferences

APPLIES TO:

Enterprise Manager for Oracle Database - Version 12.1.0.1.0 and laterInformation in this document applies to any platform.

PURPOSE

This document is to discuss the different methods of discovering a database in Enterprise Manager Cloud Control 12c, relevent backgroundinformation and the pre-requisites necessary to achieve this.If you would like to discuss any issues with Database Discovery in EM 12c or read what other EM users are experiencing,please feel free to update or monitor the EM MOS Communities discussion thread below:


1 of 13 3/4/2015 12:42 AM

All Places > My Oracle Support Community > Enterprise Manager (MOSC) > Managing Databases using Enterprise Manager (MOSC)

How to discover a database using EM 12c

Marilyn Roncati - Em Community Manager -Oracle Apr 29, 2013 11:10 PM

SCOPE

It is intended for Enterprise Manager Administrators who are famiilar with the previous versions of Enterprise Manager.

DETAILS

A) Background Information

Discovery Concepts

There are four ways to discover a database in Enterprise Manager 12c Cloud ControlAutomatic discoveryManual discovery via ConsoleDiscovery via Guided ProcessManual discovery via command line.

Database discovery in Enterprise Manager 12c Cloud Control, differs to the previous versions of Enterprise Manager (Grid control 11.1.0.1,Grid Control 10.2.0.X and 9.2.0 OEM), in the sense that database targets which are discovered automatically are not populated in theconsole. Database/listener targets can be automatically discovered but not displayed in the console until the user chooses to "promote" thatparticular database/listener target.

Note:The exception to this is Clusterware managed targets like Listeners, ASM or instances. See note:1522674.1 for further explanationof this

The concept of "target promotion" is new in 12c but involves selecting the databases to be displayed in the console, and configuring themfor monitoring by entering the dbsnmp username/password (configuring them is similar to "configuring" a database in 11g grid control). Thisremoves the possibility of the Administrator seeing unwanted or unconfigured targets in the Console. This means that when a new agent isadded to Enterprise Manager Cloud Control 12c, the database targets which run on that agent machine will not be shown automatically inthe console.

As well as the automatic discovery method, there is also a possibility to discover the database via guided processes, or to add the databasemanually via the console, or via emcli (enterprise manager command line interface). Only the automatic discover method requires targetpromotion, the other methods do not require promotion because the targets are manually chosen and configured by the user and so thenecessary dbsnmp connect info has already been supplied.

Plugins


2 of 13 3/4/2015 12:42 AM

Another new concept in 12c is the concept of the database 'plugin'. Any database which is monitored by Cloud Control needs to use the"database plugin".For 12.1.0.1.0 Cloud Control - the database plugin (version 12.1.0.1.0 ) is automatically deployed on the OMS by default.For 12.1.0.2.0 Cloud Control - the database plugin (version 12.1.0.2.0[u120804] ) is automatically deployed on the OMS by default.For 12.1.0.3.0 Cloud Control - the database plugin (version 12.1.0.5.0) is automatically deployed on the OMS by default.For 12.1.0.4.0 Cloud Control- the database plugin (version 12.1.0.6.0) is automatically deployed on the OMS by default.The database plugin is automatically deployed on the OMS by default (as shown above). However, the database plugin also needs to bedeployed on any management agent which needs to manage a database. The database plugin can either be deployed by the user to themanagement agent (via the setup/extensibility/plugins screen) or it will be deployed automatically at the time when the first database targetto be managed by an agent is added, as part of the add database/promote database process.

If subsequently it is a requirement to have a later version of the plugin installed on the agent, The existing plugin can be upgraded from the"Plugins" console.

Note that if intending to deploy the latest plugin on an agent, this latest version of the plugin needs to first be deployed on the OMS,before it can be deployed on the remote agent.

If a database is discovered by an agent that has already previously discovered a database, the database plugin will already be installed onthat agent in which case, the version of the database plugin on the OMS, and the version of the database plugin on the monitored agent,may be different. The version of the plugin installed on an agent can be checked from:-

Setup/Extensibility/Pluginsexpand "Databases" folderHighlight "Oracle Database"go to Actions:Informationclick "Management agent" tab

and can be checked on the agent itself by:-

cd $ORACLE_HOME/oracle/12cagent/core/12.1.0.3.0[oracle@pc ~]$ emctl listplugins agentOracle Enterprise Manager Cloud Control 12c Release 3Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.---------------------------------------------------------------oracle.sysman.emas 12.1.0.5.0 /oracle/12c/12cagent/plugins/oracle.sysman.emas.agent.plugin_12.1.0.5.0oracle.sysman.emrep 12.1.0.3.0 /oracle/12c/12cagent/plugins/oracle.sysman.emrep.agent.plugin_12.1.0.3.0oracle.sysman.beacon 12.1.0.3.0 /oracle/12c/12cagent/plugins/oracle.sysman.beacon.agent.plugin_12.1.0.3.0oracle.sysman.oh 12.1.0.3.0 /oracle/12c/12cagent/plugins/oracle.sysman.oh.agent.plugin_12.1.0.3.0oracle.sysman.csa 12.1.0.3.0 /oracle/12c/12cagent/plugins/oracle.sysman.csa.agent.plugin_12.1.0.3.0oracle.sysman.db 12.1.0.5.0 /oracle/12c/12cagent/plugins/oracle.sysman.db.agent.plugin_12.1.0.5.0

Note that the plugins are not platform dependent in the sense that there is not a separate plugin for each Operating System. However for12.1.0.1 only, multi OS support was not available until the 111221 revision of the 12.1.0.1.0 database plugin (12.1.0.1.0 [u111221].)Periodically, later versions of the database plugin (or later revisions of the database plugin) can be released

Plugin Revisions

A revision of a database plugin indicates that there is a newly revised version of the *same* plugin. Revisions only affect targetcertifications, so there would not be a need to update an existing remote agent with the latest revision. The plugin revisions are needed if


3 of 13 3/4/2015 12:42 AM

database monitoring for a particular platform newly becomes available, and the plugin revision adds support for that platform, so the latestrevision plugin would be needed on the OMS. However, existing agents would not need this revision, because they would already have beeninstalled on their own (different) platform. A plugin revision is shown in the console with the revision number in square brackets forexample: 12.1.0.1.0 [u111221].

Self Update

These new versions/revisions of the database plugin are obtained via EM Cloud Control's 'Self Update' feature (setup/extensibility/selfupdate). Self update automatically runs a job that regularly checks for updates. The cloud control administrator will be emailed automatically(if email notification has been set up) when any new plugins are available (via the incident rule "Event management Ruleset for SelfUpdate". It is also possible to run an on-demand search of the latest updates by clicking on "check updates" this will run a job called"SELFUPDATE" which does a 'RefreshFromEMStore'.

B) Pre-requisites for database discovery

1) A 12c agent must be installed and running on the machine where the database target resides.

There must be a 12c Management Agent (eg. 12.1.0.1.0, 12.1.0.2.0,12.1.0.3.0,12.1.0.4.0) on the remote host (where the database targetresides). Previous versions of the agent are not compatible with Enterprise Manager 12c. If there is no agent, it can be deployed usinginstructions from Section C.

2) The database plugin which exists on the OMS must support the version of the database to be discovered

The database plugin which currently exists on the OMS must support the OS platform and version of database of the database to bediscovered. Check this by:

setup/extensibility/pluginsclick on the arrow to the left of the "Databases" folder and expand itHighlight "Oracle Database"Pick "Actions:Information"view "General" tab

This will show the versions of the databases which the plugin can manage, and the OS versions which are certified. Note that to manage a12.1 database the 12.1.0.3.0 database plug-in or higher is needed. And note that for the original release (12.1.0.1.0) of Cloud Control thedefault database plugin (12.1.0.1.0 with no revisions) did not support any other platform than Linux. If the platform desired is not shown,also check the certification information on 'My Oracle Support', to clarify whether that platform is certified:-

'My Oracle Support'/Certifications/Enterprise Manager Base Platform - Agent: version 12.1.0.X.0

If the current database plugin installed on the OMS does not support the required database version or platform, either a later versiondatabase plugin, or a revision of the database plugin is needed. This new revision/version of the plugin will first need to be downloaded anddeployed on the OMS.

See note:1388143.1 How to Deploy the Latest Database Plugin to the OMS and the Agent in 12C Cloud Control

C) Getting the Agent1) If there is already an agent running on the host where the remote database is go to Section D. For discovering a RAC cluster database,an agent needs to be installed on all nodes of the cluster.

2) If there is no agent on the remote host, the agent can be deployed to the remote host as follows:-

setup/add target/add target manually/click on "add host target".

After the agent has been added, go to section D.


4 of 13 3/4/2015 12:42 AM

Note* To see the results of the agent deployment (whether successful or not, go to setup/add target/add targets manually/click "addhosts results" button. Click on the hyperlink under "session name".)

c) If unable to "add host target" because the "Agent software unavailable" message is shown for the necessary platform.

The "agent software unavailable" message may be seen because by default the OMS will only have the agent software for the platform theOMS was installed on. If the agent to be deployed is on a different platform than the OMS, then it is necessary to obtain the agent softwarefor that platform.

The agent software can be obtained from Enterprise Manager Cloud Control itself via self update. (Setup/Extensibility/Self Update/under folder "Agent Software").

Click on "download" to download the software. This runs a job called " DNLDEMUPDATEDNLDEMUPDATE (Download Update From Oracle)".After the download, the software should be automatically applied via the job (APPLYEMUPDATEAPPLYEMUPDATE). To check this, click oncheckup/extensibility/self update/expand "agent software" folder. Look at the status (either "applied, available or apply failed". If thedownload has completed but the software has not been automatically applied, highlight the row, then go to Actions/Apply.What do the Status mean:Available: means that the software for that agent is available to download from the EMStore at Oracle, but has not yet been downloadedor applied. Clicking on "download" will download the software to the OMS. The "download" action will automatically try to apply thesoftware as part of the process.Download in Progress: means that the agent software is being downloaded to the OMS machine.

Applied: means that the software for that agent has been downloaded and applied (therefore it should be possible to install an agent onthat particular platform)

Apply failed: means that there was an attempt to download and apply that software to the OMS Software Library, but the apply failed. If"apply failed" is seen, highlight it, at the bottom of the screen the "past activities" pane will show and there will be a status against theoperations "available/download and apply". If any operation has a "failed" (eg. apply:failed) click on ""details", which should drill down tothe error message

Note: In 12.1.0.1.0 the following message could be returned:-

Exception: OperationFailedExceptionOperationFailedException: Below host metric patches are not applied to OMS.[13426571]

This is due to the fact that in order for the 12.1.0.1.0 Cloud Control to successfully apply plugins on certified platforms other than Linux,the following patches needed to be applied to the OMS home. (these patches add support for Solaris, AIX, HP agents/databases)

patch:12989982,patch:13426571, patch:13086659,patch:13426642if apply failed due to these patches being missing, install the patches. Then go back into self update and highlight "apply failed", thenchoose ""apply". See also:

note:1388774.112c: Plugin Deployment Fails With "Plug-in is not certified for the Operating System" note:1388143.1 How to Deploy the Latest Database Plugin to the OMS and the Agent in 12C Cloud note:1360183.1How to install Enterprise Manager Cloud Control 12c Agent on Linux

D) Discovering the Database (4 different ways to discover the database)Once the agent exists on the remote machine (where the databases reside) the database can be discovered in one of the following ways:-

Guided ProcessManual DiscoveryAutomatic Discovery (and "run discovery now")Manual via emcli


5 of 13 3/4/2015 12:42 AM

Note: These methods also apply to cluster (RAC) databases, but for cluster databases an extra step is needed. For Cluster (RAC)databases See Note:1908635.1 "How to Discover the Cluster and Cluster Database Target in Enterprise Manager 12c"

1) Database Discovery using 'Guided Process'

Discovery via Guided Process is done via:-

Setup/Add targets/Add targets manuallyAdd Non-Host Targets Using Guided Process (Also Adds Related Targets)Target types:Oracle Database, Listener and Automatic Storage ManagementClick "add using guided discovery"

Or the guided process discovery can be done via:-

targets/databases/addchoose hostnameclick on 'continue'

This will find all databases and their listeners on a particular host. The databases will be added to the console, once they have beenconfigured by the user. 'configuring' involves entering the password for the dbsnmp account, and then finishing the dialogue.

2) Database Discovery using 'Manual Discovery'

Alternatively a complete manual discovery can be done. This option adds only one database. It is called "manually", because the necessaryconfiguration information (such as database name, port number etc) must be provided by the user. This can be useful when needing to addan individual database or listener, but if multiple databases need to be discovered it would be much quicker to use guided process orautomatic discovery.

Adding a database manually is discussed in detail in Document 1371846.1 How To Manually Add Database Targets in 12C Cloud Control.This note includes screen shots and troubleshooting tips.

Note that if the database/listener/asm to be added will be the first database/listener/asm target to be discovered by that managementagent, and that management agent has not previously had the database plugin manually deployed to it, then the database plugin will beautomatically deployed as part of the add database/listener/asm process. The database plugin will be deployed to$ORACLE_HOME/plugins/oracle.sysman.db.agent.plugin_12.1.0.X.0This means that the first time a database/listener or asm target is added on a new agent, there could be a small delay whilst thedatabase plugin is deployed.

3) Database Discovery using 'Automatic Discovery of Database Targets'

Where to find the automatically discovered Database Targets

By default when the OMS discovers a new agent only the host,the agent and the Oracle Home target are automatically shown in theEnterprise Manager 12c Cloud Control Console. The other targets (eg. database/listener/ASM) need to be discovered. A metric collectioncalled 'DiscoverTargets' runs soon after the agent has been deployed and then subsequently at a default interval of once a day, to discoverall new targets which have been added onto the machine. The targets that have been found by auto discovery results can be seen in:-

Setup/Add Target/Auto Discovery Results/Pick "Agent Based Targets" Tab

These targets will not show up in the console until they have been promoted (see below). In 12.1.0.3 Cloud Control onwards, the automaticdiscovery module is configured automatically so that any new databases which are added on the machine will be detected in Auto DiscoveryResults/Agent Based Targets. In some previous versions of Cloud Control, it may be necessary to enable the discovery module as follows:-

In 12.1.0.1.0


6 of 13 3/4/2015 12:42 AM

go to setup/addtarget/configure autodiscoveryclick on 'multitype target discovery on single host'Highlight the "Agent host Name"check that the discovery module "Oracle Database, Listener and Automatic Storage Management" shows as an "EnabledDiscovery Module"If not, click on "configure" and tick the relevant discovery modules (ensure that "oracle database, listener andAutomatic Storage Management" is ticked) and click on ok.

In 12.1.0.2.0 + later

go to setup/add target/configure auto discoveryclick on "all discovery modules"Highlight the "Agent host Name"Click on configureTick the "enabled" box, in order to enable the relevant discovery modules(in the very least "Oracle Home Discovery" and "Oracle Database, Listener and Automatic Storage Management" isneeded)Say OK to save changes

If no databases are shown in the 'auto discovery results'/'Agent Based Targets' tab, it may be due to the fact that the 'discoverTargets'metric has not yet had chance to run. In this case "run discovery now" can be used which will force the agent to run DiscoverTargets metricwhich in turn runs the database discovery algorithm.($ORACLE_HOME/plugins/oracle.sysman.db.discovery.plugin_12.1.0.X.0/discover/oracledb.pl). "Run discovery now" is performed as follows:-

How to run "Run Discovery Now"

go to setup/addtarget/configure autodiscoveryclick on 'all discovery modules' (12.1.0.2.0 onwards) or 'multitype target discovery on single host' (12.1.0.1.0)Brings you to "Target Discovery (Agent Based)" screen choose 'run discovery now'Shows dialogue box "are you sure you want to run target discovery on ?click on "yes"A "Run Discovery Now - In Progress" box should show on the screen

This "run discovery now" achieves a similar aim as to running agentca -d or "add database" in the previous versions of Grid Control . Noticethat the targets will still not show up in the console nor will they be added to the agent's targets.xml file($ORACLE_HOME/agent_inst/sysman/emd/targets.xml) until they have been promoted in Cloud Control.

How to Promote the Database

The databases which have been found by in 'autodiscovery results/Agent Based Targets', and which the user wishes to monitor by cloudcontrol need to be promoted before they will show up as database targets in the Console . To do this:-

go to setup/add target/auto discovery results/"Agent Based Targets" (this will be "non host target" in older versions)Highlight the database, click on 'promote' For database targets, there is a "configure" icon, to enter the dbsnmp password details, and test the connect string.After the database (and listener) have been promoted and configured successfully, they will be seen in the console.Any targets that need to be marked as 'ignored' can be highlighted and then click "ignore". (To multiple highlight to ignoremultiple targets in one go, do "shift/highlight").

From 12.1.0.3 onwards, there is the concept of 'mass promotion' for a target. In 12.1.0.3 it is possible to promote multiple targets asfollows:-

1) Select each database that you wish to promote (do this by holding down the 'control' key and highlighting each database)2) Click on "promote". 3) Expand the section "specify common monitoring credential". 4) Enter the dbsnmp password, tick which of the databases this password will apply to and click on "apply"5) The "monitor password" will show as 'set' for the databases after the password is set in this way.6) A combination of different passwords can be used (as long as the different relevant databases are ticked)7) Then continue as normal and promote the databases


7 of 13 3/4/2015 12:42 AM

If using an older version than 12.1.0.3 then this feature is not available. In which case, the following may be a useful workaround:Note:1543773.1 "How to Create an emcli script to Add Databases via Emcli based on the targets found in auto discovery results in EnterpriseManager 12c Cloud Control"

Note: If the management agent does not have the database plugin deployed to it (eg. a newly discovered agent where the databaseplugin has not been previously manually deployed), and is automatically discovering a database/listener/asm target for the first time, thedatabase plugin will be automatically deployed at the time when the first database/listener/asm target is successfully promoted. Thedatabase plugin will be deployed to $ORACLE_HOME/plugins/oracle.sysman.db.agent.plugin_12.1.0.1.0. This means that thefirst time a database/listener or asm target is promoted on a new agent, there could be a small delay whilst the database plugin isdeployed.

How to configure the Auto Discovery Time Period

After the initial discovery of the database/listener/ASM targets, the OMS will periodically check for any new database/listeners which havebeen added. The period in which the OMS checks for new databases is set by:

Setup/add target/configure auto discovery/click on "All Discovery Modules"Select the host, click on "configure discovery modules"Highlight "Oracle Database, Listener and Automatic Storage Management"The collection frequency "every x days" is shown.

Has the database been automatically discovered?

If the Desired Database is not Shown in setup/add target/auto discovery results/"Agent-Based Targets (or "non host target" if on an olderCloud Control release) then the following should be checked:

1) Perform a "run discovery now"as shown in Section 3 "how to perform a "run discovery now"Tip: Make sure that the pop up box "are you sure you want to run target discovery on ?" is shown. If the hyperlink by thehostname is clicked by mistake, it does not run the discovery, instead it presents the screen to configure discovery options. If the "RunDiscovery Now -In Progress" box is not shown, see step 2 below.

2) Ensure that the necessary discovery modules are showing in Target Discovery (Agent Based) screen. For 12.1.0.2 and higher:-

go to setup/addtarget/configure autodiscoveryclick on "all discovery modules"highlight host and click on "configure discovery modules" Check that all are showing as 'enabled'

For 12.1.0.1

click on 'multitype target discovery on single host'Brings you to "Target Discovery (Agent Based)" screen (or highlight and choose "configure")Tick the Discovery Modules which are required: eg.

Oracle Cluster and High Availability ServiceOracle Database, Listener and Automatic Storage ManagerOracle Fusion MiddlewareOracle Home DiscoveryOracleSecureBackup


8 of 13 3/4/2015 12:42 AM

After enabling the discovery modules, perform a "Run Discovery Now"

3) Check that the /etc/oratab or var/opt/oracle/oratab (Solaris) contains the entry for the database

4) In the agent home, on the machine where the database to be discovered resides check:-

$ORACLE_HOME/agent_inst/sysman/log/emagent_perl.trc

This should show the Db discovery 'INFO' information eg.

DB_LISTENER_DISCOVERY: ***** Start of Database and Listener Discovery***

this should indicate whether the listener was found eg. this will show the version of the listener, ipaddress/hostname, the port etc. It isalso possible to change the 'INFO' level to 'DEBUG' by changing the $ORACLE_HOME/agent_inst/sysman/config/emd.propertiesparameter for example:-'EMAGENT_PERL_TRACE_LEVEL=INFO' to 'EMAGENT_PERL_TRACE_LEVEL=DEBUG'and reloading the agent, for exaple:-emctl reload agent

Note* If the info/debug information does not show in the emagent_perl.trc try manually deploying the database plugin from theExtensibility/plugins.

setup/extensibility/pluginsexpand "databases" folderhighlight "oracle database"Actions: Deploy on Management Agent"

5) For more information on troubleshooting discovery issues see note:1543745.1. See also below (section E for the discovery algorithm)

4) Database Discovery via EMCLIEnterprise Manager Cloud Control 12c also offers a further discovery option, which is to use emcli to manually script database discovery. The advantage of using this message is that it can speed up discovery time considerably. Emcli is a command line extension to EnterpriseManager Cloud Control. It can be installed on any machine. It does not necessarily have to be on the machine running Cloud Control. In thisexample it's installed on the OMS machine, but it could also be installed on a windows pc (see note:1396785.1 ). EMCLI is downloaded fromthe OMS and is quick to set up. To use emcli to discover the database target, the following properties must be known:- Name,SID,hostname, dbsnmp account password, listener port, 'target type' and database oracle home path.

How to find the values for: Name,SID, hostname, dbsnmp account password, listener port, 'target type' and databaseoracle home path for the database target.

"Name" is the name which will be given to the database target in Cloud Control. (it can be anything, does not have to correspondwith the actual target name)SID can be determined from sql*plus command "show parameter instance_name"Hostname can be determined from uname -a. Then nslookup to get the fully qualifiedhostname.Dbsnmp account password can be checked by logging into the database as 'dbsnmp'. If password is unknown it can be changedat sql*plus using "alter user dbsnmp identified by "Listener port can be determined from $TNS_ADMIN/listener.ora or $ORACLE_HOME/network/admin/listener.ora (if $TNS_ADMINis not set)Database oracle home path can be determined from: /etc/oratab or /var/opt/oracle/oratabTarget type for the database is: oracle_database (but for the other targets could be:oracle_listener,osm_instance,rac_database,osm_cluster)


9 of 13 3/4/2015 12:42 AM

The emcli add_target command takes the form:-

emcli add_target-name="name"-type="type"-host="hostname"[-properties="pname1:pval1;pname2:pval2;..."][-separator=properties="sep_string"][-subseparator=properties="subsep_string"][-credentials="userpropname:username;pwdpropnamepwdpropname:password;..."][-input_file="parameter_tag:file_path"][-display_name="display name"][-groups="groupname1:grouptype1;groupname2:grouptype2;..."][-timezone_region="gmt_offset"][-monitor_mode="monitor_mode"][-instances="rac_database_instance_target_name1:target_type1;..."]

[ ] indicates that the parameter is optional

An example of the emcli command to add a database is:-

./emcli add_target -name="" -type="oracle_database" -host="" -credentials="UserName:dbsnmp;password:;Role:Normal" -properties="SID:;Port:;OracleHome:;MachineName:"for example:-

./emcli add_target -name="sally" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:sally;Port:1528;OracleHome:/u01/orabase/11db;MachineName:machine1.uk.oracle.com"using a preferred connection string for the database target's monitoring configuration:emcli add_target -name="

password:dbsnmp;Role:Normal" -properties="SID:DB2;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB3" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB3;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB4" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB4;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB5" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB5;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB6" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB6;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB7" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB7;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB8" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB8;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB9G" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB9;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB10" -type="oracle_database" -host="machine1.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB10;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="LISTENERTEST2" -type="oracle_listener" -host="machine1.uk.oracle.com"-properties="LsnrName:LISTENER;ListenerOraDir:/oracle/orabase/11203hometwo/network/admin/;Port:1621;OracleHome:/oracle/orabase/11203hometwo;Machine:machine1.uk.oracle.com;"logout

Then invoke emcli as follows:-./emcli argfile addtargets.txt Other commands can be added in this file. For example, commands to add all the targets to an existing group, or to add a listener

...same file as above...with the following added:-

add_target -name="DB10" -type="oracle_database" -host="rbridden-pc.uk.oracle.com" -credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB10;Port:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1 uk.oracle.com;"add_target -name="LISTENERTEST2" -type="oracle_listener" -host="machine1.uk.oracle.com"-properties="LsnrName:LISTENER;ListenerOraDir:/oracle/orabase/11203hometwo/network/admin/;Port:1621;OracleHome:/oracle/orabase/11203hometwo;Machine:machine1.uk.oracle.com;"modify_group -name=TESTING -add_targets="LISTENERTEST2:oracle_listener;DB4:oracle_database;DB8:oracle_database;DB7:oracle_database;DB10:oracle_database;DB5:oracle_database;DB1:oracle_database;

DB3:oracle_database;DB6:oracle_database;DB2:oracle_database;"logout

Alternatively the commands can be put into a shell script - eg

[oracle@rachvm1 emcliKit]$ pwd[oracle@rachvm1 emcliKit]$ /u01/emcliKit

vi adddatabase.shcontents of "adddatabase.sh" are:-

emcli login -username=sysman -password=oracle12emcli add_target -name="sally" -type="oracle_database" -host="machine1.uk.oracle.com"-credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:sally;Port:1528;OracleHome:/u01/orabase/11db;MachineName:machine1.uk.oracle.com"emcli add_target -name="test" -type="oracle_database" -host="machine1.uk.oracle.com"-credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:test;Port:1525;OracleHome:/u01/orabase/1107dbase;MachineName:machine1.uk.oracle.com"emcli add_target -name="LISTENERTEST" -type="oracle_listener" -host="machine1.uk.oracle.com"-properties="LsnrName:LISTENERTEST;ListenerOraDir:/u01/orabase/11107dbase/network/admin;Port:1525;OracleHome:/u01/orabase/11107dbase;Machine:machine1.uk.oracle.com"emcli logout


11 of 13 3/4/2015 12:42 AM

[oracle@rachvm1 emcliKit]$ chmod +x adddatabase.sh[oracle@rachvm1 emcliKit]$ . adddatabase.sh

Output is shown on the command line:-

Login successfulTarget "sally:oracle_database" added successfullyTarget "test:oracle_database" added successfullyTarget "LISTENERTEST:oracle_listener" added successfullyLogout successful[oracle@rachvm1 emcliKit]$

If a database has been added via emcli, it will straight away be monitored by Cloud Control, this means it will be seen as a target in theconsole straightaway and will not need to be promoted. This is because the dbsnmp details have been provided in the emcli input. At thismoment in time, there is no emcli promote command (for targets that have been auto discovered).

Note*If the agent is a management agent without the database plugin (eg. a newly discovered agent without the database pluginmanually deployed to it which has never discovered any targets of type database/listener or asm), and emcli is used to add the firstdatabase/listener or asm target, the database plugin will be automatically deployed as part of the discovery process. The databaseplugin will be deployed to $ORACLE_HOME/plugins/oracle.sysman.db.agent.plugin_12.1.0.X.0

For more details on emcli see:-

note:1396785.1 How to Install the 12c Enterprise Manager Cloud Control EMCLI on a Windows PCand http://docs.oracle.com/cd/E24628_01/em.121/e17786/toc.htm

E) Discovery AlgorithmThe discovery methods: 'discovery via guided processes', discovery using 'targets/databases/add" , automatic discovery and discovery via"run discovery now" all ultimately call the /plugins/oracle.sysman.db.discovery.plugin_/discover/oracledb.pl script. This script uses the following discovery algorithm:-

1.Agent checks whether $ORATAB and $TNS_ADMIN env variables are set. If so, it will read oratab file and networking files from theselocations.2. Agent obtains a list of SIDs and $ORACLE_HOMES on the host. On Unix the oratab file is read. On windows it reads the registry.3. Next, the Agent looks for TNS Listeners in the: $TNS_ADMIN/listener.ora and from each $ORACLE_HOME/network/admin/listener.ora. In 12.1.0.3 plugin, the agent also has the ability to parse a listener ifile.4. The listener version in each ORACLE_HOME is obtained5. Dynamic Discovery is run:-The agent checks for running pmon process for each of the sids discovered in step 1. Any which are not running, are now discludedfrom dynamic discovery.For each of the listeners, the agent creates a table in memory that includes the port, protocol, $ORACLE_HOME, and passwords foreach listener.The Agent runs the services command against each port to obtain a list of SIDs for that port.This is compared against the list of sids which have active pmon processesThe Database targets which have been found are assigned a target name using the format: db_name.dbdomain***

6. Static Discovery is run:-The agent creates a sid list from the sids listed in the listener.oraThe agent scans the static instance list, obtains the tcp port and reads the init.ora.If an spfile.ora is used (it will be converted to an init.ora file format, before it can be parsed. The sids are matched to list of sids found in step 1.The Database targets which have been found are assigned a target name using the format: db_name.dbdomain***

***Note:About the discovered database name:-


12 of 13 3/4/2015 12:42 AM

- if using Data Guard the discovered database name will be:- db_unique_name .dbdomain.

- If the names found in the discovery are not unique, a version number will be appended to the name. eg. orcl_1- If the spfile.ora cannot be read (or cannot be converted to a pfile) the database target will assume the name_. This would also show up in the emagent_perl.trc with errors such as:-ERROR: initParameterFileUtl::convertSPFileToPFile: Failed to convert spfileorERROR: initParameterFileUtl::getParameterFile: Cannot find any init parameter file for instance in oracle home

Master Note For Oracle Recovery Manager (RMAN) (Doc ID 1116484.1)

In this Document

DetailsActions Introduction Getting started with RMAN Rman compatibility Flash Recovery Area Configuring the Environment for RMAN Backups Recovery Catalog for Rman backups. Backing up Database files using RMAN and Maintaining the backup records. Restore and recovery techiques/scenarios using RMAN. Tablespace point in time recovery Rman Transportable tablespaces and database. Rman Duplicate Database Rman Performance. RMAN and Media managers Rman and Dataguard Rman and Rac Rman and Corruption Related Master Notes Using My Oracle Support Effectively Generic LinksReferences

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.1.0 [Release 10.1 to 11.2]Information in this document applies to any platform.

DETAILS

This Master Note is intended to provide an index and references to the most frequently used My Oracle Support Notes with respect to OracleRecovery Manager (RMAN).

In case you may want or need more about your current topic - please also access the Backup & Recover Community of Customersand Oracle Specialists directly via:https://community.oracle.com/community/support/oracle_database/database_backup_and_recovery

This Master Note is subdivided into categories to allow for easy access and reference to notes that are applicable to your area of interest,within RMAN.This includes the following categories:

Getting started with RMAN Rman compatibility Flash Recovery Area Configuring the environment for RMAN backups Recovery catalog for RMAN backups Backing up database files using RMAN and maintaining the backup records Restore and recovery techniques/scenarios using RMAN


1 of 9 3/4/2015 12:44 AM

Tablespace point in time recovery (TSPITR) RMAN Transportable tablespaces and database RMAN Duplicate database RMAN Performance. RMAN and Media managers. RMAN and Dataguard RMAN and Rac RMAN and Corruption Related Master Notes Using My Oracle Support Effectively Generic Links

ACTIONS

Introduction

Recovery Manager is Oracles utility to manage the backup, and more importantly the recovery, of the database. It eliminates operationalcomplexity while providing superior performance and availability of the database. Recovery Manager debuted with Oracle8 to provide DBAsan integrated backup and recovery solution.

Recovery Manager determines the most efficient method of executing the requested backup, restore, or recovery operation and thenexecutes these operations in concert with the Oracle database server. Recovery Manager and the server automatically identify modificationsto the structure of the database and dynamically adjust the required operation to adapt to the changes.

This note applies to the following versions of these products:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.xOracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.xOracle Server - Enterprise Edition - Version: 11.2.0.1 to 11.2.0.x

Getting started with RMAN

The articles in this section give you a overview of the oracle utility RMAN,the new features of RMAN in Oracle 11 release 1,2 and FAQ onRMAN.

Note.360416.1 Oracle10g / 11g - Getting Started with Recovery Manager (RMAN)Note 809867.1 RMAN 11gR1 : New FeaturesNote 1115423.1 Rman Enhancements In Oracle 11g.Note.469777.1 RMAN - Frequently Asked Question (FAQ)

Rman compatibility

Note.73431.1 RMAN Compatibility Matrix

Flash Recovery Area

The flash recovery area is an Oracle-managed directory, file system, or Automatic Storage Management disk group that provides acentralized disk location for backup and recovery files. All the files you need to completely recover a database from a media failure are partof the Flash Recovery Area. Oracle creates archived logs and flashback logs in the flash recovery area. RMAN can store its backup sets andimage copies in the flash recovery area, and it uses it when restoring files during media recovery. The flash recovery area also acts as a diskcache for tape.

The articles mentioned in the following section help you in understanding the concepts and working of flash recovery area,Rman integrationwith the flash recovery area,troubleshooting flash recovery area issues


2 of 9 3/4/2015 12:44 AM

Note.305648.1 What is a Flash Recovery Area and how to configure it ?Note.305796.1 RMAN and Flash Recovery AreaNote.833663.1 Flash Recovery Area - FAQNote.560133.1 Benefits Of Using Flash Recovery AreaNote.315098.1 How is the space pressure managed in the Flash Recovery Area - An Example.Note.305812.1 Flash Recovery area - Space management Warning & AlertsNote.829755.1 Space issue in Flash Recovery Area( FRA )Note.305810.1 Configuring file creation in Flash recovery area and order of PrecedenceNote.305651.1 How to change Flash Recovery Area to a new location ?Note.762934.1 Flash Recovery Area Sizing

Configuring the Environment for RMAN Backups

To simplify ongoing use of RMAN, you can set a number of persistent configuration settings for each target database. These settings controlmany aspects of RMAN behavior. For example, you can configure the backup retention policy, default destinations for backups, defaultbackup device type, and so on. You can use the SHOW and CONFIGURE commands to view and change RMAN configurations.

The articles mentioned in the following section help you in configuring the rman persistent configurations,understanding their behaviour andtroubleshooting them.

Note 305565.1 Persistent Controlfile Configurations for RMAN in 9i and 10gNote.462978.1 Rman backup retention policyNote.463875.1 Frequently asked questions on Rman backup retention policyNote.351455.1 Oracle Suggested Strategy & Backup Retention

Recovery Catalog for Rman backups.

A recovery catalog is a set of tables and views that Recovery Manager (RMAN) uses to store metadata (information about a databasestructure, archived redo logs, backup sets, and data file copies) about a target database (database that RMAN backups or restores). RMANuses this metadata to conduct its backup, recovery, and maintenance operations. Recovery catalog is optional, i.e., if a recovery catalog isnot created, RMAN uses the target databases control file to store the metadata about the target database. Although RMAN can conduct allmajor backup and recovery operations by using the control file, some RMAN commands work only if a recovery catalog exists.

The articles in the following section describe the configuration,managment of recovery catalog and some of the known issues related torecovery catalog.

Note.452529.1 Recovery catalog for RMAN backupNote.467969.1 How To Configure RMAN Recovery Catalog Using Enterprise Manager DB Console.

Backing up Database files using RMAN and Maintaining the backup records.

The articles and links in the following section describe the different methods to perform backups and useful rman backup methods.

Oracle Database Backup and Recovery Advanced User's Guide

Rman backup concepts - http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#i1006083Backing up database - http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#i1005689Advanced backups - http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckad.htm#CEGHFJCFBackup maintenance - http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmmaint.htm#j1006083

NOTE:388422.1 Top 10 Backup and Recovery best practicesNote 262853.1 10G RMAN Fast Incremental BackupsNote.745798.1 Merged Incremental Backup Strategies


3 of 9 3/4/2015 12:44 AM

Note.735953.1 How To Configure RMAN Backups To Tape via Oracle Enterprise [email protected] HOW TO CATALOG TAPE BACKUP PIECESNote.137181.1 RMAN Backup Shell Script Example

Restore and recovery techiques/scenarios using RMAN.

The articles in this section provide various restore and recovery techniques and scenarios what can be achieved using rman.

Note.144911.1 RMAN 9i Block-Level Media Recovery - Concept & ExampleNOTE:388422.1 Top 10 Backup and Recovery best practicesNote.94114.1 Backup and Recovery ScenariosNote.372996.1 Using RMAN to Restore and Recover a Database When the Repository and Spfile/Init.ora Files AreAlso LostNote.162855.1 RMAN Consistent Backup, Restore and Recovery using [email protected] How to recover the whole database from media failure while RMAN database backup is availableand no recovery catalog?Note.223543.1 How to Recover From a DROP / TRUNCATE / DELETE TABLE with RMANNote.403883.1 How To Restore Controlfile From A Backupset Without A Catalog Or AutobackupNote.580414.1 RMAN - How to restore the controlfile using RMANNote.419137.1 How To Restore Rman Backups On A Different Node When The Directory Structures Are DifferentNote.415579.1 HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another NodeNote.472536.1 10g RMAN Benefits of Simplified Recovery Through Resetlogs.Note.61994.1 Procedures/Restrictions for Point-In-Time Recovery without a Recovery CatalogNote.246325.1 Automated File Creation During RMAN RecoveryNote.358171.1 Oracle10g RMAN will not restore in parallel from tape

Tablespace point in time recovery

Recovery Manager (RMAN) Automatic TSPITR enables quick recovery of one or more tablespaces in a database to an earlier time withoutaffecting the rest of the tablespaces and objects in the database.Here are a few articles which explain the steps involved in performing aTSPITR:

Note.109979.1 RMAN Tablespace Point In Time Recovery (TSPITR) Procedure.Note.62332.1 TSPITR - An Example Walkthrough

Rman Transportable tablespaces and database.

Rman can be used to create transportable tablespace sets and can be used to convert the datafiles for cross platform transportabletablespace and database. Here are a few articles which provide all the required information to understand the procedures:

Note.371556.1 How move tablespaces across platforms using Transportable Tablespaces with RMANNote.455593.1 Creating a transportable tablespace set from RMAN backupsetsNote.831223.1 Using Rman Incremental backups To Update Transportable Tablespaces.Note.1401921.1 Cross-Platform Database Migration (across same endian) using RMAN Transportable DatabaseNote.733205.1 Migration of Oracle Database Instances Across OS Platforms

Rman Duplicate Database

Database duplication is the use of the DUPLICATE command to copy all or a subset of the data in a source database. The duplicate database(the copied database) functions entirely independently from the source database (the database being copied).In articles in this section helpyou in understanding the duplicate procedures and various techinques available for the rman duplicate operation.

Note.228257.1 RMAN 'Duplicate Database' Feature in Oracle9i / 10G and 11G


4 of 9 3/4/2015 12:44 AM

Note.452868.1 RMAN 'Duplicate Database' Feature in 11GNote.1113713.1 Creation Of Rman Duplicate Without Target And Recovery Catalog Connection.Note.388431.1 Creating a Duplicate Database on a New Host.Note.382669.1 Duplicate database from non ASM to ASM (vise versa) to a different hostNote.388424.1 How To Create A Production (Full or Partial) Duplicate On The Same HostNote.293717.1 How to duplicate a database to previous incarnationNote.1910175.1 RMAN DUPLICATE / RESTORE including Standby in ASM with OMF / non-OMF / Mixed Name forDatafile / Online Log / ControlfileNote.1913937.1 RMAN Duplicate Database From RAC ASM To RAC ASMNote.840647.1 Article on How to do Rman Duplicate on ASM/RAC/OMF/Single InstanceNote.360962.1 Manual Completion of a Failed RMAN DuplicateNote.369644.1 Answers To FAQ For Restoring Or Duplicating Between Different Versions And PlatformsNote.1079563.1 RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform SupportNote.1338233.1 Clone/Refresh Non-prod database from production

Rman Performance.

Note.360443.1 RMAN Backup PerformanceNote 740911.1 RMAN Restore PerformanceNote 247611.1 Known RMAN Performance ProblemsNOTE.579158.1 Advise On How To Improve Rman PerformanceNOTE.296985.1 RMAN Performance Data GatheringNote.463227.1 Oracle10g RMAN Recovery Catalog Known Performance Issues

RMAN and Media managers

Oracle designed an architecture that allows RMAN to manage the process of database backup and recovery, yet integrate with industry-leading tape storage management subsystems. The interface between Rman and media management vendor products is keyed on an Oracledesign specification. This specification allows Oracle RMAN to use third party media management software to back-up to and restore fromtape.

Many organizations rely on Oracle to provide solutions for very large or highly distributed mission critical systems. In addition to needingdatabases capable of handling large amounts of data and complex queries, these organizations also need robust backup and recoverytechnology. Recovery of data quickly and reliably is paramount should some aspect of the system fail. To address these needs, Oracle hascreated the Backup Solutions Program (BSP), a cooperative program designed to facilitate tighter integration between Oracle's backupproducts and those of third-party media management vendors. Together, Oracle and media management vendors provide robusteasy-to-use database backup and recovery solutions to customers with high-end requirements.

The link to access the information regarding backup solutions program is:

http://www.oracle.com/technetwork/database/features/availability/bsp-088814.html

"Under the BSP, vendors are committed to integrating Recovery Manager (RMAN) with their media management software packages andprovide first line technical support for the integrated backup and recovery solutions for Oracle RDBMS."

So any issues related to the media manager functionality or configuration has to be addressed only by the vendors and not by Oracle.

Below are a few articles which help you in understanding the most common issues with rman backups to tape, environment variable usedfor backups to tape and procedure to check if the media manager installation has been done properly.

Note.942418.1 How To Verify A Media Manager Layer Installation ?Note 1062824.6 RMAN: Unable to Backup with Third-Party Storage ManagerNote 227517.1 Main Index of Common Causes for ORA-19511NOTE.312737.1 RMAN and Specific Media Managers Environment Variables.

Rman and Dataguard


5 of 9 3/4/2015 12:44 AM

Data Guard and RMAN were both designed with the Oracle database architecture in mind. Together, they offer the most reliable and tightlyintegrated solution to achieve superior levels of Oracle database availability supporting your mission critical applications. Data Guard andRMAN are both fully supported features of the Oracle Database Enterprise Edition (RMAN is also provided with Oracle Database StandardEdition).Here are a few articles that help you in effectively using rman with dataguard and some of the known rman issues with dataguard.

Note.848716.1 Using RMAN Effectively In A Dataguard EnvironmentNote.357759.1 Known RMAN - Dataguard ProblemsNote.368336.1 10gR1 RAC/DataGuard/ASM physical standby deployment procedure

Rman and Rac

Note 243760.1 RMAN: RAC Backup and Recovery using RMANNote.415579.1 HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another NodeNote.1913937.1 RMAN Duplicate Database From RAC ASM To RAC ASMNote.840647.1 Article on How to do Rman Duplicate on ASM/RAC/OMF/Single Instance

Rman and Corruption

Rman is a very effective utility in identifying the database block corruption. Here are are a few article which provides the information aboutusing rman to detect and fix corruption.

Note.283053.1 How To Use RMAN To Check For Logical & Physical Database CorruptionNote 836658.1 Identify the corruption extension using RMAN/DBV/ANALYZE etcNote.561010.1 Which Blocks Will RMAN Check For Corruption Or Include In A Backupset?Note 428570.1 Best Practices for Avoiding and Detecting Corruption

Related Master Notes

Note 1199803.1 Master Note For Oracle Backup And RecoveryNote 1096952.1 Master Note for Real Application Clusters (RAC) Oracle Clusterware and Oracle GridInfrastructureNote 1088018.1 Master Note for Oracle Database CorruptionNote 1101938.1 Master Note for Data Guard

Using My Oracle Support Effectively

Note 736737.1 My Oracle Support - The Next Generation Support PlatformNote 730283.1 Get the most out of My Oracle SupportNote 747242.5 My Oracle Support Configuration Management FAQNote 868955.1 My Oracle Support Health Checks CatalogNote 166650.1 Working Effectively With Global Customer SupportNote 199389.1 Escalating Service Requests with Oracle Support Services

Generic Links

Note 854428.1 Patch Set Updates for Oracle ProductsNote 1061295.1 Patch Set Updates - One-off Patch Conflict ResolutionNote 881382.1 Critical Patch Update October 2009 Patch Availability Document for Oracle ProductsNote 967472.1 Critical Patch Update January 2010 Patch Availability Document for Oracle ProductsNote 1060989.1 Critical Patch Update April 2010 Patch Availability Document for Oracle ProductsNote 756671.1 Oracle Recommended Patches -- Oracle DatabaseNote 268895.1 Oracle Database Server Patchset Information, Versions: 8.1. 7 to 11.2.0Note 161549.1 Oracle Database Server and Networking Patches for Microsoft Platforms


6 of 9 3/4/2015 12:44 AM

Community DiscussionYou can directly participate in the Discussion about this article below. The Frame is the interactive live Discussion - not aScreenshot ;-)

All Places > My Oracle Support Community > Oracle Database (MOSC) > Database Backup and Recovery (MOSC) >

31732 Views Tags:

Average User Rating

(0 ratings)

My Rating:

Master Note For Oracle Recovery Manager (RMAN) [Note 1116484.1

Reem-Oracle May 21, 2013 4:05 AM

Master notes are intended to highlight articles for a particular area. I am posting this open discussion on the o

Note 1116484.1: Master Note For Oracle Recovery Manager (RMAN)

Reem

1. Re: Master Note For Oracle Recovery Manager (RMAN) [Note 1116484.1]Reem-Oracle May 21, 2013 4:05 AM (in response to Reem-Oracle)

Comments are encouraged.

Reem

REFERENCES

NOTE:967472.1 - Critical Patch Update January 2010 Patch Availability Document for Oracle ProductsNOTE:1060989.1 - Critical Patch Update April 2010 Patch Availability Document for Oracle Products


7 of 9 3/4/2015 12:44 AM

NOTE:1061295.1 - Patch Set Updates - One-off Patch Conflict ResolutionNOTE:1062824.6 - RMAN: Unable to Backup with Third-Party Storage ManagerNOTE:1088018.1 - Master Note for Handling Oracle Database Corruption IssuesNOTE:94114.1 - Backup and Recovery ScenariosNOTE:942418.1 - How To Verify A Media Manager Layer Installation ?NOTE:228257.1 - RMAN 'Duplicate Database' Feature in Oracle9i / 10G and 11.1NOTE:243760.1 - RMAN: RAC Backup, Restore and Recovery using RMANNOTE:246325.1 - Automated File Creation During RMAN RecoveryNOTE:1115423.1 - Rman Enhancements In Oracle 11g.NOTE:305565.1 - Persistent Controlfile configurations for RMAN in 9i and 10g.NOTE:1079563.1 - RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support

NOTE:109979.1 - RMAN: Tablespace Point In Time Recovery (TSPITR) Procedure.

NOTE:247611.1 - Known RMAN Performance ProblemsNOTE:262853.1 - RMAN Fast Incremental

Documents

Master Note for Oracle Database Auditing (Doc ID 1299033.1)