
MaxDB Release Information (7.5.00.08 to 7.5.00.12)

Kernel:
=======

    PTS: 1129237    since: 7.5.00.12

    Fixed Problem:
        appearance:
        The migration of the catalog to unicode aborts/crashes due
        to a corrupted AK cache.
        Preconditions and circumstances:
        The database must contain tables with columns of type
        'serial'.
        Workaround:
        None.
        Solution:
        The unicode migration now checks if a sequence record
        actually contains a sequence name before trying to convert
        that sequence name to unicode.


    PTS: 1129234    since: 7.5.00.12

    Fixed Problem:
        appearance:
        Move Error in Complex View Optimizer routine
        ak664change_where : VAK664 2
        Preconditions and circumstances:
        select * from complexview where the view has so many
        columns that the internal buffer to store original
        statement and view text is insuffizient


    PTS: 1129231    since: 7.5.00.12

    Fixed Problem:
        appearance:
        Constraints were not shown in Oracle-mode when using
        systemview all_constraints
        Preconditions and circumstances:
        - unicode-environment
        - loading the systemtables with default-code x
        (ASCII/UNICODE)
        - changing the default to the other one (UNICODE/ASCII)
        - no re-loading of systemtables
        Workaround:
        reload systemtables after changing the default-code of the
        whole database
        Solution:
        string-literal-handling in unicode-environment will not
        take default-code into account


    PTS: 1129226    since: 7.5.00.12

    Fixed Problem:
        appearance:
        error -8006 with error position -32767
        Preconditions and circumstances:
        - case-function
        - [<authid>.]<tablename>.<columnname> as  value expression
        in the ELSE-part of the case-function
        Workaround:
        get rid of the [<authid>.]<tablename>. in front of this
        columnname or use a superfluous function for this
        [<authid>.]<tablename>.columnname like
        substr([<authid>.]<tablename>.columnname, 1)
        Solution:
        the internal representation of [<authid>.]<tablename> has
        to be taken into account when checking if this is the next
        when-expression or the final else-part


    PTS: 1129195    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        Wrong result count at complex select with correlated
        subqueries
        Preconditions and circumstances:
        Usage of prepared statements with parameters
        Workaround:
        Replace parameters by literals


    PTS: 1129190    since: 7.5.00.12

    Fixed Problem:
        appearance:
        SELECT DISTINCT <join select>
        Preconditions and circumstances:
        strategy for 1. table access is "index only"
        Workaround:
        "DIAGNOSE OPTIMIZE OPERATOR JOIN OFF" or
        database parameter _JOIN_OPERATOR_IMPLEMENTATION = "NO"


    PTS: 1129172    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        AIX logical volume manager cannot manage volumes used by
        database after a restore.
        Releases:
        AIX only
        < 7.3.00.50
        < 7.4.02.27
        < 7.4.03.33
        < 7.5.00.12
        Preconditions and circumstances:
        A raw logical volume must have been configured as database
        data or log volume and a restore operation on such a volume
        must have been executed. The restore failed to read back
        the AIX
        specific reserved part of the raw logical volume and
        overwrote it with zeros. This happened only
        during restore, since attaching always is done for
        read/write access. The failure to read back the
        AIX specific reserved part was silently ignored.
        Workaround:
        none
        Solution:
        During restore operation the volumes have been opened for
        write only access. This is changed to read/write access now
        to allow reading back during restore operation.


    PTS: 1129145    since: 7.5.00.12

    Fixed Problem:
        appearance:
        Restart aborted because the offset of the savepoint is NIL
        with following messages in knldiag:
        Expected ioseq 1234, found 4567-4568 on off 4294967295
        Savepoint not found on log
        Preconditions and circumstances:
        The savepoint is a restart-savepoint, which had been written
        during log-recovery. The logrecovery has been interupted and
        the logvolume has been manipulated (e.g. by a copy from
        another database)
        Workaround:
        use only supported recovery-strategies
        Solution:
        none, only additional check introduced in order to avoid
        crash


    PTS: 1129104    since: 7.5.00.12

    New Feature:
        Feature description:
        The statement 'CHECK CATALOG [WITH UPDATE] is able to
        detect and
        repair some inconsistentcies of the catalog.
        The current user must be a DBA. If WITH UPDATE is omitted,
        inconsistencies
        are detected but not repeaired. If inconsistentcies have
        been found, the
        statement 'SELECT * FROM PARAMETERS' yields further
        information about
        them. Based on this information it should be decided
        whether to make a second
        run with the WITH UPDATE option.


    PTS: 1129004    since: 7.5.00.12

    Fixed Problem:
        appearance:
        If a view does not include all key columsn of an underlying
        base table, an insert
        via that view is not possible. Nevertheless the kernel
        computes the INSERT privilege for
        such a view.
        Preconditions and circumstances:
        A view selects some but not all key columns of an
        underlying base table.
        Workaround:
        None.
        Solution:
        Fixed the bug inside the kernel code.


    PTS: 1128942    since: 7.5.00.12

    Fixed Problem:
        appearance:
        core with traceback:
        SAPDB_MemMoveNoCheck
        SAPDB_PascalForcedOverlappingMove
        a06retpart_move
        a507select_part
        Preconditions and circumstances:
        - select
        - oracle-mode
        - prepare (as with R/3)
        --> select-fetch-optimization
        - several results, the length of the internal resultrow
        multiplied with the number of accepted resultrows within
        one reply exceeds 32KB
        - resultset is copied (see EXPLAIN)
        - _MBLOCK_DATA_SIZE > 32768
        - version 7.5.00.10 / 11
        Workaround:
        set _MBLOCK_DATA_SIZE to 32768
        Solution:
        a 2-byte integer becomes a 4-byte integer


    PTS: 1128931    since: 7.5.00.12

    New Feature:
        Feature description:
        Feature description:
        To reduce collisions on root pages of object containers,
        the removal of object frames for omsKeyedObjects has been
        recoded.
        Now the deletion of the key information within the seperate
        key index tree is done before accessing the root page to
        secure any potential page chaining operation.
        As object container root page access is critical for
        scalability of the liveCache this change hopefully
        preserves the root page access from getting a bottleneck to
        liveCache performance.


    PTS: 1128925    since: 7.5.00.12

    Fixed Problem:
        appearance:
        sometimes function NOW is accepted only with (), sometimes
        only without;
        NOW() can only be used for timestamp-columns, not for
        date/time as with MySQL
        Workaround:
        add/delete ();
        use TIME(NOW()), DATE(NOW()) although not MySQL-like or use
        TIME/DATE instead


    PTS: 1128899    since: 7.5.00.12

    Fixed Problem:
        appearance:
        System allocator statistic shows less memory consumed than
        expected
        Preconditions and circumstances:
        The internal handling of memory requests leads to an
        illegal request size, which is not detected due to an
        overflow in the internal number represention of the
        consumed memory. In a slow kernel this triggers an
        assertion.
        Workaround:
        none
        Solution:
        this patch


    PTS: 1128873    since: 7.5.00.12

    Fixed Problem:
        appearance:
        After executing the statment GRANT USERGROUP * to <user>
        only one of the usergroups owned by the current user got a
        new owner.
        Preconditions and circumstances:
        The current user owns more than one usergroup.
        Workaround:
        Execute the statement until the current user owns no
        usergroup.
        Solution:
        Fixed the bug inside the kernel.


    PTS: 1128840    since: 7.5.00.12

    Fixed Problem:
        appearance:
        core with traceback ak61one_select_column
        Preconditions and circumstances:
        range_check (slowknl) +
        select usually resulting in an error like -2013 select
        column list too long, because more output_columns as given
        as view-column-names / more than 1023 column
        Workaround:
        equalize the number of given view-column-names and
        output-columns / shorten the select-list
        Solution:
        initialize a variable always


    PTS: 1128828    since: 7.5.00.12

    Fixed Problem:
        appearance:
        -9111 vak508,  4 starting position negative >= -11 during
        fetch
        Preconditions and circumstances:
        select including at least one long-column, fetch does not
        fetch all of the output-columns, it does not fetch even the
        first long-column because less output-parameter are
        specified
        Workaround:
        equalize the number of selected and fetched output columns
        Solution:
        the check if at least one long-column is fetched has to be
        changed


    PTS: 1128813    since: 7.5.00.12

    Fixed Problem:
        appearance:
        Restore Data from parallel pipes does not start. One Task
        waits
        for the completion of their first IO, the other ones are
        suspended
        until this IO finishes.
        Preconditions and circumstances:
        A backuptool is used, which sequentializes the parallel
        output of a parallel backup. Due to this the first 8 Pages
        belongs to different parts of the parallel backup.
        Workaround:
        restore the data sequential (one pipe after the other) or
        if enough
        free capacity on harddisks is available then save the data
        from the
        pipe in different files and recover from them.
        Solution:
        code correction


    PTS: 1128770    since: 7.5.00.12

    Fixed Problem:
        appearance:
        Error -9041 System error: BD Index not accessible at update
        command.
        Preconditions and circumstances:
        During an update the index was dropped.
        Workaround:
        Usage of more restrictive sql locks.
        Solution:
        If an index root page is not belonging to the index tree
        anymore the command is parsed again
        so the access strategy is determined new.


    PTS: 1128760    since: 7.5.00.12

    Fixed Problem:
        appearance:
        restore-log or restart fails with message
        "Assertion of state ReCreateOpenTransactions failed failed"
        in knldiag. In the trace one can see
        PAMget: pno: xxxxx (Dynamic/Recoverable (perm)) access:
        ForRead, trError: 8050
        Preconditions and circumstances:
        A logrecovery had been interrupted with recover_cancel. Due
        to this
        a Savepoint interrupts the copying of a logentry, which is
        split over
        more than one page in the redofile. The PageNo of the
        lastPage
        for this redofile in corresponding entry in the
        Opentransfile is wrong and
        therefore not found if this savepoint is used for
        restart/restart for recovery.
        Workaround:
        repeat the recovery and do not interrupt the logrecovery
        Solution:
        code correction


    PTS: 1128750    since: 7.5.00.12

    Fixed Problem:
        appearance:
        crash in diagnose typebuf with traceback
        SQLManErr_Instance::BaseToReturnBinarySearch
        ....
        xt01diagnose
        Preconditions and circumstances:
        none
        Workaround:
        none
        Solution:
        in diagnose the error-instance has to be created in any case
        buf was included with 7.5.00.09


    PTS: 1128748    since: 7.5.00.12

    Fixed Problem:
        appearance:
        Database backup or restore operation from parallel pipe
        medium leads to deadlock.
        Preconditions and circumstances:
        A parallel backup medium made out of several pipes is used.
        The backup and restore does not end and using x_user DBNAME
        show active server tasks in state AsncOpen or AsyncClose
        are visible.
        Workaround:
        Cancel utility task first. Then use only a single pipe or
        several files as backup medium.
        Solution:
        this patch.


    PTS: 1128715    since: 7.5.00.12

    Fixed Problem:
        appearance:
        wrong error -8006/-8028 resp. core with traceback
        ak61one_select_column
        ak61one_star_table_check
        Preconditions and circumstances:
        union/except/intersect-select
        at least one select uses a table/view for which the current
        user has only the privilege to select SOME (NOT ALL) columns
        for this select * is used in the select-list
        Workaround:
        specify the column-names you want to select, do not use *
        Solution:
        privilege-checking for union-selects has to be changed


    PTS: 1128713    since: 7.5.00.12

    New Feature:
        Feature description:
        To avoid some precompiler problems with outdated prepared
        mass commands the kernel doesn't check optimizer statistic
        changes at insert commands.


    PTS: 1128698    since: 7.5.00.12

    Fixed Problem:
        appearance:
        the values of the description of a inversion displyed by
        diagnose are wrong
        or the diagnose crashes when displaying them
        Preconditions and circumstances:
        Logentries, which contains a description of an inversion
        are display in detail
        Workaround:
        use the display FROM ... TO in order to skip the logentries
        which causes diagnose to crash
        Solution:
        code correction


    PTS: 1128673    since: 7.5.00.12

    Fixed Problem:
        appearance:
        The kernel crashes while executing a dml statement that
        fires a trigger.
        Preconditions and circumstances:
        The trigger contains both, dynamic and static sql. The
        static sql follows
        the dynamic sql and the static statement refererences
        columns of the
        trigger table.
        Workaround:
        None.
        Solution:
        Fixed the kernel bug.


    PTS: 1128652    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        A select with rowno predicate result in row not found
        although a result should exist.
        Preconditions and circumstances:
        In the catalog record of the table the row count have to be
        0.
        This could only be checked with x_diag.
        Workaround:
        Recreate table by create like, insert select and rename
        table.


    PTS: 1128640    since: 7.5.00.12

    Fixed Problem:
        appearance:
        CREATE OR REPLACE view does not handle the system
        attribute, i.e. if a view has been
        created without the system attribute and is then recreated
        with the system attribute, this
        information is not stored in the catalog.
        Preconditions and circumstances:
        Workaround:
        None.
        Solution:
        Bug fixed in kernel.


    PTS: 1128637    since: 7.5.00.12

    Fixed Problem:
        appearance:
        wrong data after update
        Preconditions and circumstances:
        UPDATE ... SET ... = CASE WHEN ... THEN.........
        Workaround:
        Do not use CASE WHEN in the set-clause, try to use DECODE
        or the like.
        Solution:
        The code (so far setting the first qualification in the
        CASE always to true) has to check for the case when it has
        to do it and when it is not allowed to change it.


    PTS: 1128628    since: 7.5.00.12

    Fixed Problem:
        appearance:
        The knldiag contains a lot of failed read attempts. After a
        couple of read attempts of the same page,  the page could
        be returned without an error.
        Preconditions and circumstances:
        You need a small  data cache and therefore a lot of i/o.
        Workaround:
        increase configuration parameter CACHE_SIZE
        Solution:
        modification of db kernel


    PTS: 1128603    since: 7.5.00.12

    Fixed Problem:
        appearance:
        error -3008 POS Invalid keyword or missing delimiter with
        an error-position around 500 (for domain.users)
        Preconditions and circumstances:
        select ... from domain.users/domain.roles
        version 7.5.1 / 7.6
        sqlmode <> internal
           OR
        any other complex view defined with sqlmode x
        used with sqlmode y (x <> y)
        including syntax/date-format not correct for the current
        sqlmode/date-time-format
        Workaround:
        select with the same sqlmode/date-time-format as was used
        when the view was defined
        Solution:
        sqlmode/date-format-handling has to be changed when
        handling complex views


    PTS: 1128576    since: 7.5.00.12

    Fixed Problem:
        appearance:
        a kernel with a corrupted FBM doesn't crash
        Preconditions and circumstances:
        corrupted FBM
        Workaround:
        monitor knldiag and stop kernel by hand
        Solution:
        revert to old behavior


    PTS: 1128509    since: 7.5.00.12

    Fixed Problem:
        Only relevant for Hotstandby (not yet delivered)


    PTS: 1128488    since: 7.5.00.12

    New Feature:
        Feature description:
        DIAGNOSE ALTER TABLE <table name> BAD
        sets table state to bad.


    PTS: 1128477    since: 7.5.00.12

    Fixed Problem:
        appearance:
        wrong results/errors in functions like
        TRUNC
        GREATEST/LEAST
        TIMEDIFF
        Preconditions and circumstances:
        none
        Workaround:
        none
        Solution:
        wrong check destroyed;
        datatype-compatibility changed


    PTS: 1128451    since: 7.5.00.12

    New Feature:
        Feature description:
        The row
        CHECKPOINT WANTED     NO
        has been removed from table DB_STATE


    PTS: 1128420    since: 7.5.00.12

    Fixed Problem:
        Memory leak in shared sql fixed
        Workaround:
        Start the kernel with shared sql switched off


    PTS: 1128409    since: 7.5.00.12

    Fixed Problem:
        appearance:
        1. util_execute shutdown can return -7071 if autosave log
        is enabled.
        2. if the kernel is stopped by the operating system via the
        RTE the internal shutdown attempt
            can fail caused by the same reason.
        Preconditions and circumstances:
        autosave log must be enabled and db_offline is not used.
        Workaround:
        no
        Solution:
        The autosave log task is automatically disabled by the
        SHUTDOWN command after
        the shutdown-savepoint and before the kernel is terminated.
        If a log backup is running
        the shutdown waits until the backup is finished.


    PTS: 1128378    since: 7.5.00.12

    Fixed Problem:
        appearance:
        The system view MEMORY_HOLDERS yields no symbolic back
        trace.
        Preconditions and circumstances:
        The platform does not yield demangled symbols (example
        HP-IPF).
        Workaround:
        None.
        Solution:
        Kernel bug has been fixed.


    PTS: 1128231    since: 7.5.00.12

    New Feature:
        Feature description:
        The create statement of views that could not be recreated
        during a migration (either during the implicit migration
        during first startup of a database in a higher kernel
        release or the migration of the catalog to unicode) is now
        logged in a new table SYSVIEWMIGRATIONPROTOCOL which
        belongs to the sysdba.
        The table shows the migration type (either 'Implicit
        Migration' or 'CatalogToUnicode'), a timestamp stating when
        the entry was made, the error code and error position
        within the statement and the statement itself.
        In a unicode database the table's character columns will
        are of type unicode, in an ASCII database of type ASCII.
        The table will be created during the loading of the system
        tables or during any migration if it does not exist. During
        the migration of the catalog to unicode its previous
        contents will be lost.
        Formerly the implicit migration created the table
        SYS_VIEW_MIGRATION_PROT and the catalog migration to
        unicode the table SYS_UNICODE_MIGRATION_PROT. Both these
        tables will not be created any more.


    PTS: 1127654    since: 7.5.00.12

    Fixed Problem:
        appearance:
        Error messages within knldiag file, which are handled by
        the application and which new show up as errors to the
        enduser. These error messages fill up the knldiag.err file
        and make it hard to be aware of real error situations which
        must be handled by support people.
        Preconditions and circumstances:
        These messages have been written, if the application uses
        "out of history" data references
        Workaround:
        none
        Solution:
        upgrade


    PTS: 1124993    since: 7.5.00.12

    Fixed Problem:
        appearance:
        If data recovery was aborted before end you should not be
        able to restart or to continue with incremental backups.
        Solution:
        A flag in the restart record is set at the beginning of the
        recovery and unset at the end.
        If this flag is enabled restart or incremental recovery is
        not allowed.
        The following new error is returned:
        -3070, "A previous data recovery was incomplete and must be
        repeated"


    PTS: 1123427    since: 7.5.00.12

    Fixed Problem:
        appearance:
        A log-backup-operation returns -126 "Databackup missing
        (Backuphistory lost)" although a
        databackup has been made before.
        Preconditions and circumstances:
        The logvolume has been set to "autooverwrite on" or
        to "logwriting off". Due to this there is a permanent
        history-lost situation, wich can not be solved by performing
        a complete data backup.
        Workaround:
        none needed
        Solution:
        Introduction of a new error code for this situation:
        -127 "Logwriting has to be enabled"
        -128 "Overwrite of log has to be switched off"


    PTS: 1128549    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Bad performance at select on very huge table
        because of wrong strategy decision.
        Preconditions and circumstances:
        The result of the multiplication of read datapages and
        total length of the output record is larger than the
        maximum
        of signed int4
        Workaround:
        no


    PTS: 1128498    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Deadlock during liveCache restart. At least one task is in
        vsuspend state 236.
        Preconditions and circumstances:
        You need a lot of removed OID's, a high rate of savepoints
        and a lot of redo log.
        Workaround:
        Reduce the number of redo log to a minimum. Use more
        restore data resp. restore pages
        Solution:
        db kernel update


    PTS: 1128361    since: 7.5.00.11

    Fixed Problem:
        appearance:
        core in slowknl with traceback
        ak67reskey_build + 331 bytes
        a67_sel3_second_part
        ak660three_phase
        range violation value 0 lower bound 1
        Preconditions and circumstances:
        select on view +
        view defined in 7.3 +
        underlying table is systemview
        Workaround:
        none
        Solution:
        reskey_build has to take into account, that old views on
        top of systemviews do not have keycolumns


    PTS: 1128354    since: 7.5.00.11

    Fixed Problem:
        appearance:
        "NULL VALUE" for COUNT(*) on empty join result set
        Preconditions and circumstances:
        DIAGNOSE OPTIMIZE OPERATOR JOIN = ON
        DIAGNOSE OPTIMIZE JOIN ONEPHASE = ON
        Workaround:
        DIAGNOSE OPTIMIZE JOIN ONEPHASE OFF


    PTS: 1128337    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Error -3004 Invalid host file sequence at 'restore log
        replace <filename>' command
        on an unicode db with a filename > 128 characters.
        Workaround:
        Usage of filenames with less than 128 characters
        Solution:
        Now the filename limitation is 256 characters like in all
        other commands


    PTS: 1128266    since: 7.5.00.11

    Fixed Problem:
        appearance:
        dropped containers still exist after restart
            or
        restart fails with following messages within knldiag file
        004-03-04 13:11:03    89 ERR 53000 OBJECT
        vbd95.cpp:1212bd95RemovePageFromObjFile:
        2004-03-04 13:11:03    89 ERR 53000 OBJECT
        nd_free_obj_cnt != nd_max_obj_cnt page
        2004-03-04 13:11:03    89 ERR 53000 OBJECT   dumped into:
        d99240.obj
        Preconditions and circumstances:
        if error only occurs, if after dropping a container, the
        liveCache crashes for some other reason, before the
        garbagecollectors have removed the file.
        Workaround:
        none
        Solution:
        upgrade livecache to actual build


    PTS: 1128239    since: 7.5.00.11

    Fixed Problem:
        appearance:
        liveCache crash during restart
        within knldiag file you will find following messages:
        SAPDBErr Assertion of state bd91ReleaseUnusedObject failed
        failed!
        DBCRASH  vabort:Emergency Shutdown, Log_History.cpp: 1072
        Preconditions and circumstances:
        garbagecollector releases an empty page, which has got
        empty because of delete objects
        and then the page is re-allocated to satisfy the creation
        of new objects within another class container.
        Then livecache crashes for whatever reason
        Workaround:
        none
        Solution:
        uprade to actual build


    PTS: 1128235    since: 7.5.00.11

    New Feature:
        Feature description:
        For better analysis (database analyzer) the UKT Id was
        integrated into the table 'SYSMON_TASK_DETAIL'.
        Furthermore the values
        - actual run queue length of each UKT
        - state of the UKT (sleeping/running)
        - idle count
        were integrated into the existing table 'SYSMON_UKTHREAD'


    PTS: 1128184    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Wrong result when selecting a view
        Preconditions and circumstances:
        selecting a view which includes
        - select on top of a view which has some qualification
        plus
        - <function> ( <set function> (..))
              or
        - <set function> (..) with some arithmetic/concat for the
        set function-result
        for example
          create view v1 as select ... from .. where ...
          create view v2 as select count(...) - 1 from v1
          select * from v2
        Workaround:
        do not select the second view, but use the select which is
        saved in the second view
        Solution:
        the value used for the qualification in first view has to
        be stored together with the definition of the second view.
        So far it was lost/the qualification during select done
        with not-initialized/wrong values.


    PTS: 1128138    since: 7.5.00.11

    Fixed Problem:
        appearance:
        There are lock collisions on rows with different keys.
        Preconditions and circumstances:
        no
        Workaround:
        no, the transaction end solves the problem.
        Solution:
        There are two different hashes used now which produce 2
        uint4 values.
        In addition the 23rd first bytes of the original key are
        taken and the 23rd last bytes are taken
        for the compressed lock key.


    PTS: 1128133    since: 7.5.00.11

    New Feature:
        ALTER TABLE ... NOT NULL DEFAULT <defvalue> now possible in
        oracle mode


    PTS: 1128102    since: 7.5.00.11

    New Feature:
        Feature description:
        The utility command for restore data is extended by a
        possible value for
        an expected label in the backup. If the label is not equal
        to the label
        in the backup, the recovery will be rejected with the error
        -2026,Invalid label.
        The syntax is the following: An additional keyword LABEL
        followed by
        a character string with a maximal length of 10 characters.
        This is
        optional, but when given, it must be the last parameter of
        the command.


    PTS: 1128095    since: 7.5.00.11

    Fixed Problem:
        appearance:
        negative SERVERDBSTATISTICS
        Preconditions and circumstances:
        more than ~20.000.000 Pages or 160GB data
        Workaround:
        none
        Solution:
        prevent overflow in calculation


    PTS: 1128081    since: 7.5.00.11

    Fixed Problem:
        appearance:
        If a table is created via CREATE TABLE ... AS SELECT and a
        constraint is defined
        for that new table, it is posible to insert data which
        violates the constraint.
        Preconditions and circumstances:
        The <query expression> yields data violating the constraint.
        Workaround:
        Create the table without the constraint, delete all rows
        violating the constraint  and create
        the constraint via the alter table statement.
        Solution:
        Fixed the kernel bug.


    PTS: 1128076    since: 7.5.00.11

    Fixed Problem:
        appearance:
        The loader transport of constrained tables in PAGES format
        between UNICODE database instances  produces error -350
        (Referential integrity violated), even though no constraint
        violation exists.
        Preconditions and circumstances:
        There is a foreign key having unicode columns defined for
        the table to be loaded.
        Workaround:
        None.
        Solution:
        Fixed kernel bug.


    PTS: 1128074    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Some catalog query returns error -9111, from VKB721, move
        37.
        Preconditions and circumstances:
        Probably a select ... into statement has been running.
        Workaround:
        None.
        Solution:
        Fixed a bug in kernel.


    PTS: 1127999    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Error "-1 Duplicate key in index" at insert command
        although the relevant record was just deleted.
        Preconditions and circumstances:
        Prior delete used an index strategy
        Workaround:
        Avoid index strategy at delete command


    PTS: 1127945    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Out of memory problem after tracing used internal symbolic
        stack backtraces very often (AIX only)
        Preconditions and circumstances:
        Parameter ALLOW_DEMANGLE must be set to YES
        Workaround:
        Set ALLOW_DEMANGLE=NO and restart your database.
        Solution:
        ALLOW_DEMANGLE is replaced by SYMBOL_DEMANGLING leading to
        a new default after upgrade installation. This
        automatically fixes the problem.


    PTS: 1127908    since: 7.5.00.11

    Fixed Problem:
        appearance:
        crash in precompiler
        Preconditions and circumstances:
        data for one record (one dataportion) together with the
        other parts sent during execution is longer than the input
        order interface
        Workaround:
        shorten the statement --> do not include as many parameter
        --> usually shorten the number or OR-conditions or the
        number of IN-values
        Solution:
        the check in the kernel takes the other parts sent during
        execution into account


    PTS: 1127884    since: 7.5.00.11

    Fixed Problem:
        appearance:
        The restart of a aborted previous restart crashes with
        access violation caused by null-pointer access.
        The slowknl aborts with Assertion DeleteForRedoCopy failed.
        Preconditions and circumstances:
        This can happen if the previous restart has a savepoint
        which contains an open committed transaction and the reader
        just points to this commit as the last read entry.
        During second restart the transaction is immediately
        inserted into the redo list so the redo tasks can process
        it.
        When the reader is restarted again the first entry it reads
        is the commit entry of the already processed transaction.
        At this point a check should assure that this found  commit
        does not try to insert the transaction a second time.
        This condition was wrong and so resources were tried to
        deallocate which were not allocated.
        Workaround:
        The recovery must be started again with a data recovery and
        should be avoided to abort the redo process.
        Solution:
        Code Correction


    PTS: 1127842    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Linux_IA64 only: The database does not start if
        USE_COROUTINES is set to YES (Default NO)
        Preconditions and circumstances:
        Parameter USE_COROUTINES must have been set to YES on
        Linux_IA64.
        Workaround:
        None, you must set USE_COROUTINES to NO on Linux_IA64
        without this patch.
        Solution:
        The coroutine context alignment was fixed, which allows to
        set USE_COROUTINES to YES.


    PTS: 1127795    since: 7.5.00.11

    New Feature:
        Feature description:
        Implementation of an extended converter page specific i/o
        check which is used by default after a page is read from
        the data area. This is usefull to find a corrupted
        converter page as soon as possible.


    PTS: 1127791    since: 7.5.00.11

    New Feature:
        Feature description:
        A simple hash join algorithm has been implemented: during a
        join it might be advantageous to buffer small tables in
        memory and to access individual keys via a hash function
        instead of searching. If there are many accesses to the
        table the cost of reading the whole table and building the
        hash will be small compared to the benefit of faster key
        lookups.
        This hash join will only be used for key strategies.
        The hash join can be switched on and off via the 'diagnose
        optimize join hash on/off' command. It is switched on by
        default.
        To check whether the hash join optimization is activated
        you can check the sysdd.diagnose view using "select * from
        sysdd.diagnose where name = 'HASH JOIN'".
        The hash join is controlled by the following two
        configuration parameters:
        'MAX_SINGLE_HASHTABLE_SIZE': The maximum table size in KB
        for which hash joins will be executed. If
        MAX_SINGLE_HASHTABLE_SIZE = 0 then no hash tables will be
        created during join execution.
        'MAX_HASHTABLE_MEMORY': The maximum memory in KB that can
        be used for hash joins at any time. As there can be
        multiple hash joins running at the same time, the amount of
        memory used for all hashes might become excessive if it is
        unlimited. This parameter sets the upper limit for the
        memory provided for all hash joins that are running in
        parallel. If during join execution a join transition
        qualifies for a hash join but the overall memory used for
        all hash joins would be more than MAX_HASHTABLE_MEMORY a
        regular join will be executed instead.


    PTS: 1127776    since: 7.5.00.11

    Fixed Problem:
        appearance:
        The problem has never been occurred yet.
        Preconditions and circumstances:
        No more memory inside the allocator.


    PTS: 1127732    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Restart of a previous Restart fails with "SAPDBErr
        Assertion of state cannot read afterimage failed!"
        Preconditions and circumstances:
        This can happen if a previous restart is continued.
        Workaround:
        The recover must be repeated with the last data backup and
        should not be aborted until it is finished.
        Solution:
        code correction


    PTS: 1127706    since: 7.5.00.11

    Fixed Problem:
        appearance:
        During restart/recovery the order of the redo-transactions
        transactions is wrong.
        Preconditions and circumstances:
        The restart/recovery includes a Log_IOSequenceOverflow and
        the
        OpenTransFile is empty (i.e. no opent transactions during
        the restart-
        savepoint).
        Workaround:
        use another data-backup which contains open transactions in
        its restart-savepoint.
        Solution:
        code correction


    PTS: 1127638    since: 7.5.00.11

    Fixed Problem:
        appearance:
        A LogBackup is started and the kernel crashes with the
        errormessage
        "Assertion of state Log_SaveIterator::CheckPageBuffer
        pagebuffer
        contains no endOfLogDevice failed!" in the file knldiag
        Preconditions and circumstances:
        A logRecovery lead to a restart by the command
        recover_ignore, also this command should have been
        rejected by the kernel.
        Workaround:
        Try to determine, which changes had been lost by the
        recover_ignore (have a look at the timestamps of the not
        recovered logbackups). If nothing had been lost, clear the
        logvolume and do a complete backup. Otherwise the
        recovery has to be reeated including the previously not
        recovered logbackups.
        Solution:
        Code-correction: A recover_ignore is only allowed,
        when the logvolume is cleared.


    PTS: 1127627    since: 7.5.00.11

    New Feature:
        First implementation of Table_TempHashTable. Not yet used
        by AK.


    PTS: 1127597    since: 7.5.00.11

    Fixed Problem:
        appearance:
        An alter table statement whichs adds a column with default
        definition fails with error -3007.
        Preconditions and circumstances:
        The statement runs in parse/execute mode.
        Workaround:
        None.
        Solution:
        Fixed the bug in kernel code.


    PTS: 1127538    since: 7.5.00.11

    Fixed Problem:
        appearance:
        During LogRecovery the database performs
        a restart and is unexpectedly online
        Preconditions and circumstances:
        The last recovered LogSegment is not complete.
        I.e. it does not contain a the last written block,
        which holds the EndSaveInfo.
        Workaround:
        Begin the recovery again and skip the defect
        LogBackup. If no other LogBackup contains
        the required LogEntries, then the recovery
        cannot performed.
        Solution:
        code-correction


    PTS: 1127513    since: 7.5.00.11

    Fixed Problem:
        ppearance:
        trunc-error in SQLDBC
        Preconditions and circumstances:
        col (CHAR(n))  LIKE :param and the hostvariable is filled
        with more than (n+1) character
        Workaround:
        do not use more character to compare than are allowed by
        the server
        Solution:
        More additional (wildcard) character are allowed


    PTS: 1127504    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Check data on an HotStandBy instance in mode standby fails
        with error code -104.
        Preconditions and circumstances:
        This could happen only in release 7.5.0.10
        Workaround:
        none


    PTS: 1127492    since: 7.5.00.11

    New Feature:
        Feature description:
        As default new join (nested loop) implementation is
        switched on.


    PTS: 1127489    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Kernel aborts command execution with error code "-9043 BD
        Fdir access not allowed".
        Preconditions and circumstances:
        This could happen if a data base kernel release greater
        than 7.4.03.29 is used and  the optimizer chooses a merge
        strategy on an index as a good strategy. Note that the
        error is a temporay effect and probably could not be
        reproduced. Further on the data base is consistent. No
        recovery is needed!
        Workaround:
        none


    PTS: 1127378    since: 7.5.00.11

    Fixed Problem:
        appearance:
        If iso 1 for select is set and another trans alters the
        table the selector
        holds a sysshare lock which is hold until end of
        transaction.
        But the sysshare lock could be removed after the record was
        fetched.
        Solution:
        Now the sysshare lock is removed directly after reading the
        record.


    PTS: 1127374    since: 7.5.00.11

    New Feature:
        Feature description:
        In a HotStandby configuration the command TakeOver checks
        now if the master is running.
        If so TakeOver is denied.


    PTS: 1127317    since: 7.5.00.11

    New Feature:
        Feature description:
        The migration of the catalog from ASCII to unicode now no
        longer aborts if a view can't be recreated.
        Instead the view will be dropped and its name and
        definition be logged in the table
        'VIEW_UNICODE_MIGRATION_PROT'. The view name will also be
        logged in the file knldiag.
        In case the drop of the view returns an error, the view
        name will be logged in knldiag.err.
        The recreation of comments on database objects is now also
        allowed to fail if the table/view the comment is defined on
        can't be found. Failure of comment recreation will only be
        logged in knldiag.


    PTS: 1127289    since: 7.5.00.11

    Fixed Problem:
        appearance:
        hints on wrong positions in command complains, but should
        be handled as comment
        Preconditions and circumstances:
        usage of hints
        Workaround:
        none
        Solution:
        change syntax analysis


    PTS: 1127170    since: 7.5.00.11

    Fixed Problem:
        appearance:
        During logbackup the pages are checked for consistency. The
        case that
        the IOSequences will not be adjacent is not handled and
        thus not
        recognized as an error.
        Preconditions and circumstances:
        corrupted logvolume
        Workaround:
        do a complete backup in order to begin a new
        backup-history, because
        the corrupted log interupts the backup-history
        Solution:
        code correction


    PTS: 1127120    since: 7.5.00.11

    New Feature:
        Feature description:
        NO REFERENCES is no longer required as drop view option.
        Instead
        the kernel stores the required knowledge in the catalog at
        create view time.


    PTS: 1127029    since: 7.5.00.11

    New Feature:
        Feature description:
        Function isupdatedcolumn is available in update triggers.


    PTS: 1127014    since: 7.5.00.11

    Fixed Problem:
        appearance:
        A recovery of a complete or incremental backup
        returns the error, that the backup-device is already
        attached. Also the label cannot be read.
        Preconditions and circumstances:
        Complete or Incremental recovery fails during
        a precheck, which determines the correctness
        of the used backup. Afterwards the device
        is not alway detached.
        Workaround:
        restart the database
        Solution:
        code correction


    PTS: 1126823    since: 7.5.00.11

    New Feature:
        Feature description:
        The kernel provides a new statement, which rebuilds all bad
        indexes.
        Syntax :
        CREATE INDEX RESTART
        The current user must be the SYSDBA.
        Besides, the new kernel parameter AUTO_RECREATE_BAD_INDEXES
        has been
        introduced. If AUTO_RECREATE_BAD_INDEXES is YES, all bad
        indexes are rebuild
        in the course of the restart automatically.
        Default for  AUTO_RECREATE_BAD_INDEXES is NO.


    PTS: 1126169    since: 7.5.00.11

    New Feature:
        Feature description:
        Messagelists are used for Restart and HotStandby.
        This relates in more informal messages in knldiag and even
        in return packets
        with more detailed error descriptions.


    PTS: 1125942    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Hotstandby: The master could be stopped due to logFull,
        because the standby is to slow
        Preconditions and circumstances:
        Wrong configuration: E.g. the standby-hardware is too slow
        Workaround:
        improve performance of standby or remove it
        Solution:
        Now the master-instance takes not care of how fare the
        standbies has read the log. The master simple writes
        Logpages as it is needed. If the standbys are to slow
        they will be shutdown with an LogError, because the
        log they needed is overwritten. Afterwards the master will
        remove them from his list of active standbys.


    PTS: 1125578    since: 7.5.00.11

    Fixed Problem:
        appearance:
        slow restart on multi gigabyte databases
        Preconditions and circumstances:
        multi gigabyte database
        Workaround:
        wait a bit longer ...
        Solution:
        old code enters the FBM region to mark each data page as
        occupied
        new code implements bulk mode to set all data pages on a
        converter page as occupied with only one FBM region access.
        Restart of Converter is ~25% faster.


    PTS: 1128348    since: 7.5.00.10

    Fixed Problem:
        appearance:
        "Row not found" for COUNT(*) on empty join result set
        Preconditions and circumstances:
        DIAGNOSE OPTIMIZE OPERATOR JOIN = OFF
        DIAGNOSE OPTIMIZE JOIN ONEPHASE = ON
        Workaround:
        DIAGNOSE OPTIMIZE JOIN ONEPHASE OFF


    PTS: 1128316    since: 7.5.00.10

    Fixed Problem:
        appearance:
        Crash in catalog cache
        Preconditions and circumstances:
        Select on a complex view, which was defined with sqlmode <>
        oracle, for the select oracle-mode and
        select-fetch-optmization are used
        Workaround:
        None for R/3, otherwise the select-fetch-optimization
        should be avoided
        Solution:
        The handling of the systemview-record has to be changed.


    PTS: 1127856    since: 7.5.00.10

    Fixed Problem:
        appearance:
        error -9211 System error: KB Stack type illegal (-602 in
        sql mode SAPR3)
        Preconditions and circumstances:
        1. Your current MaxDB version is 7.5.00.08 or 7.5.00.09
        2. Column is part of the primary key and not part of the
        secondary key
        3. Index only strategy  is used by the sql optimizer
        Workaround:
        diagnose optimize aggregation of
        Solution:
        check if only index columns are used in output


    PTS: 1127755    since: 7.5.00.10

    Fixed Problem:
        appearance:
        join select with bad performance and bad join transitions
        Preconditions and circumstances:
        amount of tables and indexes defined on them are high
        Workaround:
        rearrangement of conditions and tables may help


    PTS: 1125354    since: 7.5.00.10

    New Feature:
        Feature description:
        With this change request the kernel is able to address a 2
        GByte datapart in the internal
        command representation.


    PTS: 1127614    since: 7.5.00.09

    Fixed Problem:
        appearance:
        -1000,Too many lock requests
        Preconditions and circumstances:
        HotStandby-Environment
        Workaround:
        none
        Solution:
        asking for the current state of restore did not release the
        transaction afterwards


    PTS: 1127357    since: 7.5.00.09

    Fixed Problem:
        appearance:
        emergency shutdown during RESTART with error 8050 no
        converter entry
        rollback of new object during restart may file, because the
        corresponding container has already been dropped.
        Preconditions and circumstances:
        crash of liveCache after calling omsDropSchema while other
        transactions, which created new objects within this schema,
        were still running.
        Workaround:
        there is no workaround
        Solution:
        revover until point in time before omsDropSchema


    PTS: 1127356    since: 7.5.00.09

    Fixed Problem:
        appearance:
        emergency shutdown during restart with following messages
        within knldiag:
        2004-01-21 16:14:19      0x880 ERR     5 Restart  REDO:
        T235522 (rollbacked) redoresult: 4, TrError: 8050
        2004-01-21 16:31:23      0xA3C ERR     8 Admin    ERROR
        'no_converter_entry' CAUSED EMERGENCY SHUTDOWN
        Preconditions and circumstances:
        crash of the livecache shortly after dropping object
        containers
        Workaround:
        not known


    PTS: 1127355    since: 7.5.00.09

    Fixed Problem:
        appearance:
        garbage collectors may enter into endless loop
        Preconditions and circumstances:
        drop of variable object container occured
        Workaround:
        none
        Solution:
        upgrade livecache software


    PTS: 1127352    since: 7.5.00.09

    Fixed Problem:
        appearance:
        After redo records are missing.
        Preconditions and circumstances:
        Redo of aborted redo does not redo a half read logentry.
        If a log recovery is cancelled and there was just half of a
        logentry copied.
        This entry is not again copied if the log recovery is
        started again at this point.
        Workaround:
        Repeat recovery without aborting the log recovery.


    PTS: 1127345    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Low performance of DML operations.
        Preconditions and circumstances:
        Performance is poor, if and only if a db kernel of release
        7.5.00.08 is used.
        Workaround:
        no


    PTS: 1127279    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Rollback of new omsVarObject fails and provokes emergency
        shutdown.
        Following messages are written to knldiag file:
        2004-01-19 17:28:35   261 ERR 53000 OBJECT   bd93new:
        ContFileNo =: 4
        2004-01-19 17:28:35   261 ERR 53000 OBJECT   bd93new:
        ChainNo=: 0
        2004-01-19 17:28:35   261 ERR 53000 OBJECT   bd93new:
        SubRoot=: 49829
        2004-01-19 17:28:35   261 ERR 53000 OBJECT
        bd90RollbackObj invalid_state 'obsReserv
        2004-01-19 17:28:35   261 ERR 53000 OBJECT   ed' found!
        RollbackType:35 OID=126053.68
        2004-01-19 17:28:35   261 ERR 53000 OBJECT   00 (vers 1)
        2004-01-19 17:28:36   261 ERR 51000 OBJECT   omsCommit :
        DbpError 9200
        2004-01-19 17:28:36   261 ERR 11264 DCOM     dispTransEnd:
        Error calling sysRequest - HRESULT: 4900
        2004-01-19 17:28:36   261 ERR 11258 DCOM-DMP mtype: 9
        mtype2: 0
        2004-01-19 17:28:36   261 ERR 11258 DCOM-DMP Drop all
        component objects active on session
        2004-01-19 17:28:42   261 ERR 11258 DCOM-DMP Drop of
        component objects done
        2004-01-19 17:28:42   261 ERR 53000 OBJECT
        bd90RollbackObj invalid_state 'obsReserv
        2004-01-19 17:28:42   261 ERR 53000 OBJECT   ed' found!
        RollbackType:35 OID=126053.68
        2004-01-19 17:28:42   261 ERR 53000 OBJECT   00 (vers 1)
        2004-01-19 17:28:42   261 ERR     8 Admin    ERROR
        'log_error' CAUSED EMERGENCY SHUTDOWN
        Preconditions and circumstances:
        2 transactions, which created omsVarObjects, try to commit
        at the same time and flushing the omsVarObjects needs
        creation of continous container files.
        If both transaction try at the same time to create the same
        continous file, an error could occur provoking the
        emergency shutdown.
        Workaround:
        There is no workaround. But is is very rare, that this
        error occurs. Up till now this error has only been recorded
        once.
        Solution:
        Try to restart livecache. But if restarting fails, you have
        to recover using some point in time before the
        transactions, provoking the error, had been started.
        The other solution is to upgrade the software.


    PTS: 1127261    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Operations which needs server tasks support could not be
        executed, because servertask management is not able to take
        new orders. Return code -1025 "Too many net request" is
        assigned. For example Check data (with update) needs a lot
        of time to examine the data base structure, because each
        -1025 yields to sleep period of one second and after 10
        attempts the utility tasks checks the structure of the
        current file without server task support.
        Preconditions and circumstances:
        Your release is greater or equal to 7.4.3.17 and your data
        base contains blobs which are longer than about 200 KB.
        Workaround:
        Set the configuration parameter _READAHEAD_BLOBS to 200.000
        pages. After the patch is available set the configuration
        sparameter to th eoriginal value.


    PTS: 1127256    since: 7.5.00.09

    Fixed Problem:
        appearance:
        error -28534 "Package must be recreated"  during execution
        of lcinit-script
        Preconditions and circumstances:
        none
        Workaround:
        if restart within LC10 failed you may try to register the
        APO routines using the dbmcli command:
        "exec_lcinit register"
        This second call of the lcinit script normally succeeds and
        the liveCache may be used.
        Solution:
        upgrade to newer build


    PTS: 1127151    since: 7.5.00.09

    Fixed Problem:
        appearance:
        the output for datacache-hitrate differs between dbm-output
        and monitor-output
        Preconditions and circumstances:
        liveCache-environment
        Workaround:
        none
        Solution:
        datacache-hits for dbm-output has to take liveCache-hits
        into account


    PTS: 1127114    since: 7.5.00.09

    New Feature:
        Feature description:
        several parameter/hint/diagnose-switch names renamed
        DB-parameter:
        JOIN_WITHOUT_TEMP_RES --> JOIN_OPERATOR_IMPLEMENTATION
        hints:
        +NEW_JOIN          --> +OPERATOR_JOIN
        +LEGACY_JOIN    -- >+COORDINATOR_JOIN
        diagnose switch:
        DIAGNOSE NEW JOIN ON/OFF --> DIAGNOSE OPTIMIZE OPERATOR
        JOIN ON/OFF


    PTS: 1127100    since: 7.5.00.09

    New Feature:
        Feature description:
        the maximum identifier length in oracle mode is increased
        to 32 (as in internal mode) to allow usage of new
        sysinfo-views, which uses identifier up to 32 character in
        length


    PTS: 1127081    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Livecache crashes with "SAPDBErr Assertion of state transno
        is nil failed!"
        The stack backtrace ends in RemoveHistory().
        Preconditions and circumstances:
        In HistoryFiles the user tasks append their und files and
        must synchronize with
        the garbage collectors which are reading, processing and
        removing these entries.
        The Append operation has accidently released the page lock
        before the undo file info entry was written. If in this
        moment a garbage collector is reading the page contents it
        may happen that
        the GC read inconsistent information which relates to this
        assertion.
        Workaround:
        Persistent structures are valid. So a restart will solve
        the situation.


    PTS: 1127078    since: 7.5.00.09

    Fixed Problem:
        appearance:
        recover_cancel of a log recovery relates to an assertion.
        Preconditions and circumstances:
        A wrong savepoint reason is used for this redo savepoint.
        Workaround:
        No. But recovery can continued as usual.


    PTS: 1127054    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Abort with traceback
        a05identifier_get
        ak660order_by
        a660_query_execute
        Preconditions and circumstances:
        EXPLAIN, UNION in From-select, pars/execute
        Workaround:
        the union and the rest have to be in separate selects
        Solution:
        the internal and too early overwriting of the command
        interface has to be avoided


    PTS: 1127009    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Restart aborts with "Assertion of state
        Rst_IoSeqList::WaitForIoSeq() pNext is nil."
        Preconditions and circumstances:
        If open transactions exist before retart this error might
        occur.
        Workaround:
        You have to use an older datab backup for recovery.


    PTS: 1126975    since: 7.5.00.09

    New Feature:
        Feature description:
        new systemview DIAGNOSE


    PTS: 1126958    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Alter table ... drop primary key may result in a corrupt
        catalog.
        Preconditions and circumstances:
        The key of the table contains a column having a length >
        254 bytes.
        Workaround:
        Don't drop the key via alter table statement. Copy the
        table instead.


    PTS: 1126914    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Functions like decode and some other comparsions accept the
        datatype-compatibility of boolean and
        string_literals/user/usergroup or the like.
        Preconditions and circumstances:
        none
        Workaround:
        none
        Solution:
        The check of compatibility has to be extended for
        string_literals/user/usergoup and the like.


    PTS: 1126831    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Kernel crash when dropping a non-existing named constraint
        via an
        ALTER TABLE T DROP CONSTRAINT CONSTRAINTNAME statement.
        Preconditions and circumstances:
        The table T must possess a referential constraint for the
        error to occur.
        Workaround:
        Do not misspell constraint names or try to drop
        non-existing constraints.


    PTS: 1126826    since: 7.5.00.09

    Fixed Problem:
        a call of a db-procedure containing 2 catalog selects may
        crash the kernel.
        This problem has been solved.


    PTS: 1126814    since: 7.5.00.09

    Fixed Problem:
        appearance:
        -8006 during create dbproc
        Preconditions and circumstances:
        dbproc includes
        - a recursive select
        - with a subquery in the final select and
        - has some parameter in this recursive select
        Workaround:
        Get rid of the subquery in the final select by changing it
        to a join or use two selects, one for reuse, so the result
        can be used in the second's select from-part
        Solution:
        So far the server forgots the parameter information of
        those recursive select-parts not being the final one. Now
        they are not overwritten any more by the parameter
        information of the final select.


    PTS: 1126807    since: 7.5.00.09

    Fixed Problem:
        appearance:
        vabort in ONLINE mode with following messages inknldiag
        file:
        2003-12-30 07:50:21      0xA58 ERR     0 SAPDBErr Assertion
        of state bd91ReleaseUnusedObject failed failed!
        2003-12-30 07:50:21      0xA58 ERR 18196 DBCRASH
        vabort:Emergency Shutdown, Log_History.cpp: 1099
        Preconditions and circumstances:
        omsDropSchema or omsDropContainer has been executed.
        Workaround:
        The only workaround would be to use only exactly 1
        Garbagecollector if feasible.
        The liveCache should be restarted and will be ok.
        Solution:
        upgrade liveCache version


    PTS: 1126804    since: 7.5.00.09

    Fixed Problem:
        appearance:
        knldiag[.err] shows funny (not initialized) character
        behind system error - info
        Preconditions and circumstances:
        unicode-environment
        Workaround:
        none
        Solution:
        end of variable to be output has to be initialized in
        unicode-environment


    PTS: 1126796    since: 7.5.00.09

    Fixed Problem:
        appearance:
        The counters OutOfMemoryExceptions and OMS_Terminate of
        table MONITOR_OMS are
        not updated.
        Preconditions and circumstances:
        A bad alloc exception or are call of omsTerminate happend,
        but MONITOR_OMS does not
        contain any information about this event.
        Workaround:
        None.


    PTS: 1126771    since: 7.5.00.09

    Fixed Problem:
        appearance:
        unicode-data returned non-swapped even for swapped client
        Preconditions and circumstances:
        - shared SQL switched on (this is NOT the default)
        - clients of two different swap-kinds working with one
        database
        - non-swapped client has parsed the statement as the first
        one,
          the swap-client uses the prepared info
        Workaround:
        switch off shared SQL
        Solution:
        swap-kind of clients will be taken into account


    PTS: 1126722    since: 7.5.00.09

    Fixed Problem:
        appearance:
        vabort of livecache with following messages within knldiag
        file:
        2003-12-20 20:00:22    14 ERR 53000 B*TREE
        1600000100000000000000B000000000
        2003-12-20 20:00:22    14 ERR 53000 B*TREE   ROOT  618
        2003-12-20 20:00:22    14 ERR 53000 OBJECT   BD930RemPFDE:
        Error: 720
        2003-12-20 20:00:22    14 ERR 53000 OBJECT
        BD930TryToRelease: Error; 720
        Preconditions and circumstances:
        an OmsKeyedObject container has been created with livecache
        release lower than  72.05.03
        and this container is dropped within a livecache higher or
        equal to 72.05.03
        Workaround:
        Don't drop the container
        Solution:
        use build 24


    PTS: 1126679    since: 7.5.00.09

    New Feature:
        Feature description:
        Timer leap message has been removed


    PTS: 1126675    since: 7.5.00.09

    Fixed Problem:
        appearance:
        -8 parse again
        Preconditions and circumstances:
        error appears if a "from-select" is an join-select with
        aggregate functions and this select is used within another
        join
        Workaround:
        disable "one phase" feature with "diagnose optimize join
        onephase off"


    PTS: 1126671    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Kernel crash in bd20_PutNewIntoLRUList with null pointer
        exception.
        Preconditions and circumstances:
        Could only happen on windows 32 bit architecture with
        enabled  AWE memory extension.
        Workaround:
        Disable AWE.


    PTS: 1126641    since: 7.5.00.09

    Fixed Problem:
        appearance:
        A LogBackup is recovered with recover_replace and returns
        an incorrect returncode -3004 (invalid log backup)
        Preconditions and circumstances:
        A multi-cpu hardware is used and
        the servertasks are configured in a way, that allows
        servertasks to be run in different UKTs. By this the
        tape-read-task and the devspace-write-tasks (aka Log_Reader)
        are running complete asynchronous.
        Workaround:
        Reconfigure the taskcluster that way, that all servertasks
        are running in one UKT
        Solution:
        code correction


    PTS: 1126629    since: 7.5.00.09

    Fixed Problem:
        appearance:
        crash of database during restart
        with following messages within knldiag:
        ==============================
        SIGNAL 4 (ILLEGAL INSTRUCTION) during redo.
        ERR   119 RTE      task 99 called leave(), but region 1 is
        free
        ERR 11196 DBCRASH  vabort:Emergency Shutdown,
        RTESync_RWRegion.cpp: 400
        ERR 11599 BTRACE   ----> Symbolic Stack Back Trace <----
           eo670_CTraceStackOCB
           vabort
           RTE_Crash__FRC20SAPDBErr_MessageList
           leave__16RTESync_RWRegionFbi
           kb511LeaveConsistView
        Preconditions and circumstances:
        database SERVERTASKs are distributed over more than 1 UKT
        Workaround:
        change startup parameters to avoid SERVERTASKs to run in
        different UKTs


    PTS: 1126619    since: 7.5.00.09

    Fixed Problem:
        appearance:
        After cancellation of an event task, the task is
        deadlocking all event producers and database shutdown is
        also blocked, but stopping database still works.
        Preconditions and circumstances:
        An event task must be cancelled during waiting for an event.
        Workaround:
        none
        Solution:
        This patch


    PTS: 1126610    since: 7.5.00.09

    Fixed Problem:
        appearance:
        error -9409 for create table..as select
        Preconditions and circumstances:
        when not using SQLStudio, for example: SAP-environment
        Workaround:
        none in this environment
        Solution:
        Calculation of needed length for the command had to be
        changed


    PTS: 1126572    since: 7.5.00.09

    Fixed Problem:
        appearance:
        In rare cases, the kernel crashes when being stopped.
        The stack backtrace ends in
        RTE_ItemRegister::SearchItemInfo, concerning allocator
        information.
        Preconditions and circumstances:
        Windows only.
        Workaround:
        As the kernel is being stopped anyway, the error can be
        ignored.
        Solution:
        Allocate the task stacks dynamically. So the allocator info
        of a task that has been killed hard by stopping its fiber
        can still be accessed without crashing.


    PTS: 1126558    since: 7.5.00.09

    Fixed Problem:
        appearance:
        The kernel crashed.
        Preconditions and circumstances:
        A complex view select has been used in a db-procedure
        definition, where
        a table in a subselect is unknown.
        Workaround:
        Correct the statement in the db-procedure.
        Solution:
        Missing check of the returncode har been introduced.


    PTS: 1126557    since: 7.5.00.09

    New Feature:
        Feature description:
        The sytem view SESSIONS has been impemented.
        The system view CACHESTATISTICS has been  extended by
        informations about the catalog caches.


    PTS: 1126518    since: 7.5.00.09

    Fixed Problem:
        appearance:
        The datatype-check in ODBC on VARCHAR UNICODE-columns does
        not return the info VARCHAR, only UNICODE
        Preconditions and circumstances:
        no special ones
        Workaround:
        none
        Solution:
        the kernel has to check for internal VARCHAR-flag and
        return the datatype accordingly


    PTS: 1126502    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Restart fails on standby instance
        Preconditions and circumstances:
        This happens with the following procedure:
        - set standby instance to mode standby
        - emergency shutdown of the standby instance
        - try to set standby online because the previous master is
        unavailable
        2003-12-15 20:23:29   118        47 Log      Savepoint
        requested by T106 reason 'Restart' (started).
        2003-12-15 20:23:29    97         4 Pager    SVP(1) Start
        Write Data
        2003-12-15 20:23:41    97         5 Pager    SVP(1) Stop
        Data IO, Pages: 48004 IO: 8565
        2003-12-15 20:23:41    97         6 Pager    SVP(2) Wait
        for last split, TaskId: 85
        2003-12-15 20:23:41    97         7 Pager    SVP(2) Stop
        Wait for last split, Pages: 0 IO: 0
        2003-12-15 20:23:41    14 ERR 11000 devio    write error
        (fd = 27): DEVNO 5 PNO 166296 Size 1 : Bad file number
        2003-12-15 20:23:41    14 ERR    15 IOMan    Access error
        on Log volume 1 blockno 166296:
        2003-12-15 20:23:41    14 ERR    17 IOMan    EMERGENCY
        SHUTDOWN
        Workaround:
        You have to call the support which can edit the loginfo
        page to set the new node as master.
        Solution:
        The restart code checks before opening the log volumes if
        the master is reachable.
        If not the standby becomes master and continues with normal
        restart.
        Now the volumes are opened writable.


    PTS: 1126500    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Too much memory is allocated for R/W lock hash in OMS. Not
        user-perceptible.
        Preconditions and circumstances:
        Always.
        Workaround:
        None.
        Solution:
        Allocate proper amount of memory.


    PTS: 1126313    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Extensive data base filling, which couldn't be explained by
        the results of the tablestatistics. Additional the query
        "select * from roots where type = 'UNKOWN' returns a couple
        of file names, after the system was startet.
        Preconditions and circumstances:
        The asynchron dropping of tables and indexes is interrupted
        by a shutdown. After the next restart nobody proceeds with
        deleting of the remaining auxiliary files in the file
        directoy.
        Workaround:
        Do not stop the data base before the asynchron remove job
        has finished. All server taks should be in state
        vsuspend(211).


    PTS: 1126244    since: 7.5.00.09

    Fixed Problem:
        appearance:
        A restart hangs due to LogFull. Even the RestartSavepoint
        cannot be written, because all reserve-pages has been
        used. A LockBackup as recommended in a log-full-situation
        fails with a log_error caused by a incorrect check
        for logvolume-consistency.
        Preconditions and circumstances:
        No logbackup had ever taken place, so that the first page on
        the log has the Log_IOSequenceNo 0. Also many
        restart-attempts
        had been taken place after LogFull, so that all reserved
        pages
        are used by restart-savepoints.
        Workaround:
        SaveData (optional for security)
        clear the log
        restart
        save data (inorder to begin a new backup-history)
        ensure that in the future log is saved
        Solution:
        code correction


    PTS: 1126207    since: 7.5.00.09

    Fixed Problem:
        Precondition:
        Only index select with min/max function and min/max operand
        is also a function.
        Appearance:
        Wrong result
        Workaround:
        Avoid only index strategy by selecting a non index column
        or dropping the index


    PTS: 1126157    since: 7.5.00.09

    New Feature:
        Feature description:
        The reading of LogPages during restart is from now on done
        not by reading single pages, but by reading blocks of pages
        in order to gain performance. The number of pages in one
        block is determined by the parameter _MULT_IO_BLOCK_CNT


    PTS: 1126143    since: 7.5.00.09

    Fixed Problem:
        not relevant for support and customers


    PTS: 1126131    since: 7.5.00.09

    Fixed Problem:
        appearance:
        - error -8006 during insert
        - error -3019 during select
        Preconditions and circumstances:
        - (-3006) LONG BYTE defined with DEFAULT, the default had
        to be used in this insert, parse/execute       used
        separately
        - (-3019) command used a one-value-subquery whose
        number-value filled the calculated number       length (the
        decimals minus the fractional part), as the constant 1 does
        (fixed (1,0)
        Workaround:
        - use the DEFAULT-value explicitely
        - use a function or some superfluous arithmetic around the
        subquery-value to increase the calculated number of digits.


    PTS: 1126119    since: 7.5.00.09

    Fixed Problem:
        appearance:
        On HP64 the kernel may crash in the course of a
        select from COMMANDSTATISTICS.
        Preconditions and circumstances:
        Unpredictable, depends on stack usage.
        Workaround:
        None.
        Solution:
        Solved alignment problem of an internal structure.


    PTS: 1126112    since: 7.5.00.09

    Fixed Problem:
        appearance:
        The restart aborts with ...
        Preconditions and circumstances:
        If the database crashed an is restarted and a savepoint was
        triggered during redo
        and this savepoint is running just before the end of the
        redo log then log writing is enabled
        and a restart savepoint is triggered. But the previously
        started savepoint is running at first
        an writing to the log volume before the restart savepoint
        was written onto the log volume.
        If a log read must read such log the previously mentiond
        assertion fails because
        after a truncated logentry only the restart savepoint is
        expected.
        Workaround:
        restart without the corrupted log or with until.
        Solution:
        The restart savepoint itself enables log writing so it is
        assured
        that no savepoint during redo may be allowed to write onto
        the log volume.


    PTS: 1126091    since: 7.5.00.09

    Fixed Problem:
        appearance:
        A page is locked in the cache but no task is referencing
        this page.
        Preconditions and circumstances:
        With the new PageAccessManager interface must a page be
        accessed
        and an error must be set like old_fileversion.
        Workaround:
        offline/online releases such page
        Solution:
        The frame is registered to the page handler even in error
        cases
        so the page handler can release the page at the end.


    PTS: 1126057    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Only DES encrypted passwords were accepted.
        Preconditions and circumstances:
        With newer linux versions, standard UNIX DES password
        encryption becomes obsolete. Instead MD5 or blowfish
        encrypted passwords are.
        Workaround:
        NONE
        Solution:
        The salt key transmission is handled more flexible and the
        buffers have been extended to allow generation of larger
        MD5/blowfish encrypted passwords.


    PTS: 1126049    since: 7.5.00.09

    Fixed Problem:
        not relevant for support and customers


    PTS: 1126037    since: 7.5.00.09

    Fixed Problem:
        appearance:
        core with trace back
        a93swap_to_application
        a93_sending
        a93_user_commands +0x0170   (a small number of bytes behind
        start of user_commands)
        ak91run_sql_process
        Preconditions and circumstances:
        in knldiag it can be seen:
        started server, then
        'malloc,....Not enough space'
        Client with different swap-kind than server tries to connect
        Solution:
        Assure that the needed memory for the server is available
        and that no malloc-error will be caused during start-up of
        the server.


    PTS: 1126032    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Kernel crash during "check data with update", if the
        serverdb fullfils the standby role in a hotstandby scenario.
        Preconditions and circumstances:
        Caused by the standby role, the filesystem is restarted.
        The subsequent "check data with update" command starts the
        filesystem again, which always yields to a crash in the
        component FBM.
        Workaround:
        Do not call check data with update for the standby node in
        a hotstandby scenario.
        Solution:
        In the future the standby node could be check only with the
        command "check data", although the serverdb is in redo
        state.


    PTS: 1126002    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Deadlock during savepoint, because the last savepoint
        relevant page could not be written into the data area,
        because this page is still in access by a suspended task,
        which waits until the data cache overflow situation is
        resolved.
        Preconditions and circumstances:
        This could happen, if the data cache is too small and a
        couple of indexes should be created at the same time.
        Workaround:
        - Increase Data Cache size
        - Do not create all indexes at the same time. Create them
        one after another.


    PTS: 1125964    since: 7.5.00.09

    Fixed Problem:
        appearance:
        The kernel crashes in the course of a drop table statement.
        Preconditions and circumstances:
        The table is referenced table of a table having many (> 30)
        foreign keys constraints.
        Workaround:
        Drop the foreign key constraints of the referencing table
        first.
        Solution:
        Corrected scan of foreign key constraints in kernel code.


    PTS: 1125909    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Kernel crash within component FBM, because the block state
        of the first block on the volume should be set to occupied
        twice.
        Preconditions and circumstances:
        This could happen, if a data volume should be added to the
        database in state online.
        Workaround:
        Do not add data volumes in state online.


    PTS: 1125836    since: 7.5.00.09

    New Feature:
        Feature description:
        Integrate parameter
        JOIN_TABLEBUFER_MIN/JOIN_TABLEBUFFER_MAX to
        JOIN_TABLEBUFFER.


    PTS: 1125818    since: 7.5.00.09

    Fixed Problem:
        appearance:
        join via descending index colunm failed
        Preconditions and circumstances:
        join via descending index colunm
        Workaround:
        disable index
        Solution:
        n/a


    PTS: 1125795    since: 7.5.00.09

    Fixed Problem:
        appearance:
        trigonometric function does not return expected value; its
        16-th digit differs
        Preconditions and circumstances:
        none
        Workaround:
        Rounding to 15 digits may help


    PTS: 1125742    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Update triggers are not fired, if just columns of datatype
        long are updated.
        Preconditions and circumstances:
        Columns of datatype long are updated, but no other
        columns are updated.
        Workaround:
        None.
        Solution:
        Save trigger parameters in this case.


    PTS: 1125696    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Endless loop within data cache. You can see that a data
        cache latch is hold by a user task and never being
        released. Additional the kernel consumes a lot of CPU time.
        Preconditions and circumstances:
        The data cache has to be very small and a lot of concurrent
        access should happen for example create index parallel.
        Workaround:
        Increase configuration parameter CACHE_SIZE.


    PTS: 1125632    since: 7.5.00.09

    New Feature:
        Feature description:
        On Unix systems, there may be a maximum file size
        configured by ulimits. If the user tries to access a
        database volume bigger than this maximum file size, error
        occur. To prevent this, the kernel now checks the
        configured volume sizes against the maximum file size
        configured by ulimits and refuses to start if the volume
        size is bigger than the maximum file size.
        Furthermore, the kernel now lists all available ulimts
        during startup.


    PTS: 1125595    since: 7.5.00.09

    Fixed Problem:
        appearance:
        If a row is inserted into a table which is not defined with
        a primary key,
        it can cause a heavy loop if a lock collisions occurs.
        For example if the table was share locked by another user.
        Preconditions and circumstances:
        see above
        Workaround:
        not known
        Solution:
        In a loop:
        If a collision occurs the locklist is used to wait for lock
        release.
        If the collided inserter wakes up it is checked if the key
        exists.
        If not the record is finally inserted and if yes the loop
        begins again with the next higher syskey.


    PTS: 1125316    since: 7.5.00.09

    New Feature:
        Feature description:
        The execution of mass deref commands ( implemented with PTS
        1120478 ) is done in 2 steps.
        1. Step: OIDs are read from the basis
        2. Step: Object data is fetched from the basis
        Both steps may have to scan history to decide if an object
        is seen by an application using a specific 'consistent
        view' to access its data.
        Now step 1 remembers the position within history data, if
        scan of history data had been necessary to decide the
        object to be seen.
        Step 2 uses the history position found by step 1 to
        position directly within history, without scanning thru the
        history chain again.
        The feature is a pure performance option.


    PTS: 1125111    since: 7.5.00.09

    New Feature:
        Feature description:
        not relevant for support and customers


    PTS: 1122278    since: 7.5.00.09

    Fixed Problem:
        Precondition:
        Usage of prepared statements joined with drop and create of
        temp tables.
        Appearance:
        Wrong result at select on temp table.
        Workaround:
        reparse select after drop and create of temp table


    PTS: 1122274    since: 7.5.00.09

    Fixed Problem:
        Precondition:
        Join select with equal condition between a coulmn and a
        constant and constan length is greater than column length.
        Appearance:
        error -2010
        Workaround:
        No


    PTS: 1121056    since: 7.5.00.09

    Fixed Problem:
        appearance:
        error messages during 'CHECK DATA WITH UPDATE' (in ADMIN
        mode) for non-error conditions:
        2003-03-11 18:06:23      0x8AC ERR 53000 OBJECT
        BD92VerObjDataPage - root:74440 page:599
        2003-03-11 18:06:23      0x8AC ERR 53000 OBJECT   94 obj
        pos:4280 committed obj with state
        2003-03-11 18:06:23      0x8AC ERR 53000 OBJECT    reserved
        2003-03-11 18:06:23      0x8AC ERR 53000 OBJECT
        BD92_CheckBeforeImage - before image no
        2003-03-11 18:06:23      0x8AC ERR 53000 OBJECT   t found
        OID 59994.4392 (vers 2)
        Preconditions and circumstances:
        none
        Workaround:
        ignore error messages


    PTS: 1126707    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Kernel crash in data cache because given pageNo is too big.
        Preconditions and circumstances:
        Add data volume in state online has been executed a couple
        of minutes before.
        Workaround:
        Do not add a data volume in state online
        Note that the data base is not corrupted. I can restart it
        and everything is fine.


    PTS: 1125926    since: 7.5.00.08

    Fixed Problem:
        appearance:
        RestartStandby returns OK but later the standby is offline
        because the log does not
        match the data area.
        Preconditions and circumstances:
        Always if standby wants to integrate but log and data is
        not compatible.
        Workaround:
        You can call db_restartinfo before.
        Solution:
        The command RESTART STANDBY now checks everything before
        calling the asybchronous server task.


    PTS: 1125914    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The restart aborts with the following error in knldiag:
        2003-12-03 04:22:33   117 ERR     0 SAPDBErr Assertion of
        state Writer.Write failed failed!
        Preconditions and circumstances:
        In online state the database must crash and be restarted.
        Later a recovery is done which reads the log from the crash
        time.
        Workaround:
        none
        Solution:
        The coding error is solved.


    PTS: 1125830    since: 7.5.00.08

    Fixed Problem:
        appearance:
        A restart of the database fails with the message
        "Savepoint not found on log", because the savepoint-
        offset in the RestartRecord had been calculated
        incorrectly and exceeds the range of the Log_Volume.
        Preconditions and circumstances:
        The savepoint-entry must be contained in a vector of
        LogPages,
        which starts at the end of the LogVolume and wraps around
        to the start of the LogVolume. If the savepoint entry is
        contained
        in the part at the start of the LogVolume, its offset is
        calculated
        incorrectly.
        This situation will occur very seldom, because savepoints
        are
        written not very often. Also the next savepoint will
        correct this
        error.
        Workaround:
        1. Possibility: Save Log and full recovery
        2. Possiblity: Patch the restartRecord. The offset of the
        savepoint
        has to be set to "savePointOffset MODULO LogSize".
        Solution:
        code correction


    PTS: 1125807    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Emergency shutdown because of error code -9013 or -9014.
        Preconditions and circumstances:
        The b*tree structure could corrupt, if an error occur
        during an update operation on the b*tree and a savepoint
        takes place before the emergency shutdown - caused by the
        error - is executed.
        Workaround:
        no


    PTS: 1125799    since: 7.5.00.08

    Fixed Problem:
        appearance:
        kernel crashes with message "kb560DeleteLogTransaction:
        pointer not valid"
        in knldiag.
        Preconditions and circumstances:
        Due to an internal error no Log_Transaction had been
        allocated for
        this session, but it is tried to delete it afterwards.
        Workaround:
        restart the kernel and repeat the failed command
        Solution:
        Change implementation


    PTS: 1125759    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The standby node in a hot standby system restarts and fails
        while
        trying to write onto the log.
        Preconditions and circumstances:
        see above.
        Workaround:
        no
        Solution:
        The standby node waits for first SYNC and it is only a SYNC
        send by the master
        if more then one page was written after last SYNC.


    PTS: 1125682    since: 7.5.00.08

    Fixed Problem:
        appearance:
        RESTART for Master and INIT STANDBY for standby did not
        work.
        Preconditions and circumstances:
        A change in the string handling caused the error that the
        name from loginfo page was compared incorrectly.
        Workaround:
        no
        Solution:
        The string handling was corrected.


    PTS: 1125635    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The kernel crashed in <create function statement>
        Preconditions and circumstances:
        function contains at least one constant expression
        Workaround:
        None.


    PTS: 1125625    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The kernel crashes, if a user defined function without
        parameters is called.
        Preconditions and circumstances:
        The function does not define the result length at copile
        time.
        Workaround:
        None.
        Solution:
        No workaraound available.


    PTS: 1125480    since: 7.5.00.08

    New Feature:
        Feature description:
        The new parameter HS_SYNC_INTERVAL specifies the
        timeinterval in seconds in which the master of a hotstandby
        configuration send a synchronize.
        In a hotstandby configuration the masternode sends
        synchronize commands to the standbynodes.
        The minimum timeinterval between two adjacent synchronize
        commands is defined by the
        parameter HS_SYNC_INTERVAL.
        The synchronize command is initiated by the timeout task.
        This leads to an inaccuracy
        of this parameter, because it is only tested once during
        the runtime of the timeout-task.
        The lower and upper limits are: 0 <= _RESTART_TIME <= 36000


    PTS: 1125413    since: 7.5.00.08

    New Feature:
        Feature description:
        Changes to the internal or support database configuration
        values
          _MAXGARBAGE_COLL
          MAXUKPS
          _TASKCLUSTER_02
        These changes optimize the tasking behavior of the database
        kernel and will provide
        a higher performance..


    PTS: 1125303    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Kernel returns -9044, if an index access was execute with
        an old parse info containing an old file root.
        Preconditions and circumstances:
        Index has to be dropped and recreated and the old root has
        to be the root of a new b*tree.
        Workaround:
        invalidate parse info; restart application


    PTS: 1125288    since: 7.5.00.08

    New Feature:
        With release 7.4.03.02 the empty page chain list has been
        removed form the container implementation ( see PTS 1115760
        ).causing pages to be "deleted" and "re-created" more often
        than in older releases.
        Each object frame on a "created" or "re-created" page is
        initialized with a Oid.Generation set to zero. Therefore
        now it became more likely for an OID of an old obsolete
        persistent object to match an OID for a new created
        persistent object.
        Now the OID.Generation is initialized using a random number.
        But still be aware: OIDs aren't GUIDs. OIDs are unique IDs
        only as long as the object  is alive. After deleting the
        object, the OID may be reused !


    PTS: 1125273    since: 7.5.00.08

    Fixed Problem:
        appearance:
        -7016 during parsing resp. -3016 during execution
        Preconditions and circumstances:
        A statement where the datatype and length of a parameter
        can not defined by the kernel
        as with SELECT * FROM DUAL respectively a bound
        application-variable resulting in a description of
        its datatype and length sent to the kernel which does not
        fulfill the needs of the kernel for this parameter as a
        char-variable does for fixed-column + ?.
        Workaround:
        The bound application-variable should be of the correct
        datatype.


    PTS: 1125214    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Error -9211 System error: KB Stack type illegal at outer
        join selects
        with order by on constant expressions.
        Workaround:
        Rewrite the statement to a from select with order by clause
        where the inner select
        is the outer join, e.g.
        select 4 as prio
        from t1, t2
        where t1.x = t2.y (+)
        order by prio
        =>
        select prio
        from (select 4 as prio
                 from t1, t2
                 where t1.x = t2.y (+))
        order by prio


    PTS: 1125194    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Windows only: Kernel does not start into admin mode with
        message in knldiag.err
        2003-11-04 10:21:12      0x890 ERR 18428 MESSAGES Could not
        open diagnostic file: 'knldiag.evt', rc = 1305
        2003-11-04 10:21:12      0x890 ERR 18152 MEMORY   Could not
        open file 'knldiag.evt', rc = 1305
        Preconditions and circumstances:
        Setting _EVENTSIZE > 0 with valid _EVENTFILE. Default is
        _EVENTSIZE == 0
        Workaround:
        None
        Solution:
        Part of security descriptor used for open call is no longer
        freed before used.


    PTS: 1125115    since: 7.5.00.08

    Fixed Problem:
        appearance:
        An insert into a table x returns error -4004, even though
        the table exists.
        Preconditions and circumstances:
        The insert has been blocked by another transaction. This
        transaction then
        drops and recreates the table. When the first transaction
        continues, error
        -4004 is returned until the catalog cache is purged.
        Workaround:
        Execute a rollback statement to purge the catalog cache.


    PTS: 1125098    since: 7.5.00.08

    New Feature:
        Feature description:
        New option EXTENDED  for CHECK TABLE <tablename>, CHECK
        DATA and CHECK DATA WITH UPDATE commands to check the
        structure of the data base. In contrast to the default
        behaviour of check table and check data the extended mode
        checks the ascending order of the keys in the primary
        (table) and secondary (indexes) data pages. Note that the
        new checks will increase the CPU consumption of the
        participated task and therefore the total runtime will
        increase too.
        Syntax:
        CHECK TABLE <tablename> [WITH SHARE LOCK] [EXTENDED]
            (db state online only)
        CHECK DATA [EXTENDED] WITH UPDATE
                          (db state admin only)
        CHECK DATA [EXTENDED] [EXCEPT INDEX ]
                          (db state online only)


    PTS: 1125036    since: 7.5.00.08

    New Feature:
        Feature description:
        IPC resource problem during backup operation does no longer
        lead to kernel abort, but only to abort of backup operation.


    PTS: 1125033    since: 7.5.00.08

    Fixed Problem:
        appearance:
        There are more resultrows returned than specified using a
        ROWNO/ROWNUM-clause.
        Preconditions and circumstances:
        SELECT with ROWNO/ROWNUM
        +
        correlation used
        Workaround:
        None within one SQL statement. And with more statements the
        ROWNO would be in the last one usually resulting in the
        full resultset in the (last-1) th statement, therefore the
        last one is useless.


    PTS: 1125019    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Drop index fails with error -9205.
        Preconditions and circumstances:
        The index has 16 columns and the index name is longer than
        18 bytes.
        Workaround:
        None.


    PTS: 1125012    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Error -9211 at select with case function in decode function
        Workaround:
        no


    PTS: 1125007    since: 7.5.00.08

    Fixed Problem:
        ppearance:
        no problem seen so far
        Preconditions and circumstances:
        s41plint writes more bytes than needed, may cause
        overwriting of info behind


    PTS: 1124998    since: 7.5.00.08

    Fixed Problem:
        ppearance:
        Crash of kernel without traceback because of stack overflow
        Preconditions and circumstances:
        Linux, 64bit, SQL-command with really many arithmetic
        operations in one expression resp. really many AND/OR-terms
        resp. unusual number of subqueries included. No specific
        values can be given because it depends on the given
        userstack.
        Workaround:
        Separate the statement into at least two.


    PTS: 1124983    since: 7.5.00.08

    New Feature:
        Feature description:
        To reduce the wait time for index updaters, index readers
        will look after every processed index leaf page if an
        exclusive index request exist. If so the index scan is
        interrupted and the exclusive request is executed. After
        the exclusive lock the read access goes on.


    PTS: 1124951    since: 7.5.00.08

    Fixed Problem:
        Core
        appearance:
        ak562do_select_insert
        a562_select_insert
        ak35call_semantik
        Preconditions and circumstances:
        INSERT...SELECT for table having SYSKEY
        Workaround:
        Some DDL (create index, drop index) before trying again.
        Then problem should never occur again


    PTS: 1124886    since: 7.5.00.08

    Fixed Problem:
        Appearence:
        A call of a db-procedure returns error -9205, catalog
        information not found.
        Preconditions and circumstances:
        The execution of a sql statement inside the db-procedure
        fails with -8 and the db-procedure
        has been dropped in the meantime..
        Workaround:
        None.


    PTS: 1124872    since: 7.5.00.08

    New Feature:
        Feature description:
        The event LOG_ABOVE_LIMIT is available.
        Log filling messages are coming now with label "Kernel_E"
        instead of "Log".


    PTS: 1124861    since: 7.5.00.08

    New Feature:
        Feature description:
        Avoid evaluation of file page count for archive tables and
        use best index access for this kind of tables


    PTS: 1124836    since: 7.5.00.08

    Fixed Problem:
        aappearance:
        locks are done according to isolation level valid during
        parse of a command, not on the isolation level (changed
        with set isolation level) valid during execution of the
        command
        Preconditions and circumstances:
        SET ISOLATION LEVEL to a different one than that valid
        during parsing of a command
        Workaround:
        none


    PTS: 1124834    since: 7.5.00.08

    New Feature:
        TRUNCATE will not make an implicit COMMIT afterwards, not
        even in Oracle-mode.


    PTS: 1124826    since: 7.5.00.08

    Fixed Problem:
        Problem:
        The kernel aborts with message in knldiag "Assertion of
        state masternodeidSize is large enough failed"
        Description:
        The internal string handlins is wrong.
        Circumvention:
        You have to use a smaller node name.


    PTS: 1124814    since: 7.5.00.08

    Fixed Problem:
        Appearence:
        more than one outer join
        Preconditions and circumstances:
        access path (index, key) to right outer join table
        Workaround:
        delete access path to right outer join table
        not R/3 relevant


    PTS: 1124800    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Error -3019, -3048 or the like (those checking input-values)
        Preconditions and circumstances:
        call of a dbproc including a declare cursor whose
        cursorname is given as parameter and which includes a join
        and the isolation level differes between creation of dbproc
        and current isolation level
        Workaround:
        No join in the select, no parameter name used for the
        cursorname --> use two selects, one with the join, second
        with no join and the cursorname resp. do the join in the
        from-part of the final select


    PTS: 1124787    since: 7.5.00.08

    Fixed Problem:
        1) circumstances/preconditions for the error-situation
        The kernel tolerates a non-existant medium for
        LogRecovery. In this case he returns from now on
         -903 (Host file I/O error). Before this correction the
        kernel went offline in this error-case.
        2) visibility of the error
        administrator
        3) probability of error-situations
        low
        4) workaround
        not needed.


    PTS: 1124786    since: 7.5.00.08

    Fixed Problem:
        not relevant for support and customers


    PTS: 1124772    since: 7.5.00.08

    New Feature:
        1) It is now also in online-mode possible to save the
        newest
        Page of the LogVolume
        2) Every commit-logentry has now a timestamp. By this
        the commit-time can be exactly evaluated when
        executing a point-in-time-recover
        3) If the youngest page on the LogVolume had been witten
        only
        partially, this page is repared automatically during restart


    PTS: 1124759    since: 7.5.00.08

    Fixed Problem:
        1) Appearance (short description of the problem and how it
        can be realized)
        Create Unique Index returns the error '250 Duplicate
        secondary key' by mistake.
        2) Preconditions and circumstance
        This could happen  if the indexed column(s) contains at
        least to rows which are completely filled with NULL.
        3) Workaround (What can I do or what have I to do, if I use
        an older version and the problem occurred?)
        nothing


    PTS: 1124756    since: 7.5.00.08

    New Feature:
        Feature Description:
        Better performance during task specific memory allocation.
        This is done by the transcontext allocator which will never
        returns the initial memory chunk to the underlying base
        allocator.


    PTS: 1124752    since: 7.5.00.08

    Fixed Problem:
        1) Appearance (short description of the problem and how it
        can be realized)
        Check Data resp. Check Table could fail with error code -8
        2) Preconditions and circumstances
        Concurrent running DDL (Statistic Update) and Check
        Data/Table operation on one tree.
        3) Workaround (What can I do or what have I to do, if I use
        an older version and the problem occurred?)
        Try again.


    PTS: 1124750    since: 7.5.00.08

    Fixed Problem:
        Corrected:
        Rollback of loadercli's fastload results in a corrupt table.
        The table access lets the kernel crash.
        Circumvention:
        You have to recover if the table is corrupted.


    PTS: 1124724    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Error -9205 at alter table add/drop primary key on temp
        tables
        Workaround:
        Define primary key at creation time or use create table as
        select to copy the temp table


    PTS: 1124692    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        CHECK TABLE <tablename> CATALOG has not been able to repair
        corrupted file versions. This has been corrected.
        2) Is it internal or external visible ?
        Internal.


    PTS: 1124680    since: 7.5.00.08

    New Feature:
        The errortext will now be returned even if not in
        online-database-state, therefore avoiding 'Message not
        available'-messages.


    PTS: 1124678    since: 7.5.00.08

    New Feature:
        The full messagelist is now returned to the client, holding
        sometimes info which is more precise than the normal
        errortext.


    PTS: 1124653    since: 7.5.00.08

    Fixed Problem:
        Appearence:
        select <aggregation function> into :var fom <join>
        Preconditions and circumstances:
        optimizer decides for join strategy


    PTS: 1124641    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        SELECT .. FROM DOMAIN.COLUMNS for a non-updatable joinview
        returns values <> NULL in the keypos column. This is wrong
        since these view don't have a key.
        2) Is it internal or external visible ?
        Both.
        3) Propability that the error occurs
        High.
        4) Is there a WorkAround and how does this work ?
        No.


    PTS: 1124633    since: 7.5.00.08

    New Feature:
        INSTANCE_TYPE does not allow BW, CS, EMERGE any more


    PTS: 1124629    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Very strange optimizerstatistics values for small tables
        after update stat estimate commands
        Workaround:
        use update stat command without estimation


    PTS: 1124611    since: 7.5.00.08

    New Feature:
        Feature description:
        introduce new parameter JOIN_WITHOUT_TEMP_RES
        JOIN_WITHOUT_TEMP_RES switch on new join implementation
        (new join is a prototyp implementation, experimental state!
        )


    PTS: 1124553    since: 7.5.00.08

    Fixed Problem:
        not relevant for support and customers


    PTS: 1124543    since: 7.5.00.08

    Fixed Problem:
        RESTART never terminates
        during restart one servertask is suspended waiting within
        "delfile" (status shown by console) and is never resumed.
        1) Preconditions and circumstances
        liveCache crashes after dropping a container.
        2) Is it internal or external visible ?
        both
        3) Propability that the error occurs
        rare
        4) Is there a WorkAround and how does this work ?
        Try to RESTART after configuring more than 1 garbage
        collector. Sometimes it's sufficient to RESTART with
        tracing enabled.


    PTS: 1124526    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Long running update stat commands
        Precondition:
        Sample rate at update stat command was given as percentage
        from table, explicite or implicit via table attribute.
        Workaround:
        Give sample rate of the table in rows instead of percent.
        Also take care of sample rate in table description (see
        system table tables)


    PTS: 1124520    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Tableextract on a table with at least 2 key columns and one
        long column result in kernel core
        Workaround:
        Usage of dataextract


    PTS: 1124491    since: 7.5.00.08

    Fixed Problem:
        miscellaneous
        Appearance
        After DELETE <tablename> without WHERE-clause the resultcnt
        is set to -1, not the the number of deleted rows
        Preconditions and circumstances
        No Foreign key defined for that table which has to be
        checked
        Workaround
        no real one except SELECT COUNT(*) FROM <tablename> before
        doing the delete


    PTS: 1124487    since: 7.5.00.08

    Fixed Problem:
        crash (in slowknl), system error, miscellaneous
        Appearance
        core-trace-back:
           sql__setrang
           g03dfchange_format_date
           g03dchange_format_date
           ak48date_time_analyze
           a48get_view_def_string
           a508get_definition_text
        -8
        datatype NULL
        Preconditions and circumstances
        core:
        when select .. from viewdefs is called and the
        viewdefinition includes a date(internal)-value, the current
        sqlmode is oracle or the date_and_time_format <> internal
        -8 : SELECT .. FROM DBTIMES
        datatype : SELECT .. FROM COLUMNS WHERE tablename =
        'DBTIMES'
        Workaround
        none


    PTS: 1124477    since: 7.5.00.08

    Fixed Problem:
        miscellaneous
        Appearance
        possible, not seen so far:
        -9206 System error: AK Duplicate catalog information
        Preconditions and circumstances
        currently a new table/view is created, leading to the error
        mentioned above after a create table...as select was done,
        which resulted internally to an old fileversion, was
        therefore retried, succeeded, but used an arbitrary
        surrogate, which now should be used (again) or the create
        table..as select tries to 'reuse' that surrogate
        (identification) because of its missing
        surrogate-initialization
        Workaround
        none


    PTS: 1124464    since: 7.5.00.08

    Fixed Problem:
        0) Releases
        UNIX only
        1) Preconditions and circumstances
        If the kernel stack is completely corrupted, the stack
        backtrace routine may not be able to produce a symbolic
        stack backtrace while a emergency stack backtrace is still
        possible. If during emergency stack backtrace a SIGSEGV
        occured, the symbolic stack backtrace would still be
        possible.
        In such a situation the trace writer task may not terminate
        too,
        leading to the wrong message 'Kernel exited normal'.
        2) Probability that the error occurs
        should not happen
        3) Solution to the problem
        An internal SIGSEGV handler is installed during stack
        backtrace that allows the symbolic stack backtrace up to
        the last level before the SIGSEGV occures. The hangup
        situation of the kernel is detected and leads to the
        correct message 'Kernel exited due to SIGHUP'.
        4) Visibility
        low
        5) Workaround
        The addresses in the emergency stack backtrace can be
        analyzed with a local debugger, if installed. The addtional
        message 'Backup of diagnostic files will be forced at next
        restart'
        proves that the kernel did existed normal.


    PTS: 1124400    since: 7.5.00.08

    New Feature:
        Feature description:
        to turn off this new feature we can use
        DIAGNOSE OPTIMIZE ONEPHASE ON/OFF


    PTS: 1124384    since: 7.5.00.08

    Fixed Problem:
        miscellaneous
        Appearance
        Error -4003 unknown user
        Preconditions and circumstances
        ALTER PASSWORD <user> <password>
        +
        <user> is given as special identifier (with "...")
        Workaround
        If possible, avoid " in that case, otherwise, there is no
        workaround


    PTS: 1124376    since: 7.5.00.08

    Fixed Problem:
        Redo/undo of "update record" not done if this transaction
        was open in last savepoint. This can relate to errors like:
        "-3007,Invalid sequence of DML and DDL statements"


    PTS: 1124332    since: 7.5.00.08

    Fixed Problem:
        1) Appearance (short description of the problem and how it
        can be realized)
        Completely wrong estimated optimizer statistics after short
        run time.
        2) Preconditions and circumstances
        Update statistics will estimates completely wrong results,
        if the given table contains a couple of GB.
        3) Workaround (What can I do or what have I to do, if I use
        an older version and the problem occurred?)
        You can set the sample rate to 100%. This will increase the
        runtime, because the entire table will be examined. Do not
        forget to set it back to its default once you have
        installed a database version fixing this bug.


    PTS: 1124331    since: 7.5.00.08

    New Feature:
        Feature Description:
        Tasks will be suspended, if the number free pageNo's is
        nearly exhausted. This will be the same behaviour known
        from the component FBM. The security area is about four
        percent of the data area, but not more than 4.000 pages.


    PTS: 1124329    since: 7.5.00.08

    New Feature:
        Feature Description:
        Create Index sequential is checking the data base filling
        before a new index record is inserted. This is important to
        guarantee that the index creation will stop (suspend) and
        not abort, if the data base is nearly full.


    PTS: 1124326    since: 7.5.00.08

    Fixed Problem:
        1) Appearance (short description of the problem and how it
        can be realized)
        Kernel crash during SQL Connect via DBM, if the data base
        has no free pageNos.
        2) Preconditions and circumstances
        Data base has to be full. See knldiag for DB Full messages0
        3) Workaround (What can I do or what have I to do, if I use
        an older version and the problem occurred?)
        no


    PTS: 1124318    since: 7.5.00.08

    New Feature:
        New neutral icons for several program files.


    PTS: 1124317    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        A warning or error message does not create a kernel event.
        2) Probability that the error occurs
        100%
        3) Solution to the problem
        The missing event generation function was implemented.
        4) Visibility
        low
        5) Workaround
        none


    PTS: 1124310    since: 7.5.00.08

    Fixed Problem:
        1) circumstances/preconditions for the error-situation
        When trying to recover a Log-Backup, the first given
        input-tape is the wrong one (e.g. error-code -7075
        current save skipped). Afer changing the tape
        to the right one it is still not possible to start the
        recovery, because the internal error-state has not
        been resetted. Another try will lead to a kernel crash.
        2) visibility of the error
        Administrator
        3) probability of error-situations
        low when information from the backup-history is
        used instead of trial and error
        4) workaround
        use the right tapes


    PTS: 1124177    since: 7.5.00.08

    New Feature:
        enabled mysql like connection for mysql proxy.


    PTS: 1124163    since: 7.5.00.08

    Fixed Problem:
        Appearence:
        Wrong result set at select on oms_heap_statistics
        Preconditions and circumstances:
        SAP DB release >= 7.4.3.20 with new like behaviour
        Workaround:
        no


    PTS: 1124112    since: 7.5.00.08

    Fixed Problem:
        wrong results, miscellaneous
        Appearance
        Error -3016, -3019 we saw, but others are possible
        Preconditions and circumstances
        Update
        * of a LONG-column +
        * another non-key-column, whose value is not specified
        using a literal or ? or :parameter, but with something that
        has to be calculated (+1, or function around or something
        like that)
        Workaround
        Separate the update of the two columns into two updates


    PTS: 1124101    since: 7.5.00.08

    Fixed Problem:
        RowShareRequests are not satisfied if SysShareLocks exist
        because TabRequests are preferred satisfied and
        if a SysShareLock was removed RowRequests were not
        satisfied.
        Such waiting RowRequests are only removed by the timeout.
        This can only happen if ALTER commands are used.


    PTS: 1124083    since: 7.5.00.08

    Fixed Problem:
        select * from historyinfo sometimes returned wrong values
        for the pagecount if an undo is greater then 32k pages and
        was not removed before the next shutdown/restart.


    PTS: 1124044    since: 7.5.00.08

    Fixed Problem:
        1) Appearance (short description of the problem and how it
        can be realized)
        Data base could be corrupted if save data/pages in mode
        admin and check data with update will be execute
        concurrently. It could happen that pages/blocks will be
        removed although they are still need.
        2) Preconditions and circumstances
        Concurrent running checkdata and data backup operation in
        DB state admin.
        3) Workaround (What can I do or what have I to do, if I use
        an older version and the problem occurred?)
        Do not execute check data with upadte and save data/pages
        ate the same time.


    PTS: 1123988    since: 7.5.00.08

    New Feature:
        not relevant for support and customers


    PTS: 1123957    since: 7.5.00.08

    Fixed Problem:
        system error
        Appearance
        Error -9210 kb stack op illegal
        Preconditions and circumstances
        in case of an EXISTS <subquery> in the select_list (for
        example as part of a case-function)
        Workaround
        Change the SQL-statement, for example do a from-select with
        COUNT(*) (perhaps with ROWNO <=..) and use a CASE/DECODE
        for the count-result as with
        SELECT DECODE (cnt, 0, 'nothing', 'some'),...
        FROM (SELECT COUNT(*) cnt FROM ...) cnttab, ...


    PTS: 1123951    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        Some problems concerning foreing key have been solved:
        1. It was possible to specify the same column twice as
        foreign key
            column of the same referential constraint.
        2. A foreign key could reference itself.
        3. It was possible to drop a default value, even though a
             referential constraint with delete rule 'ON DELETE SET
               DEFAULT'  based on it. This results in error -3007
        when
           a row of the referenced table is to be deleted.
        2) Is it internal or external visible ?
        Both.
        3) Propability that the error occurs
        Low.
        4) Is there a WorkAround and how does this work ?
        No.


    PTS: 1123887    since: 7.5.00.08

    Fixed Problem:
        appearance:
        After recovery of a data backup on a unix system the error
        "no converter entry" occurs.
        What means that not all pages are restored although the
        recovery result was OK.
        The used tape media has no upper limit and is written until
        the device driver signals
        "end of tape reached".
        Preconditions and circumstances:
        On unix systems it is allowed to write less then the given
        blocks.
        Returned is not an error but the real amount of blocks
        which could be written.
        On NT systems an error signals the "end of tape".
        The backup and recovery code assumes that an error is set
        if not all could be written or read.
        Workaround:
        You must specify an upper limit (COUNT) for the tape media.
        Solution:
        After calling vasynio not only the return code must be
        check but the written or read blocksize too.
        The io result is now analyzed correctly.


    PTS: 1123861    since: 7.5.00.08

    New Feature:
        Feature Description:
        CPU utilization through server tasks during save data resp.
        save pages is reduced and therefore the performance of data
        backups is increased.


    PTS: 1123837    since: 7.5.00.08

    Fixed Problem:
        description:
        The repeated restart of an aborted previous restart aborts
        with various errors like "fIter/Assign: inv NxtPno;
        2147483647" or "Assertion of state
        Log_RedoTrafficControl::CheckJobEntry() duplicate index.
        failed!".
        explanation:
        If the redo reader begins at a position from a previous
        restart the last log entry is read and processed again. If
        the last entry is a commit it may happen that a redo task
        and the redo-reader work on the same transaction.
        workaround:
        recover the last data backup and start recovery again.


    PTS: 1123832    since: 7.5.00.08

    New Feature:
        not relevant for support and customers


    PTS: 1123814    since: 7.5.00.08

    Fixed Problem:
        not relevant for support and customers


    PTS: 1123806    since: 7.5.00.08

    Fixed Problem:
        wrong results
        Appearance
        Float-value truncated to fixed-value
        Preconditions and circumstances
        Function having more than one numeric parameter, which have
        to be of equal datatype/length as in
        LEAST, GREATEST, DECODE
        (but not SUBSTR, where some numeric parameters are in)
        +
        the first parameter is a fixed-point-number and one of the
        others is a floating-point-number.
        Workaround
        Try to change sequence of values resp. do some arithmetic
        (division) to force the first parameter to be float (in
        case of decode, where sometime sequence-change is not
        possible)


    PTS: 1123801    since: 7.5.00.08

    Fixed Problem:
        not relevant for support and customers


    PTS: 1123793    since: 7.5.00.08

    Fixed Problem:
        1) Appearance (short description of the problem and how it
        can be realized)
        Data base could crash or hang endless during savepoint
        execution, because data cache pages are not released in a
        correct way.
        2) Preconditions and circumstances
        DDL or DML operation should finish the b*tree  operation
        unsuccessfully and at least one page of the b*tree should
        be set to free.
        3) Workaround (What can I do or what have I to do, if I use
        an older version and the problem occurred?)
        no, but the data base is still consistent!


    PTS: 1123777    since: 7.5.00.08

    Fixed Problem:
        SQL commands, system error
        Appearance
        Error -8
        Preconditions and circumstances
        - unicode-catalog
        - statement-length 4006 (ascii) resp. 8012 (unicode)
        - create table or explain
        Workaround
        Add at least 2 blanks somewhere in the middle of the
        statement.


    PTS: 1123753    since: 7.5.00.08

    Fixed Problem:
        internal only


    PTS: 1123747    since: 7.5.00.08

    Fixed Problem:
        miscellaneous
        Appearance
        The first part or the whole transaction is rollbacked,
        although not rollbacked by the user/application.
        Preconditions and circumstances
        ROLLBACK TO <savepoint_name> which resulted in -7065
        SUBTRANS COMMIT/ROLLBACK not allowed without SUBTRANS BEGIN
        Everything in this transaction before this ROLLBACK TO is
        rollbacked.
        Workaround
        Check savepoint_names three times before using them in
        ROLLBACK TO.


    PTS: 1123727    since: 7.5.00.08

    Fixed Problem:
        wrong results, miscellaneous
        Appearance
        Long-columns are empty/blank although string-literal was
        inserted to it.
        Preconditions and circumstances
        Insert was done using an updatable joinview.
        Workaround
        Insert using the primary tables, not the joinview.


    PTS: 1123713    since: 7.5.00.08

    Fixed Problem:
        0) Releases
        Windows only 7.4..4.X and 7.5.0.01
        1) Preconditions and circumstances
        The system shutdown does not lead to an automatic shutdown
        of the still running databases. Instead the kernel waits
        forever
        until it is disrupted by the OS kernel.
        2) Probability that the error occurs
        100%
        3) Solution to the problem
        The service manager SHUTDOWN event is handled differently
        now. Thas allows the sdb kernel not to spawn a 'dbmstop'
        command for shutdown, but to trigger an internal task.
        4) Visibility
        low
        5) Workaround
        make sure the databases are all offline before shutting
        down the system.


    PTS: 1123701    since: 7.5.00.08

    Fixed Problem:
        1) circumstances/preconditions for the error-situation
        The Log is saved online and manually (i.e. autolog is not
        affected). The LogSave is then aborted due to an error (e.g.
        filesystem full).
        Then the next connect to the database will lead to an
        crash.
        2) visibility of the error
        everybody
        3) probability of error-situations
        low
        4) workaround
        use autolog


    PTS: 1123691    since: 7.5.00.08

    Fixed Problem:
        wrong results
        Appearance
        digits (123000) results in '000123'
        Workaround
        in many cases function CHR will help


    PTS: 1123675    since: 7.5.00.08

    Fixed Problem:
        After RESTORE LOG CANCEL (recover_cancel) an ongoing
        restore log terminates with -3008.
        workaround:
        The recovery had to begin again with recover data and cancel
        must be avoided.


    PTS: 1123664    since: 7.5.00.08

    Fixed Problem:
        crash, SQL commands
        Appearance
        Core vak05.p', Line: (around 17000), dereferenced pointer
        is nil with trace back
        a05password_get
        ak21_alter_create_user_semantic
        Preconditions and circumstances
        unicode-database
        +
        CREATE USER/ALTER USER with no password specified.
        Workaround
        Correct the statement and do not forget to write the
        password.


    PTS: 1123653    since: 7.5.00.08

    Fixed Problem:
        After loading a table this table has the state readonly.
        If a row is tried to insert this causes a log error and if
        the transaction rollbacks the database aborts.
        The error read_only is ignored now during undo and redo.


    PTS: 1123647    since: 7.5.00.08

    Fixed Problem:
        system error
        Appearance
        -9005 System error: BD Illegal key
        Preconditions and circumstances
        <set_function> (DISTINCT <value_expression>) where the
        internal length of <value_expression> (the maximum
        definition-length+1) is > 1024
        Workaround
        <set_function> (DISTINCT SUBSTR(<value_expression>,1,1023))
        in case of a ascii/byte-column,
        <set_function> (DISTINCT SUBSTR(<value_expression>,1,511))
        in case of a unicode-column


    PTS: 1123617    since: 7.5.00.08

    Fixed Problem:
        internal only


    PTS: 1123561    since: 7.5.00.08

    Fixed Problem:
        1) category: Performance
        2) appearance:
        explain <join select> with predefined join sequence shows a
        cheaper cost value as a computed sequence
        3) precondition:
        join sequence search level = 9
        4) workaround: none


    PTS: 1123552    since: 7.5.00.08

    Fixed Problem:
        system error
        Appearance
        -9205 System error: AK Catalog information not found:
        xxxxxxxxxxxxxxxx0060  (x being any hex-digit), other errors
        are possible, too
        Preconditions and circumstances
        FETCH or SELECT on LONG-column, LONG-column-surrogate
        ending with hexadecimal '00' because inserted using an
        insert with functions
        Workaround
        none, the LONG-value is lost and has to be updated


    PTS: 1123062    since: 7.5.00.08

    Fixed Problem:
        Precondition:
        diagnose monitor parseid was enabled and then switched off
        Appearance:
        system view running_commands shows outdated entries
        Workaround:
        No


    PTS: 1122961    since: 7.5.00.08

    Fixed Problem:
        various changes to sharedsql for problem solving.
        especially problem with -8 should be solved


    PTS: 1121318    since: 7.5.00.08

    New Feature:
        Feature Description:
        Kernel is able to freeze the data area and to restore this
        data after a couple of time. This technic will be denoted
        in the future as converter snapshots. For more information
        see the attached doucmentation.


