Home | About TOYS | Download | Support | Contact


TOYS Bugs and Issues

The following lists all known issues in TOYS.

While the number of issues is small we will present bugs and issues as a single page. When the number grows so as to make this form of presentation impractical we will change to using our bug-tracking software.

All known bugs and all significant issues are listed against each of the versions of TOYS to which they apply.

See Oracle Features Supported by TOYS for a detailed list of those Oracle features that are supported.

See TOYS Release History for a summary of the changes made in each release.

To submit a new bug or issue Email our support teamEmail our support team.

Oracle® is a registered trade mark of Oracle Corporation. Microsoft® and Windows® are registered trade marks of Microsoft Corporation.




  • BUG #409 - Incorrect handling of NUMBER(*,0) in Oracle 11.

    First: 1.0.7  Resolved In: 1.0.46  Reported: June 20, 2010

    The Oracle server, prior Oracle 11, would [correctly we believe] translate a table column datatype defined as "INTEGER" to be "NUMBER(*,0)". As of Oracle 11, this behaviour changes causing "INTEGER" to be translated to "NUMBER(38,0)". For convenience, TOYS has always expressed NUMBER(*,0) as INTEGER but because the handling of INTEGER has changed behaviour in Oracle 11, TOYS will now express NUMBER(*,0) simply as such. This affects both the display of datatypes and the generated DDL.


  • BUG #408 - Snapshot files with synonyms having dependencies are not handled.

    First: 1.0.42  Resolved In: 1.0.46  Reported: June 09, 2010

    When loading a snapshot file, TOYS mistakenly rejects the snapshot file when synonyms have dependencies.


  • BUG #407 - A grant to oneself gets translated to a grant to PUBLIC.

    First: 1.0.7  Resolved In: 1.0.46  Reported: June 09, 2010

    When loading a snapshot file, TOYS mistakenly translates a grant made by a grantee to themselves as being a grant to PUBLIC.


  • BUG #406 - Some attributes fail to load correctly from snapshot files.

    First: 1.0.44  Resolved In: 1.0.45  Reported: May 27, 2010

    When loading snapshot files, some attribute values load incorrectly [their value is always loaded as 1]. The following items are affected:

    • Sequences - Minimum, Maximum, Increment, Start With, Last Value.
    • Clusters - Hash Keys.
    • Storage properties - Initial Extent, Next Extent.

    Please note that the snapshot contents are valid but that TOYS 1.0.44 will not function correctly with ANY snapshot files with respect to the above items.


  • BUG #405 - Schema capture aborted due to invalid SQL when capturing public synonyms.

    First: Prior 1.0.38  Resolved In: 1.0.44  Reported: May 12, 2010

    When capturing public synonyms [but not private synonyms] and the connected user had SELECT ANY DICTIONARY privilege, the capture would terminate because invalid SQL was generated.


  • BUG #404 - User defined types are not dropped in the sync script.

    First: 1.0.8  Resolved In: 1.0.42  Reported: January 16, 2008

    When user defined types are absent in the reference database they are not dropped in the generated synchronization script.

    As of this bug fix, TOYS now generates the correct DDL to drop types.


  • BUG #403 - Failure to load a snapshot when a check constraints has zero columns.

    First: 1.0.8  Resolved In: 1.0.42  Reported: January 15, 2008

    TOYS will happily capture and compare schemas that contain check constraints without columns. However when you try to re-load the saved snapshot TOYS pops up a message similar to the following:

    Error processing XML: no columns specified within element "check-constraint" [ detected reading "xxxxx.snp" after line 475, column 7 ]

    Checks constraints without columns are of dubious value and TOYS had been coded to reject these.

    As of this bug fix, TOYS will now handle such CHECK constraints correctly.


  • BUG #402 - Failure to re-compile invalid views.

    First: 1.0.32  Resolved In: 1.0.38  Reported: February 02, 2007

    When synchronizing views and the only differences detected is the validity state TOYS fails to emit an ALTER VIEW view COMPILE statement.


  • BUG #401 - Failure to load compare options when "Include Orphans" is selected.

    First: 1.0.31  Resolved In: 1.0.38  Reported: October 12, 2006

    If the compare option "Include Orphans" is selected for constraint types and the compare options are saved to a file then TOYS will refuse to load the file complaining that the enumerated value is invalid. As an interim work-around the "illegal" value [i.e. a "2"] can be changed to a "1" [i.e. "exclude orphans"] alternatively install TOYS 1.0.38.


  • BUG #400 - Incorrect handling of addition of NOT NULL columns without defaults.

    First: Prior 1.0.30  Resolved In: Not resolved  Reported: September 04, 2006

    If mandatory (NOT NULL) columns are added with a default clause then the Oracle server will quite happily add the column, set it to the default value and then enable the NOT NULL constraint (if required). However if there is no default clause for the new column then the Oracle server raises the following error:

    ALTER TABLE some_table ADD ( some_column DATE NOT NULL )
            *
ERROR at line 1:
ORA-01758: table must be empty to add mandatory (NOT NULL) column

    It does not matter if the column is added with the NOT NULL constraint DISABLED. The Oracle server seems to ignore this and simply rejects the command.

    Previous versions of TOYS simply attempted to add the column along with the default clause (if any) and the not null constraint (if any).

    As of this bug fix, TOYS will add columns with NOT NULL constraints as follows:

    • If the column has a default clause then the column is added along with the default and not null constraint.
    • If the column does not have a default clause then the column is added minus its not null constraint. The NOT NULL constraint is added DISABLED in a subsequent step and finally the NOT NULL constraint is [attempted to be] enabled.


  • BUG #393 - DDL Scripts containing only object grants or table constraints are incorrect.

    First: 1.0.31  Resolved In: Not resolved  Reported: January 13, 2006

    DDL generation of scripts which contain only object grants or only table constraints are incorrect.


  • ISSUE #391 - Some noted deficiencies in synchronization.

    First: Prior 1.0.18  Resolved In: Not resolved.

    When system named indexes are created / re-created the index is created with its system generated name which is not exactly correct and could fail if a system generated index already exists with that name.


  • BUG #377 - Enabled primary/unique keys not handled correctly with RELY option.

    First: 1.0.7  Resolved In: Not resolved.

    When a primary/unique key is created with the RELY option and it does not have a supporting index, TOYS ignores the enabled/disabled state and simply treats the constraint as DISABLED. This may be of concern in data ware-housing environments.


Top of Page