Small bug in Apex 3.1

Apex 3.0 (I believe it was) introduced the "Calendar Icon Details" settings, so that the calendar icon could be customized for each theme. (I like to think of this as my own little contribution to Apex, since I suggested it in the 3.0 beta testing... :-)
Anyway, if you use the apex_item.date_popup function to generate datepickers for tabular forms, it still uses the (fixed) default datepicker icon ("/i/asfdcldr.gif"), ignoring the Calendar Icon Details settings.
For consistency, the API function should return an icon based on the theme setting...

Hi, what's your first name?
I will file a bug for this observation.
As a workaround, when using the function, you can specify an alternate image with something like:
select replace(apex_item.date_popup (1,null,sysdate,'DD-MON-YYYY'),'asfdcldr.gif','people.gif')
...for example.
Scott

Similar Messages

Satellite P500-1D6 - Small bug between cover plate and screen.

Hi
I have a small bug (in Dutch: "donderbeestje") between the protective glass and the actual screen.
Where I bought the laptop they yell me that they can't do anything about it and this is not under warranty of Toshiba.
For me however, this should be under warranty of Toshiba.
The screen with it's upper layers should be firmly closed so that no foreign objects can come in between.
So, my question is if this is under warranty or if not, what can I do to get this thing out of there?
Kind regards,
Pascal.

Hey,
Regarding such hardware related problems you should contact an official authorized service provider. The guys can repair notebooks under warrant for free if its a warranty case. Furthermore they can give you an exact if its normal or hardware problem.
Here its only an user to user forum so nobody can give you an exact answer but a full list of all ASPs you can find here:
http://eu.computers.toshiba-europe.com > Support & Downloads > Find an authorized service provider

Possible Bug In Apex 4.0.2

Hi Everyone.
I would like to report what I think is a bug in Apex 4.0.2.
If you go to my workspace on apex.oracle.com:
Workspace = EEG
Username = [email protected]
Password = galaxy (all lowercase)
Run the application: 37796 - Elie_Various_Goodies [no credentials are required]
This app was imported from my 4.0.1 workspace at my job. On the page I created two Date Picker items, P1_BEGIN_DATE and P1_END_DATE. I set them up so that whenever a user selects a begin date, a dynamic action "MANAGE_DATES" fires and automatically sets P1_END_DATE to this selected begin date value. Now when a user goes to select an end date, the displayed calendar starts at the previously selected begin date rather than the default of "Today".
All of this worked fine on my office (4.0.1) workspace. However, after exporting this app and then importing onto apex.oracle.com, none of this functionality would work. Even worse, whenever I try to select a begin date or even an end date, the selected dates never make it into the date picker fields. Displaying the "Session" window shows these fields as empty.
It was only after I copied the two date picker fields and also re-created my dynamic action (P1_BEGIN_DATE2, P1_END_DATE2, MANAGE_DATES) did my functionality return.
This behavior is quite strange. I can only think this is some sort of bug attributed to the export/import process when exporting a 4.0.1 app into a 4.0.2 workspace. I am not sure if this bizarre behavior happens with non-date picker items. Nor am I sure if this beavior would be repeated if I export/import from 4.0.2 into the another 4.0.2 environment.
Another strange thing I noticed. If I change my date picker items to be "date picker (classic)" type items, the dynamic action does not work at all. This is true in both 4.0.2 and 4.0.1. I'm not sure if this a bug or not. It could be that the classic date picker is just not "javascript" enabled so to speak. If that is true, then it would have been nice if the docs would have warned us about this.
Has anyone else seen this behavior?
Thank you.
Elie

