Application Builder (Bug)- Edit Region Comment getting ORA-01461

When i edit a Region and saving it with a long comment (5366 chars) iam getting this error
Fehler beim Verarbeiten von Zeile.
ORA-01461: Ein LONG-Wert kann nur zur Einfügung in eine LONG-Spalte gebunden werden
We are using Application Express 4.1.0.00.32 in that specific project.
On apex.oracle.com in Version Application Express 4.2.0.00.27 this error occurs also.

Hi Oliver,
comment attributes do normally only save up to 4000 characters. I will file a bug to restrict the textarea to 4000 chars.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Similar Messages

Application Builder Bug?

I created a Calendar region in an application on htmldb.oracle.com (version 2.0.0.00.49), resulting in the creation of 3 region buttons: "Previous", "Today" and "Next", displayed on the page definition screen in this order but all with sequence number 30.
In the Application Builder>Application>Page Definition>Edit Page Buttons screen, I made a change to the "Previous" button and then clicked the [>] button to move to the next button definition. This displayed the Edit Page Buttons screen for the "Today" button, but the [>] button was not available to move to the "Next" button. Similarly, in the "Next" button definition, the [<] button isn't available to move to the preceding "Today" button.
Not a massive issue, but a bit awkward.

Hi Oliver,
comment attributes do normally only save up to 4000 characters. I will file a bug to restrict the textarea to 4000 chars.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Quick Application Builder - Quick Application Builder Released

