Oracle Developer Tools for Visual Studio Release Notes

---

The latest downloads, information, and community forums can be found here: http://www.oracle.com/technology/tech/dotnet/tools/index.html.

Release 11.2.0.3.20

September 2012

Copyright(c) 2005, 2012, Oracle. All rights reserved.

This file contains important information about Oracle Developer Tools for Visual Studio.  The following topics are covered:

• System Requirements
• Support and Product Feedback
• General Information and Dependencies
• Features not Covered by Documentation
• Known Issues

System Requirements

• Visual Studio 2008 SP1, Visual Studio 2010 or Visual Studio 2012 (any version other than the Express Editions, which do not support add-ins). Visual Studio.NET 2003 and Visual Studio 2005 are not supported in this release.
• Access to an Oracle11g/10g/9.2.x database (Note: Some features may require later versions of the Oracle Database)
• Download all database editions here: http://www.oracle.com/technology/software/products/database/index.html
• Oracle Database Express Edition is here: http://www.oracle.com/technetwork/database/express-edition/downloads/index.html
• .NET Framework 3.5 (VS 2008), .NET Framework 4.0 (VS 2010) or .NET Framework 4.5 (VS 2012)

Support and Product Feedback

Oracle is very interested to hear your comments related to this release, including feature requests and bug reports. Please visit the Oracle Technology Network (OTN) ODT community forum to tell us what you think! (Registration with OTN required)

The ODT Discussion Forum Frequently Asked Question List is a good place to find answers to common questions and problems with ODT.

General Information and Dependencies

Microsoft Visual C++ Redistributable Packages

The Microsoft Visual C++ 2005 SP1 Redistributable Package is automatically installed with the Oracle Database 11g Release 2 (11.2) software. Please do not remove this package from the Add or Remove Programs interface in the Control Panel or ODT will cease to work properly.

ODT should only be installed in one Oracle Home

ODT should only be installed in one Oracle home. If ODT is installed in multiple homes, and then one of them is subsequently deinstalled, any remaining installation of ODT will not work properly.

Uninstall previous version of ODT

Before installing this version of ODT, you should uninstall older versions of ODT.

Do not install Oracle Developer Tools into an Oracle8, Oracle9, or Oracle 10 Oracle Home

Installing the Oracle Developer Tools into an Oracle8, Oracle9, Oracle 10.1 or Oracle 10.2 Oracle home is not supported. By default, the Oracle Installer will create a new Oracle 11.2 Oracle home.

Integrated online help

If the ODT Help does not show up as part of Visual Studio Help in Visual Studio 2008, please follow the following steps:

1. Start Visual Studio and select ‘Search’ option from the Help menu.
2. Search for VSCC (Visual Studio Combined Help Collection).
3. Click on Visual Studio Combined Help Collection Manager from the Results window.

4. Scroll down to the bottom of the page and check off the ODT Help box if it is not checked or uncheck it if it is checked.

5. Click Update VSCC button. Close and restart Visual Studio.
6. If you unchecked the ODT Help in step 4, repeat steps 1 to 5 to check off ODT Help on the VSCC page.

Oracle connection errors after installing Oracle Developer Tools in new Oracle home

If you start receive Oracle connection errors immediately after installing Oracle Developer Tools, check to see if you created a new Oracle home during the install. If you did, you will need to copy over the TNSNAMES.ORA file from your old Oracle home to the new one.

Local Database option may not be visible from connection dialog drop down list
In order for a locally installed database to show up as a "Local Database" in the connection dialog box, Oracle Developer Tools must be installed in the same Oracle Home as the database. 

Oracle Explorer is no longer available in Visual Studio 2008 or later

For Visual Studio 2008 and Visual Studio 2010, Oracle Explorer has been removed and has been replaced by Visual Studio Server Explorer. Please refer to the online documentation for more information about Server Explorer.

Online Help

Only U.S English version of the help is shipped with this product.

Features not Covered by Documentation 

New Features for Oracle Developer Tools for Visual Studio Release 11.2.0.3.20

Oracle Developer Tools for Visual Studio release 11.2.0.3.20 includes the following:

• Support for Microsoft Visual Studio 2012.

Oracle Developer Tools for Visual Studio now supports Visual Studio 2012.

Entity Framework Designer and Wizards

