Master Note for Oracle Database Downgrade (Doc ID 1151427.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 Cloud

Control 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 not

found" 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 I nfo 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:-

<Target TYPE="oracle_listener" NAME="LISTENER11 203_machine1.uk.oracle.com"DISPLAY_NAME="LISTENER11203_machine1.uk.oracle.com" ON_HOST="" EMD_URL=" https://machine1.uk.oracle.com:3872/emd/main/ " TIMEZONE_REGION="" IDENTIFIER="TARGET_GUID=881E91 7E1CE1D3BECC361599ACDAEEEB"> <Property NAME="Password" VALUE="" ENCRYPTED="TRUE"/> <Property NAME="OracleHome" VALUE=" /oracle/orabase/11203rdbms"/> <Property NAME="LsnrName" VALUE="LI STENER11203"/>


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

<Property NAME="ListenerOraDir" VAL UE="/oracle/orabase/11203rdbms/network/admin"/> <Property NAME="Machine" VALUE="mac hine1.uk.oracle.com"/> <Property NAME="Port" VALUE="1522"/ > </Target>

B) Troubleshooting the Listener Up/down Status

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

Listener Home pageOracle listener (drop down menu)MonitoringIncident manager

2) check whether the listener name, listener direct ory and machine name 'monitoring configuration deta ils' 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 listener112 03LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 04-MAR-2013 09:51:55Copyright (c) 1991, 2011, Oracle. All rights reser ved.Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)( HOST=machine1.uk.oracle.com)(PORT=1522))) <--HOSTNAME andPORTSTATUS of the LISTENER------------------------Alias listener11203 <--LISTENER NAMEVersion TNSLSNR for Linux: Versio n 11.2.0.3.0 - ProductionStart Date 04-FEB-2013 09:29:25Uptime 28 days 0 hr. 22 min. 30 secTrace Level offSecurity ON: Local OS Authenticati onSNMP OFFListener Parameter File /oracle/orabase/11203rdbm s/network/admin/listener.ora <- LISTENER.ORA USED TO STARTTHE LISTENERListener Log File /oracle/orabase/diag/tnsl snr/machine1/listener11203/alert/log.xmlListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=machine 1.uk.oracle.com)(PORT=1522))) <-- HOSTNAME and PORTServices Summary...Service "cloudrep" has 2 instance(s). Instance "cloudrep", status UNKNOWN, has 1 handle r(s) for this service... Instance "cloudrep", status READY, has 1 handler( s) for this service...Service "cloudrepXDB" has 1 instance(s). Instance "cloudrep", status READY, has 1 handler( s) for this service...


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

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 de fined 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 /or acle/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:-

<Target TYPE="oracle_listener" NAME="LISTENER11203_ machine1.uk.oracle.com"DISPLAY_NAME="LISTENER11203_machine1.uk.oracle.com"ON_HOST="" EMD_URL="https://machine1.uk.oracle.com:3872/emd/main/ " TIMEZONE_REGION=""IDENTIFIER="TARGET_GUID=881E917E1CE1D3BECC361599ACDAEEEB"><Property NAME="Password" VALUE="" ENCRYPTED="TRUE" /><Property NAME="OracleHome" VALUE="/oracle/orabase/ 11203rdbms"/><Property NAME="LsnrName" VALUE="LISTENER11203"/><Property NAME="ListenerOraDir" VALUE="/oracle/orab ase/11203rdbms/network/admin"/><Property NAME="Machine" VALUE="machine1.uk.oracle. com"/><Property NAME="Port" VALUE="1522"/></Target>

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 -aLinux machine1 2.6.32-300.10.1.el5uek #1 SMP Wed Fe b 22 17:37:40 EST 2012 x86_64 x86_64 x86_64 GNU/Lin ux

b) ping <hostname returned from a>

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.c om.

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

eth0 Link encap:Ethernet HWaddr 18:03:73:BA:6 7: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 o verruns:0 frame:0 TX packets:56523244 errors:0 dropped:0 ov erruns: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 o verruns:0 frame:0 TX packets:939943068 errors:0 dropped:0 o verruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:306709243603 (285.6 GiB) TX byt es: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 machin e1

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 listene r 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 t he 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 'mai n' eg.

https://machine1.uk.oracle.com:3840/emd/browser/mai n/

3) Paste this into a browser. (notice that this met ric browser URL of the agent which monitors the 'pr oblem'listener, can be accessed from a browser on any mac hine 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 l istener,and click on it.

5) Then click on "Response". This will query the m etric 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 <-- Check the second column

Note that the tnsPing value could change, but the status '1' means that the listener is considered as 'Up'A down listener would show something like:-

Metric=Response Target=(oracle_listener,Listenerdb)


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

tnsPing Status oraerr 0 TNS-12541: TNS:no listener <--Check the second column

No status is returned when listener is considered as 'Down' but it will be accompanied by an error.b) Query the metric on the agent using 'getmetric' commandIf it is not possible to login to the metric browser query the Response Metric on the agent using the following syntax:-

emctl getmetric agent,oracle_listener,Response

This should show the same message as the metric browser. This is an alternative to use (if unable to run metric browser). If the agent isable to collect the metric successfully it will show:-

./emctl getmetric agent LISTENER11203_machine1.uk.o racle.com,oracle_listener,ResponseOracle Enterprise Manager Cloud Control 12c Release 2Copyright (c) 1996, 2012 Oracle Corporation. All r ights reserved.tnsPing,Status,oraerr0, 1, <--'1' means listener is up

If the listener is down, the following will be returned:-

./emctl getmetric agent Listenerdb,oracle_listener, ResponseOracle Enterprise Manager Cloud Control 12c Release 2Copyright (c) 1996, 2012 Oracle Corporation. All r ights reserved.tnsPing,Status,oraerr,0,TNS-12541: TNS:no listener <--error returned means listener is down

8) Check the severity history of the target on the agent itself.

a) If the listener is showing down in the console, but the metric browser or 'getmetric' is returning a '1' it means that the agent considersthe target as being up. Issue the command:-

emctl status agent target TARGET_NAME,TARGET_TYPE

eg.

[oracle@machine1 12.1.0.2.0]$ emctl status agent ta rget LISTENER11203_machine1.uk.oracle.com,oracle_li stenerOracle Enterprise Manager Cloud Control 12c Release 2Copyright (c) 1996, 2012 Oracle Corporation. All r ights reserved.--------------------------------------------------- ------------Target Name : LISTENER11203_machine1.uk.oracle.comTarget Type : oracle_listenerCurrent severity state----------------------Metric Column name Key State Timestamp--------------------------------------------------- -----------------------------Response Status n/a CLEAR Mon Feb 25 13:52:36 GMT 2013 <-- checkthe 'Status' columnResponse tnsPing n/a CLEAR Wed Feb 27 00:13:33 GMT 2013

This command shows the history of the target. If this shows that the states are 'CLEAR', then perform a 'clearstate' on the agent (step 10). If the last state shows a 'CRITICAL', then the agent considers that the listener is still down - eg.

emctl status agent target listenerdb,oracle_listene r

[oracle@machine1 12.1.0.2.0]$ emctl status agent ta rget Listenerdb,oracle_listenerOracle Enterprise Manager Cloud Control 12c Release 2Copyright (c) 1996, 2012 Oracle Corporation. All r ights reserved.--------------------------------------------------- ------------Target Name : ListenerdbTarget Type : oracle_listenerCurrent severity state----------------------Metric Column name Key State Timestamp--------------------------------------------------- -----------------------------


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

Response Status n/a CRITICAL Mon Mar 04 11:28:34 GMT 2013 <-- checkthe 'Status' columnResponse tnsPing n/a CLEAR Mon Mar 04 11:23:34 GMT 2013

9) Manually run the metric collection.

It can be useful to run the metric collection manually rather than wait for the agent to run the metric at it's scheduled time. Running themetric manually will help in situations where:-

The metric is not running on schedule (eg. has been suspended by the agent due to problems), but the metrics browser can nowevaluate the metric correctly.The listener has genuinely been stopped, but it has now been restarted and the metrics browser can evaluate the metric correctlyMetric is running at a non-default interval as set by an EM administrator, and does not capture changes in the listener status quickenough

Running the collection manually forces the agent to run the collection rather than waiting for it's scheduled time. To force the collection:-

emctl control agent runCollection:oracle_listener R esponse

For example:-

emctl control agent runCollection LISTENER11203_mac hine1.uk.oracle.com:oracle_listener ResponseOracle Enterprise Manager Cloud Control 12c Release 2Copyright (c) 1996, 2012 Oracle Corporation. All r ights reserved.--------------------------------------------------- ------------EMD runCollection completed successfully

10) Perform a clearstate on the agent

If the metrics browser returns a '1' indicating that the listener is up, but the listener is showing as down in the console, perform a clearstateon the agent.

emctl clearstate agent

This forces the agent to re-send the severity states of the targets to the OMS.

11) Run the lsnrresp.pl script manually

If the metric browser/getmetric command return listener status '0' but the output of "lsnrctl status" shows that the listener is running andthe monitoring configuration properties have been checked and are specified correctly. Try the following:-a) run the lsnrresp.pl script manually as outlined in note:1534087.1 "How to manually run the lsnrresp.pl script to troubleshoot listeneravailability issues in Enterprise Manager 12c Cloud Control". When running this script, the following values need to be set environmentally.

LSNR_MACHINELSNR_PORTLSNR_ORACLE_HOMELSNR_ORA_DIRLSNR_NAME

Ensure that that they match with the real values as indicated in Section B2. For example:-

export LSNR_MACHINE=machine1.uk.oracle.comexport LSNR_PORT=1522export LSNR_ORACLE_HOME=/oracle/orabase/11203rdbmsexport LSNR_ORA_DIR=/oracle/orabase/11203rdbms/netw ork/adminexport LSNR_NAME=listener11203

If the script runs successfully it should show the following output:-


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

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| <--'1' is returned in the second column if the listener is considered as 'up'

Or:-

perl lsnrresp.plDEBUG:has::Common::hasCheckForExecutableFile emcrsp is not present in cluster home /oracle/1020db at has/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|TNS-12541: TNS:no listener <-- An error is returned in the second column if listener is considered to be'down'

This should be the same result as returned by the metric browser/getmetric command. However if the script returns the correct result, butthe metric browser/get metric does not, it suggests that different environmental variables were used to test the script with which allowed itto be successful. In this case, carefully check the targets.xml or monitoring configuration in the console to ascertain the difference.b) Set debug tracing on the agent and collect the output from emagent_perl.trc output.To do this. Edit the <install home of agent>/agent_inst/sysman/config/emd.properties. Change:-

EMAGENT_PERL_TRACE_LEVEL=INFO

to

EMAGENT_PERL_TRACE_LEVEL=DEBUG

and stop and start the agent for the changes to tak e effect.

The DEBUG output will be written to:-

/agent_inst/sysman/log/emagent_perl.trc

Check the emagent_perl.trc for entries beginning with "lsnrresp.pl"

C) Commonly hit scenarios which cause incorrect listener status

i) The listener is down: tnsping not found in/bin.

Symptom: The listener is showing as 'down' in the console when it is really up. The accompanying message is:-

The listener is down: tnsping not found in /software/oracle/agent12c/core/12.1.0.1.0/bin.