Installation:
=============

    PTS: 1128158    since: 7.5.00.12

    New Feature:
        Feature description:
        Even for old databases (created before autumn 2000) the
        SYSDBA will be NOT EXCLUSIVE to allow usage of DBANALYZER
        resp. parallel usage of R_LOAD/older versions of DBANALYZER


    PTS: 1127967    since: 7.5.00.11

    New Feature:
        Feature description:
        Parameters instance_type, _unicode, default_code and
        date_time_format out of systemview dbparameters can be seen
        by any user.


    PTS: 1126632    since: 7.5.00.09

    New Feature:
        Feature description:
        SDBUPD can be used in batch mode at first update to MaxDB
        with Unix.
        In this case the command line switches -o <sdb user> -g
        <admin group>
        have to be specified.


    PTS: 1126566    since: 7.5.00.09

    New Feature:
        Feature description:
        provide MaxDB rpm packages


    PTS: 1126257    since: 7.5.00.09

    Fixed Problem:
        ppearance:
        Systemview LOCK_WAITS always returns 100 ro not found
        Preconditions and circumstances:
        none
        Workaround:
        use other systemviews concerning LOCKS
        Solution:
        Qualification of LOCK_WAITS had to be changed


    PTS: 1125950    since: 7.5.00.09

    Fixed Problem:
        appearance:
        The installation parameter DEFAULTCODE=internal results in
        EBCDIC-columns
        Workaround:
        use CHAR (..) ASCII resp. UNICODE or specify a
        user-dependant defaultcode (in releases, where this is
        possible)
        Solution:
        The installation will not allow INTERNAL any more


    PTS: 1125931    since: 7.5.00.09

    New Feature:
        Feature description:
        all systemviews do have comments for the views and its
        columns