• Entity Data Model (EDM) Wizard and Update Model From Database Wizard will only show one of the overloaded package procedures.
• Stored procedures with a "." in its name will not be displayed in the Entity Data Model (EDM) Wizard and Update Model From Database Wizard.
• If a stored procedure or function is mapped to a "collection of none" when imported into the model, then the .NET stub method, which returns an int, will always return 0.
• To work around the limitation that Oracle Stored Functions which are imported as Entity Functions cannot support returning a collection of Complex Types, a collection of entities can be returned instead. Creating a wrapper Oracle Stored Procedure can also be used as a workaround.
• Those developers who are having difficulties with the app.config or web.config implicit REF CURSOR metadata format used when importing Entity Functions may find that it is much simpler to configure this data if they are returning a collection of entities rather than complex types. In the case where a collection of entities is to be returned, the column type info need not be provided in the metadata.

New Query Window Features – Scrollable Resultset with Auto-Fetching; Parameterized Anonymous PL/SQL Blocks

• The resultset window in Query Window now automatically fetches more rows as the user scrolls. The maximum rows fetched option for the Query Window has been removed from the Oracle Developer Tools Options page. Note: The behavior of Oracle Data Window for Server Explorer Tables and Views has not changed and there remains a configurable maximum rows fetched option in the options page for the Data Window.
• Anonymous PL/SQL blocks that contain parameters are now supported. Upon execution, you will be prompted to provide values for the parameters.

PL/SQL Debugger troubleshooting

When debugging PL/SQL for the first time, please check the documentation to make sure all configuration steps have been performed. In particular please follow the steps listed in the “Debugging Setup Checklist” in the “PL/SQL Debugging Setup” section of the online help.

There are several scenarios where the database is not able to connect to the PL/SQL debugger:

• The connected user does not have the appropriate debug privilege to connect to the debugger. In this scenario, you will get the following message from ODT:
• "An error occurred while executing the procedure/function:

                     ORA-01031: insufficient privileges
                     ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
                     ORA-06512: at line 1"

                     To solve the problem, do the following:

             1. Grant the "debug connect privilege" (for 10g databases) to the connected user.
             2. Grant the "debug" and "execute" privilege on the PL/SQL program to the connected user, or
             3. Grant the "debug any procedure" privilege to the connected user.

• There are no available ports for PL/SQL Debugging.

          In this scenario, you will get the following message from ODT: "Could not begin PL/SQL debugging.  There are no available ports".
          To solve the problem, you have to modify the PL/SQL Debugging Options page to add the ports for debugging.

Please note: a port number randomly selected from the range specified in the ODT Debugging options page is reserved at the moment that the Oracle Application Debugging menu option is checked off. The specific port number reserved by the debugger is displayed to the user in the Output window.

• The debugging port is not open for external access.  This usually happens if the database connection is remote.

          In this scenario, you will get the following message from ODT:
            "An error occurred while executing the procedure/function:
             ORA-30683: failure establishing connection to debugger
             ORA-12535: TNS:operation timed out
             ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
             ORA-06512: at line 1"

To solve the problem, make sure all the ports set in the PL/SQL Debugging Options page can be opened for external access.  You can test by attempting to "ping" your development machine while logged into the database machine.

If you are still having problems, see the PL/SQL Debugger Known Issues in the section below.

Oracle Query Window

• By default all SQL is committed immediately. You can set this auto commit mode to OFF using the toolbar at the top of the query window or from the context menu of the editor in the query window (launched by right clicking on the editor).
• When the auto commit mode is ON,  "Commit" and "Rollback" commands are accepted but have no effect and every line in a SQL script will be committed immediately.
• Before executing existing SQL Scripts that contain "commit" and rollback" statements, it is strongly recommended to set the auto commit mode to OFF in the query window.
• The “@” directive can no longer be used to execute scripts in the query window. Please use the "Run SQL*Plus script" menu  item in the "Tools" menu of Visual Studio.

User Defined Types

• The parameters for user defined type methods with data type as user defined (object or collection) type cannot be expanded.
• Parameters to procedures/functions and package procedure/functions, table/view columns that are of user defined type will be expanded in the same way as an user defined type.
• A user defined type element of a collection type will be expanded in the same way as an user defined type.

Filters Settings

• In Server Explorer, the "Filters" settings for an Oracle Developer Tools connection, revert to default values if "Data Source Name" or "User Name" or "Role" properties are modified.