Note that there should be no tnsping in the agent's home. In this particular circumstance, the user has entered the agent home instead ofthe home of the listeners home in the monitoring configuration "Oracle Home" field.Action: Ensure that the home entered in the monitoring configuration is the listener's home (the home from where the listener is running ). See step B2 for tips to check this.

ii) A listener process behaviour and identity is de fined by not just the listening end-points (the 'Ho st' and 'Port'), but also by the"Listener Parameter File" (listener.ora) which was used to start the listener process. The "Listener P arameter File" definesparameters like, logging and tracing levels, log/tr ace directories etc. in addition to the listening e nd-points, and hence, itslocation is essential for EM to uniquely identify a "Listener Target".

Symptom:The listener is down in the console, clicking on oracle listener (drop down menu)/monitoring/incident manager shows:-


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

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 <Target TYPE="oracle_listener" NAME="LISTENERTEST1" DISPLAY_NAME="LISTENERTEST1" ON_HOST=""EMD_URL="https://machine1.uk.oracle.com:3872/emd/main/" TIMEZONE_REGION=""IDENTIFIER="TARGET_GUID=DE430B6C9F12FA1DD836ECD5CD5F9856"> <Property NAME="Password" VALUE="" ENCRYPTED="TRUE"/> <Property NAME="Machine" VALUE="machine1.uk.oracle.com"/> <Property NAME="Key" VALUE="KEY_LISTENERTEST1"/> <Property NAME="OracleHome" VALUE="/oracle/orabase/11203hometwo"/> <Property NAME="LsnrName" VALUE="LISTENERTEST1"/> <Property NAME="ListenerOraDir" VALUE="/oracle/orabase/11203hometwo/network/admin/test"/> </Target>

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

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 pass word

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 messag e 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 messa ge 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<of listener>/binlsnrctl status (ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>)(PORT=<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 <install home of agent>\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:-<agent_inst>/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 <listenerName>:oracle_listener Response9) Check the <agent_inst>/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 <-- HERE IS THELOCATION OF THE TEMP FILEOutput on unix:-lsnrresp.pl: Fri Dec 6 15:14:38 2013: DEBUG: listenerUtil.pl :: oracletestfilename == /tmp/gPbuYYiWX4 <-- HERE IS THELOCATION OF THE TMP FILE

10) Check that the directory specified in the debug output is really a directory. For example, on the windows machine the directory is"C:\Temp". Confirm that this is a directory, and not a file - eg. check that there is not a file in c:\ called "Temp"Also check that the agent user has permissions on the temp directory. See also Note:818065.1 "Listener is Showing Down in Grid Controlwith Message:The listener is down Failed to run lsnrctl". Note that If the agent is running on windows, and it is started as the 'local systemaccount', then SYSTEM needs to have permission on this directory. If the agent is started as a different user, check that this user has thecorrect permissions on the directory.

Information to Collect

If the listener is showing the wrong status in the console, and the above note has not helped, please raise a SR with Oracle support, orcreate a thread in the community and include the following information:-

1) The name of the problem listener.2) upload the targets.xml 3) upload the listener.ora4) upload the output of:-lsnrctl status listener5) output of:ps -ef | grep tnslsnr6) Collect networking information:-a) output of uname -ab) ping uname -a>c) nslookupd) output of netstat -an | grepe) output of ipconfig -a7) Get the output of:-emctl status agent8) get results of:-emctl getmetric agent <listenerName>,oracle_listener,Response(or a screenshot of the metric browser - drilling down to problem listener target/response)9) get the results of:-


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

emctl status agent target <listenername>,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<of agent>/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 discover ed

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 Agent

1) 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 Add s Related Targets)Target types:Oracle Database, Listener and Automati c 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<ofagent>/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, L istener and Automatic Storage Management" shows as an "EnabledDiscovery Module"If not, click on "configure" and tick the relevant discovery modules (ensure that "oracle database, li stener 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 rele vant discovery modules(in the very least "Oracle Home Discovery" and "Ora cle Database, Listener and Automatic Storage Manage ment" 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<highlight host> choose 'run discovery now'Shows dialogue box "are you sure you want to run target discovery on <hostname>?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<ofagent>/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<ofagent>/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 modu les"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 <hostname>?" 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<click on the hyperlink for the agent host name> (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<of agent>/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"<select the relevant 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 EMCLI

Enterprise 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 <name returned from uname -a> 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 <newpassword>"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="<NametoAppearinConsole>" -type="oracle_database" -host="<host_name>" -credentials="UserName:dbsnmp;password:<dbsnmp_account_password>;Role:Normal" -properties="SID:<sid>;Port:<port>;OracleHome:<path_of_oracle_home>;MachineName:<hostname>"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="<target_name" -type="oracle_database" -host="<hostname>" -credentials="UserName:dbsnmp;password:<password>;Role:Normal" -properties="SID:<sid>;Port:<port>;OracleHome:<OH>;MachineName:<hostname>;PreferredConnectString:(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>)(PORT=<port>)))(CONNECT_DATA=(SERVICE_NAME=<sid>)))"

Note: For adding a database on Windows see Note:1597698.1

Listeners can be added by:-

emcli add_target -name="<listenerName>" -type="oracle_listener" -host="<hostname>" -properties="LsnrName:<listenerName>;ListenerOraDir:<path to listener.ora file>;Port:<port>;OracleHome:<path_to_oracle_home>;Machine:<hostname>"

for example:

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"

Note: For adding a listener on Windows see Note:1597698.1

These commands can be put in a script and run - eg.create a file called addtargets.txt. Contents of addtargets.txt is:-

login -username=sysman -password=oracle12syncadd_target -name="DB1" -type="oracle_database" -hos t="machine1.uk.oracle.com" -credentials="UserName:d bsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB1;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB2" -type="oracle_database" -hos t="machine1.uk.oracle.com" -credentials="UserName:d bsnmp;


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

password:dbsnmp;Role:Normal" -properties="SID:DB2;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB3" -type="oracle_database" -hos t="machine1.uk.oracle.com" -credentials="UserName:d bsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB3;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB4" -type="oracle_database" -hos t="machine1.uk.oracle.com" -credentials="UserName:d bsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB4;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB5" -type="oracle_database" -hos t="machine1.uk.oracle.com" -credentials="UserName:d bsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB5;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB6" -type="oracle_database" -hos t="machine1.uk.oracle.com" -credentials="UserName:d bsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB6;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB7" -type="oracle_database" -hos t="machine1.uk.oracle.com" -credentials="UserName:d bsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB7;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB8" -type="oracle_database" -hos t="machine1.uk.oracle.com" -credentials="UserName:d bsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB8;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB9G" -type="oracle_database" -ho st="machine1.uk.oracle.com" -credentials="UserName: dbsnmp;password:dbsnmp;Role:Normal" -properties="SID:DB9;P ort:1621;OracleHome:/oracle/orabase/11203hometwo;MachineName:machine1.uk.oracle.com;"add_target -name="DB10" -type="oracle_database" -ho st="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_list ener" -host="machine1.uk.oracle.com"-properties="LsnrName:LISTENER;ListenerOraDir:/orac le/orabase/11203hometwo/network/admin/;Port:1621;Or acleHome:/oracle/orabase/11203hometwo;Machine:machine1.uk.or acle.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" -ho st="rbridden-pc.uk.oracle.com" -credentials="UserNa me: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_list ener" -host="machine1.uk.oracle.com"-properties="LsnrName:LISTENER;ListenerOraDir:/orac le/orabase/11203hometwo/network/admin/;Port:1621;Or acleHome:/oracle/orabase/11203hometwo;Machine:machine1.uk.oracle.com;"modify_group -name=TESTING -add_targets="LISTENERTE ST2: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_databa se" -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_databas e" -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.c om"emcli add_target -name="LISTENERTEST" -type="oracle _listener" -host="machine1.uk.oracle.com"-properties="LsnrName:LISTENERTEST;ListenerOraDir:/ u01/orabase/11107dbase/network/admin;Port:1525;Orac leHome:/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 success fullyLogout 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<ofagent>/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 Algorithm

The discovery methods: 'discovery via guided processes', discovery using 'targets/databases/add" , automatic discovery and discovery via"run discovery now" all ultimately call the <install home of agent>/plugins/oracle.sysman.db.discovery.plugin_<plugin version>/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<sid>.ora.If an spfile<sid>.ora is used (it will be converted to an init<sid>.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<sid>.ora cannot be read (or cannot be converted to a pfile) the database target will assume the name<sid>_<hostname>. 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 <instancename> in oracle home <oracle_homeNote that these errors could be caused by different reasons. Eg. in the second case, this could be due to incorrect home specified inthe listener for the database, or the database might no longer exist, but entries are still present in the listener.ora and a pfile is stillpresent. To determine the true reason, it would be necessary to obtain a full emagent_perl debug trace. This is discussed innote:1543745.1

F) Troubleshooting Discovery Issues

For more information on troubleshooting discovery issues see note:1543745.1

Online Documentation References

Online Documentation: Enterprise Manager Cloud Control Adminstrators Guide/ Chapter 1: "Adding Targets"http://docs.oracle.com/cd/E24628_01/doc.121/e24473/discovery.htm#CBADGEFC

Enterprise Manager Command Line Interfacehttp://docs.oracle.com/cd/E24628_01/em.121/e17786/cli.htm

REFERENCES

NOTE:1371846.1 - How To Manually Add Database Targets in 12C Cloud Control and Known IssuesNOTE:1360183.1 - EM 12c: How to Deploy the Enterprise Manager Cloud Control 12c Linux x86 Agent From the Enterprise Manager 12.1Console (12.1.0.1, 12.1.0.2, 12.1.0.3)

