Inheritance in a Relational Database

Hi
Now I've some problem in mapping my class hierarchy in relational database table.
How to express inheritance relationship in database?
Any advice appreciated
victor

HI Victor,
This could depend on what you are inheriting. If you have a single class inheriting from an abstract super class then I would just have a single table in the database for the sub class.
If your subclasses only override the super class methods and do not add any fields (data attributes) then you should just have a database table for your superclass.
If your sub classes have additional fields that do not exist in the super class then you should have one table for your super class, and a table for any sub classes which have additional data attributes. The super class table will have a column which holds a primary key, and each sub class table will have a column holding a foreign key which is the link to the super class table.
HTH,
Fintan

Similar Messages

Web Analysis Report prompted for relational database login

We have given access to the WA reports and everything works fine in general. One of the user trying to open same report(s) document(s) via Workspace and its getting prompted with relational database login? I have verified for the access and everything seems to be fine.
I do not know the reason for this. Can anyone help me? Thanks.

From the forums, i got the below MAXL commands to sync the user access :
alter system resync sss; --> this command will sync all the users, groups.
alter group <group name> sync security with all application; --> This can be used to individually sync the required group
alter user <user name> sync security with all application; --> This can be used to individually sync the required user
Will check it up with user on any change in her access.
Thanks,
Praveen.

Not able to create XML from an existing relational database

Hi,
I am trying to create and xml from an existing relational database. I am not able to get any XML data, I receive "XMLTYPE()" as the result.
Here's the query -
SQL> select o.order_id, XMLELEMENT("order", XMLATTRIBUTES(o.order_id as ID)) AS "result" from order_
info o where order_id=2793;
ORDER_ID
result()
+2793+
XMLTYPE()
I was expecting to get +<order id=2793 />+ instead of XMLTYPE().
I am using -
SQLPlus: Release 9.0.1.0.1*
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
I have also run some checks to confirm XML DB installation -
SQL> select 1 from all_users where username = 'XDB';
+1+
+1+
SQL> desc RESOURCE_VIEW;
Name                                      Null?    Type
RES                                                SYS.XMLTYPE
ANY_PATH                                           VARCHAR2(4000)
RESID                                              RAW(16)
I think, I have something wrong with installation or configuration.
Any idea about what have I done wrong here?

Works fine now. Got the result "<order ID="2793"></order>".
Thanks. :-)

Essbase as a source in OBIEE 11g and using lookup to Relation database

Hello All,
We are trying to implement Essbase as primary source for our obiee 11g repository and using relational database as secondary source of data.
I was using a lookup functionality in repository to lookup value from one of the Essbase's Dimension's attribute to relational database, however, there is error when testing this in OBIEE Dashboards.
And tried to look this error in support.oracle and googled it but was not able to find anything on it.
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46008] Internal error: File server\Query\Src\SQLookupUtility.cpp, line 145. (HY000)
Have you had any such issue and how can we pass this issue?
I am trying to find if there are any quick resolution before going to oracle support.
TIA.
Parish

Is Essbase 11.1.1.3 supported as a source for OBIEE 11g?From the certification matrix (http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/bi-11gr1certmatrix-166168.xls) we can see that only Essbase 9.3.3+ and 11.1.2+ are supported, not 11.1.1.3
Paul

Insert XML file into Relational database model - no XMLTYPE!

Dear all,
How can I store a known complex XML file into an existing relational database WITHOUT using xmltypes in the database ?
I read the article on DBMS_XMLSTORE. DBMS_XMLSTORE indeed partially bridges the gap between XML and RDBMS to a certain extent, namely for simply structured XML (canonical structure) and simple tables.
However, when the XML structure will become arbitrary and rapidly evolving, surely there must be a way to map XML to a relational model more flexibly.
We work in a java/Oracle10 environment that receives very large XML documents from an independent data management source. These files comply with an XML schema. That is all we know. Still, all these data must be inserted/updated daily in an existing relational model. Quite an assignment isn't it ?
The database does and will not contain XMLTYPES, only plain RDBMS tables.
Are you aware of a framework/product or tool to do what DBMS_XMLSTORE does but with any format of XML file ? If not, I am doomed.
Cheers.
Luc.
Edited by: user6693852 on Jan 13, 2009 7:02 AM