Known Issues

External Schema Objects not visible in Visual Studio Lightswitch

Visual Studio Lightswitch developers who connect to Oracle with a user account that has been granted permissions on other schemas will find that they cannot see those external schemas from the Lightswitch tool, even if they modify the "Filters" tab on the Server Explorer connection node.  For example, user HR is granted permissions on SCOTT.EMP. When the developer connects as HR in Lightswitch and modifies “Filters” tab in the Visual Studio Add Connection Dialog to include “SCOTT” in the displayed schemas, SCOTT.EMP will still not be shown in the displayed list of tables in Lightswitch.

Visual Studio 2010 Entity Designer

• Due to a Microsoft limitation, the Entity Designer will not work correctly if the LIB environment variable has invalid search paths.
• When “Generate Database From Model” using Oracle Developer Tools Entity Framework workflows and template, there is a current limitation of 30 characters for entity names and entity set names. Since certain generated names, such as foreign key names, also have some characters added to the beginning of the name, like "FK_", the limitation may actually be 27 characters.

Visual Studio 2012 Entity Designer

• Entity Data Model Wizard will not include any selected Oracle PL/SQL package procedures/functions into the model if the selection includes one or more overloaded package methods, even when Entity Data Model Wizard's "Import selected stored procedures and functions into the entity model" checkbox is checked. As a workaround, this checkbox can be unchecked so that the Entity Data Model Wizard can include the selected stored procedures/functions in the model. Then, the Add Function Import Dialog can be used to import each of the stored procedures/functions.
• Oracle Stored Functions that return any type other than a REF CURSOR, can be included in the model using Entity Data Model Wizard, but cannot be imported into the model using Entity Data Model Wizard's "Import selected stored procedures and functions into the entity model" checkbox or Add Function Import Dialog.
• Using Add Function Import Dialog, Oracle Stored Functions that return a REF CURSOR type can be imported as a procedure into the model.
• If you generate a model from database and then you generate SQL DDL from the model using "Generate Database from Model" feature, in the generated SQL some of the Oracle datatypes may not match the original Oracle datatypes from the EDM Types.

FLOAT

DATE

INTERVAL YEAR TO MONTH

INTERVAL DAY TO SECOND

TIMESTAMP WITH TIMEZONE

TIMESTAMP WITH LOCAL TIMEZONE

For example, when generating an entity model from database, Interval Year to Month is mapped to EDM Type Decimal, but when you generate the SQL from model using "Generate Database from Model" feature, the generated SQL script will create a NUMBER column instead of an Interval Year to Month column. Also, generating DDL for an entity with a float EDM property may fail, if the entity type was originally created from a FLOAT column of a table.

Visual Studio Crashes in Module 'oran11.dll' when connecting with Server Explorer or gives “Package did not load correctly”

Due to locking of OCI.DLL during installation of ODAC into a pre-existing Oracle Home, the old version of the OCI.DLL can remain and will be out of synch with the other DLLs. This can lead to a crash of Visual Studio when connecting to Oracle from Server Explorer or from a wizard or it could result in a message during launch stating “The Oracle Developer Tools for Visual Studio .NET package did not load correctly". The easiest solution is to simply reinstall into a new Oracle Home (directory). If you must use the same Oracle Home name and directory, you will still need to delete the now corrupted Oracle home and then reinstall, using the following steps:

1) Use the installer to uninstall the entire oracle home that is crashing

2) Look at the home in windows explorer. OCI.dll should still be there

3) Rename oci.dll to oci.delete

4) Reboot machine

5) Go back to windows explorer and delete all remaining files in the oracle home, including oci.delete

6) Install ODAC

Visual Studio throws “Type Initializer for Oracle.DataAccess.Client.OracleClientFactory” Exception

Both the Visual Studio Tools and an Entity Framework application require that the entry in your machine.config for the Provider Factory be set to the correct version of ODP.NET or that the policy DLL for ODP.NET 11.2.0.3.0 or later be installed. If, after you installed this release, you installed an older version of ODP.NET, either from an older ODAC or as part of an older Oracle Database install, this machine.config setting may now be set to the older version of ODP.NET, and the Policy DLL may have been removed, resulting in this error.

The easiest solution is to simply reinstall this version of ODAC.

Server Explorer Synonym Node Paging