NOTE:1543745.1 - Troubleshooting Database and Listener Discovery in Enterprise Manager 12c Cloud ControlNOTE:1388143.1 - EM 12c: How to Deploy the Latest Database Plugin to the OMS / Agent ?NOTE:1522674.1 - How to Disable Autodiscovery of Clusterware managed targets like Listeners, ASM or instances ?NOTE:1388774.1 - 12c: Plugin Deployment Fails With "Plug-in is not certified for the Operating System"NOTE:1396785.1 - How to Install the 12c Enterprise Manager Cloud Control EMCLI on a Windows PCNOTE:1908635.1 - How to Discover the Cluster and Cluster Database (RAC) Target in Enterprise Manager 12c


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

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 Oracle’s 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 M anager (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 Rec overy Area - An Example.Note.305812.1 Flash Recovery area - Space management Warning & A lertsNote.829755.1 Space issue in Flash Recovery Area( FRA )Note.305810.1 Configuring file creation in Flash recovery area a nd order of PrecedenceNote.305651.1 How to change Flash Recovery Area to a new locatio n ?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 retentio n 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 database’s 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 Enter prise 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 & Ex ampleNOTE: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 usin g [email protected] How to recover the whole database from media failu re while RMAN database backup is availableand no recovery catalog?Note.223543.1 How to Recover From a DROP / TRUNCATE / DELETE TA BLE with RMANNote.403883.1 How To Restore Controlfile From A Backupset Witho ut 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 W hen The Directory Structures Are DifferentNote.415579.1 HowTo Restore RMAN Disk backups of RAC Database t o Single Instance On Another NodeNote.472536.1 10g RMAN Benefits of Simplified Recovery Through Resetlogs.Note.61994.1 Procedures/Restrictions for Point-In-Time Recove ry 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) Pr ocedure.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 Transp ortable Tablespaces with RMANNote.455593.1 Creating a transportable tablespace set from RMAN backupsetsNote.831223.1 Using Rman Incremental backups To Update Transport able Tablespaces.Note.1401921.1 Cross-Platform Database Migration (across same end ian) using RMAN Transportable DatabaseNote.733205.1 Migration of Oracle Database Instances Across OS P latforms

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 / 1 0G 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 Reco very Catalog Connection.Note.388431.1 Creating a Duplicate Database on a New Host.Note.382669.1 Duplicate database from non ASM to ASM (vise vers a) to a different hostNote.388424.1 How To Create A Production (Full or Partial) Dupl icate On The Same HostNote.293717.1 How to duplicate a database to previous incarnati onNote.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/OM F/Single InstanceNote.360962.1 Manual Completion of a Failed RMAN DuplicateNote.369644.1 Answers To FAQ For Restoring Or Duplicating Betwe en Different Versions And PlatformsNote.1079563.1 RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Supp ortNote.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 Ma nagerNote 227517.1 Main Index of Common Causes for ORA-19511NOTE.312737.1 RMAN and Specific Media Managers Environment Vari ables.

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 deploymen t 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 Da tabase CorruptionNote 836658.1 Identify the corruption extension using RMAN/DBV/A NALYZE etcNote.561010.1 Which Blocks Will RMAN Check For Corruption Or Inc lude In A Backupset?Note 428570.1 Best Practices for Avoiding and Detecting Corrupti on

Related Master Notes

Note 1199803.1 Master Note For Oracle Backup And RecoveryNote 1096952.1 Master Note for Real Application Clusters (RAC) Or acle 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 Pl atformNote 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 Se rvices

Generic Links

Note 854428.1 Patch Set Updates for Oracle ProductsNote 1061295.1 Patch Set Updates - One-off Patch Conflict Resolut ionNote 881382.1 Critical Patch Update October 2009 Patch Availabi lity Document for Oracle ProductsNote 967472.1 Critical Patch Update January 2010 Patch Availabi lity Document for Oracle ProductsNote 1060989.1 Critical Patch Update April 2010 Patch Availabilit y Document for Oracle ProductsNote 756671.1 Oracle Recommended Patches -- Oracle DatabaseNote 268895.1 Oracle Database Server Patchset Information, Vers ions: 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 Backups using BCT = Block Change Tracking fileNOTE:1096952.1 - Master Note for Real Application Clusters (RAC) Oracle Clusterware and Oracle Grid InfrastructureNOTE:1113713.1 - Creation Of Rman Duplicate Without Target And Recovery Catalog Connection.NOTE:268895.1 - Oracle Database Patchset Information, Versions 10.2.0 to 12.1.0NOTE:283053.1 - How To Use RMAN To Check For Logical & Physical Database CorruptionNOTE:293717.1 - How to duplicate a database to a previous Incarnation

NOTE:1101938.1 - Master Note for Data GuardNOTE:462978.1 - Rman backup retention policyNOTE:305648.1 - What is a Flash / Fast Recovery Area and how to configure it ?NOTE:360962.1 - Manual Completion of a Failed RMAN Backup based DuplicateNOTE:419137.1 - How To Restore Rman Backups On A Different Node When The Directory Structures Are DifferentNOTE:428570.1 - Best Practices for Avoiding and Detecting CorruptionNOTE:452529.1 - Recovery catalog for RMAN backupNOTE:452868.1 - RMAN 'Duplicate From Active Database' Feature in 11GNOTE:455593.1 - Creating a transportable tablespace set from RMAN backupsetsNOTE:472536.1 - 10g RMAN Benefits of Simplified Recovery Through Resetlogs.NOTE:550082.1 - HOW TO CATALOG TAPE BACKUP PIECESNOTE:560133.1 - Benefits Of Using Flash Recovery AreaNOTE:561010.1 - Which Blocks Will RMAN Check For Corruption Or Include In A Backupset?NOTE:579158.1 - Advise On How To Improve Rman PerformanceNOTE:580414.1 - RMAN - How to restore the controlfile using RMANNOTE:61994.1 - Procedures/Restrictions for Point-In-Time Recovery without a Recovery CatalogNOTE:62332.1 - TSPITR - An Example Walkthrough.NOTE:730283.1 - Get the most out of My Oracle SupportNOTE:733205.1 - Migration Of An Oracle Database Across OS Platforms (Generic Platform)NOTE:73431.1 - RMAN Compatibility MatrixNOTE:735953.1 - How To Configure RMAN Backups To Tape via Oracle Enterprise Manager

NOTE:740911.1 - RMAN Restore PerformanceNOTE:745798.1 - Merged Incremental Backup StrategiesNOTE:747242.5 - My Oracle Support FAQNOTE:369644.1 - Frequently Asked Questions about Restoring Or Duplicating Between Different Versions And PlatformsNOTE:166650.1 - Working Effectively With Oracle Support - Best PracticesNOTE:1199803.1 - Master Note For Oracle Backup And RecoveryNOTE:756671.1 - Oracle Recommended Patches -- Oracle DatabaseNOTE:762934.1 - Flash Recovery Area SizingNOTE:809867.1 - RMAN 11gR1 : New FeaturesNOTE:829755.1 - Space issue in Fast / Flash Recovery Area - FRA FullNOTE:831223.1 - Using Rman Incremental backups To Update Transportable Tablespaces.NOTE:833663.1 - Flash Recovery Area - FAQNOTE:836658.1 - Identify the corruption extension using RMAN/DBV/ANALYZE etcNOTE:840647.1 - How to use Rman Duplicate on ASM/RAC/OMF/Single InstanceNOTE:848716.1 - Using RMAN Effectively In A Dataguard Environment.NOTE:854428.1 - Patch Set Updates for Oracle ProductsNOTE:868955.1 - Get Proactive - Oracle Health Checks - Installation, troubleshooting, catalog and more.NOTE:881382.1 - Critical Patch Update October 2009 Patch Availability Document for Oracle ProductsNOTE:305796.1 - RMAN and Flash Recovery AreaNOTE:305810.1 - Configuring file creation in Flash recovery area and order of PrecedenceNOTE:305812.1 - Flash Recovery area - Space management Warning & Alerts


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

NOTE:312737.1 - RMAN and Specific Media Managers Environment Variables.NOTE:315098.1 - How is the space pressure managed in the Flash Recovery Area - An Example.NOTE:463227.1 - Oracle10g RMAN Recovery Catalog Known Performance IssuesNOTE:463875.1 - Frequently asked questions on Rman backup retention policyNOTE:467969.1 - How To Configure RMAN Recovery Catalog Using Enterprise Manager DB Console.NOTE:469777.1 - RMAN -- Frequently Asked Question (FAQ)NOTE:305651.1 - How to change Flash Recovery Area to a new location ?NOTE:371556.1 - How to Migrate to different Endian Platform Using Transportable Tablespaces With RMANNOTE:372996.1 - Using RMAN to Restore and Recover a Database When the Repository and Spfile/Init.ora Files Are Also LostNOTE:382669.1 - DUPLICATE (Backup based) DATABASE from non ASM to ASM (vice versa) to different hostNOTE:388422.1 - Top 10 Backup and Recovery Best PracticesNOTE:388424.1 - How To Create A Production (Full or Partial) Duplicate On The Same HostNOTE:388431.1 - Creating a Duplicate Database on a New Host (non ASM).NOTE:403883.1 - How To Restore Controlfile From A Backupset Without A Catalog Or AutobackupNOTE:415579.1 - HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another NodeNOTE:1338233.1 - Clone/Refresh Non-prod database from productionNOTE:137181.1 - RMAN Backup Shell Script ExampleNOTE:1401921.1 - Cross-Platform Database Migration (across same endian) using RMAN Transportable DatabaseNOTE:144911.1 - RMAN : Block-Level Media Recovery - Concept & ExampleNOTE:162855.1 - RMAN : Consistent Backup, Restore and Recovery using RMANNOTE:199389.1 - How To Escalate a Service Request (SR) with Oracle Support ServicesNOTE:227517.1 - Main Index of Common Causes for ORA-19511NOTE:223543.1 - How to Recover From a DROP / TRUNCATE / DELETE TABLE with RMANNOTE:357759.1 - Known RMAN - Dataguard ProblemsNOTE:358171.1 - Oracle10g: RMAN will not restore in parallel from tapeNOTE:360416.1 - Getting Started with Recovery Manager (RMAN)NOTE:360443.1 - RMAN Backup PerformanceNOTE:351455.1 - Oracle Suggested Strategy & Backup RetentionNOTE:1910175.1 - RMAN DUPLICATE / RESTORE including Standby in ASM with OMF / non-OMF / Mixed Name for Datafile / Online Log /ControlfileNOTE:1913937.1 - RMAN DUPLICATE Database From RAC ASM To RAC ASM


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

Master Note For Oracle Database Auditing (Doc ID 1299033.1)

In this Document

PurposeScopeDetails Oracle Database Auditing Concepts and Overview What auditing will NOT provide Oracle Database Auditing Installation Oracle Database Auditing Configuration and Administration Enabling Auditing Configuring what must be audited Auditing SQL Statements Auditing Privileges Auditing Schema Objects Auditing Network Activity Auditing SYSDBA/SYSOPER activities Oracle Database Auditing Performance Overhead Frequently Asked Questions How do I audit the actions executed by the proxy users on behalf of the real users? Why do I have so many audit records ? After upgrading my database much more audit records are produced. Why? I have declared what must be audited but the audited event produces no audit records. Why? I have removed the auditing categories using the NOAUDIT statement yet audit records are still produced. Why? Auditing was disabled and the database was restarted yet I see that many audit files are written into the audit file destination

directory. Why? I want to declare an auditing category for all the users except one. How can I do it? I removed all the auditing categories using the script from Note 287436.1 yet I still have audit records created even after

restarting the database. Why? How do I audit the "alter system set NLS_DATE_FORMAT=..." statements? Why do I have messages like "USER xx is being audited for all SELECTS" in the alert.log ? Oracle Database Auditing HOWTOs Oracle Database Auditing Troubleshooting Auditing related parameters and views Scripts Oracle Database Auditing Best Practices Oracle Database Auditing Documentation Using My Oracle Support EffectivelyReferences

APPLIES TO:

Oracle Database - Enterprise Edition - Version 8.1.7.4 to 12.1.0.1 [Release 8.1.7 to 12.1]Information in this document applies to any platform.

PURPOSE

This Master Note is intended to provide an index and references to the most frequently used My Oracle Support Notes with respect to OracleDatabase Auditing. This Master Note is subdivided into categories to allow for easy access and reference to notes that are applicable to yourarea of interest.


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

SCOPE

This document is meant for use as a guide by those who are configuring or managing/troubleshooting Oracle Database Auditing.

DETAILS

Oracle Database Auditing Concepts and Overview

Database auditing is the process of recording, monitoring and reporting of the actions performed on a database. It allows the securityauditors to observe whether the database users are using the database according to the established policies and that there are no policyviolations. Database Auditing facilitates the analysis of the database activity patterns/trends and it can help in the process of gathering thehistorical data about a particular database user or activity.

