GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Document that utPLSQL does not make use of any costed database options · Issue #1064 · utPLSQL/utPLSQL

Document that utPLSQL does not make use of any costed database options #1064

New issue
Copy link
New issue
Copy link
Closed
#1065
Closed
Document that utPLSQL does not make use of any costed database options#1064
#1065
Copy link
Assignees
jgebal
Labels
documentation
Milestone
v3.1.11

Description

@john-otoole
john-otoole
opened on Mar 27, 2020
Issue body actions

While installing utPLSQL v3.1.10 on a customer's development database recently, we were asked by the customer's DBA team if utPLSQL is using any licensed Oracle database features such as Diagnostics pack / Tuning pack. They saw that it is using DBMS_PROFILER and wondered what else it might be doing. I know that utPLSQL is not using Diagnostics pack / Tuning pack and that it uses DBMS_PROFILER for code coverage. I responded to them with that information.

Would it be worth stating some of this in the utPLSQL documentation? e.g. on the install.html page of the documentation, explicitly state that utPLSQL does not have any dependency on costed database options such as Diagnostics pack / Tuning pack / Partitioning etc.

Activity

  1. PhilippSalvisberg commented on Mar 27, 2020

    @PhilippSalvisberg
    PhilippSalvisberg
    on Mar 27, 2020
    Member
    More actions

    Thanks for reporting this.

    The installation part of the documentation states that

    utPLSQL may be installed on any supported version of Oracle Database

    So the answer is, that it does not use features of Oracle Editions that must be licensed separately.

    However, I guess we could add that to the documentation for clarification purposes.

  2. PhilippSalvisberg
    added
    documentation
    on Mar 27, 2020
  3. jgebal
    added this to the 3.1.11 milestone on Mar 29, 2020
  4. jgebal
    self-assigned this
    on Mar 29, 2020
  5. jgebal
    added a commit that references this issue on Mar 29, 2020

    Added explicit requirements

    This issue will close once commit 83ee513 is merged into the 'develop' branch.
    83ee513
  6. jgebal
    closed this as completedin #1065on Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @jgebal
    jgebal

Labels

documentation

Type

No type

Projects

No projects

    Milestone

    • v3.1.11

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.