Synonym Node paging and the Previous, Next, First, Last menu options used in Synonyms collection node are not available in this release. Any Navigation Page Size set in the Options page has no effect. If you expand the Synonyms collection node, all the synonyms as per your filter selections will be displayed. This may take an excessive amount of time to populate and so using filters is advised.

Data Source Configuration Wizard error: "Failed to find or load the registered .NET Framework Data Provider"
The Data Source Configuration Wizard can fail with the error "Failed to find or load the registered .NET framework data provider" if some other data provider has not been cleanly uninstalled and still has an entry in the machine.config file. Specifically, if the entry for Oracle Data Provider for .NET in the machine.config.xml file in the DbProviderFactories section comes after an already uninstalled data provider, this error will occur. The fix is to edit machine.config and move the Oracle Data Provider for .NET to the first item in the DbProviderFactories section.

Visual Studio 2008 known issues

• When closing Visual Studio 2008, the Visual Studio devenv process could enter an infinite loop that will use all the CPU time. To terminate the devenv process, use the Task Manager. This problem is planned to be fixed by Microsoft in a future Visual Studio 2008 release
• Visual Studio 2008 may crash on some machines, after displaying the text for a procedure/function/package/packagebody/trigger. To fix this issue, install Visual Studio 2008 SP1.

PL/SQL Debugger known issues

• ORA-30689: "improper value for ORA_DEBUG_JDWP" when using Application Debugging mode or using the ORA_DEBUG_JDWP environment variable:
• If you set ORA_DEBUG_JDWP environment variable, make sure that it is formatted correctly (no spaces, correct use of quotations)
• If it is correct, you are probably encountering a database bug:
• bug #5415410 - Can occur on some machines and not others (randomly). Fixed in database version 9.2.0.8 (Windows), 10.2.0.4 (all platforms) or 11.1(all platforms).
• bug #6818814 - Always occurs if client CPU is a different "endianness" from server CPU. This will be fixed in 10.2.0.5 (all platforms) and 11.2 (all platforms).
• Workaround is to use External Application Debugging along with the DBMS_DEBUG_JDWP PL/SQL package instead of Application Debugging or the ORA_DEBUG_JDWP environment variable. For example, you could execute this PL/SQL block after connecting but before you call your stored procedures:
  const string anonymous_block = "begin " +
                                    "DBMS_DEBUG_JDWP.CONNECT_TCP('xxx.xx.xxx.xx', '9999');" +
                                    "end;";
  
  Alternatively you could add a call to DBMS_DEBUG_JDWP.CONNECT_TCP in your stored procedure or in a login trigger.
• Then, in another instance of Visual Studio, select External Database Debugging from the menu and give it the port number you gave above (in this case 9999). Now, when you execute the stored procedure from one instance of Visual Studio, a breakpoint you have set in the other instance of Visual Studio will be fired. 
• For application and external application debugging, the Debug Location Toolbar does not show the Oracle debugger process if the debugging tier is in the database tier.
• The OracleDebugger.exe process is not always able to terminate successfully and multiple copies may accumulate which may need to be killed manually to free up resources. 
• You cannot debug a trigger correctly when :
    1.  The trigger contains blank lines or lines with only a comment
    2.  When the database has been restarted after the trigger is created. 
  To workaround the problem, the trigger cannot contain blank lines or any line with only comments on it.
• When debugging a PL/SQL program that invokes a .NET Stored procedure, you might encounter ORA-03113: end of communication channel.   When this happens, the debug connection is lost and debugging will not be possible to proceed normally. You will need to stop and restart the PL/SQL debugger.
• For types that the debugger is not able to evaluate (eg.  object types that do not compile with debug information), or are not supported, the type will be shown as an "opaque" type in the Watch, Quick Watch or Local window.
• Debugging a PL/SQL program that contains VARRAY or NESTED TABLE types as local variables or parameters is supported only with database versions 9.2.0.7 or higher.
• Debugging anonymous PL/SQL blocks is supported only with database versions 10.1 or higher. 
• Oracle Application Debugging may not stop at the breakpoints in your PL/SQL program, the first time you debug an application with “Enable Visual Studio Hosting Process” selected in your project properties. To workaround this issue:
• Close the solution with your project.
• Make sure Oracle Application Debugging is selected in Visual Studio Tools menu.
• Open your solution, set breakpoints in your PL/SQL program and start debugging

Server Explorer Node Renaming does not work with Visual Studio 2008