JDBC:
=====

    PTS: 1129157    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        Using an UPDATE/INSERT command with a different ordering of
        the columns as they were in the
        CREATE TABLE command of the afflicted table, some LONG
        content may not be
        updated or inserted correctly.
        Preconditions and circumstances:
        There must be more than one LONG column, and not all LONG
        data fits in the packet of the
        execute command.
        Workaround:
        Specify the parameters in the order defined for the
        afflicted table by the CREATE TABLE command.
        Solution:
        Longs must be filled in by their position in the data part,
        not by their position in the parameter list.


    PTS: 1129001    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        Error -4004 occurs in conjunction with use of EXPLAIN
        statements without named results.
        Preconditions and circumstances:
        You have to issue EXPLAIN statements and mix them up with
        other SQL, hereby using the same
        java.sql.Statement instances.
        Workaround:
        Use named EXPLAIN statements to uniquely name the result
        sets (EXPLAIN (cursor_name) ... ).
        Solution:
        The cursor name SHOW is never dropped when created by an
        EXPLAIN statement. The cursor
        name SHOW is not used as cursor name for the next statement
        if it was created by an EXPLAIN.


    PTS: 1128970    since: 7.5.00.12

    New Feature:
        Feature description:
        Due to a better performance curors were keeped open until
        the statement was closed or reused. If you have a lot of
        statements opened this may lead to an out of temporary
        space within the database kernel. Therefor a cursor now
        will always closed if ReslutSet.close() is called.


    PTS: 1128440    since: 7.5.00.11

    Fixed Problem:
        appearance:
        The GPL sources of JDBC driver are not compilable due to a
        bug within the ant make script.
        Preconditions and circumstances:
        compile errors are reported
        Workaround:
        none
        Solution:
        update the jdbc source files


    PTS: 1126775    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Content of long column is corrupted after executing an
        insert or an update if more than one long column will be
        inserted and the first long column is of type long unicode
        and the second long column is of type long byte.
        Preconditions and circumstances:
        more than one long column within a statement
        Workaround:
        none
        Solution:
        new JDBC driver is needed


    PTS: 1126651    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Selecting strings from VARCHAR columns that contain only a
        few characters uses an unexpected
        high amount of memory in the Java Virtual Machine.
        Preconditions and circumstances:
        For any VARCHAR(n) column in a result set, a getString()
        returns a string instance having
        an internal buffer with n chars. A lot of space is thus
        waisted if the string is kept.
        Workaround:
        Use 'new String(getString(colindex))' in places where
        appropriate (check for NULL values
        if necessary/applicable).
        Solution:
        Iternally a new String instance is created in case of
        trimming, which results in the use of
        a shorter buffer by the JVM. (The larger buffer is then
        garbage-collected).


    PTS: 1126508    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        ResultSet.getDouble() returns inexact values (e.g.
        5.22500000000005 instead of 5.225).
        Preconditions and circumstances:
        The data type must be a FLOAT or a FIXED having less than
        19 digits.
        Workaround:
        Use at least a  FLOAT(20)  for floating-point numbers in
        the data definition.
        Solution:
        A wrong old conversion method was used.


    PTS: 1126101    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Special null value not handled
        Preconditions and circumstances:
        The special null value will be returned from the database
        kernel if a numeric overflow or division by zero occurs.
        This special null value wasn't handled wasn't handled by
        the JDBC driver.
        Workaround:
        None
        Solution:
        an update of JDBC driver is needed


    PTS: 1124483    since: 7.5.00.09

    New Feature:
        Feature description:
        Access to system properties is know enclosed by an
        exception handler that handles the  AccessControlException.


    PTS: 1125584    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The JDBC API call Blob.getBinaryStream().read() might
        return a wrong value for long byte columns if Blob.length()
        has been used before.
        Preconditions and circumstances:
        You run into this bug if you use
        Blob.getBinaryStream().read() after calling Blob.length()
        and the resultset contains more than one row and the long
        columns are longer than the communication packet size.
        Workaround:
        using Blob.getBinaryStream().read(byte[],int,int) instead
        of Blob.getBinaryStream().read()
        Solution:
        a jdbc driver update is needed


    PTS: 1125518    since: 7.5.00.08

    Fixed Problem:
        appearance:
        a wrong sqlcode -1 will be returned for connection errors.
        Preconditions and circumstances:
        always if a communication problem occurs the sqlcode -1
        will be returned. Sqlcode -708 would be correctly.
        Workaround:
        none
        Solution:
        Now the sqlcode is -708 instead of -1


    PTS: 1125449    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Using IBM JDK 1.3.1 Win32 build cn131-20021107, a
        ClassDefNotFoundError is thrown when
        trying to use the XA Connection or the Pooled Connection.
        Preconditions and circumstances:
        Using IBM JDK 1.3.1 Win32 build cn131-20021107, a
        ClassDefNotFoundError is thrown when
        trying to use the XA Connection or the Pooled Connection.
        Workaround:
        None. A software update is necessary.
        Solution:
        The wrapper method for hiding JDBC 3.0 features
        (java.sql.Savepoint) was added for
        the rollback and releaseSavepoint methods of the connection
        wrapper of the XA/pooled
        connection implementation.


    PTS: 1125082    since: 7.5.00.08

    Fixed Problem:
        appearance:
        When selecting negative FIXED values that are shorter than
        19 digits, an exception may be raised
        that the conversion is impossible.
        Preconditions and circumstances:
        The data value must have less significant (not equal to 0)
        digits after the decimal point,
        than the precision of the FIXED data type that was defined.
        Workaround:
        None, a software update is necessary.


    PTS: 1124635    since: 7.5.00.08

    New Feature:
        Feature description:
        Rebranding MySQL MaxDB


    PTS: 1124496    since: 7.5.00.08

    Fixed Problem:
        Appearence:
        Exception "-8006 Data types must be compatible" in
        DatabaseMetaDataSapDB.getColumns() using the oracle mode.
        Preconditions and circumstances:
        Exception "-8006 Data types must be compatible" in
        DatabaseMetaDataSapDB.getColumns() using the oracle mode.
        Workaround:
        a JDBC update is needed


    PTS: 1123986    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        When using a CallabeStatement or PreparedStatement,
        after an error the buffer for the message is handed out
        twice
        to be used for a new command that is sent to the database.
        So, these two commands write their message into the same
        buffer,
        and send corrupted data to the database. As result, all
        kinds of
        kernel errors may appear (often -3018 or -9405).
        2) Solution to the problem
        A software update is necessary.
        3) Probability that the error occurs
        Rare.
        4) Workaround
        none.


    PTS: 1123772    since: 7.5.00.08

    Fixed Problem:
        Error messages in diagnostic files:
        diagnostic file: none
        Error message: -709
        Appearance:
        Reconnect fails with error -709
        Preconditions and circumstances
        The reconnect within the JDBC driver fails if the xserver
        uses a different port than the standard port 7210.
        Probability that the error occurs
        Always if the xserver uses a other than the default port
        number.
        Workaround
        none, update of the JDBC driver needed.
        Further documentation
        none

