Skip to main content

Posts

🚀 Supporting Successful T24 Banking Application Upgrades from Oracle 11g/12c to Oracle 19c

🚀 Supporting Successful T24 Banking Application Upgrades from Oracle 11g/12c to Oracle 19c Modern banking platforms require continuous technology evolution while maintaining the highest levels of stability, security, and availability. During T24 (Temenos Transact) upgrade programs, one of the most critical activities is upgrading the underlying Oracle Database platform from legacy versions such as Oracle Database 11g / 12c to Oracle Database 19c. Upgrade execution may involve environment-specific challenges such as database compatibility issues, application dependency validations, object compilation errors, SQL behavior changes, and performance considerations. With specialized experience supporting these upgrade activities, our team provides technical assistance to help organizations: ✅ Analyze and resolve Oracle database upgrade-related challenges ✅ Validate T24 application compatibility with Oracle 19c ✅ Perform pre-upgrade readiness assessments ✅ Support upgrade execution and post-...
Post a Comment
Read more
Recent posts

AUDIT VAULT add extra data to EVENTDATA using vm disk

  check lsblk on root  [root@oracle19ctest ~]# lsblk NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS sda           8:0    0   60G  0 disk ├─sda1        8:1    0    1G  0 part /boot └─sda2        8:2    0   59G  0 part   ├─ol-root 252:0    0 39.6G  0 lvm  /   └─ol-home 252:1    0 19.4G  0 lvm  /home sdb           8:16   0   20G  0 disk └─sdb1        8:17   0   20G  0 part sdc           8:32   0   20G  0 disk └─sdc1        8:33   0   20G  0 part sdd           8:48   0   20G  0 disk └─sdd1      ...
Post a Comment
Read more

ORACLE AUDIT VAULT - UPDATE FROM 20.14 to 20.17.

 We can update the Oracle Audit Vault using the same configuration and we require to follow the below commands. firstly you need to download the Oracle Audit Vault patches. -- first need to update the new network environment using below commands.   vi /usr/local/dbfw/etc/dbfw.conf    - change GATEWAY to 192.168.128.255 and host ip to 192.168.128.50  - remove syslog ip from both records.  SYSLOGDEST="192.168.10.1" SYSLOGDEST="192.168.10.1:4444"  /usr/local/dbfw/bin/priv/configure-networking you can check the current status of the below command. [oracle@auditvault-testvm ~]$ rpm -qa | grep -i avs  [root@auditvault-testvm bin]# rpm -qa | grep -i avs avs-database-2-19.27.0.0.0-0.x86_64 avs-database-19.27.0.0.0-0.x86_64 avs-bootstrap-20.17.0.0.0-0_260303.0015.noarch bootstrap-avs-dependencies-20.17.0.0.0-0_260303.0015.noarch avs-dbsat-20.14.0.0.0-0_250520.0400.x86_64 bootstrap-avs-application-20.14.0.0.0-0_250520.0400.noarch avs-apex-20.14.0.0.0-0_2505...
Post a Comment
Read more

Implement Block Change Tracking in Oracle Database

What is Block Change Tracking? Block Change Tracking is an Oracle Database feature used with RMAN incremental backups. It tracks the physical locations of changed blocks in the database and stores this information in a separate file called the Block Change Tracking file. Oracle documentation states that this tracking information is maintained in a separate file and is used for tasks such as improving incremental backup performance. Without BCT, RMAN may need to scan the datafiles to determine which blocks have changed since the previous backup. With BCT enabled, RMAN can directly read the change tracking file and identify changed blocks more efficiently. ----- Login to SQL sqlplus / as sysdba            Set lin 400 SELECT status, filename, bytes FROM   v$block_change_tracking; CHECK OMF SHOW PARAMETER db_create_file_dest;  ENABLE BCT (BLOCK CHAIN TRACKING) Common method: ALTER DATABASE ENABLE BLOCK CHANGE TRACKING;  Add to a file path:...
Post a Comment
Read more

Warning: long redo log write elapsed times detected, the LG* process tracefiles have more details

Warning: long redo log write elapsed times detected, the LG* process tracefiles have more details This warning means LGWR / LGnn background processes are taking too long to write redo to the online redo logs. It is usually related to one of these: - Slow storage / high I/O latency on redo log disks - Redo logs placed on busy disks together with datafiles, FRA, archive logs, backups, or OS files - Too many commits from the application, causing frequent LGWR flushes - Redo log size too small, causing frequent log switches - CPU scheduling issue, where LGWR is not getting CPU quickly - Data Guard synchronous transport delay, if using SYNC/AFFIRM - In newer 19c RU versions, especially around 19.28, this warning can appear more visibly because of diagnostic changes, so first confirm whether there is a real performance impact before changing anything. - Oracle’s own wait-event documentation says log file sync is the foreground wait for redo write confirmation after commit, and log file paral...
Post a Comment
Read more

Test NETWORK interface using iperf3

 C:\iperf3.5_64>iperf3 -c 172.168.1.100 warning: Ignoring nonsense TCP MSS -13312 Connecting to host 172.168.1.100, port 5201 [  5] local 192.168.8.101 port 52570 connected to 172.168.1.100 port 5201 [ ID] Interval           Transfer     Bitrate [  5]   0.00-1.00   sec  6.88 MBytes  57.5 Mbits/sec [  5]   1.00-2.00   sec  3.50 MBytes  29.4 Mbits/sec [  5]   2.00-3.00   sec  4.00 MBytes  33.5 Mbits/sec [  5]   3.00-4.01   sec  6.25 MBytes  52.0 Mbits/sec [  5]   4.01-5.00   sec  4.75 MBytes  40.2 Mbits/sec [  5]   5.00-6.01   sec  5.50 MBytes  45.9 Mbits/sec [  5]   6.01-7.01   sec  5.88 MBytes  49.1 Mbits/sec [  5]   7.01-8.00   sec  5.25 MBytes  44....
Post a Comment
Read more

VPD Policy Implementation - ORACLE Database

VPD Policy Implementation - ORACLE Database  VPD policies Oracle CREATE TEST USERS in DB -- Owner schema for objects CREATE USER app_owner IDENTIFIED BY AppOwner#123 DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp QUOTA UNLIMITED ON users; GRANT CREATE SESSION, CREATE TABLE, CREATE PROCEDURE, CREATE ANY CONTEXT TO app_owner; -- Test application user CREATE USER app_user IDENTIFIED BY AppUser#123 DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp; GRANT CREATE SESSION TO app_user; CONNECT TO USER CONN app_owner/AppOwner#123  CREATE THE SAMPLE TABLE AND DATA CREATE TABLE employees (     emp_id         NUMBER PRIMARY KEY,     emp_name       VARCHAR2(100),     department_id  NUMBER,     salary         NUMBER ); INSERT TEST DATA   INSERT INTO employees VALUES (1, 'John',  10, 1000); INSERT INTO employees VALUES (2, 'Mary',  20, 1200); INSERT INTO empl...
Post a Comment
Read more