Community Forums
Results 1 to 4 of 4

Thread: Oracle Unknown editions in License Compliance reports

  1. #1
    Join Date
    Jun 2015
    Posts
    2

    Question Oracle Unknown editions in License Compliance reports

    Hello,

    I am looking for some solutions for Oracle unknown editions.
    Whenever, I generate compliance balance, I see loads of Oracle unknown editions.
    I checked with my DBA and he confirmed that Enterprise editions are running on those servers.

    Issue is....Why FNMS is not able to report Edition name..?
    However, I can see Version number of Oracle in all reports.

    can somebody help me to resolve this issue in FNMS?
    Is it a technical issue from Flexera or
    Is there any problem with our DB (uCMDB)?

    Regards,
    Gaurav

  2. #2
    Join Date
    May 2014
    Posts
    8
    Hi Gaurav,

    Where editions are reported as "unknown" or "unspecified" it is usually because there is software inventory for a device, but no Oracle inventory. Oracle inventory is required to recognize the edition, so until that is available the "unspecified" editions alert you to likely databases that need to be scanned.

    Regards,
    Matt

  3. #3
    Join Date
    Dec 2016
    Posts
    1

    Oracle Inventory

    Matt-
    Can you elaborate on 'oracle inventory'? Is this to mean that the oracle database is not being detected by the FNMS agent?
    I'm running into the same issue as well but want to make sure I fully understand the challenge.

    Thanks,
    Jess

  4. #4
    Join Date
    May 2010
    Location
    Santa Clara, CA
    Posts
    12

    Oracle inventory is special

    Generally, in order to collect all the detail you need for Oracle database licensing using FlexNet inventory, you need to collect both:

    1) Hardware and software inventory, as usual.
    2) Oracle inventory - connecting to the databases and gathering information about edition, users, and usage of options and management packs.

    If you see "unspecified" or "unknown component" when dealing with databases, it generally means something has gone wrong with the Oracle inventory process.

    Note: significant improvements were made starting in FNMS 2015 R2 to allow gathering of Oracle inventory by the FlexNet Inventory Agent and FlexNet Inventory Scanner - so if you are on an older version, you can really streamline gathering Oracle inventory by considering a newer version.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •