Autotrace Error

2012 - 3:30 am UTC Category: SQL*Plus – Version: 8.1.7 Latest Followup You Asked Hi Tom When I enter the statement set autotrace on i get the following error. SP2-0618: Cannot sp2-0618: cannot find the session identifier. find the Session Identifier. Check PLUSTRACE role is enabled SP2-0611: Error enabling STATISTICS sp2-0612: error generating autotrace explain report report How can solve it? and we said... set up autotrace... http://asktom.oracle.com/~tkyte/article1/autotrace.html has a howto. Reviews Write what is plustrace role in oracle a Review Tom September 28, 2002 - 1:21 pm UTC Reviewer: khalid from Yemen Thank you correct your script February 08, 2003 - 4:56 pm UTC Reviewer: A reader cd $oracle_home/rdbms/admin log

Ora-01919: Role 'plustrace' Does Not Exist

into sqlplus as system run SQL> @utlxplan run SQL> create public public synonym plan_table for plan_table run SQL> grant all on plan_table to public exit sqlplus and cd $oracle_home/sqlplus/admin log into sqlplus as SYS run SQL> @plustrce run SQL> grant plustrace to public Tom Please correct create public public synonym plan_table for plan_table Remove extra public Secondly why cant I run plustrce connect as sp2-0611: error enabling statistics report system, and why should I log out and login again... Lastly why cant I run all the above scripts connected as scott.. thanks Followup February 09, 2003 - 3:11 pm UTC removed the extra public.... you need to "log out and login" again because I want you to create the table as system -- but the grants need to be run as "sys" or "sysdba" because a) scott cannot create a public synonym b) scott cannot run plustrce.sql successfully. Why 'SYS' why not 'SYSTEM' February 09, 2003 - 9:48 pm UTC Reviewer: Nasser Tom I understand that SCOTT does not have necessary privileges to create public synonyms and create roles. But system does have those abilities, so then why connect as SYS why not as system and create the public synonym, and run the plustrce.sql script. Followup February 09, 2003 - 9:54 pm UTC Confusion on my part here. system does the public synonym: You ask " so then why connect as SYS why not as system and create the public synonym," well, SYSTEM created the public synonym in my example. system created the table and hence created the public syn

(13) Performance (2) SecureFiles and Large Objects (1) Security (1) Utilities (1) OCI/OCCI (1) Internals (1) Grid Control (19) TimesTen (14) Linux (9) Java (13) JDBC sp2-0611 error enabling statistics report 11g (8) JavaFX (4) Windows (5) VirtualBox (4) Grid Infrastructure (4) NetBeans

Sp2-0618 Sp2-0611

(2) Berkeley DB (2) JDeveloper (2) Golden Gate (2) Oracle Fusion Middleware (1) Weblogic (1) Video (1) MySQL

Cannot Set Autotrace

(1) Cloud Control (1) announcements (1) SET AUTOTRACE fails with error SP2-0618 by Eric Jenkinson on April 30, 2010 Categories: Troubleshooting Tagged: autotrace, plustrace Problem: You attempt to set autotrace https://asktom.oracle.com/pls/asktom/f?p=100:11:7768666760391491::::P11_QUESTION_ID:5671636641855 and receive the following error message. SQL> set autotrace traceonly; SP2-0618: Cannot find the Session Identifier. Check PLUSTRACE role is enabled SP2-0611: Error enabling STATISTICS report SQL> connect / as sysdba Solution: The user executing AUTOTRACE needs to have the PLUSTRACE role. By default the PLUSTRACE role does not exist and can be created by the SYS user with ORACLE_HOME/sqlplus/admin/plustrace.sql. http://www.oracledistilled.com/oracle-database/troubleshooting/set-autotrace-fails-with-error-sp2-0618/ The plustrace.sql creates the PLUSTRACE role and grants SELECT on V_$SESSTAT, V_$STATNME and V_$MYSTAT. PLUSTRACE is granted to the DBA role with ADMIN OPTION. For databases earlier than 10g you might also need to create the plan table. Execute the script ORACLE_HOME/rdbms/admin/utlxplan.sql to create the PLAN_TABLE. The PLAN_TABLE already exists on database version 10g and higher. Share this:FacebookTwitterRedditTumblrPrintEmail Comments Emma (September 20, 2011 4:34 pm) The paragon of undresatnding these issues is right here! zian (February 18, 2015 2:39 am) Thanks you very much info that could help someone on oracle 8.1 the script is plustrce.sql sk (August 29, 2016 4:54 am) to Zian Thanks for the info, although v. 8.1 is too old…. Post A Comment Click here to cancel reply. Name (required) Email (will not be published) (required) Notify me of follow-up comments by email. Notify me of new posts by email. Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! Email check failed, please try again Sorry, your blog cannot share posts by email.

