SQL Tracing

Hi,
in 8.49 tools version,
It's a part of psappsrv.cfg file :
[Trace]
;=========================================================================
; Server Trace settings
;=========================================================================
; SQL Tracing Bitfield
; Bit Type of tracing
; 1 - SQL statements
; 2 - SQL statement variables
; 4 - SQL connect, disconnect, commit and rollback
; 8 - Row Fetch (indicates that it occurred, not data)
; 16 - All other API calls except ssb
; 32 - Set Select Buffers (identifies the attributes of columns
; to be selected).
; 64 - Database API specific calls
; 128 - COBOL statement timings
; 256 - Sybase Bind information
; 512 - Sybase Fetch information
; 1024 - SQL Informational Trace
; 4096 - Manager information
; 8192 - Mapcore information
; Dynamic change allowed for TraceSql and TraceSqlMask
TraceSql=?
TraceSqlMask=?
which values should be given for TraceSql=? and TraceSqlMask=? to enable the followings :
- SQL statements
- SQL statement variables
- SQL connect, disconnect, commit and rollback
- Row Fetch (indicates that it occurred, not data)
If you suggest a value please explain how/why you have chosen it.
Many thanks.

Thank you Nicolas.
Why there is also something similar in PSPRCS.cfg :
Trace settings
;=========================================================================
; PeopleTools trace file (NT only, ignored on UNIX)
TraceFile=%PS_SERVDIR%\logs\PeopleTools.trc
; SQL Tracing Bitfield
; Bit Type of tracing
; 1 - SQL statements
; 2 - SQL statement variables
; 4 - SQL connect, disconnect, commit and rollback
; 8 - Row Fetch (indicates that it occurred, not data)
; 16 - All other API calls except ssb
; 32 - Set Select Buffers (identifies the attributes of columns
; to be selected).
; 64 - Database API specific calls
; 128 - COBOL statement timings
; 256 - Sybase Bind information
; 512 - Sybase Fetch information
; 1024 - SQL Informational Trace
; Dynamic change allowed for TraceSql and TraceSqlMask
TraceSQL=0
What is the difference ?
Thanks again.

Similar Messages

Enabling SQL Tracing for an instance

Hi,
I am aware that SQL_TRACE init parameter is deprecated :
Oracle® Database Upgrade Guide
10g Release 2 (10.2)
Part Number B14238-01
Initialization Parameters Deprecated in Release 10.2
SQL_TRACE
So I searched the recommended way of enabling sql tracing for an instance and I found :
Oracle® Database Performance Tuning Guide
10g Release 2 (10.2)
Part Number B14211-01
20.4.2 Step 2: Enabling the SQL Trace Facility
You can enable the SQL Trace facility for an instance by setting the value of the SQL_TRACE initialization parameter to TRUE in the initialization file.
Well, the Tuning guide should not mention deprecated parameter, should it?
Anyway, I found later that the recommended way is to use
exec DBMS_MONITOR.DATABASE_TRACE_ENABLEPlease update your tuning guide.
Cam on rat nieu ;-)

Laurent,
Sorry to post a reply after nearly 2 years :-)
But:
Does dbms_monitor.database_trace_enable() only trace existing sessions or does it also enable tracing for all new sessions?
I've been consulting the documentation and searching on the Internet but I can't determine this.
Cheers & thanks,
Colin

SQL tracing in ADR

Hi,
I've a question and needs calrification. As in 11g $ADR_HOME/trace holds the information of background process tracing and SQL tracing. Now I want to know how can we seperate the SQL tracing files and BG tracing files. Let say its not possible and both are written in single trace files, then my question is can we extract SQL tracing information from this single file through tkprof.
I'm not sure weather BG tracing is enabled by default or not. Please clarify it as we have to explicityly enabled the SQL tracing.
Looking for your information.
Regards,
Abbasi

I think that it would be hard to tell which file belongs to the background process or which one to the foreground process just by looking at the files. We must know the process id and then use it to track the file. The trace folder contains both the Background and User_Dump_Dest combined in it so it contains both the files. Background tracing is not on( I think that there is no such concept called background tracing) and the trace file would be generated when the process would be abruptly terminated.
Just my 2 cents.
Aman....

Enabling SQL Tracing for already connected session

Hi,
I've a requirement. i.e. my users are connected to db through schema making sessions( As multiple users are connected from single Schema). Now there are certian users which have to run batch jobs and I want to trace there SQL for tunning. I want to know how can I enable SQL tracing for specific user,session,id since it is difficult to trace exact user as multiple users are running the batch jobs.
I have a strategy to enable tracing at schema level. Can I do this while users are connected and running quries. As normally first we enable the tracing and then run the quries.
Kindly help me in working out this.
Regards,
Abbasi

You didn't post your Oracle version, but maybe you have DBMS_MONITOR available to you.
Hope this helps!

Enabling SQL tracing from Forms

Hi...
can I enable SQL tracing for Particular instance or session from my 6i/9i forms.I can do it directly from database but what if i want to do it from Forms programatically or forms provides something which can help me ....
any idea ???
Thanx in advance