One can use standard auditing to audit SQL statements, privileges, schemas, objects, and network and multitier activity. Alternatively, onecan use Fine Grained Auditing (available only in Enterprise Edition) to monitor specific database activities based on factors such as actionson a database table or times when those activities occur. FGA is very flexible since the audit_condition can reference a PL/SQL function thatwill control whether the audit record is produced or not.

Reasons for using auditing include:Enabling future accountability for current actionsDeterring users (or others, such as intruders) from inappropriate actions based on their accountabilityInvestigating, monitoring, and recording suspicious activityAddressing auditing requirements for compliance

What auditing will NOT provide

Auditing is unsuitable to answer questions about how many rows or what particular data is returned for a specific SQL statement. AlsoCOMMIT and ROLLBACK statements are not audited, this means even if a particular DML statement is recorded in the audit trail, there's noguarantee that it resulted in any database changes (since SYS auditing simply records everything, that would be the exception), for suchrequirements consider to use other features such as Flashback Data Archive.

Oracle Database Auditing Installation

The database standard auditing is a feature available by default in all the database editions.

Oracle Database Auditing Configuration and Administration

To use auditing one must first enable it and then define exactly what must be audited. The audited actions are recorded either in theSYS.AUD$ table or in operating system files.

Enabling Auditing

The auditing is enabled by setting the AUDIT_TRAIL parameter to a value different than NONE followed by a restart of the database. The following table presents all the possible legal values for the AUDIT_TRAIL parameter:

NONE Auditing is disabledDB The auditing is enabled and the audit data is written to the

SYS.AUD$ tableDB,EXTENDED Behaves as DB but also populates the SQL_TEXT and SQL_BIND

columnsOS The auditing is enabled. On Unix the audit data is written to text

files which are located in the directory specified viaAUDIT_FILE_DEST. On Windows the audit data will be sent to theEvent Viewer.


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

XML The auditing is enabled and the audit data is written to XML fileswhich are located in the directory/folder specified viaAUDIT_FILE_DEST. This is the case for Windows as well.

XML,EXTENDED Behaves as XML but also populates the SQL_TEXT and SQL_BINDtags

As seen in the above table the location where the audit data is sent to is controlled by the AUDIT_TRAIL parameter. When this parameter isset to OS, XML or XML_EXTENDED the exact location of the audit data is controlled by AUDIT_FILE_DEST and AUDIT_SYSLOG_LEVEL.Other factors that influence the exact location for the audit data are :

- the status of the database (started or shutdown) - whether the user running the audited event is a privileged user or not

The following table shows what will happen when using different combinations for these parameters/factors:

Whether database auditing is enabled or disabled, Oracle will always audit certain database actions into the OS audit trail. There is noway to change this behaviour because it is a formal requirement of the security evaluation criteria. See Note 308066.1 for details.

Note that when the database is down the SYSDBA actions will be logged into a default location. On Unix the first default location is$ORACLE_BASE/admin/ORACLE_SID/adump. If this first default location is not available then the database will try to write theaudit record to $ORACLE_HOME/rdbms/audit. On Windows the default location is the Event Log . The reason is that when thedatabase is down the value of AUDIT_FILE_DEST is unknown and as such we write the mandatory audit records to a default location.

To read more about using the AUDIT_SYSLOG_LEVEL parameter see Note 553225.1.


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

Configuring what must be audited

To specify what has to be audited one has to use the AUDIT SQL statement. With this command it is possible configure the audit of SQLstatements, privileges, schema objects, and furthermore of network and multitier activities. To undo the effects of the AUDIT command onecan use the NOAUDIT command. You can read about how NOAUDIT command works in the following note:

Note 1068714.6 - How does the NOAUDIT option work

Note:

It is important to note that the auditing categories will not be taken into account by the sessions which were started before running theAUDIT command. Only the sessions that will be initiated after declaring what must be audited will create audit records according to thenew rules. Equally when you execute the NOAUDIT statement the sessions started before executing it will continue to create auditrecords.

If there are audited categories defined but audit_trail is set to NONE/FALSE then there will be no audit records produced for the nonSYSDBA users.

Note 167293.1 provides some examples about declaring the audit categories and their output.

Auditing SQL Statements

Statement auditing allows you to audit the execution of a certain SQL command regardless of what object is accessed. The audit commandwill be followed by the name of the statement that will be monitored.

For example, you can audit the CREATE TABLE statement:

audit CREATE TABLE by scott;

Or you can audit a list of statements regardless of who executes them:

audit CREATE TABLE, CREATE VIEW, ALTER USER;

There are statement auditing options which are grouping several SQL statements. For example, one can run the following statement to auditthe CREATE INDEX, DROP INDEX, ALTER INDEX and ANALYZE INDEX individual statements:

audit INDEX;

If the above statements must be audited only when user SCOTT executes them then run this:

audit INDEX by scott;

All these shortcut statement auditing options are listed in table 3.1 in the documentation.

Note: For some specific statements we do not have a dedicated audit option. This is the case for the "drop table" or "drop view"statements. To audit these it is necessary to use the statement shortcuts(e.g. audit table).

It is possible to specify all the shortcut statement auditing options via the following command:


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

audit ALL whenever SUCCESSFUL;

To see what are the enabled statement auditing options one can use the DBA_STMT_AUDIT_OPTS view:

select USER_NAME,AUDIT_OPTION from DBA_STMT_AUDIT_O PTS;

USER_NAME AUDIT_OPTION---------------------- ----------------------SCOTT INDEX DROP PROFILE ALTER PROFILE CREATE VIEW UPDATE TABLE

Auditing Privileges

Privilege auditing allows you to monitor the usage of a system privilege. You must have the AUDIT SYSTEM system privilege before you canenable auditing of system privileges. You can audit the use of any system privilege. Privilege auditing options match the correspondingsystem privileges:

SQL> audit <system privilege>;

To see all the system privileges run the following query:

SQL> select name from system_privileges_map;

For example, the option to audit the use of the DELETE ANY TABLE privilege is DELETE ANY TABLE:

SQL> AUDIT DELETE ANY TABLE BY ACCESS WHENEVER NOT SUCCESSFUL;

Privilege auditing can audit the activities of all database users or of only a specified list. For example, you can audit the usage of the SELECTANY TABLE privilege by any user:

SQL> audit select any table;

The above audit statement instructs the database to audit any usage of the SELECT ANY TABLE privilege. It will not cause the audit of anyselect statement on whatever table if the SELECT ANY TABLE privilege will not be used. If an user will access an object using an objectprivilege or an implicit object privilege(it owns the object) then the above auditing category will not cause any record to be dumped into theaudit trail.

You can also audit the usage of SELECT ANY TABLE and DELETE ANY TABLE privileges by users SCOTT and SYSTEM:

SQL> audit select any table, delete any table by sc ott, system;

To see what are the audited system privileges one can use the DBA_PRIV_AUDIT_OPTS view:

SQL> select user_name, privilege from dba_priv_audi t_opts;

USER_NAME PRIVILEGE------------------------------ -------------------- --------------------SCOTT SELECT ANY TABLE


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

SCOTT CREATE ANY TABLE CREATE ANY JOB

Use Note 287436.1 to get the AUDIT/NOAUDIT commands for the currently enabled statement and system privileges audit options.

Auditing Schema Objects

Object auditing allows you to specify that an audit record will be produced whenever a certain object was accessed. It can audit all thestatements permitted by the object's privileges. The GRANT and REVOKE statements that control those privileges are also audited.

It is important to note that object auditing does not allow you to control the creation of the audit record based on the user who accessesthe object.

For example, you can audit all the queries executed successfully on table scott.emp:

audit select on SCOTT.EMP whenever successful;

You can also audit all the delete statements executed on scott.emp:

audit delete on SCOTT.EMP by access;

Or you can audit all the statements permitted by the object:

audit ALL on SCOTT.EMP;

If one wants to make sure that the queries executed on the tables that will be created in the future will be audited then the followingcommand must be executed:

audit select on DEFAULT;

To see what are the enabled object auditing options use view DBA_OBJ_AUDIT_OPTS:

SQL> select * from dba_obj_audit_opts;

OWNER OBJECT_NAME OBJECT_TYPE ALT AUD COM DEL GRA IND INS LOC REN SEL UPD REF EXE CRE REA WRI FBK------------------------------ -------------------- ---------- ----------------------- --- --- --- --- --- ------ --- --- --- --- --- --- --- --- --- ---

SCOTT BONUS TABLE A/A A/A A/A A/A A/A A/A A/A A/A A /A A/A A/A -/- -/- -/- -/- -/- A/ASCOTT DEPT TABLE A/A A/A A/A A/A A/A A/A A/A A/A A/ A A/A A/A -/- -/- -/- -/- -/- A/ASCOTT EMP TABLE A/A A/A A/A A/A A/A A/A A/A A/A A/A S/S A/A -/- -/- -/- -/- -/- A/ASCOTT SALGRADE TABLE A/A A/A A/A A/A A/A A/A A/A A/ A A/A A/A A/A -/- -/- -/- -/- -/- A/ASCOTT TEST PROCEDURE -/- A/A -/- -/- A/A -/- -/- -/ - A/A -/- -/- -/- A/A -/- -/- -/- -/-

Auditing Network Activity


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

You can use the AUDIT statement to audit unexpected errors in network protocol or internal errors in the network layer. The types of errorsuncovered by network auditing are not connection failures, but can have several other possible causes. One possible cause is an internalevent set by a database engineer for testing purposes. Other causes include conflicting configuration settings for encryption, such as thenetwork not finding the information required to create or process expected encryption.

To enable network auditing run the following command:

SQL> AUDIT NETWORK;

To disable network auditing, enter the following:

SQL> NOAUDIT NETWORK;

Auditing SYSDBA/SYSOPER activities

Note 174340.1 - Audit SYS User Operations.

Please note that a SYSDBA or SYSOPER connection to the database is always audited. Sometimes this can lead to the creation of anexcessive number of audit files. When this is considered to be a problem it cannot be solved at the database side and it must be investigatedwhy the 'client' applications (including Enterprise Manager components and agents) are connecting so frequently as SYSDBA/SYSOPER. Formore information about excessive audit files see :

note 1171314.1 Huge/Large/Excessive Number Of Audit Records Are Being Generated In The Database

Oracle Database Auditing Performance Overhead

Oracle Database Auditing is relatively inexpensive.

The exact performance impact on any given database cannot be assessed without testing. The performance degradation is proportional tothe number of the audited statements. Setup a detailed, well planned auditing strategy before you start auditing and then test theperformance impact on your database.

See also:Note 1509723.1 - Oracle Database Auditing Performance

Frequently Asked Questions

How do I audit the actions executed by the proxy users on behalf of the real users?

To audit the actions executed by the proxy users on behalf of the end users run the following statement:

audit <privilege / statement> by <proxy user> on be half of <end user>;

Note that before 11.2.0.2, because of bug 8604905, the above statement was not sufficient so one had to execute the following statementas well:

audit <privilege / statement> by <end user> by acce ss;


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

See the following notes for more details:

