Datatypes in HTMLDB

Hi,
I am just getting started with HTMLDB. We are planning to use it as our adhoc query tool, but when I started creating a report I cannot select certain fields. I have determined that all the affected fields so far are of type FLOAT. Can someone point me to the relevant documentation about supported datatypes.
THANKS,
Steve

Hi Rosy,
Sorry to be unclear. I am using "Query Builder". I have selected two tables in my schema that I want for a report, but there are several columns in those tables that I cannot select to show in the report, i.e. no check box next to them. I have determined that all fields in this case that I cannot select are defined in the database as of type FLOAT.
What I am looking for is documentation that would indicate what datatypes can/cannot be used or accessed.
Also, is it possible to import sql statements in to the "Query Builder"? I was able to do this in the old version of DISCOVERER I was using previously.
Versions:
HTMLDB 2.0
RDBMS 9.2.0.7
THANKS,
Steve

Similar Messages

Long column as a datatype in htmlDB

Why am I not able to add a long column or display a long
column using htmlDB?
I am trying to add a new column of data type "LONG" to one of my tables and I am not seeing "LONG" as an option in the "Type" list provided by -->Workspace Sudheshna>SQL Workshop>Manage Table.
Thank you.

Long columns were deprecated several years ago as I remember it. They only exist now for legacy support. Use CLOB.
Thanks,
Tyler

Inserting Object into Intermedia through HTMLDB form