Oracle schema nodes cannot be renamed in Server Explorer with Visual Studio 2008.

PL/SQL types as parameter types for stored procedure/function/package method

Some of the PL/SQL data types (such as NATURAL or INTEGER) are aliases to database native types (for example, NUMBER). When these PL/SQL types (NATURAL, INTEGER) are used as parameter types in stored procedure or function, the PL/SQL data type displayed in the properties window for these parameters will reflect the database native type.

PL/SQL autocompletion with synonyms.

In a PL/SQL editor window, synonyms nested beyond 2 levels will not expand for autocompletion.

Connecting with SYSOPER role

Connecting with SYSOPER role is not supported.

Case sensitivity and special characters in name

To preserve the case in a name for a schema object, the name needs to enclosed in double quotes. Otherwise, when the focus is moved out of the text box where the schema object name is entered the schema object name will be automatically uppercased.

Retrieving table or view data

When retrieving data from a table or view, editing of data for the following Oracle types is not supported:

• CLOB, BLOB, BFILE, Object Type, Nested Table, VARRAY

Table/View Designer

• Creating a non-schema based XMLType table using Table Designer is not supported.
• Committed storage parameter values appear as empty when information is not available from the database.
• Creating or altering a table with one or more nested table type columns is not supported.
• Altering a table with an object type column, where the object type has one or more nested table type attributes in the type hierarchy is not supported.

Running a stored procedure or function

• Running a stored procedure or function that returns a null value for an output  parameter of SYS_REFCURSOR datatype  is not supported.
• Running a stored procedure or function with SYS_REFCURSOR as IN or IN-OUT parameter is not supported.
• Running a stored procedure or function with Oracle User Defined (Object or Collection) type as IN or IN-OUT or OUT or RETURN VALUE parameter is not supported.
• When running a stored procedure or function, for input parameters, a <DEFAULT> value is listed in the combobox even though the procedure/function may not have a default value defined for that parameter. Selecting <DEFAULT> as the parameter value in this scenario is not supported.

OracleDataAdapter Wizard

• When the OracleDataAdapter wizard for an OracleDataAdapter component is launched more than once, the parameter information may not be populated correctly. To work around this issue, reselect the stored procedure or select statement in the wizard.
• In the OracleDataAdapter wizard, the parameter information displayed for a stored procedure is not always in sync with the stored procedure selected. To workaround this issue, select the stored procedure a few times.
• In the OracleDataAdapter wizard, previewing results for stored procedures or SQL statements with IN or IN-OUT parameters is not supported.
• In the OracleDataAdapter wizard, to auto-generate insert/update/delete statements, the SQL statement should include the primary key or a rowid in the selection list..

Oracle Project

• The available methods in the Deploy Mapping property page are determined by the current configuration, not the configuration that is selected in the Property Pages Dialog.  Use of constants to specify which methods to include in the code should be avoided, if possible.
• The Deploy Mapping property page does not support methods with parameters of type System.Byte[].
• Automation is not supported.
• There is no Oracle-specific F1 or dynamic help for the Oracle Projects in Solution Explorer.
• If changes are applied in the Deploy Options, or Deploy Mapping property pages, and the project file is in source control, then the project must be checked out first. If the checkout operation is cancelled when prompted to checkout the project file, then the property page changes will be rolled back because changes cannot be made if the project file is not checked out. However, there will not be any message box indicating what happened.
• When the Oracle Deployment Wizard for .NET completes, and the project is in source control, then there may be a message indicating the project is being edited during a build. This warning is expected, and the edit should be allowed. Selections in the wizard need to be saved to the project file.The same problem also happens when building an Oracle Project for VB.NET after renaming the root namespace since the root namespace used for the build needs to be saved to the project file.
• Enterprise Templates are not supported with Oracle Project.

Oracle .NET Deployment Wizard

• Resizing the data grid in the Parameter Type Mapping dialog may not work as expected.
• When an assembly built in debug configuration is deployed, the associated .pdb file is not copied over to the database.
• When deploying an assembly from a machine with non-English locale, the user may sometimes be prompted to enter the location of the mscorlib.resources dll. The user can either specify the new location or click Cancel and the assembly deployment will continue without any errors.
• An error may occur when copying assemblies during a deployment because Oracle Database Extensions for .NET may not unload the assemblies on the Oracle Database from a previous deployment after a .NET Stored Procedure has been executed.  If this happens, the <OracleHome>ClrAgent service needs to be stopped, the extproc.exe process killed, and the <OracleHome>ClrAgent re-started.  This affects the primary assembly being deployed, as well as the referenced assemblies.  To prevent this issue from happening, the "RecreateAppDomain" parameter may be set, please see the documentation for Oracle Database Extensions for .NET.
• Parameters of .NET stored procedures cannot be names of PL/SQL types.