ODBC:
=====

    PTS: 1129016    since: 7.5.00.12

    Fixed Problem:
        1) Preconditions and circumstances
        Fetching a long column containung a NULL value via
        SQLGetData. Additionally,
        the ODBC-application does not provide an indicator value
        but NULL within the
        call of SQLGetData.
        2) Solution to the problem
        Install a new ODBC-driver (libsqlod[w].[a|so])
        3) Probability that the error occurs
        In the situation described in 1) 100%.
        4) Workaround
        Do not call SQLGetData providing NULL as the indicator
        variable.
        In general, SQLGetData should always called with a valid
        indicator variable.


    PTS: 1128067    since: 7.5.00.11

    Fixed Problem:
        1) Preconditions and circumstances
        The ODBC-driver can crash due to a memory leak if connect
        handles are
        often reused for SQLConnect/SQLDisconnect.
        2) Solution to the problem
        Install a new ODBC-driver (libsqlod[w].[a|so])
        3) Probability that the error occurs
        Applications which reuse ODBC connect handles can suffer
        from this problem.
        Applications which have only a fixed number of connections
        are not concerned.
        4) Workaround
        Actually there are two leaks. The bigger one can be avoided
        if a connect
        handle is not reused but freed (SQLFreeHandle).


    PTS: 1127971    since: 7.5.00.11

    Fixed Problem:
        1) Preconditions and circumstances
        The ODBC-driver returns errors for catalog functions like
        SQLTables, if connected to DBs 7.5.01 or higher.
        2) Solution to the problem
        Install a new ODBC-driver (sqlod32[w].dll,
        libsqlod[w].[a|so])
        3) Probability that the error occurs
        100% for DBs 7.5.01 ff
        4) Workaround
        none


    PTS: 1127876    since: 7.5.00.11

    Fixed Problem:
        1) Preconditions and circumstances
        The ODBC-driver can crash due to a memory leak if connect
        handles are
        often reused for SQLConnect/SQLDisconnect.
        2) Solution to the problem
        Install a new ODBC-driver (libsqlod[w].[a|so])
        3) Probability that the error occurs
        Applications which reuse ODBC connect handles can suffer
        from this problem.
        Applications which have only a fixed number of connections
        are not concerned.
        4) Workaround
        Actually there are two leaks. The bigger one can be avoided
        if a connect
        handle is not reused but freed (SQLFreeHandle).


    PTS: 1127409    since: 7.5.00.11

    Fixed Problem:
        1) Preconditions and circumstances
        On big endian systems: SQLStatistics does not return all
        information correctly
        and SQLExecDirect does not process "real" Unicode.
        2) Solution to the problem
        Install a new ODBC-driver (libsqlod[w].[a|so])
        3) Probability that the error occurs
        100% on big endian systems.
        4) Workaround
        none (except using only ASCII-DBs)1) Preconditions and
        circumstances
        On big endian systems: SQLStatistics does not return all
        information correctly
        and SQLExecDirect does not process "real" Unicode.
        2) Solution to the problem
        Install a new ODBC-driver (libsqlod[w].[a|so]).
        Now there are two ODBC driver:
         - libsqlod    communicates only in ASCII regardless of the
        DB type
         - libsqlodw communicates in ASCII with ASCII-DBs and in
        UCS2 with Unicode-DBs
        3) Probability that the error occurs
        100% on big endian systems.
        4) Workaround
        none (except using only ASCII-DBs)


    PTS: 1127278    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Integration of ODBC corrections
        Preconditions and circumstances:
        <I have forgotten to enter the preconditions>
        Workaround:
        <I have forgotten to enter the workaround>
        Solution:
        <I have forgotten to enter the solution>


    PTS: 1126726    since: 7.5.00.09

    Fixed Problem:
        1) Preconditions and circumstances
        While processing UCS2 data positions and lengths
        (SQLGetData) are wrong.
        2) Solution to the problem
        Install a new ODBC-driver (sqlod32.dll, libsqlod.[a|so])
        3) Probability that the error occurs
        In case of connecting to a unicode DB and processing long
        data very high.
        Depends of actually performed API-calls
        4) Workaround
        none (except using only ASCII-DBs)


    PTS: 1125845    since: 7.5.00.08

    Fixed Problem:
        appearance:
        If packet encoding UCS2 is used, the SQLGetData() function
        may return invalid long data.
        Preconditions and circumstances:
        Use of UCS2 packet encoding.
        Workaround:
        None.
        Solution:
        Use new ODBC lib.


    PTS: 1125078    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        After a session timeout reparsing a statement results in an
        error.
        E.g. in sqlmode oracle an error can occur by execution of a
        prepared statement.
        2) Solution to the problem
        Install a new ODBC-driver (sqlod32.dll, libsqlod.[a|so])
        3) Probability that the error occurs
        Only if another sqlmode than internal is used and a timeout
        happened between
        preparing and execution of a statement.
        4) Workaround
        increase session timeout


    PTS: 1125009    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        Under Unix, ODBC DSN definitions are not found in
        /etc/odbc.ini
        2) Solution to the problem
        Install a new ODBC-driver (libsqlod.[a|so])
        3) Probability that the error occurs
        For system wide definitions 100%
        4) Workaround
        use user specific DSNs (~/.odbc.ini)


    PTS: 1124584    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        The ODBC driver crashes (e.g. under Solaris 5.6). The crash
        happens within SQLAllocHandle.
        2) Solution to the problem
        Install a new ODBC-driver (libsqlod.[a|so])
        3) Probability that the error occurs
        Other systems than Solaris 5.6 do not seem to suffer from
        this bug.
        4) Workaround
        none
        5) In the new driver, SQLGetFunctions return
        SQL_API_SQLPRIMARY_KEY.


    PTS: 1124580    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        In ODBC 3.0 SQLGetTypeInfo returns wrong values:
          in CREATE_PARAMS "length" is expected instead of "max
        length"
          for SQL_TYPE_[DATE|TIME|TIMESTAMP) the columns
        SQL_DATA_TYPE and SQL_DATETIME_SUB return wrong values.
        2) Solution to the problem
        Install a new ODBC-driver (sqlod32[w].dll, libsqlod.[a|so])
        3) Probability that the error occurs
        100%
        4) Workaround
        if the output of SQLGetTypeInfo is needed, use ODBC 2.0 if
        possible

