FK Constraints with nonmatching column definitions

Hello,
I ran a healthcheck with TOAD and he reported some foreign keys with nonmatching column definitions:
! Constraint : HERCULES.LBS_VAL_FK
! On Table : HERCULES.LOONBESLAG_SCHULDEISEN
! Columns : VAL_CD VARCHAR2 (5)
! To Table : HERCULES.VALUTA
! Columns : CODE VARCHAR2 (3)
It also mentions that this causes poor performance because of data conversion.
But, varchar2 means that each column has a variable length and this length is stored somewhere. So the value of VAL_CD and CODE will be stored in exactly the same way. No data conversion, no poor performance. Right?
Or am I missing something here?
Thanks for all the feedback.
Rik

I'm quite sure data type conversion doesn't take place here. However the very idea of different types for the PK-FK columns is nonsense, because you cannot fully use this VARCHAR2 (5) column in this case anyway. OK I'm not speaking about deferred constraints :)
Gints Plivna
http://www.gplivna.eu

Similar Messages

Listing foreign keys with non matching column definitions

Dear All,
I seen an entry in DBA weeky activities s that "Listing foreign keys with non matching column definitions" . What is meant by that?. How to pick up that?
Shiju

I seen an entry in DBA weeky activities s that
"Listing foreign keys with non matching column
definitions" . What is meant by that?. How to pick up
that?Most probably find columns which are part of foreign keys, but their respective primary key column have different length (AFAIK data type cannot be different).
Data dictionary can help you in that, I'll give you hints where to look at:
user/all/dba_constraints - foreign and primary keys
user/all/dba_cons_columns - columns which are part of constraints
user/all/dba_tab_columns - column definitions of tables
However creating query from these data dictionary views could be a nice task for you :)
Gints Plivna
http://www.gplivna.eu

Sparse table with many columns

Hi,
I have a table that contains around 800 columns. The table is a sparse table such that many rows
contain up to 50 populated columns (The others contain NULL).
My questions are:
1. Table that contains many columns can cause a performance problem? Is there an alternative option to
hold table with many columns efficiently?
2. Does a row that contains NULL values consume storage space?
Thanks
dyahav

