1. Home
  2. On-premises 5.2
  3. Guides
  4. Tours
  5. Concepts
    1. Aggregate filter
    2. Alias
    3. Apache Avro™
    4. Apache Kafka™
    5. Applied filter
    6. Base table
    7. Bookmark
    8. Business schema
    9. Business schema view
    10. Business schema view column
    11. Business schema view formula column
    12. Column
    13. Connector
    14. Dashboard filter
    15. Dashboard folder
    16. Dashboard runtime filter
    17. Data agent
    18. Data alert
    19. Data destination
    20. Date system variable
    21. Distinct filter
    22. Expression
    23. External data source
    24. External session variable
    25. Filter expression
    26. Filter expression session variable
    27. Filter option
    28. Formula column
    29. Formula expression
    30. Full load
    31. Global Variable
    32. Incorta Analyzer Table
    33. Incorta Analyzer Table column
    34. Incorta Analyzer Table formula column
    35. Incorta Analyzer View
    36. Incorta Analyzer View formula column
    37. Incorta SQL Table
    38. Incorta SQL View
    39. Individual filter
    40. Insight filter
    41. Internal query expression
    42. Internal session variable
    43. Join
    44. Join condition
    45. Join condition column
    46. Join filter
    47. Join filter column
    48. Level based measure
    49. Load filter
    50. Local data file
    51. Local data folder
    52. Materialized View
    53. Materialized View Column
    54. Materialized View Formula Column
    55. Measure filter
    56. Miscellaneous system variable
    57. Multi-Source table
    58. Physical schema
    59. Physical schema table
    60. Physical schema table column
    61. Physical schema table formula column
    62. Physical schema table runtime security filter
    63. Presentation variable
    64. Prompt
    65. Query system variable
    66. Runtime business view
    67. Runtime business view formula column
    68. Runtime security filter
    69. Session variable
    70. Shared Storage
    71. SQL Interface
    72. Upgrade Readiness
    73. Variable
    74. Visualization
  6. Tools
  7. References
  8. Integrations
  9. Data applications
  10. Releases

Concepts → Upgrade Readiness

About Upgrade Readiness

As a term, Upgrade Readiness means that an Incorta environment -- Development, User Acceptance Testing, or Production -- has been prepared for taking an upgrade. In this regard, Upgrade Readiness is the result of a process that ensures that the Incorta environment is ready for an upgrade.

Important

Depending on the number of tenants in your Incorta cluster and the number of physical schemas, business schemas, session variables, and dashboards, the process of Upgrade Verification may take anywhere from 30 minutes to several days.

Achieving Upgrade Readiness

Achieving Upgrade Readiness may require a significant of time and resources. Various resources may need to work both independently and collaboratively to proactively resolve identified issues. These resources include:

  • a System Administrator with root access to the host or hosts running Incorta Nodes, the host running the Cluster Management Console (CMC), and the host or hosts running Apache Spark
  • a CMC Administrator
  • a Database Administrator
  • a Super User that can access each tenant in the Incorta environment
  • an Incorta Developer to resolve identified issues with formula expressions, schema alias, joins between tables, and dependencies between objects such as dashboards and business schemas

Tools for achieving Upgrade Readiness

There are numerous tools that your resource team will need. Here are some examples:

Note

You only need to run the Formula Validation Tool as part of your Upgrade Readiness steps if you are upgrading from a version prior to 5.0.

The team will need to at least run these tools once your Incorta environment. In certain cases, your team will need resolve identified issues. In order to ensure success, the Upgrade Readiness process may iterative: as your team resolves some issues, new issues may surface.