SQLDBC:
=======

    PTS: 1129155    since: 7.5.00.12

    Fixed Problem:
        appearance:
        Leading spaces should be trimmed from character parameters
        that are converted to numbers.
        Preconditions and circumstances:
        Leading spaces should be trimmed from character parameters
        that are converted to numbers.
        Workaround:
        none
        Solution:
        update of sqldbc needed


    PTS: 1129102    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        Binding a value with a SQLDBC_NULL_DATA as indicator and a
        null pointer for the data
        leads to a crash oro verwritten memory on execute.
        Preconditions and circumstances:
        See above.
        Workaround:
        None, a software update is necessary.
        Solution:
        Some special checks for this case had tro be inserted.


    PTS: 1128376    since: 7.5.00.11

    Fixed Problem:
        appearance:
        The SQLDBC_Connection::cancel method returns the sqlcode
        100 on the error handle and
        a the returncode SQLDBC_NO_DATA_FOUND.
        This is a missbehaviour because the error handle should
        only return real errors.
        Preconditions and circumstances:
        The cancel method was called but no command was active.
        Workaround:
        Ignore the sql code 100 after the cancel call
        Solution:
        A software update is neccessary


    PTS: 1128303    since: 7.5.00.11

    New Feature:
        Feature description:
        For all developers using the new common MaxDB interface
        SQLDBC a software development kit will be available now as
        tarball and also installable via sdbinst.


    PTS: 1127370    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Wrong data was inserted.
        Preconditions and circumstances:
        The application bounds a character parameter with bindParam
        and set the value of the
        lengthIndicator to 0 to insert an empty string into an
        character column.
        Undefined data is inserted into the column because SQLDBC
        interpret an empty string a a
        zero terminated string an calculate the length of the given
        data argument with strlen.
        Workaround:
        None
        Solution:
        A software update is necessary


    PTS: 1125554    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Wrong length returned from truncated UTF8 or UCS2 data.
        Preconditions and circumstances:
        Using bindColumn, getObject with to short outputvalues
        The rowstatus array signals SQLDBC_DATA_TRUNC
        Workaround:
        none
        Solution:
        A softwareupdate is necassary


    PTS: 1125552    since: 7.5.00.08

    Fixed Problem:
        appearance:
        An sql command containing unicode characters should execute
        as an unicode order.
        Preconditions and circumstances:
        - A unicode enabled database and
        - An sql command prepared or executed with encoding type
        SQLDBC_StringEncodingUCS2
        Workaround:
        Use only sql commands with encodingtype
        SQLDBC_StringEncodingAscii.
        Solution:
        A software update is necessary.


    PTS: 1125527    since: 7.5.00.08

    New Feature:
        Feature description:
        A new method SQLDBC_RowSet::getRowStatus is availabe.
          /**
           * @brief Returns the row status array for the last fetch
        call.
           *
           * The row status array describes the state of each row.
        The maximum
           * size of the row status array is given by the
        setRowSetSize().
           * The row status array is filled during the fetch() call.
           * The retuncode of the first row matches to the first
        member of the
           * rowstatus array.
           * @return A pointer to the first element of the row
        status array.
           * @see setRowSetSize(), getRowsAffected
           */
          SQLDBC_DLLEXPORT
          const SQLDBC_Int4 *getRowStatus() const;


    PTS: 1125396    since: 7.5.00.08

    New Feature:
        Feature description:
        The SQL trace logs more informations for the bindParameter
        method


    PTS: 1125188    since: 7.5.00.08

    New Feature:
        Feature description:
        SELECT INTO works now with long columns as INTO-parameter.


    PTS: 1125152    since: 7.5.00.08

    Fixed Problem:
        appearance:
        sqltcp.dll is missing on starting sqlcli or the MaxDBProxy
        Preconditions and circumstances:
        You start an application based on the SQLDBC library.
        Workaround:
        copy the sqltcp.dll to the path pointied by the $PATH
        variable or in the directory where the
        executable of the application is located.


    PTS: 1125084    since: 7.5.00.08

    New Feature:
        Feature description:
        There is a new member function bindColumn() from the class
        SQLDBC_ResultSet with an additional parameter
        PositionIndicator.
        The value of this parameter specifies the start position in
        bytes from which on non-integral data should be deleivered
        into the bound column.
        If this value is negative, the start position is counted
        from the end of the non-integral data.


    PTS: 1125074    since: 7.5.00.08

    New Feature:
        Feature description:
        Added some benchmaktestfiles.
        The Benchmarktest could be made with
        imf ::SAPDB/Interfaces/benchmark.mac
        The results are localted under
         $OWN/test/benchmark


    PTS: 1124805    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        The application fetches data with bindParam or getObject.
        and a wrong value and indicatorlength is retrieved from
        SAPDBC
        2) Solution to the problem
        A Softwareupdate is necessary
        3) Probability that the error occurs
        Always if the 'Size' argument matches the exact length of
        the data returned
        4) Workaround
        Increase the Size Argument with one


    PTS: 1124775    since: 7.5.00.08

    Fixed Problem:
        1) Preconditions and circumstances
        The application crashes if the packet trace is enabled.
        2) Solution to the problem
        A Softwareupdate is necessary
        3) Probability that the error occurs
        Only if the packet trace is enabled and the database
        replies an unknown or newly added part
        4) Workaround
        Disable the packet trace with sqldbc_cons
        or use the databse VTRACE instead for analysis.


    PTS: 1124767    since: 7.5.00.08

    Fixed Problem:
        Appearence:
        Conversion form UCS2 to UTF8 failed
        Preconditions and circumstances:
        Retrieving data with hotvariables of type UTF8 from USC2
        database columns failed.
        Workaround:
        none


    PTS: 1124567    since: 7.5.00.08

    Fixed Problem:
        After executing a prepared named query statement, the
        method getCursorName() of SQLDBC_Statement returns the
        wrong cursor name.
        This error is fixed now.


    PTS: 1124410    since: 7.5.00.08

    Fixed Problem:
        For Windows
        sqlcli and libSQLDBC doesn't need a sqltcp.dll because it
        is
        linked static to these components


    PTS: 1124264    since: 7.5.00.08

    Fixed Problem:
        internal development


    PTS: 1123498    since: 7.5.00.08

    Fixed Problem:
        internal development

Interface Runtime:
==================

    PTS: 1126713    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        The loader hangs when extracting into data files that are
        encoded in UTF8.
        Preconditions and circumstances:
        The code specifier of the output data stream has to be
        UTF8. There must be some character
        in the data that is represented by more than one byte in
        UTF8 encoding.
        Workaround:
        None. A software update is necessary.
        Solution:
        An internal routine copied as much data as possible and did
        not check for the boundaries
        of characters in UTF8 and UCS2 encoding, leading to
        incomplete characters copied. This was corrected.


DBMClient:
==========

    PTS: 1127917    since: 7.5.00.10

    Fixed Problem:
        appearance:
        The transactions DB50 or LC10 report errors accessing the
        database
        via the dbmrfc in a unicode environment.
        A command line call of the dbmrfc produces several errors
        like
            --- Unicode interface [u16_prnt.c line 1911] pid = 2864
        :
            Error in format string at or near '-%211.s2d%
            --- Unicode interface ------ End of message ------
        and ends with a segmentation fault.
        Preconditions and circumstances:
        The dbmrfc runs in a unicode environment with installed ICU
        libraries.
        Workaround:
        Activate the session mode for the dbmrfc.
        Solution:
        This patch will provide a dbmrfc with new libraries from
        the RFC-SDK 6.20 which
        do not contain the error.


    PTS: 1126537    since: 7.5.00.09

    New Feature:
        Feature description:
        The Event Dispatcher now offers the additional feature to
        read user data from the XUSER file when a userkey is passed
        (using switch -U <userkey>).


    PTS: 1126041    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Using the dbmrfc in the transaction LC10 or DB50 will throw
        an "database not found" error.
        Preconditions and circumstances:
        The operating system is UNIX. We saw the problem up to now
        only on HP-UX.
        The database is on the same host like the application
        server.
        The application server is 6.20 or higher.
        Workaround:
        Place a shell script sapdbmrfc.sh in the application server
        exe directory which calls
        the sapdbmrfc executable with all parameters ("sapdbmrfc
        $*") and change
        in the transaction SM59 the entry SAPDB_DBM from sapdbmrfc
        to sapdbmrfc.sh.
        Solution:
        This patch will solve the problem.


    PTS: 1125695    since: 7.5.00.08

    Fixed Problem:
        appearance:
        It is not possible to migrate a database instance to
        installation root with a blank in the path using the
        command db_register with option -R.
        Workaround:
        Use the so called short name for the directory with the ~
        character.
        Solution:
        This patch allows to specify double quotes around the
        installtion root.
        e.g. db_register -R "c:\program file\maxdb\v74"


    PTS: 1125534    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Preconditions and circumstances:
        With the new security concept of 7.5 and 7.6 the option -s
        of the dbmcli will ignored for the most DBMServer commands.
        This refers also to the command db_create.
        Because of this it is not possible with a dbmcli (version
        7.5 or higher) from the independent
        program path to create a database instance with version 7.4
        or lower.
        Workaround:
        Use the dbmcli from the version dependent path.
        Solution:
        Now the dbmcli (7.5 or higher) checks the version which was
        adressed by the -R or -d option.
        If the version is 7.4 or lower the dbmcli will call the
        dbmcli from the version dependent path
        with the same program arguments.


    PTS: 1124761    since: 7.5.00.08

    New Feature:
        An "Event Dispatcher" that can be started manually or
        automatically by the DBMServer (if the DBMServer parameter
        RunEventDispatcher is set to yes), registers on the
        kernel's events (repititive calls of DBM command
        event_wait). It is configured by a description, which so
        called "Event Handler" it should call for each event that
        it receives from the kernel. This description can be
        modified with a text editor.
        The Event Dispatcher can automatically try to reconnect
        after the loss of connection to the kernel.
        Special situations like loss of connection to the kernel,
        crash of the kernel, start and stop of the Event Dispatcher
        itself are made available for Event Handlers through self
        created events.
        An Event Handler to add new data volumes to the db (in
        reaction to a DB_ABOVE_LIMIT event) exists.
        An Event Handler to write any events to the Windows Event
        Log is implemented.
        An Event Handler to write any events to its stdout is
        implemented.
        A default configuration (that activates the handler to add
        new data volumes) is delivered.
        Further documentation: Perforce
        //sapdb/V75/develop/sys/doc/SAPDB/DBM/Cli/Kernel_Eventing.doc


    PTS: 1120748    since: 7.5.00.08

    Fixed Problem:
        Error description
        Because of an old feature dbmcli correct the user key
        DEFAULT if it not conatin the user SAPR3 to the user name
        SAPR3. This feature was implemented to avoid problems with
        unintentionally stored default users.
        This feature is very problematical in MCOD environments
        where the SAP-User is no longer SAPR3 but SAP<SID>.
        Problem Solution
        dbmcli does not overwirte the DEFAULT key. If there is an
        unknown user stored under this key correct the problem with
        xuser.


