Welcome to IDERA DBArtisan® 16.6

DBArtisan Home | DBArtisan Documentation | IDERA Technical Support | www.idera.com

ReadMe Last Published: June 8, 2017. Any updates to these notes will be available at www.idera.com/support/productdocuments.


Thank you for using IDERA DBArtisan, the award winning DBA tool for enterprise-wide database administration. DBArtisan empowers you to manage all of your critical databases running on current versions of IBM DB2, Oracle, PostgreSQL, Microsoft SQL Server, MySQL, Sybase and Teradata systems, from a single, consistent, user-friendly interface. Before you use DBArtisan, please read the following information.

What's New in DBArtisan

Extract, Migrate, and Report Functionality Completed for Oracle Object Types Added in 16.5

Supports Additional Oracle Object Types

Improved Explain Plan Support

Adds Support for DB2 LUW 11 and Sybase 16

Technical Requirements

Browser Requirements

Hardware Requirements

Operating System Requirements

32-bit versus 64-bit Application Considerations and Restrictions

DBMS Support and Connectivity

Dedicated Support Connectivity Options

IDERA Team Server 2016 Support

Generic JDBC/ODBC Connectivity

IBM DB2 for z/OS Stored Procedure Requirements

Specifically-tested JDBC/ODBC Connectivity Products: Apache Hive/Hadoop

DBMS Versions No Longer Supported

Release Notes

Important Advisory Notes

Team Server 2016 Installation and Configuration

Known Issues

Bug Fixes

Additional Resources

Licensing Your IDERA Product

IDERA Product Support

IDERA Technical Support

IDERA on the Web

What's New in DBArtisan

Extract, Migrate, and Report Functionality Completed for Oracle Object Types Added in 16.5

DBArtisan 16.6 is updated to include migration support, schema extractions, and reporting for the object types added in this release as well as the following object types added but not fully completed in DBArtisan 16.5:

·        Context

·        Dimensions

·        Policies

·        Policy Groups

·        Queues

·        Queue Tables

·        Refresh Groups

·        Resource Consumer Groups

Supports Additional Oracle Object Types

DBArtisan also includes support for the following schema object types:

·        Audit Policies

·        Resource Plans

·        Unified Auditing

NOTE: This release does not include the implementation of the following Oracle features:

·        Editions

·        Flashback Archives

·        Pluggable Databases

·        Redaction Policies

Improved Explain Plan Support

DBArtisan 16.6 now allows you to view Explain Plans using DBMS_XPLAN formatting as well as manage the columns for your query explain plans. Some DBAs can comprehend Explain Plan output faster in the DBMS_XPLAN format rather than in a tree or graphical view. This option in DBArtisan helps those users improve efficiency and efficacy. When managing which columns appear in the results, an easy-to-use interface allows you to quickly hide/show columns, change the order in which the columns appear in the explain plan, and to save the settings so that you can share with orders who are interested in the same format.

Adds Support for DB2 LUW 11 and Sybase 16

DBArtisan includes support for DB2 LUW 11 and Sybase 16.

Technical Requirements

Before using DBArtisan, please verify that your environment meets the requirements listed below:

NOTE: Users need full registry privileges during the installation and access to the keys under HKEY_CURRENT_USER in the registry after installation.

Browser Requirements

DBArtisan requires Microsoft Internet Explorer 11 or later.

Hardware Requirements

IDERA recommends the following minimum hardware requirements:

Operating System Requirements

DBArtisan supports the following operating systems:

Windows 7 Support Notes - Windows 7 provides two user types: Standard users and Administrators. DBArtisan can be installed or uninstalled by an administrator or by a standard user using an administrator token. Standard users can run DBArtisan. For the purpose of running DBArtisan, default standard user token privileges should not be modified. Modifying standard user token privileges can result in licensing issues which will prevent DBArtisan from operating properly.

32-Bit Versus 64-Bit Application Considerations and Restrictions

If you install the 64-bit version of DBArtisan and you are using custom drivers, you must be using 64-bit versions of those drivers when using the 64-bit version of DBArtisan. Similarly, 32-bit versions of custom drivers must be used with the 32-bit DBArtisan installation.

For version control integration, if you install the 64-bit version of DBArtisan, you can work with either a 32-bit or 64-bit MSSCCI provider. The feature is controlled from the Options Editor's Version Control tab (File > Options > General > Version Control).

DBMS Support and Connectivity Options

Dedicated Support Connectivity Options

DBArtisan provides dedicated connectivity to a specific version range of IBM DB2 for Linux, UNIX, and Windows, IBM DB2 for z/OS, Microsoft SQL Server, MySQL, PostgreSQL, Oracle, Sybase, and Teradata databases.

