Opened 13 years ago

Last modified 11 years ago

#1183 new feature

IZ242: Need test for issue 6745913

Reported by: jana Owned by:
Priority: normal Milestone:
Component: testsuite Version: current
Severity: Keywords: Sun tests


[Imported from gridengine issuezilla]

        Issue #:      242             Platform:     Sun           Reporter: jana (jana)
       Component:     testsuite          OS:        All
     Subcomponent:    tests           Version:      current          CC:    None defined
        Status:       NEW             Priority:     P3
      Resolution:                    Issue type:    FEATURE
                                  Target milestone: milestone 1
      Assigned to:    issues@testsuite
      QA Contact:     joga
       * Summary:     Need test for issue 6745913
   Status whiteboard:

     Issue 242 blocks:
   Votes for issue 242:     Vote for this issue

   Opened: Wed Sep 10 06:19:00 -0700 2008 

The testsuite should check on Oracle database if OPEN_CURSOR values for dbwriter
is not continually increrasing, which would signify that some  database objects
remain open.

In Oracle instance at oin a view SYS.V_$OPEN_CURSORS_BY_USER has been created
for this purpose.

In testsuite connection needs to be created as user sys (sysadmin) to the
database in order to quewry this view.

Some jobs should be submitted (pminiworms), dbw started and then this sql query


It should store the initial value and repeat this query every minute and compare
the value. The value should remain constant.  It should do this 5 minutes,
while dbw is running and jobs are running.

   ------- Additional comments from jana Wed Sep 10 06:27:14 -0700 2008 -------
Eventually the query can also select the field "MAX_CUR" and compare that the
TOTAL_CUR=MAX_CUR. Again do it every minute for 5 minutes.

   ------- Additional comments from jana Wed Sep 10 07:34:32 -0700 2008 -------
Scratch the last comment, comparing TOTAL_CUR=MAX_CUR, is not possible. Before
getting the initial value of TOTAL_CUR, the test should wait, probably about 3
iterations of the dbwriter (3 minutes), so the value doesn't fluctuate anymore.

If there is a cursor leak, the value will be constantly getting bigger. After
the 5 minute run the TOTAL_CUR should not be bigger than 8.

Change History (0)

Note: See TracTickets for help on using tickets.