DBMGUI:
=======

    PTS: 1127722    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        DBM Server crashes during recover_replace.
        Preconditions and circumstances:
        No recover was running before or a previous running restore
        was already finished completely at the time the
        recover_replace is called.
        Workaround:
        Do not call recover_replace without an unfinished restore.
        Solution:
        Use this patch.


DBMServer:
==========

    PTS: 1129198    since: 7.5.00.12

    New Feature:
        Feature description:
        The DBMServer supports now spaces in filenames for the
        commands param_put, param_directput, param_addvolume,
        db_addvolume, file_getfirst, file_getnext, dbm_configset.


    PTS: 1129163    since: 7.5.00.12

    Fixed Problem:
        appearance:
          The DBMServer command backup_start causes a crash of the
        dbmsrv executable.
          The error message is similar to "-4, connection broken".
        Preconditions and circumstances:
          The backup works with an external backup tool and the DBA
        detail protocols
          are active ("dbm_configget DBADTL" shows 1)
        Workaround:
          Disable the DBA detail protocols with "dbm_configset
        DBADTL 0"
        Solution:
          This patch.


    PTS: 1129136    since: 7.5.00.12

    Fixed Problem:
        appearance:
          Using the DBMServer command "exec_lcinit shutdown" will
        not stop the database.
          This happens only sometimes and is not repeatable.
          Because of a operating system problem "x_cons show ..."
        does not work properly.
          The exec_lcinit starts a script lcinit which uses the
        DBMServer command "show state"
          which is based on "x_cons show state".
        Preconditions and circumstances:
          The liveCache server has a UNIX operating system.
        Workaround:
          Use db_offline or repeat the "exec_lcinit shutdown".
        Solution:
          This patch


    PTS: 1128972    since: 7.5.00.12

    New Feature:
        Feature description:
        The command sql_recreateindex supports now the recreation
        of all bad indexes
        with the database statement "CREATE INDEX RESTART".
        For recreation of all bad indexes use the commmand
        sql_recreateindex without
        parameters.
        Also an obsolete fallback to unamed indexes was removed
        which produces
        strange error messages if the command was used with a
        unknonwn or non
        bad index.


    PTS: 1128745    since: 7.5.00.12

    New Feature:
        Feature description:
        DBM Server knows now the command explain, which explains
        other DBM Server commands. For further information use DBM
        Server command explain with parameter explain ("dbmcli ...
        explain explain"). Note that currently not all DBM Server
        commands can be explained.


    PTS: 1128689    since: 7.5.00.12

    New Feature:
        Feature description:
        Backint for SAP DB states the parameters and the return
        code of any Backint for Oracle call it carries out on its
        standard output.


    PTS: 1128682    since: 7.5.00.12

    Fixed Problem:
        appearance:
        The output of Backint for MaxDB, that is delivered with
        MaxDB, is repeating itself, if the output is redirected
        into a file. Such partially duplicated output can be found
        in the files dbm.ebp and dbm.dbl.
        Preconditions and circumstances:
        Operating system is a UNIX and the Backint for MaxDB used
        is the one delivered with MaxDB
        Workaround:
        Ignore the duplicated parts of the output.
        Solution:
        Use this patch


    PTS: 1128623    since: 7.5.00.12

    Fixed Problem:
        appearance:
        The table DBPARAMSINFO does support only 18 characters for
        names of parameters, 5 characters for data types and 64
        character sfor data.
        Solution:
        Now it supports 32 characters for for names of parameters,
        6 characters fpr data types and 256 characters for data.
        Following data types are available: "int", "real"
        (currently not used), "string" and "crypt".


    PTS: 1128552    since: 7.5.00.12

    New Feature:
        Feature description:
        The db_addvolume command is now also available in database
        operational state "admin" if the paramfile ist dirty.
        This avoids problems if the database needs an "add volume"
        but
        can not restart in database operational mode "online".


    PTS: 1128290    since: 7.5.00.12

    New Feature:
        Feature description:
        The DBM Server commands recover_start and recover_check
        have the new parameter "LABEL <label>". If the label
        <label> is not the label of the backup that is recovered or
        checked the recover or the check fail with error
        "-2026,Invalid label".
        Furthermore the DBM Server command autorecover uses the
        backup labels from the backup history, to check if the
        requested backups are restored.


    PTS: 1126239    since: 7.5.00.12

    New Feature:
        Feature description:
        New syntax for DBMServer comand db_create
          db_create [-a] [-u] [-g <group>] <dbname>
        <dbmusr>,<dbmpwd> [<osusr>,<ospwd>]
          -a : (windows only) The "startup type" of the service
        entry becomes the property "automatic".
          -u : (windows only) The "llog on as" property of the
        service becomes the account <osusr>.
          -g <group> : (UNIX only) The database intstance assigns
        the user group <group> to its files.
          <dbname> : Name of the new database instance
          <dbmusr>,<dbmpwd> : Name and   password of the "forst
        database manager operator"
          <osusr>,<ospwd> : Name and password of a existing
        operatings system user for authorization if the db_create
        was sent to a remote server and/or as additional value for
        the -u option.
        New syntax for the DBMServer command db_register
          db_register [-a [OFF]  |  -u OFF  |  -u <osusr>,<ospwd> |
         -g <group>  |  -R <path>]
          -a : (windows only) The "startup type" of the service
        entry becomes the property "automatic".
          -a OFF : (windows only) The "startup type" of the service
        entry becomes the property "manual".
          -u <osusr>,<ospwd> : (windows only) The "log on as"
        property of the service becomes the account <osusr>.
          -u OFF : (windows only) reset the service entry to the
        system account
          -g <group> : (UNIX only) The database intstance assigns
        the user group <group> to its files.
          -R <path> : The database instance becomes this new path
        as dependent software path
        New syntax for hss_addstandby:
          hss_addstandby node=<node> login=<usr>,<pwd>
        [delay=<delay> path=<path> user=yes]
          node=<node> : Node for the new standby database
          login=<usr>,<pwd> : operating system user fro
        authorization (at <node>)
          delay=<delay> : (optional) delay time for the new standby
        database
          path=<path> : (optional) software path at <node>
          user=yes : (optional) (windows only) save user as account
        for service entry
        New semantik for db_addvolume
          A db_addvolume executed by the master instance will add a
        volume with
          the same parameters to all standbys in state STANDBY too.
        If a standby fails
          it will be stopped.


    PTS: 1128063    since: 7.5.00.11

    Fixed Problem:
        appearance:
        The DBMServer hangs on the DBMServer command show or during
        disconnect.
        Preconditions and circumstances:
        Another show command was executed before and not all output
        was delivered
        to the client.
        Workaround:
        The client should fetch all output from the show command
        until the END tag appears.
        Solution:
        This patch will solve the problem.


    PTS: 1127891    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        backup_cancel and backup_ignore repeat the answer of the
        previous backup_start or backup_replace command and the
        external backup log and the external backup protocol files
        contain partially duplicated output of the previous
        backup_start or backup_replace.
        Preconditions and circumstances:
        An external backup tool was used during the previous
        backup_start or backup_replace.
        Workaround:
        Ignore the unexpected command output and the unexpected
        output in the files external backup log (dbm.ebl) and
        external backup protocol (dbm.ebp).
        Solution:
        Use this patch.


    PTS: 1127765    since: 7.5.00.11

    New Feature:
        Feature description:
        Faster end of backup and end of recovery detection for
        backups and recoveries using external backup tools.


    PTS: 1127407    since: 7.5.00.11

    New Feature:
        Feature description:
        New DBMServer command db_activate_req
        Syntax: db_activate_req RECOVER <recovery options>
        For <recovery options> see the documentation of the
        recover_start command.
        The DBMServer command db_activate_req sends only the
        recover command as an request to the
        database instance and returns immediately to the caller.
        The caller may check the availability of an answer from the
        database instance with
        the DBMServer command backup_reply_available and can
        receive the answer
        with the DBMServer command with backup_reply_receive.


    PTS: 1127329    since: 7.5.00.11

    New Feature:
        Feature description:
        The DBMServer command "db_cons" allows now full access to
        the "x_cons" tool
        including the up to now not available subcommand "show".
        The DBMServer command show allows now only access to these
        subcommands
        which the DBMServer returns on the show_list command.


    PTS: 1120370    since: 7.5.00.11

    Fixed Problem:
        appearance:
        The DBMServer answers a recover_ignore with the Return Code
        -8020 and the Recovery Wizard of DBMGUI can not finish a
        restore after a reinitialization of a database successfully.
        Preconditions and circumstances:
        An external backup tool was used during the previous
        restore.
        Workaround:
        Ignore the unexpected -8020 and kill the Recovery Wizard if
        necessary.
        Solution:
        Use this patch.


    PTS: 1127303    since: 7.5.00.09

    Fixed Problem:
        appearance:
        The backup history can not be opened with DBMCLI or viewed
        in DBMGUI.
        Preconditions and circumstances:
        No backup of the database was ever created.
        Workaround:
        Make a backup of the database
        Solution:
        Use this patch.


    PTS: 1127205    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Crash of the Backint for SAP DB/MaxDB implementation
        supplied with SAP DB/MaxDB.
        Preconditions and circumstances:
        You tried to restore files with Backint for SAP DB/MaxDB.
        Workaround:
        Call Backint for Oracle instead of Backint for SAPDB/MaxDB.
        Solution:
        Use this patch.


    PTS: 1126142    since: 7.5.00.09

    New Feature:
        Feature description:
        For the dynmaic parameters (like ARCHIVE_SIZE_?) the
        DBMServer checks now
        the format of hte dynmic portion. If the dynamic porstion
        does not satisfy the
        rules the DBMServer sends a "parameter not found" error.
        The rules are:
        LOG_VOLUME_NAME_<nnn>
        LOG_VOLUME_TYPE_<nnn>
        LOG_VOLUME_SIZE_<nnn>
        M_LOG_VOLUME_NAME_<nnn>
        M_LOG_VOLUME_TYPE_<nnn>
        DATA_VOLUME_NAME_<nnnn>
        DATA_VOLUME_TYPE_<nnnn>
        DATA_VOLUME_SIZE_<nnnn>
        DATA_VOLUME_MODE_<nnnn>
        HS_NODE_<nnn>
        HS_DELAY_TIME_<nnn>


    PTS: 1126065    since: 7.5.00.09

    New Feature:
        Feature description:
        The command dban_state does not generate any error entries
        in the dbm.prt. This will allow
        a try-and-error usage of this command without producing
        protocol.


    PTS: 1125445    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Message "Did not find any stage files." in dbm.ebp and
        dbm.ebl despite existing stage files in the staging area.
        Preconditions and circumstances:
        The database is running on a UNIX.
        Workaround:
        One could try to use very short names for the log backup
        files, e.g. just one character plus the automatically added
        version number. This workaround however depends on the
        alignment and the size of the dirent structure on the
        machine, therefore it depends on the used compiler and it
        may not work on all platforms.
        Solution:
        Install a patch containing this bug fix.


    PTS: 1124796    since: 7.5.00.09

    Fixed Problem:
        appearance:
        During the creation of a database instance with the DBMGui
        it is not possible to set the configuration parameter
        _UNICODE. The error message says "-24968,ERR_XPREADONLY:
        parameter is read only".
        Preconditions and circumstances:
        Creation of a database instance with encoding "unicode"
        with the DBMGui.
        Workaround:
        Create or configure the database instance with dbmcli.
        Solution:
        This patch will solve the problem.


    PTS: 1125994    since: 7.5.00.08

    Fixed Problem:
        appearance:
        After a migration to version 7.5 from lower versions the
        database can not start. There
        are no parameters LOG_VOLUME_SIZE_<nnn>.
        The DBMServer commmand param_getvolsall shows no size for
        the log volume(s).
        Preconditions and circumstances:
        The SAPInst uses in 7.4 ARCHIVE_SIZE_<nn> instead of
        ARCHIVE_SIZE_<nnn>
        for the log volume size.
        Workaround:
        Add manually the correct log volume size
          dbmcli ... param_directput LOG_VOLUME_SIZE_<nnn> <pages>
        for each log volume.
        Solution:
        This patch will migrate ARCHIVE_SIZE_<nn> and
        ARCHIVE_SIZE_<nnn>
        to LOG_VOLUME_SIZE_<nnn>.


    PTS: 1125854    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The output of the DBMServer commands exec_load and
        load_systab contains
        security sensitive data like th password of the domain user
        or the user name and
        password of the default database user of the application
        (the SAP user).
        Workaround:
        Protect the log files against unauthorized access.
        Solution:
        With ths pathc the output does not caontains any more these
        security sensitive data.


    PTS: 1125630    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Using the DBMServer command "db_activate RECOVER ..." with
        the keyword RECOVER
        not completely in uppercases will be produce an error 'ERR
        -24985, ERR_MENOTFOUND: medium not found' even if medium
        exists.
        Workaround:
        Use the keyword RECOVER completely in uppercases.
        Solution:
        This patch solves the problem.


    PTS: 1125618    since: 7.5.00.08

    New Feature:
        Feature description:
        There is now a hidden argument transfer via a pipe
        available if one maxDB programm starts another maxDB
        program. So arguments (like name of user or password) will
        not be shown in the process list of the operating system.
        This argument transfer will be used between the DBMServer
        and the dbanalyzer (DBMServer commands dban_start,
        dban_stop, dban_state).
        Also the dbanalyzer supports now the -U <xuserkey> option
        and the default XUser key "w" for
        the SYSDBA.


    PTS: 1125547    since: 7.5.00.08

    Fixed Problem:
        appearance:
        A DBM operator can not execute the DBMServer command
        exec_lcinit if the user has
        not the right "SystemCmd". Due to a implemnmation failure
        it is not possible to grant this
        this right to the user.
        Preconditions and circumstances:
        The DBM operator was create as user with no rights. Because
        of the implemention failure it is not possible to grant the
        right SystemCmd fro this user.
        Workaround:
        Use the first DBM operator for the command exec_lcinit.
        Solution:
        This patch makes the right SystemCmd grantable again.


    PTS: 1125410    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The dbmserver crashes with a memory access violation.
        Preconditions and circumstances:
        There is a rundirectory with more than 64 characters in the
        configuration.
        Workaround:
        Do not use rundirectory with more than 64 characters.
        Solution:
        This patch is the solution.


    PTS: 1125182    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The DBMServer crashes.
        Preconditions and circumstances:
        The crash appears if there is a open session for log
        recovery when the DBMClient disconnects.
        Workaround:
        Use the command recover_cancel before disconnecting from
        DBMServer.


    PTS: 1125057    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Error "-4 received a garbled packet." during
        archive_stage_repeat.
        Preconditions and circumstances:
        The command archive_stage_repeat is called without any
        prior archive_stage.
        Workaround:
        Always use archive_stage_repeat only after a archive_stage
        in the same DBMServer session.


    PTS: 1125043    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        The DBMServer command archive_stage does not work if the
        verify option (set by default) is used. The file dbm.ebl
        contains the message "The sources differ.", but the
        archived log backup does not differ from the original log
        backup file.
        Preconditions and circumstances:
        The error will most probably occure on UNIX only.
        Workaround:
        Do not use the verify option and verify the archived log
        backups with the help of the DBMServer command
        recover_check.


    PTS: 1124977    since: 7.5.00.08

    New Feature:
        appearance:
        The output of the DBMServer commands exec_load and
        load_systab contains
        security sensitive data like th password of the domain user
        or the user name and
        password of the default database user of the application
        (the SAP user).
        Workaround:
        Protect the log files against unauthorized access.
        Solution:
        With ths patch the output does not caontains any more these
        security sensitive data.


    PTS: 1124661    since: 7.5.00.08

    New Feature:
        Name of "service database instance"
        The name of the service database instance will now computed
        always from the version number. This will avoid problems
        with this
        name because of similar installation keys.
        The name will now computed as
        .M<A><I><CC><BB>
        <A> one digit majow version
        <I> one digit minor version
        <CC> two digit correction leven
        <BB> two digit build number


    PTS: 1124628    since: 7.5.00.08

    New Feature:
        New option -group for db_create
        Syntax:
          db_create [-a[uto]] [-g[roup] <group>] <dbname>
        <dbmusr>,<dbmpwd> [<osusr>,<ospwd>]
        The option -group allows the specification of a user group
        (of the operating system), the so called "support group".
        The DBM sets this group for the UPC file. The kernel reads
        the group from the UPC file and sets it for some of the
        kernel files.


    PTS: 1123657    since: 7.5.00.08

    Fixed Problem:
        1) Category: backup
        2) Error messages in diagnostic files: none
        3) Appearance (short description of the problem and how it
        can be realized):
        A database backup with NetWorker and a file system backup
        with NetWorker happen at the same time. The file system
        backup backs up a part the database backup pipe and
        destroys the database backup.
        4) Preconditions and circumstances: NetWorker is used under
        UNIX
        5) Probability that the error occurs:
        100%
        6) Workaround (What can I do or what have I to do, if I use
        an older version and the problem occurred?)
        Avoid file system backups during backups of the database or
        exclude the pipe directory from file system backups.
        7) Further documentation
        None


    PTS: 1120750    since: 7.5.00.08

    Fixed Problem:
        Problem Description
        Long, long ago there was feature in SAPs main product R/3
        called XDB. XDB was a set of tables and corresponding
        transactions to keep a record of administrative avtivities
        of a database. Newer R/3 installations does not have this
        tables implemented and if the DBM tries to write in this
        tables a error message will be written to the DBM protocol.
        Solution
        With this patch all XDB code was removed from the DBM.
        Workaround
        The command
          dbmcli -d <dbname> -u <usr>,<pwd> dbm_configset SAPXDB 0
        disables the XDB access.

DB Analyzer:
============

    PTS: 1128465    since: 7.5.00.12

    New Feature:
        Feature description:
        The dbanalyzer will now create its views with the system
        attribute.
        The view type will be 'System'.
        This prevents the export of this views during a catalog
        extract.


    PTS: 1126811    since: 7.5.00.11

    New Feature:
        Feature description:
        The following new monitors have been implemented:
        information about
        - long running commands, if a task is processing the same
        command during two snapshots
          and diagnose monitor parseid has been enabled
          * W3  User task 16 processing parseid
        '00001503000018014C000000' last 11 seconds, 251 dispatches,
        application pid 3524
        - number of tables where update statistics is wanted /
        number of bad indexes
          is checked all the time and not during startup only
        - the table names, for which update statistics is required
        (startup only)
          * W1  Number of tables where update statistics is
        required: 1
          * W1  Owner: SAPR3, table: A621
        - number of big tables (> 1.000.000 rows) where the
        sampling rate is set to 20.000
          * W3  145 tables contain more than 1.000.000 records but
        only 20.000 rows will be sampled for statistics
        - existing old consistent views, not only about old oms
        versions
        - the amount of existing history pages is stored in
        DB_FILLING.csv
        - server tasks activities
          *  I  server tasks activity but not for backup.
        Dispatches: 14
          *  I  backup activity: number of pages read 0, written
        2688
        - garbage collection activities
          *  I  Garbage collector tasks activated 18 times,
        currently active: 0, physical reads: 1, avg read time: 4 ms
          *  I  Garbage collection deleted 271 objects and 1473
        history objects, amount of history pages now: 84946
          New file DBAN_GC.csv concerning
        GARBAGECOLLECTOR_STATISTICS
        - Region bottlenecks
          * W1  Number of tasks requesting a region 6
          * W1  6 tasks are waiting for region OMSCDIR owned by
        task 21
          * W3  Region OMSCDIR blocked from task 21 last 7 seconds


    PTS: 1127230    since: 7.5.00.09

    New Feature:
        Feature description:
        For a PARAMETER object exists now the new property
        PROTOCOLINFO.
        This a property may contain a user definied string which
        will be added to
        the protocoll files.
        The string appears in the third line of a protocol file and
        starts (if defined)
        at the third character a column.


    PTS: 1126815    since: 7.5.00.09

    Fixed Problem:
        appearance:
        1.Label for monitors will not shown correctly.
        2. MINVERSION, MAXVERSION and STARTUP properties  for ARRAY
        and PARAMETER
        objects does not wirk correctly.
        Preconditions and circumstances:
        1. Using a array as a calculation result from a array which
        comes from a database table may
        cause this error. The calculated array was not cleaned up
        if a record disappears from the
        source array. Accessing the calculated array in a monitor
        condition will work but with
        old values. Accessing the source array in the label will
        cause a "undefined value" error
        which aborts the label calculation. In this case the name
        of the monitor will be used as label.
        2. The MINVERSION, MAXVERSION and/or STARTUP properties are
        used in the configuration
        file for ARRAY and/or PARAMETER objects.
        Workaround:
        1. Ignore it.
        2. Do not use MINVERSION, MAXVERSION and STARTUP for ARRAY
        and PARAMETER
        objects.
        Solution:
        1. With this patch the dbanalyzer removes the invalid
        records from the calculated arrays too.
        2. MINVERSION, MAXVERSION and STARTUP property will now
        work correctly. All
        internal table objects (created from the TABLE property of
        a ARRAY or PARAMETER
        object) will inherit this properties. So a table which is
        only used by PARAMETER or ARRAY
        objects with the STARTUP property will be only on startup
        read. If there at least one
        PARAMETER or ARRAY object without the STARTUP property for
        a table the will
        be read on every snapshot. The behavior vor MINVERSION and
        MAXVERSION is
        similar. If a ARRAY or PARATMETER object is invalid for a
        database version the
        object does anyway exist but with initial values. It will
        be never filled from the database
        or by a calculation.

