Element order is not preserved in NESTED TABLES.

I may be silly, but I cant understand it.
Steven Feurenstein : Unlike nested tables, when you store and retrieve a VARRAY, its element order is preserved.
Element order is not preserved in NESTED TABLES.
What does it mean?
Thanks..

Could you please give an example?He just did? A nested table is really a table like any other, so the same rule applies: if you want the data selected in a specific order, you must use ORDER BY.

Similar Messages

"member of " not working with nested table of dates

Can someone explain why this doesn't work. The last select does not return any row. When trying the same with a table of number, it works fine.
drop table test;
drop type date_tab;
create type date_tab as table of date;
create table test(dates date_tab) nested table dates store as dates;
insert into test values (date_tab(to_date('10-jan-2007'),to_date('15-jan-2007'),to_date('15-jan-2007')));
commit;
select * from test where to_date('10-jan-2007') member of dates;
Line above should find the row, but does not return anything.

> With 10G Oracle said that these two engines are now sharing the same source code
Is that documented somewhere? Regarding database versions, it was 9.0.1 that claimed an integrated parser. I don't see any update for 10g.
> So in the old days one had to do a [SELECT sysdate INTO d FROM dual] to assign a function value to a PL/SQL var - as the function did not exist in PL/SQL.
Then (from Oracle 7 onwards?) these functions were also available in PL/SQL. However, the two engines did not share common code. So functions in SQL did not always behave like function in PL/SQL and vice versa.
I don't recall that limitation in PL/SQL v1 (Forms 3 to 4.5, and database v6, though I doubt many people actually used PL/SQL on the database because (1) it was separately licensed, and (2) it didn't have stored procedures) - but then it was a while ago so I could be mistaken.
I know USER, SYSDATE and others used to be implicit queries of dual (i.e. the supplied PL/SQL function was just a wrapper containing SELECT SYSDATE INTO dt FROM dual; RETURN dt;) although that's probably just confusing the issue.

BUG: Jdev 11.1.1.0.0 -- DB table data export column order is not preserved

Hello,
I've ran into a problem with Jdeveloper 11g, public release, Build JDEVADF_MAIN.BOXER_GENERIC_081002.2127.5156. Oracle IDE version is 11.1.1.0.31.51.56
When I connect to Oracle database, get the table list, right click on the table and select 'Export Data'->csv. The dialog box opens with three tabs: Format, Columns, Where. The column order displayed in both tabs Columns and Where is alphabetic. Because alphabetic ordering re-arranges columns from their initial ordering in the table, this screws up the export because columns are not in their intended order. This same problem occurs when I try to export data from views to generate a CSV file with a particular column order for our vendor. Since Jdev scrambles the column order I have to rely on SQLdeveloper to generate CSV exports, since SQLdeveloper has the same functionality but it preserves the column order.
It would be nice if Jdeveloper preserved the column order on export.
Thanks!

Update:
This bug is now also present in the SQL Developer 1.5.3.
I've posted a bug report on the appropriate forum: BUG: SQL Developer 1.5.3 CSV export column order broken

EXP/IMP does not preserve MONITORING on tables

Consider the following (on 8.1.7):
1. First, create a new user named TEST.
SQL> CONNECT SYSTEM/MANAGER
Connected.
SQL> CREATE USER TEST IDENTIFIED BY TEST;
User created.
SQL> GRANT CONNECT, RESOURCE TO TEST;
Grant succeeded.2. Connect as that user, create a table named T and enable monitoring on the table.
SQL> CONNECT TEST/TEST
Connected.
SQL> CREATE TABLE T(X INT);
Table created.
SQL> ALTER TABLE T MONITORING;
Table altered.
SQL> SELECT TABLE_NAME, MONITORING FROM USER_TABLES WHERE TABLE_NAME = 'T';
TABLE_NAME                     MON
T                              YES3. Export the schema using EXP.
SQL> HOST EXP OWNER=TEST FILE=TEST.DMP CONSISTENT=Y COMPRESS=N4. Drop and recreate the user.
SQL> CONNECT SYSTEM/MANAGER
Connected.
SQL> DROP USER TEST CASCADE;
User dropped.
SQL> CREATE USER TEST IDENTIFIED BY TEST;
User created.
SQL> GRANT CONNECT, RESOURCE TO TEST;
Grant succeeded.5. Finally, connect as the user, and import the schema.
SQL> CONNECT TEST/TEST
Connected.
SQL> HOST IMP FROMUSER=TEST TOUSER=TEST FILE=TEST.DMPNow monitoring is no longer enabled:
SQL> SELECT TABLE_NAME, MONITORING FROM USER_TABLES WHERE TABLE_NAME = 'T';
TABLE_NAME                     MON
T                              NOIs this behaviour documented anywhere?
Are there any IMP/EXP options that will preserve MONITORING?

