Browsing Solutions For SchemaEditor

  • SchemaEditor creates a new relation with a NULL type_id in adp_sch_rel_info

    When applying a set of schema changes to the database, SchemaEditor would indicate that everything was processed properly. However, an inermittent issue could occur that would create the relation definition in the adp table (adp_sch_rel_info) with a NULL type_id (meaning that the relation is not properly related to the table). This situation can occur due to a SchemaEditor bug when it resolves the order in which schema changes are to be applied. For example, if it tries to save a relation before the table (that the relation belongs to) has been saved.

  • Support for Oracle 11 in SchemaEditor

    The database type configuration setting does not support Oracle11 as a valid setting.

  • Support for Virtual Columns in Oracle

    Does Clarify and/or Dovetail support virtual columns in Oracle? A new and useful feature found in Oracle 11g, virtual columns, allow you to create table columns which are purely expression-based and aren't stored on-disk. Because virtual columns are not stored on-disk, they are especially useful for fields which are based on, or calculated using, functions, expressions, or sibling fields. Several examples include commission-based salaries, full names, order totals, etc. More info on virtual columns can be found in the Oracle wiki: http://wiki.oracle.com/page/Virtual+Columns

  • Quick Start Guide for SchemaEditor

    Quick Start Guide for SchemaEditor. This quick start guide walks through the installation and configuration of SchemaEditor, including adding a new column to an existing table using schemascript. The example adds a new integer column named x_test ot the keyphrase table. The keyphrase table isn't used, which is why this table was selected for the example.

  • SchemaEditor error: Input XML document did not pass validation. invalid child element 'databaseSpecificSql'

    Error Occurred : Input XML document did not pass validation at line number 90393. The element 'sqlView' in namespace 'http://www.dovetailsoftware.com/2006/10/DataDictionary.xsd' has invalid child element 'databaseSpecificSql' in namespace ' http://www.dovetailsoftware.com/2006/10/DataDictionary.xsd'. List of possible elements expected: 'description, sqlViewColumn' in namespace 'http://www.dovetailsoftware.com/2006/10/DataDictionary.xsd'.

  • SchemaEditor error: The schema file being used does not have the correct namespace.

    Error Occurred : The schema file being used does not have the correct namespace. The correct namespace for your database is http://www.dovetailsoftware.com/2006/10/DataDictionary.xsd

  • < storageLocations > section of the .SchemaEditor file is applicable only to those indexes identified in the schema

    For each object within the Clarify schema, a primary key index is created for the objid column. This index uses the following naming convention (Oracle): < object name >_OBJINDEX. In MSSQL Server, the naming convention is OBJINDEX only. For example, the "case" object, the index name for the objid column is CASE_OBJINDEX in Oracle and OBJINDEX in MS SQL Server. Each object/table gets this index by default. This index is not specified in the data dictionary file or in schemascript when adding a new object to the schema. Within the .SchemaEditor file, configuration can be made for tables and indexes to reside in different tablespaces (Oracle) or filegroups (MS SQL Server), however if the above index is specified in the < storageLocation > section, this configuration does not take effect. This leaves the primary key index on objid within the default tablespace/filegroup of the SA user and no mechanism for moving it to a different storage location.

  • Timeout expired. The timeout period elapsed prior to completion

    When using a Dovetail product, the following exception can occur: Exception: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

  • SchemaEditor error: Invalid field name found in the FieldNames property for Index

    SchemaEditor can throw an error such as Invalid field name "n_salesmechanixid" found in the FieldNames property for Index "i5413". (Note that the exact name of the field and index may be different)

  • SchemaEditor error: Could not find column for SpecFieldID 5

    SchemaEditor can throw the following error: Could not find column for SpecFieldID 5 Note that the number 5 could be almost any integer.

  • Using Dovetail Software products with 32bit Oracle drivers can cause ORA-12154 error

    When running a Dovetail Product that is using 32bit Oracle drivers, a user may encounter a message as follows: ORA-12154: TNS:could not resolve the connect identifier specified The above message should be displayed to the user, or located in log files for the product being used. As an example, Dovetail Schema Editor shows the following: "Error Occurred : Database settings in "Default.SchemaEditor" are not valid. Please confirm that database type and connection string are correct." Within the SchemaEditor.log file, the following exists: 2010-10-12 14:44:51,259 ERROR Dovetail.DataDictionary.Persistence.Database.SqlHelperAdapter - Database connection could not be made: ORA-12154: TNS:could not resolve the connect identifier specified System.Data.OracleClient.OracleException: ORA-12154: TNS:could not resolve the connect identifier specified This issue is not specific to Dovetail applications, but is a known Oracle bug with respect to the path used for Oracle 32 bit software. Typically this occurs in 64bit OS environments where (by default) Windows likes to install 32-bit apps into the C:\Program Files (x86)\... folder. The problem is in the C:\Program Files (x86)\ directory name - specifically, the parenthesis. Calls made to the 32bit drivers fail because the calling program information is passed to Oracle, where it takes the () as a special command. Oracle Article ID 334528.1 provides detailed information (login required): https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=334528.1

  • How do I enable logging of windows installer failures?

    Problems can crop up with windows installers. If you do not have permissions or a required subsystem is missing you can get weird errors. When you open a case with us regarding installation issues we will likely ask that you send us an installer log. Below are instructions on how to get a log of the results of an failure to install one of our MSI installers.

  • Adding view columns a SQL view with Schema Editor results in an error

    When adding a view column to an existing SQL view using schema script you may see the following error: Error Occurred : 'table_name' has fewer columns than were specified in the column list.

  • Editing SchemaEditor XML files in Wordpad causes weird letters to appear in the file

    While preparing to apply schema changes using Dovetail Schema Editor it is common to edit the exported schema XML. When editting schema files using Microsoft Wordpad you may get weird characters emitted to your saved files. For example: <description><![CDATA[Reserved; obsolete]]></description> <column nameA"dev" <indexRelation name="amort_dtl2contr_pr" order="3A />

  • Dovetail SchemaEditor did not create sequence when adding a new table

    Dovetail SchemaEditor did not create sequence when adding a new table. Previous changes to the schema did result in sequences being added, but this time a sequence was not added.

  • Removing a Table or a Column having an Index could result in an error.

    When removing a table or a column that exists in an index within the schema, SchemaEditor will correctly require you to also remove the related indexes. If the indexes and column(s) or table(s) are both removed from the schema, the DDL that is executed performs the DROP TABLE or the ALTER TABLE DROP COLUMN statement as directed. This is correct behavior. SchemaEditor next attempts to drop the associated indexes by issuing the necessary DROP INDEX statements. A problem arises when this DDL is executed since the indexes have already been silently removed by the previous DROP TABLE or ALTER TABLE DROP COLUMN statements. When this occurs, users will receive the following error: Error Occurred : ORA-01418: specified index does not exist As of version 2.1, SchemaEditor does not currently check for the existence of indexes when a simultaneous DROP TABLE or ALTER TABLE DROP COLUMN statement is executed, as directed by changes in the schema. Scenario/Steps to reproduce: 1) Add a new column to a table, and an index using that column via schemascript: <addColumn name="licenseKey" dataType="String" table="x_test_table_1" > <length>255</length> <description>null</description> </addColumn> <addIndex name="my_new_index1" columns="licenseKey" table="x_test_table_1"> <description>This is the description of my custom index</description> </addIndex> 2) Apply changes 3) Export schema, creating a data dictionary file 4) Remove the column and the index above from the data dictionary file (SchemaEditor only support drops from data dictionary, NOT schemascript). 5) Preview changes. The DDL preview shows: 2009-09-18 11:07:47,019 -- Writing out ddl preview SQL statements. 2009-09-18 11:07:47,144 -- ALTER TABLE table_x_test_table_1 DROP (licenseKey) 2009-09-18 11:07:47,144 -- DROP INDEX x_test_table_1_my_new_index1 6) Apply changes and you will receive the above error.

  • What happens when a new table is added by Dovetail SchemaEditor?

    What happens when a new table is added by Dovetail SchemaEditor?

  • Schema Editor error - SqlViews are not supported in this instance of Clarify.

    This error occurs when trying to add sql views to an early revision of Clarify which does not support it. To detect if a Clarify database supports sql views Schema Editor looks to see if a 'sql' column is present in the adp_tbl_name_map table.

  • Can I change a the dataType of a column from varchar to text ( longString) using SchemaEditor?

    Can I change a the dataType of a column from varchar to text ( longString ) using SchemaEditor?

  • SchemaEditor Error Occurred : a different object with the same identifier value was already associated with the session:

    When applying a schema script, the preview is successful, but the apply action throws an error. An error occurred while applying schema changes to the database. Your database may be in an inconsistent state. It is highly recommend that you restore your database Error Occurred : a different object with the same identifier value was already associated with the session: Dovetail.DataDictionary.Persistence.Database.ViewJoinDto, of class: Dovetail.DataDictionary.Persistence.Database.ViewJoinDto

  • Implicit cross joins error occurs when editting a view

    When using Dovetail Schema Editor to create a new view or edit an existing one it is possible to get this error when previewing or applying a schema change: "Added view "(view name)" can not have implicit cross joins."

  • Applying updates using SchemaEditor fail with the error "Could not save object"

    Applying schema changes to MS SQL Server 2005 databases using SchemaEditor can sometimes fail when adding a new table having a relation. The failure will result in the error message "Error Occurred : Could not save object" Here is an example of what the logging output looks like: INFO Dovetail.SchemaEditor.UI.Console.ApplyVerb - An error occurred while applying schema changes to the database. Your database may be in an inconsistent state. It is highly recommend that you restore your database (you did back up, right?). ERROR Dovetail.SchemaEditor.UI.Console.ConsoleController - Error Occurred : Could not save object ... NHibernate.ADOException: Could not save object ---> System.NullReferenceException: Object reference not set to an instance of an object. at Dovetail.DataDictionary.Persistence.Database.RelationDto.GetHashCode() at NHibernate.Engine.Key.GetHashCode()

  • Can SchemaEditor be used to create a new Clarify database?

    Can SchemaEditor be used to create a new Clarify database?

  • Error viewing CHM files: The page cannot be displayed

    Trying to read can result in the CHM file showing an error such as "The page cannot be displayed". There are several possible reasons why your CHM e-books and documentation files are unreadable.

  • Could not retrieve field 'x_num_recent_obj' for object type 'user'

    After applying schema changes using SChemaEditor 1.2 or below, and then starting the Clarify Classic Client, the following error can occur: "Could not retrieve field 'x_num_recent_obj' for object type 'user'; local schema file may be out of date" The column 'x_num_recent_obj' exists in SQL Server on table_user, and has been added to teh adp_sch_info table properly.

  • Invalid column name 's_login_name' OR Invalid column name 's_alias_name'.

    On MSSQL databases, after applying schema changes using SchemaEditor, and then running fcClient, the following error can occur: Invalid column name s_login_name On MSSQL databases, after applying schema changes using SchemaEditor, and then running DIET to import the fcclient_alert_tables.dat file, the following error can occur: Invalid column name 's_alias_name'.