Loader:
=======

    PTS: 1129252    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        Running
         'FASTLOAD WITH <N> ROWS USAGE ...'
        with a limited count <M> of rows to load the Loader loads
        all
        rows found in data file if <M> is a multiple of <N>.
        Workaround:
        None
        Solution:
        Use corrected Loader.


    PTS: 1129092    since: 7.5.00.12

    Fixed Problem:
        appearance:
        load user command in a target database  throws  an error
        100 (row not found)
        if the usernames of source and target database differ.
        Preconditions and circumstances:
        ithe error occurs by a transport on userlevel and if the
        usernames of source and target database differ.
        Workaround:
        edit the mapping file that was generated by the extract
        user command.
        replace the first field value ( source username ) by the
        the target username.
        Solution:
        the update data command that modifies the loader
        systemtable data by the mapping file data
        doesn' t qualify the username any more.


    PTS: 1128969    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        When DATAEXTRACT LONG values the Loader may stop with the
        following error:
        // E -25504: Error writing file: '<file name>': OS error:
        [1784].
        Preconditions and circumstances:
        The table to extract the data from has LONG values with a
        length of 2 Bytes or less.
        Workaround:
        None
        Solution:
        Use the new Loader


    PTS: 1128644    since: 7.5.00.12

    Fixed Problem:
        Appearance:
        If one runs the Loader to CATALOGEXTRACT a table with true
        UNICODE identifiers (column names and/or table name) from a
        UNICODE DB the Loader stops with the following error
        message: -25392 ''.
        No more information is given.
        Preconditions and circumstances:
        The Problem is related to the used ODBC driver. Due to an
        error in the driver the connection over ODBC is even to
        UNICODE DBs always made using the ASCII order interface. As
        the name of table is true UNICODE the conversion to ASCII
        fails but the error is not handled.
        Workaround:
        None
        Solution:
        Use the new Loader


    PTS: 1127578    since: 7.5.00.12

    New Feature:
        Feature description:
        It is possible to define the double slash as command
        separator in interactive mode in a way that makes it
        possible to run commands like this:
        'cat loader.prt | loadercli -u <username, password> -d <db
        name> -cs //'.
        Furthermore the Loadercli skips empty lines and lines
        entirely consisting of white spaces and/or control
        characters.


    PTS: 1128434    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Loader always sets the db node to localhost if it is not
        specified in USE USER command; instead it should use the
        node of the last successful connection
        Preconditions and circumstances:
        Loader did not keep the information about the node of the
        last successful connection.
        Workaround:
        Use complete USE USER commands as
        USE USER <user name> <pw> SERVERDB <db name> ON <db node
        name>
        Solution:
        Loader keeps information about the node of the last
        successful connection.


    PTS: 1128281    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        The Loader does not use a default data file format if one
        of the following commands is run: TABLEEXTRACT, TABLELOAD,
        DBEXTRACT, DBLOADa
        Running
        TABLEEXTRACT TABLE <table name> DATA OUTSTREAM FILE '<file
        name>'
        the Loader rerports no error but the created data file
        remains empty.
        The same applies for command TABLELOAD whereas here nothing
        is loaded even if the data file is not empty.
        Running
        TABLEEXTRACT [ USER | ALL ] DATA OUTSTREAM FILE '<file
        name>'
        the Loader reports
        ERR -25109
        Command  not implemented.
        Running
        TABLELOAD [ USER | ALL ] DATA INSTREAM FILE '<file name>'
        the Loader rerports no error but no data is loaded.
        Running DBEXTRACT or DBLOAD the Loader behaves as if
        running TABLEEXTRACT or TABLELOAD [ USER | ALL ]
        Workaround:
        Specify the format in the command to run.
        Solution:
        Loader uses default format PAGES for the above specified
        commands.


    PTS: 1128275    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        TABLELOAD command may time out; Loader returns following
        error message:
        ERR -25009
        Failure in db communication (request): 3 = command timeout.
        Preconditions and circumstances:
        Reason for this timeout is a table created internally by
        the Loader (to retrieve kernel swap behavior) that is
        dropped but not committed. A subsequent select on the
        catalog (save catalog all into <table name>)
        deadlocks with the table drop request.
        Workaround:
        None
        Solution:
        The drop table command is committed.


    PTS: 1128270    since: 7.5.00.11

    New Feature:
        Feature description:
        Loader should not prevent data transport in format PAGES
        between different db versions if the page layouts are
        binary compatible.


    PTS: 1128099    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        If you run the command TABLELOAD with splitted data files
        (more than one data file with extension 0001, 0002, ...) in
        format PAGES the Loader crashes.
        Preconditions and circumstances:
        The crash is caused by a read buffer object that is not
        constructed for every new opened file but reused without
        refreshing the file information.
        Workaround:
        Use the medium PIPE when extracting and loading the data.
        Due to another error the Loader will not create a real pipe
        but a simple file. As this file
        is handled by the Loader internally like a pipe anyway the
        Loader will save the data into one single file.
        Example command:
        TABLEEXTRACT ALL DATA OUTSTREAM PIPE '<pipe name>' PAGES
        //
        TABLELOAD ALL DATA INSTREAM PIPE '<pipe name>' PAGES
        Solution:
        Use corrected Loader


    PTS: 1128012    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        DATAEXTRACTing LONG values FORMATTED into single long files
        per LONG column the Loader saves the position information
        as a string with the length of the long file name instead
        of as a string of length 21 Bytes.
        Preconditions and circumstances:
        None
        Workaround:
        None
        Solution:
        Use corrected Loader.


    PTS: 1127866    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Running a CATALOGEXTRACT command the Loader creates wrong
        CREATE TABLE statements if columns of the extracted
        table(s) have one of the following defaults defined:
        USER, USERGROUP, UTCDATE, UTCDIFF, TIMEZONE, SYSDBA, SERIAL.
        Workaround:
        None
        Solution:
        Use the corrected Loader.


    PTS: 1127829    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        If you CATALOGLOAD a DDL statement whose length exceeds 16
        kB the Loader stops with the following incomprehensible
        error message:
        ERR
        -25392 ''
        The log file then has the following entry:
        CATALOGLOAD TABLE <table name> infile '<file name>'
        // E -25392: ''
        Preconditions and circumstances:
        The Loader has a statement buffer that is too small for
        statements which exceed a length of 16 kB.
        Workaround:
        None
        Solution:
        Use corrected Loader


    PTS: 1127825    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        CATALOGEXTRACT extracts user definitions ordered by user
        names which may lead to errors in recreating those users.
        Preconditions and circumstances:
        Suppose you have the following users:
        - a Superdba user named DBA
        - a user BENCHMARK created by DBA
        - users TPC2 and WISCONSIN created by BENCHMARK
        Extracting the complete catalog of a DB (CATALOGEXTRACT
        ALL) with the above users the Loader would create a file
        with the following content:
        USE USER BENCHMARK initial
        //
        CREATE USER TPC2 PASSWORD INITIAL RESOURCE NOT EXCLUSIVE
        //
        CREATE USER WISCONSIN PASSWORD INITIAL RESOURCE NOT
        EXCLUSIVE
        //
        USE USER DBA <some pw>
        //
        CREATE USER BENCHMARK PASSWORD INITIAL DBA NOT EXCLUSIVE
        //
        ...
        Running this script with 'CATALOGLOAD ALL' the Loader will
        stop with the following error message:
        CURRENT USER BENCHMARK
        // *
        // E -25392: '[MySQL MaxDB][SQLOD32 DLL][MaxDB] General
        error;-4008 POS(1) Unknown user name/password combination'
        Workaround:
        Edit the script.
        Solution:
        Use corrected Loader


    PTS: 1127821    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Running CATALOGLOAD whith DDL-Statements that contain
        non-US7ASCII characters the Loader may stop processing with
        the following error message:
        // E -25392: '[MySQL MaxDB][SQLOD32 DLL][MaxDB] General
        error;-778 Conversion to UNICODE impossible'
        Preconditions and circumstances:
        CATALOGEXTRACT/CATALOGLOAD writes/reads statements as true
        UTF8 strings but opens DDL files as ASCII files.
        Workaround:
        None
        Solution:
        Use corrected Loader


    PTS: 1127801    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Loader stops processing DATALOAD command with the following
        error message if empty LONGs have to be loaded:
         '-25010: "-3014: Invalid end of SQL-Statement"'
        Workaround:
        None
        Solution:
        Use corrected Loader.


    PTS: 1127798    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Loader stops processing DATAUPDATE command on tables with
        compound primary keys with following message: '-25010:
        "-3014: Invalid end of SQL-Statement"'
        if the qualification columns in the command are marked as
        keys like in the following example:
        CREATE TABLE <table name> (col1 int, col2 char(10), col3
        long, primary key (col1,col2))
        DATAUPDATE TABLE <table name>
        KEY col1 1
        kEY col2 2
        SET col3 3
        INFILE '<file name>'
        LONGFILE col3 '<long file name>'
        Workaround:
        Don't use the KEY qualification:
        DATAUPDATE TABLE <table name>
            col1 1
            col2 2
        SET col3 3
        INFILE '<file name>'
        LONGFILE col3 '<long file name>'
        Solution:
        Use corrected Loader.


    PTS: 1127787    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Loader crashes when processing FASTLOAD command to load
        empty values from UCS2 file into UNICODE CHAR columns.
        Workaround:
        None
        Solution:
        Use corrected Loader.


    PTS: 1127582    since: 7.5.00.11

    Fixed Problem:
        Appearance:
        Running
         'FASTLOAD WITH <N> ROWS USAGE ...'
        with a limited count <M> of rows to load the Loader loads
        all
        rows found in data file if <M> is a multiple of <N>.
        Workaround:
        None
        Solution:
        Use corrected Loader.


    PTS: 1127435    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Running
         TABLELOAD TABLE <table name>
        the Loader stops with an incomprehensible error message
        (-25801 Internal error).
        Preconditions and circumstances:
        The table to load has self referencing foreign key(s).
        Workaround:
        None
        Solution:
        The Loader now returns an error message that points to the
        real error like
        // E -25451: Integrity violation (SQL Error 350).


    PTS: 1127412    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Loader did not recognize newline in data if data files were
        in format COMPRESSED or FORMATTED.
        It did instead treat the newline as the end of the actually
        processed data line in file which
        led to unpredictable error messages.
        Workaround:
        No workaround possible if the data was extracted with
        external (non MaxDB) tools. In case the
        data was extracted with the Loader the format RECORDS
        should be used.
        solution:
        The Loader now recognizes newlines in data in the above
        mentioned formats. Furthermore to assure
        the correct handling of newlines in data the Loader doubles
        (thus escaping) delimiters in data
        upon extracting data in format COMRPESSED. The loader
        therefore checks upon loading in format
        COMPRESSED for doubled delimiters in data.


    PTS: 1122591    since: 7.5.00.11

    New Feature:
        Feature description:
        The Loader is version independent. It is always installed
        into the dependent_path/pgm and in the
        independent_program_path/pgm.
        It is assured that clients call the Loader server either in
        - INSTROOT if this is specified (-R option) in the client
        call
        or
        - in indep_program_path in all other cases.


    PTS: 1127248    since: 7.5.00.09

    New Feature:
        Feature description:
        In case of processing FASTLOAD commands the DB kernel
        reports constraint violation to the Loader returning an sql
        error (either one of the following: 300, 320, 350, 360).
        Furthermore the kernel flags the errorneous records with
        negative key lengths in the pages returned to the Loader.
        This information is
        now checked by the Loader and the exactl position of the
        record(s) that violate the contraints is reported.


    PTS: 1126542    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Running a FASTLOAD command into a table where a single row
        spans a single data page the Loader
        looped endlessly.
        The Loader still issues a warning: '25607: Value for usage
        80% to less to fit one record into one database page.
        Ignoring value.'
        Preconditions and circumstances:
        The problem was related to a default USAGE value of 80%
        (filling level of a single database page) which is too
        small to fit a single record.
        Despite the warning the Loader did not ignore the value of
        80%.
        Workaround:
        Use a usage of 99% in the command as in
         FASTLOAD WITH 99% USAGE TABLE <table name> ...


    PTS: 1126534    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        Running a DATALOAD or FASTLOAD command with an empty value
        as DEFAULT NULL value representation for a certain column
        the Loader will in case an empty value is found in the data
        file for that column
        - stop with error message -25319 (Missing data for
        specified column <column name>) if the column to load is
        not of any CHAR data type
        or
        - insert a real empty value instead of NULL value if the
        column to load is of any CHAR data type
        Workaround:
        Instead of using DEFAULT NULL representation use a NULL
        representation for that special column as in
        DATALOAD TABLE <tab name>
        <col name1> 1 NULL IF POS 1 = ''
        ...
        INSTREAM FILE <file name>


    PTS: 1125672    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Loader crashes processing DATALOAD commands if the DB
        kernel returns error for some record and MAXERRORCOUNT is
        set greater than 0.


    PTS: 1125602    since: 7.5.00.09

    Fixed Problem:
        appearance:
        DATAEXTRACTing into a file with wrong path/file name the
        Loader did not catch error when opening that file which
        leads to subsequent error when writing data to that file.
        Example:
        Running the following command with loadercli on a command
        prompt
        DATAEXTRACT * FROM <table name> OUTFILE '<wrong path>/<file
        name>'
        loadercli dropped following message without further
        information:
        ERR
        ---
        Checking the protocol file (loader.prt) one could find the
        following entries:
        // *
        // E -25502:	Error opening file '<wrong path>/<file name>':
        wrong path.
        // E -25505:	Error writing file: '<wrong path>/<file
        name>': Invalid handle.
        // M	Sum of extracted records 0, where 0 records were
        extracted with errors.


    PTS: 1125321    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Loader did not recognize newline in data if data files were
        in format COMPRESSED or FORMATTED.
        It did instead treat the newline as the end of the actually
        processed data line in file which
        led to unpredictable error messages.
        Workaround:
        No workaround possible if the data was extracted with
        external (non MaxDB) tools. In case the
        data was extracted with the Loader the format RECORDS
        should be used.
        solution:
        The Loader now recognizes newlines in data in the above
        mentioned formats. Furthermore to assure
        the correct handling of newlines in data the Loader doubles
        (thus escaping) delimiters in data
        upon extracting data in format COMRPESSED. The loader
        therefore checks upon loading in format
        COMPRESSED for doubled delimiters in data.


    PTS: 1125514    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Loader inserts 'x01' when DATALOADing empty char values
        into UNICODE databases
        Preconditions and circumstances:
        DB is UNICODE
        Workaround:
        None


    PTS: 1124736    since: 7.5.00.08

    New Feature:
        Feature description:
        FASTLOAD is restartable.
        If the Loader encounters errors processing a FASTLOAD
        command (for instance violated key order) it commits all
        data up to the erroneous record. This way the user may
        restart the FASTLOAD processing giving as start record the
        one after the erroneous record.


    PTS: 1124622    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATAEXTRACT command:
        DATAEXTRACTing empty char values in COMPRESSED format
        Loader filled the corresponding fields in the data file up
        to the column length with blanks.


    PTS: 1124619    since: 7.5.00.08

    New Feature:
        Feature description:
        The Loader reuses an already established db connection if
        the same user connects again in a single Loader session.


    PTS: 1124596    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing Loader commands:
        Running an arbitrary Loader command (not SQL) without
        having a db connection the Loader displayed a misleading
        error message
        "// E -25243: Error parsing timestamp mask: Date mask
        incomplete".


    PTS: 1124555    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATALOAD command:
        Running a command like
        DATALOAD TABLE tab
        col1   1-10 DEFAULT NULL
        col2 12-20
        INFILE '<file name>' FORMATTED
        NULL ' '
        with blanks as NULL representation the Loader could stop
        processing with the following error message:
        // M Error at record <N> in infile.
        // E -25302: This value is not a valid number:


    PTS: 1124469    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATALOAD command:
        Loader crashed if DATALOADing data into keyed table with
        LONG columns in case the data to insert contains duplicate
        keys and MAXERRORCOUNT was set to a value > 1.


    PTS: 1124387    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATALOAD command
        Running DATALOAD commands with data files in format RECORDS
        on a table that has LONG columns the Loader would crash.


    PTS: 1124345    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATALOAD and DATAUPDATE commands:
        Loading arbitrary constants with DATALOAD failed.
        Running the command
        DATALOAD TABLE <table name>
        <col name1> <pos>
        <col name2> 'HANS'
        INFILE <infile name>
        the Loader stopped processing with the following error
        message:
        // E -25317: Constant must be compatible with column type
        and length (column: '<col name2>').


    PTS: 1124325    since: 7.5.00.08

    New Feature:
        Loadercli's command separator is djustable with command
        line option cs.
        Setting semicolon as an command separator for batch files
        run
        loadercli -cs ; ...


    PTS: 1124211    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATAEXTRACT FOR DATALOAD commands:
        DATAEXTRACTing FOR DATALOAD LONG values into
        numbered/single LONGFILEs failed if the data file format
        was FORMATTED and the long file name exceeded the length of
        21 characters.
        Running the command
        DATAEXTRACT FOR DATALOAD TABLE testtab OUTFILE
        'testtab.dat' LONGFILE longcol
        'longfilename_longcol.dat######'
        Loader stopped with the following error message where the
        given minimumlength corresponds to the long file name
        length:
        // E -25344: Incorrect field length for column 'LONGCOL',
        minimum length 30.


    PTS: 1124152    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATAEXTRACT commands:
        Running
        DATAEXTRACT * FROM <table name> OUTSTREAM FILE '<data file
        name>' LONGSTREAM FILE '<long file name>' UTF8
        the Loader logged wrong offset information in data file for
        LONG values if those LONG values contained true UTF8
        characters.
        Supposed the LONG value consisted of 1000 true UTF8
        charactes with a length of 2 Bytes each the Loader logged
        1-1000 instead of 1-2000 as offset information.


    PTS: 1124118    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATAEXTRACT commands:
        Running DATAEXTRACTto extract numbers into UTF8 encoded
        data files in format FORMATTED the Loader filled the number
        fields with UCS2 blanks instead of ASCII blanks. This could
        lead to the following error message upon loading the data:
        // M	Error at record <record no> in infile.
        // E -25302: This value is not a valid number:


    PTS: 1123989    since: 7.5.00.08

    Fixed Problem:
        Appearance:
        Setting single quote as separator or delimiter is
        impossible:
        running the command  SET COMPRESSED '/'/,/'  Loader reports
        the following error
        // E -25220: Wrong separator/delimiter specification.
        Preconditions and circumstances:
        None
        Workaround:
        None


    PTS: 1123940    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in command line interface LOADERCLI:
        LOADERCLI crashed if -d option was specified but no db name
        given.


    PTS: 1123937    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing FASTLOAD command:
        FASTLOADing NULL values into UNICODE DBs caused stop of
        processing with internal Loader error
        // E -25801: Internal error [05, 973, -25869]; contact
        technical support


    PTS: 1123875    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATAEXTRACT command:
        Suppose 2 users - A and B - have a table with the same name
        <same table name>. Suppose additionally that user B granted
        all rights on her table to user A.
        If running DATAEXTRACT FOR DATALOAD TABLE <same table name>
        as user A the Loader added the column definitions of  B's
        table to the definition of A's table.


    PTS: 1123751    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATALOAD commands:
        DATALOAD/DATAUPDATE/FASTLOAD commands having DEFAULT NULL
        specification in column definition(s) caused Loader to
        crash if the data file is UTF8 encoded.


    PTS: 1123739    since: 7.5.00.08

    New Feature:
        Report exact error positon of failed SQL statements
        Additionally to the already reported byte error position
        the exact position consisting of line and column numbers of
        the error is reported by the Loader.


    PTS: 1121541    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATALOAD commands:
        Loader misinterpreted NULL representation in UCS2 data
        files as real data but not as NULL.
        Running commands like
        DATALOAD TABLE <table name>
        <col spec> <pos> DEFAULT NULL
        INFILE <infile name> UCS2
        NULL '???'
        the Loader inserted ??? instead of NULL if NULL
        representation found in data file.


    PTS: 1121007    since: 7.5.00.08

    Fixed Problem:
        Fixed bug in processing DATAEXTRACT FOR DATALOAD commands:
        1.Running DATAEXTRACT FOR DATALOAD on a table with LONG
        columns where these LONG values should be saved each in its
        own file (LONG file is numbered) the Loader created an
        extra file. The name of this file still contained the
        placeholders defined in the DATAEXTRACT command like <LONG
        file name>#####.
        2.Running DATAEXTRACT FOR DATALOAD on a table with LONG
        columns where these LONG values should be saved each in its
        own file (LONG file is numbered) as UCS2 the Loader cut the
        name of the LONG files saved in the data file. Thus the
        LONG data could not be loaded.


    PTS: 1118226    since: 7.5.00.08

    Fixed Problem:
        EXTRACT | LOAD Commands using Format Pages are available.

SQL Studio:
===========

    PTS: 1125389    since: 7.5.00.08

    New Feature:
        Feature description:
        SQL Studio will open the version and option dialog without
        starting the main window.


    PTS: 1125384    since: 7.5.00.08

    Fixed Problem:
        appearance:
        SQL Studio throws an index out of bound error when showing
        a result.
        Preconditions and circumstances:
        * select 'a1', 'a2' from dual
        * choose the pop menu of the second column
        * select 'a1' from dual
        Workaround:
        Open an new SQL Window.
        Solution:
        SQL Studio will reinitialise the pop position of the menu
        when displaying a new result.


    PTS: 1125365    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Stored form dialog is not updateable.
        Preconditions and circumstances:
        Open a stored form dialog. It is always read only.
        Workaround:
        Rebuild the stored from dialog.
        Solution:
        SQL Studio will take into account the read only setting for
        the form dialog.


    PTS: 1125178    since: 7.5.00.08

    Fixed Problem:
        appearance:
        If the default value of a column is the string literal
        'Default' assertion fails.
        Preconditions and circumstances:
        If the default value of a column is the string literal
        'Default'.
        Workaround:
        SQL Studio will now work correct. Until the solution is
        available use the domain.columns table to evaluate the
        structure of a table with 'Default'  as default value of a
        column.


    PTS: 1124892    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The image of the splash screen is stretched.
        Preconditions and circumstances:
        Windows setting "large fonts" makes the image of the splash
        screen stretched.
        Workaround:
        Use windows setting "small fonts".
        Solution:
        The splash screen will not stretch the image.


    PTS: 1124803    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Update of the values of a table, which contains a blob
        column, fails.
        Preconditions and circumstances:
        If a key was pressed inside the edit window of a blob
        column the new value is not taken into account.
        Workaround:
        Import the new blob value with the menu "Import Long" and
        don't press any key before update.
        Solution:
        The key press event, which marks a column as dirty, is
        suppressed for blob columns.


    PTS: 1124624    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The displayed definition of a db procedure is not complete.
        Preconditions and circumstances:
        DB procedures with more then 8192 bytes are not displayed
        completely.
        Workaround:
        Select the definition directly from the DOMAIN.DBPROCEDURES
        table.
        Solution:
        SQL Studio will completely display db procedure up to 1 MB.


    PTS: 1124597    since: 7.5.00.08

    Fixed Problem:
        When a table is dropped a second time on the form dialog
        the value from the settings dialog for the read only mode
        is correctly applied.


    PTS: 1124071    since: 7.5.00.08

    Fixed Problem:
        The No Timeout feature of SQL Studio does now work
        correctly.


    PTS: 1123623    since: 7.5.00.08

    Fixed Problem:
        The field for the statistics sample value on the 'table
        definition' dialog is now capable of values up to
        2147483647 (unsigned int).


    PTS: 1123584    since: 7.5.00.08

    New Feature:
        If at least one column of a table is updateable the form
        dialog can be switched to a writeable mode regardless if
        there is a system table or not.


    PTS: 1123399    since: 7.5.00.08

    New Feature:
        The restrictions for tablenames in the catalogview and the
        state of the open folders of the catalogview are now stored
        per connection.


    PTS: 1123390    since: 7.5.00.08

    New Feature:
        The SQLStudio splash screen will be hidden before a connect
        is called from command line.