Apparently it's a non-public bug #809007 in 8.1.7 which should be fixed with 9i

Update photoshop elements catalog did not preserve people tags

I recently bought Lightroom, having been a long-standing user of Elements. I tried to update my Elements 11 catalog, but many of my pictures have People tags which failed to make it through into the Lightroom catalog. In other words, many of my pictures, when looking at them in Lightroom, don't have the tags for the names of the people in the pictures, even though this information was present in Elements 11.
Is there something I can do to get the People information across from Elements 11 into Lightroom 4.3?
Thanks
Rob

I see you have already tried the usual methods.
One thing that puzzles me is the screenshot with the file 'thumbs.5.cache'.
That file is the cache storing the thumbnails : it's an sqlite database just like the main catalog : catalog.pse11db.
Normally, when you 'optimize' the catalog, that cache file is rebuilt, but sometimes the only way to replace it is to delete it, and wait for the Organizer to rebuild it (several hours in your case...)
It would not hurt to do so in PSE10 before trying the conversion.
The conversion in PSE11 also converts (or make a copy ?) of the cache file.
In my tests, the conversions in PSE11 do work even if the cache file is missing, and even if there are missing files. So, trying to convert without the cache file and let the Organizer rebuild the thumbnails in PSE11 is possible.
Edit:
I see 99jon was on the same track.

XML Query Performance on Nested Tables

I am running an Xpath query on an XMLTYPE column extracting rows from a nested table which is two levels down from the root element:
e.g.
select extractValue(x.xmldata,'/rootElement/VersionNumber') VerNumber
, etc...
, etc.
, extractValue(value(m),'/Member/Name/Ttl') Member_title
, to_char(extractValue(value(e),'/Event/EventDate'),'yyyy-mm-dd') Event_Date
, extractValue(value(e),'/Event/Type') Event_type
from xml_table x,
table(XMLSequence(extract(x.xmldata,'/rootElement/Member'))) m
,table(XMLSequence(extract(value(m),'/Member/Event'))) e
The query is taking around 7 minutes to process 2000 XML docs and the result returns 61,000 rows.
Statspack reports indicate that the main resource used is the LOBSEGMENT which supports the SYS_XDBPD$ column (system generated) in the Member nested table - result was over 100 million Logical Reads and Consistent Gets.
Is there any way to influence the Schema Registration/XML Table creation to result in the XDBPD$ column being stored as a Table or VARRAY - the underlying data type for XDBPD$ is:
XDB.XDB$RAW_LIST_T VARRAY(1000) OF RAW(2000)
OR
Should I spend time tuning access to the LOBSEGMENT?
Anyone tuned this area of XDB before??
Thanks
Dave