The following connectivity options are provided:

The following table provides a summary of resources/requirements for connectivity to dedicated DBMS platforms. For each platform, it lists supported versions, the client software that must be installed if using native IDERA clients, and the third-party, Type 4 JDBC drivers packaged with DBArtisan.

DBMS Platform

Supported Versions

Client Required for use with Native IDERA Drivers

Packaged JDBC Driver

Source & License

IBM DB2 for z/OS

910.x and 11.x*

DB2 UDB Client for Windows 8.0 or later

IBM Data Server Driver for JDBC

IBM DB2 for LUW

910.x and 11.x*

IBM DB2 LUW Client for Windows 8.0 or later

IBM Data Server Driver for JDBC

Microsoft SQL Server

2008
2012
2014*

2016*

Microsoft SQL Server Client Library

jTDS Type 4 JDBC Driver for Microsoft SQL Server
Microsoft SQL Server JDBC Driver

LGPL source & license

MySQL

4.x

MySQL Connector/ODBC Driver 5.2.x Driver - MySQL Connector/ODBC driver 3.51.x Driver

MySQL Connector/J JDBC Driver

GPL source & license

Oracle

9i, 10g, 11g, and 12c*

Oracle SQL*Net Client

Oracle JDBC Thin Driver

PostgreSQL

9.3 and 9.4  
Specifically-supported PostgreSQL-based database products include Greenplum, Pivotal HAWQ, and BigSQL.

PostgreSQL ODBC Driver (latest version recommended)

PostgreSQL JDBC Driver

BSD License

Sybase ASE

12.5 - 15.7, 16.0

Sybase Open Client

jTDS Type 4 JDBC Driver for Microsoft SQL Server
Sybase jConnect JDBC Driver

LGPL source & license

Sybase IQ

12.7 - 15.4, 16.0

SQL Anywhere ODBC drivers for Sybase IQ 12.7
Sybase IQ 32-bit ODBC drivers

Sybase jConnect JDBC Driver for Sybase IQ

 

* About Technical Previews - Technical previews are intended to introduce a new DBMS platform only. The available functionality is typically minimal. For example, command Line startup, standard datasource registration and connection features, limited Datasource Navigator tree functionality, a minimal set of object actions, as well as SQL Editor execution and related, common SQL Editor functionality such as Query Options, Paste SQL Syntax, and Paste SQL Statement.

IDERA Team Server 2016 Support

DBArtisan can make use of datasource definitions stored on an IDERA Team Server 2016.

Generic JDBC/ODBC Connectivity

Generic JDBC/ODBC connectivity to non-dedicated DBMS systems or non-database datasources is also provided. DBArtisan can connect to a datasource using a customer-provided, third-party JDBC version 4.0 or ODBC version 3.0 drivers. Minimal DBArtisan functionality is provided, including a basic Explorer tree and SQL querying.

IBM DB2 for z/OS Stored Procedure Requirements

When working against an IBM DB2 for z/OS data source, DBArtisan relies on the following stored procedures, provided as an optional installation step in setting up the DB2 subsystem:

·        DSNWZP

·        DSNUTILS

·        ADMIN_COMMAND_DSN

·        ADMIN_COMMAND_DB2

Prior to using DBArtisan against an IBM DB2 for z/OS data source, ensure that these components are installed on the server.

Specifically-Tested JDBC/ODBC Connectivity Products: Apache Hive/Hadoop

DBArtisan has been successfully tested against Apache Hive/Hadoop datasources using the Hortonworks ODBC driver. Similarly, Cloudera Impala datasources have been tested using the Cloudera JDBC driver. In both cases, SQL querying and a Datasource Explorer/Navigator tree are available.

DBMS Versions No Longer Supported

DBArtisan is no longer being tested against Sybase ASE versions before 15.7.

Release Notes

Important Advisory Notes

Team Server 2016 Installation and Configuration

Team Server 2016 must be installed and configured in order to get its Datasource and Credential Synchronization in DBArtisan.

You can find all the information for installing Team Server 2016 in Install and Configure Team Server 2016.

Team Server URL must be also configured in DBArtisan. For that, add the Team Server URL in Tools > Options... > Team Server.

Known Issues

 

1.      Close DBArtisan.

2.      Uninstall the older MySQL ODBC client.

3.      Restart DBArtisan and try connecting to a MySQL datasource. You are prompted to install the MySQL client drivers.

4.      Follow the installation instructions to install the new driver.

