[svn] 4879: Patch for integration bug.

Revision: 4879
Author: [email protected]
Date: 2009-02-06 13:12:53 -0800 (Fri, 06 Feb 2009)
Log Message:
Patch for integration bug. There was a regression with check-in 4793 when getLayoutBoundsX and getLayoutBoundsY were added to Path. Path now tries to factor in the implicit scale, but in the case of SDK-19154
, when these methods are first called during initial layout, _width and _height are 0 (too early), so we assume a 0 scale, which ends up losing 'measuredX' and 'measuredY' from successive calculations. Evtim will need to refactor slightly and replace with a more robust fix for the long term. Bugs: SDK-19154
. QE Notes: None. Doc Notes: None.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19154
http://bugs.adobe.com/jira/browse/SDK-19154
http://bugs.adobe.com/jira/browse/SDK-19154
http://bugs.adobe.com/jira/browse/SDK-19154
Modified Paths:
flex/sdk/branches/i10/frameworks/projects/flex4/src/mx/graphics/Path.as

Similar Messages

  • [svn] 4878: Patch for integration bug.

    Revision: 4878
    Author: [email protected]
    Date: 2009-02-06 12:56:58 -0800 (Fri, 06 Feb 2009)
    Log Message:
    Patch for integration bug. There was a regression with check-in 4793 when getLayoutBoundsX and getLayoutBoundsY were added to Path. Path now tries to factor in the implicit scale, but in the case of SDK-19154, when these methods are first called during initial layout, _width and _height are 0 (too early), so we assume a 0 scale, which ends up losing 'measuredX' and 'measuredY' from successive calculations.
    Evtim will need to refactor slightly and replace with a more robust fix for the long term.
    Bugs: SDK-19154.
    QE Notes: None.
    Doc Notes: None.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19154
    http://bugs.adobe.com/jira/browse/SDK-19154
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Path.as

  • Has someone applied the one off patch for-ONS bug 5749953 SIGBUS ERROR

    Hello all,
    Env:: 10g on Soalris
    I need to apply the one-off patch for
    Bug:5749953 -- ONS SIGBUS ERROR AFTER INSTALL PATCHSET 10.2.0.3 FOR CRS
    Usually for any CPU we issue opatch apply from the patch directory.
    and its mentioned in the readme.html as well.
    But for this one off patch, there isn't anything mentioned in the readme.html.
    All it says is
    #  6. Patch the Files
    #    6.1 Patch the CRS home files
    #    After unlocking any protected files and saving configuration settings
    #    you are now ready to run opatch using the following command.
    #    As the Oracle Clusterware (CRS) software owner;
    #    % opatch apply -local -oh <CRS_HOME>
    #    Note: In configuration A, invoke this only on one node.
    #    6.2 Patch the RDBMS home files.
    #    Alert: The RDBMS portion can only be applied to an RDBMS home that
    #          has been upgraded to 10.2.0.3.0.
    #    For additional information please read Note.363254.1;
    #    Applying one-off Oracle Clusterware patches in a mixed version home
    #    environment
    #    As the RDBMS software owner;
    #    % opatch apply custom/server/5749953 -local -oh <RDBMS_HOME>
    #    Note: In configuration A, invoke this only on one node.Could someone let me know from where i should give 'opatch apply' if patch.zip files are unzipped in /export/home/oracle/5749953  ? TIA,
    JJ

    The patch can always be installed in 2 ways.
    1. Do a cd and then run opatch
    cd <patchlocation>
    opatch apply
    2. Else specify the patch location as an argument
    opatch apply <full path to the patch i.e the one you do cd above> ...
    Both the above styles yield same result.
    VJ

  • Generic Patchs for 11.2.0.4 WIN 2008

    Hi Friends,
    As per SAP note 1949250 - Oracle 11.2.0: Patches / Patch collections for 11.2.0.4 below are the required Bundel and Generic patches.
    Oracle Database Patch
    Patch ID
    Patch Description
    PATCHBUNDLE11204P_10-20010784.ZIP
    19651773
    Windows 64-bit, Bundle Patch
    PATCHBUNDLE11204P_10-20010783.ZIP
    19651773
    Windows 32-bit, Bundle Patch
    PATCHBUNDLE11204P_7-20010784.ZIP
    18842982
    Windows 64-bit, Bundle Patch
    PATCHBUNDLE11204P_7-20010783.ZIP
    18842982
    Windows 32-bit, Bundle Patch
    p9584028_112040_Generic.zip
    9584028
    Generic, Database Upgrade scripts (SAP Note 1431793)
    p9656644_112040_Generic.zip
    9656644
    Generic, Database Vault scripts (SAP Note 1502374)
    p13724904_112040_Generic.zip
    13724904
    Generic, additional patch
    p17511071_112040_Generic.zip
    17511071
    Generic, additional patch
    p17259786_112040_Generic.zip
    17259786
    Generic, additional patch
    But on service market place I see below patches one patch extra (P18304304GEN11204P_1-20010784.ZIP  Patch 18304304 for Windows 64-bit)
    P13724904GEN11204P_1-20010784.ZIP  Patch 13724904 for Windows   1
    P17259786GEN11204P_1-20010784.ZIP  Patch 17259786 for Windows   1
    P17511071GEN11204P_1-20010784.ZIP  Patch 17511071 for Windows   1
    P18304304GEN11204P_1-20010784.ZIP  Patch 18304304 for Windows 64-bit
    P9584028GEN11204P_1-20010784.ZIP  Patch 9584028 for Windows   1
    P9656644GEN11204P_1-20010784.ZIP  Patch 9656644 for Windows   1
    PATCHBUNDLE11204P_10-20010784.ZIP  Windows Patch Bundle 10 with CPUOct2014
    PATCHBUNDLE11204P_7-20010784.ZIP  Windows Patch Bundle 7 with CPUJul2014
    Can any one please let us know why this generic patch is not mention in SAP Note??  Do we have to apply this Patch 18304304?? if yes why it is not mention in the note?
    Thanks
    Tabrayz

    Hi
    Just have a look to the readme file inside the patch... it is RAC specific, so if if you do not have RAC no need to apply it.
    Regards
    =========================================================================
    Interim Patch for Base Bug: 18304304
    =========================================================================
    Date: 2014 Feb 25 15:12:56 CET
    Platform Patch for          : GENERIC
    Product Patched             : RDBMS
    Product Version #           : 11.2.0.4.0
    RAC Rolling Installable     : YES
    SAP note                    : 1976879
    Bugs Fixed by this patch:
      18304304: SAP SPECIFIC POWERSHELL SCRIPTS FOR MS CLUSTER ENVIRONMENTS

  • [svn:fx-trunk] 13207: Accepted patch for UITextField textHeight property to work around an underlying bug in the player .

    Revision: 13207
    Revision: 13207
    Author:   [email protected]
    Date:     2009-12-23 13:11:43 -0800 (Wed, 23 Dec 2009)
    Log Message:
    Accepted patch for UITextField textHeight property to work around an underlying bug in the player.
    flash.text.TextField does not take into account the leading on the final line of text when measuring itself, yet will scroll if it is not given this extra height. The player has retired this bug.
    Ported componentSmoke test to basicTests.  If this fail it means the player has fixed the bug and we need to remove the workaround.
    QE notes: components/Text/Properties/Text_Properties_tester Checking_Property_textHeight needs to be updated
    Doc notes:
    Bugs: SDK-24461
    Reviewer:
    Tests run: checkintests, mx Label, Panel, TextInput, TextArea and Text
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24461
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UITextField.as
        flex/sdk/trunk/frameworks/tests/basicTests/halo/scripts/TextTestScript.mxml

    Revision: 13207
    Revision: 13207
    Author:   [email protected]
    Date:     2009-12-23 13:11:43 -0800 (Wed, 23 Dec 2009)
    Log Message:
    Accepted patch for UITextField textHeight property to work around an underlying bug in the player.
    flash.text.TextField does not take into account the leading on the final line of text when measuring itself, yet will scroll if it is not given this extra height. The player has retired this bug.
    Ported componentSmoke test to basicTests.  If this fail it means the player has fixed the bug and we need to remove the workaround.
    QE notes: components/Text/Properties/Text_Properties_tester Checking_Property_textHeight needs to be updated
    Doc notes:
    Bugs: SDK-24461
    Reviewer:
    Tests run: checkintests, mx Label, Panel, TextInput, TextArea and Text
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24461
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UITextField.as
        flex/sdk/trunk/frameworks/tests/basicTests/halo/scripts/TextTestScript.mxml

  • [svn] 4610: Commit Josh's patch for 3. x to fix bug SDK-17367 which works around an issue with Dictionary that stops ObjectUtil .toString() working with QNames.

    Revision: 4610
    Author: [email protected]
    Date: 2009-01-21 12:48:01 -0800 (Wed, 21 Jan 2009)
    Log Message:
    Commit Josh's patch for 3.x to fix bug SDK-17367 which works around an issue with Dictionary that stops ObjectUtil.toString() working with QNames.
    QE: Yes, please add a test case to ObjectUtil tests for this scenario.
    Doc: No
    Checkintests: Pass
    Bugs:
    SDK-17367 ObjectUtil.toString(QName) causes RTE
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17367
    http://bugs.adobe.com/jira/browse/SDK-17367
    Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/utils/ObjectUtil.as

    VPN-User,
    Ok - I see the list of issues and will ensure our X300 specialist takes a look at it.   
    Please do understand that while you have put together a very coherent list, I try to ensure priority to threads in which multiple customers are focused on a single issue, as we deliver the most benefit to the community in working on those.   This forum is primarly a peer to peer discussion forum rather than a Lenovo chat / tech support where we try to solve each and every issue put forth.
    Individuals with a long list of issues on a particular machine may find benefit from either contacting technical support and working through their list, or publishing it as you have done and wait for other users of the same system to share their experiences.
    Thanks for your patience
    Mark
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • [svn] 2649: Committing Josh McDonald' s patch for bug SDK-15795 after review and testing.

    Revision: 2649
    Author:   [email protected]
    Date:     2008-07-29 09:33:23 -0700 (Tue, 29 Jul 2008)
    Log Message:
    Committing Josh McDonald's patch for bug SDK-15795 after review and testing. Various minOccurs and maxOccurs scenarios could lead to short circuit logic that would not release the schema stack scope if a reference was previously resolved.
    Checkintests: Pass
    BlazeDS 3.0.x webService flexunit tests: 100% Pass
    BlazeDS 3.0.x webService mxunit tests: 100% Pass
    QE: Yes, please review schema that is described in this bug and consider adding a test case. Note that I'm seeing intermittent failures on a few tests that pass when re-run (likely due to timeouts being too aggressive?).
    Doc: No
    Reviewer: Svetlin
    Bugs:
    SDK-15795 - minOccurs on breaks XMLEncoder
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-15795
        http://bugs.adobe.com/jira/browse/SDK-15795
    Modified Paths:
        flex/sdk/branches/3.0.x/frameworks/projects/rpc/src/mx/rpc/xml/XMLEncoder.as

    Hi.
    Alot of good feedback. Personally I miss some keybindings, such as for branch switching.
    Anyways, on the github corruption issue it seems like this was fixed in 0.8.4 according to http://www.eclipse.org/forums/index.php?t=msg&th=183637& amp;start=0&S=81dfec74c1b979b21614f923fb09b1da

  • [svn:fx-trunk] 11601: Integrating Min' s recent fixes to FXGUtils for a group of attribute parsing bugs and clarification of error messages .

    Revision: 11601
    Author:   [email protected]
    Date:     2009-11-09 22:00:50 -0800 (Mon, 09 Nov 2009)
    Log Message:
    Integrating Min's recent fixes to FXGUtils for a group of attribute parsing bugs and clarification of error messages.
    QE notes: Please confirm test cases.
    Doc notes: N/A
    Bugs:
    SDK-22982 - FXG compiler fails on percentage lineheight inside formatted text content
    SDK-24093 - If a
    tag has children, you do not get a compile error.
    SDK-24092 - You get a compile error if you set justificationStyle="prioritizeLeastAdjustment"
    SDK-24097 - Setting an invalid verticalAlign style on RichText has a typo in the error message
    Reviewer: Min
    Tests run: Checkintests, Bug test cases
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22982
        http://bugs.adobe.com/jira/browse/SDK-24093
        http://bugs.adobe.com/jira/browse/SDK-24092
        http://bugs.adobe.com/jira/browse/SDK-24097
    Modified Paths:
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/fxg/FXGException_en.properties
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/RichTextNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich BlockTextNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich TextLeafNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich TextNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/BRNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/ImgNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/TabNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/TextHelper.j ava
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/text/AbstractCharacte rTextNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/sax/FXGSAXScanner.java

    Dear Pallavi,
    Very useful post!
    I am looking for similar accelerators for
    Software Inventory Accelerator
    Hardware Inventory Accelerator
    Interfaces Inventory
    Customization Assessment Accelerator
    Sizing Tool
    Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
    Request help on such accelerators... Any clues?
    Any reply, help is highly appreciated.
    Regards
    Manish Madhav

  • [svn:fx-trunk] 12972: Commit Catalyst-submitted patch for fixing up unicode path/ file names in ActiveX.

    Revision: 12972
    Revision: 12972
    Author:   [email protected]
    Date:     2009-12-15 15:27:40 -0800 (Tue, 15 Dec 2009)
    Log Message:
    Commit Catalyst-submitted patch for fixing up unicode path/file names in ActiveX.
    QE notes: None.
    Doc notes: None.
    Bugs: SDK-24648
    Reviewer: Alex & I
    Tests run: checkintests
    Is noteworthy for integration: Yes
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24648
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/SWFLoader.as

    Dear Pallavi,
    Very useful post!
    I am looking for similar accelerators for
    Software Inventory Accelerator
    Hardware Inventory Accelerator
    Interfaces Inventory
    Customization Assessment Accelerator
    Sizing Tool
    Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
    Request help on such accelerators... Any clues?
    Any reply, help is highly appreciated.
    Regards
    Manish Madhav

  • [svn:fx-3.x] 10974: Submitting customer patch for SDK-19188.

    Revision: 10974
    Author:   [email protected]
    Date:     2009-10-12 14:56:48 -0700 (Mon, 12 Oct 2009)
    Log Message:
    Submitting customer patch for SDK-19188. Correcting XSD scope lookup while decoding wrapped style document literal responses.
    QE notes: Please add a regression test for this scenario.
    Doc notes: N/A
    Bugs: SDK-19188
    Reviewer: Pete
    Tests run: Checkintests, webtier mxunit, flexunit
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-19188
        http://bugs.adobe.com/jira/browse/SDK-19188
    Modified Paths:
        flex/sdk/branches/3.x/frameworks/projects/rpc/src/mx/rpc/soap/SOAPDecoder.as

  • [svn:fx-trunk] 10898: Fix for a bug: After playing a hide effect, a window wouldn't be visible again.

    Revision: 10898
    Author:   [email protected]
    Date:     2009-10-06 13:54:04 -0700 (Tue, 06 Oct 2009)
    Log Message:
    Fix for a bug: After playing a hide effect, a window wouldn't be visible again.
    The issue here is that all effects that occur because of HIDE end up calling setVisible() (see EffectManager.effectEndHandler).  Window/WindowedApplication was basically left with two concepts of setVisible...the displayObject one and the native application one, and they were out of synch.  So setting visible=true on the window wasn?\226?\128?\153t calling setVisible(true) which controls the display object visibility.  Now instead of doing our work in the visible setter, we override setVisible() and do it in there.
    QE notes: -
    Doc notes: -
    Bugs: SDK-23263
    Reviewer: Darrell
    Tests run: checkintests, Rob ran mustella window/windowedapplication
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23263
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/Window.as
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
        flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/Window.as
        flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/WindowedApplication. as

    I run Suse 9.1 Linux, and Suse has a package called lmsensors which by default on my machine gives readings like this:
    Code: [Select]
    temp1:       +27°C  (high =    +0°C, hyst =   +22°C)   sensor = thermistor
    temp2:     +41.0°C  (high =   +80°C, hyst =   +75°C)   sensor = PII/Celeron diode 
    Now that 41C is pretty high for an idle AMD643000+ running at 1000Mhz, 1.08V. Too high, I would say. temp 1 in this case is the SYS temp, temp2 is the CPU temp.
    Now, using lmsensors I can duplicate your little trick and tell it that temp 2 is in fact a 3904 transistor. Having done this can I get readings like this:
    Code: [Select]
    temp1:       +27°C  (high =    +0°C, hyst =   +22°C)   sensor = thermistor
    temp2:     +16.0°C  (high =   +80°C, hyst =   +75°C)   sensor = 3904 transistor 
    Problem is, I'm not sure that the sensor is actually a 3904 transistor! The number's lower, but I was pretty sure that the sensor in the AMD64 is in fact a diode. Also, surely the CPU temp can't actually be that much lower than the SYS temp.
    So, I think your fix succeeds in giving lower temps and that's great in that it will tell your system software that the CPU is not overheating, but I don't think it's the solution to high temp reporting. Anyway, as you say, its a solution for people who can't run with system shutdowns due to bogus high temps.  
    I've been looking at these temp issues with the MSI K8T, and I was thinking the problem was simply a miscalibration. The Winbond sensor chip on my board (maybe the K8N is the same, maybe not) has a sensor temp offset that gets added to the temp coming from the sensor. On the K8T this number is +54C.   Funny number I know, but I've "fixed" the problem while I wait for a real bios fix on the K8T by simply reducing this offset to give me a CPU temp that matches SYS temp when idle. This enables cool'n'quiet fan control to work properly on my system, which is my main practical concern.

  • How to find description for the bugs fixed in a CPU ( Critical patch alert)

    Hi
    I am having a hell of a time trying to figure out WHICH BUGS are fixed in the recent Critical patch alert
    I looked into the README file of the patch ( in my case its 8534387 for Solaris SPARC ) - but even in the README file there is only the list of the bugs fixed:
    +2.1 Bugs Fixed by This Patch+
    This patch includes the following molecules:
    +7155248 - DB-10.2.0.4-MOLECULE-001-CPUJUL2008+
    +7155249 - DB-10.2.0.4-MOLECULE-002-CPUJUL2008+
    +7155250 - DB-10.2.0.4-MOLECULE-003-CPUJUL2008+
    +7155251 - DB-10.2.0.4-MOLECULE-004-CPUJUL2008+
    +.....+
    +.....+
    But its impossible to even find them in metallink by the bug ID !
    I tried the first one and you get multiple document where this patch is mentioned , but no clear place for the bug description .
    Is there a convenient way to know exactly the DESCRIPTION of each bug that was fixed in a CPU ?
    thanks in advance
    Orna

    >
    But its impossible to even find them in metallink by the bug ID !
    I tried the first one and you get multiple document where this patch is mentioned , but no clear place for the bug description .
    Is there a convenient way to know exactly the DESCRIPTION of each bug that was fixed in a CPU ?
    thanks in advance
    OrnaDo a BUG search using the BUG ID rather than a Knowledge Base search. After that if you look closely at those multiple documents you mentioned that was returned, there should be only one for your Platform and for your product. Ignore the rest and click on only the one relevant to your Platform and Product.

  • Error applying patch for bug 4554072 (APEX 2.2.1 requirement)

    All,
    I am installing APEX 2.2.1 and is trying to apply the patch for bug 4554072. I have checked the OWA version:
    SQL> select owa_util.get_version from dual;
    GET_VERSION
    10.1.2.0.0
    And When I am trying to execute the privht8.sql script I get the following errors:
    SQL> @904x_1012x/privht8.sql
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY HTF:
    LINE/COL ERROR
    19/10 PLS-00323: subprogram or cursor 'TITLE' is declared in a package
    specification and must be defined in the package body
    21/10 PLS-00323: subprogram or cursor 'HTITLE' is declared in a package
    specification and must be defined in the package body
    35/7 PL/SQL: Statement ignored
    35/15 PLS-00307: too many declarations of 'TITLE' match this call
    205/7 PL/SQL: Statement ignored
    205/15 PLS-00307: too many declarations of 'ANCHOR' match this call
    433/7 PL/SQL: Statement ignored
    LINE/COL ERROR
    433/14 PLS-00307: too many declarations of 'EM' match this call
    443/7 PL/SQL: Statement ignored
    443/14 PLS-00307: too many declarations of 'KBD' match this call
    829/7 PL/SQL: Statement ignored
    829/14 PLS-00307: too many declarations of 'TABLEDATA' match this call
    834/7 PL/SQL: Statement ignored
    834/14 PLS-00307: too many declarations of 'TABLEDATA' match this call
    836/7 PL/SQL: Statement ignored
    836/14 PLS-00307: too many declarations of 'TABLEDATA' match this call
    840/8 PL/SQL: Statement ignored
    840/15 PLS-00307: too many declarations of 'TABLEDATA' match this call
    LINE/COL ERROR
    914/9 PL/SQL: Statement ignored
    914/24 PLS-00307: too many declarations of 'ESCAPE_SC' match this call
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY HTP:
    LINE/COL ERROR
    14/11 PLS-00323: subprogram or cursor 'TITLE' is declared in a package
    specification and must be defined in the package body
    15/11 PLS-00323: subprogram or cursor 'HTITLE' is declared in a package
    specification and must be defined in the package body
    1691/7 PL/SQL: Statement ignored
    1691/7 PLS-00307: too many declarations of 'PRINT' match this call
    1694/7 PL/SQL: Statement ignored
    1694/7 PLS-00307: too many declarations of 'PRINT' match this call
    1697/7 PL/SQL: Statement ignored
    LINE/COL ERROR
    1697/7 PLS-00307: too many declarations of 'PRN' match this call
    1700/7 PL/SQL: Statement ignored
    1700/7 PLS-00307: too many declarations of 'PRN' match this call
    1703/7 PL/SQL: Statement ignored
    1703/7 PLS-00307: too many declarations of 'PRINT' match this call
    1706/7 PL/SQL: Statement ignored
    1706/7 PLS-00307: too many declarations of 'PRINT' match this call
    1709/7 PL/SQL: Statement ignored
    1709/7 PLS-00307: too many declarations of 'P' match this call
    1712/7 PL/SQL: Statement ignored
    1712/7 PLS-00307: too many declarations of 'P' match this call
    LINE/COL ERROR
    1715/7 PL/SQL: Statement ignored
    1715/7 PLS-00307: too many declarations of 'P' match this call
    SQL>
    Any ideas? I am hoping that I am just tired and is doing something really stooopid ;-)
    Cheers,
    Andy

    Andy,
    From the README.txt included with that patch:
    - If the PL/SQL Web Toolkit version is either 9.0.4 series or 10.1.2 series and
    the database version is higher than 8.1.7.4
    SQL> @904x_1012x/privht.sql
    SQL> exit
    I’m assuming your database version is higher than 8.1.7.4. If so, then you need to run privht.sql and not privht8.sql.
    Joel

  • [svn:fx-gumbo_beta2] 10472: Fix for Fade bug.

    Revision: 10472
    Author:   [email protected]
    Date:     2009-09-21 15:11:11 -0700 (Mon, 21 Sep 2009)
    Log Message:
    Fix for Fade bug. Previously, Fade assumed that any target object with a 'parent' must be a child of that container. However, a target object can also be the 'mask' property of that parent. When Fade went to query which element the mask was on the parent, the parent threw an RTE because its element list did not contain that target object. The fix was to special-case the mask situation and return 'undefined' for the index value, meaning that the object does not have a parent and will not be tracked as an element that can be removed/added.
    QE notes: None
    Doc notes: None
    Bugs: SDK-23327
    Reviewer: Jason
    Tests run: checkintests, Mustella effects/Fade, manual tests
    Is noteworthy for integration: Yes
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23327
    Modified Paths:
        flex/sdk/branches/gumbo_beta2/frameworks/projects/spark/src/spark/effects/Fade.as

  • [svn:fx-trunk] 12370: Fix for doc bug FLEXDOCS-1150

    Revision: 12370
    Revision: 12370
    Author:   [email protected]
    Date:     2009-12-02 08:48:37 -0800 (Wed, 02 Dec 2009)
    Log Message:
    Fix for doc bug FLEXDOCS-1150
    Added a few new examples and default sizes to Spark components
    QE notes: -
    Doc notes: -
    Bugs: -
    Reviewer: -
    Tests run: - FLEXDOCS-1150
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FLEXDOCS-1150
        http://bugs.adobe.com/jira/browse/FLEXDOCS-1150
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/formatters/DateFormatter.as
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/BorderCont ainerExample.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/VScrollBar Example.mxml
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Application.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/BorderContainer.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/ComboBox.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DataGroup.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DropDownList.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Group.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/HGroup.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Label.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/NavigatorContent.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Panel.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/SkinnableContainer.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/SkinnableDataContainer.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TabBar.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TextInput.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TileGroup.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VGroup.as
    Added Paths:
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/Applicatio nContainerExample.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/HScrollBar Example.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/MyBorderSk in.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/SkinnableC ontainerExample.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/SkinnableD ataContainerExample.mxml

Maybe you are looking for