Stuff like this is the main reason why I still prefer manual DB creation
and export/import for upgrades.

I had a similar issue, although not after a migration. It was fixed by
unloading and reloading the JVM manually. I believe it requires the
instance bounced and usually takes quite awhile. See MetaLink for
details.

Just in time for the long holiday weekend (in the States)...

GL!

Rich

-----Original Message-----
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)
Sent: Thursday, May 25, 2006 2:11 PM
To: Oracle Discussion List
Subject: Post10gR2Migration:Java:ORA-29532

Hello
We migrated to 10gRel2 from 9iRel2 and started getting this error.
29532, 00000, "Java call terminated by uncaught Java exception: %s"
// *Cause: A Java exception or error was signaled and could not be
//       resolved by the Java code.
// *Action: Modify Java code, if this behavior is not intended

Metalink did not help us much based on our search.
execute
dbms_java.grant_permission('SCHEMA_USER','java.net.SocketPermission','SE
RVER','resolve');
commit;
execute
dbms_java.grant_permission('SCHEMA_USER','java.util.PropertyPermission',
'*','read,write');
commit;

Has any one come across this? Googling too did not help much.
This is production and we have raised a SR with Oracle. In the meantime
i thought i will ping oracle-l.

Thanks
GovindanK
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l