In case you decide to follow my advice, here's a simple example showing how to do this.. (Note the XMLTable syntax is the preferred approach in 10gr2 and later..
SQL> spool testase.log
SQL> --
SQL> connect / as sysdba
Connected.
SQL> --
SQL> set define on
SQL> set timing on
SQL> --
SQL> define USERNAME = XDBTEST
SQL> --
SQL> def PASSWORD = XDBTEST
SQL> --
SQL> def USER_TABLESPACE = USERS
SQL> --
SQL> def TEMP_TABLESPACE = TEMP
SQL> --
SQL> drop user &USERNAME cascade
2 /
old   1: drop user &USERNAME cascade
new   1: drop user XDBTEST cascade
User dropped.
Elapsed: 00:00:00.59
SQL> grant create any directory, drop any directory, connect, resource, alter session, create view to &USERNAME identified by &PASS
ORD
2 /
old   1: grant create any directory, drop any directory, connect, resource, alter session, create view to &USERNAME identified by &
ASSWORD
new   1: grant create any directory, drop any directory, connect, resource, alter session, create view to XDBTEST identified by XDB
EST
Grant succeeded.
Elapsed: 00:00:00.01
SQL> alter user &USERNAME default tablespace &USER_TABLESPACE temporary tablespace &TEMP_TABLESPACE
2 /
old   1: alter user &USERNAME default tablespace &USER_TABLESPACE temporary tablespace &TEMP_TABLESPACE
new   1: alter user XDBTEST default tablespace USERS temporary tablespace TEMP
User altered.
Elapsed: 00:00:00.00
SQL> connect &USERNAME/&PASSWORD
Connected.
SQL> --
SQL> var SCHEMAURL varchar2(256)
SQL> var XMLSCHEMA CLOB
SQL> --
SQL> set define off
SQL> --
SQL> begin
2    :SCHEMAURL := 'http://xmlns.example.com/askTom/TransactionList.xsd';
3    :XMLSCHEMA :=
4 '<?xml version="1.0" encoding="UTF-8"?>
5 
6 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xdb:storeVarrayAsTable="true">
7     <xs:element name="TransactionList" type="transactionListType" xdb:defaultTable="LOCAL_TABLE"/>
8     <xs:complexType name="transactionListType" xdb:maintainDOM="false" xdb:SQLType="TRANSACTION_LIST_T">
9             <xs:sequence>
10                     <xs:element name="Transaction" type="transactionType" maxOccurs="unbounded" xdb:SQLCollType="TRANSACTION_V"
>
11             </xs:sequence>
12     </xs:complexType>
13     <xs:complexType name="transactionType" xdb:maintainDOM="false" xdb:SQLType="TRANSACTION_T">
14             <xs:sequence>
15                     <xs:element name="TradeVersion" type="xs:integer"/>
16                     <xs:element name="TransactionId" type="xs:integer"/>
17                     <xs:element name="Leg" type="legType" maxOccurs="unbounded" xdb:SQLCollType="LEG_V"/>
18             </xs:sequence>
19             <xs:attribute name="id" type="xs:integer" use="required"/>
20     </xs:complexType>
21     <xs:complexType name="paymentType" xdb:maintainDOM="false" xdb:SQLType="PAYMENT_T">
22             <xs:sequence>
23                     <xs:element name="StartDate" type="xs:date"/>
24                     <xs:element name="Value" type="xs:integer"/>
25             </xs:sequence>
26             <xs:attribute name="id" type="xs:integer" use="required"/>
27     </xs:complexType>
28     <xs:complexType name="legType" xdb:maintainDOM="false" xdb:SQLType="LEG_T">
29             <xs:sequence>
30                     <xs:element name="LegNumber" type="xs:integer"/>
31                     <xs:element name="Basis" type="xs:integer"/>
32                     <xs:element name="FixedRate" type="xs:integer"/>
33                     <xs:element name="Payment" type="paymentType" maxOccurs="unbounded" xdb:SQLCollType="PAYMENT_V"/>
34             </xs:sequence>
35             <xs:attribute name="id" type="xs:integer" use="required"/>
36     </xs:complexType>
37 </xs:schema>';
38 end;
39 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.00
SQL> set define on
SQL> --
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(:XMLSCHEMA);
4 begin
5    dbms_xmlschema.registerSchema
6    (
7      schemaurl => :schemaURL,
8      schemadoc => xmlSchema,
9      local     => TRUE,
10      genTypes => TRUE,
11      genBean   => FALSE,
12      genTables => TRUE,
13      ENABLEHIERARCHY => DBMS_XMLSCHEMA.ENABLE_HIERARCHY_NONE
14    );
15 end;
16 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.26
SQL> desc LOCAL_TABLE
Name                                                                   Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "http://xmlns.example.com/askTom/TransactionList.xsd" Element "TransactionList") STORAGE Object-rela
ional TYPE "TRANSACTION_LIST_T"
SQL> --
SQL> create or replace VIEW TRAN_VIEW
2 as
3 select
4    extractvalue(x.column_value,'/Transaction/TradeVersion/text()') tradeversion,
5    extractvalue(x.column_value,'/Transaction//text()') transactionid
6 from
7    local_table,
8    table(xmlsequence(extract(OBJECT_VALUE,'/TransactionList/Transaction'))) x
9 /
View created.
Elapsed: 00:00:00.01
SQL> create or replace VIEW TRAN_LEG_VIEW
2 as
3 select
4    extractvalue(x.column_value,'/Transaction/TransactionId/text()') transactionid,
5    extractvalue(y.column_value,'/Leg/Basis/text()') leg_basis,
6    extractValue(y.column_value,'/Leg/FixedRate/text()') leg_fixedrate
7 from
8    local_table,
9    table(xmlsequence(extract(OBJECT_VALUE,'/TransactionList/Transaction'))) x,
10    table(xmlsequence(extract(x.column_value,'/Transaction/Leg'))) y
11 /
View created.
Elapsed: 00:00:00.01
SQL> create or replace VIEW TRAN_LEG_PAY_VIEW
2 as
3 select
4    extractvalue(x.column_value,'/Transaction/TransactionId/text()') transactionid,
5    extractvalue(y.column_value,'/Leg/LegNumber/text()') leg_legnumber,
6    extractvalue(z.column_value,'/Payment/StartDate/text()') pay_startdate,
7    extractValue(z.column_value,'/Payment/Value/text()') pay_value
8 from
9    local_table,
10    table(xmlsequence(extract(OBJECT_VALUE,'/TransactionList/Transaction'))) x,
11    table(xmlsequence(extract(x.column_value,'/Transaction/Leg'))) y,
12    table(xmlsequence(extract(y.column_value,'/Leg/Payment'))) z
13 /
View created.
Elapsed: 00:00:00.03
SQL> desc TRAN_VIEW
Name                                                                   Null?    Type
TRADEVERSION                                                                    NUMBER(38)
TRANSACTIONID                                                                   VARCHAR2(4000)
SQL> --
SQL> desc TRAN_LEG_VIEW
Name                                                                   Null?    Type
TRANSACTIONID                                                                   NUMBER(38)
LEG_BASIS                                                                       NUMBER(38)
LEG_FIXEDRATE                                                                   NUMBER(38)
SQL> --
SQL> desc TRAN_LEG_PAY_VIEW
Name                                                                   Null?    Type
TRANSACTIONID                                                                   NUMBER(38)
LEG_LEGNUMBER                                                                   NUMBER(38)
PAY_STARTDATE                                                                   DATE
PAY_VALUE                                                                       NUMBER(38)
SQL> --
SQL> create or replace VIEW TRAN_VIEW_XMLTABLE
2 as
3 select t.*
4    from LOCAL_TABLE,
5         XMLTable
6         (
7            '/TransactionList/Transaction'
8            passing OBJECT_VALUE
9            columns
10            TRADE_VERSION NUMBER(4) path 'TradeVersion/text()',
11            TRANSACTION_ID NUMBER(4) path 'TransactionId/text()'
12         ) t
13 /
View created.
Elapsed: 00:00:00.01
SQL> create or replace VIEW TRAN_LEG_VIEW_XMLTABLE
2 as
3 select t.TRANSACTION_ID, L.*
4    from LOCAL_TABLE,
5         XMLTable
6         (
7            '/TransactionList/Transaction'
8            passing OBJECT_VALUE
9            columns
10            TRANSACTION_ID NUMBER(4) path 'TransactionId/text()',
11            LEG            XMLType   path 'Leg'
12         ) t,
13         XMLTABLE
14         (
15           '/Leg'
16           passing LEG
17           columns
18           LEG_NUMBER     NUMBER(4) path 'LegNumber/text()',
19           LEG_BASIS      NUMBER(4) path 'Basis/text()',
20           LEG_FIXED_RATE NUMBER(4) path 'FixedRate/text()'
21         ) l
22 /
View created.
Elapsed: 00:00:00.01
SQL> create or replace VIEW TRAN_LEG_PAY_VIEW_XMLTABLE
2 as
3 select TRANSACTION_ID, L.LEG_NUMBER, P.*
4    from LOCAL_TABLE,
5         XMLTable
6         (
7            '/TransactionList/Transaction'
8            passing OBJECT_VALUE
9            columns
10            TRANSACTION_ID NUMBER(4) path 'TransactionId/text()',
11            LEG            XMLType   path 'Leg'
12         ) t,
13         XMLTABLE
14         (
15           '/Leg'
16           passing LEG
17           columns
18           LEG_NUMBER     NUMBER(4) path 'LegNumber/text()',
19           PAYMENT        XMLType   path 'Payment'
20         ) L,
21         XMLTABLE
22         (
23           '/Payment'
24           passing PAYMENT
25           columns
26           PAY_START_DATE     DATE      path 'StartDate/text()',
27           PAY_VALUE          NUMBER(4) path 'Value/text()'
28         ) p
29 /
View created.
Elapsed: 00:00:00.03
SQL> desc TRAN_VIEW_XMLTABLE
Name                                                                   Null?    Type
TRADE_VERSION                                                                   NUMBER(4)
TRANSACTION_ID                                                                  NUMBER(4)
SQL> --
SQL> desc TRAN_LEG_VIEW_XMLTABLE
Name                                                                   Null?    Type
TRANSACTION_ID                                                                  NUMBER(4)
LEG_NUMBER                                                                      NUMBER(4)
LEG_BASIS                                                                       NUMBER(4)
LEG_FIXED_RATE                                                                  NUMBER(4)
SQL> --
SQL> desc TRAN_LEG_PAY_VIEW_XMLTABLE
Name                                                                   Null?    Type
TRANSACTION_ID                                                                  NUMBER(4)
LEG_NUMBER                                                                      NUMBER(4)
PAY_START_DATE                                                                  DATE
PAY_VALUE                                                                       NUMBER(4)
SQL> --
SQL> set long 10000 pages 100 lines 128
SQL> set timing on
SQL> set autotrace on explain
SQL> set heading on feedback on
SQL> --
SQL> VAR DOC1 CLOB
SQL> VAR DOC2 CLOB
SQL> --
SQL> begin
2    :DOC1 :=
3 '<TransactionList>
4    <Transaction id="1">
5      <TradeVersion>1</TradeVersion>
6      <TransactionId>1</TransactionId>
7      <Leg id="1">
8        <LegNumber>1</LegNumber>
9        <Basis>1</Basis>
10        <FixedRate>1</FixedRate>
11        <Payment id="1">
12          <StartDate>2000-01-01</StartDate>
13          <Value>1</Value>
14        </Payment>
15        <Payment id="2">
16          <StartDate>2000-01-02</StartDate>
17          <Value>2</Value>
18        </Payment>
19      </Leg>
20      <Leg id="2">
21        <LegNumber>2</LegNumber>
22        <Basis>2</Basis>
23        <FixedRate>2</FixedRate>
24        <Payment id="1">
25          <StartDate>2000-02-01</StartDate>
26          <Value>10</Value>
27        </Payment>
28        <Payment id="2">
29          <StartDate>2000-02-02</StartDate>
30          <Value>20</Value>
31        </Payment>
32      </Leg>
33    </Transaction>
34    <Transaction id="2">
35      <TradeVersion>2</TradeVersion>
36      <TransactionId>2</TransactionId>
37      <Leg id="1">
38        <LegNumber>21</LegNumber>
39        <Basis>21</Basis>
40        <FixedRate>21</FixedRate>
41        <Payment id="1">
42          <StartDate>2002-01-01</StartDate>
43          <Value>21</Value>
44        </Payment>
45        <Payment id="2">
46          <StartDate>2002-01-02</StartDate>
47          <Value>22</Value>
48        </Payment>
49      </Leg>
50      <Leg id="22">
51        <LegNumber>22</LegNumber>
52        <Basis>22</Basis>
53        <FixedRate>22</FixedRate>
54        <Payment id="21">
55          <StartDate>2002-02-01</StartDate>
56          <Value>210</Value>
57        </Payment>
58        <Payment id="22">
59          <StartDate>2002-02-02</StartDate>
60          <Value>220</Value>
61        </Payment>
62      </Leg>
63    </Transaction>
64 </TransactionList>';
65    :DOC2 :=
66 '<TransactionList>
67    <Transaction id="31">
68      <TradeVersion>31</TradeVersion>
69      <TransactionId>31</TransactionId>
70      <Leg id="31">
71        <LegNumber>31</LegNumber>
72        <Basis>31</Basis>
73        <FixedRate>31</FixedRate>
74        <Payment id="31">
75          <StartDate>3000-01-01</StartDate>
76          <Value>31</Value>
77        </Payment>
78      </Leg>
79    </Transaction>
80 </TransactionList>';
81 end;
82 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.01
SQL> insert into LOCAL_TABLE values ( xmltype(:DOC1))
2 /
1 row created.
Elapsed: 00:00:00.01
Execution Plan
Plan hash value: 1
| Id | Operation                | Name        | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | INSERT STATEMENT         |             |     1 |   100 |     1   (0)| 00:00:01 |
|   1 | LOAD TABLE CONVENTIONAL | LOCAL_TABLE |       |       |            |          |
SQL> insert into LOCAL_TABLE values ( xmltype(:DOC2))
2 /
1 row created.
Elapsed: 00:00:00.01
Execution Plan
Plan hash value: 1
| Id | Operation                | Name        | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | INSERT STATEMENT         |             |     1 |   100 |     1   (0)| 00:00:01 |
|   1 | LOAD TABLE CONVENTIONAL | LOCAL_TABLE |       |       |            |          |
SQL> select * from TRAN_VIEW_XMLTABLE
2 /
TRADE_VERSION TRANSACTION_ID
            1              1
            2              2
           31             31