Release http://myorastuff.blogspot.com/2008/06/how-do-we-enable-autotrace-on-oracle.html 9.2.0.1.0 - ProductionPL/SQL Release 9.2.0.1.0 - ProductionCORE 9.2.0.1.0 https://linux.die.net/man/1/autotrace ProductionTNS for 32-bit Windows: Version 9.2.0.1.0 - ProductionNLSRTL Version 9.2.0.1.0 - ProductionIf we don't set the autotrace, then we get the below error.SQL> connect scott/tiger@dba1Connected.SQL> set autotrace onSP2-0613: Unable to verify PLAN_TABLE format or existenceSP2-0611: error enabling Error enabling EXPLAIN reportSP2-0618: Cannot find the Session Identifier. Check PLUSTRACE role is enabledSP2-0611: Error enabling STATISTICS reportSQL>Here are the steps to resolve the error.Step 1 Run the plustrace.sql file on sys schema.In windows, the plustrace file is residing at @$ORACLE_HOME\sqlplus\admin\plustrce.sqlIn UNIX, the error enabling statistics plustrace file is residing at @$ORACLE_HOME/sqlplus/admin/plustrce.sqlSQL> start d:/oracle/ora92/sqlplus/admin/plustrce.sqlSQL>SQL> drop role plustrace;drop role plustrace*ERROR at line 1:ORA-01919: role 'PLUSTRACE' does not existSQL> create role plustrace;Role created.SQL>SQL> grant select on v_$sesstat to plustrace;Grant succeeded.SQL> grant select on v_$statname to plustrace;Grant succeeded.SQL> grant select on v_$session to plustrace;Grant succeeded.SQL> grant plustrace to dba with admin option;Grant succeeded.SQL>SQL> set echo offSQL>Step 2Grant the plustrace role to Scott schema.SQL> connect sys/password@dba1 as sysdbaConnected.SQL> grant plustrace to scott;Grant succeeded.SQL>Step 3Create the plan_table on sys schema and grant select privileges to Scott schema.SQL> connect sys/password@dba1 as sysdbaConnected.SQL> CREATE TABLE PLAN_TABLE (2 statement_id varchar2(30),3 plan_id number,4 timestamp date,5 remarks varchar2(4000),6 operation varchar2(30),7 options varchar2(255),8 object_node varchar2(128),9 object_owner varchar2(30),10 object_name varchar2(30),11 object_alias varchar2(65),12 object_instance numeric,13 object_type varchar2(30),14 optimizer varchar2(255),15 search_columns number,16 id numeric,17 parent_id numeric,18 dep

angle] [-despeckle-level int] [-despeckle-tightness real] [-dpi int] [-error-threshold real] [-filter-iterations int] [-help] [-input-format format] [-line-reversion-threshold real] [-line-threshold real] [-list-input-formats] [-list-output-formats] [-log] [-output-file file] [-output-format format] [-preserve-width] [-remove-adjacent-corners] [-report-progress] [-debug-arch] [-debug-bitmap] [-tangent-surround int] [-version] [-width-factor real] inputfile Description The autotrace program accepts bitmap graphics from the file inputfile specified on the command line, and as output produces a collection of splines approximating the original image, the converting the image from bitmap to vector format. It behaves in a manner similar to the commercial software known as *tream*ine or *orel*race. The result is sent to standard output unless the -output-file option is active. Options Options can begin with either -- or -. Any unambiguous abbreviation can be used for the option name. Option names and values can be separated with either a space or equal sign (=). -background-color hexvalue Employ the color specified by the hexadecimal code hexcode as the background that should be ignored, for example FFFFFF (default: no background color). -centerline Trace an object's centerline (default: employ its outline). -color-count int Reduce the bitmap to using the number of colors specified by the unsigned integer int (range: 1-256). The default value of 0 indicates that no color reduction is to be done. Does not work with grayscale images. -corner-always-threshold angle Consider any angle at a pixel which falls below the specified angle (in degrees) as a corner, even if it is bordered by other corner pixels (default: 60). -corner-surround int Consider the specified number of pixels on either side of a point when determining if that point is a corner (default: 4). -corner-thresholdangle Consider any pixel which forms an angle with its predecessor(s) and successor(s) that is smaller than the specified angle (in degrees) as a corner (default: 100). -despeckle-level int Employ the specified integer (range: 1