On Thu, 13 May 1999, Gopal Raghavan wrote:
> Hi Ari:
>
> I have a couple of questions for you. Is the TKPROF utility
> available for Oracle 7.3.4 and Oracle8? I dont see any mention of this
> in Oracle8 books. If available, how does one use it? I remember
> having to input the FOREGROUND_DUMP_DEST parameter in the Init.ora file
> for Oracle V 6. Oracle8 does not permit me to put this parameter in
> the Init.ora file. The second question is, Is anybody using the
> Object-oriented features of Oracle8 for development, in the real world?
> Looks like the mixture of Object-oriented and relational features are
> more of a hinderance than enhancement. What do we have to do
> specifically as DBAs to accomodate object-orientedness? Your web page
> is the best!!
>
> Best Regards.
> Gopal Raghavan
>
Gopal,
Glad that you like my web page. I will answer your questions below:
1) TKPROF: Yes, it is still used but the FOREGROUND_DUMP_DEST is no longer
used. There is info in the Oracle docs on this. Here is the syntax:
Usage: tkprof tracefile outputfile [explain= ] [table= ]
[print= ] [insert= ] [sys= ] [sort= ]
table=schema.tablename Use 'schema.tablename' with 'explain=' option.
explain=user/password Connect to ORACLE and issue EXPLAIN PLAN.
print=integer List only the first 'integer' SQL statements.
aggregate=yes|no
insert=filename List SQL statements and data inside INSERT statements.
sys=no TKPROF does not list SQL statements run as user SYS.
record=filename Record non-recursive statements found in the trace
file.
sort=option Set of zero or more of the following sort options:
prscnt number of times parse was called
prscpu cpu time parsing
prsela elapsed time parsing
prsdsk number of disk reads during parse
prsqry number of buffers for consistent read during parse
prscu number of buffers for current read during parse
prsmis number of misses in library cache during parse
execnt number of execute was called
execpu cpu time spent executing
exeela elapsed time executing
exedsk number of disk reads during execute
exeqry number of buffers for consistent read during execute
execu number of buffers for current read during execute
exerow number of rows processed during execute
exemis number of library cache misses during execute
fchcnt number of times fetch was called
fchcpu cpu time spent fetching
fchela elapsed time fetching
fchdsk number of disk reads during fetch
fchqry number of buffers for consistent read during fetch
fchcu number of buffers for current read during fetch
fchrow number of rows fetched
userid userid of user that parsed the cursor
2) The object-relational features:
I do not know anyone who uses these. Basically, you can define your own
datatypes, nest tables, and have array-type columns. If you have a need
for them go for it, otherwise I do not know anyone using these features
yet. I heard that their performance is worse than having regular tables
joined together. This was as of 8.0.3.
Best regards,
-Ari Kaplan
Independent Oracle DBA Consultant
<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->
<-> For 295+ Oracle tips, visit my Web Page: <->
<-> <->
<-> www.arikaplan.com <->
<-> <->
<-> email: akaplan@interaccess.com <->
<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->
Back to Ari Kaplan's Home Page