REPOST

Setting SQL TRACING

Hi ,
I want to set Sql tracing on in my machine.
I am using the oracle 9i Database (9.2.0.4.0).
My operating system is windows 2000 professional.
Can anyone tell me how to enable SQL tracing in my database and wat is the use of it.
Thanks...

http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96533/sqltrace.htm#8760

Enable SQL Tracing for Session

Hi,
I know how to enable SQL tracing for a session created either through SQL*Plus or like similar tool, but I want to explore is there any way to can we enable sql tracing for a single session which is connected to database through an application.
ssome time for testing purpose we have a requirement to enable tracing for that user which run batch Job. Now that particular user gets connected to database through application and i want to enable tracing right at that moment. How can I accomplish it.
Regards,
Ababsi

If you don't want to identify database session you can try to create a logon trigger to enable tracing for all database sessions created by a specific Oracle user account. In the following example you need to replace UWCLASS with the Oracle user account for which you want to trace sessions:
CREATE OR REPLACE TRIGGER trace_trig
AFTER LOGON
ON DATABASE
DECLARE
sqlstr VARCHAR2(200) := 'ALTER SESSION SET EVENTS ''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12''';
BEGIN
IF (USER = 'UWCLASS') THEN
execute immediate sqlstr;
END IF;
END trace_trig;
/Reference:
http://psoug.org/reference/system_trigger.html
If you want to identify database session you need to query V$SESSION to retrieve SID and SERIAL# of the session you want to trace and then you can use DBMS_MONITOR. See examples in http://www.oracle-base.com/articles/10g/SQLTrace10046TrcsessAndTkprof10g.php
Edited by: P. Forstmann on 15 janv. 2011 11:07

AWR SQL TRACING

Hi all,
I want to produce sql tracing using AWR.
But i can not find the hits in google for "AWR sql tracing".
Kindly assist what is the right keywords.
Thanks a lot.

Hi,
AWR doesn't provide any chronological information. It provides aggregate statistics per snapshots. For example you can use it to find out what was top SQL during that snapshot, and how many times it was executed, but you won't be able to see who was doing what at what moment in time. For that you would have to use ASH -- just run the query I gave you (add "order by sample_time", I forgot that part) and see what kind of information it gives you.
Tracing the entire database would also give you information about SQL run by every user, but I wouldn't recommend that for several reasons:
1) there will be a performance overhead
2) trace files grow very fast, and they can eat up all your free space in the matter of minutes
3) trace files are harder to read (if you want them formatted nicely, then you'll have to do some additional processing like running tkprof)
And to reiterate: the tool of choice for monitoring user activity is not ASH, not trace, not AWR, but audit. So I would approach your problem as follows:
1) use ASH to find out who was doing what at the period of interest
2) enable audit to facilitate such investigations in the future
Best regards,
Nikolay

SQL Tracing for session started from Java code

I am working with Oracle 10g on Solaris 9. I am facing a problem when trying to enable SQL Trace for Oracle sessions initiated from Weblogic server. I am querring V$SESSION to get the SID and SERIAL# of those sessions and then using DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION(<sid>, <serial#>, TRUE); from the SQLPlus (using sys login). But the trace file is not being generated in UDUMP even after some queries are fired from the application. But when I am using the same procedure to turn SQL Trace on for SQLPlus sessions or SQLDeveloper sessions, they are just working fine.
Can anyone please help me out?

Please help.....
There is already a thread
Problem with SQL_Trace for a Session
but there is no solution there.

SQL tracing and TKPROF tool, how to get object name

Hi,
I set sql_trace = ture for my session.
Then I use TKPROF (on trace file) to get the explain plan (for my stored procedure). but the explain plan shows obj# (object number), HOW do I get TKPROF to show object name on explain plan (I have checked the SYBEX book, it has no info on that)?
Also can you get explain plan from SQL (without sql_trace) for stored procs, if so HOW?
Thanks

SELECT
SERVERPROPERTY('MachineName') AS [ServerName],
SERVERPROPERTY('ServerName') AS [ServerInstanceName],
SERVERPROPERTY('InstanceName') AS [Instance],
SERVERPROPERTY('Edition') AS [Edition],
SERVERPROPERTY('ProductVersion') AS [ProductVersion],
Left(@@Version, Charindex('-', @@version) - 2) As VersionName
|
Blog: MSBICOE.com |
MCITP - BI, SQL Developer & DBA
Hate to mislead others, if I'm wrong slap me. Thanks!

SQL Tracing in TimesTen with actual data visible

