[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dectrace_v20

Title:DECtrace V2.0 and All-in-1 Perf Rpts conf.
Notice:Kits+Doc, 2 | Patches, 3
Moderator:OMYGOD::LAVASH
Created:Mon Apr 26 1993
Last Modified:Mon Jun 02 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:467
Total number of notes:2058

460.0. "Trace 1.3.5 - No Services Discovered" by BROKE::BITHER () Wed Apr 16 1997 15:58

Hi,

Oracle Enterprise Manager 1.3.5
Windows NT 4.0
Oracle 7.3.3
SQL*Net 2.3.3

Customer has just intalled 1.3.5 OEM and is trying to use Oracle trace.
They use the wizard to see what products have been instrumented or
available for tracing.  She clicks on the trace icon, and an agent goes
out to do discovery.  She expects it find all her 7.3.3 Oracle databases
and all her databases accessible via 2.3.3 SQL*Net.  However, it comes
back and says "No Services Discovered."

They are about to teach a class on this and wanted to show the latest
version as she told me 1.2.2 had a lot of problems.

Thanks, Diane



T.RTitleUserPersonal
Name
DateLines
460.1We need more informationOOTOOL::CRAIGThu Apr 17 1997 12:4218
	Hi Diane,

	If you could add the /l switch to the trace executable
	and send us a copy of the log that is produced it would
	give us additional information to help us analyze this
	problem.

	You can add this switch in either of two places:

		1) in the registry

		2) on the property sheet for the trace executable
		   (choose the trace icon and properties)

	We'll be waiting to hear back from you.

	Thanks,
	Sheri
460.2Log files weren't createdBROKE::BITHERFri Apr 18 1997 11:2510
Hi Sheri,

The customer turned on the /l flag for tracing and got information coming
across the screen but no log files were created.  Looked for epc_error.log
and epcw_error.log files.  I only got this as a message last night and
cannot reach customer so am waiting to hear if she looked for these
files in ORACLE_HOME.  In the meantime any other thoughts as to why
these files might not have been created and how to capture the info?

Thanks a lot, Diane
460.3More infoBROKE::BITHERFri Apr 18 1997 12:1914
Hi Sheri,

Got some more clarification.  Customer searched absolutely everywhere
for epc*.log files and there were none.  She set the /l flag in 
properties and not the registry as the documentation didn't provided
enough details as to how to use the registry to set up logging.
It did work in that logging messages show up on the screen and she could
see some error messages flying across but they went too fast for her
to read them.  Is there any other way to capture this information into
a log file?  Maybe using the registry is the only way?  If so, how do
we do that?

Thanks a lot, Diane

460.4May not get a log fileOOTOOL::CRAIGMon Apr 21 1997 14:0313
	Hi Diane,

	It may be that the customer did not get a .log file.
	They would only see one if there was a server error.
	To verify, have them check with capital letters.

	Using the /l switch should create a scrollable window
	on the terminal. It doesn't create a file of the output.
	They will need to cut and past the output to a file
	and send it to us. If their window isn't scrollable
	let me know, it's supposed to be.

	Sheri
460.5logBROKE::BITHERFri Apr 25 1997 17:26156
Hi Sheri,

Yes, customer's window is scrollable but she was unable to
cut & paste from one window to another at first.  After a while she was
able to cut and paste into a mail message but it took her an hour.
I only say this because I'm wondering, will it be possible someday to
create a log file even when no server errors occur?  Below is the
log followed by a bit of additional info.

Thanks very much!  Diane
---------------------------------------------------------------------
Updating Navigator View... 
Performing OEM Discovery... 
Initializing OEM Console IDispatch... 
OEM Discovered Node(EXISTING): erseq 
Service PRODERS Discovered From OEM on Node erseq. 
Node erseq doesn't have any discovered products or services 
OEM Discovered Node(EXISTING): ed-sesun1 
Service ED Discovered From OEM on Node ed-sesun1. 
Node ed-sesun1 doesn't have any discovered products or services 
OEM Discovered Node(EXISTING): KGILL-PC 
Service PROD Discovered From OEM on Node KGILL-PC. 
Service ORCL Discovered From OEM on Node KGILL-PC. 
Node KGILL-PC doesn't have any discovered products or services 
Collections Details List 
Navigator View Update Complete 
Registering Trace in the Running Object Table... 
Initializing OEM Console IDispatch... 
Flushing OEM Job Notifications... 
Initializing OEM Console IDispatch... 
Discovered Node: erseq 
Discovered Node: ed-sesun1 
Discovered Node: KGILL-PC 
Attempting to submit discovery job  to node KGILL-PC. 
New job submitted with JobId 41 on node KGILL-PC 
New OEM Job Information... 
Destination: KGILL-PC 
Schedule: /R=I 
Job Notification ID: Oracle.Trace.1.3.5 
Job Name:  
Batch: 0 
Readonly: 1 
Script: C:\ORANT\sysman\scripts\tcl\otrcjob.tcl 
Input Filename:  
Parameters: 
 {{{otrcflis}}} 
Job notification Received for node KGILL-PC at 25-APR-1997 09.29.32 AM 
  JobId: 41 
  Status: Started 
  Output: The Task returned no output 
 