o   The Debugger windows (Variables, Watch, CallStack, Dependency) cannot be undocked. This behavior is deliberate and is true only for the Debugger windows. The Output window can be undocked.

o   When running Windows XP SP2, SQL Server 2000 SP4 is required on both the client and the server.

o   When running the Debugger on SQL Server 2005 CLIENTS:

1.      Verify that the file ssdebugps.dll is registered on the client machine. This file is REQUIRED for debugging and Microsoft only installs it on the server machine and not as a part of a client-only install.

2.      Follow the instructions under the "Configure DCOM on the computer that is running Visual Studio. NET" heading from Microsoft to reconfigure the DCOM settings on your client machine: //support.microsoft.com/en-us/kb/833977.

3.      On the Default Properties tab of the My Computer dialog box, make sure the Default Authentication Level is set to None and that the Default Impersonation Level is set to Impersonate.

o   When using the IDERA Sybase debugger against a Sybase database with multiple temporary databases (supported in Sybase ASE 12.5.0.3 and above), either the user or the debugger application must be bound to a specific temporary database.

§  To bind the IDERA Sybase Debugger:

sp_tempdb "bind" , "ap", "Sybase Debugger", "DB", "<tempdb name>"

§  To bind the user:

sp_tempdb "bind", "lg", "<login id>", "DB", "<tempdb name>"

Bug Fixes

Customer-reported bugs fixed for the DBArtisan 16.6 release:

Issue #

Description

DBMS

DBA-15442

View Extraction sometimes works but will cause the application to crash or be in a hung status

Oracle

DBA-24417

[SQL Assist] Code complete is enabled but does not display suggested columns

Oracle

DBA-29432

Comment lines not showing in the transaction logs

 

DBA-31490

[SQL Editor] Explain plan is not displaying all the steps for a parallel DML

Oracle

DBA-33555

DBArtisan 2016 when extract SQL for a GLOBAL index it gets converted to a LOCAL index in the extraction

Sybase ASE

DBA-33690

Sybase User Object Editor crashes

Sybase ASE

DBA-33697

Oracle passwords are not taking during new user creation

Oracle

DBA-33843

Extracting view definition showing invalid columns

Oracle

DBA-33870

DBArtisan discovers a data source multiple times and adds it with a new extension

Oracle

DBA-33903

Oracle extract is not pulling complete information and is giving a message, AS LANGUAGE C NAME , LIBRARY

Oracle

DBA-33910

Just upgraded to DBArtisan 2016 9.7.5 and on my Oracle connection I cannot see the parameters for an instance

Oracle

DBA-33911

Copying the connection description for an AWS connection to Oracle the program core dumps and exits

Oracle

DBA-33935

Last datasource registered using a TNSNames alias does not show in list

Oracle

DBA-33971

Create like function not working properly

Oracle

DBA-33974

DBArtisan crash

 

RAP-5816

[SQL Editor][Code Complete] Auto complete feature fails to function properly, nothing appears after period

Sybase ASE

RAP-6118

Proc Missing Defines Test gives an error message

Oracle

RAP-6120

ETSQLProblemRequestManagerThread.log

 

Customer-reported bugs fixed for the DBArtisan 2016+ (16.5) release:

Issue #

Description

DBMS

RAP-6086

Login Dialog crash.

RAP-6048

[Data Source Navigator] Occasional crashes when expanding databases node from the datasource navigator.

SQL Server

DBA-33446

[Data Cache] After Preview statements are in the wrong order.

Sybase ASE

DBA-33390

[BNF] CBufferedOutputRouter crash.

 

DBA-33331

PCLender crash.

SQL Server

DBA-32998

[Sybase][Parsers] Batch delimiter ‘go’ on its own is treated as procedure instead of empty statement.

Sybase ASE

DBA-32608

[Oracle][Extract Role] Extracting DDL a role, the users assigned to the role are no longer included.

Oracle

DBA-31248

[Crash Report] DBArtisan crashes while outputting sql results.

All

DBA-30756

[DBMS Actions] Cannot create insert statements from a particular table.

Sybase ASE

DBA-30248

Error establishing a debugger session with the server.

DB2 for LUW

DBA-18630

Extraction issue – XML INLINE LENGTH and compression not recognized.

DB2 for LUW

Customer-reported bugs fixed for the DBArtisan 2016.0.1 release:

Issue #

Description

DBMS

DBA-33166

Case Number 00455434: Invalid column name 'systemwide password expiration'.

Sybase ASE

DBA-33159

[Enhancement] Change fillfactor default value to prevent space consumption and performance issues on index rebuild.

SQL Server

DBA-33154

DBA-33150 [BCBSVT][SQL Editor] Application crashes during SQL Editor session.

