Verified the successful UDF generation by running the query in both DATA & RULES schema : SELECT dbms_java.longname(object_name) FROM all_objects WHERE status!='VALID' AND object_type LIKE 'JAVA%' and owner = 'schemaname';
Next day when we ran the same query, /2b12b644_DirectStreamReaderDB & /fad24711_DirectStreamReaderDB JAVA object's status got changed to INVALID. Verified dependencies for both objects but no results found. Please let us know, if anyone come across similar issue.
DB: Oracle 11g
Application Server: WebSphere 8.5
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
We are also facing same issue, we resolved most of the invalid java classes by running Pega suggested Alert command but still we are not able to fix the invalid status for below class- tried multiple times but no luck.
ALTER JAVA CLASS" com/pega/pegarules/data/internal/clipboard/directstream/DirectStream"
Able to resolve the issue by cloning the fresh copy of PRPC instance and run all the UDF functions.
Pena can think about the tool that would fix the UDF issue whenever Pega DB is cloned to different schema, this is a frequent requirement for most of the companies when they set-up prpc across multiple environments.