Hi,
We're having some issues with our TimesTen-based application where under some circumstances (it appears to increase under load) the results appear to get 'mixed up', i.e. a query appears to not have received the right result set from the database. I know the result set is wrong because we're doing performance testing where each query should actually return exactly the same.
I also say 'appears' because I think the problem is on the client side, where multiple threads access the database simultaneously and somehow things get mixed up. This happens so deep in the application that increasing the logging on client side didn't tell me what I need to know thus far.. And before I look further, I want to exclude the possibility that the database is mixing up results from queries processed in parallel.
To accomplish that I would like to enable a TimesTen trace in ttTraceMon where the actual data returned as a result set to the client is visible. Is this possible? There are a lot of components you can trace, I haven't tried them all but at least the SQL component does not show this information, not even at the highest trace level.
Is there any way to get a view of the actual result set that is being returned to a client, before that client's driver or the application (we use JDBC) actually interprets the results?
Any clues are greatly appreciated! Thanks in advance.
We use TimesTen 11.2.2.
Kind regards,
Pieter van Wijngaarden

The answer sadly is no. There is not currently any trace level that will show data values.
If you really need to share database connections between application threads then it should be done very carefully. Some rules to observe are:
1. When a thread is using a connection it should have exclusive use of it. Do not allow multiple threads to make concurrent use of the same connection; TimesTen has internal mutex protection to avoid this causing problems for the database but due to the nature of the ODBC and JDBC APIs it is very hard at an application level to ensure correctness with this approach.
2. Many objects (statements, result sets etc.) are closely associated with a specific connection. When a thread has 'relinquished control' of a connection it should not then manipulate any object associated with that connection in any way whatsoever.
For example:
1. Thread 1 'reserves' connection 1.
2. Thread 1 issues a query on connection 1 and obtains a result set.
3. Thread 1 'releases' connection 1.
4. Thread 2 'reserves' connection 1 and starts to do some work.
5. Thread 1 starts to process values from the result set obtained in step 2.
At this point you have two threads working concurrently on connection 1 and all bets are off (and certainly you will see problems).
Code that violates these rules may seem to work okay with some databases but not with others. That is not the fault of the database but just a happy coincidence. This code pattern is just incorrect.
Also please note that, unlike Oracle DB, in TimesTen a commit or rollback operation on a connection closes / invalidates all result sets associated with that connection so again if you share connections in a way similar to the above this can also cause you problems.
Good luck with your debugging.
Chris
Edited by: ChrisJenkins on Jan 30, 2013 10:03 AM

Sql tracing in 10g

Hi,
I need to trace the sql statements in 10g in linux so that as sys as sysdba i have entered the command
alter session set sql_trace=true;
session altered
Now i need to know the location where i can find the sql statements pls help me

Check USER_DUMP_DEST init. parameter. See http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/sqltrace.htm#g22503.
Example with a SQL*Plus SYSDBA connection :
SQL> show parameter user_dump_dest
NAME                                 TYPE        VALUE
user_dump_dest                       string      C:\ORACLEXE\APP\ORACLE\ADMIN\X
                                                 E\UDUMPEdited by: P. Forstmann on 14 janv. 2010 09:35

Missing or invalid version of SQL library PSORA (200,0)