[NULLs Indicate Absence of Value|http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10743/schema.htm#sthref725]
A null is the absence of a value in a column of a row. Nulls indicate missing, unknown, or inapplicable data. A null should not be used to imply any other value, such as zero. A column allows nulls unless a NOT NULL or PRIMARY KEY integrity constraint has been defined for the column, in which case no row can be inserted without a value for that column.
Nulls are stored in the database if they fall between columns with data values. In these cases they require 1 byte to store the length of the column (zero).
Trailing nulls in a row require no storage because a new row header signals that the remaining columns in the previous row are null. For example, if the last three columns of a table are null, no information is stored for those columns. In tables with many columns, the columns more likely to contain nulls should be defined last to conserve disk space.
Most comparisons between nulls and other values are by definition neither true nor false, but unknown. To identify nulls in SQL, use the IS NULL predicate. Use the SQL function NVL to convert nulls to non-null values.
Nulls are not indexed, except when the cluster key column value is null or the index is a bitmap index.>
My guess for efficiently storing this information would be to take any columns that are almost always null and place them at the end of the table definition so they don't consume any space.
HTH!

Data type in column definition

Hi,
I create a table with column called "Direction of Travel code ".
The travel codes in the functional spec are numbers.
In the column definition which one is efficient to define the data type as number or varchar?
Code
1
2
3
4
5
6
7
8
9
0

tijmen wrote:
Tubby wrote:
And then when you issue a query and ask for travel codes 2 through 10 the CBO can't determine that there are 8 values (cardinality wise) because you're not storing the data type in the format you should be storing it as. Statistics? Perhaps even histograms?
Simple testcase:
create table t1(x number(1)) as select mod(rownum, 10) from all_objects where rownum <= 100;
create table t2(x varchar2(1)) as select to_char(mod(rownum, 10)) from all_objects where rownum <= 100;
exec dbms_stats.gather_table_stats(user, 'T1', method_opt => 'FOR ALL COLUMNS SIZE 1');
exec dbms_stats.gather_table_stats(user, 'T2', method_opt => 'FOR ALL COLUMNS SIZE 1');Tried a few simple statements against those (where x = N, where x between N and M), using either literals or bind values. I didn't see any difference in the explain plan...
Not to mention what happens when someone decides to put an "A" in your travel code that should be only numbers, it will eventually happen.Yes, and that's an input error that should be caught by a database constraint (and possibly even before that by the application). Who knows, the codes 0 and 5 might become obsolete as well with changing business rules. Your number datatype is not going to protest when someone still uses them. Hey, maybe even tomorrow someone from the business will come in and demand for the codes 'a' to 'd' to be created. Histograms, application code and database constraints (which all have side effects and add complexity to the system) as opposed to declaring the data type as a NUMBER (which it is). Doesn't seem like a really good argument for intentionally choosing the wrong data type. Well, at least you didn't suggest a trigger in there as well.
>
I'm not saying you should use a char type instead of a number. I'm saying I doubt there's much difference as far as the database is concerned, and I would base the decision on how it works out on the application and business side.As you've found out, the OP stated the functional specs define this as a number. IF in the future the specs change and a business analyst mandates that this support characters as well then the data type gets changed to support the new requirement, no database constraints to remove, no application code to remove, etc...

Interactive Report's Column Definition - Single Row View Label Bug?

Hello,
I have an Interactive report that I've added a Blue background to certain column headings (done by giving Column Heading a background color), this works fine except for the Single Row view - it displays the <....> code I used to get the background color and the column heading. I've tried to change the Single Row View Label by unchecking the 'Use Same Text for Single Row View' on the Column Definition and giving a different label, it just ignores whatever I put in and shows the Column Heading with the < .... > code. Is this a Bug or am I doing something wrong?
Thanks,
Anna

Hi Anna,
I believe that it is a bug.
If the 'Use Same Text for Single Row View' checkbox is unticked and some text is entered in the 'Single Row View Label' field it gets ignored completely when viewed in the single row view and the existing value in 'Column Heading' is used.
I wanted to do something similar to you, colouring some of the Interactive Report column headers, and it works fine in the IR report itself but shows the code (span style:color etc) in the single row query. I am using Apex 3.1.1 and the Sand Theme.
I created a simple application on apex.oracle.com using the red theme and in single row view it still ignores the 'Single Row View Label' but interestingly shows the Column Heading text without the code. This indicates that there could be a work-around by altering the theme.
Regards,
Chris

Is it possible to create a Column with Conditional Mandatory with another Column?

Is it possible to create a Column with Conditional Mandatory with another Column?
For example
In a Table we have column A, B, C.
A is Primary Column.
B is Optional
C is Conditional Mandatory.
A B
C
12345 ABC
OK
12346 NULL
NULL
12347 ABC
OK
Only if the B Column has the value then only C column should be mandatory

I guess you can't create a condtional mandatory column directly. However, you can use check constraint to on the column
create table YourTable
A int primary key,
B char(3),
C int,
constraint ch_con check(
B
is not null
or C is null

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?

DataGrid with dynamic columns & renderers

I'm developing using Flash Builder 4 & Flex SDK 4.1.
I need to manage very dynamic DataGrid components and keep their definitions, which are all part of a complex item renderer of an Offers list.
The objects structure is simplified as follows -
Data: Model --> Offers ArrayCollection --> Offer VO --> DataGrid data ArrayCollection & DataGrid columns Array
View: List --> Offer Item Renderer --> DataGrid
1. Since the DataGrid's columns property accepts only an Array (not ArrayCollection), it seems like Data Binding for defining the columns is very problematic.
I tried to bind it to the source property of an ArrayCollection that would keep my columns definitions, but it didn't really work (mainly header display bugs).
What is the recommended way to keep the dynamic columns definition of a DataGrid?
2. Each column can have a set of dynamic properties, so I created a "mutant" - Column VO that extends DataGridColumn and got a dynamic properties ArrayCollection on it.
The columns got a custom header renderer that includes an icon when there are properties.
The header renderers got 4 main states (NotSelectedWithProperties, SelectedWithProperties, NotSelectedWithoutProperties & SelectedWithoutProperties).
However, the header renderer area seems a bit buggy when maintaning dynamic columns.
Any thoughts on the subject?
3. Anyway, I ended up recreating the DataGrid's columns Array very often (copying the columns definition on the offer's item renderer's dataChange event handler).
Note that the dynamic properties can be edited when the column is selected and I copy their values from the view back to the model when entering the state NotSelectedWithProperties.
This feels way too complicated and I really try to keep it simple, inspite of the required complexity.
Does anyone have better ideas?
4. In some cases the column's item renderer should also be modified into another DataGrid (grid-in-grid).
I used the MXDataGridItemRenderer with a DataGrid and included an ArrayCollection for the "newValue" returned by the editor.
(I use RendererIsEditor=true and on updateComplete populate that variable with the DataGrid's dataProvider contents)
When needed, I loop though the data objects of the parent DataGrid and populate the related field with an ArrayCollection of key-value objects that are displayed on the internal DataGrid.
After adding this feature I encounter very strange bugs -
a. After editing the grid-in-grid values and changing the column's state (selecting & deselecting), I get the following exception:
ArgumentError. Error #2025: The supplied DisplayObject must be a child of the caller.
at flash.display::DisplayObjectContainer/setChildIndex()
at mx.core::UIComponent/setChildIndex().......6993....
All I could find about this is that it might be related to some context error or something, but I'm really stuck on this one.
b. Sometimes another column might copy value from one row to another, running over the previous value.
I'm not sure exactly what sequence of actions causes this behavior, but it's related to that itemRenderer for sure.
c. Switching places with a column that uses the grid item renderer (headerShift) causes a stak overflow of StyleManager that tried to get style from the DataGridItemRenderer. This one I just found out, but couldn't reproduce a second time... strange!
I'm pretty sure this caused another problem that I don't remember at the moment.
The bottom line is that there got to be a better way to implement this feature within this already-complicated environment.
Maybe I'm doing something very wrong here...
Please advice and thanks for reading all this.

Update on item 4a -
This was a major issue (the main reason for opening this thread really) and I managed to resolve it!
As part of my application, I override the default DataGrid behavior for column selection (headerRelease event).
Instead of sorting, I change the column's header looks and define it as Selected (for showing its dynamic properties and enable its deletion).
At first I did this by setting styles, but the look didn't refresh unless I created a new instance of the header renderer.
Later I changed thi behavior to work with states, but I left the new header renderer instance creation commands and those lines created all the mess!
Conclusion -
If you define a custom header renderer for your datagrid column and then a custom item renderer, don't create a new instance of your header renderer!
It would still be nice to get some response for the other issues I raised.
Thanks and have a nice week.

Importing From Flat File with Dynamic Columns

HI
I am using ssis 2008,i have folder in which I have Four(4) “.txt” files each file will have 2 columns(ID, NAME). I loaded 4
files in one destination, but today I receive one more “.txt” file here we have 3 columns (ID, NAME, JOB) how can I get a message new column will receive in source. And how can I create in extra column in my destination table dynamically …please help me

Hi Sasidhar,
You need a Script Task to read the names and number of columns in the first row of the flat file each time and store it in a variable, then create a staging table dynamically based on this variable and modify the destination table definition if one ore more
new columns need to be added, and then use the staging table to load the destination table. I am afraid there is no available working script for your scenario, and you need some .NET coding experience to achieve your goal. Here is an example you can refer
to:
http://www.citagus.com/citagus/blog/importing-from-flat-file-with-dynamic-columns/
Regards,
Mike Yin
TechNet Community Support

TreeTable with inputText column data gets lost in adf 10g

Hello All. I have a TreeTable in my page with two columns for user inputs. After a node is expanded, the data gets lost... The TreeTable was created using ViewObjects, here is one example of the sql query of one of the ViewObjects:
select distinct det.cliente id_cliente
, cust.customer_name descripcion
, city.id_simcot
, to_number(null) horas_normales
, to_number(null) horas_recargo
, 'CLIENTE' tipo
from grc_dist_factura dist
, grc_det_simcot_v city
, grc_det_dist_factura det
, ra_customers cust
where det.id_dist_fact = dist.id_dist_fact
and cust.party_id = det.cliente
and dist.id_det_simcot = city.id_det_simcot
and city.tipo = 'CIUDAD'
The inputText are mapped to the attributes HorasNormales and HorasRecargo. Those columns does not existe in DataBase, that's why I create them in the View Object in that way.
This is my TreeTable:
<af:treeTable value="#{bindings.GrcConfTarifaRaizView.treeModel}"
var="node"
binding="#{ConfiguracionTarifas.treeTable1}"
id="treeTable1" width="100%"
emptyText="No hay un Arbol Disponible.">
<f:facet name="nodeStamp">
<af:column binding="#{ConfiguracionTarifas.column1}"
id="column1" noWrap="true" headerNoWrap="true"
headerText="Descripcion">
<af:outputText value="#{node.Descripcion}"
binding="#{ConfiguracionTarifas.outputText2}"
id="outputText2"/>
</af:column>
</f:facet>
<f:facet name="pathStamp">
<af:outputText value="#{node.Descripcion}"
binding="#{ConfiguracionTarifas.outputText3}"
id="outputText3"/>
</f:facet>
<af:column sortable="false" headerText="Tarifa Hora Normal"
formatType="number"
binding="#{ConfiguracionTarifas.column2}" id="column2">
<af:inputText binding="#{ConfiguracionTarifas.txtHoraNormal}"
id="txtHoraNormal" rendered="#{node.Tipo ne 'RAIZ'}"
value="#{node.HorasNormales}">
</af:inputText>
</af:column>
<af:column sortable="false" headerText="Tarifa Hora Recargo"
formatType="number"
binding="#{ConfiguracionTarifas.column3}" id="column3">
<af:inputText binding="#{ConfiguracionTarifas.txtHoraRecargo}"
id="txtHoraRecargo" rendered="#{node.Tipo ne 'RAIZ'}"
value="#{node.HorasRecargo}"/>
</af:column>
</af:treeTable>
And this is the page Def:
<tree id="GrcConfTarifaRaizView"
IterBinding="GrcConfTarifaRaizViewIterator">
<AttrNames>
<Item Value="IdSimcot"/>
<Item Value="Descripcion"/>
<Item Value="Tipo"/>
<Item Value="HorasNormales"/>
<Item Value="HorasRecargo"/>
</AttrNames>
<nodeDefinition DefName="gsgappl.grc.datamodel.view.confTarifa.GrcConfTarifaRaizView"
id="GrcConfTarifaRaizViewNode">
<AttrNames>
<Item Value="IdSimcot"/>
<Item Value="Descripcion"/>
<Item Value="Tipo"/>
<Item Value="HorasNormales"/>
<Item Value="HorasRecargo"/>
</AttrNames>
<Accessors>
<Item Value="ClientesView"/>
</Accessors>
</nodeDefinition>
<nodeDefinition DefName="gsgappl.grc.datamodel.view.confTarifa.GrcConfTarifaClientesView"
id="GrcConfTarifaClientesViewNode">
<AttrNames>
<Item Value="IdCliente"/>
<Item Value="Descripcion"/>
<Item Value="IdSimcot"/>
<Item Value="Tipo"/>
<Item Value="HorasNormales"/>
<Item Value="HorasRecargo"/>
</AttrNames>
<Accessors>
<Item Value="RegionalesView"/>
</Accessors>
</nodeDefinition>
<nodeDefinition DefName="gsgappl.grc.datamodel.view.confTarifa.GrcConfTarifaRegionalesView"
id="GrcConfTarifaRegionalesViewNode">
<AttrNames>
<Item Value="CodRegional"/>
<Item Value="Descripcion"/>
<Item Value="IdSimcot"/>
<Item Value="IdCliente"/>
<Item Value="Tipo"/>
<Item Value="HorasNormales"/>
<Item Value="HorasRecargo"/>
</AttrNames>
<Accessors>
<Item Value="CiudadesView"/>
</Accessors>
</nodeDefinition>
<nodeDefinition DefName="gsgappl.grc.datamodel.view.confTarifa.GrcConfTarifaCiudadesView"
id="GrcConfTarifaCiudadesViewNode">
<AttrNames>
<Item Value="CodCiudad"/>
<Item Value="Descripcion"/>
<Item Value="CodRegional"/>
<Item Value="IdSimcot"/>
<Item Value="IdCliente"/>
<Item Value="Tipo"/>
<Item Value="HorasNormales"/>
<Item Value="HorasRecargo"/>
</AttrNames>
</nodeDefinition>
</tree>
Note the Node Definition for gsgappl.grc.datamodel.view.confTarifa.GrcConfTarifaClientesView, it correspond to the View Object showed at the beginning of the post.
Can any one help me please?
bye

Thanks for the links.
I checked them up, but first, I noticed they apply to adf 11g, and second none of them use inputText in columns. I really couldn't find a any idea to solve my issue.
Any other suggestions?
My problem is that when I expand/collapse a node, the values in the inputTexts are lost. I don't know if I need something else on my page Definition...
thank you.

Import is very Slow with xmltype column in oracle 9.2.0.7

Hi
We are using oracle 9.2.0.7 on Solaris
The import without XMLTYPE column is faster the import of the table with XMLTYPE column.Also when we do the export in direct path it is still going for Conventional(I suppose this is correct for XMLTYPE).
Is this the general behaviour of XMLTYPE...if so how to improve the performance of the import.
Can anybody help us out in resolving the issue.

here is the output
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
CREATE TABLE "MMSCBMC"."PAYMENTS_AUDIT"
( "PMTID" NUMBER NOT NULL ENABLE,
"PMTSTATUS" VARCHAR2(32) NOT NULL ENABLE,
"PMTSTATUS_CODE" VARCHAR2(10) NOT NULL ENABLE,
"CSREFID" VARCHAR2(32),
"CURAMT" NUMBER(15,2) NOT NULL ENABLE,
"CUSTOMER_KEY" NUMBER NOT NULL ENABLE,
"ACCTID" VARCHAR2(32) NOT NULL ENABLE,
"BANKREFID" VARCHAR2(34) NOT NULL ENABLE,
"PAYEEID" NUMBER,
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
"PAYMENTS_AUDIT_KEY" NUMBER NOT NULL ENABLE,
"PROCDATE" DATE NOT NULL ENABLE,
"DUEDATE" DATE NOT NULL ENABLE,
"IMMEDIATE_GENERATION" NUMBER DEFAULT 0 NOT NULL ENABLE,
"RECURRINGPMTID" NUMBER,
"BATCHID" NUMBER,
"REMIT_INFO" VARCHAR2(200),
"BILLING_ACCT" VARCHAR2(32),
"PAYMENT_METHOD" VARCHAR2(20) NOT NULL ENABLE,
"IS_ACCTNUMBER" NUMBER,
"SPREFID" VARCHAR2(36),
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
"FIDEBITTRCNUM" VARCHAR2(32),
"FEE" NUMBER(12,2),
"FEE_TYPE" VARCHAR2(10) DEFAULT NULL ,
"DATE_ADDED" DATE NOT NULL ENABLE,
"CLIENTIP" VARCHAR2(32) NOT NULL ENABLE,
"LAST_UPDATED" DATE NOT NULL ENABLE,
"ACTION" VARCHAR2(32),
"MODIFIEDBY" VARCHAR2(32) NOT NULL ENABLE,
"ISCSR" VARCHAR2(1) NOT NULL ENABLE,
"SUBUSER_KEY" NUMBER,
"TOKEN" NUMBER DEFAULT 0 NOT NULL ENABLE,
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
"FUNDINGSTATUS_CODE" NUMBER DEFAULT 0 NOT NULL ENABLE,
"FUNDINGSTATUS" VARCHAR2(32) DEFAULT 'Funds Pending' NOT NULL ENABLE,
"PRODUCT_CODE" VARCHAR2(10),
"SUB_PRODUCT_CODE" VARCHAR2(10),
"ACCT_TYPE" VARCHAR2(3),
"DEST_PRODUCT_CODE" VARCHAR2(10),
"DEST_SUB_PRODUCT_CODE" VARCHAR2(10),
"DEST_BANKREFID" VARCHAR2(34),
"DEST_ACCT_TYPE" VARCHAR2(3),
"ISDEBIT" NUMBER NOT NULL ENABLE,
"PAYMENTFROM_NICKNAME" VARCHAR2(96),
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
"PAYMENTFROM_ACCTID" VARCHAR2(32),
"PAYMENTTO_NICKNAME" VARCHAR2(96),
"PAYMENTTO_ACCTID" VARCHAR2(32),
"DEST_ISBUSINESSACCT" NUMBER,
"APPROVE_DATE" DATE,
"APPROVE_KEY" NUMBER,
"LAST_MODIFIER_KEY" NUMBER,
"CHECK_DESC" VARCHAR2(200),
"FAILURE_REASON" VARCHAR2(250),
"PMTFUNDRETRY_COUNT" NUMBER DEFAULT 0 ,
"MQ_TRANSACTIONID" NUMBER,
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
"FREQUENCY" NUMBER,
"NUMBEROFREMPAYMENTS" NUMBER,
"OPENENDED" NUMBER,
"ORIGINATOR_KEY" NUMBER NOT NULL ENABLE,
"EXTERNALREFERENCE" "SYS"."XMLTYPE" ,
"EXTERNALINFO" "SYS"."XMLTYPE" ,
"PRINCIPAL_AMT" NUMBER(15,2),
"ESCROW_AMT" NUMBER(15,2),
"LATEFEE_AMT" NUMBER(15,2),
"OTHERFEE_AMT" NUMBER(15,2),
"REGULARPMT_AMT" NUMBER(15,2),
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
CONSTRAINT "PK_PAYMENTSADT_KEY" PRIMARY KEY ("LAST_UPDATED", "PAYMENTS_AUDIT_K
EY")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "MMS_DATA_TBS" ENABLE,
CONSTRAINT "FK01_PAYMENTS_AUDIT" FOREIGN KEY ("APPROVE_KEY")
REFERENCES "MMSCBMC"."CUSTOMER" ("CUSTOMER_KEY") ENABLE,
CONSTRAINT "FK02_PAYMENTS_AUDIT" FOREIGN KEY ("LAST_MODIFIER_KEY")
REFERENCES "MMSCBMC"."CUSTOMER" ("CUSTOMER_KEY") ENABLE,
CONSTRAINT "FK06_PAYMENTS_AUDIT" FOREIGN KEY ("ORIGINATOR_KEY")
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
REFERENCES "MMSCBMC"."ORIGINATOR" ("ORIGINATOR_KEY") ENABLE
) PCTFREE 2 PCTUSED 40 INITRANS 1 MAXTRANS 255 LOGGING
STORAGE(
BUFFER_POOL DEFAULT)
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS"
PARTITION BY RANGE ("LAST_UPDATED")
(PARTITION "M1_2005" VALUES LESS THAN (TO_DATE(' 2005-02-01 00:00:00', 'SYYYY-
MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
PCTFREE 2 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS"
LOB ("SYS_NC00059$") STORE AS (
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSI
ON 10
NOCACHE
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT))
LOB ("SYS_NC00061$") STORE AS (
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSI
ON 10
NOCACHE
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)) NOCOMPRESS ,
PARTITION "M2_2005" VALUES LESS THAN (TO_DATE(' 2005-03-01 00:00:00', 'SYYYY-M
M-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
PCTFREE 2 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS"
LOB ("SYS_NC00059$") STORE AS (
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSI
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
ON 10
NOCACHE
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT))
LOB ("SYS_NC00061$") STORE AS (
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSI
ON 10
NOCACHE
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)) NOCOMPRESS ,
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
PARTITION "MAX_VALUE" VALUES LESS THAN (MAXVALUE)
PCTFREE 2 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS"
LOB ("SYS_NC00059$") STORE AS (
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSI
ON 10
NOCACHE
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT))
DBMS_METADATA.GET_DDL('TABLE','PAYMENTS_AUDIT')
LOB ("SYS_NC00061$") STORE AS (
TABLESPACE "PAYMENTS_AUDIT_DATA_TBS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSI
ON 10
NOCACHE
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)) NOCOMPRESS )

Unicode : cannot filter query with NVARCHAR2 column

Hi,
this is not a POL/SQL-Developer specific problem - but help would be appreciated.
Configuration Server :
NLS_CHARACTERSET WE8ISO8859P15
NLS_NCHAR_CHARACTERSET AL16UTF16
Client :
NLS_LANG GERMAN_GERMANY.WE8MSWIN1252
Column definition :
LEGALNAME NVARCHAR2 (255);
If i store for example a kyrillic name with the application i am able to finde the row searching the for the most current modification date and with correct kyrillic coded name.
but if i want to query by the Legalname - a)/b) does not work;
A) SELECT * FROM COMPANY WHERE LEGALNAME LIKE 'View, системой%';
B) SELECT * FROM COMPANY WHERE LEGALNAME LIKE N'View, системой%';
Do you have some hints???
kind regards
Karl
Edited by: [email protected] on 10-Mar-2009 07:05
Edited by: [email protected] on 10-Mar-2009 07:10
Edited by: Spinthma on 12-Mar-2009 03:23