Job notification Received for node KGILL-PC at 25-APR-1997 09.29.47 AM 
  JobId: 41 
  Status: Intermediate 
  Output: EPC-00154: Invalid/missing restriction 
 
Job notification Received for node KGILL-PC at 25-APR-1997 09.29.53 AM 
  JobId: 41 
  Status: Intermediate 
  Output: EPC-00152: Error opening input parameter file 
 
Job notification Received for node KGILL-PC at 25-APR-1997 09.29.54 AM 
  JobId: 41 
  Status: Completed 
  Output:  
 
Oracle home: C:\ORANT
 
 
 
 Service = ORCL
 
     SID = ORCL
 
 
 
 Service = PROD
 
     SID = PROD
 
 
 
 Trace CLI version = 1
 
 
 
   (No fdf files found)
 
 
 
 
 
Oracle home: C:\ORANT
 
 
 
 Service = ORCL
 
     SID = ORCL
 
 
 
 Service = PROD
 
     SID = PROD
 
 
 
 Trace CLI version = 1
 
 
 
   (No fdf files found)
 
 
 

 
 
 
Oracle Home: C:\ORANT 
 Service = ORCL 
 SID = ORCL 
 Service = PROD 
 SID = PROD 
This oracle home has 2 services. 
 
This oracle home has 0 facilities. 
 
Progress Status Text: No Products Discovered(KGILL-PC) 
Progress Status Text: Processing Complete 
Job notification Received for node KGILL-PC at 25-APR-1997 09.29.59 AM 
  JobId: 41 
  Status: Expired 
  Output: The Task returned no output 
 
EPCJob::GetJobInfo Failed. 
End Of Cursor 
Updating Navigator View... 
Performing OEM Discovery... 
Initializing OEM Console IDispatch... 
OEM Discovered Node(EXISTING): erseq 
Service PRODERS Discovered From OEM on Node erseq. 
Node erseq doesn't have any discovered products or services 
OEM Discovered Node(EXISTING): ed-sesun1 
Service ED Discovered From OEM on Node ed-sesun1. 
Node ed-sesun1 doesn't have any discovered products or services 
OEM Discovered Node(EXISTING): KGILL-PC 
Service PROD Discovered From OEM on Node KGILL-PC. 
Service ORCL Discovered From OEM on Node KGILL-PC. 
Node KGILL-PC doesn't have any discovered products or services 
Collections Details List 
Navigator View Update Complete 
Initializing OEM Console IDispatch... 


------------------------------------------------------------------------ 
She says there are no products to be discovered on notes erseq and ed-sesun1
and she deselected them.  However on kgill-pc there are the following products:
   - Two oracle 7.3.3 databases
   - SQL*Net 2.3.3
All three of which the customer expected to be discovered.

I don't know if the EPC errors are relevant but they appear to refer to
CLI and CLI=l in this log so maybe they have something to do with why
a log file is not created if not something to do with the actual problem
(not finding products in discovery).  I looked up the errors but couldn't
provide any advice based on them:

  EPC-00154 Invalid/missing restriction
   Cause:  The CLI found input restriction record with either missing or
           otherwise invalid value
   Action: If restriction input is not to be used with CLIL, make sure
           it is complete.

  EPC-00152 Error opening input parameter file.
   Cause:  May be due to parameter file required by Oracle Trace CLI not 
           having been provided by the user, else it is an Oracle Trace
           internal error.
   Action: If missing parameter file can be provided, then do so, else
           contact support.

Thanks, Diane
460.6No products found - workaround availableOOTOOL::CRAIGMon Apr 28 1997 11:4644
	Hi Diane,

	Thanks for the information. In your last message there were
	three issues that you addressed. I will put answers for you
	about all three in this message.

	1) No products found during auto discovery

	Engineering has the following workaround:

		o Edit the file otrcflis.tcl
		  This file is located in:

			$ORACLE_HOME\network\agent\jobs\oracle\otrace\general

			(for Oracle8 users the "network" directory will be "net30"

		o Search for "*"
		o Remove the ".fdf" leaving the *

		o Rerun the auto discovery and the products will be discovered

		Note: There should be no files other than .fdf files in the directory
			$ORACLE_HOME\otrace73\admin\fdf
			If there are files with another extension than .fdf in this
			directory the user will need to move them or this workaround
			will cause another error

	2) Customer unable to cut and paste from Log window

		I will enter a bug in the bugs database for this problem.
		Engineering will plan to allow cut and paste in this window
		or provide the capability to save the log to a file.

	3) Irrelevant EPC errors generated -= EPC-00154 and EPC-00152

		Engineering has corrected the problem of these bogus errors
		in 7.3.4 and 8.0.2.

	Thanks for your patience let me know if you need further assistance.

	Best regards,
	Sheri
	
460.7ThanksBROKE::BITHERTue Apr 29 1997 08:515
Hi Sheri,

Thanks for all the information!  

Diane
460.8it worked!BROKE::BITHERWed Apr 30 1997 09:006
Hi Sheri,

Just wanted to let you know that the customer said the workaround
worked and thanks for all the help.

Diane
460.9Great!OOTOOL::CRAIGWed Apr 30 1997 13:096
	Diane,

	Glad to hear that it worked. Thanks for letting
	us know!

	Sheri