Yes, Mark, and I also think Raymond misspelled a word, too.
Raymond Shahan
Information Systems
REPUBLIC TITLE OF TEXAS, INC.
2701 W Plano Parkway
Plano, TX 75075
direct 214.556.0202
main 972.578.8611
fax 972.424.5621
www.republictitle.com
[log in to unmask]
Life is not a journey to the grave with the
intention of arriving safely in a pretty and
well preserved body, but rather to skid in
broadside, thoroughly used up, totally worn out,
and loudly proclaiming:
-- WOW!!! What a Ride!!!
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Mark Landin
Sent: Wednesday, August 01, 2007 1:13 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] STALLED TRANSACTION: EXCEEDED ACCUMULATED LOG
DATA THRESHOLD
That's a pretty vague answer, Raymond. Can you provide any detail? :)
On 8/1/07, Legault, Raymond D <[log in to unmask]> wrote:
> indexing
> (TPI) are the most likely to see this problem.
>
> Stalled transaction: EXCEEDED ACCUMULATED LOG DATA THRESHOLD
>
> Warning: One or more entries on the error stack have been overwritten
> HPE error management message 205
> Warning: Message set 185, error number 1030 was not found in system
> catalog.
> Intrinsic layer: An access violation occurred File system message 3
>
>
> RESOLUTION
> The Transaction Manager(XM) message occurs because the length of the
> transaction defined by dbxbegin and dbxend exceeded the allowable
limit.
> If you use TPI (Third Party Indexing) the reason for the stall may be
a
> large number of deletes to a dataset.
>
> TPI by Omnidex does the DBPUT as follows:
>
> The DBPUT uses empty records from delete chain, than a reshuffle of
the
> index records is done in order to keep the RRNs in sorted order. This
> can apparently take up lots of XM buffer space.
>
> XM Transaction size:
> Pre-6.0 the allowable limit per TURBOIMAGE transaction is 1 megabyte.
> (There is no accurate way to estimate how much of that 1 meg each
> transaction will take.) As of 6.5 XM transactions have been increased
> to 128 megabytes (SR|1653291559).
>
> TPI Solution:
>
> Omnidex suggests that customers do a REPACK of detail set and REINDEX.
> If the delete rate is high a REPACK of the detail set and REINDEX
should
> be done often. Contact this 3rd party if you have more questions.
>
> Workaround: Disable TPI XM:
>
> Turn off XM for TPI (Omnidex)
>
> RUN DBINSTAL.PUB.DISC
> Data base name: mydb
> Cmd: SET TPI NOXM
>
>
> Image/Sql Stalled Transactions Solution:
>
> >SET AUTOCOMMIT ON;
> >SET AUTOSAVE 100; set the number of rows to commit on
>
> This will force a commit work more often, which should decrease the
> amount of XM buffer space used.
>
> Other SRs on the subject:
>
> SR#5003028662 TurboIMAGE intrinsics should provide optional control
>
> Lab Text: XM has the 1 MB transaction limit and the XM rollover
> maximum.Since this is a feature that was within the original design,
> TurboIMAGE has no control and cannot intercept the XM error.XM will
need
> to return a new error status to TurboIMAGE, whichenables TurboIMAGE
> intrinsics to return a new error conditionto the application program.
> This SR is indeed a complicatedrequest which requires resolution of
> several issues betweenXM and TurboIMAGE, and also, requires
redesigning
> and recoding.Overall, this does not seem like a big payback for XM
> andTurboIMAGE. In reality, there may be a problem with thedesign of
the
> application program itself when the application program allows for a
> DBXBEGIN/DBXEND that loops thru codewhich does 630 DBPUTs and 629
> DBUPDATEs.
>
> SR# 1643024158 Request for larger TurboIMAGE Dynamic Transactions
>
> Enhance Dynamic Rollback feature such that the users are not
restricted
> to use only DBXUNDO or DBCLOSE after an unsuccessful intrinsic call
> (non-zero status).
> Based on the status condition, theuser would like flexibility and take
> appropriate steps so that the whole transaction does not have to be
> rolled back.
>
>
> 6.5 transaction manager changes:
>
> The checkpoint improvement feature added in on 6.0 using
ALTERCHKPTSTAT
> was intended to reduce the lock time on the memory management
semaphore
> while posting out files attached to the XM user log. In 6.5 and
later,
> two changes have occurred that resulted in removal of this feature.
>
> 1. The memory management semaphore strategy has been entirely
> redesigned to eliminate the single, system-wide resource.
>
> 2. The maximum file size of a file that is attached to the XM user
> log increased to 128 gb.
>
> Change #1 reduced the need for the ALTERCHKPTSTAT feature. Change #2
> caused the bitmap that was kept in the GUFD to grow too large for the
> GUFD structure. As a result, the code that would have been executed
if
> ALTERCHKPTSTAT was enabled was removed with the $skip_text on$ and
> $skip_text off$ compiler options.
>
> ============================================= END
> ==========================
>
> From Omnidex-----
>
> Also, TPI settings apply only to Omnidex enhanced (Installed)
Databases.
> I see here that you were using the command on a non-Omnidex enhanced
> database.
>
> Cmd: set tpi noxm
> TPI will be enabled during installation
>
> The statement above that "TPI will be enabled during installation"
only
> applies to the current session within dbinstal. That means that if
you
> install as I do below, TPI will be set at the end of the Omnidex
> installation. It is more common to SET TPI {ON|OFF|NOXM} on a
currently
> Omnidex enhanced database.
>
> HPIX3> [DMDDEV.DMD]:run dbinstal.pub.disc308
>
>
> OMNIDEX DBInstal, Release 3.8.14 Tue Dec 5 2006 09:27:42
> (c) Copyright 1981-1998 Dynamic Information Systems Corporation
>
> Database or Environment: sales.demodb
>
> Cmd: set tpi noxm
> TPI will be enabled during installation
>
> Cmd: i
>
> ** OMNIDEX MultiDimensional/Keyword (MDK) Index Installation **
>
> Enter Tables (Data Sets) and Columns (Data Items) to be indexed
>
> To create an index comprised of all or parts of one or more columns,
> enter an Index Name followed by '!' at the Column prompt
>
> Enter '?' for a list of Tables or Columns, '/' to exit the current
> prompt
>
> Table name? customers
> Column name: contact
> Column name: /
> Table name? /
>
> Specification of MDK indexes is complete
>
> ** OMNIDEX Aggregation/Sorted_Key (ASK) Index Installation **
>
> Table name? /
>
> Proceed with installation? [Y]
>
> Use the Build command to load the following indexes:
>
> CUSTOMERS (Omnidex MDK)
> TurboIMAGE TPI enabled
>
> Rootfile lgth = 4096 bytes. Installation complete.
>
> Cmd: quit
>
> END OF PROGRAM
> HPIX3> [DMDDEV.DMD]:
>
> Thanks,
>
> Derek
>
> -----Original Message-----
> Subject: RE: TPI NOXM what cmd turns it back on
>
> Ray,
>
> Set tpi off - turns tpi off no matter how it was turned on.
>
> Set tpi on - turns on tpi with transaction management on the indexes.
>
> Set tpi noxm - turns on tpi with no transaction management on the
> indexes.
>
> Thanks
> Jeff
>
> -----Original Message-----
>
> Subject: TPI NOXM what cmd turns it back on
>
> Cmd: set tpi noxm
> TPI will be enabled during installation
>
> Cmd: set tpi xm
> Expecting ON or OFF
>
> Cmd: redo
> Unrecognized command. Try Help
>
> Cmd:
>
> Cmd: set tpi xmon
> Expecting ON or OFF
>
> Cmd: set tpi xm on
> Expecting ON or OFF
>
>
>
> -----Original Message-----
> From: Rao, Raghu [mailto:[log in to unmask]]
> Sent: Tuesday, July 31, 2007 6:09 PM
> Subject: STALLED TRANSACTION: EXCEEDED ACCUMULATED LOG DATA THRESHOLD
>
> Any help is really appreciated.. Thanks..
>
>
> 600 :RUN BCP0100.PROGXL.!HPACCOUNT;XL="!QXLINFO";NMSTACK=1300000
> 601
> 602
> 603 ** BCP0100 VERSION 11.01.08.04 02/27/2004 01:02 AM **
> 604 ** Copyright AMISYS, LLC **
> 605 ** 1990-2003 All Rights Reserved **
> 606
> 607
> 608 Enter the Mode : 1
> 609
> 610 Enter the Batch/Operator : @
> 611
> 612 Enter the Claim Type : @
> 613
> 614 Enter the Effective Date : 19000101
> 615
> 616 Enter the End date : 99991231
> 617
> 618 Enter the Action Trigger :
> 619
> 620 Enter the User Op# : *SYS
> 621
> 622 Enter the Load EX-Code flag: N
> 624
> 625 **** STALLED TRANSACTION: EXCEEDED ACCUMULATED LOG DATA
> THRESHOLD
>
> 627 WARNING ** One or more entries on the error stack have been
> overwritten.
> 628
> 629 HPE Error Management message 205
> 630
> 631 WARNING ** Message set 185, Error number 1030 was not found
in
> the syste
> 632 m catalog.
> 633
> 634 Intrinsic layer; an access violation occurred.
> 635
> 636 File System message 3
> 637
> 638 Intrinsic layer; an access violation occurred.
> 639
> 640 File System message 3
> 641
> 642 Intrinsic layer; an access violation occurred.
> 643
> 644 File System message 3
> 645
> 646 Intrinsic layer; an access violation occurred.
> 647
> 648 File System message 3
> 649
> 650 Intrinsic layer; an access violation occurred.
> 651
> 652 File System message 3
> 653
> 654 Intrinsic layer; an access violation occurred.
> 655
> 656 File System message 3
> 657
> 658 Intrinsic layer; an access violation occurred.
> 659
> 660 File System message 3
> 661
> 662 Specifying the LONG MAPPED OPTION (item# 21) for this file
> type is inval
> 663 id.
> 664 (FILE OPEN ERROR -299)
> 665
> 666 File System message 299
> 667
> 668 Specifying the LONG MAPPED OPTION (item# 21) for this file
> type is inval
> 669 id.
> 670 (FILE OPEN ERROR -299)
> 671
> 672 File System message 299
> 673
> 674 Intrinsic layer; an access violation occurred.
> 675
> 676 File System message 3
> 677
> 678 Intrinsic layer; an access violation occurred.
> 679
> 680 File System message 3
> 681
> 682 Intrinsic layer; an access violation occurred.
> 683
> 684 File System message 3
> 685
> 686 Intrinsic layer; an access violation occurred.
> 687
> 688 File System message 3
> 689
> 690 Intrinsic layer; the operation could not be completed because
> a nonexist
> 691 ent
> 692 file was specified.
> 693
> 694 File System message 38
> 695
> 696 FLABELINFO intrinsic.
> 697
> 698 SUBSYS_INTRIN_ID message 25
> 699 ABORT: BCP0100.PROGXL.AMISYS
> 700 NM SYS a.00fdbf70 dbg_abort_trace+$28
> 701 NM USER 1a0.00d57d94 PROC'EXIT000445+$78
> 702 NM PROG 357.00074544 bcp0100$006$+$3aac
> 704
> 705 RUN
>
BCP0100.PROGXL.AMISYS;XL="XL.PUB.AMISYS,XL.OW.DISC3,xl0707c2.pub.hss,PHL
> IBXLS.PH839C.COGNOS,XLOMNIDX.PUB.SYS,ST2XL.PU
> 706 LAMISYS.PUB.SYS";NMSTACK=1300000
> 707 Program terminated in an error state. (CIERR 976)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
> Raghu Rao
> Preferred Care - Senior Systems Analyst
> 259 Monroe Ave.
> Rochester, NY 14607
> 585.327.5755
>
> Confidentiality Notice:
> The information contained in this electronic message is intended for
the
> exclusive use of the individual or entity named above and may contain
> privileged or confidential information. If the reader of this message
> is not the intended recipient or the employee or agent responsible to
> deliver it to the intended recipient, you are hereby notified that
> dissemination, distribution or copying of this information is
> prohibited. If you have received this communication in error, please
> notify the sender immediately by telephone and destroy the copies you
> received.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
--
"If hard work were such a wonderful thing, you'd think rich people
would have kept it all for themselves" - Lane Kirkland
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
