Xsql-query Attributes Bug
Some of the xsql-query tag attributes in an XSQL page are only available in the XSQL page, not in the Query tag from the component palette.
1. Create a XSQL page.
2. Add a Query (xsql-query) tag from the Component Palette. The Query lists some xsql-query tag attributes.
3. In the XSQL page, the xsql-query tag lists some additional attributes such as page-param, date-format and error-statement that are not listed in the Query frame when the Query tag is selected from the component pallette.
Correction.
3. In the XSQL page, the xsql-query tag lists some additional attributes such as bind-params, date-format and error-statement that are not listed in the Query frame when the Query tag is selected from the component pallette.
Similar Messages
-
Some of the xsql-query tag attributes in an XSQL page are only available in the XSQL page, not in the Query tag from the component palette.
1. Create a XSQL page.
2. Add a Query (xsql-query) tag from the Component Palette. The Query lists some xsql-query tag attributes.
3. In the XSQL page, the xsql-query tag lists some additional attributes such as page-param, date-format and error-statement that are not listed in the Query frame when the Query tag is selected from the component pallette.Correction.
3. In the XSQL page, the xsql-query tag lists some additional attributes such as bind-params, date-format and error-statement that are not listed in the Query frame when the Query tag is selected from the component pallette. -
XSQL bug when using CURSOR in xsql:query SELECT statement?
Hi there,
When I tested with different XSQL pages, I found out that if I
did not involve any XSQL pages that contain "CURSOR", I received
data correctly and when I shut down Tomcat, Oracle DB server did
NOT create any dump file (???). However, as long as I involve a
XSQL page which contains "CURSOR", even I received data
correctly, but when I shut down my Tomcat, Oracle DB server
created a dump file (???).
for example, if I involve xsql:query like:
<xsql:query>
SELECT emp_name,
emp_id
CURSOR( SELECT emp_address
from address a
where a.emp_id = b.emp_id)
FROM employee b
</xsql:query>
Once, I involve this xsql page, when I shut down Tomcat, Oracle
dB will create a dump file on the server.
Even when I run this xsql page from
oracle.xml.xsqlXSQLCommandLine, Oracle dB server still create a
dump file on the server.
Any idea for help ?
Thanks,Hi,
Is this what you are trying:
try {
Statement *stmt = conn->createStatement("SELECT ename AS aaaaaaaaaaaaaaa FROM emp");
ResultSet *rs = stmt->executeQuery ();
vector<MetaData> md = rs->getColumnListMetaData ();
int numCols = md.size ();
cout<< "Number of columns :" << numCols << endl;
string *colName = new string [numCols];
int type = (int ) malloc (numCols);
for (int i = 0; i < numCols; i++ ) {
int ptype = md [ i ].getInt (MetaData::ATTR_PTYPE);
if ( ptype == MetaData::PTYPE_COL ) {
colName[ i ] = md[ i ].getString (MetaData::ATTR_NAME);
cout<<"Column Name :" << colName[ i ] << endl;
delete[] colName;
stmt->closeResultSet (rs);
conn->terminateStatement (stmt);
catch (SQLException &ex) {
cout<<ex.getMessage()<<endl;
}The above snippet works correctly for me.
Rgds.
Amogh -
Object types return hex characters with xsql:query
How do I use xsql servlet to return an object which contains street address etc. as a character string and not a hexadecimal string. If I use the following ddl and implement the following xsql, I get the following results.
CREATE TYPE address_objtyp AS object
(street VARCHAR(30),city VARCHAR(30),state VARCHAR(2));
CREATE SEQUENCE employees_seq START WITH 105 INCREMENT BY 1;
CREATE TABLE employees(
id NUMBER(4) CONSTRAINT emp_pkId PRIMARY KEY,
first_name VARCHAR(30),
last_name VARCHAR(30),
address address_objtyp);
INSERT INTO employees VALUES (
103, 'Fred', 'Couples',
address_objtyp('9201 Park St', 'Alexandria', 'VA'));
<?xml version="1.0"?>
<xsql:query null-indicator="yes" connection="demo"
allow-client-style="yes" xmlns:xsql="urn:oracle-xsql">
select * from employees
</xsql:query>
<?xml version="1.0" ?>
- <ROWSET xsql-timing="20">
- <ROW num="1">
<ID>103</ID>
<FIRST_NAME>Fred</FIRST_NAME>
<LAST_NAME>Couples</LAST_NAME>
- <ADDRESS>
<STREET>0x39323031205061726B205374</STREET>
<CITY>0x416C6578616E64726961</CITY>
<STATE>0x5641</STATE>
</ADDRESS>
</ROW>
</ROWSET>
I'm using the most recent jdbc thin driver (ojdbc14.jar) that is for jdk 1.4. I'm using a 9.0.1 db, and I'm using xdk for java 9.2.0.3. So I thought that the thin driver is not capable, so I tried the oci driver, and find another set of problems.
I get the following error:
Oracle XDK Java 9.2.0.3.0 Production
XSQL-017: Unexpected Error Occurred
java.lang.UnsatisfiedLinkError: no ocijdbc8 in java.library.path
Now why does XDK insist to look for ocijdbc8 if I only have ocijdbc9.dll installed on my client? The config file only allows oci8 in the dburl specification, which is probably why XDK insists to look for ocijdbc8, but I CANNOT specify oci9, which would make sense to me, although it's most likely not a valid specification.
<connection name="9ic">
<username>scott</username>
<password>tiger</password>
<dburl>jdbc:oracle:oci8:@</dburl>
<driver>oracle.jdbc.OracleDriver</driver>
<autocommit>true</autocommit>
</connection>
And lastly documentation that comes with ojdbc14.jar indicates to now use a different specification for the jdbc thin driver. Instead of the usual
<dburl>jdbc:oracle:thin:@host:port:sid</dburl>
it recommends
<dburl>jdbc:oracle:thin:@//host:port/service</dburl>
however this does not work with XDK 9.2.0.3. Any ideas why not?
By the way if I use SQL*Plus and select * from employees, I get the desired result in SQL*Plus, which suggests to me that I DO need the oci driver for XSQL Servlet. So how do I get XSQL Servlet 9.2.0.3 to use the oci 9 driver. I know how to set wrapper.path in the servlet config file to find ocijdbc9.dll, but XSQL Servlet still wants to find ocijdbc8.
I sense that there is a bug hidden somewhere in the XDK kit.
Steve.How do I use xsql servlet to return an object which contains street address etc. as a character string and not a hexadecimal string. If I use the following ddl and implement the following xsql, I get the following results.
CREATE TYPE address_objtyp AS object
(street VARCHAR(30),city VARCHAR(30),state VARCHAR(2));
CREATE SEQUENCE employees_seq START WITH 105 INCREMENT BY 1;
CREATE TABLE employees(
id NUMBER(4) CONSTRAINT emp_pkId PRIMARY KEY,
first_name VARCHAR(30),
last_name VARCHAR(30),
address address_objtyp);
INSERT INTO employees VALUES (
103, 'Fred', 'Couples',
address_objtyp('9201 Park St', 'Alexandria', 'VA'));
<?xml version="1.0"?>
<xsql:query null-indicator="yes" connection="demo"
allow-client-style="yes" xmlns:xsql="urn:oracle-xsql">
select * from employees
</xsql:query>
<?xml version="1.0" ?>
- <ROWSET xsql-timing="20">
- <ROW num="1">
<ID>103</ID>
<FIRST_NAME>Fred</FIRST_NAME>
<LAST_NAME>Couples</LAST_NAME>
- <ADDRESS>
<STREET>0x39323031205061726B205374</STREET>
<CITY>0x416C6578616E64726961</CITY>
<STATE>0x5641</STATE>
</ADDRESS>
</ROW>
</ROWSET>
I'm using the most recent jdbc thin driver (ojdbc14.jar) that is for jdk 1.4. I'm using a 9.0.1 db, and I'm using xdk for java 9.2.0.3. So I thought that the thin driver is not capable, so I tried the oci driver, and find another set of problems.
I get the following error:
Oracle XDK Java 9.2.0.3.0 Production
XSQL-017: Unexpected Error Occurred
java.lang.UnsatisfiedLinkError: no ocijdbc8 in java.library.path
Now why does XDK insist to look for ocijdbc8 if I only have ocijdbc9.dll installed on my client? The config file only allows oci8 in the dburl specification, which is probably why XDK insists to look for ocijdbc8, but I CANNOT specify oci9, which would make sense to me, although it's most likely not a valid specification.
<connection name="9ic">
<username>scott</username>
<password>tiger</password>
<dburl>jdbc:oracle:oci8:@</dburl>
<driver>oracle.jdbc.OracleDriver</driver>
<autocommit>true</autocommit>
</connection>
And lastly documentation that comes with ojdbc14.jar indicates to now use a different specification for the jdbc thin driver. Instead of the usual
<dburl>jdbc:oracle:thin:@host:port:sid</dburl>
it recommends
<dburl>jdbc:oracle:thin:@//host:port/service</dburl>
however this does not work with XDK 9.2.0.3. Any ideas why not?
By the way if I use SQL*Plus and select * from employees, I get the desired result in SQL*Plus, which suggests to me that I DO need the oci driver for XSQL Servlet. So how do I get XSQL Servlet 9.2.0.3 to use the oci 9 driver. I know how to set wrapper.path in the servlet config file to find ocijdbc9.dll, but XSQL Servlet still wants to find ocijdbc8.
I sense that there is a bug hidden somewhere in the XDK kit.
Steve. -
XSQL new feature suggestion: transform="url" for xsql:query
To the Oracle XML developers:
I'd like to suggest adding the transform="url" attribute/feature to the <xsql:query> action.
This would allow one to transform and/or apply XSLT conditional logic to the posted XML before it reaches the <xsql:query> action. A couple of key areas where I think this would be very useful are:
1. handling multiple HTML parameters of the same name.
Currently, the only way to handle this in an <xsql:query> action is to call a Java program via <xsql:action> that can parse the rowified parameters of the same name, then transform it in a format suitable for the <xsql:query>.
2. verifying user session login status for password protected XSQL pages.
If one could use XSLT to check user authentication BEFORE the <xsql:query> action you could display a login page if the user is not authenticated.
Since the transform="url" feature is already available for other tags (<xsql:update>, <xsql:delete>, etc) I would think adding this to the <xsql:query> action would not require extensive coding from the Oracle XML development team, and yet this simple but powerful feature could help us users to develop pure XML solutions that don't require calls to external Java actions.
MichaelThere would also be able to simply add the "perspective"as in Photoshop, probablyeasier to develop and integrate the interface.
-
xsql:query - Is there a character limit on the SQL contained in the tag?
Is there a limit to the length of the SQL contained in the
<xsql:query> tag ?
I've been very successful with short queries using xsql:query
tags, however, for longer queries they seem to fail the XML
Syntax check using JDeveloper 3.2.3.
The resulting error from the XSQLServlet is XSQL-005 page is not
well formed with the following:
XML-0201: (Fatal Error) Expected name instead of .
XML-0122: (Fatal Error) '=' missing in attribute.
XML-0125: (Fatal Error) Attribute value should start with quote
(Posted example 10/16/01)Hello Bill,
>> … to our apex environment (9.2)
The following might give you some more information on your possible situation -
Re: Is there a maximum number of characters allowed in PL/SQL Anonymous Blo
ORA-06550 recieved when trying to modify existing page after 3.1 Apex upg
Regards,
Arie. -
Generating DTD with xsql:query
Is there any attribute to xsql:query to generate DTD for the result.
Hmm,
Even more confusing - the same .xsql document works fine with WebToGo - so I guess this is a Tomcat problem, somehow... Just can't understand why xsql:include-xsql works and xsql:query doesn't.
Steve -
Crystal didn't show the BEx query Attributes description changes/Values
We experiencing the BEx query attributes/crystal report issue.
I create a crystal report using BW- BEx query. Bex query displays the attributes values. But in crystal report side it didn;t show up the values as well as description changes.
But If I change the display properties of attributes (different from one attribute to another) the crystal report reflect the values. But crystal report didn't show the Attribute description changes , the one i did it in BEx query side.
Example:
Bex has a Masterdata as well as attribute Field1, Field2 etc.. I changed the description like Field_Test1 and Field_Test2. Also I changed the display property for Field_Test1 is Key and text and long , Field_Test2 is Text & LOng text.
I got the attribute values is crystal report Xi R2. But crystal didn't reflect the description changes?
Suggestions Please?Post your question to the Business Object Integration Kits forum
-
Hi,
I'm having a problem with the following simple XSQL document:
<?xml version="1.0"?>
<xsql:query connection="xsqltest" xmlns:xsql="urn:oracle-xsql">
SELECT concat(concat(forename, ' '), surname) AS Name
, d.name AS Department
FROM emp, dept d
WHERE emp.dept_no = d.id
ORDER BY surname
</xsql:query>When I transform this using the command line xsql, it produces the following (as expected):
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<Name>Cindy Delight</Name>
<Department>Accounting</Department>
</ROW>
<ROW num="2">
<Name>Adrian Rue</Name>
<Department>Product Development</Department>
</ROW>
<ROW num="3">
<Name>Dwight Dweeb</Name>
<Department>Accounting</Department>
</ROW>
</ROWSET>However, when I access the same page through my browser, the output is:
<?xml version = '1.0'?>
<xsql:query>
SELECT concat(concat(forename, ' '), surname) AS Name
, d.name AS Department
FROM emp, dept d
WHERE emp.dept_no = d.id
ORDER BY surname
</xsql:query>(this is the same as the input document, except the namespace declaration has been stripped out, making the XML invalid).
I've tried including other xsql tags in the same document (e.g. xsql:include-xsql), these seem to work fine. Also, if I change the connect details, XSQL fails as expected, so it would appear xsql is being invoked by Tomcat (.xsql is mapped to the servlet), and XSQL successfully connecting to the database.
My setup is slightly unusual: I'm trying to use XSQL 1.0.4.1 with MySQL 3.23.32 using the mm.mysql 2.0.4 JDBC drivers. This is running on Tomcat 3.2.1 with JDK 1.3 (OJVM 1.2.330). But, since it works with the command line xsql, I'm at a loss as to why it's misbehaving through the servlet engine only... any ideas?
SteveHmm,
Even more confusing - the same .xsql document works fine with WebToGo - so I guess this is a Tomcat problem, somehow... Just can't understand why xsql:include-xsql works and xsql:query doesn't.
Steve -
Lower case tag names in XSQL query
XSQL queries appear to default all column tag names to upper case, even when you specifically use lower case characters. Is there any way to get them into lower case?
For example,
<?xml version="1.0"?>
<test connection="devel" xmlns:xsql="urn:oracle-xsql">
<xsql:query rowset-element="" row-element="" null-indicator="yes">
select 'hello' as hi from dual
</xsql:query>
</test>
Results in,
<?xml version="1.0" ?>
<test>
<HI>hello</HI>
</test>
I would really like to get <HI> to <hi>...
thanks.You can also preserve case by putting quotes around the column alias:
For example,
<?xml version="1.0"?>
<test connection="devel" xmlns:xsql="urn:oracle-xsql">
<xsql:query rowset-element="" row-element="" null-indicator="yes">
select 'hello' as "hi"
, 'Hello' as "Hi"
, 'HELLO' as "HI"
from dual
</xsql:query>
</test>
This way you can also get mixed case. -
XSQL query output as parameter for next xsql query
Hi,
Is it possible to use the output of one xsql query as input parameter for the next xsql query in the same file. I am trying to retreive an id from the query and use it in the next one. I cannot combine all the queries into one, since I intend to make the first query a database function that returns the id I am looking for. I am looking for something like this
<xsql:query>
select '1000' as myid
from dual
</xsql:query>
<xsql:query>
select add1,ro1
from table1
where id = {@myid}
</xsql>
I need the id returned by the first query to be used in the second one. Eventually my first query will be a stored procedure that validates the users rights and on sucess return the following tag <myid> 1000 <myid>.
Please let me know , how I can achieve my goal of validating a user's priveleges and then executing the second query.
Thanks
PadmajaHi ,
Thanks for the response.This works if the first query is a select .
If the first query was a call to a db procedure that returned the <myid>100<myid> would this still work?
<xsql:set-page-param name="myid">
<xsql:include-owa>
xyz;
</xsql:include-owa>
</xsql:set-page-param>
<xsql:include-param name="myid"/>
<xsql:query>
select name from mytable where id={@myid}
</xsql:query>
I have to use include-owa as the db procedure xyz does some cookie validations and then returns an id based on that. The procedure xyz returns an xml tag of form <myid>100<myid>
This does not work as the value of myid is not available to the second query.
Thanks
Padmaja -
XMLElement not returning XML with xsql:query
I am trying to use a select statement containing XMLElement, XMLAgg and XMLForest functions from a xsql servlet.
<page xmlns:xsql="urn:oracle-xsql" connection="HOM_WISP">
<xsql:query row-element="" rowset-element="STATEMENT">
SELECT
XMLElement("GROUP", XMLAttributes(gst_group AS GSTGroup,
display_group AS DisplayGroup),
XMLAgg(
XMLElement("PAYMENTDETAIL",
XMLForest(phase_type,
contract_num,
mark_block,
cut_permit,
destination,
stratum_code,
species_code,
sort_code,
truck,
back_haul,
uom_desc,
uom_code,
gst_exempt_flag,
pay_deduct_desc,
actual_rate,
gst_registrant_num,
load_count,
quantity,
volume,
earnings)))).getClobVal() as PAYMENTITEM
FROM ws_cntr_statement_vw
GROUP BY gst_group, display_group
</xsql:query>
</page>
When XML is returned only the out most XML as follows the inner elements are text. I truncated the output but you can see that GROUP and PAYMENTDETAIL are not elements but text. I want them all to be elements.
<page>
<STATEMENT><PAYMENTITEM><GROUP GSTGROUP="1_GST" DISPLAYGROUP="2_RETRO"><PAYMENTDETAIL><PHASE_TYPE>Purchasing</PHASE_TYPE><CONTRACT_NUM>3346</CONTRACT_NUM><MARK_BLOCK>GA500B-0001</MARK_BLOCK><DESTINATION>LC</DESTINATION><STRATUM_CODE>18</STRATUM_CODE><SPECIES_CODE>SP</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>-9.32</ACTUAL_RATE><GST_REGISTRANT_NUM>R102090347</GST_REGISTRANT_NUM><LOAD_COUNT>1</LOAD_COUNT><QUANTITY>28440</QUANTITY><VOLUME>36.68</VOLUME><EARNINGS>-265.06</EARNINGS></PAYMENTDETAIL></GROUP></PAYMENTITEM><PAYMENTITEM><GROUP GSTGROUP="1_GST" DISPLAYGROUP="4_CNTRPAY"><PAYMENTDETAIL><PHASE_TYPE>ADV/REC NO CONTRACT</PHASE_TYPE><UOM_DESC>flat</UOM_DESC><UOM_CODE>FL</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><PAY_DEDUCT_DESC>PAY 12 ADVANCE RECOVERY ES4922</PAY_DEDUCT_DESC><ACTUAL_RATE>32644.87</ACTUAL_RATE><GST_REGISTRANT_NUM>R123330532</GST_REGISTRANT_NUM><EARNINGS>-32644.87</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>FIREWOOD/STUMPAGE ALL BLOCKS</PHASE_TYPE><UOM_DESC>flat</UOM_DESC><UOM_CODE>FL</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><PAY_DEDUCT_DESC>FIREWOOD LOAD # 151819</PAY_DEDUCT_DESC><ACTUAL_RATE>25</ACTUAL_RATE><GST_REGISTRANT_NUM>R123083735</GST_REGISTRANT_NUM><EARNINGS>-25</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>SB#2 PAY RD USE</PHASE_TYPE><UOM_DESC>flat</UOM_DESC><UOM_CODE>FL</UOM_CODE><GST_EXEMPT_FLAG>1</GST_EXEMPT_FLAG><PAY_DEDUCT_DESC>ROAD USE ES4208 BLOCK 9</PAY_DEDUCT_DESC><ACTUAL_RATE>898.1</ACTUAL_RATE><EARNINGS>898.1</EARNINGS></PAYMENTDETAIL></GROUP></PAYMENTITEM><PAYMENTITEM><GROUP GSTGROUP="1_GST" DISPLAYGROUP="1_ORIGINAL"><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>FED</DESTINATION><STRATUM_CODE>01</STRATUM_CODE><SPECIES_CODE>FI</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>14</LOAD_COUNT><QUANTITY>498300</QUANTITY><VOLUME>579.54</VOLUME><EARNINGS>9716.85</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>06</STRATUM_CODE><SPECIES_CODE>FI</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>33</LOAD_COUNT><QUANTITY>1096770</QUANTITY><VOLUME>1300.24</VOLUME><EARNINGS>21387.07</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>13</STRATUM_CODE><SPECIES_CODE>LO</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>84</LOAD_COUNT><QUANTITY>3219510</QUANTITY><VOLUME>3990.95</VOLUME><EARNINGS>62780.68</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>21</STRATUM_CODE><SPECIES_CODE>MX</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>2</LOAD_COUNT><QUANTITY>71030</QUANTITY><VOLUME>91.4</VOLUME><EARNINGS>1385.09</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>PUL</DESTINATION><STRATUM_CODE>16</STRATUM_CODE><SPECIES_CODE>LO</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>18</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>3</LOAD_COUNT><QUANTITY>104980</QUANTITY><VOLUME>173.46</VOLUME><EARNINGS>1889.64</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0030</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>06</STRATUM_CODE><SPECIES_CODE>FI</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>15</LOAD_COUNT><QUANTITY>514800</QUANTITY><VOLUME>610.27</VOLUME><EARNINGS>10038.64</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0030</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>18</STRATUM_CODE><SPECIES_CODE>SP</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>1</LOAD_COUNT><QUANTITY>35740</QUANTITY><VOLUME>46.43</VOLUME><EARNINGS>696.93</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0030</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>PUL</DESTINATION><STRATUM_CODE>16</STRATUM_CODE><SPECIES_CODE>LO</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>18</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>3</LOAD_COUNT><QUANTITY>100280</QUANTITY><VOLUME>165.68</VOLUME><EARNINGS>1805.04</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>3350</CONTRACT_NUM><MARK_BLOCK>ES4922-0026</MARK_BLOCK><CUT_PERMIT>922</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>06</STRATUM_CODE><SPECIES_CODE>FI</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>37</ACTUAL_RATE><GST_REGISTRANT_NUM>R123330532</GST_REGISTRANT_NUM><LOAD_COUNT>5</LOAD_COUNT><QUANTITY>197320</QUANTITY><VOLUME>233.92</VOLUME><EARNINGS>7300.84</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>3350</CONTRACT_NUM><MARK_BLOCK>ES4922-0027</MARK_BLOCK><CUT_PERMIT>922</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>21</STRATUM_CODE><SPECIES_CODE>MX</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>37</ACTUAL_RATE><GST_REGISTRANT_NUM>R123330532</GST_REGISTRANT_NUM><LOAD_COUNT>1</LOAD_COUNT><QUANTITY>38920</QUANTITY><VOLUME>50.08</VOLUME><EARNINGS>1440.04</EARNINGS></PAYMENTDETAIL><Sorry I guess I haven't explained very well. When I am issuing the SELECT statement which uses XMLElement I have to convert output to string in order to have a column alais PAYMENTITEM. It is then not reconnized as XML in the
xsql:query call
If I do not assign a alias to query I get following error
oracle.xml.sql.OracleXMLSQLException: Character ',' is not allowed in an XML tag
If I assign without using getClobVal() I get this error
oracle.xml.sql.OracleXMLSQLException: Conversion to String failed
If I then use the getClobVal() to assign column alias it appears as if entire result set is now a string then <> tag delimiters are now show with "<" signs instead. -
I am getting an error when running an xsql:query. I can run simple queries, so it is not a connection porblem. The xml parses in jDeveloper10g so it appears to not be ill-formed XML. I have tried containing the SQL statement in CDATA tags, and tried replacing < and > with their entity references < and & gt; and I have tried both at the same time.
The Query is as follows
<page xmlns:xsql="urn:oracle-xsql" connection="V7Test">
<xsql:query fetch-size="100" max-rows="-1" null-indicator="no" tag-case="lower">
<![CDATA[
select
ts_jobs.job_number,
sum(ts_jobs.period_hours),
ts.period_end_date
from
etr.etr_timesheet_days ts_days,
etr.etr_timesheet_hours ts_hours,
etr.etr_timesheet_jobs ts_jobs,
etr.etr_timesheets ts
where
ts_hours.hours != 0
and (
(nvl(ts_jobs.corrected_id,0) = 0
and nvl(ts_hours.corrected_id,0) = 0
and ts.date_sent_to_pmjcap >=ts_hours.date_entered)
or (ts.date_sent_to_pmjcap < ts_hours.date_corrected)
and ts_days.timesheet_day_id = ts_hours.timesheet_day_id
and (
(ts_days.period_date in ('01-JAN-03','02-JAN-03','03-JAN-03')
and ts.period_end_date = '03-JAN-03')
or (ts_days.period_date in ('27-DEC-03','28-DEC-03','29-DEC-03','30-DEC-03','31-DEC-03')
and ts.period_end_date = '02-JAN-04')
and ts_days.timesheet_id = ts.timesheet_id
and ts_jobs.timesheet_job_id = ts_hours.timesheet_job_id
and (
(ts_jobs.job_number in (9719003,9849003,9849001,9719001))
or (ts_jobs.job_number in (9719333,9849333,9849334,9719334))
or (ts_jobs.job_number in (9719004,9849004,9719009,9849009))
or (ts_jobs.job_number in (9719444,9849444,9849445,9719445))
and ts.timesheet_id = ts_jobs.timesheet_id
and ts.employee_number = '050405'
and exists
(select
emp_clock,
date_incurred
from
asi_apps.vw00plw
where
substr(job_number,-8) = ts_jobs.job_number
and date_incurred = ts.period_end_date
and emp_clock = lpad('050405',6,0)
group by
ts_jobs.job_number,
ts.period_end_date,
ts_hours.hours
]]>
</xsql:query>
The Error I get is as follows
<?xml version="1.0" encoding="windows-1252" ?>
- <!--
| Uncomment the following processing instruction and replace
| the stylesheet name to transform output of your XSQL Page using XSLT
<?xml-stylesheet type="text/xsl" href="YourStylesheet.xsl" ?>
-->
- <page>
<error>oracle.xml.sql.OracleXMLSQLException: Character ')' is not allowed in an XML tag name.</error>
</page>
I think it is parsing a '<' as a tag delimiter.
Anyone have a similiar problem? a workaround?
regards,
BillI found the answer. The problem is the selected 'column' sum(ts_jobs.period_hours). Apparently, the XSQL servlet attempts to assign the value 'sum(ts_jobs.period_hours)' directly to an XML element.total_hours. That fails.
The work-around is to use an alias. This code works
sum(ts_jobs.period_hours) total_hours,
A fix to the XSQL servlet would be in order, perhaps adding a CDATA container around 'columns' that are are normal SQL functions.
regards,
Bill -
<?xml version="1.0"?>
<Antraege connection="xmldemo9i" xmlns:xsql="urn:oracle-xsql">
<Antragsteller>
<xsql:query tag-case="lower" rowset-element="" row-element="antragsteller">
select * FROM v_betriebsdaten
WHERE betr_id='{@betr_id}'
</xsql:query>
</Antragsteller>
</Antraege>
This is the File *.xqsl which makes problems.
When I use a connection to our 8i database it works correctly.
In use with our 9i database I get the following error:
ORA-00600: Interner Fehlercode, Argumente: [ttcgcshnd-1], [0], [], [], [], [], [], []
If I use the SQL select statement in SQLPlus on the 9i db I get the correct result.
Thanks for your adwiseIf I try your solution I got the message "There is no value for all variables"
But it seems the problem must be another.
When I hardcode the value for betr_id as you will see after I got the same error messsage as I described.
<?xml version="1.0"?>
<Antraege connection="xmldemo9i" bind-params="betr_id" xmlns:xsql="urn:oracle-xsql">
<Antragsteller>
<xsql:query tag-case="lower" rowset-element="" row-element="antragsteller">
select * FROM v_betriebsdaten
WHERE betr_id=727709
</xsql:query>
</Antragsteller>
</Antraege>
And the error
ORA-00600: Interner Fehlercode, Argumente: [ttcgcshnd-1], [0], [], [], [], [], [], []</
If I connect with a 8i DB all works correct -
Af:query number attributes BUG in TP3
Hello,
The component af:query renders a spinbox for the number attributes. The spinbox stops working when it reaches the zero value or when I put a zero value manually.
I suppose it's a bug in the javascript code that manages it.
Thanks,
MarcBy "stops working" do you mean it doesn't allow you to decrement the zero (0) value to a negative number [but still allows incrementing]?
or do you mean that neither the increment or decrement buttons works from that point on?
Maybe you are looking for
-
Error in external interactive activity redirection from workspace
I'm not able to configure external interacitve activity in studio 6.0. Here what's done: -added activity, main task imlementation = external -assigned prepare(), commit() methods -added new server configuration When launching workspace, the > sign on
-
ESYU: MTL_MATERIAL_TRANSACTIONS 와 MTL_ONHAND_QUANTITIES_DETAIL의 mismatch 찾는
Purpose Oracle Inventory Management - Version: 11.5.7 to 11.5.10 Onhand quantity table(MTL_ONHAND_QUANTITIES_DETAIL - MOQD) 과 transaction history table(MTL_MATERIAL_TRANSACTIONS - MMT) 간의 수량 불일치 내역을 찾는 방법에 대해 알아본다. Solution 제공되는 standard scripts는 onh
-
SQL subselect rounds unintentional in SAP B1
Hey everyone, if I am executing a select-statement with a subselect in sap b1, the result of the subselect is rounded - why? If I run a query without other tables, I get the exact value. SELECT T0.[TransId], T0.[RefDate], (SELECT T2.Rate FROM ORTT T2
-
Com.sap.portal.connectivity.destinations.PortalDestinationsServiceException
Hi I am getting this error for some users in the portal. com.sap.portal.connectivity.destinations.PortalDestinationsServiceException:User is missing credentials for connecting to alias SAP_R3_humanResources. This is only happenning for some of the us
-
Error in itunes when connecting ipod
hi if anyone could help me it would be good. when i connect my ipod and it loads itunes it displays an error message saying the file or directory itunes/iprefs is corrupt and unreadable what can i do?