Note 782078.1 - Proxy Users and Auditing Proxy UsersNote 1074690.1 - How To Monitor The Identity Of A Proxy Enterprise User In The Audit Trail?Note 1357829.1 - Declaring Auditing Categories With 'ON BEHALF OF' Clause Not Working With 'BY ACCESS' or 'BY SESSION'

Why do I have so many audit records ?

See Note 1171314.1 - Huge/Large/Excessive Number Of Audit Records Are Being Generated In The Database

After upgrading my database much more audit records are produced. Why?

This is the result of the fix for bug 6023472 which changes the behaviour of the auditing configured as 'By Session'. Each occurrence of theaudited event will result in a new audit record. This fix is included in patchsets 10.2.0.5 and 11.1.0.7. 11gR2 base release (11.2.0.1)includes the fix as well. The list of all the auditing changes introduced by this fix can be seen in Note 6023472.8.

Please note that when you audit BY SESSION in a database which is patched with the fix for 6023472, each audited action will produce anew record and the name of the action in the audit trail will be SESSION REC(format is still the old format). If you do not specify BYACCESS explicitly in AUDIT commands, it audits by session.

See as well:Note 1375419.1 - Obsoleted "BY SESSION" Audit Option Leads to Massive Audit Output (Huge AUD$)Note 852815.1 - AUD$ Growing After Upgrade to 11g or ATC patch installed

I have declared what must be audited but the audited event produces no audit records. Why?

You need to make sure that the sessions executing the statements meant to produce audit records are started after declaring the auditingcategories. Furthermore make sure that that the audit_trail parameter is set to the correct value, that the database was restarted aftersetting the audit_trail parameter and that you are looking at the right audit trail( AUD$ if audit_trail=DB, etc.).

I have removed the auditing categories using the NOAUDIT statement yet audit records are still produced. Why?

The sessions started before executing the NOAUDIT statement will continue to produce the audit records according the old auditing rules.Only the new sessions will behave according to the new settings. Furthermore it is possible that the users are enabling auditing for theircurrent sessions with a statement like this :

AUDIT <privilege name> IN SESSION CURRENT;

Whomever is analyzing this problem might not be immediately aware of this because this session specific auditing might be enabled via aLOGON trigger like the following:

create trigger MY_LOGON_TRIGGER after logon on data base

begin

execute immediate 'audit select table in session cu rrent';

end;

/


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

Auditing was disabled and the database was restarted yet I see that many audit files are written into the audit file destinationdirectory. Why?

These audit files might include audit information related to the operations performed by the privileged users. This behaviour is expected andis documented in Note 308066.1.

I want to declare an auditing category for all the users except one. How can I do it?

It is not possible to declare a generic auditing category and then run a statement that will remove that auditing category for some users.Equally it is not possible to declare auditing selectively( e.g . audit <priv> by all users except X). As such the only way to achieve this is touse PL/SQL. If for example you want to audit the usage of the create session privilege for all users except DBSNMP then you have to runthe following PL/SQL block:

declarecursor c1 is select username from dba_users where u sername not in ('SYS','DBSNMP');beginfor rec in c1 loopexecute immediate 'audit create session by '||rec.u sername;end loop;end;/

I removed all the auditing categories using the script from Note 287436.1 yet I still have audit records created even after restartingthe database. Why?

Note 287436.1 will undo only the statement and the privilege level auditing categories but will not remove the object auditing categories. Tosee these you can run the following query :

select owner, object_name, object_type,alt,aud,com,del,gra,ind,ins,loc,ren,sel,upd,ref,exefrom sys.dba_obj_audit_optswherealt !='-/-' or aud !='-/-' or com !='-/-'or del !='-/-' or gra !='-/-' or ind !='-/-'or ins !='-/-' or loc !='-/-' or ren !='-/-'or sel !='-/-' or upd !='-/-' or ref !='-/-' or exe !='-/-'/

How do I audit the "alter system set NLS_DATE_FORMAT=..." statements?

Statements for 'alter session', which do not require a privilege, cannot be audited. For example "alter session set sql_trace=true"requires that the user executing it is granted the 'alter session' privilege. "Alter session set cursor_sharing=...", by contrast does notneed the alter session privilege and as such cannot be audited.

An enhancement request has already been logged to request that the functionality be changed to add this feature in a future release.


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

Why do I have messages like "USER xx is being audited for all SELECTS" in the alert.log ?

See Note 1497187.1 - Why are there Audit Log Messages In the Alert.log like: USER xx is being audited for all SELECTS

Oracle Database Auditing HOWTOs

Note 1020945.6 - How to Setup AuditingNote 1080112.1 - How To Shrink AUD$ IN ORACLE 10GNote 175292.1 - Overview Auditing: Possibilities of Auditing, using Triggers and FGANote 174556.1 - 9i/9.2: Fine Grained AuditingNote 266896.1 - 10g: Fine Grained AuditingNote 1407434.1 - How To Audit Direct Path Load And Unload Activities?Note 278184.1 - 9i and 10g: Installing Oracle Label Security Automatically Moves AUD$ Table out from SYS into SYSTEM schemaNote 175259.1 - Using autonomous triggers to audit detailed information.Note 209801.1 - How to Disable Audit Action 103 to Avoid Unnecessary Rows in Table SYS.AUD$Note 158348.1 - How to Find Results Back in Data Dictionary When Using AUDIT SYSTEM GRANTNote 166301.1 - How to Reorganize SYS.AUD$ TableNote 230845.1 - How to Import SYS.AUD$ Table from 8i to 9i Database When SYS User is not ExportedNote 222807.1 - How To Audit GRANT ANY PRIVILEGE Or GRANT ANY ROLENote 239621.1 - How to audit 'analyze index'Note 199419.1 - How to Avoid Common Flaws and Errors Using Fine Grained AuditingNote 99786.1 - How to Audit User Connection, Disconnection Date and TimeNote 73408.1 - How to Truncate, Delete, or Purge Rows from the Audit Trail Table SYS.AUD$Note 1025832.6 - How to audit data changes in tables using triggersNote 103964.1 - How to Audit Connect Internal Using Oracle ServerNote 208855.1 - What is Audit Action 103 ?Note 282091.1 - How to find Whether an OBJECT-level Audited by ACCESS Statement Succeeded or FailedNote 174340.1 - Audit SYS user OperationsNote 308066.1 - AUDIT_SYS_OPERATIONS Set To FALSE Yet Audit Files Are GeneratedNote 1025314.6 - Descriptions of action code and privileges used in fields in SYS.AUD$ tableNote 167293.1 - Some examples about auditing and output of auditingNote 41800.1 - Quick Reference to Auditing InformationNote 293973.1 - Find List Of All Possible Keywords In Audit Log FilesNote 99137.1 - Setting up, Interpreting Auditing Using Windows NT Event ViewerNote 1049048.6 - Auditing with Oracle Parallel ServerNote 72291.1 - VMS The AUDIT_TRAIL=OS Initialization Parameter on OpenVMSNote 221944.1 - How to Audit a User Who is Trying to Break DB Username/PasswordNote 123128.1 - How To Identify an RDBMS session using AUDSIDNote 274697.1 - LOGOFF and LOGOFF BY CLEANUP Do Not Have Any LOGON Records in DBA_AUDIT_TRAIL and Vice-VersaNote 277219.1 - How to Retrieve the Whole Audited SQL Statement From DBA_FGA_AUDIT_TRAIL View ?Note 310873.1 - Audit Record written When We Select From View even if The Audited Column Is Not SelectedNote 309798.1 - How to Trace Specific Database Users to Collect Full DML Statements ExecutedNote 282091.1 - How to find Whether an OBJECT-level Audited by ACCESS Statement Succeeded or FailedNote 271615.1 - Timestamp And Logoff_time Columns In Audit views Are In Different Time ZonesNote 402528.1 - How to cleanup the log table FGA_LOG$ ?Note 414666.1 - Audit Action #283Note 427296.1 - Why is column TIMESTAMP# having NULL values in AUD$ and FGA_LOG$ tables?Note 469007.1 - SCRIPT: How To Apply the Same Fine Grained Audit Policy To All Tables In A SchemaNote 731908.1 - New Feature DBMS_AUDIT_MGMT To Manage And Purge Audit InformationNote 731782.1 - Format Of OS Audit Files Changes Starting with 10.2.0.4 and 11.1.0.7Note 794402.1 - What Is the Expected Behavior Of The Oracle Database Instance When The Audit Trail is Full And Cannot ExtendAnymore?


10 of 13 3/4/2015 12:45 AM

Oracle Database Auditing Troubleshooting

Note 1392161.1 - Queries on XML Audit Trail Views Crash With: ORA 600 [KZAXGFL:IDX]Note 1495463.1 - SYS.AUD$ SQLBIND Clob Column Truncating Bind values Data At 4000 BytesNote 1393275.1 - ORA-600 [kzaxpopr14 -error in decoding xml text] When Querying V$Xml_audit_trailNote 334486.1 - SYS.AUD$ Table Not Found Though Exists in SYS.OBJ$Note 1063941.6 - LRM-00101: Unknown parameter name 'AUDIT_FILE_DEST' when config auditing on NTNote 74725.1 - How often tables are accessed (AUDIT)Note 1372067.1 - Audit Action# 102 Is Not Written To Aud$ If session Exceeds A Profile LimitNote 166674.1 - Auditing Does Not Supply A Full Name Of TriggersNote 1068714.6- How does the NOAUDIT option workNote 1019326.102- SES_ACTIONS in DBA_AUDIT_OBJECTNote 130146.1 - Auditing DML (Insert, Update and Delete)Note 363590.1 - How to Retrieve DML Statements Text and Values from Bind VariablesNote 107842.1 - Application Log is Full with Event ID 34 : Audit Trail:Connect InternalNote 106823.1 - Unknown Users Comparing sys.aud$ and user_audit_sessionNote 125378.1 - ORA-2096 setting TRANSACTION_AUDITING dynamicallyNote 197598.1 - Audit users with "DROP ANY TABLE" privilege: example client event triggerNote 267389.1 - AUDIT CREATE PROCEDURE Does not Audit "Create OR Replace Procedure" StatementsNote 198468.1 - SYS.AUD$ Filling up Fast When Auditing Failed Logon Attempts Because of DBSNMP.Note 240766.1 - ORA-00904 When Using RAWTOLAB Function on SYS.AUD$ Columns OBJ$LABEL and SES$LABELNote 246665.1 - ORA-22921 When Fine Grained Auditing with Multibyte Character Set in 9.2.0.3Note 316915.1 - Unexpected Audit Records Are Generated Within APPS When CREATE SESSION is Audited ActionNote 310876.1 - CREATE USER System Privilege Not Being AuditedNote 343413.1 - Default Actions Audited in OS Audit Files Contain Messages for Completed Archive Operations

Auditing related parameters and views

Note 30690.1 - Init.ora Parameter "AUDIT_TRAIL" Reference NoteNote 39796.1 - Init.ora Parameter "AUDIT_FILE_DEST" Reference NoteNote 72203.1 - OERR ORA-16006 audit_trail destination incompatible with database open modeNote 19287.1 - OERR ORA 2002 error while writing to audit trailNote 21073.1 - OERR ORA-9925 "Unable to create audit trailNote 20985.1 - OERR ORA-9822 Translation of audit file name failed.Note 249438.1 - 10G: New Value DB_EXTENDED for the AUDIT_TRAIL init.ora ParameterNote 1503726.1 - Compendium of Audit Views

