Posts

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/pegarul...

configure Oracle Golden Gate between Oracle - Postgres

 Source: Oracle 19c  Target: PostgreSQL 15 Golden Gate Version: Golden Gate 19.1 for Oracle (Source), Golden Gate 19.1 for PostgreSQL Database (Target ). Source Hostname: oracle  Target Hostname: postgres  Run below commands on Target Postgres database by root , postgres and Oracle users :-  install postgress dev binary :- rpm -ivh libtermcap-devel rpm -ivh readline-devel rpm -ivh gcc* rpm -ivh zlib rpm -ivh postgresql93-odbc yum search postgre | grep odbc give full permission to /tmp folder ( chmod -R 777 /tmp) download and install postgress 15  https://www.postgresql.org/ftp/source/v15.1/ postgresql-15.1.tar.gz tar -xvf above file  ./configure mkdir build_dir cd build_dir /path/to/source/tree/configure [options go there] make make install make install-docs adduser postgres mkdir /u02/pgsql/data chown postgres /u02/pgsql/data su - postgres /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data You can now start the database server using: /usr/local/pgsq...

oracle physical standby db creation with broker config

SOURCE SERVER Create the new directories: mkdir /oraflashback/PRODDG1 mkdir /oraarc1/PRODDG1 mkdir /oralog1/PRODDG1 mkdir /oralog2/PRODDG1 create a backup of pfile . then move ahead . Using SQL*Plus: show parameter recovery; alter system set db_recovery_file_dest='/oraflashback/PRODDG1' scope=spfile; alter system set db_recovery_file_dest_size=10G scope=spfile; alter system set db_flashback_retention_target=2880; Modify the parameters in the pfile: *.instance_name=PRODDG1 *.service_names=PROD.com *.db_file_name_convert=PRODDG2,PRODDG1 *.log_file_name_convert=PRODDG2,PRODDG1 SQL> alter system set instance_name=PRODDG1 scope=spfile; System altered. SQL>  alter system set service_names='PROD.com'  scope=spfile; System altered. SQL> alter system set db_file_name_convert=PRODDG2,PRODDG1 scope=spfile; System altered. SQL> alter system set log_file_name_convert=PRODDG2,PRODDG1 scope=spfile; System altered. shutdown immediate; ...

recover oracle database exclude tablespace

db_file_name_convert=('/oradata3/PRODPV/','/oradata3/PRODQA/','/oratemp1/PRODPV/','/oratemp1/PRODQA/') log_file_name_convert=('/oralog1/PRODPV/','/oralog1/PRODQA/','/oralog2/PRODPV/','/oralog2/PRODQA/') [oracle@usnode dbs]$ cat CRQ000000123456.cmd run { set until time "to_date('mar 03 2016 11:59:00','Mon DD YYYY HH24:MI:SS')"; allocate channel t1 type 'SBT_TAPE' PARMS='ENV=(NB_ORA_CLIENT=usnode.com,NB_ORA_POLICY=P-A11-BE-ORAL-FULL)'; allocate channel t3 type 'SBT_TAPE' PARMS='ENV=(NB_ORA_CLIENT=usnode.com,NB_ORA_POLICY=P-A11-BE-ORAL-INCR)'; allocate channel t5 type 'SBT_TAPE' PARMS='ENV=(NB_ORA_CLIENT=usnode.com,NB_ORA_POLICY=P-A11-BE-ORAL-ARCH)'; allocate auxiliary channel a1 type 'SBT_TAPE' PARMS='ENV=(NB_ORA_CLIENT=usnode.com,NB_ORA_POLICY=P-A11-BE-ORAL-INCR)'; allocate auxiliary channel a3 type 'SBT_T...