Resolving invalid Pega Java class while upgrading Pega application from 7.1 to 8.4

 Resolving invalid Pega Java class from Oracle , If you got below error from DB side while upgrading Pega application from 7.1 to 8.4  :-


SQL> select dbms_java.longname(object_name), status, object_type from all_objects where
      object_type = 'JAVA CLASS' and status='INVALID';  2

 

DBMS_JAVA.LONGNAME(OBJECT_NAME)
--------------------------------------------------------------------------------
STATUS  OBJECT_TYPE
------- -----------------------
com/pega/pegarules/data/udf/directstreamreader/DirectStreamReaderDB2LUW
INVALID JAVA CLASS

 

com/pega/pegarules/data/udf/directstreamreader/DirectStreamReaderDB2ZOS
INVALID JAVA CLASS

 

com/pega/pegarules/data/udf/directstreamreader/BasicEnvironmentAdapter
INVALID JAVA CLASS

 


DBMS_JAVA.LONGNAME(OBJECT_NAME)
--------------------------------------------------------------------------------
STATUS  OBJECT_TYPE
------- -----------------------
com/pega/pegarules/data/udf/directstreamreader/DirectStreamReader
INVALID JAVA CLASS

 

com/pega/pegarules/data/udf/directstreamreader/DirectStreamReaderBase$Version6
INVALID JAVA CLASS

 

com/pega/pegarules/data/udf/directstreamreader/DirectStreamReaderBase$Version7
INVALID JAVA CLASS

 


DBMS_JAVA.LONGNAME(OBJECT_NAME)
--------------------------------------------------------------------------------
STATUS  OBJECT_TYPE
------- -----------------------
com/pega/pegarules/data/udf/directstreamreader/DirectStreamReaderBase
INVALID JAVA CLASS

 

com/pega/pegarules/data/udf/directstreamreader/DirectStreamReaderDB2LUW
INVALID JAVA CLASS

 

com/pega/pegarules/data/udf/directstreamreader/DirectStreamReaderDB2ZOS
INVALID JAVA CLASS

 


DBMS_JAVA.LONGNAME(OBJECT_NAME)
--------------------------------------------------------------------------------
STATUS  OBJECT_TYPE
------- -----------------------
com/pega/pegarules/data/udf/directstreamreader/DirectStreamReaderPostgreSQL
INVALID JAVA CLASS

 

com/pega/pegarules/data/internal/clipboard/directstream/DirectStreamV7
INVALID JAVA CLASS

 

com/pega/pegarules/data/internal/clipboard/directstream/InflaterV7
INVALID JAVA CLASS

 


DBMS_JAVA.LONGNAME(OBJECT_NAME)
--------------------------------------------------------------------------------
STATUS  OBJECT_TYPE
------- -----------------------
com/pega/pegarules/data/internal/clipboard/directstream/DirectStream
INVALID JAVA CLASS

 

com/pega/pegarules/data/internal/clipboard/directstream/PropertyReferenceUtiliti
es
INVALID JAVA CLASS

 14 rows selected.

Then , check the Java_class comp_name from dba_registry and if it valid then login via username whose  DBMS_JAVA.LONGNAME(OBJECT_NAME) is invalid and fire the below command :-


ALTER JAVA CLASS "com/pega/pegarules/data/internal/clipboard/directstream/PropertyReferenceUtiliti" RESOLVER ((*PG7_P820_SITA_RULES)(* public)) RESOLVE;

Run the above command for all invalid DBMS_JAVA.LONGNAME(OBJECT_NAME).

Comments

Post a Comment

Popular posts from this blog

Installing DBMS_JAVA package in Oracle and calling UTL_DBWS web services through Oracle database

Installing DBMS_JAVA package in Oracle following  files need to be run:-  sql> select comp_name, version, status from dba_registry where comp_name like '%JAVA%'; @?/javavm/install/initjvm.sql; @?/xdk/admin/initxml.sql; @?/xdk/admin/xmlja.sql; @?/rdbms/admin/catjava.sql; @?/rdbms/admin/catexf.sql; and verify your java installation in Oracle Database  sql> select comp_name, version, status from dba_registry where comp_name like '%JAVA%'; sql> select dbms_java.longname(object_name), status, object_type from all_objects where       object_type = 'JAVA CLASS'; ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ calling  UTL_DBWS  web services through Oracle Database :-  set the follwing parameters in .bash_profile of oracle user  export JAVA_HOME=$ORACLE_HOME/jdk ORACLE_BASE=/opt/oracle/product; export ORACLE_BASE ORACLE_HOME=/opt/oracle/product/11.2.0/dbhome_1; export ORACLE_HOME PATH=$PATH:/opt/o
Read more

stick the job to the specific instance in Oracle RAC

First method ( and easy one too ) :- note:-  must perform this activity on each instance one by one. ......stop jobs which is assigning to the specific instance..... $ export ORACLE_SID=SID connect database using job owner .... $ sqlplus username/password list of jobs and its instance....  sql> select JOB,INSTANCE from user_jobs;        JOB   INSTANCE ---------- ----------       2510          0       2951          0       2992          0       3091          0       3111          0       1570          0       1567          0       1568          0       1569          0       1571          0       1572          0 stick the job to the specific instance..... Syntax DBMS_JOB.INSTANCE (    job        IN BINARY_INTEGER,    instance   IN BINARY_INTEGER,    force      IN BOOLEAN DEFAULT FALSE); sql>execute dbms_job.instance(job=>1571, instance=>2,force=>true); verify from the instance number........
Read more

Starting background process GTX4 and GLOBAL_TXN_PROCESSES

Starting background process GTX4 Tue Jan 01 15:51:12 2012 GTX4 started with pid=64, OS id=11122 Tue Jan 01 15:51:43 2012 Auto-tuning: Starting background process GTX5 and Auto-tuning: Shutting down background process GTXi Like messages in alert log in RAC database This event is recorded in RAC environment only, which is normal.    Its normal for the database to automatically tune the number of these processes based on the workload of XA global transactions. If any application which using XA transaction and connecting to oracle RAC database, is it required. This normal behavior and you do not have to worry about this error messages.  If you are sure that you are not using XA and want to stop these messages. You can disable the GTXn background processes, then you must set GLOBAL_TXN_PROCESSES to 0 in your parameter file. Setting this parameter to 0 will disable the XA support on an Oracle RAC database. GLOBAL_TXN_PROCESSES specifies the initial numb
Read more