Scripts

Note 287436.1 - SCRIPT: Generate AUDIT and NOAUDIT Statements for Current Audit SettingsNote 1019377.6 - Script to move SYS.AUD$ table out of SYSTEM tablespaceNote 1019552.6 - Script to Show Audit Options/Audit TrailNote 279169.1 - Script: How To Store the Checksum of PL/SQL Code

Oracle Database Auditing Best Practices

Plan your auditing strategy carefully to limit the number of audited events as much as possible but make sure that the security is notcompromised because of this. This will minimize the performance impact on the execution of statements that are audited and will alsominimize the size of the audit trail.

Manage your audit trails properly using DBMS_AUDIT_MGMT( Note 731908.1 ) starting with release 11.2 or use the methoddescribed in Note 73408.1 for the earlier versions.Monitor the activity of the privileged users by setting the AUDIT_SYS_OPERATIONS parameter to TRUE.


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

Oracle Database Auditing Documentation

Oracle 10g documentationOracle 11g documentationOracle 12c documentation


Note 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

REFERENCES

NOTE:271615.1 - Timestamp And Logoff_time Columns In Audit views Are In Different Time Zones in 10gNOTE:175259.1 - Using Autonomous Triggers To Audit Detailed Information.NOTE:309798.1 - How to Trace Specific Database Users to Collect Full DML Statements ExecutedNOTE:1372067.1 - Audit Action# 102 Is Not Written To Aud$ If session Exceeds A Profile LimitNOTE:308066.1 - AUDIT_SYS_OPERATIONS Set To FALSE Yet Audit Files Are GeneratedNOTE:174340.1 - Audit SYS User Operations (How to Audit SYSDBA)NOTE:343413.1 - Default Actions Audited in OS Audit Files Contain Messages for Completed Archive OperationsNOTE:363590.1 - How to Retrieve DML Statements Text and Values from Bind VariablesNOTE:39796.1 - Init.ora Parameter "AUDIT_FILE_DEST" Reference NoteNOTE:402528.1 - How to cleanup the log table FGA_LOG$ ?NOTE:21073.1 - OERR: ORA-9925 "Unable to create audit trailNOTE:221944.1 - How to Audit Potential Attempts to Break a Username/PasswordNOTE:239621.1 - How To Prevent The Audit Of 'ANALYZE INDEX'NOTE:222807.1 - How To Audit GRANT ANY PRIVILEGE Or GRANT ANY ROLENOTE:334486.1 - SYS.AUD$ Table Not Found Though Exists in SYS.OBJ$NOTE:6023472.8 - Bug 6023472 - Collection of changes to auditingNOTE:731908.1 - New Feature DBMS_AUDIT_MGMT To Manage And Purge Audit InformationNOTE:731782.1 - Format Of OS Audit Files Changes Starting with 10.2.0.4 and 11.1.0.7BUG:3684796 - ORA-904 WHEN EXPLAINING GROUPING SETS QUERY WITH FINE GRAINED AUDITINGNOTE:20985.1 - OERR: ORA-9822 Translation of audit file name failed.NOTE:30690.1 - Init.ora Parameter "AUDIT_TRAIL" Reference NoteNOTE:287436.1 - SCRIPT: Generate AUDIT and NOAUDIT Statements for Current Audit SettingsNOTE:293973.1 - Find List Of All Possible Keywords In Audit Log FilesBUG:2998476 - SQL_TEXT COLUMN IN DBA_FGA_AUDIT_TRAIL VIEW IS GARBLED AFTER APPLYNG BUG#2973008NOTE:130146.1 - Auditing DML (Insert, Update and Delete)NOTE:230845.1 - How to Import SYS.AUD$ Table from 8i to 9i Database When SYS User is not ExportedNOTE:427296.1 - Why Is Column TIMESTAMP# Having NULL Values In AUD$ And FGA_LOG$ Tables?NOTE:106823.1 - Unknown Users Comparing sys.aud$ and user_audit_sessionNOTE:282091.1 - How to find Whether an OBJECT-level Audited by ACCESS Statement Succeeded or FailedNOTE:1020945.6 - How to Setup AuditingNOTE:246665.1 - ORA-22921 When Fine Grained Auditing with Multibyte Character Set in 9.2.0.3NOTE:72203.1 - OERR: ORA-16006 audit_trail destination incompatible with database open modeNOTE:72291.1 - VMS: The AUDIT_TRAIL=OS Initialization Parameter on OpenVMS

NOTE:316915.1 - Unexpected Audit Records Are Generated Within APPS When CREATE SESSION is Audited ActionNOTE:1080112.1 - How To Shrink Table AUD$NOTE:469007.1 - SCRIPT: How To Apply the Same Fine Grained Audit Policy To All Tables In A Schema.NOTE:99137.1 - Setting up, Interpreting Auditing Using the Windows Event ViewerNOTE:414666.1 - Audit Action #283NOTE:209801.1 - How to Disable Audit Action 103 to Avoid Unnecessary Rows in Table SYS.AUD$


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

BUG:2916125 - AUDITED_CURSORID ONLY AVAILABLE FOR REGULAR AUDITINGNOTE:123128.1 - How To Identify an RDBMS session using AUDSIDNOTE:208855.1 - What is Audit Action 103 ?NOTE:1019377.6 - Script to move SYS.AUD$ table out of SYSTEM tablespaceNOTE:74725.1 - How often tables are accessed (AUDIT)NOTE:782078.1 - Proxy Users and Auditing Proxy UsersNOTE:266896.1 - 10g: Fine Grained AuditingNOTE:267389.1 - AUDIT CREATE PROCEDURE Does not Audit "Create OR Replace Procedure" StatementsNOTE:240766.1 - ORA-00904 When Using RAWTOLAB Function on SYS.AUD$ Columns OBJ$LABEL and SES$LABELNOTE:310876.1 - CREATE USER System Privilege Not Being AuditedNOTE:868955.1 - Get Proactive - Oracle Health Checks - Installation, troubleshooting, catalog and more.NOTE:158348.1 - How to Find Results Back in Data Dictionary When Using AUDIT SYSTEM GRANTNOTE:166301.1 - How to Reorganize SYS.AUD$ TableNOTE:1019326.102 - SES_ACTIONS in DBA_AUDIT_OBJECTNOTE:99786.1 - How to Audit User Connection, Disconnection Date and TimeNOTE:1171314.1 - Huge/Large/Excessive Number Of Audit Records Are Being Generated In The DatabaseNOTE:125378.1 - ORA-2096 setting TRANSACTION_AUDITING dynamicallyBUG:2973008 - FINE-GRAINED AUDITING FAILS WITH ORA-22921 USING MULTI-BYTE CHARACTER SETNOTE:199419.1 - How to Avoid Common Flaws and Errors Using Fine Grained AuditingNOTE:1392161.1 - Queries on XML Audit Trail Views Crash With: ORA 600 [KZAXGFL:IDX]NOTE:1393275.1 - Ora-600 [kzaxpopr14 -error in decoding xml text] When Querying V$Xml_audit_trailNOTE:1407434.1 - How To Audit Direct Path Load And Unload Activities?BUG:13524613 - INSERT ALL SLOW WHEN AUDIT_TRAIL SETNOTE:279169.1 - SCRIPT: How To Store the Checksum of PL/SQL CodeNOTE:1025314.6 - Descriptions of Action Code and Privileges Used in Fields in SYS.AUD$ TableNOTE:1025832.6 - How To Audit Data Changes In Tables Using TriggersNOTE:103964.1 - How to Audit Connect AS SYSDBA Using Oracle ServerNOTE:1049048.6 - Auditing with Oracle Parallel ServerNOTE:1063941.6 - LRM-00101 or ora-2065 ; cannot specify audit_file_dest on Windows platformNOTE:175292.1 - Overview Of The Auditing Possibilities In An Oracle DatabaseNOTE:19287.1 - OERR: ORA 2002 error while writing to audit trail

NOTE:310873.1 - Audit Record written When We Select From View even if The Audited Column Is Not SelectedNOTE:1375419.1 - Obsoleted "BY SESSION" Audit Option Leads to Massive Audit Output (Huge AUD$)NOTE:274697.1 - LOGOFF and LOGOFF BY CLEANUP Do Not Have Any LOGON Records in DBA_AUDIT_TRAIL and Vice-VersaNOTE:277219.1 - How to Retrieve the Whole Audited SQL Statement From DBA_FGA_AUDIT_TRAIL View ?NOTE:278184.1 - Installing Oracle Label Security Automatically Moves AUD$ Table out from SYS into SYSTEM schemaNOTE:73408.1 - How to Truncate, Delete, or Purge Rows from the Audit Trail Table AUD$NOTE:166650.1 - Working Effectively With Oracle Support - Best PracticesNOTE:166674.1 - Auditing Does Not Supply A Full Name Of TriggersNOTE:167293.1 - Some Examples About Auditing And Output Of AuditingNOTE:174556.1 - 9i/9.2: Fine Grained AuditingNOTE:1357829.1 - Declaring Auditing Categories With 'ON BEHALF OF' Clause Not Working With 'BY ACCESS' or 'BY SESSION'NOTE:41800.1 - Quick Reference to Auditing InformationNOTE:197598.1 - Audit Users with "DROP ANY TABLE" Privilege: Example Client Event TriggerNOTE:1068714.6 - How does the NOAUDIT option work (Disabling AUDIT commands)NOTE:107842.1 - Application Log is Full with Event ID 34 : Audit Trail: Connect InternalNOTE:198468.1 - SYS.AUD$ Filling up Fast When Auditing Failed Logon Attempts Because of DBSNMP.NOTE:249438.1 - 10G: New Value DB_EXTENDED for the AUDIT_TRAIL init.ora ParameterNOTE:1074690.1 - How To Monitor The Identity Of A Proxy Enterprise User In The Audit Trail?NOTE:1019552.6 - Script to Show Audit Options/Audit TrailBUG:3836829 - COLUMNS THAT ARE NOT SELECTED IN VIEW STILL AUDITED USING FGANOTE:199389.1 - How To Escalate a Service Request (SR) with Oracle Support ServicesBUG:8649263 -NOTE:553225.1 - How To Set the AUDIT_SYSLOG_LEVEL Parameter?


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

Master Note: Troubleshooting Database Configuration Assistant (DBCA) (Doc ID 1510457.1)

In this Document

PurposeTroubleshooting Steps DBCA log files Starting DBCA Instance creation Storage - F/S, Raw, ASM File system (F/S) Raw devices ASM Database creation Running EMCA Silent mode Using a Template RAC related issues Using DBCA after Database Creation Further DiagnosticsReferences

APPLIES TO:

Oracle Database Configuration Assistant - Version 10.2.0.1 and laterInformation in this document applies to any platform.

PURPOSE

This document is intended to provide a standard approach for resolving issues with the Database Creation Assistant (DBCA). The informationis primarily targeted to the creation of single instance databases but is also largely applicable to cluster databases. For RAC specifictroubleshooting, no actual information is provided here but a list of known issues is included.

TROUBLESHOOTING STEPS