Do you need DOM Fidelity at all. DOM Fidelity is typically only needed in a document orientated application or where items like processing instructions and comments are present and need to be maintaned.
Here are some notes from some training ppt slides that may help you decide
Dom Fidelity requires that XML DB track document level meta data
It creates overhead when inserting and retrieving XML due to processing as well as adding additional storage requirements. Dom Fidelity can be turned on and off at the 'Type' Level Each SQL Type corresponding to a complexType where DOM is enabled includes a System Binary attribute called SYS_XDBPD$. The SYS_XDBPD$ attribute is referred to as the Positional Descriptor (PD)
The PD is used to manage the instance level meta data. The format of the PD is not documented The PD is stored as a (in-line) LOB.
The PD is used to track
Comments and Processing Instructions
Location and Prefixes in Namespace declarations
Empty Vs Missing Nodes
Presence of Default Values
Use of Substitutable elements
Ordering of elements in all and choice models
XMLSchemaInstance attributes
xsi:nil, xsi:Type
Mixed content
Text() nodes that are interspaced with elements
Disabling DOM Fidelity improves performance
Reduces storage requirements
Reduces elapsed time for insert and retrieval operations
DOM Fidelity is disabled on a Type by Type basis
Use annotation xdb:maintainDOM="false on complexType definition
Specifying xdb:maintainDOM="false
Removes the PD attribute from the SQLType.
Causes the information managed in the PD to be discarded when shredding the XML document
In general you can disable DOM Fidelity when
All information is represented as simple content
Elements with text() node children and or attribute values
XML does not make use Mixed Text
No Comments or Processing Instructions
Applications do not need to differentiate between empty and missing elements
Applications do not differentiate between default Vs missing values
Order of elements in repeating Sequence, All and Choice models is not meaningful
Typically Data-Centric XML does not require DOM Fidelity while Document Centric XML does. With DOM Fidelity disabled retrieved documents will still be valid per the XML Schema
Order is preserved when repetition is specified at element or complexType level
Use annotation xdb:maintainOrder=false for slight performance improvement in this case that order is not required in these cases.
Order is not preserved when repetition is specified at the model level, eg on a Choice, Sequence or All containing multiple child elements.
Take the following document
<?xml version="1.0" encoding="UTF-8"?>

<dft:root xmlns:dft="domFidelityTest"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="domFidelityTest domFidelityExample">
<?SomePI SomeValue?>
     <xxx:choice xmlns:xxx="domFidelityTest">
     
          <xxx:A>String</xxx:A>
          <xxx:B>String</xxx:B>
          <?Another PI SomeOtherValue?>
          <xxx:C>String</xxx:C>
          <xxx:A>String</xxx:A>
          
          <xxx:B>String</xxx:B>
          <xxx:C xsi:nil="true"/>
</xxx:choice>
</dft:root>
With DOM Fidelity disabled it would come back as
<?xml version="1.0" encoding="WINDOWS-1252"?>

<dft:root xmlns:dft="domFidelityTest testAttr="NotInOriginal">
<dft:choice>
<dft:A>String</dft:A>
<dft:A>String</dft:A>
<dft:B>String</dft:B>
<dft:B>String</dft:B>
<dft:C>String</dft:C>
<dft:C/>
</dft:choice>
</dft:root>
In general you can disable DOM Fidelity and see reduced storage requirements and increased throughout...
Hope this helps...

Problem with Nested Table

I am trying to make a nested table receive an arbitrary number of values (from a shuttle) through a loop, and then insert the table into a table of nested table in my database. The problem I am having is that when I try to insert more than one value into the nested table, it will only insert the last item in the loop into the database. Thanks in advance.
This is the code I used to create my objects:
create or replace type OUTPUT_TY as object( ATTRIBUTE_ID Number(8) )
create or replace type OUTPUTS_NT as table of OUTPUT_TY
This is my actual code in ApEx:
declare
temp_NT OUTPUTS_NT;
temp_TY OUTPUT_TY;
temp Number(10);
l_vc_arr2 htmldb_application_global.vc_arr2;
begin
temp_nt := outputs_nt();
l_vc_arr2 := HTMLDB_UTIL.string_to_table (:P2_SHUTTLE, ':');
FOR i IN 1 .. l_vc_arr2.COUNT
LOOP
temp_ty := output_ty(l_vc_arr2(i)) ;
temp_NT:= outputs_nt(temp_ty);
END LOOP;
INSERT INTO OUTPUT_TEST values (temp_NT);
commit;
end;

> temp_NT:= outputs_nt (temp_ty);You are not extending the nested table / collection, you are simply assigning an entirely new collection to it for each element of l_vc_arr2.
Try something like...
FOR i IN 1 .. l_vc_arr2.COUNT LOOP
   temp_ty := output_ty (l_vc_arr2 (i));
   temp_nt.EXTEND;
   temp_nt (temp_nt.LAST) := temp_ty;
END LOOP;Or perhaps more succintly...
FOR i IN 1 .. l_vc_arr2.COUNT LOOP
   temp_nt.EXTEND;
   temp_nt (temp_nt.LAST) := output_ty (l_vc_arr2 (i));
END LOOP;

Nested table as column & foreign key

Hi,
I have question - is possible to create foreign key (constraint) which references to element in nested table (for example element named ID)?
Thanks for replies, Petr

