Ah, that would require logging onto the server, which I almost never do.
It's NT. Win2k is livable, NT is not. Ugh.
Jared
|
| "OrclBabu" <orclbabu@hotmail.com>
Sent by: oracle-l-bounce@freelists.org
02/24/2004 01:30 PM
Please respond to oracle-l
|
To: <oracle-l@freelists.org>
cc:
Subject: Re: 7.3 anyone? |
Jared..
Thinking abt it - try it from SVRMGRL instead of SQLPlus...
Babu
----- Original Message -----
From: OrclBabu
To: oracle-l@freelists.org
Sent: Tuesday, February 24, 2004 4:27 PM
Subject: Re: 7.3 anyone?
Its from a 7.3.4.. We may have the turbo patch on ;-)
SVRMGR> select * from v$version;
BANNER
----------------------------------------------------------------
Oracle7 Server Release 7.3.4.5.0 with the 64-bit option - Produc
PL/SQL Release 2.3.4.5.0 - Production
CORE Version 3.5.4.0.0 - Production
TNS for DEC OSF/1 AXP: Version 2.3.4.0.0 - Production
NLSRTL Version 3.2.4.0.0 - Production
5 rows selected.
Babu
----- Original Message -----
From: Jared.Still@radisys.com
To: oracle-l@freelists.org
Sent: Tuesday, February 24, 2004 2:02 PM
Subject: Re: 7.3 anyone?
Exacly which version of Oracle 7.x would this be from?
To the best of my knowledge, doing a describe on a package
never worked this way in 7.x.
Jared
SVRMGR> connect internal
Connected.
SVRMGR> desc dbms_system
package dbms_system is
------------
-- OVERVIEW
--
-- This package provides some system level utilities.
-- SECURITY
--
-- This package is only accessible to user SYS by default. You can control
-- access to these routines by only granting execute to privileged users.
----------------------------
-- PROCEDURES AND FUNCTIONS
--
procedure set_ev(si binary_integer, se binary_integer,
ev binary_integer, le binary_integer, nm varchar2);
-- This is an internally used routine that should never be called by users.
procedure read_ev(iev binary_integer, oev out binary_integer);
-- This is an internally used routine that should never be called by users.
--
--
procedure dist_txn_sync(inst_num number);
-- This should be normally be only called by the XA library.
procedure set_sql_trace_in_session(sid number, serial# number,
sql_trace boolean);
-- Enable sql_trace in the session identified by (sid, serial#). These
-- value are gotten from v$session.
-- Input arguments:
-- sid
-- session id
-- serial#
-- session serial number
-- sql_trace
-- if true then enable tracing, if false disable tracing.
--
procedure ksdwrt(dest in binary_integer, tst in varchar2);
-- Print the given string out to the trace file.
-- Input arguments
-- dest - destination of the output (Alert file or Trace file or both)
-- for specifying both, the value of dest should be
-- trace_file+alert_file
-- tst - Trace string to print.
procedure ksdfls;
-- flush the output written to trace file.
procedure ksdddt;
-- Dump date and time information to trace file
procedure ksdind(lvl in binary_integer);
-- Set the indentation level for the further output to trace file.
-- Level - the level of indentation.
end;
----- Original Message -----
From: Cary Millsap
To: oracle-l@freelists.org
Sent: Tuesday, February 24, 2004 2:37 AM
Subject: 7.3 anyone?
Would someone with a 7.3 database mind running the following query?
connect sys
desc dbms_system
exit;
Again, thanks in advance.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Nullius in verba
Upcoming events:
- Performance Diagnosis 101: 2/24 San Diego, 3/23 Park City, 4/6 Seattle
- Hotsos Symposium 2004: March 7–10 Dallas
- Visit www.hotsos.com for schedule details...
Please see the official ORACLE-L FAQ:
http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Received on Tue Feb 24 2004 - 16:16:57 CST