Database Configuration Assistant (DBCA) is the preferred way to create a database because it is a more automated approach and yourdatabase is ready to use when DBCA completes. DBCA can be launched by the Oracle Universal Installer (OUI), depending upon the type ofinstall that you select. You can also launch DBCA as a standalone tool at any time after the Oracle Database software installation.

You can run DBCA in interactive mode or noninteractive/silent mode. Interactive mode provides a graphical interface and guided workflowfor creating and configuring a database. Noninteractive/silent mode enables you to script the database creation. You can run DBCA innoninteractive/silent mode by specifying command-line arguments, a response file, or both.DBCA is a java based graphical application like NetCA, ASMCA and is started with a shell script (.bat file on Windows) located in$ORACLE_HOME/bin.

Starting 12c, new databases created using the DBCA can optionally have a default password complexity check enabled. Passwordcomplexity checks increase the security of Oracle databases and the overall enterprise by reducing the potential for new databases to becreated without a strong password check enabled.

For an overview of DBCA, please refer to

Note 1488770.1 - Master Note: Overview of Database Configuration Assistant (DBCA)


1 of 6 3/4/2015 12:46 AM

Note 454631.1 - 11g DBCA New features / Enhancements

Issues can arise during different stages or situations as listed below, however it may not always be immediately clear what that stage orsituation is. This applies especially to the instance creation and the actual database creation.

Starting DBCAInstance creationGetting storageDatabase creationRunning EMCASilent modeUsing a Template

DBCA log files

The starting point for investigation of any DBCA issue is the log files which can be located in different locations depending on the version:Oracle 10.2: under %ORACLE_HOME%, e.g. D:\oracle\product\10.2.0\db_1\cfgtoollogs\dbca (for general log files, e.g. trace.log)) D:\oracle\product\10.2.0\db_1\cfgtoollogs\dbca\v1020 (for instance/database specific log files)

Oracle 11.2: under $ORACLE_BASE /u01/app/oracle/cfgtoollogs/dbca/v1120

NOTE:The DBCA trace.log file also lists errors that frequently get mistaken for actual issues, e.g.

...[Thread-99] [ 2012-11-26 16:09:04.459 EST ] [BasicStep.execute:202] Executing Step : CLONE_DB_CREATION[Thread-99] [ 2012-11-26 16:09:04.460 EST ] [StepErrorHandler.setFatalErrors:322] setting Fatal Error: ORA-01503[Thread-99] [ 2012-11-26 16:09:04.460 EST ] [StepErrorHandler.setFatalErrors:322] setting Fatal Error: ORA-01034[Thread-99] [ 2012-11-26 16:09:04.460 EST ] [StepErrorHandler.setFatalErrors:322] setting Fatal Error: ORA-01092[Thread-99] [ 2012-11-26 16:09:04.460 EST ] [StepErrorHandler.setFatalErrors:322] setting Fatal Error: ORA-03113[Thread-99] [ 2012-11-26 16:09:04.460 EST ] [StepErrorHandler.setFatalErrors:322] setting Fatal Error: ORA-03114[Thread-99] [ 2012-11-26 16:09:04.460 EST ] [StepErrorHandler.setIgnorableErrors:250] setting Ignorable Error: ORA-01109[Thread-99] [ 2012-11-26 16:09:04.460 EST ] [StepErrorHandler.setIgnorableErrors:250] setting Ignorable Error: ORA-12712[Thread-99] [ 2012-11-26 16:09:04.461 EST ] [StepErrorHandler.setIgnorableErrors:250] setting Ignorable Error: ORA-00942[Thread-99] [ 2012-11-26 16:09:04.461 EST ] [StepErrorHandler.setIgnorableErrors:250] setting Ignorable Error: ORA-04043...

Please note that these are not actual errors. This is just for marking the listed errors as Fatal or Ignorable for further processing.

Starting DBCA

Starting the DBCA and using the GUI can present some issues even before an instance and/or database are created.

If the DBCA GUI does not start, the issue is most likely caused by Java. In that case the process can be investigated by tracing java codeaccording to:

Note 428118.1 - How to enable Java code tracing for DBUA, DBCA and NETCA?Note 188134.1 - Tracing the Database Configuration Assistant (DBCA)

Running the GUI, there may be a permission issue with the creation of required files, e.g.

Note 1340990.1 - While Installing Oracle11.2.0.2: [Ins-20802] Oracle Database Configuration Assistant Failed (DBCA)


2 of 6 3/4/2015 12:46 AM

The DBCA GUI may also seem fully usuable until the end, but then the database creation process does not start.

Note 727290.1 - DBCA/DBUA APPEARS TO HANG AFTER CLICKING FINISH BUTTON

Please also verify the Oracle software installation requirements, according to the manuals and following documents:

Note 169706.1 - Oracle Database (RDBMS) on Unix AIX,HP-UX,Linux,Mac OS X,Solaris,Tru64 Unix Operating Systems Installation andConfiguration Requirements Quick Reference (8.0.5 to 11.2)Note 250262.1 - RDA 4 - Health Check / Validation Engine Guide

Instance creation

If the instance creation fails, this can point to an oversizing of memory usage that has been configured with ASMM or AMM.Please check:

the configured memory parametersthe alert logkernel configuration and ulimit settings on Linux/Unix (Please refer to the HCVE tool in Note 250262.1)whether other databases are already running

Specifically on Windows, there could be an issue with the Windows Oracle Service that gets created with the oradim command.Please check:

the oradim.log in %ORACLE_HOME%\databasethe windows event logs

Problems with instance creation (or access) often report an TNS related error, e.g. ORA-12560

Note 1396185.1 - DBCA Fails With ORA-12560 (OS 1376) On Windows AD ControllerNote 729774.1 - ORA-12560 running DBCA on Windows 2008 AD ControllerNote 747243.1 - ORA-12560 - Database Creation Assistant (DBCA) Fails With TNS ErrorNote 110758.1 - DIM-00019 ERROR WHILE CREATING A SERVICE USING ORADIMNote 1323422.1 - Creation Of 10.2.0.5 Database On Non-English Windows 7/2008 SP2 Fails With ORA-3113Note 404075.1 - Database Configuration Assistant (DBCA) reports ORA-12547 creating a new database on LinuxNote 333467.1 - Database Configuration Assistant (DBCA) Errors with TNS-04404Note 229623.1 - Database Configuration Assistant (DBCA) Fails to Start

Storage - F/S, Raw, ASM

Database creation can fail at an early stage because files cannot be created on the chosen storage location, e.g. File System, Raw or ASM.

File system (F/S)

Errors with respect to the File System could be caused by aspects like:mount optionsaccess privilegesspace limitations

An O/S error would be expected in the reported error stack. Please first investigate that then check out the possible causes as mentioned.

Note 1051352.1 - ORA-313, ORA-312, ORA-27041, OSD-4002 Reported in Alert Log When Creating a Database via DBCA

Raw devices

Raw devices for individual datafiles are only used for shared storage for RAC, as this note primarily focuses on single instance DBCA, hence


3 of 6 3/4/2015 12:46 AM

no further information is provided here.However, please note that with the introduction of the Grid Intrastructure in 11.2, raw devices are desupported.Please refer for instance to Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Linux Section 3.4 Desupport of Block and Raw Devices http://docs.oracle.com/cd/E11882_01/install.112/e22489/storage.htm#CWLIN312

Note 91790.1 - DBCA: Raw Device Support in Database Configuration AssistantNote 37914.1 - Raw Devices and Oracle - 20 Common Questions and AnswersNote 217319.1 - Raw Device Validation Check When Using DBCA to Create a RAC Database

ASM

With Oracle 11gR2, ASM has been included in the Grid Infrastructure (GI) which is installed in a separate Oracle Home. Before 11gR2, anASM instance was also running from a standard RDBMS Home and the ASM instance was created with the DBCA. As far as DBCA isconcerned, the utility only needs to be able to connect to the ASM instance. ASM issues as such are handled by the Oracle Storage/ASMsupport group and assistance should be requested in a separate service request if needed.For additional information and specific DBCA issues with ASM, please refer to:

Note 1187723.1 - Master Note for Automatic Storage Management (ASM)Note 436827.1 - ERRORS DBCA DISCOVERING AN EXISTENT ASM INSTANCE IN RAC AND NON RACNote 948456.1 - Pre 11.2 Database Issues in 11gR2 Grid Infrastructure EnvironmentNote 1177483.1 - DBCA Does Not Display ASM Disk Groups In 11.2Note 468941.1 - Could Not Access Asm In Dbca To Create New DatabaseNote 403644.1 - How to get the DBCA to see an ASM instance without the standard +ASM instance name?Note 744237.1 - DBCA in Silent mode with ASMNote 550509.1 - DBCA Could Not Startup the ASM Instance Configured on This NodeNote 393121.1 - DBCA is Not Discovering Raw Devices for ASM on a RAC/Cluster Environment (Unix).

Database creation

The process of database creation can best be seen looking at the creation scripts that can be saved from within DBCA. The scripts arelocated in the $ORACLE_BASE/admin/<SID>/scripts/ directory. The main script is <SID>.sh (<SID>.bat on Windows) which calls<SID>.sql.All other scripts really depend on the chosen database type (using a template) and selected database options/features. If a template wasused including datafiles, there will be steps for RMAN dbms_backup_restore functionality and creating a new controlfile. Without includeddatafiles, a regular 'create database' command is used.All scripts create their own log file in the previously specified locations.It is always advised to have DBCA generate the database creation scripts. In case of an error, the relevant script and accompanying log fileare the starting point for locating the root cause. The scripts can also be used to easily reproduce an issue when needed.As mentioned, it is not always clear at the beginning if an issue is encountered during the instance creation or after connecting to thecreated instance when creating the actual database. The alert log would be the first place to look.Errors running the actual sql scripts like catalog.sql and catproc.sql or scripts for additional products are rather unlikely. Most of theproblems could be expected when creating the datafiles in relation to storage.

Note 388488.1 - Database Configuration Assistant (DBCA) is Failing With ORA-01034

Running EMCA

EMCA is a separate utility that is invoked by DBCA to configure the Database Control (DBConsole).For the successful creation of the database, you may ignore EMCA related errors for the time being because the DBConsole can be createdafterwards.For initial information, pleased refer toNote 1099271.1 - Master Note for Enterprise Manager Configuration Assistant (EMCA) in Single Instance Database Environment


4 of 6 3/4/2015 12:46 AM

Some Oracle Net configuration issues could prevent EMCA connecting to the database.The log file $ORACLE_BASE/cfgtoollogs/dbca/v1120/emConfig.log may show the following error:

...Nov 26, 2012 4:16:29 PM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControlCONFIG: ORA-12641: Authentication service failed to initialize

oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-12641: Authentication service failed toinitialize...

For a solution. please refer to

Note 826382.1 - Database Control Homepage shows ORA-12641 : Authentication Service Failed To Initialise

If the solution in Note 826382.1 does not work, please try removing the next line temporarily from $ORACLE_HOME/network/admin/sqlnet.ora:

SQLNET.AUTHENTICATION_SERVICES = (none)

Silent mode

DBCA can be used in silent mode using a response file and/or command line parameters. Most issues are probably caused by incorrectparameter usage or an incorrectly modified response file. To get more information when addressing such an issue, you can first leave outthe '-silent' option.For full parameter usage, please refer to the information provided by the next command:

dbca [ -h | -help ]