Hi Joel.
First let me thank you for the warning about allowing "everyone" access to my workspace.
You're correct, of course. Anyone could destroy anything within my workspace. I guess I was too trusting especially as I have seen many posts on the Forum where others have given access to their workspace so that responders can offer help. I really should be more discreet about this. Again, thank you. Needless to say, I have changed my password.
With respect to the possible bug, the MANAGE_DATES dynamic action is intended to be a submit page because that is the only way I can see to get BOTH the P1_END_DATE date picker item as well as the end date textual field to be assigned the selected P1_BEGIN_DATE. I tried to use a dynamic action in which javascript sets the value of the end date textual field to the selected P1_BEGIN_DATE value. This works without the need to submit the page. Unfortunately, this does not cause the P1_END_DATE date picker item to default to this value. Instead, the default remains at today's date. This is why I finally resorted to a dynamic action that submits the page whenever a new value is selected (that is, a "change" event) from the P1_BEGIN_DATE date picker item.
All of this works in my office 4.0.1 environment. However, I was puzzled when this fails under 4.0.2 on the hosted web site at apex.oracle.com. This is why I posted a "possible" bug in 4.0.2.
I hope this all makes sense.
One more thing, as already mentioned in my original post, this "defaulting a date picker" functionality does NOT work at all for the "classic" date picker items in both 4.0.1 nor in 4.0.2. I realize one can implement this functionality (I' guessing) my using, say, a "onChange" javascript call to submit the page. It's just funny that the "classic" date picker items are not acted upon by the dynamic action MANAGE_DATES that submits the page.
Thank you.
Elie

Open Cursor Issue because of file browse Item - Is this a Bug in APEX 3.2

Hi All,
I am using file browse Item to upload file into the database at two places in my application, but it seems whenever I am submitting those two pages, with file path or without file path, its opening an cursor which remains open after that, because of this open cursor count in the application is getting exceeding every time.
For testing this I have made an dummy page containing just file browse item and submit button, and still it is increasing the open cursor count.
Is this a bug in Apex file browse item or there is some other way to handle this.
Please kindly help me in the above issue as this is affecting the production application.
Thanks & Regards
Sanjay
Edited by: user11204334 on Dec 5, 2010 9:57 PM
Edited by: user11204334 on Dec 5, 2010 9:58 PM

Hi,
One observation, Apex is switching the Session ID after one got killed ? I was working on Apex page with browse Item to test open cursor count,
after killing the SID (227) on which the open cursor count was getting increase, it APEX automatically switches to new SID(149) for that session.
Now the problem is even if I have two SID's and one hits the maximum open cursor count, It is not switching to other SID instead the whole application becomes unavailable.
STATNAME SID VALUE USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 74 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 227 325 APEX_PUBLIC_USER Killed
opened cursors current 244 15 APEX_PUBLIC_USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 76 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 244 15 APEX_PUBLIC_USER
Please kindly help in this.
Thanks in Advance
Thanks & Regards
Sanjay
Edited by: user11204334 on Dec 8, 2010 1:02 AM

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?

Is this a bug in APEX 3.0.1 Installation RAC database with RAW device???

Hello,
I am getting the following error when I try to complete approval process.
ORA-20001: Unable to create tablespace. ORA-01
119: error in creating database file '//./FLOW_1.dbf' ORA-27040: skgfrcre: creat
e error, unable to create file OSD-04002: unable to open file O/S-Error: (OS 2)
The system cannot find the file specified.
I checked the alert log for error here is the error in the alert log file.
ORA-1119 signalled during: CREATE TABLESPACE FLOW_1 DATAFILE '//./FLOW_1.dbf'..
and i found the syntax for create tablespace was wrong.
To create a tablespace in RAC with RAW device environment under windows.
it should have forward black slash instead of backward slash "/" without .dbf extension.
so, I changed the syntax i was able to create tablespace through sqlplus.
When APEX tool try to create this tablespace it throws this error..
Old: CREATE TABLESPACE FLOW_1 DATAFILE
'\\.\FLOW_1.dbf' SIZE 10304 K REUSE AUTOEXTEND OFF
EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
error : ORA-01119: error in creating database file '\\.\FLOW_1.dbf'
New:
CREATE TABLESPACE FLOW_1 DATAFILE
'\\.\FLOW_1' SIZE 10304 K REUSE AUTOEXTEND OFF
EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
Tablespace created.
Is it a bug in APEX 3.0.1.??
Is anyone installed APEX in RAC ??
James

Hi,
One observation, Apex is switching the Session ID after one got killed ? I was working on Apex page with browse Item to test open cursor count,
after killing the SID (227) on which the open cursor count was getting increase, it APEX automatically switches to new SID(149) for that session.
Now the problem is even if I have two SID's and one hits the maximum open cursor count, It is not switching to other SID instead the whole application becomes unavailable.
STATNAME SID VALUE USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 74 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 227 325 APEX_PUBLIC_USER Killed
opened cursors current 244 15 APEX_PUBLIC_USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 76 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 244 15 APEX_PUBLIC_USER
Please kindly help in this.
Thanks in Advance
Thanks & Regards
Sanjay
Edited by: user11204334 on Dec 8, 2010 1:02 AM

It looked like a small bug going up and down on my screen then it stopped about 12 o clock a quarter of the way from the top, now it seems to be burned in to the inside of the screen, anyone seen this before? And what can be done about it, macbook pro

I have what looked like a small bug that ran up and down the screen and then sudenly stopped in center upper half of screen and now appears to be burned in to the inside of the screen, anyone had this probelm before and what can be done about it?

Thanks for the suggestion, the next step was to call Apple, who gave me a claim number, which I discovered you must have to get anything done with them. They refered me to a Apple store or repair center, after some reseach took it to the Computer Store in Mobile, Alabama and they were excellent. They took pictures of the screen with bug submitted it to Apple who denied the claim but they kept kicking it up to the next level and finally Apple agreed to sent new cover. The Computer Store had the cover the next day, they changed it out and now I am bug free. If your in the area of Mobile Alabama you can feel good about getting help from the Computer Store. For the two folks that responded to my note, Thank You, good comments and good advice.

Small Bug in Flash 8: loading swf that´s a vectorized image in many layers

Hi! There´s a small bug in flash 8. If you load a swf
that it´s a vectorized image in many layers, when you give it
an action in onLoadInit, like mc.onRelease, the mc don´t
"catch" that action. You can try loading an image (it works), a lot
of swf (it works), but with this kind of swf the actions onRelease,
onPress, etc... don´t work.
The
swf
I´ll make a different vectorized image to make it works
(if there is only one layer it works)

Seems odd it will only run once. Usually if a cache problem
you get the same
results even when you update the movie or server scripts.
If it is
http:// it is not local even if from the browser
cache.
Verify the html is validated.
Check to see if this applies to all swfs. Create a simple
hello world swf
that connects to a JSP script that returns a simple value to
Flash. If that
seems to work, then the problem is in the JSP or
Actionscripting coding.
Check you can load the JSP script repeatedly using a direct
call to it on
the browser line using
http://.
Lon Hosford
www.lonhosford.com
Flash, Actionscript and Flash Media Server examples:
http://flashexamples.hosfordusa.com
May many happy bits flow your way!
"srikanth_s_india" <[email protected]> wrote
in message
news:e6obld$lfb$[email protected]..
> Thanks for the article link.
>
> I can't provide the URL as it is within our application
which requires
> logging
> in. However, one more interesting thing about it is that
it always works
> for
> the first time (in the browser/machine) but not from the
next time.
>
> My doubt is whether it is because of the caching? When
it loads for the
> first
> time, the HTML and SWF files load from our server and
hence are allowed to
> communicate with our JSP. However, when it loads the
subsequent times, it
> probably loads from the cache and hence considered as a
local file and not
> allowed to communicate with our JSP file which is on the
Internet.
>
> Can anybody tell me how to enable a local SWF file to
load SWF files from
> the
> Internet & access URLs from the Internet in Flash 8
pluggin?
>

Bug in Apex 4.1 tabular form with rowid as PK

Hi
I think this is a bug in Apex 4.1. I tested it on apex.oracle.com. This is the simple scenario.
Create a simple table:
create table dropme (code number, description varchar2(200));
Now use the wizard to create a tabular form.
Select Allowed Operations insert and update for this table.
Select ROWID as Primary key type.
After finishing the wizard click on Run and you get:
failed to parse SQL query:
ORA-00904: "APEX$ROWID": invalid identifier
Note: this does not happen when you select insert, update and delete.

Hello,
>> Select Allowed Operations insert and update for this table.
>> Select ROWID as Primary key type.
It seems that you are correct. I was able to reconstruct your scenario on my local system. Now we need the verification of the dev team.
Regards,
Arie.
&diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
&diams; Author of Oracle Application Express 3.2 – The Essentials and More

Small bug in WAP4410N firmware 2.0.3.3

Attached is a screenshot of a small bug in the System Up Time. It shows Hour:Day:Sec where it should show Hour:Min:Sec.

It seems to happen when using external monitor and "Mirroring" is enabled.
We'll do some more tests to fully confirm
If someone else has also noticed this, please post details.
Thanks!
HD Cam Team
Group of photographers and filmmakers using Canon cameras for serious purposes.
www.hdcamteam.com | www.twitter.com/HDCamTeam | www.facebook.com/HDCamTeam

Small bug in iTunes 7.4.3. on Win XP Pro SP2

It's a small bug. When I try to edit few or more MP3's file information (ID Tag), but they are "read-only", the change dialog appear normally - all edit forms are enabled - but when I press "OK" the changes didn't save and no error box appear.
I think that somebody understand this - sorry for my English!

Yes I do, I'm using an administrator account.
I dont understand what is going on.
I had an Oracle 8i installed before. but I delete all the registry entries. And installed the jre 1.4.2.05.
But nothing . Always abort in 36%.

Some small bugs and errors

Hi,
In the meantime, waiting for the DPS network fix, I have some small bugs and errors to post:
#1: When signed ot from the folio builder panel, the click to create new folio message isn't useful, as it doesn't work. You must be signed in.
#2: "System Status" cut off on the DPS Status Website:

Hi Bob,
Just tested again. but nope, it doesn't work for me anymore. Since one of the latest updates, I can only create folios, when I'm signed in. Here is my video proof:
This is the case for me on two (tested) computers running CS5.5 and CS6!
That's why I thought this feature has been removed.

Small bug: Database configuration - Initialization parameters

Hi!
SQLDeveloper version: 3.2.20.09
View -> DBA -> Database configuration -> Initialization Parameters -> right click "Open" -> editor with "Parameter" and "Value" (inter alia) columns appears
Changing value for parameter "optimizer_features_enable" isn't working:
Example:
Parameter: optimizer_features_enable
Changing value from 11.2.0.1 to 9.2.0 -> commiting changes -> ORA-02017 error appears ("integer value required")
In "Messages - Log" window appears the following statement: ALTER SYSTEM SET optimizer_features_enable=9.2.0 COMMENT='' SCOPE=MEMORY
I think rather it should be: ALTER SYSTEM SET optimizer_features_enable='9.2.0' COMMENT='' SCOPE=MEMORY
It looks like a small bug.

Hi dz_r,
One workaround for this case is, when editing the data in the grid cell, to enclose the Oracle version in single quotes. After committing to apply the update (which works), the grid refresh strips away the single quotes, leaving the desired value displayed in the cell.
So this is, as you say, a small bug. Note that not all parameters of type String require single quotes, e. g., cursor_sharing=exact. Probably any String beginning with a numeric digit should be enclosed in quotes automatically.
I logged the following bug:
Bug 16733790 - UPDATING INITIALIZATION PARAMETER OF TYPE STRING FAILS IF BEGINS WITH A NUMERIC
Thanks for reporting this,
Gary
SQL Developer Team

Small bug in DHCP setting

If I write a message in DHCP settings using quote (for example: Welcome to "NewNetwork") the base assigns to the clients a local IP (169.x.x.x) and no connections to internet.
If I write the same message without quotes (Welcome to NewNetwork) IP assigned to the client are correct (10.0.1.x or other ranges) and all works fine.
A small bug but all a night to find it!

Right, the original method does not make much sense. It shows the point wrt.Generics, though.

Small bug in 4.0.4

Hi, I own Neo V with android 4.0.4 installed, I found a small bug:
In the smart dial if you press the volume up or down, instead of ringer volume it sets media volume. It's no big deal but it is a bug

Thanks for posting this. I will feed this back to the developers.
What do you think about this forum? Let us know by doing this short survey.

Small bug in Apex 3.1

Similar Messages

Maybe you are looking for