Greetings,
I'm using HTMLDB and trying to upload an image via a form into an intermedia table with the following columns
id number
image ORDSYS.ORDIMAGE
The object is uploaded into www_flow_files into a BLOB datatype (I'm using an html form and browsing for the file) into wwv_flow_files. I'm trying to figure out how to copy this into my intermedia table from the wwv_flow_files table. How does one go about doing this in pl/sql. Is there a conversion from blob to ORDSYS.ORDIMAGE?
Any help greatly appreciated.
thx in advance,
cliff

at the end is an example of a procedure that will copy lobs from a table and make them image objects, it may help...
You could load OrdImage for one blob at a time with something like:
insert into images <YOURID>,ORDSYS.ORDImage.init()
returning rowid, pict into thisrowid, obj;
select b from wwv_flow_files into myblob;
-- Set the lob locator in the object and flag it as local
obj.source.localdata := myblob;
obj.setLocal();
obj.setMimeType(<MIMETYPE FROM WEB FILE POST>);
begin
obj.setProperties();
Exception
when others then
null; -- Ignore exceptions
end;
create table lobs (item_id number primary key, b blob);
create table images (item_id number primary key, pict ordsys.ordimage);
create or replace procedure copy_blobs_to_imgobjs
as
obj ORDSYS.ORDImage;
ctx raw(4000):=null;
nxtseq number;
thisrowid urowid;
BEGIN
for b_rec in (select item_id, b from lobs) loop
insert into images (item_id,pict) values (
b_rec.item_id,
ORDSYS.ORDImage.init())
returning rowid into thisrowid;
select t.pict into obj from images t
where rowid = thisrowid for update;
-- Set the lob locator in the object and flag it as local
obj.source.localdata := b_rec.b;
obj.setLocal();
-- Extract the properties of the image.
obj.setproperties();
update images t set t.pict=obj
where rowid = thisrowid;
commit;
end loop;
END;
show errors;

Complex datatypes for webservices

Hello all,
Question from customer:
"...Its not possible to user webservices in htmldb, that user complex types for paramater or return.
Creation htmldb webservice formulars work only with literal soap data types. But soap xsd support complex types or arrays. Thus, we can not use htmldb for accessing such services. .."
If customer uses complex datatypes it appears a ora-20001.
Is there a way to use complex datatypes for webservices in htmldb or will it be included in a new release or patch?
thanks
Hendrik

Hi,
Did you solve this one?
I'm having the exact same problem, trying to communicate with Oracle Wireless webservices from htmldb,
which kind of made me dissapointed because they are both Oracle products! Basically what wireless wants is an array input and htmldb complains about this!
Any solutions?
Magnus

HTMLDB 1.6 fails during plain text upload (ORA-20001 & ORA-01461)

All
I'm trying to upload a txt file into HTMLDB 1.6 but it's failing with the following error:ORA-20001: Load csv data error: ORA-01461: can bind a LONG value only for insert into a LONG column
I don't have any LONG column types but I do have 3 VARCHAR2(2000) columns within the Oracle table. The source file I'm trying to upload comes from an Access2000 table.
If anyone can advise that would be great...becoming a bit frustrated !!
David

Similar problem maybe?
I have created a page with a tabular form using the wizard. I am trying to create a Function returning Error Text validation for the grid. I can step through the wizard without any problems, but when I hit Create I am getting this error...Not even inserting records yet?
Is there a limit to the characters that you can enter in the Validation process? I'm verifying quite a bit so the procedure is fairly long. I also have a varchar2(1000) column but no LONG datatypes.
Any help with this error would be wonderful.
I am still in HTMLDB 1.6, running against a 10g database.
Thanks,
Janel

HTMLDB trimming - when and why?

Hi, I recentrly found that I couldn't delete one row that I entered within my htmldb app.
It turned out that when I was inserting this row I've entered a value (varchar2) beginning with space. However on displaying the space was trimmed. And my delete process did not even fail (It gave something like "Process concluded successfully!") which was a pure lie. :-)
The proces is "DELETE FROM MYTABLE WHERE MYFIELD = :P99_MYITEM";
I am using version 1.6
Please tell me is this a bug and why am forced to use trim on every insert process.
Please don't tell me to use numeric ID for a key because am not the designer of this table.
If there is an automatic trim, why isn't it used when the value is inserted or why is this trim used at all if this space is part of the value?
10x.

Sounds like this has very little to do with HTMLDB. The VARCHAR2 datatype will contain exactly what you put in it (if you insert a value with a leading space, that's what you'll get). Also, your delete did not really fail (which would indicate a error of some kind), it merely resulted in zero rows deleted.
There is no automatic trim, but you can code this functionality into a trigger or stored procedure.

Clob DataType, NULL and ADO

Hello,
First, I'm french so my english isn't very good
I have a problem with Oracle Clob DataType. When I try to put NULL value to
CLOB DataType with ADO, changes aren't not made.
rs.open "SELECT ....", adocn, adOpenKeyset, adLockOptimistic
rs.Fields("ClobField") = Null ' In this case, the Update doesn't work
rs.update
rs.Close
This code works if I try to write a value which is different than Null but
not if is equal to Null. Instead of having Null, I have the old value
(before changes), the update of the field doesn't work.

I experience the same, did you find a solution to your problem?
Kind regards,
Roel de Bruyn

Questions on Master-Detail HTMLDB HOW-TO

Hi all
I have created a 3 page application based on the master detail how-to given at http://www.oracle.com/technology/products/database/htmldb/howtos/index.html
Instead of DEPT and EMP tables I have PERSON and PERSON_ADDR tables. The PK of PERSON is the person_id and the PK of PERSON_ADDR is the person_id and addr_start_dt. Person_id column in PERSON_ADDR is obviously the FK to the master table PERSON(person_id).
At first I had problems trying to create the pages themselves because the wizard always hides the person_id column on all the forms(and I don't want that,even though it is a sequence number I still want people to see it) , it being the PK, then somehow I managed it to display the person_id by replacing the EDIT link with the person_id itself. Now if a person already has an address and I click on EDIT then it copies the person_id values and others to the next page and all looks good but when I try to create a new address it does it ?? (It should take across the person_id as well)
My PERSON report is on page 1, when I click edit against a person it takes me to page 2 where I can see+change all the person details plus I can see the person_addr details. When I click edit against a person address it takes me to page 3 and I can edit all the address details nicely copied to the new page but when I click CREATE on the page 2, then all the fields appear as NULL on page 3( all the fields but the person_id should be null here). How can I fix this ?
Also, for my person address I would like to validate the address dates , there should be no overlapping start and end dates for a person's address. How to do this ? I think I will need to create a function to which I pass the person id and the new start and end dates and this function returns error message,if any, or null. I had a play around with validation and I think I need to use "function returning error text", what should I put in the "validate expression 1" box then...just something like
begin
my_function(param_1,param_2)
end;
If yes, then what variables would store the new start date and new end date of an address.
Lastly, for every table do I have to user a sequence number or a trigger to define a primary key, what if the primary key is just a character code and I want the users to add it ?
Thanks a lot in advance !!

thanks Marc.
Yes you are right, I used the 1.5 viewlet. I will try the master-detail wizard now.
With the primary key problems, for things to work nicely in HTMLDB, do you suggest each and every tables should have a sequence number generated primary key ? We have some tables for various statuses like ACTIVE,CLOSED where these codes themselves are the primary keys, so you suggest making these codes unique keys but still have a sequence number PK ? Also when I want the users to enter the primary key themselves I will let them enter new ones but not update existing ones, so data entegrity is maintained.
I was able to work out how to create validations using "functions returning error text" but my problem is I need to be able to compare what the user has just updated/entered with the data that already exists in the table. I have a table called person_Address having columns like person_id, start_dt,end_dt and various other fields. The primary key is person_id and start_dt and I need to put a validation which avoids any overlapping addresses. Overlap as in there can be only 1 active address for a given start and end date range. Does HTMLDB has something like :new.start_dt the way we can write database triggers ? Please suggest a way to do this.
Lastly, how does HTMLDB handles error messages raised by table triggers. Can they be shown along with the item on the page as we can with the other HTMLDB validations ? I have many tables with all sorts of triggers and if any validation fails I generally do...raise_application_error(-20001,get_my_message(234));
get_my_message function returns the message text for message number 234 . Will this message be displayed somewhere or not ? Do I have to duplicate my validations , once in the triggers and then in HTMLDB as well ?

Questions on printing in htmldb

I try to create an invoice page to print.
Some questions I ask to myself:
- Is it possible to print to an A4 (papersize)? (I mean, does the application have notions of pagesize or is everything controlled by the browser? this is important when you need to repeat some information on the second page)
- can I include "pagenumber of total pagenumbers"?
- Is it possible to repeat an header / footer?
In my opinion it is very hard to do this with htmldb...
I started my "print report" like this:
- created static html like I would like to have my report(in notepad)
- in htmldb I try to create "the same thing", first I tried with the creation of a report, but, because you 'll always have rows, I stopped with that (I need to say "that item needs to be placed there"). Than I created a form, afterwards I added some other forms (regions) to the same page. One region for every table. I still have problems to place my items like I wish, because of region overlapping. Should I create other items in an other region (and link them) if I want to show the content of an item of an other region in that region?
I try to replace an Access application, and it looks good so far, but replacing the reports is very difficult!?
Is it me?
Dimitri

I found the answer on most of my questions on this site:
http://www.w3.org/TR/REC-CSS2/page.html#propdef-size
In short: you can a lot with css! so for my htmldb application: I probably need to change (create a new) my "print" template
HTMLDB is a very nice product and in a way it can replace an Access application, but in my opinion we are limited by the html.
What I would like to have in htmldb (compared with access):
- submission of a region and not the whole page (like in access subforms)
- in the tabular form, automatic one (or more) empty line(s) to create a new record (in access you have a new empty record)
- an easier why to customize the templates/css, for the default ones you can't change everything... (in access you can "draw" your form/report, that's very easy, in htmldb it's more difficult)

Not seeing a DataType.ICON request when browsing with Adobe Bridge?

Hi All,
I have followed the instructions in the "Customizing the UI->Displaying Thumbnails" section of the Adobe Drive SDK documents, but I have a problem. When I browse through my drive with Adobe Bridge, I am not getting the expected request for DataType.ICON for any of my items; when I call item.getDataTypes() from my
IGetAssetsHandler, I only see the DataTypes [BASIC, ASSET_PROPERTY].
Any ideas as to why this might be is happening?

In your ConnectHandler implementation, add the following capability:
capabilities.add(Capability.READ_XMP_METADATA);
I spent a week to figure it out.

Error Message when installing Companion CD for HTMLDB 1.6 and HTTP Server

Hi. First time forum user so bear with me.
I'm not sure if this is the correct forum for this but the assistance of anyone who may be able to shed some light on the problem whould be greatly appreciated. I am having a problem when attempting to install the Companion CD for HTMLDB 1.6 and HTTP Server, details given below:
The following Oracle components have been successfully installed
     Oracle 10gR2 Database.
     Oracle 10gR2 Database patch 10.2.03.
     Critical patch up date (security).
The following Oracle component failed to install.
     Companion CD for HTMLDB 1.6 and HTTP server
Scenario leading up to failure
     Extracted companion CD installation files to D:\oracle\utilities\Oracle_10_2_0_Companion
     Executed D:\oracle\utilities\Oracle_10_2_0_Companion\companion\setup.exe.
The following error message is displayed in a "JAVA VIRTUAL MACHINE LAUNCHER" dialog box
     "Could not find the main event class. Program will exit."
I have been attmepting to resolve this problem for over a week and have already checked the following with no resolution to the problem:
Cause. This issue may have to do with two issues (and may occur more on Windows):-
1. Within the ORACLE_HOME directory full pathname there is a space.
2. The directory from where the software / patch is being installed has a space within the directory full
pathname (where the file for the installation by default is named products.jar or products.xml).
Solution. To implement the solution, please execute the following steps:-
1. Rename the full pathname directory NOT to contain a space.
2. Launch again the OUI... and verify if the problem occurs.
Any further guidance would be greatly appreciated.
Edited by: user10386555 on 03-Oct-2008 02:51

Can you install using OUI from the RDBMS installation? IIRC, there is a problem using OUI on companion to install companion items.

Query results: which kind of datatype?

Hi to all,
I have a query which returns more more more records. I must insert this records in a string that i have to return from a function ( i have to invoke this procedure from an application visual basic 6).
What kind of datatype i have to use? Long datatype is small for me (and for my demand i cannot use clob).
Maybe i could return from a function (for example) a string that is concatenation of more than 2 long datatype! But could i do this? And, if yes, how could i declare my procedure (or function)?
Thanks
Edited by: user635881 on 8-ott-2008 11.09
Edited by: user635881 on 8-ott-2008 11.20

This is my code:
declare
risultati LONG;*
i number;
TYPE t_cur IS REF CURSOR;
TYPE type_rec IS RECORD (...more code...more code...);
cur t_cur;
bilancio_def_entry   type_rec;
BEGIN
OPEN cur FOR
SELECT q.codicepool, q.codicefisico, q.denominazione,
q.tipoedificio, q.tipoimpianto, q.stationtypecaminus, q.codiceateco,
+...more code ...more code...+
--end of select;+
risultati:='';
LOOP
FETCH cur INTO bilancio_def_entry;
EXIT WHEN cur%NOTFOUND;
if bilancio_def_entry.codicepool is null then
bilancio_def_entry.codicepool := bilancio_def_entry.codicefisico;
end if;
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita1)) || ';' || trim(to_char( bilancio_def_entry.energia1)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato1)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita2)) || ';' || trim(to_char( bilancio_def_entry.energia2)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato2)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita3)) || ';' || trim(to_char( bilancio_def_entry.energia3)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato3)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita4)) || ';' || trim(to_char( bilancio_def_entry.energia4)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato4)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita5)) || ';' || trim(to_char( bilancio_def_entry.energia5)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato5)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita6)) || ';' || trim(to_char( bilancio_def_entry.energia6)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato6)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita7)) || ';' || trim(to_char( bilancio_def_entry.energia7)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato7)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita8)) || ';' || trim(to_char( bilancio_def_entry.energia8)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato8)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita9)) || ';' || trim(to_char( bilancio_def_entry.energia9)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato9)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita10)) || ';' || trim(to_char( bilancio_def_entry.energia10)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato10)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita11)) || ';' || trim(to_char( bilancio_def_entry.energia11)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato11)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita12)) || ';' || trim(to_char( bilancio_def_entry.energia12)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato12)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita13)) || ';' || trim(to_char( bilancio_def_entry.energia13)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato13)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita14)) || ';' || trim(to_char( bilancio_def_entry.energia14)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato14)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita15)) || ';' || trim(to_char( bilancio_def_entry.energia15)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato15)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita16)) || ';' || trim(to_char( bilancio_def_entry.energia16)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato16)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita17)) || ';' || trim(to_char( bilancio_def_entry.energia17)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato17)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita18)) || ';' || trim(to_char( bilancio_def_entry.energia18)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato18)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita19)) || ';' || trim(to_char( bilancio_def_entry.energia19)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato19)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita20)) || ';' || trim(to_char( bilancio_def_entry.energia20)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato20)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita21)) || ';' || trim(to_char( bilancio_def_entry.energia21)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato21)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita22)) || ';' || trim(to_char( bilancio_def_entry.energia22)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato22)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita23)) || ';' || trim(to_char( bilancio_def_entry.energia23)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato23)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita24)) || ';' || trim(to_char( bilancio_def_entry.energia24)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato24)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita25)) || ';' || trim(to_char( bilancio_def_entry.energia25)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato25)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita26)) || ';' || trim(to_char( bilancio_def_entry.energia26)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato26)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita27)) || ';' || trim(to_char( bilancio_def_entry.energia27)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato27)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita28)) || ';' || trim(to_char( bilancio_def_entry.energia28)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato28)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita29)) || ';' || trim(to_char( bilancio_def_entry.energia29)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato29)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita30)) || ';' || trim(to_char( bilancio_def_entry.energia30)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato30)) || chr(10);*
risultati:= risultati || trim(bilancio_def_entry.codicepool) || ';' || trim(bilancio_def_entry.codicefisico) || ';' || trim(bilancio_def_entry.denominazione) || ';' || trim(bilancio_def_entry.tipoedificio) || ';' || trim(bilancio_def_entry.tipoimpianto) || ';' ||*
trim(bilancio_def_entry.stationtypecaminus) || ';' || trim(bilancio_def_entry.codiceateco) || ';' || trim(to_char(bilancio_def_entry.capacitatrasporto)) || ';' ||*
trim(to_char(bilancio_def_entry.capacitaconferita31)) || ';' || trim(to_char( bilancio_def_entry.energia31)) || ';' ||   trim(to_char(bilancio_def_entry.volumeprofilato31)) || chr(10);*
END LOOP;
INSERT INTO APPOGGIO VALUES (risultati);
commit;
CLOSE cur;
END;
Pl sql variable is risultati (it is a long type).
In the previous code i insert it in a table (but only to see what is results of concatenation ...it's not my purpose). When i insert this code in a procedure i want return from the procedure pl sql the variable risultati+. If risultati is longer than 32k i obtain an error. How could i do to obtain at the end a variable (or a concatenation of variables) long (for example) 2.000.000 of characters? This variable is the return variable of a procedure pl sql.
Thanks a lot.

Outlook can not display htmldb mail message correctly

We are using some applications which constructed by HTML DB. All mail messages from HTML DB applications can not be displayed correctly in Outlook, but they are displayed very well in Netscape mail client. This issue happens in both HTML DB 1.5 and 1.6. Therefore, I am not sure this is HTML DB mail package issue or outlook issue. Have anyone experienced this issue. Any suggestions are highly appreciated. Thanks in advance!
Here is a sample in our application.
We see the mail message in Outlook:
This message generated by the HTML DB Mail Package. -----=1T02D27M75MU981T02D27M75MU98
Content-Type: text/plain; charset=utf-8
 E-Leave System Notification for SGT China.(Note: it is NOT an official leave system) <HR align=left width="70%" noShade><TABLE width="80%"><TBODY><TR><TD width="20%">Leave User :</TD><TD width="50%">[email protected]</TD></TR><TR><TD>Formal:</TD><TD>No</TD></TR><TR><TD>Type :</TD><TD>Personal </TD></TR><TR><TD>Begin Time :</TD><TD>04-MAR-05 11:30</TD></TR><TR><TD>End Time :</TD><TD>04-MAR-05 13:30</TD></TR><TR><TD>Urgent Contact :</TD><TD>13811512211 </TD></TR><TR><TD>Note :</TD><TD>Go to CCB Haidian Branch for my debit cards again :( </TD></TR></TBODY></TABLE><A
href="http://sgt.us.oracle.com/pls/htmldb/f?p=132:101">E-Leave
System</A> E-Leave System Notification for SGT China.(Note: it is NOT an official leave system) <HR align=left width="70%" noShade><TABLE width="80%"><TBODY><TR><TD width="20%">Leave User :</TD><TD width="50%">[email protected]</TD></TR><TR><TD>Formal:</TD><TD>No</TD></TR><TR><TD>Type :</TD><TD>Personal </TD></TR><TR><TD>Begin Time :</TD><TD>04-MAR-05 11:30</TD></TR><TR><TD>End Time :</TD><TD>04-MAR-05 13:30</TD></TR><TR><TD>Urgent Contact :</TD><TD>13811512211 </TD></TR><TR><TD>Note :</TD><TD>Go to CCB Haidian Branch for my debit cards again :( </TD></TR></TBODY></TABLE><A
href="http://sgt.us.oracle.com/pls/htmldb/f?p=132:101">E-Leave
System</A> 
-----=1T02D27M75MU981T02D27M75MU98--
-----=1T02D27M75MU981T02D27M75MU98--
And this is my code:
declare
l_body_html varchar2(4000);
l_subject varchar2(100);
begin
l_subject := 'eLeave Notification from ' || lower(:app_user) || '@oracle.com'; l_body_html := ' E-Leave System Notification for SGT China.(Note: it is NOT an official leave system) ' || '<HR align=left width="70%" noShade>' || '<TABLE width="80%"><TBODY><TR>' || '<TD width="20%">Leave User :</TD><TD width="50%">' || lower(:app_user) || '@oracle.com' || '</TD></TR><TR><TD>Formal:</TD><TD>' || :P3_FORMAL || '</TD></TR><TR><TD>Type :</TD><TD>' || :P3_LEAVE_TYPE || ' </TD></TR><TR><TD>Begin Time :</TD><TD>'
|| '' || :P3_BEGIN_TIME || '' ||
'</TD></TR><TR><TD>End Time :</TD><TD>' || '' || :P3_END_TIME || '' || '</TD></TR><TR><TD>Urgent Contact :</TD><TD>'
|| :P3_CONTACT ||
' </TD></TR><TR><TD>Note :</TD><TD>' || :P3_NOTE || ' </TD></TR></TBODY></TABLE><A
href="http://sgt.us.oracle.com/pls/htmldb/f?p=132:101">E-Leave
System</A> ';
HTMLDB_MAIL.SEND(
P_TO => :P3_MAIL_TO,
P_FROM => '[email protected]',
P_CC => :P3_MAIL_CC,
P_BCC => :P3_MAIL_BCC,
P_BODY => l_body_html,
P_BODY_HTML => l_body_html,
P_SUBJ => l_subject);
end;
---------------------------------------------------------------------------------------------------------------

This was not well documented, but we have improved the doc for the next relase. Essentially, you need a carriage return / line feed every 1000 characters. This is part of the SMTP spec. The package does not do this automatically for you, so try adding them yourself. You can use utl_tcp.crlf for the crlf.
Tyler

Data of column datatype CLOB is moved to other columns of the same table

Hi all,
I have an issue with the tables having a CLOB datatype field.
When executing a simple query on a table with a column of type CLOB it returns error [POL-2403] value too large for column.
SQL> desc od_stock_nbcst_notes;
Name Null? Type
OD_STOCKID N NUMBER
NBC_SERVICETYPE N VARCHAR(40)
LANGUAGECODE N VARCHAR(8)
AU_USERIDINS Y NUMBER
INSERTDATE Y DATE
AU_USERIDUPD Y NUMBER
MODIFYDATE Y DATE
VERSION Y SMALLINT(4)
DBUSERINS Y VARCHAR(120)
DBUSERUPD Y VARCHAR(120)
TEXT Y CLOB(2000000000)
NBC_PROVIDERCODE N VARCHAR(40)
SQL> select * from od_stock_nbcst_notes;
[POL-2403] value too large for column
Checking deeply, some of the rows have got the data of the CLOB column moved in another column of the table.
When doing select length(nbc_providercode) the length is bigger than the datatype of the field (varchar(40)).
When doing substr(nbc_providercode,1,40) to see the content of the field, a portion of the Clob data is retrieved.
SQL> select max(length(nbc_providercode)) from od_stock_nbcst_notes;
MAX(LENGTH(NBC_PROVIDERCODE))
162
Choosing one random record, this is the stored information.
SQL> select length(nbc_providerCode), text from od_stock_nbcst_notes where length(nbc_providerCode)=52;
LENGTH(NBC_PROVIDERCODE) | TEXT
-------------------------+-----------
52 | poucos me
SQL> select nbc_providerCode from od_stock_nbcst_notes where length(nbc_providerCode)=52;
[POL-2403] value too large for column
SQL> select substr(nbc_providercode,1,40) from od_stock_nbcst_notes where length(nbc_providercode)=52 ;
SUBSTR(NBC_PROVIDERCODE
Aproveite e deixe o seu carro no parque
The content of the field is part of the content of the field text (datatype CLOB, containts an XML)!!!
The right content of the field must be 'MTS' (retrieved from Central DB).
The CLOB is being inserted into the Central DB, not into the Client ODB. Data is synchronized from CDB to ODB and the data is reaching the client in a wrong way.
The issue can be recreated all the time in the same DB, but between different users the "corrupted" records are different.
Any idea?

939569 wrote:
Hello,
I am using Oracle 11.2, I would like to use SQL to update one column based on values of other rows at the same table. Here are the details:
create table TB_test (myId number(4), crtTs date, updTs date);
insert into tb_test(1, to_date('20110101', 'yyyymmdd'), null);
insert into tb_test(1, to_date('20110201', 'yyyymmdd'), null);
insert into tb_test(1, to_date('20110301', 'yyyymmdd'), null);
insert into tb_test(2, to_date('20110901', 'yyyymmdd'), null);
insert into tb_test(2, to_date('20110902', 'yyyymmdd'), null);
After running the SQL, I would like have the following result:
1, 20110101, 20110201
1, 20110201, 20110301
1, 20110301, null
2, 20110901, 20110902
2, 20110902, null
Thanks for your suggestion.How do I ask a question on the forums?
SQL and PL/SQL FAQ

After upgrade HTMLDB 2.0, the browser can not launch MS words to view doc

I create a page with an item to hold the file id in flows_files.wwv_flow_file_objects$. and use the htmldb_util.get_file(:P14_file_id) on-load before header process to allow user to view the documents under flows_files.wwv_flow_file_objects$ table.
When we are still in HTMLDB 1.6, the window would pop-up to ask for Open, Save or Cancel. When we click open, the window would depend on the file extension to lauch the Ms Words or Excel or Acrobat reader to view the file.
After we upgrade to HTMLDB 2.0, the window won't pop-up asking for open, save or cancel. Instead, it would open another Internet Explorer to try to read the file. Since the web browser could not read the MS words or excel, all of page display strange characters. I check the httpd.conf file and mime.type in the apache, everything looks fine with me. Could anyone provide me further information on the troubleshooting...

>
Does any one have this issue before?
>
Probably not because this is internal build so most of us don't have this version :)
I suppose that there is internal forum for questions like this.
Dario

Datatypes in HTMLDB

Similar Messages

Maybe you are looking for