DB2 for LUW

DBA-33152

DBA-33150 [Enhancement] Improve the exception handling in case of driver blowing up.

Oracle

DBA-33151

DBA-33150 [ISQL] Nomura crashes.

Oracle

DBA-33150

Find a solution to the random crashes experienced by customers.

All

DBA-33141

[DBMS Object Management] Crash and inoperative state with views.

DB2 for LUW

DBA-33108

Oracle 11g and higher already has a PLAN_TABLE installed.

Oracle

DBA-33095

Provide support for SQL*PLUS script commands.

Oracle

DBA-33076

[Analysts] Unable to run an analysis report.

SQL Server

DBA-33068

[Enhancement][Functions] Some objects do leave out the schema name in the CREATE.

SQL Server

DBA-33033

Customer case 00443195: Schedule of Capacity Analyst does not work on machines with Windows in Spanish.

SQL Server

DBA-32999

[DBMS Object Management] Database option "allow incremental dumps" is not shown for Sybase 15.7 SP130.

Sybase ASE

DBA-32987

[Edit Data] Copy-Paste from Edit Data grid returns weird characters.

SQL Server

DBA-32967

[Schema extraction/publication] Can't execute schema extraction and schema publication with some DBMS.

SQL Server

DBA-32960

In Edit Data, the DELETE of a row is not actually performed in the table.

SQL Server

DBA-32959

[Enhancement] Migrate Database object is misleading.

Sybase ASE

DBA-32945

[DBMS Object Management] Can't exchange a table partition.

Oracle

DBA-32943

Unable to kill sessions from the Lock tab in Database monitoring.

Sybase ASE

DBA-32935

Analyst update error on Oracle datasources ORA-01031: insufficient privileges.

Oracle

DBA-32713

[Utilities] No records are migrated with migrated feature.

Sybase ASE

DBA-32698

[ISQL] Crashes in Isql when running multiple scripts.

All

DBA-31366

[DBMS Actions] Tables based on materialized views do not get extracted with the appropriate unique index.

Oracle

RAP-6050

[JDBC][Procedures] Smallint being treated as bit datatype.

SQL Server

RAP-6048

[Data Source Navigator] Occasional crashes when expanding databases node from the datasource navigator.

SQL Server

RAP-6027

[Crash] Sybase IQ customer crashes.

Sybase IQ

 

Customer-reported bugs fixed for the DBArtisan 2016 release:

Issue #

Description

DBMS

DBA-32830

Not consistently opening SQL files from location set in Directories option for "User SQL Scripts".

DBA-32585

Lapsed time clock at the bottom of a Query/Results tab frame no longer works.

Oracle

DBA-32474

[File Execution Facility] After row 43, Dates are being returned as zeros.

All

DBA-32472

[Regression][DMBS Actions] Hide time portion of DATE datatype if zero option suppresses the time portion for all rows, even if they have non-zero times.

Oracle

DBA-31935

[Schema Extraction] When extracting or compiling Function, the comments are missing from Function.

Oracle

DBA-30919

[DBMS Actions] Ability to name output file.

All

DBA-22901

Request support for Excel 2007.

All

DBA-22732

[Editor results]Request for support for the option to save the result in Excel binary format, extension xlsb.

All

DBA-4638

Wrong database device size is displayed in Explorer window.

Sybase ASE

RAP-5970

Customer case 00430700: The application generates a corrupt xlsx file when importing results to Excel.

Oracle

RAP-5865

[Tools] Ability to save a .csv file from results where all the fields are enclosed in double quotes.

Oracle

RAP-5742

508 compliance for the application: JAWS incorrectly reads the drop-down options that have separators.

 

Additional Resources

Licensing Your IDERA Product

All IDERA products include a 14-day trial period. To continue using the product without interruption, we recommend that you license it as soon as possible. For information on licensing your product, refer to the Installation Guide. If you have not yet purchased this product, contact [email protected].

IDERA Product Support

The IDERA Web site is an excellent source for additional product information, including white papers, articles, discussion forums, and the IDERA Knowledge Base. Visit www.idera.com/support, or click any of the links below, to find:

IDERA Technical Support

If you have a valid maintenance contract with IDERA, the Technical Support team is available to assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of IDERA products to download free software upgrades during the active contract period. Evaluators receive free technical support for the term of their evaluation (14 days).

We encourage you to open technical support cases via the Customer Support Center. For additional information about IDERA Technical Support, visit the Support section of our Web site.

IDERA on the Web

To download evaluations of other IDERA products or to learn more about our company and our products visit us at www.idera.com.