Hello JohnSorensenDK, I understand your position. And a case is already open @flexnetsupport. But is the inquiry here not enough to see the business value for the customers? I also understand that OracleLMS detection is built into FlexNetAgent - and that OracleLMS scripts must provide the necessary information to be fetched by FlexAgent. I'm sorry here - but do you really think a customer will turn to Oracle for their scripts? If I am wrong here - then I would like to sincerely apologize.   regards, Matthias ... View more

Hi JohnSorensenDK, we're a little afraid to chase possible Errors just to find out, that's not an Error. In my honest opinion, I've would have expected that OracleLMS-scans or FlexNet Agent could give a hint, that this particular System might be part of a cluster and therefore the failure message in tracker.log - or somewhere else - is more precise about the current situation. Else wise, as an global acting company, we've a lot of Oracle DBs installed. And this error message appears for almost 100 Systems. hope this helps regards, Matthias ... View more

Hello JohnSorensenDK the Instanz is not running on "B". B is only prepared to take over from A in case of Errors. When scanning B with FlexNet Agent 2020 R1 - we can see following error message in tracker.log:   [Fri Nov 20 09:54:21 2020 (G, 0)] {56951004} WARNING: Configuration properties for the Oracle home "/pkg/addp/oracle/base/product/12.1.0/dbhome_1" could not be discovered and instances in this home will not be inventoried. [Fri Nov 20 09:54:21 2020 (G, 0)] {56951004} +-- "/pkg/addp/oracle/base/product/12.1.0/dbhome_1": Discovered by = Oratab, Executable ID = 0:0, DBA group = "dba", Home owner = "", Has SQLPlus = false, SQLNet Authentication Services = "", Can Inventory = false, Real Home = "" [Fri Nov 20 09:54:21 2020 (G, 0)] {56951004} | +-- Instance "LISTENER_addp": Discovered by = Oratab, Process ID = 0, State = unknown, Process owner = "<N/A>" [Fri Nov 20 09:54:21 2020 (G, 0)] {56951004} | +-- Instance "addp": Discovered by = Oratab, Process ID = 0, State = unknown, Process owner = "<N/A>" [Fri Nov 20 09:54:21 2020 (G, 0)] {56951004} WARNING: The SQLPlus command was not found in Oracle home "/pkg/addp/oracle/base/product/12.1.0/dbhome_1". [Fri Nov 20 09:54:21 2020 (G, 0)] {56951004} WARNING: Did not detect instance "LISTENER_addp" in "/pkg/addp/oracle/base/product/12.1.0/dbhome_1" to be in a running state. [Fri Nov 20 09:54:21 2020 (G, 0)] {56951004} WARNING: Did not detect instance "addp" in "/pkg/addp/oracle/base/product/12.1.0/dbhome_1" to be in a running state.   Also in our FNMS reports we can see following errormsg for this particular instanz. Unable to gather Oracle database information, sqlplus or sqlnet.ora file may be missing for oracle home: /pkg/addp/oracle/base/product/12.1.0/dbhome_1   We thought that's an Error so we investigated with our DB-Admins, they told us, it's not an Error because the System is prepared for the Instanz but it is currently not running there. Maybe the false-positiv statement is wrong here. Sorry for the confusion.              ... View more

Hi ChrisG, thanks a lot for your reply. As you said, there might be some special szenarios not to install the Agent-Component during Beacon-Installation. But even if you do it, there seems to be a lack of functionality on the Beacon afterwards, if it comes to downloading the latest packages from the Server. For e.g. you're not able to auto-upgrade this Beacon automatically. As you mentioned.   We came across this issue because of some performance issues on our Beacons and the initial idea - suggested from Flexera - was to deactivate/uninstall the component on Beacon-side. After it was clear that the component is not responsible for the issue, and to be honest here - we've missed to activate it again, because we didn't expect such kind of things to come, we've experianced these issues afterwards.   Nevertheless, what you will get in UI - which is a disturbing fact - is an Error in Beacon overview for this particular beacon, telling, it was unable to download latest packages from Server. You will face this issue, not knowing, that the integrated Agent is a crucial part of the Beacon, and therefore your Infrasturctue Agents are also suffering from this. I, personally expect that the Beacon itself is able to do all the neccesserray parts, without the Agent component.   Furthermore, we noticed that with integration of the Agent, it will scan the Beacon-version and it is getting recognized, but the Version of the Agent is not displayed as an installed Application in UI for that Beacon afterwards. best regards, Matthias   ... View more

Hi mfranz, we're running "out of the box" - standard - schedules and tasks/jobs on AWS beacon. Except, the initial discovery-Job for AWS is taking more time within it's Job, than the upgrade of Beacon-Policy. So there might be a Timing issue here. I mean: AWS-Job for gathering Data from AWS got started and in background policyupdates are done on Beacon-side. Due to this, the scripts on Beacon-side are getting downloaded/deleted and recreated, during collecting the Data from of AWS even if it is not finished yet.     ... View more

Thanks a lot kclausen   is there a something like a "Best Practise Guide for Flexera Agent in AWSImage" available? ... View more

Hello, can you give a little more insight? what has been done to fix the issue?   regards, Matthias ... View more

Hi, the initial Problem has been determined on an on-premise environment. I'm not sure if the workaround (mentioned here) will help on a cloud-based environment, too.   If you're facing issue with updating your cloud-based solution, you should ask Flexera-support and open up a case for it.   best regards, Matthias ... View more

Hi Alexander, we do have the same issue on our side. Only solution is to copy the packages manually as you described. btw. we also have a case open for it but with no solution til now   best regards, Matthias ... View more