FCUBS Patchset Installation Frequently Asked Questions - Oracle FLEXCUBE Universal Banking
(Doc ID 2816950.1)
Last updated on JUNE 06, 2024
Applies to:
Oracle FLEXCUBE Universal Banking - Version 12.0 and laterInformation in this document applies to any platform.
Purpose
This document is created to provide the instant solutions to the issues faced at customer front. The main objective is to enable customers to self-patch frequently encountered minor issues during and after applying a patchset. This document provides help for dealing with frequently encountered minor issues and resolving them locally and quickly and saves time by provides instant solutions with experience and turnaround time of the issues will be reduced.
Questions and Answers
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Questions and Answers |
| 1. FCUBS Patchset Application FAQ |
| 1.1 Application Setup Related Queries |
| 1.1.1 What are the various FCUBS logs that can be used for troubleshooting of issues? |
| 1.1.2 Is it required to recreate all the property files as part of a patchset? |
| 1.1.3 How to apply Patchset? |
| 1.1.4 What is FLEXCUBE home with respect to patchsets and how to maintain it? |
| 1.1.5 If multiple patchsets are to be applied, what is the ideal approach to do it? |
| 1.1.6 Where can we see list of new/deprecated features introduced as part of a patchset? |
| 1.1.7 Is it required to apply the patchset in a non-production environment? |
| 1.1.8 When will FCUBS Patchset take long time to apply? |
| 1.1.9 How to package/retro customization changes done by third party for bank? |
| 1.1.10 How to identify / figure out possible impact on customizations due to PS release? |
| 1.1.11 How to deploy Patchset in multi products installation – FCUBS, OBLM, OBPM, OFCL, etc – do all products needs to be applied PS on same time to be on same version always? |
| 1.1.12 How to determine if patchsets of different product (same release version) are compatible with each other? |
| 1.1.13 How to consolidate screens for all function IDs from different products and multiple patchsets? |
| 1.1.14 If previous version of Patchset are being applied, installer utility to be used from that Patchset or any installer utility can work or installer utility should be from latest Patchset? |
| 1.2 Testing related queries |
| 1.2.1 How to simulate the issues resolved in a patchset? |
| 1.2.2 Are there any recommended test cases to be performed? |
| 1.2.3 Is there any regression testing done for the patchsets? |
| 1.3 Database/Application Server Queries |
| 1.3.1 Which logs must be checked in case of Patchset database compilation issue? |
| 1.3.2 Which logs must be checked in case of application EAR deployment failure? |
| 1.3.3 Which logs must be checked in case of application EAR starting issue? |
| 1.3.4 Which logs must be checked in case of application login issue? |
| 1.3.5 Which logs must be checked in case of application transaction/functional issue? |
| 1.3.6 Is there any rollback mechanism in case there are issues faced after deployment in production? What are the possible rollback options? |
| 1.3.7 How do we find out compatibility matrix of each PS – which Database/Middleware version it is compatible with? |
| 1.3.8 Should Database jobs be stopped and restarted as part of the patchset? |
| 1.3.9 Is it required to stop and start application server during a patchset application? |
| 1.3.10 Is it required to stop and start FLEXCUBE scheduler jobs? |