3 rows selected.
Elapsed: 00:00:00.03
Execution Plan
Plan hash value: 650975545
| Id | Operation          | Name                           | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |                                |     3 |   168 |     3   (0)| 00:00:01 |
|   1 | NESTED LOOPS      |                                |     3 |   168 |     3   (0)| 00:00:01 |
|* 2 |   TABLE ACCESS FULL| SYS_NTGgl+TKyhQnWoFRSrCxeX9g== |     3 |   138 |     3   (0)| 00:00:01 |
|* 3 |   INDEX UNIQUE SCAN| SYS_C0010174                   |     1 |    10 |     0   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   2 - filter("SYS_NC_TYPEID$" IS NOT NULL)
   3 - access("NESTED_TABLE_ID"="LOCAL_TABLE"."SYS_NC0000800009$")
Note
   - dynamic sampling used for this statement
SQL> select * from TRAN_LEG_VIEW_XMLTABLE
2 /
TRANSACTION_ID LEG_NUMBER LEG_BASIS LEG_FIXED_RATE
             1          1          1              1
             1          2          2              2
             2         21         21             21
             2         22         22             22
            31         31         31             31
5 rows selected.
Elapsed: 00:00:00.04
Execution Plan
Plan hash value: 1273661583
| Id | Operation           | Name                           | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT    |                                |     5 |   560 |     7 (15)| 00:00:01 |
|* 1 | HASH JOIN          |                                |     5 |   560 |     7 (15)| 00:00:01 |
|   2 |   NESTED LOOPS      |                                |     3 |   159 |     3   (0)| 00:00:01 |
|* 3 |    TABLE ACCESS FULL| SYS_NTGgl+TKyhQnWoFRSrCxeX9g== |     3 |   129 |     3   (0)| 00:00:01 |
|* 4 |    INDEX UNIQUE SCAN| SYS_C0010174                   |     1 |    10 |     0   (0)| 00:00:01 |
|* 5 |   TABLE ACCESS FULL | SYS_NTUmyermF/S721C/2UXo40Uw== |     5 |   295 |     3   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - access("SYS_ALIAS_1"."NESTED_TABLE_ID"="SYS_ALIAS_0"."SYS_NC0000800009$")
   3 - filter("SYS_NC_TYPEID$" IS NOT NULL)
   4 - access("NESTED_TABLE_ID"="LOCAL_TABLE"."SYS_NC0000800009$")
   5 - filter("SYS_NC_TYPEID$" IS NOT NULL)