Hello Sergiusz,
first thanks a lot for your taking time!!
it did not work for PL/SQL-Developer (applied both registry - all oracle homes and in environment)
but it worked for Oracle SQL-Developer according your last posting;
[m-1951097]
bq. {color:#808080}By default, SQL Developer uses the JDBC Thin driver. This driver does not recognize the ORA_NCHAR_LITERAL_REPLACE, but the oracle.jdbc.convertNcharLiterals property. Try to add this property to the <SQLDEV_HOME>\sqldeveloper\bin\sqldeveloper.conf file: \\ AddVMOption -Doracle.jdbc.convertNcharLiterals=true \\ Let us know if it helps. I have no time to test myself. \\ {color} \\ {color:#808080} \\ Sergiusz{color}
{color:#000000}Karl{color}
bq. {color:#808080} \\ {color}

Interactive Report with Checkbox column

Hello everyone,
our users love the Interactive Report filtering, so they want all forms in apps. to behave like Interactive Reports.
I need a form where each row consists of 2 columns and a checkbox, that handles some flag. I can create checkboxes using APEX_ITEM, however, the filtering on such column look ridicolous. I would like to have a tabular form (with one editable checkbox column), but with all those Interactive Report filtering features.
Is there any example (or inspiration) how to achieve such functionality?
Thanks a lot!
Adam

Hello Adam,
Why don't you just switch off the Filtering option for that column?
(Go to the Interactive Report, click on your column, then in Column Definition you can (un)check the features for that column).
Greetings,
Roel
http://roelhartman.blogspot.com/
You can reward this reply by marking it as either Helpful or Correct ;-)

Exporting Table with CLOB Columns

Hello All,
I am trying to export table with clob columns with no luck. It errors saying EXP-00011TABLE do not exist.
I can query the table and the owner is same as what i am exporting it from.
Please let me know.

An 8.0.6 client definitely changes things. Other posters have already posted links to information on what versions of exp and imp can be used to move data between versions.
I will just add that if you were using a client to do the export then if the client version is less than the target database version you can upgrade the client or better yet if possilbe use the target database export utility to perform the export.
I will not criticize the existance of an 8.0.6 system as we had a parent company dump a brand new 8.0.3 application on us less than two years ago. We have since been allowed to update the database and pro*c modules to 9.2.0.6.
If the target database is really 8.0.3 then I suggest you consider using dbms_metadata to generate the DDL, if needed, and SQLPlus to extact the data into delimited files that you can then reload via sqlldr. This would allow you to move the data with some potential adjustments for any 10g only features in the code.
HTH -- Mark D Powell --

Select list with multiple columns

I want to create a select list with multiple column option. What are the options. Any developments in apex 3.0.1 ? Thanks in advance. I tried the tutorials by Kubicek.
I am kind of stuck to see the function entry inside LOV definition returns a error.

Still really one column.
If they need to be independent then you've got to have three selection lists.
%

FK Constraints with nonmatching column definitions

Similar Messages

Maybe you are looking for