Oracle Project in Visual Studio 2008

• In the New Project dialog, Oracle Project can be located directly under the Database category under Visual C# or Visual Basic categories. 
• F1 help is not supported in deploy options and deploy mapping property pages.  Help can be located in the Oracle Developer Tools for Visual Studio .NET online help.
• If the property designer is open, then any changes made in code to .NET stored procedures, or any changes in the Oracle Deployment Wizard for .NET, will not be reflected in the property designer. The workaround is to close the property designer, and reopen it.
• Creating a new project configuration from an existing project configuration is not supported.

Oracle Query Window

• SQL statements which are blocked due to row locking cannot be canceled.
• Variable binding is not supported.
• It is not possible to use dbms_output.put_line more than 1024 times in a PL/SQL block.

Oracle Database Script Project

• Oracle Database Project is not currently supported with Visual Studio 2008 Standard Edition.
• While Oracle Database Project does not restrict project items from containing certain characters in the name, such as "$", file names containing those characters may not be supported by certain source control providers.
• Before upgrading a project that is under source control from Visual Studio .NET 2003 to Visual Studio 2008, you will need to check out the project file explicitly from source control.
• Cut/Copy/Paste, and drag and drop from an Oracle Database Project to a C++ project is not supported.
• Drag and drop of package methods from Server Explorer to an Oracle Database Project is not supported. To generate the create script for package methods you will need to drag and drop either the package or the package body from Server Explorer to an Oracle Database Project.

Generating Custom Classes for Oracle User Defined Types

• The custom class code generated for Collection types where the element of the collection type is mapped to an array of any type, will not compile.
• In Visual Studio 2008, when generating custom class to a Visual C++ Project, the precompiled header file is not included in the generated .cpp file. You will need to add the precompiled header file in the .cpp file, before compiling the generated code.
• The custom class code generator does not support "Web Site" Project type (File->New->Web Site). Please use ASP.NET Web Application project type instead. 

Visual Studio 2008 Designers and Wizards

• Drag/Drop to Query Designer from Server Explorer.
• From a ODT connection in Server Explorer, if you drag/drop database objects that have a ‘_’(underscore) as a leading character to the Query Designer, the database object name may not be enclosed in ‘’ (single quotes) in the SQL generated in the SQL pane of the Query Designer.

• ASP.NET Designer
• Drag and drop of database schema object(s) under Oracle Developer Tools for Visual Studio .NET data connection in Server Explorer to ASP.NET designer is not supported.
• Parameters of a stored procedure, once added in SQLDataSource, cannot be refreshed using the Refresh Parameters button.
• Configuring a SqlDataSource on a relational table with user defined type column and executing this ASP.NET application is not supported.
• In an ASP.NET Web Site project, to generate a typed dataset from an OracleDataAdapter component you will need to do the following steps:

• Drag and drop OracleDataAdapter component from the Toolbox to the Component Designer of the project and save the project.
• Generate the typed dataset from the context menu of the OracleDataAdapter component in the Component Designer.

Importing Table Data from Microsoft SQL Server or Microsoft Access Database

When importing tables from data connections using the Microsoft SQLServer or Microsoft Access Database File providers (SQL Server Databases, Excel files etc.), the character columns for the corresponding new Oracle tables will use character length semantics by default. This could result in larger storage requirements. If the character columns store multi-byte data, it is recommended that you specify the length semantics (byte or character) and the column length.

Creating and Deleting ADDM Tasks

• If an error occurs when creating an ADDM task, for example, the AWR snapshots no longer exist, the ADDM task still might get created, although it will be in an error state.
• When deleting an ADDM task that has the same name as an ADDM task in a different schema, the error, "ORA-13605: The specified task or object <TASK NAME> does not exist for the current user.", will occur where "<TASK NAME>" is the name of the ADDM task being delete. Although the error occurs, the task still gets deleted.