Method R Discussion Group

Method R helps developers, DBAs, and decision-makers optimize Oracle-based software in every phase of the software life cycle.

Discuss Method R products, techniques, and events.

Ask new questions or post your own responses.

Timeout on sid pipe

Hi

  I am trying to install and run the harness tool and I am getting the below message when I try to run the do.sql


Any idea?

Thanks
Sundar R

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

*
ERROR at line 1:
ORA-20001: timeout on sid pipe
ORA-06512: at "SYS.SNAP_REQUEST", line 32
ORA-06512: at line 1


BEGIN snap_request(1, 2,            824, 'N', ''); END;

*
ERROR at line 1:
ORA-20001: timeout on sid pipe
ORA-06512: at "SYS.SNAP_REQUEST", line 32
ORA-06512: at line 1
Sundar Raghavan Send private email
Monday, September 24, 2007
 
 
This is likely a problem with having the harness started properly and the job it creates being persistent.  First, execute @hshowconfig to display the following information:

SQL> @hshowconfig
========================================
Harness User          : op
Harness User Password : OP
Database Instance    : hotsos
SQL*Plus HOST command : $
OS erase command      : erase
Preferred Editor      : notepad.exe
========================================
******************************
The harness is running
Harness Pipe Name  : f41002
Capture Session Job#: 861
******************************
Harness Capture Session Info
SID    : 137
Serial#: 4
Program: ORACLE.EXE (J000)
Module : Hotsos Test Harness
Action : harness_pipe_f41002 (capture)
******************************

Your information will differ slightly from what is shown for your own id/password/instance/editor/harness pipe name  and other info.  But, it should appear very similarly.  The harness must be running and have a valid job #.  You can also check the job queue with:

SELECT job, what FROM USER_JOBS ;

  JOB WHAT
----- --------------------------------------------
  861 begin  snap_request_fulfill('f41002');  end;

This job number should match the job number shown in the hshowconfig output.  In order for the job to be submitted successfully, the job_queue_processes parameter must be greater than 0.  A good default would be at least 10.  This also needs to be checked. 

Please review this information and make sure it all looks correct and the job is submitted.  If all that looks good, please let me know and we'll take additional steps.
Karen Morton Send private email
Thursday, October 4, 2007
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Discussion Groups Main Page

Powered by FogBugz