Note 744237.1 - DBCA in Silent mode with ASMNote 1263965.1 - How To Change Database Parameters Using A DBCA Silent Installation?Note 1301254.1 - Registering Database With DBCA Silent Results in Error For User With Spaces in UsernameNote 1370820.1 - DBCA Creation Silent Mode Failed to Enable Automatic Memory ManagementNote 5875729.8 - Bug 5875729 - DBCA silent carries on and completes 'successfully' despite fatal errors

Using a Template

Templates are XML based files that define a database configuration (.dbt files) or may also use an actual seed database (.dbc files). Thetemplates are located under $ORACLE_HOME/assistants/dbca/templates. Templates can be used with silent installations or with the GUI.It is important to note that seed databases have a specified block size for the datafiles and are not necessarily of the same patch set level asa patched Oracle Home.

Note 148676.1 - DBCA TemplatesNote 578830.1 - Dbca Fails Creating A Database Using Template That Contains DataNote 387598.1 - DBCA Cannot Find Template Files ORA-19870 Note 444811.1 - ORA-09925 When Using DBCA Template Note 374568.1 - Trying to create a database (10.2.0.2.0 home) from a template (10.2.0.1.0 structure only) generate errors:ORA-1503:ORA-01130 : ORA-0110 Note 1506166.1 - DBCA Delete All Files Specified In Template If The Database Creation FailedNote 1508337.1 - DBCA Silent Mode Is Not Setting DB_UNIQUE_NAME Even Though It Is Specified In DBCA Template File.Note 456631.1 - Altering an Existing DBCA Template using the Same Template NameNote 404292.1 - Unable To Supply Variable To Dbca Template In Silent Mode


5 of 6 3/4/2015 12:46 AM

RAC related issues

DBCA can be used to create cluster databases, however, this article primarily discusses single instance databases. Further information onRAC databases here is limited to only a list of related information and known issues. For DBCA issues specific to RAC, a separate servicerequest can be logged with the Oracle RAC competency.

Note 856783.1 - How to create a RAC database using DBCA generated scripts from templatesNote 1446322.1 - Use Database Configuration Assistant (DBCA) To Create or Drop a RAC DatabaseNote 1099475.1 - DBCA Add Instance Does Not Update tnsnames.ora on New NodesNote 460695.1 - DBCA Fails with "Exception In Thread "Main" Java.Lang.Noclassdeffounderror: oracle/sysman/oip/oipc/oipch/OipchKernelProperty"Note 220970.1 - RAC: Frequently Asked QuestionsNote 1073926.1 - DBCA does not Show "Oracle Real Application Clusters database" (RAC) OptionNote 1446322.1 - Use Database Configuration Assistant (DBCA) To Create or Drop a RAC DatabaseNote 804975.1 - DBCA Creates a RAC Database But at the End Shows PRPP-1001 and CRS-0215Note 856783.1 - How to create a RAC database using DBCA generated scripts from templatesNote 473287.1 - DBCA Requires That All RAC Nodes Be Accessible When Adding A New InstanceNote 359356.1 - DBCA Not Listing Existing Single Instance DB When Trying To Convert it to RACNote 754712.1 - How a RAC Listener is Selected in DBCANote 436827.1 - ERRORS DBCA DISCOVERING AN EXISTENT ASM INSTANCE IN RAC AND NON RACNote 733592.1 - RAC Database not showing In DBCA 'List of cluster databases'Note 394519.1 - DBCA Fails With PRKC-1055 While Adding a New Instance to an Existing RAC DatabaseNote 373022.1 - DBCA does not detect RAC installationNote 1268904.1 - Pre-11.2: How to Get Around the Issue of DBCA Choosing Incorrect Listener to Find Out ASM Instance Information inRAC EnvironmentNote 550196.1 - Empty Pop-up From DBCA When Adding an Instance or Creating a RAC DatabaseNote 217319.1 - Raw Device Validation Check When Using DBCA to Create a RAC DatabaseNote 393121.1 - DBCA is Not Discovering Raw Devices for ASM on a RAC/Cluster Environment (Unix).

Using DBCA after Database Creation

After the database is created, DBCA can be used for some configuration changes or to remove the database. For this purpose, DBCA usesagain the oratab file (in /etc or /var/opt/oracle) that is initially also created by DBCA upon database creation.In case the database is not created with DBCA (or the scripts generated by DBCA), the oratab file may not contain all required information.For such an issue, please refer to

Note 1609516.1 - DBCA Does Not Recognize Database If It Is Created With RMAN

Further Diagnostics

If you were not able to resolve the issue with the details provided in this document, please raise a Service Request for further assistancefrom Oracle Support.

REFERENCES

NOTE:454631.1 - 11g DBCA New features / EnhancementsNOTE:1488770.1 - Master Note: Overview of Database Configuration Assistant (DBCA)


6 of 6 3/4/2015 12:46 AM

Master Note For Oracle Database Downgrade (Doc ID 1151427.1)

In this Document

PurposeScopeDetails MY ORACLE SUPPORT COMMUNITIES General Information How to Known Issues Using My Oracle Support Effectively Generic LinksReferences

APPLIES TO:

Oracle Database - Enterprise Edition - Version 8.1.7.1 and laterOracle Database - Standard Edition - Version 8.1.7.1 and laterInformation in this document applies to any platform.

PURPOSE

This Master Note is intended to provide an index and references to the most frequently used My Oracle Support Notes with respect to OracleDatabase Downgrade.This Master Note is subdivided into categories to allow for easy access and reference to notes that are applicable toyour area of interest, within DOWNGRADE.This includes the following categories:

General InformationHow toDiagnostic ToolsKnown IssuesUsing My Oracle Support EffectivelyGeneric Link

SCOPE

This note guides you through the process of downgrading a database back to the previous Oracle Database release.

This note applies to the following versions of these products:

Oracle Server - Enterprise Edition - Version: 8.1.7.1 to 8.1.7.xOracle Server - Enterprise Edition - Version: 9.0.1.1 to 9.0.1.xOracle Server - Enterprise Edition - Version: 9.2.0.1 to 9.2.0.xOracle 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.xOracle Server - Enterprise Edition - Version: 12.1.0.1 to 12.1.0.x

DETAILS

MY ORACLE SUPPORT COMMUNITIES

In case this is a functional question, a rich community of Oracle experts and users around the world may also have an answer for you.In that case, you may want to log a thread on the My Oracle Support Database Install/Upgrade Community.

General Information


1 of 3 3/4/2015 12:47 AM

The documentation listed below help you in understanding the compatibility, concepts and usage of Oracle DatabaseDowngrade:

Note 551141.1 Database Server Upgrade/Downgrade Compatibility MatrixNote.444709.1 COMPATIBLE Initialization Parameter and Upgrade/Downgrade in 11g

Downgrade Guides:Oracle Database Upgrade Guide 12c Release 1 (12.1)Part Number E17642-13Oracle Database Upgrade Guide 11g Release 2 (11.2)Part Number E10819-02

Oracle Database Upgrade Guide 11g Release 1 (11.1)Part Number B28300-03



Oracle9i Database Migration Release 2 (9.2)Part Number A96530-02

How to

The documentation listed below help you in understanding the concepts and usage of Oracle Database Downgrade:

Note 334598.1 How to rollback a patchsetNote 208237.1 How to Downgrade a Database Using Export/Import?Note 1516622.1 How To Downgrade Oracle Database 12c Release 1 (12.1) To Previous VersionsNote 883335.1 How To Downgrade From Database 11.2 To Previous Release (includes 11.2.0.3-11.2.0.1)Note 443890.1 Complete Checklist For Downgrading The Database From 11.1 To Lower ReleasesNote 398372.1 How to Downgrade from Oracle RDBMS 10gR2?Note 345123.1 How to Downgrade from Oracle RDBMS 9.2.0.8/9.2.0.7 to Lower Patchset Releases?Note 391879.1 How to Rollback Oracle Database Patchset 9.2.0.8.0 (applicable to both Single instance and RAC) ?Note 208201.1 Downgrading from 9.2.0.1 to 9.0.1/8.1.7

Note 876353.1 How To Restore The Oracle Enterprise Manager Data To Downgrade The Single Instance Database To Previous/SourceRelease ?Note 783643.1 Downgrading Database Without Executing catdwgrd.sql (11.1.0.x to 10.2.0.x/10.2.0.x to 10.2.0.x)Note 871665.1 How To Restore A Database Back To The Source Release After Upgrading It To Oracle 11gR2 Using DBUANote 883855.1 Overview of the New Feature 'emdwgrd' Utility in DBControl

Known Issues

The articles listed below will help you solving the Downgrade issues:Note 1520209.1 QT_*BUFFER Views Invalid after downgrade from Oracle Database 12.1 (12c)Note 1107285.1 catdwgrd.sql fails with xds_acl ORA-00942 table or view does not existNote 435536.1 "ORA-01722 invalid number" During Upgrade/DowngradeNote 1446710.1 Catrelod.sql failed with ORA-00600: internal error code, arguments: [qcisSetPlsqlCtx:tzi init] And Alert log showing :Failed to find timezone data file # 14 (DST_4)Note 1367333.1 Downgrade From 11.2.0.3 To 11.2.0.2 Fails At Catrelod.Sql with error: ORA-20000: Upgrade from version 11.2.0.2.0cannot be downgraded to version 11.2.0.1Note 1292035.1 Ora-20000 : Direct Downgrade Of EM Database Control Not Supported Despite Sysman User Is DroppedNote 391656.1 Downgrade Not Supported With ORA-20000 And ORA-06512 At "SYS.VERSION_SCRIPT"Note 388604.1 ORA-00201 while downgrading from 10gR2 to 10gR1 or 9iR2


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

Note 948710.1 Troubleshooting ORA-201 ORA-202Note 433354.1 After Downgrading From 10.2 To 9.2 Startup Migrate Returns ORA-402 ORA-405 ErrorsNote 338199.1 Downgrading A 10.1.0 DatabaseNote 1016089.102 ORA-00402, ORA-00405, when Downgrading from 8.1.5 to 8.0.5Note 9967451.8 Bug 9967451 - Downgrade catrelod fails (ORA-600 [qcisSetPlsqlCtx:tzi init])


Note 868955.1 My Oracle Support Health Checks CatalogNote 166650.1 Working Effectively With Global Customer SupportNote 199389.1 Escalating Service Requests with Oracle Support ServicesNote 732897.1 How to Log Good Service Requests for Database Upgrade/Migration Issues

Generic Links

Note 854428.1 Patch Set Updates for Oracle ProductsNote 1061295.1 Patch Set Updates - One-off Patch Conflict ResolutionNote 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 PlatformsNote 161818.1 Oracle Database (RDBMS) Releases Support Status SummaryInformation on Critical Patch Updates (CPU's)

REFERENCES

NOTE:1351112.2 - Information Center: Upgrading and Migration Oracle DatabaseNOTE:1520299.1 - Master Note For Oracle Database 12c Release 1 (12.1) Database/Client Installation/Upgrade/Migration StandaloneEnvironment (Non-RAC)NOTE:1152016.1 - Master Note For Oracle Database Upgrades and Migrations


3 of 3 3/4/2015 12:47 AM

Documents

Master Note for Oracle Database Downgrade (Doc ID 1151427.1)