Also, what is the logic of foreign key constraint not being supported? The following is supposition.
As far as I know, Oracle have not formally explained why this is not supported. My guess is: it's too hard.
Quite why it's too hard I don't know but I suspect it is to do with the implementation of NESTED TABLEs. Remember, the actual data for the Nested Table is stored in a separate table - that's why we need the STORE AS clause. Consequently, the nested table already has a foreign key - to join the rows in it to the appropriate rows in the parent table - which is not exposed to us (it uses magic columns).
This is just another good reason not to use nested tables to store data. Just have a proper child table and then you can build all the reational integrity you like.
Cheers, APC

Third party sales orders are not showing in Billing due list (VF04 )

Hi,
In Billing due list Third party sales orders are not appearing because VKDFS table those entries are there. How can we get Third party sales orders in VKDFS table as well as VF04 ?
Please suggest me.
Regards,
KUR

Hi Kur & Sandepp,
Check this notes:A) Note 210500 - Billing status of a third-party item,B)2) Note 210561 - When is a third-party item displayed in VF04.
Re
Regards,
Madhu.

CRM sales order is not saved in CRM but in ECC

Hi,
I am new CRM area and will not some hints on where to check.
When the the Sales orders are successfully created in CRM, they are replicated to R/3 but the sales orders are not saved in CRMD_ORDERADM_H table of the CRM system.
Also, I dont know see any details of the sales order in the interaction record document flow.
Can you please help me with any hints on where to check to fix this issue..

Hi Sangameshwar,
In CRM you can have two scenarios for ERP Sales Order.
1. ERP Sales offer and Sales order, using the CRM User Interface to create directly the ERP Sales Documents with LORD interface. The document is only saved in ERP. I believe this the scenario you are using.
2. CRM Sales offer and Sales order, the document is saved both CRM and ERP. The documents are replicated via Middleware.
In both scenarios the interaction record should add the document in the doc. flow, it's probably a missing customizing in the interaction record.
Hope this information help you.
Regards,
Jorge G.

Sql*loader and nested tables

I'm having trouble loading a nested table via sqlldr in Oracle 10g and was hoping someone could point me in the right direction. I keep getting the following error:
SQL*Loader-403: Referenced column not present in table mynamespace.mytable
Here's an overview of my type and table definitions:
create type mynamespace.myinfo as object
i_name varchar2(64),
i_desc varchar2(255)
create TYPE mynamespace.myinfotbl as TABLE of mynamespace.myinfo;
create table mynamespace.mytable
Info mynamespace.myinfotbl,
note varchar2(255)
NESTED TABLE Info STORE AS mytable_nested_tab;
My control file looks like this:
load data
infile 'mydatafile.csv'
insert into table mynamespace.mytable
fields terminated by ',' optionally enclosed by '"'
TRAILING NULLCOLS
Info nested table count(6)
Info column object
i_name char(64),
i_desc char(255)
note
Example mydatafile.csv would be something like:
lvl1,des1,lvl2,des2,lvl3,des3,lvl4,des4,lvl5,des5,lvl6,des6,a test data set
I can't figure out why sqlldr keeps rejecting this control file. I'm using 'direct=false' in my .par file.
Any hints?

I just noticed that my email is wrong. If you can help, plese send email to [email protected]
thanks.

Nested Tables and Predictable Attributes

BOL states "The data in a nested table can be used for prediction or for input, or for both. For example, you might have two nested table columns in a model: one nested table column might contain a list of the products that a customer
has purchased, while the other nested table column contains information about the customer's hobbies and interests, possibly obtained from a survey. In this scenario, you could use the customer's hobbies and interests as an input for analyzing purchasing behavior,
and predicting likely purchases."
However I cannot find where it states you cannot use a predictable attribute from a Nested Table within the Neural Network algorithm.
Can you please tell me why I receive the error "Microsoft Neural Network does not support predictable nested tables" when attempting to process my model with one predictable column in a Nested Table, or am I missing something? The
same structure works fine for Naive Bayes, Decision Trees etc but not for Neural Network of Logistic Regression.

Hi Namak,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Charlie Liao
TechNet Community Support

HOw to improve insert/update/select for nested table.