Note
   - dynamic sampling used for this statement
SQL> select * from TRAN_LEG_PAY_VIEW_XMLTABLE
2 /
TRANSACTION_ID LEG_NUMBER PAY_START PAY_VALUE
             1          1 01-JAN-00          1
             1          1 02-JAN-00          2
             1          2 01-FEB-00         10
             1          2 02-FEB-00         20
             2         21 01-JAN-02         21
             2         21 02-JAN-02         22
             2         22 01-FEB-02        210
             2         22 02-FEB-02        220
            31         31 01-JAN-00         31
9 rows selected.
Elapsed: 00:00:00.07
Execution Plan
Plan hash value: 4004907785
| Id | Operation            | Name                           | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT     |                                |     9 | 1242 |    10 (10)| 00:00:01 |
|* 1 | HASH JOIN           |                                |     9 | 1242 |    10 (10)| 00:00:01 |
|* 2 |   HASH JOIN          |                                |     5 |   480 |     7 (15)| 00:00:01 |
|   3 |    NESTED LOOPS      |                                |     3 |   159 |     3   (0)| 00:00:01 |
|* 4 |     TABLE ACCESS FULL| SYS_NTGgl+TKyhQnWoFRSrCxeX9g== |     3 |   129 |     3   (0)| 00:00:01 |
|* 5 |     INDEX UNIQUE SCAN| SYS_C0010174                   |     1 |    10 |     0   (0)| 00:00:01 |
|* 6 |    TABLE ACCESS FULL | SYS_NTUmyermF/S721C/2UXo40Uw== |     5 |   215 |     3   (0)| 00:00:01 |
|* 7 |   TABLE ACCESS FULL | SYS_NTelW4ZRtKS+WKqCaXhsHnNQ== |     9 |   378 |     3   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - access("NESTED_TABLE_ID"="SYS_ALIAS_1"."SYS_NC0000900010$")
   2 - access("SYS_ALIAS_1"."NESTED_TABLE_ID"="SYS_ALIAS_0"."SYS_NC0000800009$")
   4 - filter("SYS_NC_TYPEID$" IS NOT NULL)
   5 - access("NESTED_TABLE_ID"="LOCAL_TABLE"."SYS_NC0000800009$")
   6 - filter("SYS_NC_TYPEID$" IS NOT NULL)
   7 - filter("SYS_NC_TYPEID$" IS NOT NULL)
