Error importing data via Apex

Question

Hi,
I have an apex application on a 10g XE machine, and am in the process of migrating
this to an 11g machine (same version of apex: 3.2.1).
With a dozen or more "Apex" users, I first was a little disgruntled to find that there wasn't
a readily-available tool to migrate all the users across (add that to the "wish list" presuming there
isn't an easy user-migration mechanism, please).
Then I took the DDL across to the new platform, which worked quite well.
My next task was to move the data, in prior preparation for moving the applications.
On the old machine I performed a "data unload" to a separate XML file on each of my three tables
(its not a huge application).
On the new machine, I tried a "data load" into one table, and all I got was the unimaginative
error message shown below:
ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00222: error received from SAX callback function ORA-01008: not all variables bound ORA-24801: illegal parameter value in OCI lob function ORA-24801: illegal parameter value in OCI lob function
Of course, all these error messages are really informative... I can work out (not) from the error message
how to solve the problem... !
The table I'm moving has a dozen rows in it. The table has two CLOB columns in it and two BLOB columns.
If I cannot easily migrate the data, there's no point in moving the applications. Time to ask the forum for
help please.
Various attempts of backing up the whole schema with "exp" and "expdp" and even "SQL Developer" proved futile, now
it looks that I can add "apex" to that list too.
Any help appreciated; thanks in advance.
Mungo

Answer 1

Thankyou for your kind reply.
flavioc wrote:
First of all, apex users are migrated when you export and import the workspace.I'm guessing you have to be the Apex Administrator to do that? On my hosted source
application the highest privilege I enjoy is a single Workspace Administrator - nothing higher.
Hence the need to transfer the data "the long way".
>
Secondly, in my own experience XML data exports are good for simple cases, reasonable amount data (less than 100.000 rows) otherwise you may incur in a variety of problems like insufficient memory, table loading order because of failing constraints and trigger based rules.The XML file I am attempting to import is 928Kbytes in size, and comprises about twelve records with photographs stored in BLOBs
to bulk out this file.
>
Thirdly, i do not see why exp or expdp should not work, i'm using them all the time, so may be you want to be more specific on this.
As I understand it "expdp" needs a Directory object... that would require raising a ticket with the hosting company and asking for
them to create one (a step too far, at the moment ;-)
From failing human memory, the "exp" command seemed to store the tablespace where the tables were stored in. When I then went to
import from the resultant exported file, the tablespaces were different on the new machine. So I gave up on "exp".
I thought that the relatively new "SQL Developer" would come to my rescue, but it also has problems with CLOB and BLOB columns.
All in all it seems to be more work than I had bargained for: all I want to do is "lift" the application off one machine and drop it on
to the new machine, but Oracle seems to want me to spend at least three days to workaround all the silly "features".
Comments borne on frustration; forgiveness requested...
Mungo :-)