Stop_on_close attribute ORA-27475 error

I have a job that runs a chain. I have set the schedule name as a window. When I try to set the stop_on_window_close attribute, I get the error
ORA-27475: "APP_TIBIA.LOAD_BILLS_INIT_CHAIN" must be a program. Does that attribute not work with a job_type of 'CHAIN'?
DBMS_SCHEDULER.CREATE_SCHEDULE
schedule_name => 'APP_TIBIA.WORK_DAYS_NO_EOFY_SCHD'
,start_date => '18-NOV-2009 5:00:00.000000 PM US/Central'
,repeat_interval =>'FREQ=MONTHLY;BYDAY=MON,TUE,WED,THU,FRI;EXCLUDE=HOL_FED_HOLIDAYS_SCHD,END_FISCAL_YEAR_SCHD'
,comments => 'Standard working days (excludes Federal Holidays)'
END;
DBMS_SCHEDULER.CREATE_WINDOW
window_name => 'SYS.WORK_DAYS_NO_EOFY_WINDOW',
resource_plan => null,
schedule_name => 'APP_TIBIA.WORK_DAYS_NO_EOFY_SCHD',
duration => INTERVAL '13' HOUR,
window_priority => 'LOW',
comments => 'Window for jobs that run everyday. If they are not started by 6 am the window closes'
DBMS_SCHEDULER.CREATE_JOB
job_name => 'APP_TIBIA.LOAD_BILLS_CHAIN_JOB',
job_type => 'CHAIN',
job_action => 'APP_TIBIA.LOAD_BILLS_INIT_CHAIN',
schedule_name => 'SYS.WORK_DAYS_NO_EOFY_WINDOW',
auto_drop => FALSE,
enabled => TRUE,
comments =>'Job that runs the load bills chain.'
DBMS_SCHEDULER.SET_ATTRIBUTE('APP_TIBIA.LOAD_BILLS_CHAIN_JOB','STOP_ON_WINDOW_CLOSE',TRUE);
thanks.

Sorry,
I'll try to word this more clearly.
Here is my job definition
DBMS_SCHEDULER.CREATE_JOB
job_name => 'APP_TIBIA.LOAD_BILLS_CHAIN_JOB',
job_type => 'CHAIN',
job_action => 'APP_TIBIA.LOAD_BILLS_INIT_CHAIN',
schedule_name => 'SYS.WORK_DAYS_NO_EOFY_WINDOW',
auto_drop => FALSE,
enabled => TRUE,
comments =>'Job that runs the load bills chain.'
When i run this...
DBMS_SCHEDULER.SET_ATTRIBUTE('APP_TIBIA.LOAD_BILLS_CHAIN_JOB','STOP_ON_WINDOW_CLOSE',TRUE);
I get the error--ORA-27475: "APP_TIBIA.LOAD_BILLS_INIT_CHAIN" must be a program.
I have created other jobs that run in a window and set the stop_on_window_close attribute, however those jobs had a "job_type" ofr PL/SQL block or the job executed a program. Why would i be getting this error? Is it because the "job_type" of this job is a CHAIN? btw, I included above the schedule and window definitions for reference.
thanks.