I am trying to configure App. Server on Vista laptop machine.
The machine name is VRGhati03.
It is a logical 3 tier archtecture. Its a EPM 9.0 Install. My database (PFDMO) is all configured and I am able to signon using a User ID VP1 and password VP1. My connect id is people with password of peop1e.
My access id is SYSADM.
I have created a user id in Oracle as VP1 and granted him the PSADMIN role .
When I try to boot up the App. Server it tells me ' Missing or invalid version of SQL Library PSORA' and 'Could not sign on to database PFDMO with user VP1'
The VP1 sign on works via SQLPLUS.
I also created a User Account of VP1 and tried to boot the appserver under that id but still no success.
I have gone thru some of the postings on this topic but they have not helped me. What am I doing wrong?
Below are the details of the log files, portion of my psappserv.cng file and the system environment variables.
Can somebody help. Thanks in advance
Sudhir
I) Log from APPSERV:
PSADMIN.10000 (0) [08/05/09 09:19:24](0) Begin boot attempt on domain PFDMO
PSWATCHSRV.2556 (0) [08/05/09 09:19:33] Checking process status every 120 seconds
PSWATCHSRV.2556 (0) [08/05/09 09:19:33] Server started
PSAPPSRV.5636 (0) [08/05/09 09:19:34](0) PeopleTools Release 8.49 (WinX86) starting
PSAPPSRV.5636 (0) [08/05/09 09:19:34](0) Cache Directory being used: C:\PT8.49\appserv\PFDMO\CACHE\PSAPPSRV_2\
PSAPPSRV.5636 (0) [08/05/09 09:19:34](1) GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library PSORA (200,0)
PSAPPSRV.5636 (0) [08/05/09 09:19:34](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database PFDMO with user VP1.
PSAPPSRV.5636 (0) [08/05/09 09:19:34](0) Server failed to start
PSWATCHSRV.2556 (0) [08/05/09 09:19:35] Shutting down
PSADMIN.10000 (0) [08/05/09 09:19:41](0) End boot attempt on domain PFDMO
II) Log from TUXLOG:
091924.VRGHATI03!PSADMIN.10000: Begin attempt on domain PFDMO
091927.VRGHATI03!tmadmin.9844.8684.-2: TMADMIN_CAT:1330: INFO: Command: boot -A
091929.VRGHATI03!tmboot.9720.8272.-2: 08-05-2009: Tuxedo Version 9.1, 32-bit
091929.VRGHATI03!tmboot.9720.8272.-2: CMDTUX_CAT:1851: INFO: TM_BOOTTIMEOUT is set to 60 seconds
091929.VRGHATI03!tmboot.9720.8272.-2: CMDTUX_CAT:1855: INFO: TM_BOOTPRESUMEDFAIL option is selected
091931.VRGHATI03!BBL.8340.3320.0: 08-05-2009: Tuxedo Version 9.1, 32-bit, Patch Level 036
091931.VRGHATI03!BBL.8340.3320.0: LIBTUX_CAT:262: INFO: Standard main starting
091933.VRGHATI03!tmboot.9224.8412.-2: 08-05-2009: Tuxedo Version 9.1, 32-bit
091933.VRGHATI03!tmboot.9224.8412.-2: CMDTUX_CAT:1851: INFO: TM_BOOTTIMEOUT is set to 60 seconds
091933.VRGHATI03!tmboot.9224.8412.-2: CMDTUX_CAT:1855: INFO: TM_BOOTPRESUMEDFAIL option is selected
091933.VRGHATI03!PSWATCHSRV.2556.9492.-2: 08-05-2009: Tuxedo Version 9.1, 32-bit
091933.VRGHATI03!PSWATCHSRV.2556.9492.-2: LIBTUX_CAT:262: INFO: Standard main starting
091934.VRGHATI03!PSAPPSRV.5636.9008.0: 08-05-2009: Tuxedo Version 9.1, 32-bit
091934.VRGHATI03!PSAPPSRV.5636.9008.0: LIBTUX_CAT:262: INFO: Standard main starting
091934.VRGHATI03!PSAPPSRV.5636.9008.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
091934.VRGHATI03!tmboot.9224.8412.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
091938.VRGHATI03!BBL.8340.3320.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
091941.VRGHATI03!PSADMIN.10000: End boot attempt on domain PFDMO
III) System Environmental Variables:
LIBPATH=c:\oracle\product\10.2.0\db_1\LIB
ORACLE_SID=PFDMO
OS=Windows_NT
path=C:\oracle\product\10.2.0\db_1\bin;C:\product\10.1.3.1\OracleAS_1\jdk\bin;C:\product\10.1.3.1\OracleAS_1\ant\bin;C:\product\10.1.3.1\OracleAS_1\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files (x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Shared\10.0\DLLShared\;c:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\bea\Tuxedo9.1\bin
TUXDIR=C:\bea\Tuxedo9.1
IV) psappserv.cfg File:
[Startup]
;=========================================================================
; Database Signon settings
;=========================================================================
DBName=PFDMO
DBType=ORACLE
UserId=VP1
UserPswd=tRWpMM0Cragi9I0nrWPAxZ+GS1YD0PRXzCrF4YWbe5E=
ConnectId=people
ConnectPswd=kyD3QPxnrag=
ServerName=VRGhati03
[Database Options]
;=========================================================================
; Database-specific configuration options
;=========================================================================
SybasePacketSize=
UseLocalOracleDB=0
;ORACLE_SID=
EnableDBMonitoring=1
OracleDisableFirstRowsHint=0
[Security]
;=========================================================================
; Security settings
;=========================================================================
Validate Signon with Database=0
[Workstation Listener]
;=========================================================================
; Settings for Workstation Listener
;=========================================================================
Address=%PS_MACH%
Port=7000
Encryption=0
Min Handlers=1
Max Handlers=3
Max Clients per Handler=40
Client Cleanup Timeout=60
Init Timeout=5
Tuxedo Compression Threshold=5000
[JOLT Listener]
;=========================================================================
; Settings for JOLT Listener
;=========================================================================
Address=%PS_MACH%
Port=9000
Encryption=0
Min Handlers=5
Max Handlers=7
Max Clients per Handler=40
Client Cleanup Timeout=10
Init Timeout=5
Client Connection Mode=ANY
Jolt Compression Threshold=1000000
[JOLT Relay Adapter]
;=========================================================================
; Settings for JOLT Relay Adapter (JRAD)
;=========================================================================
Listener Address=%PS_MACH%
Listener Port=9100
[Domain Settings]
;=========================================================================
; General settings for this Application Server.
;=========================================================================
Domain ID=PFDMO
Add to PATH=c:\oracle\product\10.2.0\db_1\BIN
Spawn Threshold=1,600:1,1
Restartable=Y
;Log Directory=%PS_SERVDIR%\LOGS
; This allows for dynamic changes to certain setting without having to reboot
; the domain. The settings that can be dynamically changed are: Recycle Count,
; Consecutive Service failures, Trace SQL, Trace Mask SQL, TracePC, TracePCMask,
; TracePpr, TracePprMask, TracePIA, TracePIAMask, Log Fence, Enable DB Monitoring,
; Enable Debugging, LogErrorReport, MailErrorReport, DumpMemoryImageAtCrash
; These settings are further identified by the "Dynamic change allowed for .."
; comment.
Allow Dynamic Changes=N
; Logging detail level
; Level Type of information
; -100 - Suppress logging
; -1 - Protocol, memory errors
; 0 - Status information
; 1 - General errors
; 2 - Warnings
; 3 - Tracing Level 1 (default)
; 4 - Tracing Level 2
; 5 - Tracing Level 3
; Dynamic change allowed for LogFence
LogFence=3
; Trace-Log File Character Set: Character set used for log and trace files
Trace-Log File Character Set=ANSI
[PeopleCode Debugger]
;=========================================================================
; PeopleCode Debug Server settings
;=========================================================================
PSDBGSRV Listener Port=9500
; PeopleCode Debugger Trace Settings
; Level Type of tracing
; 0 Off (default)
; 1 Level 1 - log connection activity
; 2 Level 2 - log debug broker transactions (getsession, register/unregister, acquire/unacquire)
; 3 Level 3 - log primary debuggee/debugger transactions (register, modechange, seteventflag, break)
; 4 Level 4 - log debuggee/debugger variables transactions
; 5 Level 5 - log debuggee/debugger command responses and gotbreaks
; Warning: Levels 3 thru 5 result in lots of transaction data being logger and require plenty of disk space.
DebuggerMsgLogEnable=0
[Trace]
;=========================================================================
; Server Trace settings
;=========================================================================
; SQL Tracing Bitfield
; Bit Type of tracing
; 1 - SQL statements
; 2 - SQL statement variables
; 4 - SQL connect, disconnect, commit and rollback
; 8 - Row Fetch (indicates that it occurred, not data)
; 16 - All other API calls except ssb
; 32 - Set Select Buffers (identifies the attributes of columns
; to be selected).
; 64 - Database API specific calls
; 128 - COBOL statement timings
; 256 - Sybase Bind information
; 512 - Sybase Fetch information
; 1024 - SQL Informational Trace
; 4096 - Manager information
; 8192 - Mapcore information
; Dynamic change allowed for TraceSql and TraceSqlMask
TraceSql=0
TraceSqlMask=12319
; PeopleCode Tracing Bitfield
; Bit Type of tracing
; 1 - Trace Evaluator instructions (not recommended)
; 2 - List Evaluator program (not recommended)
; 4 - Show assignments to variables
; 8 - Show fetched values
; 16 - Show stack
; 64 - Trace start of programs
; 128 - Trace external function calls
; 256 - Trace internal function calls
; 512 - Show parameter values
; 1024 - Show function return value
; 2048 - Trace each statement in program (recommended)
; Dynamic change allowed for TracePC and TracePCMask
TracePC=0
TracePCMask=4095
; Panel Processor Tracing Bitfield
; Bit Type of tracing
; 1 - Log extra debug messages
; 2 - Dump panel after build
; 4 - Dump buffers after PPRInit
; 8 - Dump buffers before/after service
; 16 - Dump buffers after scrollselect
; 32 - Dump buffers after modal panel
; 64 - Dump buffers before save
; 128 - Dump buffers after insertrow
; 256 - Trace default processing
; 512 - Dump PRM data
; 1024 - Show function return value
; 2048 - dump memory statistics
; 4096 - Trace related display processing
; 8192 - Trace keylist generation
; 16384 - Trace work record settings
; Dynamic change allowed for TracePPR and TracePPRMask
TracePPR=0
TracePPRMask=32767
; PIA Page Generation Tracing Bitfield
; Bit Type of tracing
; 1 - Log page generation errors
; 2 - Show table layout via cell borders in generated page
; 4 - Annotate field overlap in HTML source
; 8 - Detailed trace of table generation algorithm
; 16 - Inline stylesheet in generated pages
; 32 - Inline javascript in generated pages
; 64 - QATesting - annotation and extra tags needed by Robot
; 128 - Format source. Make HTML more readable
; 256 - Save File. Save each generated page in log directory
; 512 - Debug JavaScript. Include debug functions in page
; 1024 - Log form data. Log all request parameters on each service
; 2048 - Log key errors. Write log message for unrecognized query parameters.
; Dynamic change allowed for TracePIA and TracePIAMask
TracePIA=0
TracePIAMask=32767
; AE Tracing Bitfield
; Bit Type of tracing
; 1 - Trace STEP execution sequence to AET file
; 2 - Trace Application SQL statements to AET file
; 4 - Trace Dedicated Temp Table Allocation to AET file
; 8 - not yet allocated
; 16 - not yet allocated
; 32 - not yet allocated
; 64 - not yet allocated
; 128 - Timings Report to AET file
; 256 - Method/BuiltIn detail instead of summary in AET Timings Report
; 512 - not yet allocated
; 1024 - Timings Report to tables, ignored if Process Instance is 0
; 2048 - DB optimizer trace to file
; 4096 - DB optimizer trace to tables
; 8192 - Transform trace
TraceAE=0
; Analytic Server Tracing Bitfield
; MostSignificantBit -> LeastSignificantBit
; QAS |ACE MODEL | ACE CALC | ACE API| Plugin | DCache | Utils | Analytic Server |
; 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
; Bit Type of tracing 3 bits per component (octal word)
; 1 - Analytic Server LSB
; 2 - Analytic Server MSB LSB LogFence
; 4 - Analytic Server MSB --- --- --------------------
; 8 - Utilities LSB 0 0 0 0 (Severity_Status)
; 16 - Utilities 0 0 1 1 (Severity_Error)
; 32 - Utilities MSB 0 1 0 2 (Severity_Warn)
; 64 - DataCache LSB 0 1 1 3 (Severity_Info)
; 128 - DataCache 1 0 0 4 (Severity_Trace1)
; 256 - DataCache MSB 1 0 1 5 (Severity_Trace2)
; 512 - Plug-in LSB 1 1 0 6 (not used)
; 1024 - Plug-in 1 1 1 7 (not used)
; 2048 - Plug-in MSB
; 4096 - ACE API LSB
; 8192 - ACE API
; 16384 - ACE API MSB
; 32768 - ACE CALC LSB
; 65536 - ACE CALC
; 131072 - ACE CALC MSB
; 262144 - ACE MODEL LSB
; 524288 - ACE MODEL
; 1048576 - ACE MODEL MSB
; 2097152 - QAS LSB
; 4194304 - QAS
; 8388608 - QAS MSB
; The bits enable logging for OptEngine components beyond the standard
; LogFence setting. E.g., TraceAnalytic=14380470 sets full trace on all components.
; Using 110 (1 greater than Severity_Trace2) for each component:
; OptEng: 4 + 2
; Utils : 32 + 16
; DC : 256 + 128
; Plugin: 2048 + 1024
; ACE API: 16384 + 8192
; ACE CALC: 131072 + 65536
; ACE MODEL: 1048576 + 524288
; QAS : 8388608 + 4194304
; Total : 14380470
TraceAnalytic=9586980
TraceAnalyticMask=16777215
; Performance Monitor Tracing Bitfield
; Bit Type of tracing
; 1 - Trace All performance monitor agent activity
TracePPM=0
; Create a memory image of the failing process during a crash
; Setting Meaning
; NONE no memory image
; MINI mini memory image
; FULL full memory image
; If set to MINI or FULL, when a crash occurs, a memory.dmp file is
; generated under <log directory>/<server name>.<process id>.
; Dynamic change allowed.
DumpMemoryImageAtCrash=NONE
;If set to Y, when a crash occurs, the application server process will write
;additional information to help in debugging the crash that occurred.
;This consists of the customized object definitions for reproducing
;the request on another database.
DumpManagerObjectsAtCrash=Y
; If set to Y, when a runtime error is detected, the message and a dump of
; the application state will be written to the current log file.
; Dynamic change allowed.
LogErrorReport=N
; When set to an email address, an email will be sent when an error report
; or a crash dump is written to the log.
; Dynamic change allowed.
MailErrorReport=
[Cache Settings]
;==============================================================================================
; Settings for managed object caching;
; Default EnableServerCaching=2, ServerCacheMode=0
; Default CacheBaseDir=%PS_SERVDIR% if defined else %PS_HOME/<domain name>/cache
; You can change these values by uncommenting and setting to the desired value
;==============================================================================================
; EnableServerCaching -
; 0 Server file caching disabled
; 1 Server file caching limited to most used classes
; 2 Server file caching for all types
;EnableServerCaching=2
; CacheBaseDir = the base file cache directory
;CacheBaseDir=%PS_SERVDIR%
; ServerCacheMode
; 0 One file cache directory per app server process
; 1 One file cache directory per domain (shared file cache, needs to be preloaded)
;ServerCacheMode=0
; Deprecated cache settings : MaxInMemoryObjects
; MaxCacheMemory - controls cache memory pruning
; 0 cache memory pruning disabled
; >0 max size of memory cache in MBytes
MaxCacheMemory=0
; Preload Cache projects for file and in memory cache
;PreloadFileCache=
;PreloadMemoryCache=
[RemoteCall]
;=========================================================================
; Settings for RemoteCall
;=========================================================================
; RemoteCall child process output redirection
; If this parameter is non-zero, the child process output is saved to
; <Domain Settings\Log Directory>\<program>_<oprid>.out, and any error
; output is saved to <program>_<oprid>.err.
; By default, the output is not saved
RCCBL Redirect=0
; Location of COBOL programs
; NT/Windows 2000: By default, RemoteCall looks for the COBOL programs in
; %PS_HOME%\cblbin%PS_COBOLTYPE%. PS_COBOLTYPE is automatically set when
; the application server is started. The value depends upon the database.
; Possible values:
; PS_COBOLTYPE = A (non-Unicode)
; PS_COBOLTYPE = E (EBCDIC)
; PS_COBOLTYPE = U (Unicode)
; UNIX: By default, RemoteCall looks for the COBOL programs in $PS_HOME/cblbin.
; You can override the default setting by commenting out the appropriate
; line and modifying the setting to fit your requirements.
; NT/Windows 2000:
;RCCBL PRDBIN=%PS_HOME%\cblbin%PS_COBOLTYPE%
; UNIX:
;RCCBL PRDBIN=%PS_HOME%/cblbin
[PSAPPSRV]
;=========================================================================
; Settings for PSAPPSRV
;=========================================================================
; UBBGEN settings
Min Instances=3
Max Instances=3
Service Timeout=300
; Number of services after which PSAPPSRV will automatically restart.
; If the recycle count is set to zero, PSAPPSRV will never be recycled.
; The default value is 5000.
; Dynamic change allowed for Recycle Count
Recycle Count=5000
; Percentage of Memory Growth after which PSAPPSRV will automatically restart.
; Default is 20, meaning additional 20% of memory growth after the process has
; built up its memory cache.
; Uncomment the setting to use memory growth instead of Recycle Count at
; determining the restart point.
; Percentage of Memory Growth=20
; Number of consecutive service failures after which PSAPPSRV will
; automatically restart.
; If this is set to zero, PSAPPSRV will never be recycled.
; The default value is zero.
; Dynamic change allowed for Allowed Consec Service Failures
Allowed Consec Service Failures=2
; Max Fetch Size -- max result set size in KB for a SELECT query
; Default is 5000KB. Use 0 for no limit.
Max Fetch Size=5000
; Automatically select prompt, 1 = yes, 0 = no
Auto Select Prompts=1
; This parameter is used for Tuxedo Queue Thresold Determination (used forPub/Sub
; processing only). This parameter is the actual Tuxedo message queue size.
; This is a kernel parameter in Unix. For Windows, look in BEA Tuxedo, IPC Resources.
; A value of 0 will disable Tuxedo Queue threshold Determination and usage.
; A value of -1 will use these defaults: Windows = 65535, AIX = 4000000,
; Solaris = 65535, HP = 65535
Tuxedo Queue Size=65535
[PSANALYTICSRV]
;=========================================================================
; Settings for PSANALYTICSRV
;=========================================================================
; UBBGEN settings
Min Instances=3
Max Instances=3
; Number of Analytic Instances an Analytic Server instance will load and
; unload before recycling. If the recycle count is set to zero, the
; Analytic Server will never be recycled.
; The default value is 1.
; Dynamic changes to this setting are allowed. A dynamic change will
; affect running Analytic Servers.
;Recycle Count=1
; Number of minutes an analytic instance will remain loaded without being
; accessed when it is auto-loaded by the analytic grid or when a
; PeopleCode program loads the instance with a timeout value of -1.
; The default value is 30
; Setting this to zero will disable timeouts for auto-loaded instances.
; Dynamic changes to this setting are allowed.
;Analytic Instance Idle Timeout=30
; Setting this to 1 will cause each analytic server to log to it's own
; file rather than the common PSANALYTICSRV_<Month|Day>.LOG file. The
; individual log files will include the Tuxedo server ID.
; Dynamic changes to this setting are allowed. Changes will only come
; into affect for running analytic servers when they are recycled.
; The default value is 0
;Analytic Per Server Log=1
; This setting determines what is the threshold to enable file swaping
; in ACE. Each data block is of 6K. Each data cube is divided into multiple
; data blocks. In batch environment this could be configured to a higher value.
; The default value is 1024 blocks. If set to zero, the disk swaping is disabled.
;ACE Max Memory Data Blocks=1024
; Queue size for data loading in batches. If set to zero, batch loading is disabled.
;ACE Load Queue Size=100000
[PSSAMSRV]
;=========================================================================
; Settings for PSSAMSRV
;=========================================================================
; UBBGEN settings
; PSSAMSRV never spawns, so we set Instances instead of setting a Min and
; Max value for Instances.
Min Instances=1
Max Instances=3
Service Timeout=300
; Number of services after which PSSAMSRV will automatically restart.
; If the recycle count is set to zero, PSSAMSRV will never be recycled.
; The default value is zero.
Recycle Count=100000
; Number of consecutive service failures after which PSSAMSRV will
; automatically restart.
; If this is set to zero, PSSAMSRV will never be recycled.
; The default value is zero.
Allowed Consec Service Failures=2
; Max Fetch Size -- max result set size in KB for a SELECT query
; Max Fetch Size=n indicates n * 1024 bytes
; Default is 32KB. Use 0 for no limit
Max Fetch Size=32
[PSQCKSRV]
;=========================================================================
; Settings for PSQCKSRV
;=========================================================================
; UBBGEN settings
Min Instances=1
Max Instances=3
Service Timeout=300
; Number of services after which PSQCKSRV will automatically restart.
; If the recycle count is set to zero, PSQCKSRV will never be recycled.
; The default value is zero.
Recycle Count=100000
; Number of consecutive service failures after which PSQCKSRV will
; automatically restart.
; If this is set to zero, PSQCKSRV will never be recycled.
; The default value is zero.
Allowed Consec Service Failures=2
; Max Fetch Size -- max result set size in KB for a SELECT query
; Default is 5000KB. Use 0 for no limit.
Max Fetch Size=5000
[PSQRYSRV]
;=========================================================================
; Settings for PSQRYSRV
;=========================================================================
; UBBGEN settings
Min Instances=1
Max Instances=3
Service Timeout=1200
; Number of services after which PSQRYSRV will automatically restart.
; If the recycle count is set to zero, PSQRYSRV will never be recycled.
; The default value is zero.
Recycle Count=100000
; Number of consecutive service failures after which PSQRYSRV will
; automatically restart.
; If this is set to zero, PSQRYSRV will never be recycled.
; The default value is zero.
Allowed Consec Service Failures=2
; Max Fetch Size -- max result set size in KB for a SELECT query
; Default is 10000KB. Use 0 for no limit.
Max Fetch Size=10000
; Use dirty-read(uncommitted read) for PSQRYSRV only on DB2/OS390 or SQL Server
Use dirty-read=0

