This is NOT an Open Text recommendation. This is me thinking out loud. It seems to me that OTC got rid of all Long datatypes when they moved to LL95 and later systems. Part of that was (I think)converting Longs to CLOBs. Not sure that would help you either but could you probablyconvert the Longs to varchar2. This article explains how:
http://www.arikaplan.com/oracle/ari11498.html
--
Greg Kellogg
(361) 815-8950
From: eLinkDiscussion: Open Text Live Reports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Monday, August 24, 200912:35 PMTo: eLink RecipientSubject: How to manipulate LongData Type or Convert Long to Varchar2?
How to manipulate Long Data Type or Convert Long to Varchar2?
Posted by gdatsuser1 (Gerkin, Rick) on 2009/08/24 13:33
Livelink 9.1 workflows store mulit-line text as a Long datatype. However, LiveReport cannot do much with a Long. It cannot be used as a condition in a select and I cannot do find/replace on the contents. I want to convert the long to Varchar, but cannot do that either. I tried the Cast function Cast(wad.WF_VALLONG as VARCHAR2(500)), but that returns ORA-00932: inconsistent datatypes: expected NUMBER got LONG I also tried converting to char: to_char(wad.WF_VALLONG), but still get an ORA-00932 ORA-00932: inconsistent datatypes: expected CHAR got LONG. I've seen other (non-Livelink) articles that refer to PL/SQL scripts that execute SQL into a varchar2, but I don't know that I can insert PL/SQL commands into a Livereport. Does any body have any suggestions on how to convert Long's to a type I can manipulate?
BTW, I have NOT tested the methodology inmy last post on this topic – be sure to thoroughly test in Dev or outsideof Livelink altogether before trying with a Prod system.
If you can create a temporary table thatholds VARCHAR2 data, you should be able to export the data you are looking toconvert to a temporary table (don’t convert it in the original table),convert it and feed it to a new table so you can access it throughLiveReports. Long way around I know but it should get you what you need. Before you do ANYTHING with the Livelink DB, back it up, and test, test and testsome more before even thinking about doing this on PROD.
