Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 168400

[JIRA] (HHQ-5869) When editing oracle instance via UI - getting a UI error, but in fact the instance has changed

$
0
0

 

     https://jira.hyperic.com/browse/HHQ-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

 

Nira Shafrir resolved HHQ-5869.

-


 

    Resolution: Fixed

   

When editing oracle instance via UI - getting a UI error, but in fact the instance has changed

----------------------------------------------------------------------------------------------

 

                Key: HHQ-5869

                URL: https://jira.hyperic.com/browse/HHQ-5869

            Project: Hyperic HQ

         Issue Type: Bug

         Components: UI / UX

           Reporter: Osnat Haiman

           Assignee: Nira Shafrir

           Priority: Major

 

The bug was found in build 415 while testing Oracle control actions.

I wanted to verify that when server has multiple instances - the control action works only on the configured instance (and not on the others).

The scenario is a bit long. The problem in one sentence is that not always the DB instance that is configured in the UI is the correct instance & when contrl actions are executed - user think that it will affect the configured instance, while in practice it affects other instance

 

Scenario:

=========

1. My Windows Oracle server (10.23.160.127, administrator/admin) has the following instances: ora11201, ora11202

2. Both instances were up

3. In the UI only one instance was configured: Server --> Inventory --> Control --> jdbcUrl= jdbc:oracle:thin:@10.23.160.127:1521:ora11201

4. Via Control tab I stopped ora11201(stop abort)

5. I verified that ora11201 was not reachable (# su - oracle --> set ORACLE_SID=ora11201 --> sqlplus / as sysdba --> I saw that connection was idle)

   and that ora11202 was reachable

6. Now I wanted to get the second instance down, so in the UI I modified the following property:

   jdbcUrl= jdbc:oracle:thin:@10.23.160.127:1521:ora11202

7. Via Control tab I stopped ora11202(stop abort) & verified that now both instances were down

8. Via Control tab I then strated ora11202 & verified that ora11201 was down & ora11202 was up

9. In the UI I edited now the instance as follows:

   jdbcUrl= jdbc:oracle:thin:@10.23.160.127:1521:ora11201

Problem:

=======

10. I received a UI error (see error at the end of teh description) & the UI remain displaying me ora11202

11. In practive, though user receives an error & UI doesn't change - in fact the instance does change behind the scenes

12. User thinks taht UI is still configured to ora11202 & stops the instance (via Control tab). in fact ora11202 remains up

    (though user expects it to get down).

    If user starts the instance, in fact ora11201 is getting up

This is the UI error:

he configuration has not been set for this resource due to : Invalid configuration: org.hyperic.hq.measurement.monitor.LiveMeasurementException: Error contacting resource: Query failed for UserCommits, while attempting to issue query SELECT value FROM V$SYSSTAT WHERE name = 'user commits':ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist

 

--

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.hyperic.com/secure/ContactAdministrators!default.jspa

For more information on JIRA, see: http://www.atlassian.com/software/jira

 

       

 


Viewing all articles
Browse latest Browse all 168400

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>