Setting up Database Oracle FLEXCUBE Universal Banking

Version 12.0 [May] [2012]

Table of Contents
1. SETTING UP DATABASE ............................................................................................................................ 1-1
1.1 INTRODUCTION ........................................................................................................................................... 1-1
1.2 PREREQUISITES ........................................................................................................................................... 1-1
1.3 PRE-INSTALLATION TASKS ......................................................................................................................... 1-1
1.3.1 Purpose .............................................................................................................................................. 1-1
1.3.2 Setting up Database for Oracle FLEXCUBE..................................................................................... 1-1 1.4
BEFORE GETTING STARTED ........................................................................................................................ 1-5
1.5 INSTALLER SWITCHES ................................................................................................................................ 1-6
2. INSTALLING ORACLE FLEXCUBE DATABASE ................................................................................... 2-7
2.1 INTRODUCTION ........................................................................................................................................... 2-7
2.2 CREATING SCHEMA BY IMPORTING FULL DUMP ........................................................................................ 2-7
2.3 CREATING SCHEMA FROM SHIPMENT MEDIA ............................................................................................. 2-7
2.3.1 Loading from Shipment Media........................................................................................................... 2-8
2.3.2 Custom Installation .......................................................................................................................... 2-10
2.4 LOADING DATA ........................................................................................................................................ 2-21
2.4.1 Import Database Installation ........................................................................................................... 2-31
2.4.2 Template Database Installation ....................................................................................................... 2-37
3. SETTING UP FGL DATABASE ................................................................................................................... 3-1
3.1 INTRODUCTION ........................................................................................................................................... 3-1
3.2 CREATING FGL SCHEMA BY IMPORTING FULL DUMP ................................................................................ 3-1
3.3 CREATING FGL SCHEMA FROM SHIPMENT MEDIA ...................................................................................... 3-1
3.3.2 Custom Installation ............................................................................................................................ 3-3
3.4 LOADING DATA ........................................................................................................................................ 3-13
3.4.1 Import Database Installation ........................................................................................................... 3-23
3.4.2 Template Database Installation ....................................................................................................... 3-29
4. SETTING UP ELCM DATABASE ................................................................................................................ 4-1
4.1 INTRODUCTION ........................................................................................................................................... 4-1
4.2 CREATING ELCM SCHEMA BY IMPORTING FULL DUMP ............................................................................. 4-1
4.3 CREATING ELCM SCHEMA FROM SHIPMENT MEDIA .................................................................................. 4-1
4.3.2 Custom Installation ............................................................................................................................ 4-3
4.4 LOADING DATA ........................................................................................................................................ 4-13
4.4.1 Import Database Installation ........................................................................................................... 4-23
4.4.2 Template Database Installation ....................................................................................................... 4-29
1-1
1. Setting up Database
1.1 Introduction
This document explains the steps to install the Host and Branch database. These steps include
Load objects, Import Dump, Basic Setup, and Clone Database.

This tool automates the creation of the database. The database created using this tool will have
the database objects that are available in the shipment media.

1.2 Prerequisites
Following are the prerequisites for installing decentralize branch database:

Prerequisite Description

Operating System Windows 2000/XP, UNIX

Software You will require the following software:

1. JDK1.6 or later version (Update 17 or higher for JDK1.6)
2. Oracle 11g Client or later version (Refer the release
certificate)
Note the following:
• Ensure that Oracle FLEXCUBE Schema (Branch) and database connectivity details are as
per the standards.
• Make sure that Oracle FLEXCUBE Schema and database connectivity exist as per the
norms in ‘TNSNAMES.ORA’ file of Oracle 11g Client or later versions.
• During the setup, service/DB jobs should not be running in the schema. If some services
are still running in the schema, use 'exec dbms_job.remove('||job||');' from user_jobs.

1.3 Pre-Installation Tasks

1.3.1 Purpose
To guide DBA to setup the database for Oracle FLEXCUBE and to do the routine DBA basic
activities for the following DB version:
DB version Refer Release Certificate

Oracle FLEXCUBE Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit
version Production
1.3.2 Setting up Database for Oracle FLEXCUBE
This section guides you through the steps to setup database for Oracle FLEXCUBE.

1-1
1.3.2.1 Environment Setup Phase

Following are the main Kernel and database initialization parameters that you need to setup as
part of the environment.
Sun Solaris Kernel Parameters

Kernel Suggested Starting Value Description

Parameter

SHMMAX 4294967295 Maximum size of a single shared memory

segment
or
70% of physical memory
(whichever is larger)

SHMMIN 1 Minimum size of a single shared memory

segment

SHMMNI 100 Maximum number of shared memory

segments in entire system

SHMSEG 10 Maximum number of shared memory

segments one process can attach

SEMMNS 2000 Maximum number of semaphores in entire

system

SEMMSL 1000 Maximum number of semaphores per set

SEMMNI 100 Maximum number of semaphore sets in

entire system

Swap Space Twice the physical memory present

Patches Verify as per Oracle’s platform specific release notes

IBM AIX Kernel Parameters

