Data Loss Prevention

 View Only
  • 1.  Upgrade 15.5 to 15.7 URT readiness with 6 warnings

    Posted Jun 12, 2020 08:59 AM
    hi everyone,

    we are testing our upgrade method from 15.5 to 15.7 in lab environment with similar setup to production (3 tier with seperate oracle as DB).  We have 15.5 running with clients communicating to the enforce server.
    we ran the 15.7 upgrade (msi) and have tried running the URT, however this exits with error message :

    "Error: UpdateReadinessTool failed to run."
    upon investigation we don't see any error messages within the output log, only "6 warnings" regarding "tuning"
    We have verified protect user permissions and readiness user permissions.

    Any advice would be appreciated.

    Regards
    Gino I.

    output log detail :

    Hostname                 : PRD-DLPENFOR02                                      
    Upgrade Source Version   : 15.5                                                
    Upgrade Target Version   : 15.7
    Readiness Tool Version   : 1
    Database Schema Version  : 15.5
    Oracle Version           : Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
    Oracle Patchset          :
    Oracle Server Platform   : AIX-Based Systems (64-bit)
    Date                     : 2020-06-04 15:33:05

    Enforce Version      Date Installed                 Is Current Version?
    -------------------- ------------------------------ -------------------
    15.5.0.17018         2020-05-12 15:22:04            Y

    Start: Oracle Support Validation - 2020-06-04 15:33:05
    End  : Oracle Support Validation - elapsed 0s - PASSED

    Start: Oracle CDC support not enabled - 2020-06-04 15:33:05
    End  : Oracle CDC support not enabled - elapsed 0s - PASSED

    Start: Oracle Queued Jobs - 2020-06-04 15:33:05
    End  : Oracle Queued Jobs - elapsed 0s - PASSED

    Start: Oracle Securefile Validation - 2020-06-04 15:33:05
    End  : Oracle Securefile Validation - elapsed .35s - PASSED

    Start: Oracle Virtual Column Validation - 2020-06-04 15:33:05
    End  : Oracle Virtual Column Validation - elapsed .91s - PASSED

    Start: Oracle Partition Table Validation - 2020-06-04 15:33:06
    End  : Oracle Partition Table Validation - elapsed .03s - PASSED

    Start: Numeric Overflow Validation - 2020-06-04 15:33:06
    End  : Numeric Overflow Validation - elapsed .01s - PASSED

    Start: Table Definition Validation - 2020-06-04 15:33:06
    End  : Table Definition Validation - elapsed 4.9s - PASSED

    Start: Index Definition Validation - 2020-06-04 15:33:11
    End  : Index Definition Validation - elapsed 51.77s - PASSED

    Start: Foreign Key Validation - 2020-06-04 15:34:03
    End  : Foreign Key Validation - elapsed 15.05s - PASSED

    Start: Miscellaneous Object Validation - 2020-06-04 15:34:18
    End  : Miscellaneous Object Validation - elapsed .1s - PASSED

    Start: Invalid Object Validation - 2020-06-04 15:34:18
    End  : Invalid Object Validation - elapsed .11s - PASSED

    Start: Oracle System Privilege Validation - 2020-06-04 15:34:18
    End  : Oracle System Privilege Validation - elapsed .12s - PASSED

    Start: Tablespace Validation - 2020-06-04 15:34:19
    End  : Tablespace Validation - elapsed .03s - PASSED

    Start: Oracle Object Privilege Validation - 2020-06-04 15:34:19
    End  : Oracle Object Privilege Validation - elapsed 1.86s - PASSED

    Start: Check Constraint Validation - 2020-06-04 15:34:20
    End  : Check Constraint Validation - elapsed 1.84s - PASSED

    Start: Sequence Validation - 2020-06-04 15:34:22
        Out-of-order sequences
        Sequence Name                  Table Name                     Column Name                    Sequence.NEXTVAL Highest PK Value
        ------------------------------ ------------------------------ ------------------------------ ---------------- ----------------
    End  : Sequence Validation - elapsed 2.59s - PASSED

    Start: Oracle System Parameter Validation - 2020-06-04 15:34:25
        Parameter Name                 Current Value        Recommended Value
        ------------------------------ -------------------- --------------------
        disk_asynch_io                 TRUE                 FALSE
        memory_target                  0                    3221225472
        pga_aggregate_limit            3418357760           0
        pga_aggregate_target           1709178880           314572800
        query_rewrite_enabled          TRUE                 FALSE
        session_max_open_files         10                   20
    End  : Oracle System Parameter Validation - elapsed .05s - WARNING (6 warnings)

    Start: Data Validation - 2020-06-04 15:34:25
    End  : Data Validation - elapsed 0s - PASSED

    Data Objects Check Summary: There are total of 6 warnings and 0 errors.                                                                                                                                                                                                                                   
    For details about the Update Readiness Tool output messages and troubleshooting information, see the Support Center article at https://support.symantec.com/en_US/article.DOC10667.html                                                                                                                    



    ------------------------------
    Gino Issel
    DFA Solutions
    ------------------------------


  • 2.  RE: Upgrade 15.5 to 15.7 URT readiness with 6 warnings

    Posted Jun 23, 2020 09:40 AM
    Hi Gino, it's been my experience with the 15.5 upgrade and now 15.7 under my belt, that warnings are not show stoppers.  it's the errors that will prevent upgrade.  if you have data in your log i'd say the URT did finish.  Since it's your dev i'd say go for it but I'm not you.


  • 3.  RE: Upgrade 15.5 to 15.7 URT readiness with 6 warnings

    Broadcom Employee
    Posted Jun 30, 2020 05:36 PM
    I agree with the comments from DLP Freak.  The migration utility will be halted with any errors in the URT results, and with warnings alone will proceed forward.  The details you posted with 6 warnings and 0 errors will not stop the upgrade from running.  When in doubt of any URT results, consider opening a technical support case for the support team to review.  Make sure to have good backups prior to running any upgrade so you have a remediation strategy if the upgrade doesn't complete as planned.


  • 4.  RE: Upgrade 15.5 to 15.7 URT readiness with 6 warnings

    Posted Aug 08, 2020 12:58 PM
    Hi Gino,

    While the URT tool checks for schema related errors, it does not check for the actual data. So even if your URT succeeds without any errors, if there are any data related errors(i mean data corruption in the database tables), the upgrade would fail. Check the upgrade logs generated. They could show errors other than URT related warnings. if that is the case, you will have to open a ticket with Symantec and let the support figure out the corrupted data. The upgrade log would show the process failed at which step. This will help support troubleshoot the issue.

    I my case, the URT succeeded with just 1-2 warnings. However, when we ran the upgrade, it failed at Data migration step. later, Support identified there were some issues with the Data Identifier table as it had some corrupt entries which where causing the problems.

    I hope this is of some help.