Hi Nagma,

There are 9-10 OOTB Large text attributes available at Page-Two and Page-Three level with Maximum length of 60000. You can rename one/multiple fields based on user needs. 

Regards,
MAK

Hi Nagma,

the attribute type for a large text (up to 4000 chars) is the MultiText.
It could be created in Page Three or reused from the ones available.
Once created, you can define the size and if any pattern has to be maintained (for example only number, not symbols, etc)

Hi Arif,

there are huge differences between both text attribute types, MT is a plain text attribute type, while LT it’s a rich text type. In MT you can use just one font type, with fixed font size.
In LT you can choose font, color, size, create tables and so on. I explain this functionality to my clients as an attribute that works like a “MS Word page”.

My best
Carlos

3 things for LT attributes :
1) The actual schema size limit is 2 million characters, the default max length is 60000 characters. Note that the default value can only be up to 4000 characters long.
2) In addition, Large Text attributes can be set as Journal fields. What this means is that the latest entry can be what is displayed, unless you set it to be Oldest First. In any event, every entry includes a date/time value and the name of the user that made the entry.
3) The HTML features that can be used are configurable. By no stretch are the ones available (see page 5-41 of the Admin Guide) the full HTML set, but they do allow you to do some pretty cool stuff (TABLES!!!!). And this is configurable for each LT attribute.

 Note that user-defined (flex) fields cannot be defined as LT as of 9340 (I haven’t seen a client 9350/9360 database yet).

Thank you everyone. Those are really helpful.
However, the content from that large text field doesn’t get copied if we do save as for that object. Is there any way to do so.

Regards,
Nagma

Not that I am aware of. I would post an SR at Oracle Support to ask that question.
 I looked around, and did not see anything about LT and save-as functionality. On the one hand, copying a huge amount of “stuff” when doing the save-as might have been seen as not a good thing to do. On the other hand, why not do it anyway??
 It may have just been an issue of it possibly taking WAY too much time if there were many LT attributes defined, and most had a large amount of text in there.

Thanks, Kevin. Users also face the same inconvenience. They don’t want to copy-paste the same content every time they do Save As for an Object which may contain tables, images etc. If Oracle can provide any workaround as well, that would be helpful.