SQLCLI:
=======

    PTS: 1127936    since: 7.5.00.12

    New Feature:
        Feature description:
        the internal command \dc should not order the columns by
        their name


    PTS: 1127111    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Different syntax errors when running sqlcli in batch mode
        and the command separator is followed by other characters.
        Preconditions and circumstances:
        Using the batch mode and if the command separator is
        followed by other characters.
        Workaround:
        none
        Solution:
        update of sqlcli


    PTS: 1125520    since: 7.5.00.08

    New Feature:
        Feature description:
        - you can now close the current connection using the
        internal command \di[sconnect]
        - the tool asks for a missing password in interactive mode
        - printout the dbname within the command line prompt only
        if the connection is established
        - printout the duration time of a command
        - forward scrolling for resultsets in interactive mode
        - mangle command line to avoid greping the
        username/password from process list
        - beautifying the output:
              - omit the solash screen
              - omit useless empty line before printing the result
        table
              - omit *ok/*not ok messages after finishing a command


    PTS: 1124710    since: 7.5.00.08

    New Feature:
        Feature description:
        SQLCLI supports the same separator as SQLStudio and repmcli
        for commands reads from batchfiles. It is possible to
        configure this separator using the option -c.

WWW Server:
===========

    PTS: 1127294    since: 7.5.00.11

    New Feature:
        Feature description:
        "Transfer-Encoding: chunked" has been implemented.
        "Transfer-Encoding: chunked" is supported by default with
        HTTP 1.1.


    PTS: 1127252    since: 7.5.00.11

    New Feature:
        Feature description:
        Following command line options have been added to the MaxDB
        Web Server
        command line option for wahttp
        -p <port>
        -r <document root>
        -l <og directory>
        -t <max threads>


    PTS: 1127233    since: 7.5.00.11

    New Feature:
        Feature description:
        Persistent connection has been implemented. Persistent
        connection is supported by default.
        But if the client requests a connection with connection
        header "Keep-Alive" persistent connection will be refused,
        due to problems with the MS Internet Explorer and the
        WebTools.


Web DBM:
========

    PTS: 1127524    since: 7.5.00.11

    New Feature:
        The WebDBM has a new Style.


    PTS: 1127342    since: 7.5.00.11

    Fixed Problem:
        appearance:
        The wahttp webserver crashes with a assertion from the
        module Tools_DynamicUTF8String
        if the DBM-Api returns a error message.
        Solution:
        This patch avoids the crash.


    PTS: 1124269    since: 7.5.00.11

    Fixed Problem:
        For database instances greater or equal then 7.5 the
        DBM-Server command "db_activate" must be used in the
        installation process. With this patch the behavior was
        assured.


    PTS: 1123784    since: 7.5.00.11

    Fixed Problem:
        With this patch the right parameters
        (MAXDATAVOLUMES/MAXLOGVOLUMES) are shown in the
        configuration volume page for database instances greater or
        equal 7.5..


WebAgent:
=========

    PTS: 1125537    since: 7.5.00.08

    Fixed Problem:
        appearance:
        on HP platform the WebAgent Administration Service does not
        work properly
        Preconditions and circumstances:
        always when calling waadmin.wa on HP64
        Workaround:
        open WebAgent75.ini file and replace "R.slurce" with
        "Resource" and "dat.slurce" with "datasource"
        Solution:
        apply bugfix


WebDAV:
=======

    PTS: 1129095    since: 7.5.00.12

    Fixed Problem:
        appearance:
        When using WebDAV and sending a PROPFIND request with empty
        body.
        Preconditions and circumstances:
        no special circumstances or preconditions
        Workaround:
        no workaround
        Solution:
        apply patch


    PTS: 1128868    since: 7.5.00.12

    Fixed Problem:
        appearance:
        while upgrading a database instance from 7.4.03.30 or later
        to 7.4.03.31/32/33
        while upgrading a database instance from 7.5.00.08 or later
        to 7.5.00.09/10/11
        Preconditions and circumstances:
        1. Instance was created with a release before 7.4.03.23 as
        a ASCII Instance
        2. This instance was migrated to Unicode
            or
            an backup of an ASCII instance of release between
        7.4.03.10 and 7.4.03.23 was loaded to an UNICODE Instance
        3. Instance was upgraded to 7.4.03.30 or later or 7.5.00.08
        or later and while doing this the instance was migrated to
        unicode if not already done
        4. upgrading the instance to a release higher than the one
        used in step 3.
        Workaround:
        In case WebDAV was not used with this instance
        1. drop the WEBDAV Tables
           WEBDAV_INODE
           WEBDAV_CONTAINER
           WEBDAV_PROPERTY
           WEBDAV_PROPERTY_MANAGEMENT
           WEBDAV_NAMESPACE
        2. perform a load_systab
        Solution:
        upgrade to the release containg this patch


    PTS: 1128501    since: 7.5.00.12

    Fixed Problem:
        appearance:
        When using the WebDAV server to lock a resource the error
        reply contains a list of URL to already locked resources.
        The URL's are wrong because the WebDAV service name is not
        part of them.
        Preconditions and circumstances:
        The resource to lock has to be a collection. The tree of
        resources contained in this collection contains an already
        locked resource. The lock to create has to be of depth
        "infinty" or, if the already locked resource is member of
        the resource to lock, of depth "1".
        Workaround:
        no workaround to avoid this behavior. When using the
        provided URL's for unlocking the already locked resources,
        then correct them as follows:
        provided URL:
        http://<your-server-name>:<your-port>/<resource-URI>
        correct URL:
        http://<your-server-name>:<your-port>/<WebDAV-service-name>/<resource-URI>
        The WebDAV service name is the name you gave while creating
        the WebDAV service via waadmin.wa. Default is "webdav"
        Solution:
        apply the patch


    PTS: 1128253    since: 7.5.00.12

    Fixed Problem:
        appearance:
        The error occurs on a regular base but not completely
        deterministic, when PUTting a file to the WebDAV server.
        Preconditions and circumstances:
        no special preconditions
        Workaround:
        no workaround
        Solution:
        apply the patch


    PTS: 1128352    since: 7.5.00.11

    Fixed Problem:
        appearance:
        When using WebDAV server to copy or move a resource between
        two different WebDAV servers the server replies with 200 Ok
        instead of 501 Not implemented.
        Preconditions and circumstances:
        no special preconditions or circumstaces
        Workaround:
        no workaround
        Solution:
        apply the patch


    PTS: 1128341    since: 7.5.00.11

    Fixed Problem:
        appearance:
        When setting up a database instance of release >= 7.5.00.08
        the "creationdate" and "getlastmodified" property of the
        WebDAV root collection and the "Deleted Items" collection
        are set with a date in internal date format. It should be
        ISO format to get a proper PROPFIND reply for these
        collections.
        Preconditions and circumstances:
        no special preconditions or circumstances
        Workaround:
        The false date format does cause the PROPFIND to send an
        empty string for these properties. Because the collections
        affected are server defined and no known side effects
        occur. There is no need to patch the dates.
        Solution:
        apply the patch. newly created instances will have the
        correct date format for the two collections mentioned above.


    PTS: 1128340    since: 7.5.00.11

    Fixed Problem:
        appearance:
        When using the WebDAV server and sending a PROPFIND request
        that should return the "creationdate" property of a
        resource.
        Preconditions and circumstances:
        no special preconditions or circumstances
        Workaround:
        no workaround
        Solution:
        apply the patch


    PTS: 1128008    since: 7.5.00.11

    Fixed Problem:
        appearance:
        While sending a PUT request to the MaxDB WebDAV Server with
        a wrong content type
        Preconditions and circumstances:
        no special preconditions or circumstances needed
        Workaround:
        Do not send malformed content types
        Solution:
        apply the pathch


    PTS: 1127686    since: 7.5.00.11

    Fixed Problem:
        appearance:
        on all platforms
        Preconditions and circumstances:
        when sending a PUT/LOCK/PROPFIND/PROPPATCH request with
        Content-Length=0 to WebDAV
        Workaround:
        for PUT: PUT at least one character (blank)
        for LOCK/PROPFIND/PROPPATCH: none
        Solution:
        apply the patch


    PTS: 1126020    since: 7.5.00.09

    Fixed Problem:
        appearance:
        deleting a resource using the webdav GUI fails with a 404
        Not Found reply
        Preconditions and circumstances:
        nothing special
        Workaround:
        deleting with another tool like Windows FileExplorer
        WebFolder or any other webdav supporting tool.
        Solution:
        apply the patch


    PTS: 1123822    since: 7.5.00.09

    Fixed Problem:
        appearance:
        While using WebDAV
        Preconditions and circumstances:
        unconditional
        Workaround:
        no workaround
        Solution:
        apply patch


    PTS: 1124235    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server replied with 500 Intenal Server Error if
        an UNLOCK request provided the wrong lock token for the
        resource.
        This is fixed. According to RFC2518 it returns 423 Locked
        instead now.


    PTS: 1124196    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server returned 500 Internal Server Error if a
        UNLOCK request provided a malformed lock token.
        Now a maleformed lock token will cause a 400 Bad Request
        along with a propper error message in the body.


    PTS: 1124184    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server crashed when a PROPFIND request was
        submitted that contained at least one namespace name longer
        than 499 characters or a property name longer than 300
        characters.
        This was fixed.
        The WebDAV server now returns a 409 Conflict reply with a
        proper error message instead.


    PTS: 1124042    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server did crash if a lock owner larger than 450
        characters was issued or if the lock request body exceeded
        a certain amount of characters.
        This is fixed. As of now only lock owner of a length <= 450
        characters are allowed. Otherwise a 409 Conflict - "Lock
        owner exceeds supported length of 450 characters." reply
        will be sent.


    PTS: 1124022    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server did cut the last charater of the owner
        tag of a  LOCK request. This is fixed.


    PTS: 1124008    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server now returns a 403 Forbidden reply in the
        case a file is used as directory if a client tries to
        creating a new resource beneath a non-collection resource.


    PTS: 1123907    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server returned 400 Bad Request for PROPPATCH
        requests of this or similar structure:
        <?xml version="1.0" encoding="utf-8" ?>
           <D:propertyupdate xmlns:D="DAV:"
               xmlns:Z="www.sapdb.org/xml/indexing">
               <D:set>
                   <D:prop>
                       <Z:prop1>1</Z:prop1>
                   </D:prop>
               </D:set>
               <D:remove>
                   <D:prop>
                       <Z:prop1/>
                   </D:prop>
               </D:remove>
               <D:set>
                   <D:prop>
                       <Z:prop1>2</Z:prop1>
                   </D:prop>
               </D:set>
           </D:propertyupdate>
        This is fixed. Now requests of this structure will be
        processed properly


    PTS: 1123799    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server crashed when properties with a name
        longer than 300 characters or property values longer than
        450 characters or namespaces with more than 499 characters
        were used in a proppatch request.
        This will no longer happen.
        Instead a proper error message (409 Conflict) along with a
        responsedescription is provided for each property that
        violates these restrictions.


    PTS: 1123590    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server crashed when using the WebDAV GUI while
        no connect parameters are given in the WebDAV session pool.
        This was fixed.


    PTS: 1123442    since: 7.5.00.08

    Fixed Problem:
        The WebDAV server did not forbid PROPPATCH requests on live
        properties.
        This is fixed. By now the following requests are forbidden:
        <DAV:set> for
           <!ELEMENT creationdate (#PCDATA) >
           <!ELEMENT getcontentlength (#PCDATA) >
           <!ELEMENT getetag (#PCDATA) >
           <!ELEMENT getlastmodified (#PCDATA) >
           <!ELEMENT lockdiscovery (activelock)* >
           <!ELEMENT resourcetype ANY >
           <!ELEMENT source (link)* >
           <!ELEMENT supportedlock (lockentry)* >
        <DAV:remove> for
           <!ELEMENT creationdate (#PCDATA) >
           <!ELEMENT displayname (#PCDATA) >
           <!ELEMENT getcontentlanguage (#PCDATA) >
           <!ELEMENT getcontentlength (#PCDATA) >
           <!ELEMENT getcontenttype (#PCDATA) >
           <!ELEMENT getetag (#PCDATA) >
           <!ELEMENT getlastmodified (#PCDATA) >
           <!ELEMENT lockdiscovery (activelock)* >
           <!ELEMENT resourcetype ANY >
           <!ELEMENT source (link)* >
           <!ELEMENT supportedlock (lockentry)* >
        A patch of getcontenttype, getcontentlanguage and
        displayname is allowed.


    PTS: 1123370    since: 7.5.00.08

    New Feature:
        The WeDAV server accepted any string delivered as
        Content-Type although it has to check the compliance of the
        content type to RFC2068.
        The WebDAV server now performs a syntax check of the
        delivered content type on PUT requests. For the correct
        syntax please refer to RFC2068 section 3.7. Media Types.

Runtime Environment:
====================

    PTS: 1129126    since: 7.5.00.12

    Fixed Problem:
        appearance:
        UNIX only : Release 7.4.03.23 - 7.4.03.32, 7.5.00.00 -
        7.5.00.11
        Error message in knldiag while opening pipes as backup
        media:
        2004-04-12 01:05:31     9 ERR 11000 devio    seek (fd = 56)
        error: Illegal seek
        Preconditions and circumstances:
        During open of pipes used as backup media the first 2K are
        tried to preserve. This is
        meaningfull only for AIX raw logical volumes, where first
        512 bytes are still reserved for AIX internally...
        Workaround:
        not needed, message can be ignored as it was internally
        ignored until now.
        Solution:
        The error is no longer ignored for volumes where the first
        2K are always skipped if they exist. For all backup media
        the first 2K are no longer preserved. Therefore no seek for
        backup media is needed anymore.


    PTS: 1128967    since: 7.5.00.12

    New Feature:
        Feature description:
        If  there is no DNS server installed or the server is not
        functioning properly each remote connect-request takes up
        to 20 seconds to respond.
        A new XSERVER installation option -F (fast mode) has been
        added to suppress reverse IP lookup.
        Disadvantage: Only raw ip addresses are shown by diagnostic
        tools like "x_cons".
        To reinstall the xserver start "serv.exe -u -F" from
        command prompt.


    PTS: 1128939    since: 7.5.00.12

    Fixed Problem:
        appearance:
        a db_register (without any parameters) command overwrites a
        configured operating system user for a database
        Preconditions and circumstances:
        windows only
        Workaround:
        do not use db_register without parameters or configure the
        operating system user afterwards again
        Solution:
        If no parameters are given, leave the configured operating
        system user untouched


    PTS: 1128806    since: 7.5.00.12

    Fixed Problem:
        appearance:
        the db_Stop command returns "RTE Error 1,"
        Preconditions and circumstances:
        happened within the test frame only. The message was
        generated when the kernel process was still alive 90
        seconds after a SIGKILL command had been issued
        Workaround:
        ignore the message...
        Solution:
        The   - sign was generated because of an uninitialized
        string. This has been replaced by a meaningful error
        message. In addition to that, the timeout has been set to
        120 seconds. Now the error does not appear anymore...


    PTS: 1128785    since: 7.5.00.12

    New Feature:
        Feature description:
        In the past, detecting the state of a database that was not
        running at all took four seconds. now it is working much
        faster.


    PTS: 1128530    since: 7.5.00.12

    Fixed Problem:
        appearance:
        DBM commands reports error message containing unprintable
        characters
        Preconditions and circumstances:
        Message output in dbm.prt contains lines like
        2004-03-16 05:49:20 0x000035f1              0 DBM
        command db_stop
        2004-03-16 05:52:22 0x000035f1 ERR     -24994 DBM
        ERR_RTE: runtime environment error
                                          0x000035f1 ERR     -24994
        DBM      1,RTE error 
        but the command itself worked fine.
        Workaround:
        not needed
        Solution:
        The message is issued due to an uninitialized error message
        buffer.


    PTS: 1128472    since: 7.5.00.12

    Fixed Problem:
        appearance:
        weird error messages when accessing the parameter file from
        the dbm.
        Preconditions and circumstances:
        the path to the parameter file is more than 32 characters
        long
        Workaround:
        move the parameter file to another place in the file system
        so that it can be accessed by a shorter path
        Solution:
        reserve more (==enough) space for the parameter file path.
        In addition check when that size should be exceeded.


    PTS: 1128200    since: 7.5.00.11

    Fixed Problem:
        appearance:
        Database crash in 'vgetapplpid'
        Preconditions and circumstances:
        A SQL Statement such as
        'SELECT * FROM INFO_CONNECTED_USERS'
        is issued to the Standby Node on a Hot Standby system
        Workaround:
        No workaround
        Solution:
        Use patch


    PTS: 1128115    since: 7.5.00.11

    Fixed Problem:
        appearance:
        database kernel crashes when very complex select statements
        or subqueries are given.
        The kernel should not crash, but give an error "-9018 stack
        overflow"
        Preconditions and circumstances:
        Linux or HP UX running on Itanium processor
        Workaround:
        none
        Solution:
        in addition to checking the size of the normal stack
        itself, the size of the Itanium-specific backing store
        is now checked


    PTS: 1127780    since: 7.5.00.11

    Fixed Problem:
        appearance:
        When the dbmsrv crashes, the dbmcli produces a garbled
        error message
        Preconditions and circumstances:
        windows only
        Workaround:
        ignore the garbled message
        Solution:
        Now the character array for the error message is
        initialized before use...


    PTS: 1127753    since: 7.5.00.11

    New Feature:
        Feature description:
        On Unix, the database kernel now reports detailed
        information of the cpu it is running on when being started


    PTS: 1127569    since: 7.5.00.11

    New Feature:
        Feature description:
        The message output to knldiag was improved if a task awakes
        from a wrong event.
        The message
        'vsuspend'/'vsleep/vwait awoke from wrong event
        was substituted by:
        "'vsuspend'/'vsleep/vwait awoke from wrong event: [T: x]
        CurrReq: y expected Req: z"
        where x is the current task index,
                   y is the pointer to current request queue
        element,
                   z is the pointer to the expected request queue
        element.
        Additionally the following message is written:
        "Ta awoked from Tb by c (wanted d)"
        where a is the current task index,
                   b is the task index of the task from which the
        current task awoke
                   c is the request type, the current task awoke
        from
                   d is the request type the current task was
        expected


    PTS: 1127482    since: 7.5.00.11

    Fixed Problem:
        appearance:
        When a dbmsrv is frequently checking the state of a
        database using db_state and another dbmsrv is currently
        starting the database, the first dbmsrv may hang.
        Preconditions and circumstances:
        windows only
        Workaround:
        Avoid frequently checking the database state while the
        database is being started
        Solution:
        When the checking the state of a database and finding a
        state between stopped and running, the dbmsrv now waits
        until the database is completely running OR stopped.


    PTS: 1127069    since: 7.5.00.11

    Fixed Problem:
        appearance:
        On windows SYNCHRONIZE connection of hot standby STANDBY
        node sometimes terminates without reason.
        Preconditions and circumstances:
        In kernel diagnostic messages a line
        2004-01-08 14:16:44      0xF38 ERR 13911 RTEHSS   Closing
        command pipe for 'Kernel command no longer active' failed
        [0]
        is found.
        Workaround:
        You have to reinitialize the STANDBY node (RESTART STANDBY
        command).
        Solution:
        Detection of correct SYNCHRONIZE command termination is
        fixed now.


    PTS: 1128003    since: 7.5.00.10

    Fixed Problem:
        appearance:
        On HP-UX the database kernel runs in a tight loop.
        Preconditions and circumstances:
        Load balancing is enabled ( Kernel parameter
        LOAD_BALANCING_CHK not equal to  0 )
        Workaround:
        Set the kernel parameter LOAD_BALANCING_CHK to 0
        Solution:
        A initialization of a locked scope varaible was missing.
        The variable is now initialized during kernel startup phase.


    PTS: 1127709    since: 7.5.00.10

    Fixed Problem:
        appearance:
        Kernel crashes with signal 11 (SIGSEGV)
        Preconditions and circumstances:
        A x_cons command which is executed by the console thread
        (e.g.show all, show moveinfo, show t_move)
        Workaround:
        no workaround
        Solution:
        new release


    PTS: 1127193    since: 7.5.00.09

    Fixed Problem:
        appearance:
        A user can not  execute a x_cons command. He get the
        following error message:
        13404 ERROR: + 2004-01-16 12:06:04.803 RTE ERROR 13412
        13404 ERROR: -   XCons: Access to server DB TEST1 denied
        13404 ERROR: + 2004-01-16 12:06:04.803 RTE ERROR 13428
        13404 ERROR: -   XCons: Send request 4294934272 to server
        DB TEST1 failed
        13404 ERROR: XCons: Connect failed
        Preconditions and circumstances:
        The user is not in the administors group of the machine.
        Workaround:
        No workaround
        Solution:
        New release


    PTS: 1127157    since: 7.5.00.09

    Fixed Problem:
        appearance:
        the kernel refuses start with a message that a volume size
        exceeds the configured ulimit - even if the volume is on a
        raw device. Sometimes even the size of not configured
        volumes (system devspace) is complained about.
        Preconditions and circumstances:
        Unix only
        Workaround:
        Configure the ulimit big enough
        Solution:
        Before checking the volume size againts the ulimit check if
        the volume actually exists and is not a raw device


    PTS: 1127071    since: 7.5.00.09

    Fixed Problem:
        appearance:
        kernel crash. The stack back trace ends in e73_dl_enqu(),
        call by e75_connect()
        Preconditions and circumstances:
        Connects are made to the kernel in a high frequency
        Workaround:
        none
        Solution:
        the free list used by e73_dl_enqu was not completely
        multi-thread-safe. This has been fixed.


    PTS: 1126950    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Incorrect build number in table sysdd.version on windows.
        Preconditions and circumstances:
        none
        Workaround:
        none
        Solution:
        The SAPDB_sprintf() statement that produces the version
        string has been fixed. Now the correct build number is
        produced and also the service pack version is added to the
        version string.


    PTS: 1126834    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Runtime configuration values could not be removed in user
        configuration (Windows only)
        Preconditions and circumstances:
        A configuration value in the user registration part is to
        be modified.
        Workaround:
        none
        Solution:
        The correct registry section is choosen with this patch.


    PTS: 1126648    since: 7.5.00.09

    Fixed Problem:
        Not relevant because Itanium is no supported platform for
        Hot Standby so far.


    PTS: 1126569    since: 7.5.00.09

    Fixed Problem:
        appearance:
        The dbm command db_state hangs
        Preconditions and circumstances:
        The database kernel is currently being stopped. Windows
        only.
        Workaround:
        Stop the hanging dbm and issue the db_state command again
        Solution:
        Now the error code is checked correctly when the state of
        the database kernel service is checked.


    PTS: 1126215    since: 7.5.00.09

    Fixed Problem:
        Appearance:
        The kernel crashes with an exception/signal in:
            __os74SendMoveRequest / en71SendMoveRequest
        Preconditions and circumstances:
        This error occurs if a long running LC-Application prevents
        runtime dispatching.
        Workaround:
        Disable load balancing
        Solution:
        Software update


    PTS: 1125791    since: 7.5.00.08

    Fixed Problem:
        appearance:
        The following commands get no result if they are executed
        from x_cons:
        TRACE_FLUSH
        PAGECACHE_RELEASE
        DIAGNOSE_PAGECACHE
        LD_BAL_CHK
        SHOW MOVEINFO
        SHOW T_MOVE
        SHOW ALL
        On linux the database even crashes.
        Preconditions and circumstances:
        The user of X_CONS does not belong to the same group as the
        owner of the database.
        Workaround:
        No workaround available.


    PTS: 1125790    since: 7.5.00.08

    Fixed Problem:
        appearance:
        Database may chrash if the  X_CONS command 'SHOW QUEUES'
        (also included in 'SHOW ALL') is excecuted.
        Preconditions and circumstances:
        This effect is enforced if load balancing is activated for
        the database.
        Workaround:
        No workaround available
        Solution:
        Update to version including this patch.


    PTS: 1125558    since: 7.5.00.08

    Fixed Problem:
        appearance:
        During local connection attempt, the error
         Error -8888: SERVERDB not accessible, cannot create
        communication semaphore
        is shown.
        Preconditions and circumstances:
        The database name is not given in all uppercase letters and
        a local connection is attempted.
        Workaround:
        Use only UPPERCASE database names.
        Solution:
        An automatic uppercase mapping in the routines, that
        establish the connection.


    PTS: 1124904    since: 7.5.00.08

    Fixed Problem:
        appearance:
        during a migration from 7.3 log mode DUAL is not correctly
        transformed
        Preconditions and circumstances:
        migration from 7.3, log mode DUAL
        Workaround:
        set LOG_MIRRORED manually after the migration


    PTS: 1124645    since: 7.5.00.08

    Fixed Problem:
        appearance:
        the kernel crashes on a MONITOR INIT command
        Preconditions and circumstances:
        32-bit linux is used
        Workaround:
        none


    PTS: 1124589    since: 7.5.00.08

    Fixed Problem:
        Appearence:
        database cannot be restarted. (state online ---> state
        admin). error message "database already started", but a
        state check gives state offline
        Preconditions and circumstances:
        may happen under unix, not reproducable
        Workaround:
        wait a small amount of time before restarting the database


    PTS: 1124563    since: 7.5.00.08

    New Feature:
        In a cluster configuration, the <indepData> may now be used
        in a shared partition. The protocol files, named pipes and
        pid files are extended with the local machine name. The
        following files have been renamed:
        <indepData>/wrk/xserver.prt -> xserver_host.prt (All
        Platforms)
        <indepData>/wrk/niserver.pid       -> niserver_host.pid
        (UNIX only)
        <indepData>/wrk/niserver.prot      -> niserver_host.prot
        (UNIX only)
        <indepData>/wrk/NI_TRACEFILE -> niserver_host.trace (UNIX
        only)
        /usr/spool/sql/fifo/xserver_logger -> xserver_host_logger
        (UNIX only)
        /usr/spool/sql/fifo/xserver_update -> xserver_host_update
        (UNIX only)
        <indepData>/wrk/NI_TRACEFILE.srv -> niserver_host.trace
        (Windows only)
        NOTE: <indepData>/wrk/xserver.prt and
        <indepData>/wrk/xserver.old want be automatically deleted
        on Windows


    PTS: 1124518    since: 7.5.00.08

    Fixed Problem:
        appearance:
        After DATALOADing UTF8 data the character data may be
        corrupted if the data contains characters with a size
        greater than 1 Byte


    PTS: 1124495    since: 7.5.00.08

    Fixed Problem:
        On windows, bringing a database from online to admin state
        sometimes failed with an error message "database already
        started", but afterwards the database was offline.
        This never happened on windows 2000 PCs, but  frequently
        occurred on a windows xp make/test server.


    PTS: 1124125    since: 7.5.00.08

    Fixed Problem:
        If a client application connects with a serverDB name
        longer than 18 Characters the application may crush with an
        access violation.
        Correction:
        Connects with serverDB names longer than 18 characters are
        not supported . The client application gets the error
        message 'serverDB name too long'.


    PTS: 1124003    since: 7.5.00.08

    Fixed Problem:
        SECURITY
        1) Preconditions and circumstances
        This is a security fix. It protects against potential
        buffer overflow using a specialized 'intrusion' program,
        that could
        execute code an behalf of the owner of 'niserver' or
        'x_server'.
        The possible attack position is inside common used code
        shared between all platforms.
        2) Probability that the error occurs
        low (no such program was ever known off, but the code would
        allow to write it...). If such a program was written: 100%
        3) Solution to the problem
        The copy routines is modified to check the string for being
        correctly terminated by a zero byte. If not the connection
        packet is rejected.
        4) Visibility
        it depends on the action taken by the intruders coding...
        5) Workaround
        none


    PTS: 1123804    since: 7.5.00.08

    New Feature:
        If a database had been created using the -a flag, the
        autostart flag was set for all database speeds. That made
        this option unusable.
        This has been changed so that the autostart flag is set for
        the "fastest" speed available only. This is normally the
        fast kernel.


    PTS: 1123710    since: 7.5.00.08

    Fixed Problem:
        0) Releases
        UNIX only
        1) Preconditions and circumstances
        If the  home directory of the database software owner does
        not allow to create subdirectories, the DBM installation
        command
        'inst_reg' crashes or runs into untermined state.
        2) Probability that the error occurs
        100%
        3) Solution to the problem
        the subdirectory is no longer created and the error message
        which leads to stack corruption is fixed.
        4) Visibility
        high (installation fails)
        5) Workaround
        Make Homedirectory of database software owner writable.


XSERVER:
========

    PTS: 1129073    since: 7.5.00.12

    Fixed Problem:
        appearance:
        A Windows or older UNIX client application such as
        'SQLStudio' or 'xci' can not connect to an UNIX database
        server. The client gets the following message: 'SQL_ERROR
        (-709): database not running'.
        In the XSERVER protocol one can find the following message:
        2004-04-06 18:54:40 20461 ERR 11311  IPC      idfile:
        'UserProfileContainer(stat)' open error, No such file or
        directory
        Preconditions and circumstances:
        The database name is given with lower case letters
        Workaround:
        The database name has to be given in uppercase letters.
        Solution:
        Update for the XSERVER.


    PTS: 1128964    since: 7.5.00.12

    New Feature:
        Feature description:
        d


    PTS: 1127651    since: 7.5.00.11

    Fixed Problem:
        appearance:
        XServer crashes with a access violation.
        Preconditions and circumstances:
        Kernel has corrupted the communication segment header (e.g.
        if a task has caused a stack overflow)
        Workaround:
        No workaround
        Solution:
        Range check for one of the elements of the communication
        segment header


    PTS: 1126985    since: 7.5.00.09

    Fixed Problem:
        appearance:
        Update installation of release 7.5.00.08 fails due to
        blocking x_server.
        Preconditions and circumstances:
        Running x_server must be be 7.5.00 build 08 or 7.4.03 build
        > 33 and Installation of 7.5.00.08 is wanted.
        Workaround:
        Stop x_server before installation.
        Solution:
        x_server update process no longer fails to open its reply
        pipe.


    PTS: 1125784    since: 7.5.00.09

    Fixed Problem:
        appearance:
        During software update DBMGUI/dbmcli is able to connect
        from a remote host. Since it can happen in any state of
        update process the behavour is completely undefined.  One
        appearance is the update process fails since dbmsrv is busy.
        Preconditions and circumstances:
        x_server is running
        Workaround:
        Only by policy: Do not try to use software while it is
        updating. Do not connect a DBMGUI/dbmcli while
        update process is running.
        Solution:
        The x_server checks if the installation is registered.
        Since the software update first deregisters the
        installation, no futher dbmsrv connection will be
        establishable.


    PTS: 1126264    since: 7.5.00.08

    Fixed Problem:
        appearance:
        If port number > 32767 are choosen as x_server well known
        tcp-port, the x_server cannot be stopped. The x_server stop
        command report successfull completion, but the x_server
        runs as if no stop command was issued.
        Preconditions and circumstances:
        You must have modified the port number in /etc/services to
        a number > 32767 or started the
        x_server with -S port option, where port is > 32767. With
        normal setting, the x_server is not affected.
        Workaround:
        None, you must all the 'vserver' processes running.
        Solution:
        The port numbers > 32767 are accepted with this patch.


    PTS: 1125125    since: 7.5.00.08

    Fixed Problem:
        appearance:
        A normal UNIX user was allowed to stop/update  x_server.
        A normal UNIX user was not allowed to enumerate databases.
        Preconditions and circumstances:
        none
        Workaround:
        none


    PTS: 1124308    since: 7.5.00.08

    Fixed Problem:
        0) Releases
        UNIX only 7.5.0.0 - 7.5.0.2
        1) Preconditions and circumstances
        A unknown INSTROOT specified in a dbmcli command leads to a
        crash of main x_server.
        2) Probability that the error occurs
        100%
        3) Solution to the problem
        Missing parameter added in faulty function call.
        4) Visibility
        low
        5) Workaround
        none