Note
   - dynamic sampling used for this statement
SQL>Out of interest why are you so against using XMLType...
Edited by: mdrake on Jan 13, 2009 8:25 AM

Insert XML file into Relational database model without using XMLTYPE tables

Dear all,
How can I store a known complex XML file into an existing relational database WITHOUT using xmltypes in the database ?
I read the article on DBMS_XMLSTORE. DBMS_XMLSTORE indeed partially bridges the gap between XML and RDBMS to a certain extent, namely for simply structured XML (canonical structure) and simple tables.
However, when the XML structure will become arbitrary and rapidly evolving, surely there must be a way to map XML to a relational model more flexibly.
We work in a java/Oracle10 environment that receives very large XML documents from an independent data management source. These files comply with an XML schema. That is all we know. Still, all these data must be inserted/updated daily in an existing relational model. Quite an assignment isn't it ?
The database does and will not contain XMLTYPES, only plain RDBMS tables.
Are you aware of a framework/product or tool to do what DBMS_XMLSTORE does but with any format of XML file ? If not, I am doomed.
Constraints : Input via XML files defined by third party
Storage : relational database model with hundreds of tables and thousands of existing queries that can not be touched. The model must not be altered.
Target : get this XML into the database on a daily basis via an automated process.
Cheers.
Luc.