Hi All,
I think this is my second thread for nested table.
i just want to know what are the different ways available to improve the insert/update/select operation on Nested table.
Thanks in advance.

By not using a nested table for data storage in the first place...
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:8135488196597
Perhaps Parallel Query/DML might give some relief.

JAXB, element order and optional elements

Hi,
I am trying to write a program that depends on JAXB and I am encountering a number of problems. The first is that the party from which we get our XML data from is capable of sending the elements in a given element in any order and JAXB is very stringent about order, is there any way to override this behaviour? The next, is if an element, that has children, is marked as optional in the DTD, JAXB will treat it as mandatory which also creates problems for us as some of these type of elements are optional.
Does anyone know when JAXB ea2 is due?

To your second topic, this is a known bug in the EA, see
http://developer.java.sun.com/developer/bugParade/bugs/4497267.html
To the first topic: If you define the DTD in a way, that the element order is not fixed, then JAXB should accept that. E.g. instead of<!ELEMENT foo (a,b,c)>you could write<!ELEMENT foo ((a|b|c)*)>Of course, this is even looser, as it does not prevent you from sending multiple instances of a, b and c, and the generated code does not contain a getA, getB and getC method, but just a getContent returning a List.

Insert into Nested Tables

Good day All,
I am working on my first nested table and having difficulty with INSERTS. Can someone explain what I am doing wrong?
Many Thanks,
Danny
describe PAT_HOST_SYSTEM
Name Null Type
HOST_ID NOT NULL NUMBER
IPADDR NOT NULL VARCHAR2(16 CHAR)
OS VARCHAR2(50 CHAR)
OS_VERSION VARCHAR2(254 CHAR)
KERNEL VARCHAR2(75 CHAR)
KERNEL_BUILD VARCHAR2(75 CHAR)
LAST_REBOOT VARCHAR2(50 CHAR)
OS_PATCH VARCHAR2(50 CHAR)
NUM_OF_CPU VARCHAR2(20 CHAR)
GLOBAL_ZONE VARCHAR2(3)
LOCAL_ZONE VARCHAR2(3)
MACHINE VARCHAR2(255)
UPTIME VARCHAR2(50)
LAST_UPDATE DATE
ZONE_CHILDREN LOCAL_ZONE()
15 rows selected
describe LOCAL_ZONE
user type definition
TYPE local_zone AS OBJECT
(ID VARCHAR2(50),
ZONE_NAME VARCHAR2(50));
3 rows selected
INSERT INTO TABLE (SELECT ZONE_CHILDREN FROM PAT_HOST_SYSTEM WHERE HOST_ID='561') VALUES ('a808d6ceee', 'tspxxx01');
Error starting at line 1 in command:
INSERT INTO TABLE (SELECT ZONE_CHILDREN FROM PAT_HOST_SYSTEM WHERE HOST_ID='561') VALUES ('a808d6ceee', 'tspxxx01')
Error at Command Line:1 Column:12
Error report:
SQL Error: ORA-22905: cannot access rows from a non-nested table item
22905. 00000 - "cannot access rows from a non-nested table item"
*Cause:    attempt to access rows of an item whose type is not known at
parse time or that is not of a nested table type
*Action:   use CAST to cast the item to a nested table type

Hello Danny and welcome to the forum,
are you trying to insert data into a table which has a collection as a column ?
The phrase nested table was very misleading (at least for me), also the code you posted was kinda incomplete.
I could not follow the code you posted, alternately I am posting some sample code with the DDL and insert statements for your understanding.
create or replace type emp_obj as object
ejob varchar2(100),
comm number,
edeptno number
create table employee
(ename varchar2(50),
empno number,
esal number,
edetails emp_obj
/Populating the employee table with INSERT :
insert into employee values ('KING',7839,5000,emp_obj('PRESIDENT',0,10));
insert into employee values ('BLAKE',7698,2850,emp_obj('MANAGER',0,30));Now, querying the table for all columns with SELECT :
ENAME     EMPNO     ESAL     EDETAILS.EJOB     EDETAILS.COMM     EDETAILS.EDEPTNO
KING     7839     5000     PRESIDENT         0                 10
BLAKE     7698     2850     MANAGER       0                 30Hope it is now clear.

Element order is not preserved in NESTED TABLES.

Similar Messages

Maybe you are looking for