DatawareStudio.com is proud to announce the immediate availability of
Quick Application Suite and Quick Application Builder.
Developed by DotSolutions s.r.l, QaS and QaB dramatically simplify the process of
creating and maintaining a web-based complex application for every day usage.
Their's unique features make Quick Application family the fastest web application
development tools on earth.
Tested with most widley used portals and database servers, both open source and
commercial, they allow web developers to build a complete application, comprehensive of
strong data entry controls and impressive reports in a bunch of minutes.
You can combine them with leading Data Warehousing technology like Pentaho, SpagoBI or
JasperIntelligence to add exclusive data entry characteristic to your dashboard.
Their tide integration with Pentaho Data Integration (previosly known as Kettle) allows
power users to add complex back end control logic every time is needed.
Or you can use them alone, just a WebPortal like Liferay, Jahia, Jboss Portal,
ExoPlatform, Jetspeed, to create all the applications your society requires.
And all can be done without writing a single line of html/java/jsp/php/asp code, thank's
to a flexible user interface and standard sql syntax.
You can download Quick Application Builder community Edition for MySQL and PostgreSql at this URL:
[www.datawarestudio.com|http://www.datawarestudio.com]

I tried opening all the vi's in a stripped down project, doing a "save as" on each before closing them all and then did a build which failed in the same way.
I also tried creating a .lvlib library file, added the vi's to it and got the same build failure.
I did manage to get a NI SRV # opened to get support on this issue. I've attached a zip file of the reduced project that I send to NI, if anyone's interested.
In the CfgIni2Cluster.vi if I remove one of the last two remaining cases, the error changes to one referring to "Config Data Refnum.vi" in the same library, "config.llb".
In this case the "Build errors" dialog box shows the following:
The build was unsuccessful.
Possible reasons
Error copying files.
Source: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\config.llb\Config Data RefNum
Destination: C:\ECL\builds\FlashTest\L&S Flashlight Test\internal.llb\Config Data RefNum
Invoke Node in AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Set Path</b>
Details
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1051 occurred at AB_Source_VI.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: A LabVIEW file of that name already exists in memory, or exists within a project library already in memory.
Thanks for your comments and ideas.
Sincerely,
Mark
Attachments:
NITest10.zip ‏39 KB

Application Builder problem on one server but not another

I am having an Application Builder problem. When I get into App Express and go inside the builder and try to edit a listed application, I get an “http 404 the page cannot be found. The page might have had its name changed or is temporarily unavailable” situation. I can get into SQL commands, utilities, and administrative activities. I can also run the application. Also, if I go onto a different server with App Express on it, I can get into the builder and edit applications with no trouble. Our DBA had the server in question rebooted a little over a week ago and that took care of the problem for a couple days. Any ideas? Is this an Express problem or a server problem? He had also tried restarting Express before he had the reboot done and that didn’t help.
Thank you for any help.
Cordially,
Robert J. Smith

I have messages from the Apache error log files from the dates I was getting the builder error. For future reference, I will post them below. The builder has been working fine lately.
Robert Smith
** error log messages follow **
[Mon Jul 16 07:25:12 2007] [error] [client 147.159.5.134] [ecid:
79143788610,1] File does not exist:
/app/oracle/oraappsrv10g/forms/java/java/awt/KeyboardFocusManager.class
[Mon Jul 16 07:25:12 2007] [error] [client 147.159.5.134] [ecid:
79143788611,1] File does not exist:
/app/oracle/oraappsrv10g/forms/java/java/awt/event/MouseWheelListener.class
[Mon Jul 16 07:25:13 2007] [error] [client 147.159.5.134] [ecid:
83438757083,1] File does not exist:
/app/oracle/oraappsrv10g/forms/java/oracle/forms/registry/default.dat

How to insert a widget in a editable region from a template

Hi there,
ok so basically I am trying to create a HTML page from a template i have already designed.
when I try to insert a widget (Lightbox Gallery) in the editable region I get the following error.
"the widget requires code that must be inserted into the head of the document. insertion cannot happen because this document is read only"
I saw a previous thread (http://forums.adobe.com/thread/901299) that had the same problem with a solution but cant seem to make sense of it.
Not exactly sure where and what to paste in the header of the HTML page.
Any help will be much appreciated.
Thanks

Hi Murray,
ha funny you would say that is the exact answer you would give me seeing you posted it
I understand the logic behind it though not sure what i need to copy and where.
Basically i craeted a "dummy page" and inserted the widget-no problem there.
next step- what code do i copy from the dummy page and where do i paste it? in the template or HTML page.
Dummy HTML with widget code
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Untitled Document</title>
<script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/jquery.js" type="text/javascript"></script>
<script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/lightbox.js" type="text/javascript"></script>
<link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/lightbox.css" rel="stylesheet" type="text/css" />
<link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/sample_lightbox_layout.css" rel="stylesheet" type="text/css" />
<style type="text/css">
/* BeginOAWidget_Instance_2127022: #gallery */
                    .lbGallery {
                              /*gallery container settings*/
                              background-color: #CCC;
                              padding-left: 20px;
                              padding-top: 20px;
                              padding-right: 20px;
                              padding-bottom: 20px;
                              width: 540px;
                              height: auto;
                              text-align:left;
                    .lbGallery ul { list-style: none; margin:0;padding:0; }
                    .lbGallery ul li { display: inline;margin:0;padding:0; }
                    .lbGallery ul li a{text-decoration:none;}
                    .lbGallery ul li a img {
                              /*border color, width and margin for the images*/
                              border-color: #3e3e3e;
                              border-left-width: 10px;
                              border-top-width: 10px;
                              border-right-width: 10px;
                              border-bottom-width: 20px;
                              margin-left:5px;
                              margin-right:5px;
                              margin-top:5px;
                              margin-bottom:5px:
                    .lbGallery ul li a:hover img {
                              /*background color on hover*/
                              border-color: #ffffff;
                              border-left-width: 10px;
                              border-top-width: 10px;
                              border-right-width: 10px;
                              border-bottom-width: 20px;
                    #lightbox-container-image-box {
                              border-top: 0px none #ffffff;
                              border-right: 0px none #ffffff;
                              border-bottom: 0px none #ffffff;
                              border-left: 0px none #ffffff;
                    #lightbox-container-image-data-box {
                              border-top: 0px;
                              border-right: 0px none #ffffff;
                              border-bottom: 0px none #ffffff;
                              border-left: 0px none #ffffff;
/* EndOAWidget_Instance_2127022 */
</style>
<script type="text/xml">

</script>
</head>
<body>
<div id="gallery" class="lbGallery">
<ul>
    <li> <a href="/images/lightboxdemo1.jpg" title=""><img src="/images/lightboxdemo_thumb1.jpg" width="72" height="72" alt="Flower" /></a> </li>
    <li> <a href="/images/lightboxdemo2.jpg" title=""><img src="/images/lightboxdemo_thumb2.jpg" width="72" height="72" alt="Tree" /></a> </li>
    <li> <a href="/images/lightboxdemo3.jpg" title=""><img src="/images/lightboxdemo_thumb3.jpg" width="72" height="72" alt="" /></a> </li>
    <li> <a href="/images/lightboxdemo4.jpg" title=""><img src="/images/lightboxdemo_thumb4.jpg" width="72" height="72" alt="" /></a> </li>
    <li> <a href="/images/lightboxdemo5.jpg" title=""><img src="/images/lightboxdemo_thumb5.jpg" width="72" height="72" alt="" /></a> </li>
</ul>
</div>
<script type="text/javascript">
// BeginOAWidget_Instance_2127022: #gallery
                    $(function(){
                              $('#gallery a').lightBox({
                                        imageLoading:                              '/images/lightbox/lightbox-ico-loading.gif',                    // (string) Path and the name of the loading icon
                                        imageBtnPrev:                              '/images/lightbox/lightbox-btn-prev.gif',                              // (string) Path and the name of the prev button image
                                        imageBtnNext:                              '/images/lightbox/lightbox-btn-next.gif',                              // (string) Path and the name of the next button image
                                        imageBtnClose:                              '/images/lightbox/lightbox-btn-close.gif',                    // (string) Path and the name of the close btn
                                        imageBlank:                                        '/images/lightbox/lightbox-blank.gif',                              // (string) Path and the name of a blank image (one pixel)
                                        fixedNavigation:                    false,                    // (boolean) Boolean that informs if the navigation (next and prev button) will be fixed or not in the interface.
                                        containerResizeSpeed:          400,                               // Specify the resize duration of container image. These number are miliseconds. 400 is default.
                                        overlayBgColor:                     "#999999",                    // (string) Background color to overlay; inform a hexadecimal value like: #RRGGBB. Where RR, GG, and BB are the hexadecimal values for the red, green, and blue values of the color.
                                        overlayOpacity:                              .6,                    // (integer) Opacity value to overlay; inform: 0.X. Where X are number from 0 to 9
                                        txtImage:                                        'Image',                                        //Default text of image
                                        txtOf:                                                  'of'
// EndOAWidget_Instance_2127022
</script>
</body>
</html>
thanks again

Application builder exe does not load excel

I have used application property node and invoke node to cerate a set of VIs that read and write data to an Excel sperad sheet. This works fine in when running in LabVIEW, however when I run myApp.exe as build from application builder, the data does not get logged to Excel. The file dialog appears to open the XL Spreadsheet but not data gets logged nor is any error reported?
What is going on? All the VI are in the same project folder? Is there some additional addon run-time the must be installed on the target machine? I am uisng LabVIEW 2012 on the development station with Win7 Pro and Office 2010 on both the devleopment station and the target system. Is there one document that describes using Application Builder? It was not clear that I needed both LabVIEW and VISA run-time engines to get my application.exe to run on the target. Is there something simialr I must do to get Office to work as well?

I was finally able to track this back through by starting from scratch and received an error code, which led me to this post:
https://forums.ni.com/t5/LabVIEW/Error-2147319779-Excel-ActiveX-and-Broken-LabVIEW-Icon/td-p/2354776
Deleting the "1.7" items solved the problem.

Duplicating an Editable Region

Is it possible to duplicate an editable region without
getting the error "Duplicate editable regions found". I need to
duplicate the content in one editable region multiple times. I have
Windows XP SP2, version 7.0.1. Thanks!

Are you interested in duplicating the region or the region's
contents? If
the latter just copy and paste it as many times as you
need...
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Acta non verba" <[email protected]> wrote
in message
news:e6skvq$cla$[email protected]..
> Is it possible to duplicate an editable region without
getting the error
> "Duplicate editable regions found". I need to duplicate
the content in one
> editable region multiple times. I have Windows XP SP2,
version 7.0.1.
> Thanks!
>

Nothing in Application builder

For some reason my applications from the Application Builder got wiped, on Oracle's site. The applications are showing under the Recent section, and run just fine. When I opt to copy the application, it puts a copy in the Recent section, but not in the Application Builder. How do I get my apps back where they are supposed to be?

James,
For some reason my applications from the Application Builder got wiped,...
Actually, you don't know what happened and as you can still run them, that description would seem to be incorrect.
Did you set any of the applications' Build Status to Run Only?
What's the name of your workspace? I'll check it.
Scott

Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
   (     "MICRO" VARCHAR2(4),
     "PRIM" VARCHAR2(4),
     "UNIT" NUMBER,
     "SEC_REF_1" NUMBER,
     "SECN_1" VARCHAR2(88),
     "SEC_REF_2" NUMBER,
     "SECN_2" VARCHAR2(88),
     "SEC_REF_3" NUMBER,
     "SECN_3" VARCHAR2(88),
     "SEC_REF_4" NUMBER,
     "SECN_4" VARCHAR2(88),
     "SEC_REF_5" NUMBER,
     "SECN_5" VARCHAR2(88),
     "SEC_REF_6" NUMBER,
     "SECN_6" VARCHAR2(88),
     "SEC_REF_7" NUMBER,
     "SECN_7" VARCHAR2(88),
     "SEC_REF_8" NUMBER,
     "SECN_8" VARCHAR2(88),
     "SEC_REF_9" NUMBER,
     "SECN_9" VARCHAR2(88),
     "SEC_REF_10" NUMBER,
     "SECN_10" VARCHAR2(88),
     "SEC_REF_11" NUMBER,
     "SECN_11" VARCHAR2(88),
     "SEC_REF_12" NUMBER,
     "SECN_12" VARCHAR2(88),
     "SEC_REF_13" NUMBER,
     "SECN_13" VARCHAR2(88),
     "SEC_REF_14" NUMBER,
     "SECN_14" VARCHAR2(88),
     "SEC_REF_15" NUMBER,
     "SECN_15" VARCHAR2(88),
     "SEC_REF_16" NUMBER,
     "SECN_16" VARCHAR2(88),
     "SEC_REF_17" NUMBER,
     "SECN_17" VARCHAR2(88),
     "SEC_REF_18" NUMBER,
     "SECN_18" VARCHAR2(88),
     "SEC_REF_19" NUMBER,
     "SECN_19" VARCHAR2(88),
     "SEC_REF_20" NUMBER,
     "SECN_20" VARCHAR2(88),
     "SEC_REF_21" NUMBER,
     "SECN_21" VARCHAR2(88),
     "SEC_REF_22" NUMBER,
     "SECN_22" VARCHAR2(88),
     "SEC_REF_23" NUMBER,
     "SECN_23" VARCHAR2(88),
     "SEC_REF_24" NUMBER,
     "SECN_24" VARCHAR2(88),
     "SEC_REF_25" NUMBER,
     "SECN_25" VARCHAR2(88),
     "SEC_REF_26" NUMBER,
     "SECN_26" VARCHAR2(88),
     "SEC_REF_27" NUMBER,
     "SECN_27" VARCHAR2(88),
     "SEC_REF_28" NUMBER,
     "SECN_28" VARCHAR2(88),
     "SEC_REF_29" NUMBER,
     "SECN_29" VARCHAR2(88),
     "SEC_REF_30" NUMBER,
     "SECN_30" VARCHAR2(88),
     "SEC_REF_31" NUMBER,
     "SECN_31" VARCHAR2(88),
     "SEC_REF_32" NUMBER,
     "SECN_32" VARCHAR2(88),
     "SEC_REF_33" NUMBER,
     "SECN_33" VARCHAR2(88),
     "SEC_REF_34" NUMBER,
     "SECN_34" VARCHAR2(88),
     "SEC_REF_35" NUMBER,
     "SECN_35" VARCHAR2(88),
     "SEC_REF_36" NUMBER,
     "SECN_36" VARCHAR2(88),
     "SEC_REF_37" NUMBER,
     "SECN_37" VARCHAR2(88),
     "SEC_REF_38" NUMBER,
     "SECN_38" VARCHAR2(88),
     "SEC_REF_39" NUMBER,
     "SECN_39" VARCHAR2(88),
     "SEC_REF_40" NUMBER,
     "SECN_40" VARCHAR2(88),
     "SEC_REF_41" NUMBER,
     "SECN_41" VARCHAR2(88),
     "SEC_REF_42" NUMBER,
     "SECN_42" VARCHAR2(88),
     "SEC_REF_43" NUMBER,
     "SECN_43" VARCHAR2(88),
     "SEC_REF_44" NUMBER,
     "SECN_44" VARCHAR2(88),
     "SEC_REF_45" NUMBER,
     "SECN_45" VARCHAR2(88),
     "SEC_REF_46" NUMBER,
     "SECN_46" VARCHAR2(88),
     "SEC_REF_47" NUMBER,
     "SECN_47" VARCHAR2(88),
     "SEC_REF_48" NUMBER,
     "SECN_48" VARCHAR2(88),
     "SEC_REF_49" NUMBER,
     "SECN_49" VARCHAR2(88),
     "SEC_REF_50" NUMBER,
     "SECN_50" VARCHAR2(88),
     "SEC_REF_51" NUMBER,
     "SECN_51" VARCHAR2(88),
     "SEC_REF_52" NUMBER,
     "SECN_52" VARCHAR2(88),
     "SEC_REF_53" NUMBER,
     "SECN_53" VARCHAR2(88),
     "SEC_REF_54" NUMBER,
     "SECN_54" VARCHAR2(88),
     "SEC_REF_55" NUMBER,
     "SECN_55" VARCHAR2(88),
     "SEC_REF_56" NUMBER,
     "SECN_56" VARCHAR2(88),
     "SEC_REF_57" NUMBER,
     "SECN_57" VARCHAR2(88),
     "SEC_REF_58" NUMBER,
     "SECN_58" VARCHAR2(88),
     "SEC_REF_59" NUMBER,
     "SECN_59" VARCHAR2(88),
     "SEC_REF_60" NUMBER,
     "SECN_60" VARCHAR2(88),
     "SEC_REF_61" NUMBER,
     "SECN_61" VARCHAR2(88),
     "SEC_REF_62" NUMBER,
     "SECN_62" VARCHAR2(88),
     "SEC_REF_63" NUMBER,
     "SECN_63" VARCHAR2(88),
     "SEC_REF_64" NUMBER,
     "SECN_64" VARCHAR2(88),
     "SEC_REF_65" NUMBER,
     "SECN_65" VARCHAR2(88),
     "SEC_REF_66" NUMBER,
     "SECN_66" VARCHAR2(88),
     "SEC_REF_67" NUMBER,
     "SECN_67" VARCHAR2(88),
     "SEC_REF_68" NUMBER,
     "SECN_68" VARCHAR2(88),
     "SEC_REF_69" NUMBER,
     "SECN_69" VARCHAR2(88),
     "SEC_REF_70" NUMBER,
     "SECN_70" VARCHAR2(88),
     "SEC_REF_71" NUMBER,
     "SECN_71" VARCHAR2(88),
     "SEC_REF_72" NUMBER,
     "SECN_72" VARCHAR2(88),
     "SEC_REF_73" NUMBER,
     "SECN_73" VARCHAR2(88),
     "SEC_REF_74" NUMBER,
     "SECN_74" VARCHAR2(88),
     "SEC_REF_75" NUMBER,
     "SECN_75" VARCHAR2(88),
     "SEC_REF_76" NUMBER,
     "SECN_76" VARCHAR2(88),
     "SEC_REF_77" NUMBER,
     "SECN_77" VARCHAR2(88),
     "SEC_REF_78" NUMBER,
     "SECN_78" VARCHAR2(88),
     "SEC_REF_79" NUMBER,
     "SECN_79" VARCHAR2(88),
     "SEC_REF_80" NUMBER,
     "SECN_80" VARCHAR2(88),
     "SEC_REF_81" NUMBER,
     "SECN_81" VARCHAR2(88),
     "SEC_REF_82" NUMBER,
     "SECN_82" VARCHAR2(88),
     "SEC_REF_83" NUMBER,
     "SECN_83" VARCHAR2(88),
     "SEC_REF_84" NUMBER,
     "SECN_84" VARCHAR2(88),
     "SEC_REF_85" NUMBER,
     "SECN_85" VARCHAR2(88),
     "SEC_REF_86" NUMBER,
     "SECN_86" VARCHAR2(88),
     "SEC_REF_87" NUMBER,
     "SECN_87" VARCHAR2(88),
     "SEC_REF_88" NUMBER,
     "SECN_88" VARCHAR2(88),
     "SEC_REF_89" NUMBER,
     "SECN_89" VARCHAR2(88),
     "SEC_REF_90" NUMBER,
     "SECN_90" VARCHAR2(88),
     "SEC_REF_91" NUMBER,
     "SECN_91" VARCHAR2(88),
     "SEC_REF_92" NUMBER,
     "SECN_92" VARCHAR2(88),
     "SEC_REF_93" NUMBER,
     "SECN_93" VARCHAR2(88),
     "SEC_REF_94" NUMBER,
     "SECN_94" VARCHAR2(88),
     "SEC_REF_95" NUMBER,
     "SECN_95" VARCHAR2(88),
     "SEC_REF_96" NUMBER,
     "SECN_96" VARCHAR2(88),
     "SEC_REF_97" NUMBER,
     "SECN_97" VARCHAR2(88),
     "SEC_REF_98" NUMBER,
     "SECN_98" VARCHAR2(88),
     "SEC_REF_99" NUMBER,
     "SECN_99" VARCHAR2(88),
     "SEC_REF_100" NUMBER,
     "SECN_100" VARCHAR2(88),
     "SEC_REF_101" NUMBER,
     "SECN_101" VARCHAR2(88),
     "SEC_REF_102" NUMBER,
     "SECN_102" VARCHAR2(88),
     "SEC_REF_103" NUMBER,
     "SECN_103" VARCHAR2(88),
     "SEC_REF_104" NUMBER,
     "SECN_104" VARCHAR2(88),
     "SEC_REF_105" NUMBER,
     "SECN_105" VARCHAR2(88),
     "SEC_REF_106" NUMBER,
     "SECN_106" VARCHAR2(88),
     "SEC_REF_107" NUMBER,
     "SECN_107" VARCHAR2(88),
     "SEC_REF_108" NUMBER,
     "SECN_108" VARCHAR2(88),
     "SEC_REF_109" NUMBER,
     "SECN_109" VARCHAR2(88),
     "SEC_REF_110" NUMBER,
     "SECN_110" VARCHAR2(88),
     "SEC_REF_111" NUMBER,
     "SECN_111" VARCHAR2(88),
     "SEC_REF_112" NUMBER,
     "SECN_112" VARCHAR2(88),
     "SEC_REF_113" NUMBER,
     "SECN_113" VARCHAR2(88),
     "SEC_REF_114" NUMBER,
     "SECN_114" VARCHAR2(88),
     "SEC_REF_115" NUMBER,
     "SECN_115" VARCHAR2(88),
     "SEC_REF_116" NUMBER,
     "SECN_116" VARCHAR2(88),
     "SEC_REF_117" NUMBER,
     "SECN_117" VARCHAR2(88),
     "SEC_REF_118" NUMBER,
     "SECN_118" VARCHAR2(88),
     "SEC_REF_119" NUMBER,
     "SECN_119" VARCHAR2(88),
     "SEC_REF_120" NUMBER,
     "SECN_120" VARCHAR2(88),
     "SEC_REF_121" NUMBER,
     "SECN_121" VARCHAR2(88),
     "SEC_REF_122" NUMBER,
     "SECN_122" VARCHAR2(88),
     "SEC_REF_123" NUMBER,
     "SECN_123" VARCHAR2(88),
     "SEC_REF_124" NUMBER,
     "SECN_124" VARCHAR2(88),
     "SEC_REF_125" NUMBER,
     "SECN_125" VARCHAR2(88),
     "SEC_REF_126" NUMBER,
     "SECN_126" VARCHAR2(88),
     "SEC_REF_127" NUMBER,
     "SECN_127" VARCHAR2(88),
     "SEC_REF_128" NUMBER,
     "SECN_128" VARCHAR2(88),
     "SEC_REF_129" NUMBER,
     "SECN_129" VARCHAR2(88),
     "SEC_REF_130" NUMBER,
     "SECN_130" VARCHAR2(88),
     "SEC_REF_131" NUMBER,
     "SECN_131" VARCHAR2(88),
     "SEC_REF_132" NUMBER,
     "SECN_132" VARCHAR2(88),
     "SEC_REF_133" NUMBER,
     "SECN_133" VARCHAR2(88),
     "SEC_REF_134" NUMBER,
     "SECN_134" VARCHAR2(88),
     "SEC_REF_135" NUMBER,
     "SECN_135" VARCHAR2(88),
     "SEC_REF_136" NUMBER,
     "SECN_136" VARCHAR2(88),
     "SEC_REF_137" NUMBER,
     "SECN_137" VARCHAR2(88),
     "SEC_REF_138" NUMBER,
     "SECN_138" VARCHAR2(88),
     "SEC_REF_139" NUMBER,
     "SECN_139" VARCHAR2(88),
     "SEC_REF_140" NUMBER,
     "SECN_140" VARCHAR2(88),
     "SEC_REF_141" NUMBER,
     "SECN_141" VARCHAR2(88),
     "SEC_REF_142" NUMBER,
     "SECN_142" VARCHAR2(88),
     "SEC_REF_143" NUMBER,
     "SECN_143" VARCHAR2(88),
     "SEC_REF_144" NUMBER,
     "SECN_144" VARCHAR2(88),
     "SEC_REF_145" NUMBER,
     "SECN_145" VARCHAR2(88),
     "SEC_REF_146" NUMBER,
     "SECN_146" VARCHAR2(88),
     "SEC_REF_147" NUMBER,
     "SECN_147" VARCHAR2(88),
     "SEC_REF_148" NUMBER,
     "SECN_148" VARCHAR2(88),
     "SEC_REF_149" NUMBER,
     "SECN_149" VARCHAR2(88),
     "SEC_REF_150" NUMBER,
     "SECN_150" VARCHAR2(88),
     "SEC_REF_151" NUMBER,
     "SECN_151" VARCHAR2(88),
     "SEC_REF_152" NUMBER,
     "SECN_152" VARCHAR2(88),
     "SEC_REF_153" NUMBER,
     "SECN_153" VARCHAR2(88),
     "SEC_REF_154" NUMBER,
     "SECN_154" VARCHAR2(88),
     "SEC_REF_155" NUMBER,
     "SECN_155" VARCHAR2(88),
     "SEC_REF_156" NUMBER,
     "SECN_156" VARCHAR2(88),
     "SEC_REF_157" NUMBER,
     "SECN_157" VARCHAR2(88),
     "SEC_REF_158" NUMBER,
     "SECN_158" VARCHAR2(88),
     "SEC_REF_159" NUMBER,
     "SECN_159" VARCHAR2(88),
     "SEC_REF_160" NUMBER,
     "SECN_160" VARCHAR2(88),
     "SEC_REF_161" NUMBER,
     "SECN_161" VARCHAR2(88),
     "SEC_REF_162" NUMBER,
     "SECN_162" VARCHAR2(88),
     "SEC_REF_163" NUMBER,
     "SECN_163" VARCHAR2(88),
     "SEC_REF_164" NUMBER,
     "SECN_164" VARCHAR2(88),
     "SEC_REF_165" NUMBER,
     "SECN_165" VARCHAR2(88),
     "SEC_REF_166" NUMBER,
     "SECN_166" VARCHAR2(88),
     "SEC_REF_167" NUMBER,
     "SECN_167" VARCHAR2(88),
     "SEC_REF_168" NUMBER,
     "SECN_168" VARCHAR2(88),
     "SEC_REF_169" NUMBER,
     "SECN_169" VARCHAR2(88),
     "SEC_REF_170" NUMBER,
     "SECN_170" VARCHAR2(88),
     "SEC_REF_171" NUMBER,
     "SECN_171" VARCHAR2(88),
     "SEC_REF_172" NUMBER,
     "SECN_172" VARCHAR2(88),
     "SEC_REF_173" NUMBER,
     "SECN_173" VARCHAR2(88),
     "SEC_REF_174" NUMBER,
     "SECN_174" VARCHAR2(88),
     "SEC_REF_175" NUMBER,
     "SECN_175" VARCHAR2(88),
     "SEC_REF_176" NUMBER,
     "SECN_176" VARCHAR2(88),
     "SEC_REF_177" NUMBER,
     "SECN_177" VARCHAR2(88),
     "SEC_REF_178" NUMBER,
     "SECN_178" VARCHAR2(88),
     "SEC_REF_179" NUMBER,
     "SECN_179" VARCHAR2(88),
     "SEC_REF_180" NUMBER,
     "SECN_180" VARCHAR2(88),
     "SEC_REF_181" NUMBER,
     "SECN_181" VARCHAR2(88),
     "SEC_REF_182" NUMBER,
     "SECN_182" VARCHAR2(88),
     "SEC_REF_183" NUMBER,
     "SECN_183" VARCHAR2(88),
     "SEC_REF_184" NUMBER,
     "SECN_184" VARCHAR2(88),
     "SEC_REF_185" NUMBER,
     "SECN_185" VARCHAR2(88),
     "SEC_REF_186" NUMBER,
     "SECN_186" VARCHAR2(88),
     "SEC_REF_187" NUMBER,
     "SECN_187" VARCHAR2(88),
     "SEC_REF_188" NUMBER,
     "SECN_188" VARCHAR2(88),
     "SEC_REF_189" NUMBER,
     "SECN_189" VARCHAR2(88),
     "SEC_REF_190" NUMBER,
     "SECN_190" VARCHAR2(88),
     "SEC_REF_191" NUMBER,
     "SECN_191" VARCHAR2(88),
     "SEC_REF_192" NUMBER,
     "SECN_192" VARCHAR2(88),
     "SEC_REF_193" NUMBER,
     "SECN_193" VARCHAR2(88),
     "SEC_REF_194" NUMBER,
     "SECN_194" VARCHAR2(88),
     "SEC_REF_195" NUMBER,
     "SECN_195" VARCHAR2(88),
     "SEC_REF_196" NUMBER,
     "SECN_196" VARCHAR2(88),
     "SEC_REF_197" NUMBER,
     "SECN_197" VARCHAR2(88),
     "SEC_REF_198" NUMBER,
     "SECN_198" VARCHAR2(88),
     "SEC_REF_199" NUMBER,
     "SECN_199" VARCHAR2(88),
     "SEC_REF_200" NUMBER,
     "SECN_200" VARCHAR2(88),
     "SEC_REF_201" NUMBER,
     "SECN_201" VARCHAR2(88),
     "SEC_REF_202" NUMBER,
     "SECN_202" VARCHAR2(88),
     "SEC_REF_203" NUMBER,
     "SECN_203" VARCHAR2(88),
     "SEC_REF_204" NUMBER,
     "SECN_204" VARCHAR2(88),
     "SEC_REF_205" NUMBER,
     "SECN_205" VARCHAR2(88),
     "SEC_REF_206" NUMBER,
     "SECN_206" VARCHAR2(88),
     "SEC_REF_207" NUMBER,
     "SECN_207" VARCHAR2(88),
     "SEC_REF_208" NUMBER,
     "SECN_208" VARCHAR2(88)
   );Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PM

So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil?

Display Bug in LV 8.20 Application Builder

There seems to be a minor bug in the displaying of the "VI Settings" in the application builder for LabVIEW 8.20.
The problem is in an executable build spec, in the "Source File Settings" category.
Select a sub VI in the tree, then uncheck the select box for the "Remove Panel" property. Now select any other VI in the tree, then go back to the one you unchecked the "Remove Panel" box. You should see that the box is now checked.
If you don't do anything else and just select "OK, then go back into the build spec, you'll see that the property was correctly saved as unchecked. So it looks like it's just a display problem.
I've made sure the VI I try this with does not use any property nodes and it is not marked as a dynamic VI. I can reproduce this on two machines running Windows XP Pro SP2 and LabVIEW 8.20.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

In addition to Ed's
comment, I would like to say that this unexpected behaviour is not
always appearing. I have just seen following while editing this text :
I have unchecked the Remove Panel box for all the UI VIs (all are
located in the same directory). When scrolling through the different UI
VIs in the Soure File Settings, the box was unchecked for all the VIs.
Without closing the Source File Settings window, I switched to
Developer Zone and switched back to the Source File Settings. For some
UI VIs, the Remove Panel box was checked. I closed the window and
opened it again, the box was unchecked again for all the UI VIs.
But I have also encountered the case that when scrolling through the
VIs to try to uncheck this setting for all of them, it suddenly appears
checked again for a VI for which it was unchecked or unchecked for a
before checked VI.
You finally end with a very unclear situation and it may be that the
Remove Panel is really checked for some VIs. At least, in some cases,
the built EXE could not run because of missing front panels. I can't
remember the exact error messages when running the EXE but they
mentionned the name of the VI and something about missing ressources. I
opened the .lvproj file and noticed that the "Remove Panel" property of
these VIs was set to TRUE. After modifying these settings and
rebuilding the EXE, it ran as expected.
In development, I
normally uncheck "Allow user to resize window" of the UI VIs because
this setting can unfortunately not be changed when configuring the
executable. In the "Source File Settings" I uncheck all options of "Use
VI Setting" for these UI VIs and I only check "Auto-Center" (all VIs)
and "Window is Modal" (some VIs).
There is another problem with the application builder that I would like
to mention. For (at least) following settings, the development settings
of a VI will not be overwritten by the Source File Settings when
building the executable :
- Window has title bar
- Show Menu bar
- Show Toolbar
- Show Scroll Bars
This is also very annoying because you will need to change these
settings in the development environement in order to get the expected
appearance in the executable.
LV8.2 English / WXP SP2

Application Builder page ORA-06502

I'm having the same problem as described in this old thread that doesn't seem to have been resolved:
application builder page error ORA-06502
After logging in, I click Application Builder and get this error message three times:
report error:
ORA-06502: PL/SQL: numeric or value error: NULL index table key value
On the main part of the page where there should be a bunch of icons for each of the applications, and also on the right in the boxes labeled "Recent" and "Application Groups". The URL states that I'm in application 4000, page 1500. Using info from the old thread I tried changing the view option of the report from "Icons" to "Details" and find I am able to see the list of applications this way. I am worried that eventually even this method of reaching my application will become compromised. Anyone know how to fix this issue yet?
My versions are:
Application Express 3.2.1.00.12
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options

So after a while the problem went away by itself, but it's back again and I've noticed another section of APEX that becomes affected when this error starts happening. When I click the icon for Copy Region, instead of a list of region names I get the error message.

ORA-28112: failed to execute policy function - Error in Application Builder

Hey all,
I've added a policy function to one of my tables and now I'm getting this error when I try to update a report region that references that table.
"Query cannot be parsed within the Builder. If you believe your query is syntactically correct, check the ''generic columns'' checkbox below the region source to proceed without parsing. ORA-28112: failed to execute policy function"
If I remove the policy then everything works fine. My application also runs fine with the policy in place. I just get these errors in the application builder when updating a report or an LOV that references the secure table.
The parsing schema is APPL_USER.
Here is the policy function:
FUNCTION DOCUMENT_TABLE_POLICY (object_schema IN VARCHAR2 DEFAULT NULL
,object_name IN VARCHAR2 DEFAULT NULL)
RETURN VARCHAR2 IS
v_nt_seq NUMBER;
BEGIN
IF user = 'APPL_USER' OR INSTR(user, 'ITFC_') = 1 THEN
RETURN NULL;
END IF;
IF V('APP_USER') IS NOT NULL THEN
IF V('F_NT_SEQ') IS NOT NULL THEN
v_nt_seq := V('F_NT_SEQ');
ELSE
SELECT NT_SEQ
INTO v_nt_seq
FROM APPL_USERS
WHERE UPPER(NT_ID) = UPPER(V('APP_USER'));
END IF;
RETURN '(DOCUMENT_TYPE, MANAGED_BY_ELEMENT, PROGRAM_CODE, CONTRACT_NUMBER) IN (SELECT DISTINCT R.DOCUMENT_TYPE, USL.ELEMENT, USL.PROGRAM_CODE, USL.CONTRACT_NUMBER FROM IPRACA_USERS_SECURITY_LINK USL, IPRACA_SECURITY_ROLES R WHERE R.SECURITY_ROLE_SEQ = USL.SECURITY_ROLE_SEQ AND USL.NT_SEQ = ' || TO_CHAR(v_nt_seq) || ')';
END IF;
--UNAUTHORIZED USERS CAN SEE NO DATA
RETURN '1=0';
END;
This is how I setup the policy:
BEGIN
DBMS_RLS.ADD_POLICY(
object_schema => 'APPL_USER'
,object_name => 'APPL_DOCUMENT'
,policy_name => 'APPL_DOCUMENT_POLICY'
,function_schema => 'APPL_USER'
,policy_function=> 'APPL_SECURITY.DOCUMENT_TABLE_POLICY'
END;
Any help would be greatly appreciated!
Thanks,
Jonathan Hart
APEX 3.1.1

Thanks.
After looking at it again, I think that may be the problem, too. I guess the APP_USER is set when in the application builder and the Builder is running the report query as it is being parsed which is causing the error. I added a Begin - Exception block around that query and everything seems to work now.
Thanks again!

Bug? Application not appearing in Application builder

Version 3.1.2.00.02
I have an application 102 which is translated to japanese as application 103 in my workspace - training
I have another application in a different database with application number 102 in workspace - develop.
I export application 102 from develop and import it into training. I select Auto Assign New Application ID. This creates the application with ID 103!
I was able to work and make changes and do everything on this new application. However, when I check in the application builder, I cannot not see this application. And when I try to run the application 102 in japanese (translated), then, it fails with an error.
Though I cannot see the new application 103 in my builder, I can run the application by making changes in the URL and if I click on 'Edit Application' link, then, I am able to make changes and work on application 103.
I realised that this is a corrupted version, and deleted my japanese translation of 102. This deleted my new application as well.
Is this a bug ?

Hi Naveen,
It will be most probably because of Security not defined for this new application in the "Member Access profile". Please check.
Thanks & Regards
Arun Kumar S

Application builder page error ORA-06502

We get an intermittent error with the application builder page of application express. The report that normally shows the icons or rows for each application returns the error "report error:
ORA-06502: PL/SQL: numeric or value error: NULL index table key value". is this a know issue? is there anything we can do to fix it?
Tom

Scott,
Thanks for the reply.
I will try my best to explain, following is the navigation:
1. After logging into my workspace --> Click on Application Builder --> Click either on a custom application or sample application --> I get report error: ORA-06502: PL/SQL: numeric or value error: NULL index table key value (Default View of the pages is set to Details)
2. If I change the page[s] View to Icons then there is no error.
3. We bounced the web but still having the error, did not try flushing the shared pool on the server.
HTH
Thanks
Pradeep
PS: How can I upload a screenshot?

Run page with cleared cache after edit in application builder

When I am building a form and run into an error while submitting the page I get the following situation. After making some changes to the page I try to run it again but the values from the previous try are still in the cache. So I immediately run into the same error I had earlier. The only way around this, that I currently know of, is to select another page in the application builder and start this. Then I can navigate to the page I'm working on using the menu. I usually start pages from the menu with a cleared cache.
Is there an easier way to do this?
There are currently two "run" buttons in the application builder. There is the button that says "run" and there is the "traffic light". Maybe one of those can be used the run the page with a cleared cahche and the other one with the cache still intact.
Edited by: Rene W. on Dec 23, 2010 6:26 AM

Hi,
One of the parameters in the URL is for clearing cache:
f?p=App:Page:Session:Request:Debug:ClearCache:itemNames:itemValues:PrinterFriendly
so, you could just enter the page number into the 6th parameter to clear the cache for that page
Andy

Application Builder (Bug)- Edit Region Comment getting ORA-01461

Similar Messages

Maybe you are looking for