VP1 is an application user, not a database user.
PS is a database user, the Peoplesoft objects' owner. It is also an application user on some application.
Did you try to connect onto the database with people user through SQL*Plus ? Are you able to read PSOPRDEFN, PSVERSION, PSACCESSPRFL tables ?
What Vista version are you on ? What Oracle version ?
If you have Metalink3 access, you should read the note :
Missing or invalid version of SQL library libpsora (0,0) or (200,0) (Doc ID 608741.1)+
Nicolas.

SQL Area Usage, Performance Problem

Hi,
I'm a software engineer, not a DBA, with a lot of doubts about our production environment, but I think that I have found a problem at our production Database.
At our development database when I execute the same SQL statement over than onces, I can see this behaviour (for example):
* First execution 580 milisenconds.
* Second execution 21 milisencons.
As where I know, I understand that the compiled SQL statement is stored at the SQL Area, and by that reason the second execution is faster then the first one. Is that assumption correct?
If it is correct, I have a problem on our production Database because it does not work as expected. I have done a lot of trials, and SQL statement executions do not reduce her time execution when I do consecutive SQL execution.
Could you help me? I think that the parameter shared_pool_size value is too lower for our production server.
Thanks in advance.
Best Regards,
Joan

Just a comment about performance tuning and troubleshooting in general Joan.
It is very dangerous to base your conclusions on observation only. Consider the following example:
SQL> set timing on
SQL> select count(*) from all_objects;
COUNT(*)
10296
Elapsed: 00:00:18.38
SQL>
SQL> -- now using the magically warp speed hint
SQL> select /*+ WARP_SPEED */ count(*) from all_objects;
COUNT(*)
10296
Elapsed: 00:00:00.32
SQL>
From 18 seconds to less than half a second. It does look, based on pure observation of the results, that there is a WARP_SPEED hint in Oracle and it does increase performance dramatically. And we can also infer that this is an undocumented feature added by one of the Oracle kernel developers that is also a Star Trek fan. ;-)
But if we turn on SQL tracing (as suggested), we will see that the first SELECT did a lot of physical I/O. The 2nd SELECT did the same work, but without having to do the very expensive physical I/O - as the data blocks it need to hit (again) was now in memory (inside Oracle's buffer cache).
It had nothing to do with an invalid and non-existing CBO hint called WARP_SPEED.
The critical bit is KNOWING exactly what you are measuring when using this type of approach. If you do not know that, you are in no position to determine a sound and valid conclusion.
Side note on shared pool size - one of the worse mistakes can be to increase it. It can cause incredible damage to performance on an instance that deals with bindless/non-sharable SQL as the pool that Oracle needs to use to determine if a soft parse is possible gets to be huge.. without the benefit of being able to soft parse and forced to hard parse anyway. And that hard parse also now added to the size of the pool.

Find start and end execution time of a sql statement?

I am have databases with 10.2.0.3 and 9.2.0.8 on HP UNIX 11i and Windows 200x.
I am not in a position to turn on sql tracing in production environment. Yet, I want to find when a sql statement started executing and when it ended. When I look at v$sql, it has information such FIRST_LOAD_TIME, LAST_LOAD_TIME etc. No where it has information last time statement began execution and when it ended execution.. It shows no of executions, elapsed time etc, but they are cumulative. Is there a way to find individual times (time information each time a sql statement was executed. – its start time, its end time ….)? If I were to write my own program how will I do it?
Along the same line, when an AWR snapshot is shown, does it only include statements executed during that snapshot or it can have statements from the past if they have not been flushed from shared memory. If it only has statements executed in the snapshot period, how does it know when statement began execution?

Hi,
For oracle 10g you can use below query to find start and end time, you can see data for last seven days.
select min(to_char(a.sample_time,'DD-MON-YY HH24:MI:SS')) "Start time", max(to_char(a.sample_time,'DD-MON-YY HH24:MI:SS')) "End Time", b.sql_text
from dba_HIST_ACTIVE_SESS_HISTORY a,DBA_HIST_SQLTEXT b where
a.sql_id=b.sql_id
order by 1;
Regards
Jafar

SQL Tracing

Similar Messages

Maybe you are looking for