Unlike other UNIX platforms, AIX does not have the ability to directly configure Kernel
parameters. Instead, the AIX Kernel dynamically allocates and reallocates resources as they are
needed, up to a predefined limit, making the traditional practice of tuning parameters
unnecessary. The only tuneable Kernel parameter is ‘maxuprc’ (maximum number of processes
per user ID) which can be modified via SMIT (AIX's menu-based system administration utility) or
the command line utility.
Swap Space Twice the Physical memory present

Patches Verify as per Oracle’s platform specific release notes

HP UNIX Kernel Parameters

Kernel Suggested Starting Description

Parameter Value

aio_max_ops 2048 Maximum number of queued AIO ops

1-2
 Kernel Suggested Starting Description
Parameter Value

dbc_min_pct 2 Minimum percentage of system memory used

for buffer cache

dbc_max_pct ensure <= 128MB Maximum percentage of system memory used

for buffer cache

Fsasync 0 Asynchronous i/o on file systems

max_async_ports 1024 Maximum ports for asynchronous I/O

operations

maxdsiz64 1Gb Shadow process' heap size

Maxfiles 512 Soft limit number of open files per process

maxfiles_limit 1024 Hard limit number of open files per process

Maxusers no of Oracle Influences nproc, nfile, ninode and maxuprc

connections+64

Maxuprc maxusers*5 Number of processes per user ID

nfile use SAM formula Open files system wide

Nflocks >= (200 + (sum of db files File locks system wide

))

Nproc use SAM formula Processes system wide

Shmmax 4294967295 Maximum size of a single shared memory

segment

Swap Space Twice the physical memory present

Patches Verify as per Oracle’s platform specific release notes

1.3.2.2 Database Setup

This section contains the following details:

• Create database using Oracle DBCA utility with (jvm and xdb options)
• Create Oracle FLEXCUBE schema
• Storage for Oracle FLEXCUBE schema
TABLESPACES Storage Table Space Table Extent Extent Segment
Name Space Size Allocation Space
%
Type (KB) Type Management
FCC Data 60% FCCDATASML DATA UNIFORM AUTO
128
15% or 4 GB
1024

1-3
 TABLESPACES Storage Table Space Table Extent Extent Segment
Name Space Size Allocation Space
%
Type (KB) Type Management
FCCDATAMED 5120
25% or 20 GB
FCCDATALAR
60%
FCC Index 40% FCCINDXSML INDEX 128 UNIFORM AUTO
15% or 4 GB 512
FCCINDXMED 5120
25% or 20 GB
FCCINDXLAR
60%
System 5 GB SYSTEM SYSTEM
Not Not
applicable applicable
Temporary 5 GB TEMP TEMP 1024
Not Not
applicable applicable
Undo 5 GB UNDO UNDO
Not Not
applicable applicable
Note: The storage parameters for FCC Data and FCC Index table spaces are provided as
percentage. The exact sizing for these table spaces need to be worked out based on the sizing of
Oracle FLEXCUBE, which is a factor of volumes at the bank.
For the parameters to be set at the database level for Oracle FLEXCUBE, refer to the excel sheet
‘Initparameters_to_change.xls’.
Granting Rights to Oracle FLEXCUBE Schema

You need to disable the password case sensitivity and grant rights to the schema. While doing
this, ensure that you are connected to the database as ‘sys’ user.

Before granting rights to the schema, you need to execute the following command:

ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;

Note: The above command should be executed if the database is Oracle 11G and the application
server is Oracle SOA Suite. This command disables the case sensitivity of the schema password.

Further, execute the following script to grant rights to the schema. This should also be executed
while connected as “sys” user to the database.

Refer ‘grants_dbms.sql’ file.

Listener and Tnsentries Setup

Create the Listener and Tnsentries using Oracle net manager utility.
Invalid Objects and Recompile

Find all the invalid objects and recompile the invalid units using the following syntax.

1-4
 exec utl_recomp.recomp_parallel(4, ‘FCUBS_SCHEMA) Database
Statistics Gathering

The script for gathering database statistics creates two jobs. Once job gathers the
DICTIONARY_STATS of the instance and the other job gathers the Oracle FLEXCUBE schema
stats. The script is given below:

Refer ‘StatsJobs.sql’ file.

1.3.2.3 Environment Monitoring Procedures

Once Oracle FLEXCUBE database is created and being used, a set of regular monitoring steps
should be carried out by the DBA. This section outlines a set of such daily, weekly and monthly
tasks.
Daily Procedures

Following are the daily tasks:

• Verify whether all instances are up: Check whether the database instance status is up
and running.
• Review alert log: Check Oracle FLEXCUBE instance alert log file of for error messages.
• Verify the success of backup: Check whether the backup taken by using database
utility is successful.
• Verify free space in table spaces: Check whether there is enough free space to handle
the day’s expected growth in each table space.
• Review contention for CPU, memory, network or disk resources: Use OS related tool
to get report on above statistics and analyze the details.
Weekly Procedures

Following are the weekly tasks:

• Table space violations: All indexes should lay on the appropriate index table spaces as
specified at the design stage. If there are invalid indexes, those should be rebuilt to the
index tablespace.
• Security violations: Review the client and server side network and the audit logs to for
security violations.
• Cleanup actions: The log files of the database instance such as the alert logs, trace files
and listener logs should be cleared on a weekly basis. If required, these can be archived
prior to cleanup.

1.4 Before Getting Started

Before going to the next step, you need to run the command given below:

Go to Start > Run on your system and enter the command given below and press Enter key:

Sqlplus (schema_name)/(password)@(connect_string)

Example
Suppose that you are connecting to a schema FCUBS (schema_name). The password is FCUBS and
connect string is FCUBS.WORLD (Connect_string ). In that case, you need to run the following command:

1-5
 Sqlplus FCUBS/[email protected]

Ensure that you are able to connect to the schema without errors. Also, check the SQL* Plus
version is 10.2.0.0 or above.

1.5 Installer Switches

The installer switch is required in case of RMAN/TEMPLET based DB installations. The
installation steps are maintained depending on the tag of FCUBS-ENV-CHECK.xml. This is
available under the folder ‘<INSTALLER_PATH>/InstallOptions/Database/Config’.

<ENVIRONMENT>

<INSTOPT>VER</INSTOPT>

</ENVIRONMENT>

Based on the following tag values, the installer will navigate to different screens:
1. DEV: For Development, a folder based database creation.

2. VER: For shipment media, a restoration of the database provided by DBA’s and
customization of the modules according to customer’s requirements. Take a backup after the
customization. The files are then ready to be shipped to the customer.
3. TMP: For Template, the concept remains the same as it was in the previous release of our
Installer.
Note: In case of template based DB setup, the tag value of DBCA_TEMPLATE in folder
‘<INSTALLER_PATH>/InstallOptions/Database/Config/FCUBS-ENV-CHECK.xml’ should be
the name of the template given by DBA team.
<DBCA_TEMPLATE>FCUBS_ModelBank</DBCA_TEMPLATE>
4. PRD: For Customers, the RMAN backup is bundled in the installer. This will restore the
database at customer site.

1-6
 2. Installing Oracle FLEXCUBE Database
2.1 Introduction
Oracle FLEXCUBE database can be installed in one of the following methods.
• Import full dump – Import the Oracle FLEXCUBE objects into an empty schema using full
dump. This is a manual activity.
• From Shipment Media – Load the Shipment Mediaobjects into an empty schema using
Installer.
• Clone database or template based setup – Clone the database using Installer.

These methods are discussed in detail under the following heads.

2.2 Creating Schema by Importing Full Dump

Under this method, you need to manually import the Oracle FLEXCUBE DMP file into the Oracle
FLEXCUBE schema. This can be done using the following command.

$ imp user_name/password file = dmp_file_name.dmp full = Y commit = Y log = imp.log

compile=n
Post Import Activities

Once the DMP file is imported, you need to carry out the following activities:
 Enabled all triggers by running the procedure ‘pr_instlr_post_import.prc’ located under
the folder ‘InstallOptions\Database\Common’  Update STTM_BANK with
auto_gen_cif='N'  Update the following tables:
 actb_daily_log
 bktb_schema_defaults
 dstb_maint, ictb_acc_action
 ictb_action_log, ictb_resolution_error
 lmtb_offline_nodes, lmtb_offline_utils
 mstb_current_msg_ind_out
 mstb_dly_msg_in
 mstb_dly_msg_out
 mstm_mcs
 mstm_undo
 sttm_branch_node
 sttm_branch
 sttm_customer

Set node as the connection string for the above tables.

2.3 Creating Schema from Shipment Media

Under this method, you need to create the schema from the Shipment Media.

2-7
2.3.1 Loading from Shipment Media
You have an option of loading both host and branch objects together. Database installation
includes the provision of details of the schema to connect and the location of the source objects.
The objects of the selected modules are compiled as explained below.
Source input for installer for DB setup

Copy the folder ‘MAIN’ from the shipment media to a folder in the local system.

Eg: D:\source\MAIN

Further, copy the folder ‘ELCM’ from the shipment media to a folder in the local system.

Eg: D:\source\ELCM

The folder to which you have copied the sources can be the source to the Installer.

Note: After copying all the sources from shipment media to a folder in the local system, ensure
that the folder containing those has full rights for that user.

It is not mandatory to copy the sources to local system. You may also directly refer the Installer to
the shipment media.

2.3.1.1 Loading Objects from Shipment Media

The steps to load objects from the Shipment Media are given below:
1. Launch Oracle FLEXCUBE Universal Banking Solution Installer.

2. Choose ‘Universal Banking Solution’. Click ‘Next’.

The following screen is displayed:

2-8
3. Choose ‘Database Setup’.
4. Specify the following details:

Operating System and Version

Specify the operating system in which you are installing Oracle FLEXCUBE.

You also need to specify the version of the operating system.

Application Server and Version

Specify the application server on which you are installing Oracle FLEXCUBE. You also need to
specify the version of the application server. Database Server and Version

Specify the database server on which you are installing Oracle FLEXCUBE. You also need to
specify the version of the database server.

5. Once you have specified the above details, click ‘Next’. The following screen is displayed:

2-9
 As you see on this screen, you can install Oracle FLEXCUBE in two methods:
• Custom Installation
• Template Installation
6. Select the appropriate installation method and click ‘Next’.

Template installation is performed through Oracle DBCA tool.

2.3.2 Custom Installation

The Oracle FLEXCUBE Universal Solutions installer supports custom installation of Oracle
FLEXCUBE in two methods:
• Compile objects and load static data into the database
• Load objects and data by importing data and objects from the import file
1. Select the installation type ‘Custom Installation’.

2-10
2. Select ‘Compile Objects’ under ‘Custom Installation’ and click ‘Next’. The following screen is
displayed.

3. Specify the following details:

Source Directory

Specify the source directory location. The source directory should have the ‘MAIN’ folder and the
contents. Use the directory icon to browse the source directory.

2-11
Destination Directory

Specify the destination directory. Use the directory icon to browse the source directory.

This is optional. If you do not specify the destination directory, on clicking ‘Next’, the Installer
displays a message ‘Sources will be compiled from source directory’. If you want to proceed, click
‘Yes’. The files will be taken directly from source directory for compilation. If you click ‘No’, you
need to specify the destination directory.
Multiple Sources

In case of Cluster and Patch installations, you can install the files from multiple source directories.
Check this box to use multiple directories.

If you check ‘Multiple Sources’, on clicking ‘Next’, the following screen is displayed.

Here, you need to specify the different source directories. Use the directory icon to browse the
source directory.

If you do not check the box ‘Multiple Sources’, you will be directly navigated to the module
selection screen.
4. Once you have specified the details, click ‘Next’. The following screen is displayed.

2-12
5. Select the modules to be included. In case you need to include all the modules, check the
box ‘Select All’.
6. Click ‘Next’ to start database objects source copy.

7. The Installer will copy the source files from the source directory to the destination directory.
The files are taken from this location for compilation.
8. You can view the status of the copy process on a separate window.

2-13
9. Once the copy process is completed, the Installer navigates you to the following screen.

10. Specify the following schema details:

User Name

Specify the user name to access the schema.

Password

Enter the schema password.

Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed.

2-14
Port

Specify the port number.

11. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

12. After testing the connection, click ‘Next’. The following screen is displayed.

13. This screen displays the parameter details of the database. This is for information purpose.
14. Click ‘Next’. The following screen is displayed.

2-15
15. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

16. If you click ‘Generate Report’ button, in the ‘Logs’ folder, the installer creates an SQL file
‘grantScript.sql’ containing the script for granting the privileges. You can use this file to get
the access. The following screen is displayed.

17. You can select the objects to be dropped and click ‘Drop’ button to drop the selected objects.
As you drop the objects, the count in this screen is updated.

18. Click ‘Drop Log’ button to view the drop log.

Note: The details of the drop process are logged in a file ‘Drop_All.log’ in the folder <Destination
Folder>/DBLogs.
19. If all the objects do not get dropped at the first time, you can drop them again.

20. Click ‘Next’ button, the following screen is displayed.

2-16
21. The table, sequences and type objects are compiled and the count is updated.
22. You can verify the DDL objects compilation by comparing the current count and the release
count.

23. Click ‘DDL Log’ button to view the DDL logs. The log file ‘LoadDDL.log’ will be available in the
destination directory under the folder ‘DBLogs’.

24. Click ‘Missing DDL List’ button to view the list of DDL files that are available in the source
directory, but not in the schema. The list ‘FilesNotCompiled_DDLObj.txt’ will be available in
the destination directory under the folder ‘DBLogs’.

25. Click ‘Next’. The following screen is displayed.

2-17
26. Specify the following details:

Include Scheduler DDLs

Check this box to include scheduler DDLs. If you do not need to include the scheduler DDLs,
leave this field unchecked.
Scheduler DDL Source Path

Specify the location of the ‘tables_oracle.sql’ folder, which is available in extracted ‘quartz.jar’.

Note: You first need to download the file ‘quartz.jar’ and extract this to the local machine. You
need to specify the location of the ‘dbTables’ folder.
27. Click ‘Load Scheduler DDLs’ to compile the files.

28. Click ‘Next’. The following screen is displayed.

2-18
29. Check the objects that you need to load.

30. Click ‘Load Objects’ button. The installer loads the functions, procedures, views, triggers and
packages as per your selection and compiles them.

Note: You can verify the application objects compilation by comparing the count shown in this
screen with the release count.
31. Click ‘Objects Log’ button to view the log. The log file ‘LoadAppObj.log’ will be available in the
destination directory under the folder ‘DBLogs’.

32. Click ‘Missing Object List’ button to view the list of application object files that are available in
the source directory but not in the schema. You can view this list in the file
‘FilesNotCompiled_APPObj.txt’ available in the destination directory under the folder
‘DBLogs’.
33. The installer loads the DDL and application objects of the selected modules.
34. You can view the list of invalid objects in the following screen.

2-19
35. Click ‘Invalid List’ button to view the count of invalid objects. The installer creates the file
‘InvalidList.txt’ in the destination directory under the folder ‘DBLogs’.

36. You can use the ‘Recompile’ button to do a cyclic recompilation. This will reduce the invalid
objects count.

37. You can view the recompile logs by clicking ‘Log’ button. The installer creates a file
‘recompile.log’ in the destination directory under the folder ‘DBLogs’.

38. Click ‘Next’. The following screen is displayed. This starts the ELCM POJO installation
process.

2-20
 39. Specify the following details:

Oracle Java Home Path

Specify the Oracle Java home location. This is required for ELCM POJO compilation.
You can validate the Oracle Java home path by clicking ‘Validate’ button.

40. Click ‘Next’. The following screen is displayed.

41. This screen displays the status of ELCM JAR file creation. The following JAR files are created
for ELCM POJO.
• ELCMDAO.jar
• ELCMDTO.jar
• ELCMProcess.jar
• ELCMUtility.jar
42. Click ‘Load Objects’ button to load the JAR files to the database.

2.4 Loading Data

Once the objects are loaded, you need to insert data into the tables.

This section explains the steps to load static data into the database and the basic setup to be
done.

Follow the steps given below:

1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

2-21
2. Select ‘Load Static Data’ and click ‘Next’. The following screen is displayed.

3. Specify the following details:

Source Directory

Specify the source directory location. The source directory should have the ‘MAIN’ folder and the
contents. Use the directory icon to browse the source directory. Destination Directory

Specify the destination directory. Use the directory icon to browse the source directory.

2-22
This is optional. If you do not specify the destination directory, on clicking ‘Next’, the Installer
displays a message ‘Sources will be compiled from source directory’. If you want to proceed, click
‘Yes’. The files will be taken directly from source directory for compilation. If you click ‘No’, you
need to specify the destination directory.
Multiple Sources

In case of Cluster and Patch installations, you can install the files from multiple source directories.
Check this box to use multiple directories.

If you check ‘Multiple Sources’, on clicking ‘Next’, the following screen is displayed.

Here, you need to specify the different source directories. Use the directory icon to browse the
source directory.

If you do not check the box ‘Multiple Sources’, you will be directly navigated to the module
selection screen.
4. Click ‘Next’ to start objects copy.

2-23
5. The Installer will copy the source files from the source directory to the destination directory.
The files are taken from this location for compilation.
6. Once the copy process is completed, the Installer navigates you to the following screen.

7. Specify the following schema details:

User Name

Specify the user name to access the schema.

Password

2-24
Enter the schema password.
Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed.
Port

Specify the port number.

8. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

9. After testing the connection, click ‘Next’. The following screen is displayed.

10. This screen displays the parameter details of the database. This is for information purpose.
11. Click ‘Next’. The following screen is displayed.

2-25
12. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

13. Click ‘Next’. The following screen is displayed.

14. Specify the following details:

2-26
Branch Plug-in

Check this box to include branch plug-in. If you check this box, you need to specify the
deployment mode in the field ‘Branch DB Centralized’. If you do not need branch plug-in, leave
this field unchecked.
Branch DB Centralized?

Specify the deployment mode. You can choose one of the following modes:
• Centralized
• Decentralized
• Hybrid

Once you have specified the above details, click ‘Next’.

15. The installer executes the procedures required before beginning static data compilation. All
the triggers will be disabled during this process.
16. One the process is completed, you will see the following screen.

2-27
17. You can view the static data log by clicking ‘Static Data Log’ button.
18. Click ‘Next’. The following screen is displayed.

19. Here, you can do the basic maintenances for the table ‘CSTB_PARAM’.

20. Click ‘Next’. The following screen is displayed.

2-28
21. Here you can do the basic maintenances for the tables ‘STTM_BANK’ and ‘STTM_BRANCH’.
22. Click ‘Next’. The following screen is displayed.

23. Here, you can do the basic maintenances for the table ‘STTM_DATES’.

24. Click ‘Next’. The following screen is displayed.

2-29
25. Here, you can do the basic maintenances for the table ‘CYTM_CCY_DEFN’.

26. Click ‘Next’. The following screen is displayed.

27. Here you can do the basic maintenances for the table ‘SMTB_USER’ and
‘SMTB_USER_ROLE’.

28. Click ‘Next’. The following screen is displayed.

2-30
 29. Click ‘Start Setup’ button to compile the entries.
30. This completes the static maintenance and basic setup process.

2.4.1 Import Database Installation

This section describes the process of Import DB installation.
1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

2. Select ‘Import Data’ and click ‘Next’. The following screen is displayed.

2-31
3. Specify the following schema details:

User Name

Specify the user name to access the schema. Password

Enter the schema password.

Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed. Port

Specify the port number.

4. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

5. After testing the connection, click ‘Next’. The following screen is displayed.

2-32
6. This screen displays the parameter details of the database. This is for information purpose.

7. Click ‘Next’. The following screen is displayed.

8. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

9. Click ‘Next’. The following screen is displayed.

2-33
10. Specify the following details:

Include PAR File

Check this box to include the PAR file. If you check this box, you need to specify the PAR file
name.
PAR File Name

If you have checked the box ‘Include PAR File’, you need to specify the PAR file name here.
11. Once you have specified the above details, click ‘Next’ button.

2-34
12. Click ‘Import’ button to import the database with the PAR file parameters.

13. If you have not checked the box ‘Include PAR File’, on clicking ‘Next’, you will be navigated
to the following screen.

14. Specify the Oracle directory name. This is the directory in the server machine where the
import file is located.

15. Click ‘Next’. The following screen is displayed.

16. Specify the following details:

Dump File Name

2-35
Specify the import file name.
Export Schema Name

Specify the export schema name from which the import file is imported.
Export Schema Tablespace

Specify the export schema tablespace from which the import file is imported.
17. Once you have specified the above details, click ‘Next’. The following screen is displayed.

18. Specify the following details:

Import Schema Name

Specify the import schema name to which the import file is loaded.
Import Schema Tablespace

Specify the import schema tablespace to which the import file is loaded.
19. Once you have specified the above details, click ‘Next’ button. The following screen is
displayed.

2-36
 20. This triggers the import operation. You can optionally import the objects, data or full set by
using ‘Import Objects’, ‘Import Data’ or ‘Full Import’ buttons respectively.

2.4.2 Template Database Installation

This section describes the process of template database installation.
1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

2. Select ‘Template Installation’ and click ‘Next’. The following screen is displayed.

3. Specify the following details:

2-37
Source File

Specify the location of the source file. You can use the directory icon to browse to the appropriate
file location.
Destination Directory

Specify the destination. You can use the directory icon to browse to the appropriate file location.
Template Type

Specify the template type. You can choose one of the following destination types.
• PDATA
• MDATA
4. Once you have specified the above details, click ‘Next’. The following screen is displayed.

5. Specify the following details:

DB Unique name

Specify a unique name of the database.

SID

Specify the SID of the database.

6. Once you have specified the above details, click ‘Next’ button. The following screen is
displayed.

2-38
7. Specify the following details:

Oracle Database Home

Specify the Oracle database home directory. You can use the ‘Browse’ button to browse and
select the appropriate directory.
Copy FCUBS Database Template

Check this box to use the existing FCUBS template.

Auto Launch Oracle DBCA

Check this box to launch the Oracle DBCA tool. If you check this button and click next, the
installer will start Oracle DBCA tool, from which you can proceed with the database installation.

2-39
 3. Setting up FGL Database
3.1 Introduction
This chapter explains the steps to set up database for FGL.

3.2 Creating FGL Schema by Importing Full Dump

You can create the FGL schema by way of a full dump import. This is a manual activity. For
details, refer to the section ‘Creating Schema by Importing Full Dump’. You may follow the same
steps for FGL database setup.

3.3 Creating FGL Schema from Shipment media

You can create the FGL schema by loading the objects from the shipment media itself. The
method is described under the following headings.

3.3.1.1 Loading Objects from Shipment Media

The steps to load objects from the Shipment Media are given below:
1. Launch Oracle FLEXCUBE Universal Banking Solution Installer.

2. Choose ‘General Ledger’. Click ‘Next’.

The following screen is displayed:

3-1
3. Choose ‘Database Setup’.
4. Specify the following details:

Operating System and Version

Specify the operating system in which you are installing Oracle FLEXCUBE.

You also need to specify the version of the operating system.

Application Server and Version

Specify the application server on which you are installing Oracle FLEXCUBE. You also need to
specify the version of the application server. Database Server and Version

Specify the database server on which you are installing Oracle FLEXCUBE. You also need to
specify the version of the database server.

5. Once you have specified the above details, click ‘Next’. The following screen is displayed:

3-2
 As you see on this screen, you can install Oracle FGL in two methods:
• Custom Installation
• Template Installation
6. Select the appropriate installation method and click ‘Next’.

Template installation is performed through Oracle DBCA tool.

3.3.2 Custom Installation

The Oracle FLEXCUBE Universal Solutions installer supports custom installation of Oracle
FLEXCUBE in two methods:
• Compile objects and load static data into the database
• Load objects and data by importing data and objects from the import file
1. Select the installation type ‘Custom Installation’.

3-3
2. Select ‘Compile Objects’ under ‘Custom Installation’ and click ‘Next’. The following screen is
displayed.

3. Specify the following details:

Source Directory

Specify the source directory location. The source directory should have the ‘MAIN’ folder and the
contents. Use the directory icon to browse the source directory.

3-4
Destination Directory

Specify the destination directory. Use the directory icon to browse the source directory.

This is optional. If you do not specify the destination directory, on clicking ‘Next’, the Installer
displays a message ‘Sources will be compiled from source directory’. If you want to proceed, click
‘Yes’. The files will be taken directly from source directory for compilation. If you click ‘No’, you
need to specify the destination directory.
Multiple Sources

In case of Cluster and Patch installations, you can install the files from multiple source directories.
Check this box to use multiple directories.

If you check ‘Multiple Sources’, on clicking ‘Next’, the following screen is displayed.

Here, you need to specify the different source directories. Use the directory icon to browse the
source directory.

If you do not check the box ‘Multiple Sources’, you will be directly navigated to the module
selection screen.
4. Once you have specified the details, click ‘Next’. The following screen is displayed.

3-5
5. The Installer will copy the source files from the source directory to the destination directory.
The files are taken from this location for compilation.
6. You can view the status of the copy process on a separate window.

7. Once the copy process is completed, the Installer navigates you to the following screen.

3-6
8. Specify the following schema details:

User Name

Specify the user name to access the schema. Password

Enter the schema password.

Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed. Port

Specify the port number.

9. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

10. After testing the connection, click ‘Next’. The following screen is displayed.

3-7
11. This screen displays the parameter details of the database. This is for information purpose.

12. Click ‘Next’. The following screen is displayed.

13. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

14. If you click ‘Generate Report’ button, in the ‘Logs’ folder, the installer creates an SQL file
‘grantScript.sql’ containing the script for granting the privileges. You can use this file to get the
access. The following screen is displayed.

3-8
15. You can select the objects to be dropped and click ‘Drop’ button to drop the selected objects.
As you drop the objects, the count in this screen is updated.

16. Click ‘Drop Log’ button to view the drop log.

Note: The details of the drop process are logged in a file ‘Drop_All.log’ in the folder <Destination
Folder>/DBLogs.
17. If all the objects do not get dropped at the first time, you can drop them again.

18. Click ‘Next’ button, the following screen is displayed.

3-9
19. The table, sequences and type objects are compiled and the count is updated.
20. You can verify the DDL objects compilation by comparing the current count and the release
count.

21. Click ‘DDL Log’ button to view the DDL logs. The log file ‘LoadDDL.log’ will be available in the
destination directory under the folder ‘DBLogs’.

22. Click ‘Missing DDL List’ button to view the list of DDL files that are available in the source
directory, but not in the schema. The list ‘FilesNotCompiled_DDLObj.txt’ will be available in
the destination directory under the folder ‘DBLogs’.

23. Click ‘Next’. The following screen is displayed.

24. Specify the following details:

Include Scheduler DDLs

Check this box to include scheduler DDLs. If you do not need to include the scheduler DDLs,
leave this field unchecked.
Scheduler DDL Source Path

Specify the location of the ‘tables_oracle.sql’ folder, which is available in extracted ‘quartz.jar’.
Note: You first need to download the file ‘quartz.jar’ and extract this to the local machine. You
need to specify the location of the ‘dbTables’ folder.
25. Click ‘Load Scheduler DDLs’ to compile the files.

26. Click ‘Next’. The following screen is displayed.

3-10
27. Check the objects that you need to load.

28. Click ‘Load Objects’ button. The installer loads the functions, procedures, views, triggers and
packages as per your selection and compiles them.

Note: You can verify the application objects compilation by comparing the count shown in this
screen with the release count.
29. Click ‘Objects Log’ button to view the log. The log file ‘LoadAppObj.log’ will be available in the
destination directory under the folder ‘DBLogs’.

30. Click ‘Missing Object List’ button to view the list of application object files that are available in
the source directory but not in the schema. You can view this list in the file
‘FilesNotCompiled_APPObj.txt’ available in the destination directory under the folder
‘DBLogs’.
31. The installer loads the DDL and application objects of the selected modules.
32. You can view the list of invalid objects in the following screen.

3-11
33. Click ‘Invalid List’ button to view the count of invalid objects. The installer creates the file
‘InvalidList.txt’ in the destination directory under the folder ‘DBLogs’.

34. You can use the ‘Recompile’ button to do a cyclic recompilation. This will reduce the invalid
objects count.

35. You can view the recompile logs by clicking ‘Log’ button. The installer creates a file
‘recompile.log’ in the destination directory under the folder ‘DBLogs’.

36. Click ‘Next’. The following screen is displayed. This starts the ELCM POJO installation
process.

3-12
 37. Specify the following details:

Oracle Java Home Path

Specify the Oracle Java home location. This is required for ELCM POJO compilation.
You can validate the Oracle Java home path by clicking ‘Validate’ button.

38. Click ‘Next’. The following screen is displayed.

39. This screen displays the status of ELCM JAR file creation. The following JAR files are created
for ELCM POJO.
• ELCMDAO.jar
• ELCMDTO.jar
• ELCMProcess.jar
• ELCMUtility.jar
40. Click ‘Load Objects’ button to load the JAR files to the database.

3.4 Loading Data

Once the objects are loaded, you need to insert data into the tables.

This section explains the steps to load static data into the database and the basic setup to be
done.

Follow the steps given below:

1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

3-13
2. Select ‘Load Static Data’ and click ‘Next’. The following screen is displayed.

3. Specify the following details:

Source Directory

Specify the source directory location. The source directory should have the ‘MAIN’ folder and the
contents. Use the directory icon to browse the source directory. Destination Directory

Specify the destination directory. Use the directory icon to browse the source directory.

3-14
This is optional. If you do not specify the destination directory, on clicking ‘Next’, the Installer
displays a message ‘Sources will be compiled from source directory’. If you want to proceed, click
‘Yes’. The files will be taken directly from source directory for compilation. If you click ‘No’, you
need to specify the destination directory.
Multiple Sources

In case of Cluster and Patch installations, you can install the files from multiple source directories.
Check this box to use multiple directories.

If you check ‘Multiple Sources’, on clicking ‘Next’, the following screen is displayed.

Here, you need to specify the different source directories. Use the directory icon to browse the
source directory.

If you do not check the box ‘Multiple Sources’, you will be directly navigated to the module
selection screen.
4. Click ‘Next’ to start objects copy.

3-15
5. The Installer will copy the source files from the source directory to the destination directory.
The files are taken from this location for compilation.
6. Once the copy process is completed, the Installer navigates you to the following screen.

7. Specify the following schema details:

User Name

Specify the user name to access the schema.

Password

3-16
Enter the schema password.
Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed.
Port

Specify the port number.

8. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

9. After testing the connection, click ‘Next’. The following screen is displayed.

10. This screen displays the parameter details of the database. This is for information purpose.

11. Click ‘Next’. The following screen is displayed.

3-17
12. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

13. Click ‘Next’. The following screen is displayed.

14. Specify the following details:

3-18
Branch Plug-in

Check this box to include branch plug-in. If you check this box, you need to specify the
deployment mode in the field ‘Branch DB Centralized’. If you do not need branch plug-in, leave
this field unchecked.
Branch DB Centralized?

Specify the deployment mode. You can choose one of the following modes:
• Centralized
• Decentralized
• Hybrid

Once you have specified the above details, click ‘Next’.

15. The installer executes the procedures required before beginning static data compilation. All
the triggers will be disabled during this process.
16. One the process is completed, you will see the following screen.

3-19
17. You can view the static data log by clicking ‘Static Data Log’ button.

18. Click ‘Next’. The following screen is displayed.

19. Here, you can do the basic maintenances for the table ‘CSTB_PARAM’.

20. Click ‘Next’. The following screen is displayed.

3-20
21. Here you can do the basic maintenances for the tables ‘STTM_BANK’ and ‘STTM_BRANCH’.

22. Click ‘Next’. The following screen is displayed.

23. Here, you can do the basic maintenances for the table ‘STTM_DATES’.

24. Click ‘Next’. The following screen is displayed.

3-21
25. Here, you can do the basic maintenances for the table ‘CYTM_CCY_DEFN’.

26. Click ‘Next’. The following screen is displayed.

27. Here you can do the basic maintenances for the table ‘SMTB_USER’ and
‘SMTB_USER_ROLE’.

28. Click ‘Next’. The following screen is displayed.

3-22
 29. Click ‘Start Setup’ button to compile the entries.
30. This completes the static maintenance and basic setup process.

3.4.1 Import Database Installation

This section describes the process of Import DB installation.
1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

2. Select ‘Import Data’ and click ‘Next’. The following screen is displayed.

3-23
3. Specify the following schema details:

User Name

Specify the user name to access the schema. Password

Enter the schema password.

Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed. Port

Specify the port number.

4. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

5. After testing the connection, click ‘Next’. The following screen is displayed.

3-24
6. This screen displays the parameter details of the database. This is for information purpose.

7. Click ‘Next’. The following screen is displayed.

8. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

9. Click ‘Next’. The following screen is displayed.

3-25
10. Specify the following details:

Include PAR File

Check this box to include the PAR file. If you check this box, you need to specify the PAR file
name.
PAR File Name

If you have checked the box ‘Include PAR File’, you need to specify the PAR file name here.
11. Once you have specified the above details, click ‘Next’ button.

3-26
12. Click ‘Import’ button to import the database with the PAR file parameters.

13. If you have not checked the box ‘Include PAR File’, on clicking ‘Next’, you will be navigated
to the following screen.

14. Specify the Oracle directory name. This is the directory in the server machine where the
import file is located.

15. Click ‘Next’. The following screen is displayed.

16. Specify the following details:

3-27
Dump File Name

Specify the import file name.

Export Schema Name

Specify the export schema name from which the import file is imported.
Export Schema Tablespace

Specify the export schema tablespace from which the import file is imported.
17. Once you have specified the above details, click ‘Next’. The following screen is displayed.

18. Specify the following details:

Import Schema Name

Specify the import schema name to which the import file is loaded. Import
Schema Tablespace

Specify the import schema tablespace to which the import file is loaded.
19. Once you have specified the above details, click ‘Next’ button. The following screen is
displayed.

3-28
 20. This triggers the import operation. You can optionally import the objects, data or full set by
using ‘Import Objects’, ‘Import Data’ or ‘Full Import’ buttons respectively.

3.4.2 Template Database Installation

This section describes the process of template database installation.
1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

2. elect ‘Template Installation’ and click ‘Next’. The following screen is displayed.

3-29
3. Specify the following details:

Source File

Specify the location of the source file. You can use the directory icon to browse to the appropriate
file location.
Destination Directory

Specify the destination. You can use the directory icon to browse to the appropriate file location.
Template Type

Specify the template type. You can choose one of the following destination types.
• PDATA
• MDATA
4. Once you have specified the above details, click ‘Next’. The following screen is displayed.

5. Specify the following details:

DB Unique name

Specify a unique name of the database.

SID

Specify the SID of the database.

6. Once you have specified the above details, click ‘Next’ button. The following screen is
displayed.

3-30
7. Specify the following details:

Oracle Database Home

Specify the Oracle database home directory. You can use the ‘Browse’ button to browse and
select the appropriate directory.
Copy FCUBS Database Template

Check this box to use the existing FCUBS template.

Auto Launch Oracle DBCA

Check this box to launch the Oracle DBCA tool. If you check this button and click next, the
installer will start Oracle DBCA tool, from which you can proceed with the database installation.

3-31
 4. Setting up ELCM Database
4.1 Introduction
This chapter explains the steps to setup ELCM database.

4.2 Creating ELCM Schema by Importing Full Dump

You can create the ELCM schema by way of a full dump import. This is a manual activity. For
details, refer to the section ‘Creating Oracle FLEXCUBE Schema by Importing Full Dump’. You
may follow the same steps for ELCM database setup.

4.3 Creating ELCM Schema from Shipment media

You can create the ELCM schema by loading the objects from the shipment media itself. The
method is described under the following headings.

4.3.1.1 Loading Objects from Shipment media

This section explains the steps to load objects for setting up the ELCM database. Database
installation includes the provision of schema details and source of objects.

The steps to load objects from the Shipment Media are given below:
1. Launch Oracle FLEXCUBE Universal Banking Solution Installer.

2. Choose ‘Enterprise Limits & Collaterals’. Click ‘Next’.

The following screen is displayed:

4-1
3. Choose ‘Database Setup’.
4. Specify the following details:

Operating System and Version

Specify the operating system in which you are installing Oracle FLEXCUBE.

You also need to specify the version of the operating system.

Application Server and Version

Specify the application server on which you are installing Oracle FLEXCUBE. You also need to
specify the version of the application server. Database Server and Version

Specify the database server on which you are installing Oracle FLEXCUBE. You also need to
specify the version of the database server.

5. Once you have specified the above details, click ‘Next’. The following screen is displayed:

4-2
 As you see on this screen, you can install Oracle FGL in two methods:
• Custom Installation
• Template Installation
6. Select the appropriate installation method and click ‘Next’.

Template installation is performed through Oracle DBCA tool.

4.3.2 Custom Installation

The Oracle FLEXCUBE Universal Solutions installer supports custom installation of Oracle
FLEXCUBE in two methods:
• Compile objects and load static data into the database
• Load objects and data by importing data and objects from the import file
1. Select the installation type ‘Custom Installation’.

4-3
2. Select ‘Compile Objects’ under ‘Custom Installation’ and click ‘Next’. The following screen is
displayed.

3. Specify the following details:

Source Directory

Specify the source directory location. The source directory should have the ‘MAIN’ folder and the
contents. Use the directory icon to browse the source directory.

4-4
Destination Directory

Specify the destination directory. Use the directory icon to browse the source directory.

This is optional. If you do not specify the destination directory, on clicking ‘Next’, the Installer
displays a message ‘Sources will be compiled from source directory’. If you want to proceed, click
‘Yes’. The files will be taken directly from source directory for compilation. If you click ‘No’, you
need to specify the destination directory.
Multiple Sources

In case of Cluster and Patch installations, you can install the files from multiple source directories.
Check this box to use multiple directories.

If you check ‘Multiple Sources’, on clicking ‘Next’, the following screen is displayed.

Here, you need to specify the different source directories. Use the directory icon to browse the
source directory.

If you do not check the box ‘Multiple Sources’, you will be directly navigated to the module
selection screen.
4. Once you have specified the details, click ‘Next’. The following screen is displayed.

4-5
5. The Installer will copy the source files from the source directory to the destination directory.
The files are taken from this location for compilation.
6. You can view the status of the copy process on a separate window.

7. Once the copy process is completed, the Installer navigates you to the following screen.

4-6
8. Specify the following schema details:

User Name

Specify the user name to access the schema. Password

Enter the schema password.

Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed. Port

Specify the port number.

9. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

10. After testing the connection, click ‘Next’. The following screen is displayed.

4-7
11. This screen displays the parameter details of the database. This is for information purpose.

12. Click ‘Next’. The following screen is displayed.

13. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

14. If you click ‘Generate Report’ button, in the ‘Logs’ folder, the installer creates an SQL file
‘grantScript.sql’ containing the script for granting the privileges. You can use this file to get the
access. The following screen is displayed.

4-8
15. You can select the objects to be dropped and click ‘Drop’ button to drop the selected objects.
As you drop the objects, the count in this screen is updated.

16. Click ‘Drop Log’ button to view the drop log.

Note: The details of the drop process are logged in a file ‘Drop_All.log’ in the folder <Destination
Folder>/DBLogs.
17. If all the objects do not get dropped at the first time, you can drop them again.

18. Click ‘Next’ button, the following screen is displayed.

4-9
19. The table, sequences and type objects are compiled and the count is updated.
20. You can verify the DDL objects compilation by comparing the current count and the release
count.

21. Click ‘DDL Log’ button to view the DDL logs. The log file ‘LoadDDL.log’ will be available in the
destination directory under the folder ‘DBLogs’.

22. Click ‘Missing DDL List’ button to view the list of DDL files that are available in the source
directory, but not in the schema. The list ‘FilesNotCompiled_DDLObj.txt’ will be available in
the destination directory under the folder ‘DBLogs’.

23. Click ‘Next’. The following screen is displayed.

24. Specify the following details:

Include Scheduler DDLs

Check this box to include scheduler DDLs. If you do not need to include the scheduler DDLs,
leave this field unchecked.
Scheduler DDL Source Path

Specify the location of the ‘tables_oracle.sql’ folder, which is available in extracted ‘quartz.jar’.
Note: You first need to download the file ‘quartz.jar’ and extract this to the local machine. You
need to specify the location of the ‘dbTables’ folder.
25. Click ‘Load Scheduler DDLs’ to compile the files.

26. Click ‘Next’. The following screen is displayed.

4-10
27. Check the objects that you need to load.

28. Click ‘Load Objects’ button. The installer loads the functions, procedures, views, triggers and
packages as per your selection and compiles them.

Note: You can verify the application objects compilation by comparing the count shown in this
screen with the release count.
29. Click ‘Objects Log’ button to view the log. The log file ‘LoadAppObj.log’ will be available in the
destination directory under the folder ‘DBLogs’.

30. Click ‘Missing Object List’ button to view the list of application object files that are available in
the source directory but not in the schema. You can view this list in the file
‘FilesNotCompiled_APPObj.txt’ available in the destination directory under the folder
‘DBLogs’.
31. The installer loads the DDL and application objects of the selected modules.
32. You can view the list of invalid objects in the following screen.

4-11
33. Click ‘Invalid List’ button to view the count of invalid objects. The installer creates the file
‘InvalidList.txt’ in the destination directory under the folder ‘DBLogs’.

34. You can use the ‘Recompile’ button to do a cyclic recompilation. This will reduce the invalid
objects count.

35. You can view the recompile logs by clicking ‘Log’ button. The installer creates a file
‘recompile.log’ in the destination directory under the folder ‘DBLogs’.

36. Click ‘Next’. The following screen is displayed. This starts the ELCM POJO installation
process.

4-12
 37. Specify the following details:

Oracle Java Home Path

Specify the Oracle Java home location. This is required for ELCM POJO compilation.
You can validate the Oracle Java home path by clicking ‘Validate’ button.

38. Click ‘Next’. The following screen is displayed.

39. This screen displays the status of ELCM JAR file creation. The following JAR files are created
for ELCM POJO.
• ELCMDAO.jar
• ELCMDTO.jar
• ELCMProcess.jar
• ELCMUtility.jar
40. Click ‘Load Objects’ button to load the JAR files to the database.

4.4 Loading Data

Once the objects are loaded, you need to insert data into the tables.

This section explains the steps to load static data into the database and the basic setup to be
done.

Follow the steps given below:

1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

4-13
2. Select ‘Load Static Data’ and click ‘Next’. The following screen is displayed.

3. Specify the following details:

Source Directory

Specify the source directory location. The source directory should have the ‘MAIN’ folder and the
contents. Use the directory icon to browse the source directory. Destination Directory

Specify the destination directory. Use the directory icon to browse the source directory.

4-14
This is optional. If you do not specify the destination directory, on clicking ‘Next’, the Installer
displays a message ‘Sources will be compiled from source directory’. If you want to proceed, click
‘Yes’. The files will be taken directly from source directory for compilation. If you click ‘No’, you
need to specify the destination directory.
Multiple Sources

In case of Cluster and Patch installations, you can install the files from multiple source directories.
Check this box to use multiple directories.

If you check ‘Multiple Sources’, on clicking ‘Next’, the following screen is displayed.

Here, you need to specify the different source directories. Use the directory icon to browse the
source directory.

If you do not check the box ‘Multiple Sources’, you will be directly navigated to the module
selection screen.
4. Click ‘Next’ to start objects copy.

4-15
5. The Installer will copy the source files from the source directory to the destination directory.
The files are taken from this location for compilation.
6. Once the copy process is completed, the Installer navigates you to the following screen.

7. Specify the following schema details:

User Name

Specify the user name to access the schema.

Password

4-16
Enter the schema password.
Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed.
Port

Specify the port number.

8. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

9. After testing the connection, click ‘Next’. The following screen is displayed.

10. This screen displays the parameter details of the database. This is for information purpose.

11. Click ‘Next’. The following screen is displayed.

4-17
12. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

13. Click ‘Next’. The following screen is displayed.

14. Specify the following details:

4-18
Branch Plug-in

Check this box to include branch plug-in. If you check this box, you need to specify the
deployment mode in the field ‘Branch DB Centralized’. If you do not need branch plug-in, leave
this field unchecked.
Branch DB Centralized?

Specify the deployment mode. You can choose one of the following modes:
• Centralized
• Decentralized
• Hybrid

Once you have specified the above details, click ‘Next’.

15. The installer executes the procedures required before beginning static data compilation. All
the triggers will be disabled during this process.
16. One the process is completed, you will see the following screen.

4-19
17. You can view the static data log by clicking ‘Static Data Log’ button.

18. Click ‘Next’. The following screen is displayed.

19. Here, you can do the basic maintenances for the table ‘CSTB_PARAM’.

20. Click ‘Next’. The following screen is displayed.

4-20
21. Here you can do the basic maintenances for the tables ‘STTM_BANK’ and ‘STTM_BRANCH’.

22. Click ‘Next’. The following screen is displayed.

23. Here, you can do the basic maintenances for the table ‘STTM_DATES’.

24. Click ‘Next’. The following screen is displayed.

4-21
25. Here, you can do the basic maintenances for the table ‘CYTM_CCY_DEFN’.

26. Click ‘Next’. The following screen is displayed.

27. Here you can do the basic maintenances for the table ‘SMTB_USER’ and
‘SMTB_USER_ROLE’.

28. Click ‘Next’. The following screen is displayed.

4-22
 29. Click ‘Start Setup’ button to compile the entries.
30. This completes the static maintenance and basic setup process.

4.4.1 Import Database Installation

This section describes the process of Import DB installation.
1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

2. Select ‘Import Data’ and click ‘Next’. The following screen is displayed.

4-23
3. Specify the following schema details:

User Name

Specify the user name to access the schema. Password

Enter the schema password.

Connect String

Specify a valid connect string that contains the details for database connectivity.
IP Address

Specify the IP address of the system where the database schema is installed. Port

Specify the port number.

4. Once you have entered the details, you can test the database schema connection using ‘Test
Connection’ button.

5. After testing the connection, click ‘Next’. The following screen is displayed.

4-24
6. This screen displays the parameter details of the database. This is for information purpose.

7. Click ‘Next’. The following screen is displayed.

8. This screen displays the grants provided to the schema. If object compilation is required and
the privilege is not given, then you can find that out from this screen. This is for information
purpose.

9. Click ‘Next’. The following screen is displayed.

4-25
10. Specify the following details:

Include PAR File

Check this box to include the PAR file. If you check this box, you need to specify the PAR file
name.
PAR File Name

If you have checked the box ‘Include PAR File’, you need to specify the PAR file name here.
11. Once you have specified the above details, click ‘Next’ button.

4-26
12. Click ‘Import’ button to import the database with the PAR file parameters.

13. If you have not checked the box ‘Include PAR File’, on clicking ‘Next’, you will be navigated
to the following screen.

14. Specify the Oracle directory name. This is the directory in the server machine where the
import file is located.

15. Click ‘Next’. The following screen is displayed.

16. Specify the following details:

4-27
Dump File Name

Specify the import file name.

Export Schema Name

Specify the export schema name from which the import file is imported.
Export Schema Tablespace

Specify the export schema tablespace from which the import file is imported.
17. Once you have specified the above details, click ‘Next’. The following screen is displayed.

18. Specify the following details:

Import Schema Name

Specify the import schema name to which the import file is loaded. Import
Schema Tablespace

Specify the import schema tablespace to which the import file is loaded.
19. Once you have specified the above details, click ‘Next’ button. The following screen is
displayed.

4-28
 20. This triggers the import operation. You can optionally import the objects, data or full set by
using ‘Import Objects’, ‘Import Data’ or ‘Full Import’ buttons respectively.

4.4.2 Template Database Installation

This section describes the process of template database installation.
1. Launch Oracle FLEXCUBE Universal Banking Solutions Installer.

2. Select ‘Template Installation’ and click ‘Next’. The following screen is displayed.

4-29
3. Specify the following details:

Source File

Specify the location of the source file. You can use the directory icon to browse to the appropriate
file location.
Destination Directory

Specify the destination. You can use the directory icon to browse to the appropriate file location.
Template Type

Specify the template type. You can choose one of the following destination types.
• PDATA
• MDATA
4. Once you have specified the above details, click ‘Next’. The following screen is displayed.

5. Specify the following details:

DB Unique name

Specify a unique name of the database.

SID

Specify the SID of the database.

6. Once you have specified the above details, click ‘Next’ button. The following screen is
displayed.

4-30
7. Specify the following details:

Oracle Database Home

Specify the Oracle database home directory. You can use the ‘Browse’ button to browse and
select the appropriate directory.
Copy FCUBS Database Template

Check this box to use the existing FCUBS template.

Auto Launch Oracle DBCA

Check this box to launch the Oracle DBCA tool. If you check this button and click next, the
installer will start Oracle DBCA tool, from which you can proceed with the database installation.

4-31
Setting up Database
[May] [2012]
Version 12.0

Oracle Corporation
World Headquarters
500 Oracle Parkway Redwood
Shores, CA 94065 U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000 Fax:
+1.650.506.7200
www.oracle.com/ financial_services/

Copyright © [2012] Oracle Financial Services Software Limited. All rights reserved.

No part of this work may be reproduced, stored in a retrieval system, adopted or transmitted in any form or by any means,
electronic, mechanical, photographic, graphic, optic recording or otherwise, translated in any language or computer
language, without the prior written permission of Oracle Financial Services Software Limited.

Due care has been taken to make this document and accompanying software package as accurate as possible. However,
Oracle Financial Services Software Limited makes no representation or warranties with respect to the contents hereof and
shall not be responsible for any loss or damage caused to the user by the direct or indirect use of this document and the
accompanying Software System. Furthermore, Oracle Financial Services Software Limited reserves the right to alter,
modify or otherwise change in any manner the content hereof, without obligation of Oracle Financial Services Software
Limited to notify any person of such revision or changes.

All company and product names are trademarks of the respective companies with which they are associated.
4-1