Luc,
your Doomed !
If you would try something like DBMS_XMLSTORE, you probably would be into serious performance problems in your case, very fast, and it would be very difficult to manage.
If you would use a little bit of XMLType stuff, you would be able to shred the data into the relational model very fast and controlable. Take it from me, I am one of those old geezers like Mr. Tom Kyte way beyond 40 years (still joking). No seriously. I started out as a classical PL/SQL, Forms Guy that switched after two years to become a "DBA 1.0" and Mr Codd and Mr Date were for years my biggest hero's. I have the utmost respect for Mr. Tom Kyte for all his efforts for bringing the concepts manual into the development world. Just to name some off the names that influenced me. But you will have to work with UNSTRUCTURED data (as Mr Date would call it). 80% of the data out there exists off it. Stuff like XMLTABLE and XML VIEWs bridge the gap between that unstructured world and the relational world. It is very doable to drag and drop an XML file into the XMLDB database into a XMLtype table and or for instance via FTP. From that point on it is in the database. From there you could move into relational tables via XMLTABLE methods or XML Views.
You could see the described method as a filtering option so XML can be transformed into relational data. If you don't want any XML in your current database, then create an small Oracle database with XML DB installed (if doable 11.1.0.7 regarding the best performance --> all the new fast optimizer stuff etc). Use that database as a staging area that does all the XML shredding for you into relational components and ship the end result via database links and or materialized views or other probably known methodes into your relational database that isn't allowed to have XMLType.
This way you would keep your realtional Oracle database clean and have the Oracle XML DB staging database do all the filtering and shredding into relational components.
Throwing the XML DB option out off the window beforehand would be like replacing your Mercedes with a bicycle. With both you will be able to travel the distance from Paris to Rome, but it will take you a hell of lot longer.
:-)

How to store, in an effective way, analyzer data into a relational database?

We want to store the "sweep traces" of a network analyzer in a relational database in a way that it saves as much as possible space without loosing resolution.
The solutions were we thinking on are to separate the x-axes information from the y-axes information and store it in different tables of the database.
Because the repeating character of the measurements the data in the x-axes will be nearly all ways the same. So we want to store only new data in the x-axes table as a different x-axes is detected.
In a third table we want to save the relation between the x and y data and other data that belongs to the measurement.
Question is are there other or better possibilities to solve this proble
m?