Similar Messages

  • 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?

  • Report suddenly showing ORA-20001: Error fetching column value: ORA-06502:

    Hi,
    Some reports in my applications are suddenly showing:
    ORA-20001: Error fetching column value: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    instead iof the data they used to show.
    In my development system I can fix this by:
    1. changing the column alias in my sql
    select 'a' alias1 from dual becomes
    select 'a' alias2 from dual
    2. SAVE CHANGES
    3. change column alias back to original
    select 'a' alias2 from dual becomes
    select 'a' alias1 from dual
    4. reorder columns back to original in the 'report attributes' tab
    alias1 is now at the bottom of my colum list - i just bounce it up to column 4 using the up arrows
    5. SAVE CHANGES
    then everything starts working OK again.
    There seems to be nothing wrong with my sql as I can make it works on a new page or after I run the above steps, so I guess something is breaking somewhere but I cannot work out what.
    Has anyone else seen this? Does anyone know the cause? Does anyone have a fix for this that does not involve the above steps (plus redeployment to prodcution and all the work that involves)?
    I am seeing this on version 2.3 and 3.0.
    Thanks,
    Martin

    Hi Scott,
    I think this is want you want (sorry it's not easy to read):
    wp.suite_id - Database Column NUMBER - Report Column Based on LOV
    wp.project_id - Database Column NUMBER - Report Column Based on LOV
    wp.application_order wp_order - Database Column NUMBER - Report Column Standard
    lpad(wp.work_package_id,5,'0')||' - '||wp.name wp_name - Database Column NUMBER/VARCHAR2 - Report Column Standard
    pt.application_order pt_order - Database Column NUMBER - Report Column Standard
    pt.name pt_name - Database Column VARCHAR2 - Report Column Standard
    substr(pt.description,1,30) description - Database Column VARCHAR2 - Report Column Standard
    pt.application_tier - Database Column VARCHAR2 - Report Column Based on LOV
    pt.application_method - Database Column VARCHAR2 - Report Column Based on LOV
    pt.TECH_LEAD_ID - Database Column NUMBER - Report Column Based on LOV
    This report has no link columns and no derived columns.
    Regards,
    Martin

  • ORA-19279 error extracting one-to-many sequence

    I have an xml table built from a registered schema that I'm trying to extract data from using a view. The lowest level is a polygon with multiple vertices -- vertices number, latitude, and longitude. The xml file lists data as
    POLYGON
    SEQ_NUM
    LAT
    LON
    SEQ_NUM
    LAT
    LON
    SEQ_NUM
    LAT
    LON
    /POLYGON
    The method I use to extract the data returns an ORA-19279 error: "XQuery dymanic type mismatch: expected singleton sequence - got multi-item sequence." The error is pointing to the polygon data; however the polygon sequence tag in the xsd file has the attribute of maxOccurs="unbounded".
    Below is the xsd file, a samlpe xml file and the Select statement I use.
    ABC.xsd file:
    &lt;?xml version="1.0"?&gt;
    &lt;xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified" attributeFormDefault="unqualified"&gt;
    &lt;xs:element name="A_B_C"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:sequence&gt;
    &lt;xs:element name="A"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:sequence&gt;
    &lt;xs:element name="B"&gt;
    &lt;xs:simpleType&gt;
    &lt;xs:restriction base="xs:string"&gt;
    &lt;xs:enumeration value="1A"/&gt;
    &lt;xs:enumeration value="1B"/&gt;
    &lt;xs:enumeration value="2A"/&gt;
    &lt;xs:enumeration value="2B"/&gt;
    &lt;xs:enumeration value="2C"/&gt;
    &lt;/xs:restriction&gt;
    &lt;/xs:simpleType&gt;
    &lt;/xs:element&gt;
    &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;xs:choice&gt;
    &lt;xs:element name="D" maxOccurs="unbounded"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:sequence&gt;
    &lt;xs:element name="D_ID" type="xs:string"&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="D_UQ_ID" type="xs:string"&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="D_TIME"&gt;
    &lt;xs:simpleType&gt;
    &lt;xs:restriction base="xs:string"/&gt;
    &lt;/xs:simpleType&gt;
    &lt;/xs:element&gt;
    &lt;xs:choice&gt;
    &lt;xs:element name="F"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:sequence&gt;
    &lt;xs:element name="F_TYPE" type="xs:string"&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="F_SUBTYPE" type="xs:string"&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="G" minOccurs="0"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:choice&gt;
    &lt;xs:element name="H"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:sequence&gt;
    &lt;xs:element name="H_TYPE" type="xs:string" minOccurs="0"&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="H_MODE" type="xs:string" minOccurs="0"&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="H_SHAPE" minOccurs="0"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:choice&gt;
    &lt;xs:element name="POLYGON"&gt;
    &lt;xs:complexType&gt;
    {color:#ff0000}*&lt;xs:sequence maxOccurs="unbounded"&gt;*{color}
    &lt;xs:element name="SEQ_NUM" type="xs:unsignedInt"&gt;
    &lt;xs:annotation&gt;
    &lt;xs:documentation&gt;sequence number in the polygon&lt;/xs:documentation&gt;
    &lt;/xs:annotation&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="LAT" type="xs:float"/&gt;
    &lt;xs:element name="LON" type="xs:float"/&gt;
    &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="CIRCLE"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:sequence&gt;
    &lt;xs:element name="LAT" type="xs:float"/&gt;
    &lt;xs:element name="LON" type="xs:float"/&gt;
    &lt;xs:element name="RAD" type="xs:float"/&gt;
    &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="ELLIPSE"&gt;
    &lt;xs:complexType&gt;
    &lt;xs:sequence&gt;
    &lt;xs:element name="ORIENT"&gt;
    &lt;xs:simpleType&gt;
    &lt;xs:restriction base="xs:float"&gt;
    &lt;xs:minInclusive value="0"/&gt;
    &lt;xs:maxInclusive value="360"/&gt;
    &lt;/xs:restriction&gt;
    &lt;/xs:simpleType&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="MAJ_AX" type="xs:float"&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="MIN_AX" type="xs:float"&gt;
    &lt;/xs:element&gt;
    &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;/xs:choice&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;/xs:choice&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="E"&gt;
    &lt;xs:complexType/&gt;
    &lt;/xs:element&gt;
    &lt;/xs:choice&gt;
    &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;xs:element name="C"&gt;
    &lt;/xs:element&gt;
    &lt;/xs:choice&gt;
    &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
    &lt;/xs:element&gt;
    &lt;/xs:schema&gt;
    abc.xml file:
    &lt;?xml version="1.0" encoding="utf-8"?&gt;
    &lt;A_B_C&gt;
    &lt;A&gt;
    &lt;B&gt;1B&lt;/B&gt;
    &lt;/A&gt;
    &lt;D&gt;
    &lt;D_ID&gt;D_0001&lt;/D_ID&gt;
    &lt;D_UQ_ID&gt;UQ_D_0001&lt;/D_UQ_ID&gt;
    &lt;D_TIME&gt;2007 FEB 11:11:11.11&lt;/D_TIME&gt;
    &lt;F&gt;
    &lt;F_TYPE&gt;F_TYPE_TEST&lt;/F_TYPE&gt;
    &lt;F_SUBTYPE&gt;SUB_TEST&lt;/F_SUBTYPE&gt;
    &lt;G&gt;
    &lt;H&gt;
    &lt;H_TYPE&gt;Ipod&lt;/H_TYPE&gt;
    &lt;H_MODE&gt;SCANNING&lt;/H_MODE&gt;
    &lt;H_SHAPE&gt;
    &lt;POLYGON&gt;
    &lt;SEQ_NUM&gt;1&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;10.1&lt;/LAT&gt;
    &lt;LON&gt;11.1&lt;/LON&gt;
    &lt;SEQ_NUM&gt;2&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;20.2&lt;/LAT&gt;
    &lt;LON&gt;22.2&lt;/LON&gt;
    &lt;SEQ_NUM&gt;3&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;30.3&lt;/LAT&gt;
    &lt;LON&gt;33.3&lt;/LON&gt;
    &lt;SEQ_NUM&gt;4&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;40.4&lt;/LAT&gt;
    &lt;LON&gt;44.4&lt;/LON&gt;
    &lt;/POLYGON&gt;
    &lt;CIRCLE&gt;
    &lt;LAT&gt;12.3&lt;/LAT&gt;
    &lt;LON&gt;45.6&lt;/LON&gt;
    &lt;RAD&gt;78.9&lt;/RAD&gt;
    &lt;/CIRCLE&gt;
    &lt;ELLIPSE&gt;
    &lt;ORIENT&gt;99.90&lt;/ORIENT&gt;
    &lt;MAJ_AX&gt;111.10&lt;/MAJ_AX&gt;
    &lt;MIN_AX&gt;222.20&lt;/MIN_AX&gt;
    &lt;/ELLIPSE&gt;
    &lt;/H_SHAPE&gt;
    &lt;/H&gt;
    &lt;/G&gt;
    &lt;/F&gt;
    &lt;E&gt;&lt;/E&gt;
    &lt;/D&gt;
    &lt;D&gt;
    &lt;D_ID&gt;D_0002&lt;/D_ID&gt;
    &lt;D_UQ_ID&gt;UQ_D_0002&lt;/D_UQ_ID&gt;
    &lt;D_TIME&gt;2007 FEB 22:22:22.22&lt;/D_TIME&gt;
    &lt;F&gt;
    &lt;F_TYPE&gt;F_TYPE_TEST&lt;/F_TYPE&gt;
    &lt;F_SUBTYPE&gt;SUB_TEST&lt;/F_SUBTYPE&gt;
    &lt;G&gt;
    &lt;H&gt;
    &lt;H_TYPE&gt;Ipod&lt;/H_TYPE&gt;
    &lt;H_MODE&gt;SCANNING&lt;/H_MODE&gt;
    &lt;H_SHAPE&gt;
    &lt;POLYGON&gt;
    &lt;SEQ_NUM&gt;1&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;10.1&lt;/LAT&gt;
    &lt;LON&gt;11.1&lt;/LON&gt;
    &lt;SEQ_NUM&gt;2&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;20.2&lt;/LAT&gt;
    &lt;LON&gt;22.2&lt;/LON&gt;
    &lt;SEQ_NUM&gt;3&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;30.3&lt;/LAT&gt;
    &lt;LON&gt;33.3&lt;/LON&gt;
    &lt;SEQ_NUM&gt;4&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;40.4&lt;/LAT&gt;
    &lt;LON&gt;44.4&lt;/LON&gt;
    &lt;/POLYGON&gt;
    &lt;CIRCLE&gt;
    &lt;LAT&gt;12.3&lt;/LAT&gt;
    &lt;LON&gt;45.6&lt;/LON&gt;
    &lt;RAD&gt;78.9&lt;/RAD&gt;
    &lt;/CIRCLE&gt;
    &lt;ELLIPSE&gt;
    &lt;ORIENT&gt;99.90&lt;/ORIENT&gt;
    &lt;MAJ_AX&gt;111.10&lt;/MAJ_AX&gt;
    &lt;MIN_AX&gt;222.20&lt;/MIN_AX&gt;
    &lt;/ELLIPSE&gt;
    &lt;/H_SHAPE&gt;
    &lt;/H&gt;
    &lt;/G&gt;
    &lt;/F&gt;
    &lt;E&gt;&lt;/E&gt;
    &lt;/D&gt;
    &lt;D&gt;
    &lt;D_ID&gt;D_0003&lt;/D_ID&gt;
    &lt;D_UQ_ID&gt;UQ_D_0003&lt;/D_UQ_ID&gt;
    &lt;D_TIME&gt;2007 FEB 33:33:33.33&lt;/D_TIME&gt;
    &lt;F&gt;
    &lt;F_TYPE&gt;F_TYPE_TEST&lt;/F_TYPE&gt;
    &lt;F_SUBTYPE&gt;SUB_TEST&lt;/F_SUBTYPE&gt;
    &lt;G&gt;
    &lt;H&gt;
    &lt;H_TYPE&gt;Ipod&lt;/H_TYPE&gt;
    &lt;H_MODE&gt;SCANNING&lt;/H_MODE&gt;
    &lt;/H&gt;
    &lt;/G&gt;
    &lt;/F&gt;
    &lt;E&gt;&lt;/E&gt;
    &lt;/D&gt;
    &lt;D&gt;
    &lt;D_ID&gt;D_0004&lt;/D_ID&gt;
    &lt;D_UQ_ID&gt;UQ_D_0004&lt;/D_UQ_ID&gt;
    &lt;D_TIME&gt;2007 FEB 44:44:44.44&lt;/D_TIME&gt;
    &lt;F&gt;
    &lt;F_TYPE&gt;F_TYPE_TEST&lt;/F_TYPE&gt;
    &lt;F_SUBTYPE&gt;SUB_TEST&lt;/F_SUBTYPE&gt;
    &lt;G&gt;
    &lt;H&gt;
    &lt;H_TYPE&gt;Ipod&lt;/H_TYPE&gt;
    &lt;H_MODE&gt;SCANNING&lt;/H_MODE&gt;
    &lt;H_SHAPE&gt;
    &lt;POLYGON&gt;
    &lt;SEQ_NUM&gt;1&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;10.1&lt;/LAT&gt;
    &lt;LON&gt;11.1&lt;/LON&gt;
    &lt;SEQ_NUM&gt;2&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;20.2&lt;/LAT&gt;
    &lt;LON&gt;22.2&lt;/LON&gt;
    &lt;SEQ_NUM&gt;3&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;30.3&lt;/LAT&gt;
    &lt;LON&gt;33.3&lt;/LON&gt;
    &lt;SEQ_NUM&gt;4&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;40.4&lt;/LAT&gt;
    &lt;LON&gt;44.4&lt;/LON&gt;
    &lt;/POLYGON&gt;
    &lt;CIRCLE&gt;
    &lt;LAT&gt;12.3&lt;/LAT&gt;
    &lt;LON&gt;45.6&lt;/LON&gt;
    &lt;RAD&gt;78.9&lt;/RAD&gt;
    &lt;/CIRCLE&gt;
    &lt;ELLIPSE&gt;
    &lt;ORIENT&gt;99.90&lt;/ORIENT&gt;
    &lt;MAJ_AX&gt;111.10&lt;/MAJ_AX&gt;
    &lt;MIN_AX&gt;222.20&lt;/MIN_AX&gt;
    &lt;/ELLIPSE&gt;
    &lt;/H_SHAPE&gt;
    &lt;/H&gt;
    &lt;/G&gt;
    &lt;/F&gt;
    &lt;E&gt;&lt;/E&gt;
    &lt;/D&gt;
    &lt;D&gt;
    &lt;D_ID&gt;D_0005&lt;/D_ID&gt;
    &lt;D_UQ_ID&gt;UQ_D_0005&lt;/D_UQ_ID&gt;
    &lt;D_TIME&gt;2007 FEB 55:55:55.55&lt;/D_TIME&gt;
    &lt;F&gt;
    &lt;F_TYPE&gt;F_TYPE_TEST&lt;/F_TYPE&gt;
    &lt;F_SUBTYPE&gt;SUB_TEST&lt;/F_SUBTYPE&gt;
    &lt;/F&gt;
    &lt;E&gt;&lt;/E&gt;
    &lt;/D&gt;
    &lt;D&gt;
    &lt;D_ID&gt;D_0006&lt;/D_ID&gt;
    &lt;D_UQ_ID&gt;UQ_D_0006&lt;/D_UQ_ID&gt;
    &lt;D_TIME&gt;2007 FEB 66:66:66.66&lt;/D_TIME&gt;
    &lt;F&gt;
    &lt;F_TYPE&gt;F_TYPE_TEST&lt;/F_TYPE&gt;
    &lt;F_SUBTYPE&gt;SUB_TEST&lt;/F_SUBTYPE&gt;
    &lt;G&gt;
    &lt;H&gt;
    &lt;H_TYPE&gt;Ipod&lt;/H_TYPE&gt;
    &lt;H_MODE&gt;SCANNING&lt;/H_MODE&gt;
    &lt;H_SHAPE&gt;
    &lt;POLYGON&gt;
    &lt;SEQ_NUM&gt;1&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;10.1&lt;/LAT&gt;
    &lt;LON&gt;11.1&lt;/LON&gt;
    &lt;SEQ_NUM&gt;2&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;20.2&lt;/LAT&gt;
    &lt;LON&gt;22.2&lt;/LON&gt;
    &lt;SEQ_NUM&gt;3&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;30.3&lt;/LAT&gt;
    &lt;LON&gt;33.3&lt;/LON&gt;
    &lt;SEQ_NUM&gt;4&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;40.4&lt;/LAT&gt;
    &lt;LON&gt;44.4&lt;/LON&gt;
    &lt;/POLYGON&gt;
    &lt;CIRCLE&gt;
    &lt;LAT&gt;12.3&lt;/LAT&gt;
    &lt;LON&gt;45.6&lt;/LON&gt;
    &lt;RAD&gt;78.9&lt;/RAD&gt;
    &lt;/CIRCLE&gt;
    &lt;ELLIPSE&gt;
    &lt;ORIENT&gt;99.90&lt;/ORIENT&gt;
    &lt;MAJ_AX&gt;111.10&lt;/MAJ_AX&gt;
    &lt;MIN_AX&gt;222.20&lt;/MIN_AX&gt;
    &lt;/ELLIPSE&gt;
    &lt;/H_SHAPE&gt;
    &lt;/H&gt;
    &lt;/G&gt;
    &lt;/F&gt;
    &lt;E&gt;&lt;/E&gt;
    &lt;/D&gt;
    &lt;D&gt;
    &lt;D_ID&gt;D_0007&lt;/D_ID&gt;
    &lt;D_UQ_ID&gt;UQ_D_0007&lt;/D_UQ_ID&gt;
    &lt;D_TIME&gt;2007 FEB 77:77:77.77&lt;/D_TIME&gt;
    &lt;F&gt;
    &lt;F_TYPE&gt;F_TYPE_TEST&lt;/F_TYPE&gt;
    &lt;F_SUBTYPE&gt;SUB_TEST&lt;/F_SUBTYPE&gt;
    &lt;G&gt;
    &lt;H&gt;
    &lt;H_TYPE&gt;Ipod&lt;/H_TYPE&gt;
    &lt;H_MODE&gt;SCANNING&lt;/H_MODE&gt;
    &lt;/H&gt;
    &lt;/G&gt;
    &lt;/F&gt;
    &lt;E&gt;&lt;/E&gt;
    &lt;/D&gt;
    &lt;D&gt;
    &lt;D_ID&gt;D_0008&lt;/D_ID&gt;
    &lt;D_UQ_ID&gt;UQ_D_0008&lt;/D_UQ_ID&gt;
    &lt;D_TIME&gt;2007 FEB 88:88:88.88&lt;/D_TIME&gt;
    &lt;F&gt;
    &lt;F_TYPE&gt;F_TYPE_TEST&lt;/F_TYPE&gt;
    &lt;F_SUBTYPE&gt;SUB_TEST&lt;/F_SUBTYPE&gt;
    &lt;G&gt;
    &lt;H&gt;
    &lt;H_TYPE&gt;Ipod&lt;/H_TYPE&gt;
    &lt;H_MODE&gt;SCANNING&lt;/H_MODE&gt;
    &lt;H_SHAPE&gt;
    &lt;POLYGON&gt;
    &lt;SEQ_NUM&gt;1&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;10.1&lt;/LAT&gt;
    &lt;LON&gt;11.1&lt;/LON&gt;
    &lt;SEQ_NUM&gt;2&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;20.2&lt;/LAT&gt;
    &lt;LON&gt;22.2&lt;/LON&gt;
    &lt;SEQ_NUM&gt;3&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;30.3&lt;/LAT&gt;
    &lt;LON&gt;33.3&lt;/LON&gt;
    &lt;SEQ_NUM&gt;4&lt;/SEQ_NUM&gt;
    &lt;LAT&gt;40.4&lt;/LAT&gt;
    &lt;LON&gt;44.4&lt;/LON&gt;
    &lt;/POLYGON&gt;
    &lt;CIRCLE&gt;
    &lt;LAT&gt;12.3&lt;/LAT&gt;
    &lt;LON&gt;45.6&lt;/LON&gt;
    &lt;RAD&gt;78.9&lt;/RAD&gt;
    &lt;/CIRCLE&gt;
    &lt;ELLIPSE&gt;
    &lt;ORIENT&gt;88.80&lt;/ORIENT&gt;
    &lt;MAJ_AX&gt;111.10&lt;/MAJ_AX&gt;
    &lt;MIN_AX&gt;222.20&lt;/MIN_AX&gt;
    &lt;/ELLIPSE&gt;
    &lt;/H_SHAPE&gt;
    &lt;/H&gt;
    &lt;/G&gt;
    &lt;/F&gt;
    &lt;E&gt;&lt;/E&gt;
    &lt;/D&gt;
    &lt;C&gt;TPS Report 4&lt;/C&gt;
    &lt;/A_B_C&gt;
    SELECT statement:
    SELECT a_level.a_class
    , d_level.D_UQ_ID
    , d_level.D_TIME
    , h_level.SEQ_NUM
    , h_level.LAT
    , h_level.LON
    FROM ABC_XML,
    XMLTABLE('/A_B_C'
    PASSING ABC_XML.ABC_SPEC
    COLUMNS
    A_CLASS VARCHAR2(4000 BYTE) PATH '/A_B_C/A/B'
    , D XMLTYPE PATH 'D'
    ) a_level,
    XMLTABLE ('/D'
    PASSING a_level.D
    COLUMNS
    D_UQ_ID varchar2(4000) PATH 'D_UQ_ID'
    , D_TIME varchar2(4000) PATH 'D_TIME'
    , POLYGON XMLTYPE PATH 'F/G/H/H_SHAPE/POLYGON'
    ) d_level
    XMLTABLE('/POLYGON'
    passing d_level.POLYGON
    COLUMNS
    SEQ_NUM NUMBER PATH 'SEQ_NUM'
    , LAT NUMBER PATH 'LAT)'
    , LON NUMBER PATH 'LON'
    ) h_level;
    As you see I need to return data from three levels of data (a, d and h). I can remark out the bottom level (h_level) and the statement runs returning 8 rows from the xml file above (which is correct). The h_level XMLTABLE reference returns the ORA-19279 error. The full statement should return 20 rows of data.

    Yes. I looked at that string.
    Never mind on this one. You helped solve the problem in another string
    XMLTable 'For $i in ... return ROW' clause help needed

  • ORA-20001: Error in MRU – Master-Detail

    We don’t allow to user modify the data and I remove a delete button in Master Detail.
    When I Add a row, I have the following message.
    Error in mru internal routine: ORA-20001: Error in MRU: row= 1,
    ORA-20001: ORA-20001: Current version of data in database has changed
    since user initiated update process. current checksum =
    "BCCD5C47988C796DDF2D84B10BB8E345", item checksum =
    "C604943867B330EAE028B93903CE2F08"., update "SVR"."SVR_NOTES" set
    "SVRN_ID" = :b1, "SVRN_SVRL_ID" = :b2, "NOTE_DETAIL" = :b3, "CR_DT" =
    :b4, "CR_USR" = :b5, "LM_DT" = :b6, "LM_USR" = :b7Can anyone help me?
    Thanks in advance,
    Sam

    Hi Sam,
    You can hide the button very easily without deleting it. Click on the Button in the edit page under the button section. Click on the Condition in the heading tab and change the Condition type attribute to Never. It will never display the button in your page.
    Hope this helps.
    Regards,
    M Tajuddin

  • Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01403:

    Hi All,
    I have an ADD ROW and SUBMIT button on my page in APEX. After i add a row or submit it the following error appears,
    Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01403: no data found, update "APPS"."GAU_V" set "PK_FIELDS" = :b1, "SERVICELINEID" = :b2, "SERVICELINEDESC" = :b3, "SERVICEDISPLAYORDER" = :b4, "DIVISION" = :b5
    Error Unable to process update.
    OK
    I have the following select query under region definition :
    select
    "PK_FIELDS",
    "SERVICELINEID",
    "SERVICELINEDESC",
    "SERVICEDISPLAYORDER",
    "DIVISION",
    "STATUSID" // this column was added later in the query
    from "#OWNER#"."GAU_V"
    where "SERVICELINEID" like nvl(:P99_SERVICELINE,'%')
    Order by "SERVICELINEID"
    The region attributes has PK_FIELDS as a hidden column. Value in PK_FIELDS is same as SERVICELINEID column.
    Also the GAU_V view has an INSTEAD OF trigger for insert or update or delete.
    Please tell me the solution for this error..
    Its urgent..
    Regards,
    GTS

    Hi All,
    I have an ADD ROW and SUBMIT button on my page in APEX. After i add a row or submit it the following error appears,
    Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01403: no data found, update "APPS"."GAU_V" set "PK_FIELDS" = :b1, "SERVICELINEID" = :b2, "SERVICELINEDESC" = :b3, "SERVICEDISPLAYORDER" = :b4, "DIVISION" = :b5
    Error Unable to process update.
    OK
    I have the following select query under region definition :
    select
    "PK_FIELDS",
    "SERVICELINEID",
    "SERVICELINEDESC",
    "SERVICEDISPLAYORDER",
    "DIVISION",
    "STATUSID" // this column was added later in the query
    from "#OWNER#"."GAU_V"
    where "SERVICELINEID" like nvl(:P99_SERVICELINE,'%')
    Order by "SERVICELINEID"
    The region attributes has PK_FIELDS as a hidden column. Value in PK_FIELDS is same as SERVICELINEID column.
    Also the GAU_V view has an INSTEAD OF trigger for insert or update or delete.
    Please tell me the solution for this error..
    Its urgent..
    Regards,
    GTS

  • ORA-28500 error message

    Dear all,
    i have oracle 11gR1 installed on RedHat Eterprise linux X86_64 platform. I try to make a heterogeneous connectivity to SQL Server using Oracle Gateway 11g.
    I already configure initdg4msql.ora, listener.ora and tnsnames.ora as in manual.
    when I try to test the database link i've got some error messages
    select * from dual@msqllink;
    Error at line 1:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message: [Oracle][ODBC SQL Server Driver][libssclient22]General network error.
    Check your network documentation.
    [Oracle][ODBC SQL Server Driver][libssclient22]ConnectionOpen (connect()).[Oracle][ODBC SQL Server Driver]Invalid connection string attribute ORA-02063: preceding 2 lines from MSQLLINK
    can anyone tell me the solutions for this problem?
    thanks b4

    actually this is a simple mistake that i found when i'm doing re-check on tnsnames.ora configuration.
    i forgot to change the host name in tnsnames.ora (its still pointing to localhost, not the sqlserver machine IP)

  • ORA-27475: "DBREPORT.GATEKEEPER_JOB" must be a job

    Hi All,
    When ever i am calling the below from a procedure i am getting the error,ORA-27475: "DBREPORT.GATEKEEPER_JOB" must be a job.
    I am getting this error in first drop box it self in(DBMS_SCHEDULER.DROP_JOB ).
    Please help.
    DBMS_SCHEDULER.DROP_JOB
                                   job_name   => 'Gatekeeper_Job',
                                   force  => TRUE,
                                   commit_semantics   => 'STOP_ON_FIRST_ERROR'
                             DBMS_SCHEDULER.create_job (
                              job_name              => 'Gatekeeper_Job',
                              job_type              => 'EXECUTABLE',
                              job_action            => '/home/cobr_sftp/var/controllingload/download/transfer_gatekeeper.sh',
                               number_of_arguments   => 4, 
                             -- auto_drop             => true,
                               enabled               => FALSE,
                              comments              => 'CREATE_PROGRAM test using a schell script'
                           DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
                            job_name                => 'Gatekeeper_Job',
                            argument_position           => 1,
                            argument_value          => ip_d_filename              );
                            DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
                            job_name                => 'Gatekeeper_Job',
                            argument_position           => 2,
                            argument_value          => v_ftype                          );                      
                            DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
                            job_name                => 'Gatekeeper_Job',
                            argument_position           => 3,
                            argument_value          => v_d_db_name          );
                            DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
                            job_name                => 'Gatekeeper_Job',
                            argument_position           => 4,
                            argument_value          => v_sendoraddress      );
                            DBMS_SCHEDULER.enable ('Gatekeeper_Job');Edited by: user11942774 on Oct 21, 2012 6:30 PM

    Then you could be hitting this bug. See the end of this thread
    Unable to drop the dbms_scheduler job using "dbms_scheduler.drop_job"

  • Ora-01427 error

    Hi ,
    i am getting Ora-01427 error when i ran below script . my sub query returns more
    than 1 row . please help me in fixing this .
    update registrant_address a set a.text_res_address_nbr =
    (select c.street_number from registrant_address e , registrant b , z_polk_conv08172005 c
    where e.key_registrant = b.key_registrant and b.key_registrant_old = c.registrant_id)
    thanks,
    Kar

    Hi ,
    i am getting Ora-01427 error when i ran below script
    . my sub query returns more
    than 1 row . please help me in fixing this .
    update registrant_address a set
    a.text_res_address_nbr =
    (select c.street_number from registrant_address e ,
    registrant b , z_polk_conv08172005 c
    where e.key_registrant = b.key_registrant and
    b.key_registrant_old = c.registrant_id)
    thanks,
    Kar
    i am getting Ora-01427 error when i ran below script
    . my sub query returns more
    than 1 row . please help me in fixing this .are you sure that you are getting ORA-01427, because ORA-01422 gives you the message 'Exact fetch returns more than one row' !!
    There are different ways to cope up with this issue,
    1. If you really don't care about a particular street_number, then go for rownum =1 in the where condition if the select statement.
    2. If you care about returning the right value, then probably you need to find out an attribute or a combination of attributes in these three tables used in your select statement that gives you distinct identification for each row.
    Hope this helps
    Thanks

  • ORA-20001: Error

    hi all,
    I have a problem when I try to delete or a save in my my form I am getting this error.
    ORA-20001: Error in DML: p_rowid=52, p_alt_rowid=MSB_ID, p_rowid2=, p_alt_rowid2=. ORA-20001: Current version of data in database has changed since user initiated update process. current checksum = "310B7C5EFC6B9299BC7CB7DB500A2E84" application checksum = "0"
    what can be the problem?
    Thanks.

    1. Please tell us your first name and put it in your handle and/or profile to help us.
    2. Explain all the details of your page (all components and all of their attributes, etc.) or show us the application on apex.oracle.com so we can see it (preferred).
    3. What version of Application Express and database?
    Scott

  • Export Results ORA-00936 Error Reported

    In an attempt to extract all of a package's source code in one file as well as work in a file-oriented fashion (which other posters have commented is not well supported), I issued a select dbms_metadata.get_ddl(...) from dual. This generated the output I wanted in the worksheet results. However, the ORA-00936 error is thrown when I try to export this as text to overwrite my (checked out from source control) file. My only recourse then becomes to copy the result, open my file (outside SQL-D) and replace what's there (which does work, by the way).
    There was another post on this issue in a prior version where the error was attributed to double quotes around aliases, but I'm still getting the error (see Re: Export query results error, v. 5 / 1343

    This is a bug with how SQL Developer does it's export (not that I could find it logged on MetaLink).
    When you export a query, SQL Developer writes a wrapper select around your query to drive the export. In an example of what you are trying to do, it converts the following query (I added an alias to see if that helped, but it didn't):
    select dbms_metadata.get_ddl('PACKAGE', 'MY_PKG') my_ddl from dual;
    to (based on the trace file with sql_trace switched on):
    select * from (select from ( select dbms_metadata.get_ddl('PACKAGE', 'MY_PKG') my_ddl from dual));
    Your immediate options are to continue with your current workaround, switch to a query on DBA_SOURCE for this export, or cope with the way SQL Developer currently does it's file based development.
    As far as getting this fixed (hopefully before 1.1), you would either need to log an SR on MetaLink or hope that one of the SQL Developer team logs a bug based on this thread.

  • ORA-20001: Error in multi row delete operation: ORA-01403: no data

    Whenever I attempt a multi-row delete on my master detail page, I recieve the error:
    ORA-20001: Error in multi row delete operation: ORA-01403: no dataI have seen in other threads that the primary key attribute of the underlying table needs to be set to 'Show' in the report attributes. I have tried this both with it displaying as 'Hidden' ('Show' is unchecked) and with it displaying as text. Either way still gives me the same error.
    Is there anything else not mentioned in the other threads that could be causing this error for me?
    Thanks.
    BoilerUP

    Jimmy,
    In your multi row delete process you specify schema name, table and column name. Your report needs to be of type “SQL query (Updateable report)”. And your report needs to include the primary key column of your table. The column or alias name of that report column needs to correspond with the actual column name of your table.
    Marc

  • ORA-27475: "JOB" must be a job

    Hi All,
    When ever i am calling the below from a procedure i am getting the error,ORA-27475: "DBREPORT.GATEKEEPER_JOB" must be a job.
    I am getting this error in first drop box it self in(DBMS_SCHEDULER.DROP_JOB ).
    Please help.
                                 DBMS_SCHEDULER.DROP_JOB
                                   job_name   => 'Gatekeeper_Job',
                                   force  => TRUE,
                                   commit_semantics   => 'STOP_ON_FIRST_ERROR'
                             DBMS_SCHEDULER.create_job (
                              job_name              => 'Gatekeeper_Job',
                              job_type              => 'EXECUTABLE',
                              job_action            => '/home/cobr_sftp/var/controllingload/download/dbcobra_transfer_gatekeeper.sh',
                               number_of_arguments   => 4, 
                             -- auto_drop             => true,
                               enabled               => FALSE,
                              comments              => 'CREATE_PROGRAM test using a schell script'
                           DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
                            job_name                => 'Gatekeeper_Job',
                            argument_position           => 1,
                            argument_value          => ip_d_filename              );
                            DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
                            job_name                => 'Gatekeeper_Job',
                            argument_position           => 2,
                            argument_value          => v_ftype                          );                      
                            DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
                            job_name                => 'Gatekeeper_Job',
                            argument_position           => 3,
                            argument_value          => v_d_db_name          );
                            DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
                            job_name                => 'Gatekeeper_Job',
                            argument_position           => 4,
                            argument_value          => v_sendoraddress      );
                            DBMS_SCHEDULER.enable ('Gatekeeper_Job');Edited by: user11942774 on Oct 22, 2012 11:21 PM

    Every job has an owner. YOu are probably logged as DBREPORT user.
    It is better to specify full job name in OWNER.JOBNAME
    See who is owner of job
    select * from dba_scheduler_jobs where job_name='GATEKEEPER_JOB';the use fully qualified job name in dbm_scheduler.drop_job procedure

  • Cannot resolve ORA-00955 error.

    I have a script which I run to drop and create preferences, set attributes and drop and create a context index. When dropping and creating preferences and setting the attributes everything works fine and I get the standard messages.
    My problem is I get the
    ORA-00955 name is already used by an existing object
    even after seeing the messages "index dropped" and index created.
    I have checked the ctx_user_index_errors view and the timestamps are from when I approximately ran my script so it seems the index worked.
    I have tried prefacing the index name with the schema name both when dropping and creating the index and I have even tried to use the keyword "force" when trying to drop the index, yet I still get the ORA-00955 error.
    A snippet from my code is below:
    PROMPT 23 DROP oracle text context index
    DROP INDEX schema1.my_index;
    PROMPT 24 CREATE the oracle text context with the above preferences and attributes
    CREATE INDEX schema1.my_index ON docs(doc_contents)
    INDEXTYPE IS ctxsys.context
    PARAMETERS('DATASTORE docs_data_store
    FILTER CTXSYS.INSO_FILTER
    FORMAT COLUMN oracle_text_format_column
    LEXER docs_lexer
    STOPLIST CTXSYS.DEFAULT_STOPLIST
    SECTION GROUP docs_group
    SYNC(ON COMMIT)' )
    /

    I think my problem was I really had a semi colon and a a foward slash at the end of the file, hence there was attempt to create the index twice, once for when the command was ended with a semicolon and once with the foward slash. I just removed the slash and everything worked fine.

  • Report error: ORA-20001: Error fetching column value

    Hi,
    I try to build a tabular form with 1 column as "Select List (Query based on LOV)". This select list should display round about 1.100 rows in the LOV ordered by name. So I got the error: report error:
    ORA-20001: Error fetching column value: ORA-06502: PL/SQL: numerischer oder Wertefehler: character string buffer too small
    When I try tho define this column as Popup LOV (Query based LOV) only the the ID of the attribute and not the display value appeares in the row. The LOV it self displays the display number and not the the ID. I want to see the display value in the column of the particular row and the LOV and return the ID to the record by insert or update as it is normal in LOVs of form regions.
    This lot of rows in the LOV is necessary because it is a part to develop formulas like (number_of_acquisitions - number_of_old_parts)/100 or so. The most formulas will be more complex. In the database there should only be the ID as reference to the attributes.
    Please help me to display the attribute bases on LOV in every particular row.
    Thank you
    Siegwin

    In Apex 4 there is now a column type "Popup Key LOV (named LOV)" which is exactly what you are looking for.
    Edited by: 964978 on Oct 12, 2012 4:53 AM

Maybe you are looking for

  • Itunes won't open because of newer version

    When I try to open my itunes it sits there like it is loading up then a message appears saying "The file 'itunes library' cannot be read because it was created by a newer version of itunes." what does this mean and why can't i open my itunes why?

  • Problem copying iTunes to a external hard drive

    I have been trying to move my very large iTunes library from my Macbook Pro to a external HD to free up space. I have upgraded to iTunes 9 and upgraded the iTunes media organization. I have consolidated my library on my Macbook Pro. I have gone to ad

  • Can i use swing under JSP?

    i have a JSP, now my question is, can I display swing components under JSP?

  • Problems moving pictures between rolls

    I have also posted a topic about a problem combining rolls. This question was originally there too, but I thought it was a bit long, so I split it. To solve my combining rolls problem, I could also move pictures from one roll to another. However, thi

  • Question about variable copying, referencing and LinkedList constructors.

    Is there any advantage in this recommendation? "In general, do make sure that you copy mutable arguments and mutable return values when appropriate." Now, according to this suggestion: public ClassName(LinkedList<String> list)      this.list = new Li