Topics:
· Perform the Data Model Upload Outside of the Installer
· Upgrade the OFSDF Application Pack from v8.1.0.0.0 or v8.1.0.1.0 to v8.1.1.0.0
NOTE:
· The user profile executing the installation must have the permission on /tmp before installation.
· Sufficient space must be available in /tmp before installation, else the installation will terminate, and logs are not generated.
ATTENTION:
Ensure you run the upgrade installer only on the cloned environment.
Scenario |
Upgrade Instructions |
|---|---|
Upgrade the OFSDF Application Pack from v8.1.0.0.0 or 8.1.0.1.0 to v8.1.1.0.0 In this scenario, you are upgrading the OFSDF Application Pack from Release v8.1.0.0.0 or v8.1.0.1.0 to Release v8.1.1.0.0.
|
1. Clone your existing environment to the OFSAA Technology Matrix v8.1.1.0.0. 2. Run the Environment Check Utility tool and ensure that the hardware and software requirements are installed as per the OFSAA Technology Matrix v8.1.1.0.0. 3. Update the OFS_BFND_PACK.xml file to enable ONLY the existing installed applications. 4. Update the Silent.props file present in the OFSDF v8.1.1.0.0 installer pack. 5. Trigger the installation. |
|
In this scenario, an Application Pack of v8.1.1.0.0 is already installed and you need to upgrade OFSDF Application Pack from v.8.1.0.0.0 or 8.1.0.1.0 to v8.1.1.0.0. Example: OFS ALM v8.1.1.0.0 Application Pack is already installed and you need to install the OFSDF Application Pack. |
1. Update the OFS_BFND_PACK.xml file of the OFSDF Application Pack. 2. Update the Silent.props file of the OFSDF Application Pack. 3. Trigger the installation. |
This section is applicable if you are performing the OFSDF v8.1 OOB data model upload outside of the installer. A utility is introduced called as the ModelUpgrade utility. This utility enables the Upgrade installation using the Incremental model upload process. The two execution processes supported in the ModelUpgrade utility are as follows:
· Execute the ModelUpgrade.sh File for the Prescripts
· Execute the ModelUpgrade.sh File for the Postscripts
Execute the OFSDF ModelUpgrade.sh file for the Prescripts to backup and delete the data, and then to backup and delete the metadata. Then proceed with the merged model upload and the OFSDF Application Pack upgrade to v8.1.1.0.0.
For detailed information, see the Execute the ModelUpgrade.sh file for the Prescripts and OFSDF Application Pack Upgrade Process sections in the Oracle Financial Services Data Foundation Application Pack Upgrade Guide Release 8.1.x.x.
This section provides information about the preparations that need to be done before proceeding with the upgrade installation.
Topics:
· Download the OFSDF Application Pack Installer and Data Model
· Prepare the Environment for Upgrade
This section provides the details of the download that you need to complete before triggering the application installation.
Topics:
· Download the OFSDF Application Pack Installer
· Download the Mandatory Patches
To download the OFSDF Application Pack installer Release v8.1.1.0.0, follow these steps:
1. Log in to the My Oracle Support (MOS) with a valid Oracle account.
2. In the Patches & Updates tab, search for the OFSDF Application Pack installer patch 32257272 and download the patch. Copy the patch to your OFSAA server in the Binary mode in the setup identified for OFSDF installation.
NOTE:
The archive files are different for every operating system like AIX, Solaris, and RHEL/Oracle Linux.
To download the OFSDF OOB v8.1.1.0.0 Data Model, follow these steps:
NOTE:
This is an optional section that is applicable if you are performing the customized model upload.
1. Log in to the My Oracle Support (MOS) with a valid Oracle account.
2. In the Patches & Updates tab, search for the OFSDF Data Model installer patch 32294660 and download the patch. See the Readme available with the patch for further instructions on downloading the patch and extracting the erwin files.
The following table includes information about the mandatory patches that need to be downloaded during the OFSDF Application Pack upgrade installation.
One-off Patch |
Description |
|---|---|
32548944 |
Download the OFSAAI patch. |
33663417 |
Download this Mandatory OFSAAI One-off Patch. See the ATTENTION below. |
ATTENTION:
For the Mandatory Patch ID 33663417:
On the 10th of December 2021, Oracle released the Security Alert CVE-2021-44228 in response to the disclosure of a new vulnerability affecting Apache Log4J prior to version 2.15. The application of the 33663417 Mandatory Patch fixes the issue.
For details, see the My Oracle Support Doc ID 2827801.1.
Ensure that you reapply the OFSAAI Mandatory Patch 33663417 whenever you Install or Upgrade the Application, or whenever you apply an Incremental Patch.
Before you plan to upgrade any of your application packs to Release 8.1.1.0.0, ensure that all the application packs in your current OFSAA instance are available in the Release 8.1.1.0.0 version. Contact My Oracle Support (MOS) for more information about the release version details.
1. Backup the following environment file from the OFS_BFND_PACK/conf/ directory:
§ OFS_BFND_PACK.xml
2. Backup the following environment files from the OFS_BFND_PACK/schema_creator/conf/ directory:
§ DBMASTER_SC.xml
§ OFS_BFND_SCHEMA_IN.xml
§ OFS_BFND_SCHEMA_BIGDATA_IN.xml
3. Backup the following environment file from the OFS_BFND_PACK/OFS_AAI/conf/ directory:
§ OFSAAI_InstallConfig.xml
4. Ensure that the following property files are present in the OFS_BFND_PACK/appsLibConfig/conf/ directory and make a backup:
§ Silent_upgrade_to_811.template
5. See OFSAA Technology Matrix for the hardware and software required to upgrade to the OFSDF Application Pack Release 8.1.1.0.0.
6. Enable unlimited cryptographic policy for Java. For more information, see the Enabling Unlimited Cryptographic Policy section in the Oracle Financial Services Advanced Analytical Applications Infrastructure Administration and Configuration Guide Release 8.1.x.
7. Clone your environment. For more information, see the Oracle Financial Services Analytical Applications Infrastructure Cloning Reference Guide Release 8.1.x.
8. Execute the following SQL query in the Atomic Schema:
update rev_tables_b set version=0 where version is null;
commit;
In this scenario, you are upgrading the OFSDF Application Pack from v8.1.0.0.0 or 8.1.0.1.0 to v8.1.1.0.0.
NOTE:
If you are upgrading the OFSAA Application Pack to the release v8.1.1.0.0, to ensure successful deployment, you must upgrade the other packs installed in the same environment to the release v8.1.1.0.0.
Topics:
· Clone Your Existing Environment
· Update the OFS_BFND_PACK.xml File
· Update the Silent.props File
· Verify the Log File Information
Clone your existing environment to the v8.1.1.0.0 of OFSAA Technology Matrix. For more information, see the Oracle Financial Services Analytical Applications Infrastructure Cloning Reference Guide Release 8.1.x.
ATTENTION:
This step is required if you need to move from the Linux 7 to Linux 8 version.
Always ensure you run the upgrade installer only on the cloned environment.
You need to be logged in to the UNIX Operating System as a non-root user to perform the following steps. To extract the OFSDF Application Pack software, follow these steps:
1. Download the unzip utility (OS-specific) unzip_<os>.Z and copy it in the Binary mode to the directory that is included in your PATH variable.
If there is already an unzip utility to extract the contents of the downloaded archive, skip this step. Uncompress the unzip installer file using the following command:
uncompress unzip_<os>.Z
NOTE:
If an error message "uncompress: not found [No such file or directory]" is displayed, contact your UNIX Administrator.
2. Assign the 751 permission to the file using the following command:
chmod 751 unzip_<os>
For example, chmod 751 unzip_sparc
3. Extract the contents of the OFSDF Application Pack Release v8.1.1.0.0 installer archive file in the download directory using the following command:
unzip OFS_BFND_8.1.1.0.0_<Operating_System>.zip
NOTE:
Do not rename the Application Pack installer folder name on extraction from the archive.
4. Log in to OFSAA Infrastructure Config Schema and execute the following SQL query:
ALTER TABLE CONFIGURATION MODIFY PARAMNAME VARCHAR2 (100 CHAR);
5. Navigate to the Download Directory and assign the 750 permission to the Installer Directory using the following command:
chmod ?R 750 OFS_BFND_PACK
Update the OFS_BFND_PACK.xml file to enable the existing installed Application Packs.
To configure the OFS_BFND_PACK.xml file, follow these steps:
1. Navigate to the OFS_BFND_PACK/conf/ directory.
2. Rename the file OFS_BFND_PACK.xml to OFS_BFND_PACK.xml.template.
3. Open the OFS_BFND_PACK.xml file in a text editor.
4. Update the OFS_BFND_PACK.xml file in the text editor as mentioned in the following table only for the specified parameter.
NOTE:
For the Big Data mode of installation, enable the option as YES for the APP_ID parameter with the value OFS_AAIB as illustrated in the sample.
Figure 42: Sample OFS_BFND_PACK.xml File
Tag Name |
Attribute Name |
Description |
Mandatory? |
Comments |
|---|---|---|---|---|
APP_ID |
ENABLE |
Enable the Application or Product |
YES if installing in the SILENT mode. |
The default value is YES for Infrastructure. The default value is NO for Others. The permissible values are YES and NO. Set this attribute value to YES against every APP_ID, that is licensed and enable for the upgrade. NOTE: You cannot disable the Application or Product after you enable it. However, the Application or the Product that is not enabled during installation can be enabled later through the Administration UI. |
5. Save the file.
Topics:
· Silent Upgrade to OFSDF v8.1.1.0.0 for RDBMS
This section is applicable only for the RDBMS mode of OFSDF Application Pack v8.1.1.0.0 upgrade installation.
NOTE:
In an integrated environment, Oracle recommends the customers use the same Staging source in the Silent.props file for the T2Ts that load data from the Stage tables into the Result tables.
To configure the Silent.props file to upgrade to the OFSDF Application Pack Release 8.1.1.0.0, follow these steps:
1. Navigate to the installer kit OFS_BFND_PACK/appsLibConfig/conf/ directory.
2. Rename the file Silent_upgrade_to_811.template to Silent.props.
3. Open the Silent.props file in a text editor.
4. Update the Silent.props file and mention the following parameters:
Property Name |
Description of Property |
Permissible values |
Comments |
|---|---|---|---|
LOG_MODE |
Mode for logging |
1 = Debug 0= General |
# Optional; Default: 0 |
SEGMENT_1_CODE |
Segment Code |
Example: BFNDSEG |
# Mandatory Segment Code must be the same as the code that is used during the first OFSDF installation (Base Pack) |
APPFTP_LOG_PATH |
Information Domain Maintenance log path (to be created) for the new Information Domain for App Layer |
Example: /ftpshare/<INFODOM_NAME>/logs |
# Mandatory Information Domain Maintenance log path must be the same as the log path that is used during the first OFSDF installation (Base Pack) |
DBFTP_LOG_PATH |
Information Domain Maintenance log path (to be created) for the new Information Domain for DB Layer |
Example: /ftpshare/<INFODOM_NAME>/logs |
# Mandatory Information Domain Maintenance log path must be the same as the log path that is used during the first OFSDF installation (Base Pack) |
UPLOAD_MODEL |
Whether you need to perform Model Upload |
0 = No 1 = Yes |
# Mandatory |
MODEL_TYPE |
Released Data Model or Customized Data Model |
0 = released Data Model 1 = customized Data Model |
# Mandatory only in the case of UPLOAD_MODEL=1 |
DATAMODEL |
The file name for the customized Data Model |
Not Applicable |
# Mandatory only in the case of uploading the customized Data Model # Option selected for MODEL_TYPE=1 |
DM_DIRECTORY |
The path for the customized Data Model |
Not Applicable |
# Mandatory only in the case of uploading the customized Data Model # Option selected for MODEL_TYPE=1 |
ETL_APPSRC_TYPE |
The ETL application name |
0=New Pair 1=Existing |
# Mandatory |
ETL_NEW_SRCS_REQUIRED |
Whether ETL new sources are required |
N |
# Mandatory |
ENABLE_CONCURRENCY |
#Support for Parallelism |
0 = No 1 = Yes |
#Optional |
CONCURRENCY_LEVEL |
#Support for Parallelism |
Example: CONCURRENCY_LEVEL=10, which means 10 threads are triggered to handle the processing of fsapps. |
#Optional |
5. Save the file.
In this upgrade installation process, an Application Pack of v8.1.1.0.0 is already installed and now you need to upgrade OFSDF Application Pack from v.8.1.0.0.0 or 8.1.0.1.0 to v8.1.1.0.0.
To upgrade the OFSDF Application Pack to Release 8.1.1.0.0 on an existing v8.1.1.0.0 OFSAA instance, follow these steps:
1. Ensure that you completed the following procedures:
a. Download the installer.
b. Perform the prerequisites for installation.
c. Prepare for Upgrade.
d. Extract the software.
e. Update the OFS_BFND_PACK.xml file.
f. Update the Silent.props file.
2. Execute the following command in the console to initiate the OFSDF Application Pack installation in the Silent mode:
./setup.sh SILENT
3. The installer proceeds with the Pre-installation Checks.
4. Enter the OFSAA Processing Tier FTP or SFTP password value and proceed, when prompted in the command prompt.
Figure 43: OFSAA Processing Tier FTP or SFTP Password Prompt
NOTE:
Enter the password to access the Product Staging or Metadata repository directory FTPSHARE in the application server.
5. The process displays the OFSAA License. Enter Y and proceed.
Figure 44: Accept the OFSAA License Agreement
6. The installer installs the OFSAAAI application.
Figure 45: OFS AAAI Silent Mode Installation
7. After OFSAAAI is installed, the OFSDF Application Pack installation begins.
Figure 46: OFSDF Application Pack Installation
NOTE:
· The Data Model upload may take several hours to complete. You can check the installation logs in the /OFS_BFND_PACK/OFS_FSDF/logs directory.
· For the existing customers, with the DB XML, the time taken for the Data Model upload will be significantly reduced. You can upload the warehouse data from the operational systems to the database schema using the ERwin XML or Database XML file. Using the stand-alone command-line utility for TransformErwin.sh, you can transform ERwin XML into Database XML, and use the DB XML instead of ERwin XML to speed up the model upload process. For more information, see the Command Line Utility for Transforming ERwin XML to Database XML section in the Oracle Financial Services Advanced Analytical Applications Infrastructure User Guide Release 8.1.1.0.0.
Figure 47: OFSDF Application Pack Installation Complete
8. The following message is displayed in the console:
Installation completed?
9. The OFSAA Infrastructure installation performs a post-install health check automatically on the successful installation of the product.
10. To verify if the release is applied successfully, check the log files mentioned in the section Verify the Log File Information.
NOTE:
If any applications are installed on top of the OFS AAAI Application Pack 8.1.1.0.0 version, execute the script update_dq_batches_optional_params.sql, which is available in the folder $FIC_HOME/Post_AAI_Migration, after the installation of the applications.
11. For more information on securing your OFSAA Infrastructure, refer to the Oracle Financial Services Analytical Applications Infrastructure Security Guide Release 8.1.x.
12. After successful installation, perform the Post-installation procedures. For detailed information, see the Post-installation section.
13. Perform the necessary Additional Configuration.
See the following logs files for more information:
· The Pack_Install.log file in the OFS_BFND_PACK/logs/ directory.
· The OFS_FSDF_installation.log file and the OFS_FSDF_installation.err file in the OFS_BFND_PACK/OFS_FSDF/logs directory.
· The Infrastructure installation log files in the OFS_BFND_PACK/OFS_AAI/logs/ directory.
· The OFSAAInfrastucture_Install.log file in the $FIC_HOME directory.
ATTENTION:
You can ignore the "ORA-00001: unique constraint" error, and Object already exists and Table has a primary key warnings for the OFSA_CATALOG_OF_LEAVES table in the log file.
In case of any other errors, contact My Oracle Support (MOS).
Follow the steps mentioned in the Post-installation section.
For additional configuration information, see the Additional Configuration section.
In this upgrade installation scenario, an Application Pack of v8.1.1.0.0 is already installed and now you need to upgrade OFSDF Application Pack from v.8.1.0.0.0 or 8.1.0.1.0 to v8.1.1.0.0. For example, OFS ALM v8.1.1.0.0 Application Pack is already installed and now you need to install the OFSDF Application Pack.
NOTE:
If you are upgrading the OFSAA Application Pack to the release v8.1.1.0.0, to ensure successful deployment, you must upgrade the other packs installed in the same environment to the release v8.1.1.0.0.
Topics:
· Update the OFS_BFND_PACK.xml File
· Update the Silent.props File
· Verify the Log File Information
You must be logged in to the UNIX operating system as a non-root user to perform the following steps. To extract the OFSDF Application Pack software, follow these steps:
1. Download the unzip utility (OS-specific) unzip_<os>.Z and copy it in Binary mode to the directory that is included in your PATH variable.
If you already have an unzip utility to extract the contents of the downloaded archive, skip this step. Uncompress the unzip installer file with the command:
uncompress unzip_<os>.Z
NOTE:
If an error message "uncompress: not found [No such file or directory]" is displayed, contact your UNIX administrator.
2. Assign 751 permission to the file with the following command:
chmod 751 unzip_<os>
For example, chmod 751 unzip_sparc
3. Extract the contents of the OFSDF Application Pack Release v8.1.1.0.0 installer archive file in the download directory with the following command:
unzip OFS_BFND_8.1.1.0.0_<Operating_System>.zip
NOTE:
Do not rename the Application Pack installer folder name on extraction from the archive.
4. Log in to OFSAA Infrastructure Config Schema and execute the following SQL query:
ALTER TABLE CONFIGURATION MODIFY PARAMNAME VARCHAR2 (100 CHAR);
5. Navigate to the Download Directory and assign 750 permission to the installer directory with the following command:
chmod ?R 750 OFS_BFND_PACK
Update the OFS_BFND_PACK.xml file to enable only the existing installed Application Packs.
To configure the OFS_BFND_PACK.xml file, follow these steps:
1. Navigate to the OFS_BFND_PACK/conf/ directory.
2. Rename the file OFS_BFND_PACK.xml to OFS_BFND_PACK.xml.template
3. Open the OFS_BFND_PACK.xml file in a text editor.
4. Update the OFS_BFND_PACK.xml file as mentioned in the following table only for the specified parameter.
NOTE:
For the Big Data mode of installation, enable the option as YES for the APP_ID parameter with the value OFS_AAIB as illustrated in the sample.
Figure 48: Sample OFS_BFND_PACK.xml File
Tag Name |
Attribute Name |
Description |
Mandatory (Y/N) |
Comments |
|---|---|---|---|---|
APP_ID |
ENABLE |
Enable the Application or Product |
YES if installing in the SILENT mode. |
The default value is YES for Infrastructure. The default value is NO for Others. Permissible values are YES and NO. Set this attribute value to YES against every APP_ID, which is licensed and should be enabled for the upgrade. NOTE: You cannot disable the Application or Product after you have enabled it. However, the Application or Product not enabled during installation can be enabled later through the Administration UI. |
5. Save the file.
Topics:
· Silent Upgrade to OFSDF v8.1.1.0.0 for RDBMS
ATTENTION:
Do not install the new applications in the same segment if the preinstalled applications use Run Management.
This section is applicable only for the RDBMS mode of OFSDF v8.1.1.0.0 upgrade installation.
NOTE:
In an integrated environment, Oracle recommends the customers use the same Staging source in the Silent.props file for the T2Ts that load data from the Stage tables into the Result tables.
To configure the Silent.props file to upgrade to the OFSDF Application Pack Release 8.1.1.0.0, follow these steps:
1. Navigate to the installer kit OFS_BFND_PACK/appsLibConfig/conf/ directory.
2. Rename the Silent_upgrade_to_811.template file to Silent.props.
3. Update the Silent.props file and mention the following parameters:
Property Name |
Description of Property |
Permissible values |
Comments |
|---|---|---|---|
LOG_MODE |
Mode for logging |
1 = Debug 0= General |
# Optional; Default: 0 |
SEGMENT_1_CODE |
Segment Code |
Example: BFNDSEG |
# Mandatory Segment Code must be the same as the code that is used during the first OFSDF installation (Base Pack) |
APPFTP_LOG_PATH |
Information Domain Maintenance log path (to be created) for the new Information Domain for App Layer |
Example: /ftpshare/<INFODOM_NAME>/logs |
# Mandatory Information Domain Maintenance log path must be the same as the log path that is used during the first OFSDF installation (Base Pack) |
DBFTP_LOG_PATH |
Information Domain Maintenance log path (to be created) for the new Information Domain for DB Layer |
Example: /ftpshare/<INFODOM_NAME>/logs |
# Mandatory Information Domain Maintenance log path must be the same as the log path that is used during the first OFSDF installation (Base Pack) |
UPLOAD_MODEL |
Whether you need to perform Model Upload |
0 = No 1 = Yes |
# Mandatory |
MODEL_TYPE |
Released Data Model or Customized Data Model |
0 = released Data Model 1 = customized Data Model |
# Mandatory only in the case of UPLOAD_MODEL=1 |
DATAMODEL |
The file name for the customized Data Model |
Not Applicable |
# Mandatory only in the case of uploading the customized Data Model # Option selected for MODEL_TYPE=1 |
DM_DIRECTORY |
The path for the customized Data Model |
Not Applicable |
# Mandatory only in the case of uploading the customized Data Model # Option selected for MODEL_TYPE=1 |
ETL_APPSRC_TYPE |
The ETL application name |
0=New Pair 1=Existing |
# Mandatory |
ETL_NEW_SRCS_REQUIRED |
Whether ETL new sources are required |
N |
# Mandatory |
ENABLE_CONCURRENCY |
#Support for Parallelism |
0 = No 1 = Yes |
#Optional |
CONCURRENCY_LEVEL |
#Support for Parallelism |
Example: CONCURRENCY_LEVEL=10, which means 10 threads are triggered to handle the processing of fsapps. |
#Optional |
4. Save the file.
In this upgrade installation process, an Application Pack of v8.1.1.0.0 is already installed and now you need to upgrade OFSDF Application Pack from v.8.1.0.0.0 or 8.1.0.1.0 to v8.1.1.0.0.
To upgrade the OFSDF Application Pack to Release 8.1.1.0.0 on an existing v8.1.1.0.0 OFSAA instance, follow these steps:
1. Ensure that you completed the following procedures:
a. Download the installer.
b. Perform the prerequisites for installation.
c. Prepare for Upgrade.
d. Extract the software.
e. Update the OFS_BFND_PACK.xml file.
f. Update the Silent.props file.
2. Enter the following command in the console to execute the OFSDF Application Pack installer with the Silent option:
./setup.sh SILENT
3. The installer proceeds with the Pre-installation Checks.
4. Enter the OFSAA Processing Tier FTP/SFTP password value and proceed, when prompted in the command prompt.
Figure 49: OFSAA Processing Tier FTP/SFTP Password Prompt
NOTE:
Enter the password to access the Product Staging or Metadata repository directory FTPSHARE in the application server.
5. The process displays the OFSAA License. Enter Y and proceed.
Figure 50: Accept the OFSAA License Agreement
6. The installer installs the OFSAAAI application.
Figure 51: OFS AAAI Silent Mode Installation
7. After OFSAAAI is installed, the OFSDF Application Pack installation begins.
Figure 52: OFSDF Application Pack Installation
NOTE:
· The Data Model upload may take several hours to complete. You can check the installation logs in the /OFS_BFND_PACK/OFS_FSDF/logs directory.
· For the existing customers, with the DB XML, the time taken for the Data Model upload will be significantly reduced. You can upload the warehouse data from the operational systems to the database schema using the ERwin XML or Database XML file. Using the stand-alone command-line utility for TransformErwin.sh, you can transform ERwin XML into Database XML, and use the DB XML instead of ERwin XML to speed up the model upload process. For more information, see the Command Line Utility for Transforming ERwin XML to Database XML section in the Oracle Financial Services Advanced Analytical Applications Infrastructure User Guide Release 8.1.1.0.0.
Figure 53: OFSDF Application Pack Installation Complete
8. The following message is displayed in the console:
Installation completed?
9. The OFSAA Infrastructure installation performs a post-install health check automatically on the successful installation of the product.
10. To verify if the release is applied successfully, check the log files mentioned in the section Verify the Log File Information.
NOTE:
If any applications are installed on top of the OFS AAAI Application Pack 8.1.1.0.0 version, execute the script update_dq_batches_optional_params.sql, which is available in the folder $FIC_HOME/Post_AAI_Migration, after the installation of the applications.
11. For more information on securing your OFSAA Infrastructure, refer to the Oracle Financial Services Analytical Applications Infrastructure Security Guide Release 8.1.x.
12. After successful installation, perform the Post-installation procedures. For detailed information, see the Post-installation section.
13. Perform the necessary Additional Configuration.
See the following logs files for more information:
· The Pack_Install.log file in the OFS_BFND_PACK/logs/ directory.
· The OFS_FSDF_installation.log file and the OFS_FSDF_installation.err file in the OFS_BFND_PACK/OFS_FSDF/logs directory.
· The Infrastructure installation log files in the OFS_BFND_PACK/OFS_AAI/logs/ directory.
· The OFSAAInfrastucture_Install.log file in the $FIC_HOME directory.
ATTENTION:
When upgrading the OFSDF Application Pack to v8.1.1.0.0 in an integrated environment, you can ignore the Object already exists and the Table has a primary key warnings for the OFSA_CATALOG_OF_LEAVES table in the log file.
You can ignore the "ORA-00001: unique constraint" error.
In case of any other errors, contact My Oracle Support (MOS).
Follow the steps mentioned in the Post-installation section.
For additional configuration information, see the Additional Configuration section.