Hi Ben,
Thanks for you help.
The use of a third table that links the X-axe and y-axe table together depends on if I store the datapoints in the y-axe table sequential, so I need an identification of the points belonging together and I can have a varying number of data-points, (i.e. 401 of 801 ...) or I save it in one record.
The problem here is I have to save a varying nummer of points in tables with a lot of "datapoint columns".
Another solution is save the datapoints as a semicolon ( separated text string in one field.
Problem now is the limitation in the max. text field length.
In my Oracle Rdb database I can use "Varchar" fields.
(is here no limitation??)
In other databases a "Note field" will maybe give a solution.
The question sti
ll is: What is the best solution and uses the smallest amount of space?
In the next week I will do some tests with the solutions mentioned.
Please let me know what DSC is??
Greetings Huub

RELATIONAL DATABASE TABLES IN SAP BW

hi
friends please give me the information regarding the RELATIONAL DATABASE TABLES IN SAP BW?

Hi,
See the tables.
InfoObjects Table:
RSDIOBJ Directory of all InfoObjects
RSDIOBJT Texts of InfoObjects
InfoCube Tables:
RSDCUBE Directory of InfoCubes
RSDCUBET Texts on InfoCubes
DSO Tables:
RSDODSO Directory of all ODS Objects
RSDODSOT Texts of all ODS Objects
PSA Table:
RSTSODS Directory of all PSA Tables
For reports:
RSRREPDIR
Thanks & Regards,
Sathish

CITADEL DATABASE NOT CONFIGURED AS A RELATIONAL DATABASE

HI:
I have the same problem described by another member before, and I haven't found any resolution of this problem:
The problem was:
>I enabled database logging, and configured the shared variables that I wanted to log. Then I deployed the variables. When I try to read alarms and events (Alarm & Event Query.vi), I get this message:
>Error -1967386611 occurred at HIST_RunAlarmQueryCORE.vi,
Citadel: (Hex 0x8ABC100D) The given Citadel database is not currently
configured to log alarms to a relational database.
Please help me with this topic
Thanks in advance

I'm configuring the variables to be logged in the same way that appears on the file you send, but it doesn't work... I don't know what else to do.
I'm sending you the configuration image file, the error message image and a simple vi that creates the database; after, values are logged; I generate several values for the variable, values that are above the HI limit of the acceptance value (previously configured) so alarms are generated. When I push the button STOP, the system stops logging values to the database and performs a query to the alarms database, and the corresponding error is generated... (file attached)
The result: With the aid of MAXThe data is logged correctly on the DATA database (I can view the trace), but the alarm generated is not logged on the alarms database created programatically...
The same vi is used but creating another database manually with the aid of MAX and configuring the library to log the alarms to that database.... same result
I try this sabe conditions on three different PCs with the same result, and I try to reinstall LabVIEW (development and DSC) completelly (uff!) and still doesn't work... ¿what else can I do?
I'd appreciate very much your help.
Ignacio
Attachments:
error.jpg ‏56 KB
test_db.vi ‏38 KB
config.jpg ‏150 KB

SQL ENTERPRISE: The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database

The error below makes absolutely no sense! I'm using Enterprise Core...yet I'm being told I can't use remote data sources:
w3wp!library!8!03/05/2015-19:08:48:: i INFO: Catalog SQL Server Edition = EnterpriseCore
w3wp!library!8!03/05/2015-19:08:48:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The edition of Reporting
Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services.;
Really? This totally contradicts the documentation found here:
https://msdn.microsoft.com/en-us/library/ms157285(v=sql.110).aspx
That article says remote connections are completely supported.
ARGH! Why does this have to be so difficult to setup?!?

Hi jeffoliver1000,
According to your description, you are using Enterprise Core edition and you are prompted that you can’t use remote data sources.
In your scenario, we neither ignore your point nor be doubt with what you say. But actually we have met the case before that even though the SQL Server engine is Enterprise but the reporting services is still standard. So I would recommend you to find the
actual edition of reporting services you are using. You can find Reporting Services starting SKU in the Reporting Service logs ( default location: C:\Program Files\Microsoft SQL Server\<instance name>\Reporting Services\LogFiles). For more information,
please refer to the similar thread below:
https://social.technet.microsoft.com/Forums/en-US/f98c2f3e-1a30-4993-ab41-acbc5014f92e/data-driven-subscription-button-not-displayed?forum=sqlreportingservices
By the way, have you installed the other SQL Server edition before?
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Can I configure Enterprise search to search a Relational database

We have several legacy web applications. We are currently using coveo to search the relational databases. We create mapping xml file for the coveo indexing services. The coveo access the database using jdbc. It provides the ability to create uri for search result. The uri is invoked when the user clicks on search result.
Can I setup something similar with SAP Enterprise search.

Hi:
SAP NetWeaver Enterprise Search contains an SAP NetWeaver BI instance within the architecture on the appliance. You can utilize the BI features to extract data from your relational DataBase, then index that data into the TREX part of ES. BI features both "DB connect" and "UD Connect", which give you techiques to connect the BI system to an external DataBase and extract data. You will need to model a DataSource, but the features of SAP NetWeaver 2004s BI make this relatively easy. Once you have a datasource, you can create an Open Hub destination for indexing (with a transformation and DTP to deliver the data), and create a process chain to extract and index the data.
ES offers numerous DataSources "out of the box" for extraction from SAP ERP systems, you could follow the business content structure for those, but instead use DB connect or UDconnect to get the data from a non-SAP system.
For more info on this, see the BI area of SDN and help.sap.com > NetWeaver > Key Capability > Information Integration > BI.
Thanks for any points you choose to assign (they are the way of saying thanks on SDN).
Best Regards -
Ron Silberstein
SAP

Mapping Objects to Relational Databases

Hi,
I do not know if this is the more suitable forum to ask this question, but I am going to try it:
I am developing an application with two parts.
1. A server developed in J2SE which is connected to a MySQL database.
2. A client developed in Swing which shows data received from the server by RMI.
Up to now, I map the relational database data in objects manually in the server side. But I would like to use a framework to do this (JDO, EJB 3.0, hibernate...).
I have read a lot about them, but I have serious doubts. Can I use them with J2SE? I think that it is necessary to use JBoss (or another application server) if I use EJB, it is true? Which is the easiest?
Which technology do you advice me?
I am very confused, thanks in advance.

I am developing an application with two parts.
1. A server developed in J2SE which is connected to
a MySQL database.Interesting since the JDBC API is not part of J2SE. How do you connect to the database without using JDBC? If you are using JDBC, why are you so confused?
2. A client developed in Swing which shows data
received from the server by RMI.Again, the RMI API is not part of the J2SE. If you are truthfully writing RMI code, which is complex, and you are writing Swing code, and you may be writing JDBC code, why are you very confused?
I have read a lot about them, but I have serious
doubts. Can I use them with J2SE? Did read a lot about them? Why do you have serious doubts? Did you understand what you read?
I suggest you read some more.

Do we still need relational databases?

Dears,
will this new in-memory technology reduce the need of a relational database?
There are also rumors about a column-based database... are we talking about the same product?
Thanks,
Federico Biavati

Hi Vitali,
2 things:
1st
It is much more as SQL Ansi and the in-memory stuff.
See the different DB vendors
How they
* handle lock escalation on their DB objects a
* concurrency
* high availability
* reliable DB recovery and backups
This is a knowledge they had to buy from Sybase - SAP will not invent a new DB relational system
Sybase has a very small customer base wich may grow with SAP installations in the future.
But have in mind: Other DB vendors are technologically spoken more advanced (not only Oracle)
2nd:
Oracle Exadata is not vapor ware as HANA , you can buy since 2008 (first with HP servers now also on Sun systems)
and it's not only adressing in-memory but also intelligent prefetching of OS data blocks via massive parallel systems BEFORE they go into the DB buffer .
Think of IT DB staff: you need expirienced personell for it, not sure if SAP can move Oracle DB staff to Sybase staff
at their customer base (at least not in the U.S.
I think customers will force SAP also to certify the Exadata machine also.
Best breed strategy may go for Exdata on Oracle and SAP ERP/BW
bye
yk

Embedded LDAP Server or relational database

Hi,
I'm pretty new to this subject, but I do have a question. Here is the situation.
I need to set up a login portal (in weblogic 8.1) for a webapplication. Customers
(in the future) can login into a secure part of the website, where they can modify
their personal settings and information. We are talking about < 100.000 users.
Now I was thinking of using the embedded LDAP server to set up the authorisation
and identification, but because 2 variables are needed to see if it is a customer
of the company, I am also looking into the possibility of using a relation database
(oracle) to set up the username - password authentication table.
Can somebody tell me the (dis)advantages of using LDAP instead of the relational
database (oracle)? Or give me advise which authorisation method is the best one?
Your help is needed!
Thanks in advance,
Hans
the customer more information is needed to

Ensure that the managed server is running with "Managed Server Independence Enabled" flag checked.
It can be checked on console via Environment --> Servers --> <ServerName> --> Configuration --> Tuning
For more information, please check
http://docs.oracle.com/cd/E14571_01/web.1111/e13708/failures.htm#START169
The above flag is required for the managed server to use the local LDAP repository.
Arun

JDBC for non-relational Databases.

Hi All,
correct me if I am wrong in my understanding,
1. JDBC are a set of specifications (as interfaces etc..) which each
vendor is expected to provide implementation.
2. JDBC is for relationsla databases only (like oracle,MySQL etc..) it
does not take into account the access to non-relational databases.
3. If 2 is true, is there an equivalent of JDBC for non-relational
databases?
TIA.

1. JDBC are a set of specifications (as interfaces etc..) which each
vendor is expected to provide implementation.
Broadly speaking, yes. It doesn't have to be the vendor that provides the implementation, and an ODBC driver (to be used via the JdbcOdbc bridge) is adequate if a native JDBC driver is not available.
2. JDBC is for relationsla databases only (like oracle,MySQL etc..) it
does not take into account the access to non-relational databases.
It expects tabular results. Aside from that I don't think it mandates anything about the design of the underlying system. Certainly it's entirely agnostic about syntactic issues.
For example, it can talk to Excel spreadsheets, via the JdbcOdbc bridge, and Excel is by no stretch of the imagination a relational database. IMS is not a relational database, but that has a JDBC driver.
3. If 2 is true, is there an equivalent of JDBC for non-relational
databases?
2 is not true, and I'm not aware of any "non relational" database connection standard, probably for this very reason. There may well be vendor specific tools for talking to some systems.

Inheritance in a Relational Database

Similar Messages

Maybe you are looking for