When you try to convert an xml file, which has a tag that contains for example one or more pdf files, into an XMLTYPE object, you will get the following error:
ORA-19011: CHARACTER string BUFFER too small
This error will be thrown because the content of a tag of an XMLTYPE is limited to 4000 bytes(this problem should be solved in 11g).
I have developed a solution/workaround for this.
For a project with Oracle Portal, I had to do some lookups in packages and procedures on the database to get some information about the project. Since I wasn’t working full-time for this project I had no access to the DB, except via the portal itself.
Several times I had the problem that the client wanted a quick answer for his question, but therefor I needed to dig into the code that was developed in the past. The problem was that the size for editing/viewing a package or procedure was limited to 30K and since there where several packages bigger than 30K, I couldn’t give them a quick answer.
If you only want to read the packages(not edit), there is a very easy portal solution for this problem:
A few months ago I wrote a blogpost about forms titled “Forms isn’t dead!”
Since then I went to Oracle Open World and gave a presentation on how to modernize your existing Oracle Forms application.
So you don’t have to throw away years of investment in Oracle forms.
I’m working at a customer that created a new application in Forms 10g and it was put in production last year.
And now there’s a thread on the OTN Forms forum started by Grant Ronald(Product Manager at Oracle):
What new features would you want to see in Oracle Forms?
So, if you want a cool new feature or an improvement in Oracle Forms…you know what to do!
Still not convinced that “Forms isn’t dead”?
In ApEx 4.0 you will be able to determine the “Default Error Display Location” under Shared Components/Edit Application Definition