RSS Feed

Method R Discussion Group

I installed the HOTSOS Harness, ran start_harness, and then tried to use the do.sql script and got the following error.  The job_queue_processes is set to < 0.  I ran the harness_test_load.sql with no errors.  I also ran the do.sql with debug turned on and didn't find anything more than what was listed below.

dev11 >@do
Enter .sql file name (without extension)            : test1
Enter the workspace name                            : test
Enter the scenario name                            : orig
Is this a (S)QL or (P)L/SQL test execution[S]?      :
Display results of SQL (Y/N) [N]?                  :
Load trace files (Y/N) [Y]?                        :
Execute once prior to test (Y/N) [N]?              :
Display? (S)tats/(L)atches/(A)ll/(C)ustom/(N)one [C]:
BEGIN snap_request(3, 1,              18, 'N', 'harness02'); END;

*
ERROR at line 1:
ORA-20001: Pipe name: harness_pipe_harness02 Error: Timeout (> 2 seconds) on pipe
ORA-06512: at "HOTSOS_USER.SNAP_REQUEST", line 43
ORA-06512: at line 1


BEGIN snap_request(3, 2,              18, 'N', 'harness02'); END;

*
ERROR at line 1:
ORA-20001: Pipe name: harness_pipe_harness02 Error: Timeout (> 2 seconds) on pipe
ORA-06512: at "HOTSOS_USER.SNAP_REQUEST", line 43
ORA-06512: at line 1


dev11 >
dev11 >rem Display error message if trace file(s) didn't load
dev11 >prompt

dev11 >select 'Extended SQL Trace (10046) file DID NOT load!' the_msg
  2    from dual
  3  where not exists (select null from hscenario_10046_line
  4                      where hscenario_id = &htst_scenario_id)
  5  /
dev11 >
dev11 >rem If this is a SQL test file, must gather 10053 and plan data...else skip it
dev11 >set termout &debug verify off heading off feed off


Actual PARSE and STAT line data for test:orig

PARSE #1:c=0,e=1982,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=25542979332251

STAT #1 id=1 cnt=1 pid=0 pos=1 obj=68281 op='TABLE ACCESS FULL DUAL (cr=3 r=0 w=0 time=144 us)'


Explain Plan for test:orig


--------------------------------------------------------------------
| Id  | Operation            |  Name      | Rows  | Bytes | Cost  |
--------------------------------------------------------------------
|  0 | SELECT STATEMENT    |            |    1 |      |    2 |
|  1 |  TABLE ACCESS FULL  | DUAL        |    1 |      |    2 |
--------------------------------------------------------------------

Note: cpu costing is off


Statistics Snapshot for test:orig

dev11 >


Your help will be greatly appreciated.

I sorry the job_queue_processes is set to 18 not < 0.

Anytime you get the pipe timeout error, it is an indication that there is an issue with the job submission portion of the harness.  Can you verify that there is an available job_queue_process when you attempt to use the harness?  Basically, if the job_queue_processes parameter is set to 18, then there must be less than 18 processes running for your session to be able to successfully work.  So, the job may have gotten submitted, but when the harness attempts to use it, if there is not an available process, then it will fail.  This error is caused by something on the database side...not a harness configuration thing.  So, we'll have to try and track down what the issue is on the database that is keeping the pipe from being accessible.
 
Let us know what you find out about the job_queue count and we'll go from there.