setting Event dynamically
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: setting Event dynamically

Hybrid View

  1. #1
    Join Date
    Sep 2001
    Posts
    200

    setting Event dynamically

    Hi all,
    I'm running into some nasty ora 600. not really a show stopper but and Oracle says setting an event would suppress it. This is a prod box. My question is whether this event can be set dynamically?

    event = "10262 trace name context forever, level 4000"

    Thanks
    Tony
    Last edited by ndisang; 01-23-2007 at 11:00 AM.
    Life is what is happening today while you were planning tomorrow.

  2. #2
    Join Date
    Sep 2000
    Location
    Sao Paulo,SP,Brazil, Earth, Milky Way
    Posts
    350
    By "dinamically" you mean "without a db cycle" ??? If so : I donīt know specifically for 10262, BUT for all events what I needed until today, yes, I could to do an :

    sql> Alter session set events 'nnn trace name context nnn, level x';

    OR use oradebug, inside sqlplus, as :

    /u1/app/oracle>sqlplus /nolog

    SQL*Plus: Release 9.2.0.5.0 - Production on Ter Jan 23 13:16:08 2007

    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

    SQL> conn sys as sysdba
    Enter password:
    Connected.
    SQL> oradebug help
    HELP [command] Describe one or all commands
    SETMYPID Debug current process
    SETOSPID Set OS pid of process to debug
    SETORAPID ['force'] Set Oracle pid of process to debug
    DUMP [addr] Invoke named dump
    DUMPSGA [bytes] Dump fixed SGA
    DUMPLIST Print a list of available dumps
    EVENT Set trace event in process
    SESSION_EVENT Set trace event in session
    DUMPVAR [level] Print/dump a fixed PGA/SGA/UGA variable
    SETVAR Modify a fixed PGA/SGA/UGA variable
    PEEK [level] Print/Dump memory
    POKE Modify memory
    WAKEUP Wake up Oracle process
    SUSPEND Suspend execution
    RESUME Resume execution
    FLUSH Flush pending writes to trace file
    CLOSE_TRACE Close trace file
    TRACEFILE_NAME Get name of trace file
    LKDEBUG Invoke global enqueue service debugger
    NSDBX Invoke CGS name-service debugger
    -G Parallel oradebug command prefix
    -R Parallel oradebug prefix (return output
    SETINST Set instance list in double quotes
    SGATOFILE Dump SGA to file; dirname in double quotes
    DMPCOWSGA Dump & map SGA as COW; dirname in double quotes
    MAPCOWSGA Map SGA as COW; dirname in double quotes
    HANGANALYZE [level] Analyze system hang
    FFBEGIN Flash Freeze the Instance
    FFDEREGISTER FF deregister instance from cluster
    FFTERMINST Call exit and terminate instance
    FFRESUMEINST Resume the flash frozen instance
    FFSTATUS Flash freeze status of instance
    SKDSTTPCS Helps translate PCs to names
    WATCH
    Watch a region of memory
    DELETE watchpoint Delete a watchpoint
    SHOW watchpoints Show watchpoints
    CORE Dump core without crashing process
    IPC Dump ipc information
    UNLIMIT Unlimit the size of the trace file
    PROCSTAT Dump process statistics
    CALL [arg1] ... [argn] Invoke function with arguments

    try it....

    regards,

    Chiappa

  3. #3
    Join Date
    Sep 2001
    Posts
    200
    Quote Originally Posted by JChiappa
    By "dinamically" you mean "without a db cycle" ??? If so : I donīt know specifically for 10262, BUT for all events what I needed until today, yes, I could to do an :

    sql> Alter session set events 'nnn trace name context nnn, level x';

    OR use oradebug, inside sqlplus, as :

    /u1/app/oracle>sqlplus /nolog

    SQL*Plus: Release 9.2.0.5.0 - Production on Ter Jan 23 13:16:08 2007

    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

    SQL> conn sys as sysdba
    Enter password:
    Connected.
    SQL> oradebug help
    HELP [command] Describe one or all commands
    SETMYPID Debug current process
    SETOSPID Set OS pid of process to debug
    SETORAPID ['force'] Set Oracle pid of process to debug
    DUMP [addr] Invoke named dump
    DUMPSGA [bytes] Dump fixed SGA
    DUMPLIST Print a list of available dumps
    EVENT Set trace event in process
    SESSION_EVENT Set trace event in session
    DUMPVAR [level] Print/dump a fixed PGA/SGA/UGA variable
    SETVAR Modify a fixed PGA/SGA/UGA variable
    PEEK [level] Print/Dump memory
    POKE Modify memory
    WAKEUP Wake up Oracle process
    SUSPEND Suspend execution
    RESUME Resume execution
    FLUSH Flush pending writes to trace file
    CLOSE_TRACE Close trace file
    TRACEFILE_NAME Get name of trace file
    LKDEBUG Invoke global enqueue service debugger
    NSDBX Invoke CGS name-service debugger
    -G Parallel oradebug command prefix
    -R Parallel oradebug prefix (return output
    SETINST Set instance list in double quotes
    SGATOFILE Dump SGA to file; dirname in double quotes
    DMPCOWSGA Dump & map SGA as COW; dirname in double quotes
    MAPCOWSGA Map SGA as COW; dirname in double quotes
    HANGANALYZE [level] Analyze system hang
    FFBEGIN Flash Freeze the Instance
    FFDEREGISTER FF deregister instance from cluster
    FFTERMINST Call exit and terminate instance
    FFRESUMEINST Resume the flash frozen instance
    FFSTATUS Flash freeze status of instance
    SKDSTTPCS Helps translate PCs to names
    WATCH
    Watch a region of memory
    DELETE watchpoint Delete a watchpoint
    SHOW watchpoints Show watchpoints
    CORE Dump core without crashing process
    IPC Dump ipc information
    UNLIMIT Unlimit the size of the trace file
    PROCSTAT Dump process statistics
    CALL [arg1] ... [argn] Invoke function with arguments

    try it....

    regards,

    Chiappa

    Thnks,
    It appears that those "events" with "=" sign cannot be set dynamically.
    Life is what is happening today while you were planning tomorrow.

  4. #4
    Join Date
    Sep 2000
    Location
    Sao Paulo,SP,Brazil, Earth, Milky Way
    Posts
    350
    Nonsense, the "=" is just part of the syntax to set an event inside an initfile, ANY event setted in initfiles need it, this is NOT the stopper here..... The sintax showed is right, BOTH for oradebug and for ALTER SESSION (and you can use ALTER SYSTEM with the same syntax), but the point is : some events MUST be setted before the database is completely open (at startup-time), so such events works ONLY in initfiles... As I said, I do not use 10262, so I donīt know if it works out of the initfile, YOU will test it, in your test db, and (of course!!!) with Oracle Support help...

    []s

    Chiappa

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width