4 Applying This Maintenance Level Release

To apply this ML release, follow these steps:

1. Load the .profile and make sure that $FIC_HOME corresponds to the proper environment where the patch application is required.
2. Start the OFSAAI Services.
3. Download and copy the 37766307_GENERIC.zip file (in Binary mode) to the server where OFSAAI is installed.
4. Navigate to the <USER_PATCH_DIR> directory and extract the contents of the patch archive file using the following command:

   unzip -a <name of the archive file to be unzipped>

   For example: unzip -a 37766307_GENERIC.zip

   Note:

   <USER_PATCH_DIR> is the directory containing the <patch>.zip file copied in step 3. "-a" option is mandatory to unzip the patch. In case, you notice an error message: “unzip: not found [No such file or directory]” when the package is not installed, contact your UNIX Administrator.
   The list of files available when you unzip the folder is as follows:

   • PatchConfig.xml
   • CRR_DataModel.xml
   • install.sh
   • Setup.bin
   • validateXMLInputs.jar
   • Readme_OFSCRR_8.1.2.10.0.htm
5. Navigate to the <USER_PATCH_DIR>/37766307/bin directory and grant 755 permission using the following command: $ chmod 755 *
6. Update the parameter ##RR_UPLOAD_MODEL## in the <USER_PATCH_DIR>/37766307/conf/ PatchConfig.xml file to 1.
7. Update the variables ##OFS_RRS_DATA_TBSP## and ##OFS_RRS_INDEX_TBSP## in PatchConfig.xml. These attributes correspond to the Data and Index Tablespace values found in OFS_CRR_SCHEMA_OUTPUT.xml, which was generated during the installation process. Additionally, the ##EXECUTE_PRE_AND_POST_SCRIPTS## attribute controls the execution of pre- and post-scripts during installation:
   • Setting the value to 1 executes the pre- and post-scripts.
   • Setting the value to 0 skips their execution.
   For BD 8.1.2.10, it is mandatory to set this attribute to 1 to ensure pre- and post-scripts are executed.
8. Install the patch by executing the install.sh command as follows: $ ./install.sh.

   Note:

   • While applying a patch, you might get the following warning in your Putty session, but you can ignore this.
   • WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector$ 1 (file:/../<FICHOME>/ficapp/common/FICServer/lib/jaxb-impl.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
   • WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1
   • WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
   • WARNING: All illegal access operations will be denied in a future release
9. Check if the ML release is applied successfully by verifying the patch install logs under the <USER_PATCH_DIR>/37766307/logs directory. Contact My Oracle Support in case of any errors.
10. For Websphere Server, remove all the jackson* Jars from below folder before creating OFSAAI EAR/WAR file $FIC_HOME/ficweb/webroot/externalib/WEB-INF/lib.
11. For Websphere server, after the EAR/WAR File is deployed, copy the below mentioned jars from <ofsaa_deployed_area_location>/WEB-INF/lib/ directory to the path <ofsaa_deployed_area_location>/externallib/WEB-INF/lib/.
    Ensure the classpath is configured to the path where the above jars are copied under websphere console->Shared Libraries > JERSEY2X.

    • jaxb-xjc.jar
    • jaxb-impl.jar
    • jaxb-core.jar

    For more information, see Configure WebSphere Shared Library to Support Jersey 2x and Jackson 2.9x Libraries section in OFSAA Installation Guide.

12. Execute the following command in Atomic schema:

    analyze table fct_suspect_info compute statistics;
    commit;

13. After the patch is installed successfully, re-create the OFSAA EAR/WAR file and re-deploy a new EAR/WAR file on the web application server.
14. Restart the OFSAA App server and the Webserver.

    For more information on the application configuration, see Administration Guide on OHC.