Tuesday, September 04, 2007
11g PX tracefiles now have the tracefile identifier on them
Now that I've got 11g up and running on OpenSuse 10.2 on a VMWare 6 VM, I've had time to do some playing with the latest and greatest release and the first thing I've noticed, when running some of Doug's PX test scripts, is that the trace files generated for PX slaves now have the Tracefile Identifier appended to their name, making it easier to see which OS Process (PID) was responsible for the creation of the trace file - makes things a little easier and clearer.
In 10gR2 (10.2.0.2.0 specifically) the trace files would come out with names in this format:
<instance name>_<PX Slave identifier>_<background process ID>.trc
e.g. fred_p001_6789.trc
In 11gR1 (11.1.0.6.0 specifically) the trace files come out with names in this format:
<instance name>_<PX Slave identifier>_<background process ID>_<Trace file identifier>.trc
e.g. fred_p001_5678_jeff.trc
This assumes you've set the tracefile identifier in the first place, otherwise that bit won't be present. Use the following to set it, choosing whatever identifier you require of course:
It was interesting that the location of such files has also changed due to the implementation of Automatic Diagnostic Repository (ADR). More information on that here.
In 10gR2 (10.2.0.2.0 specifically) the trace files would come out with names in this format:
<instance name>_<PX Slave identifier>_<background process ID>.trc
e.g. fred_p001_6789.trc
In 11gR1 (11.1.0.6.0 specifically) the trace files come out with names in this format:
<instance name>_<PX Slave identifier>_<background process ID>_<Trace file identifier>.trc
e.g. fred_p001_5678_jeff.trc
This assumes you've set the tracefile identifier in the first place, otherwise that bit won't be present. Use the following to set it, choosing whatever identifier you require of course:
alter session set tracefile_identifier='jeff';
It was interesting that the location of such files has also changed due to the implementation of Automatic Diagnostic Repository (ADR). More information on that here.
Comments:
Links to this post:
<< Home
In 10g, If I set tracefile_identifier before as you do in 11g (
This assumes you've set the tracefile identifier in the first place)I get the same result. What is changed then ?
D:\oracle\product\10.2.0\admin\dabak\udump>dir
Volume in drive D is DATA
Volume Serial Number is 8052-754C
Directory of D:\oracle\product\10.2.0\admin\dabak\udump
06.09.2007 10:55 .
06.09.2007 10:55 ..
0 File(s) 0 bytes
2 Dir(s) 1.013.526.528 bytes free
D:\oracle\product\10.2.0\admin\dabak\udump>sqlplus sys as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Per Eyl 6 10:56:05 2007
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> alter session set tracefile_identifier='jeff';
Session altered.
SQL> select * from dual;
D
-
X
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
D:\oracle\product\10.2.0\admin\dabak\udump>dir
Volume in drive D is DATA
Volume Serial Number is 8052-754C
Directory of D:\oracle\product\10.2.0\admin\dabak\udump
06.09.2007 10:56 .
06.09.2007 10:56 ..
06.09.2007 10:56 47 dabak_ora_6108_jeff.trc
1 File(s) 47 bytes
2 Dir(s) 1.013.460.992 bytes free
This assumes you've set the tracefile identifier in the first place)I get the same result. What is changed then ?
D:\oracle\product\10.2.0\admin\dabak\udump>dir
Volume in drive D is DATA
Volume Serial Number is 8052-754C
Directory of D:\oracle\product\10.2.0\admin\dabak\udump
06.09.2007 10:55 .
06.09.2007 10:55 ..
0 File(s) 0 bytes
2 Dir(s) 1.013.526.528 bytes free
D:\oracle\product\10.2.0\admin\dabak\udump>sqlplus sys as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Per Eyl 6 10:56:05 2007
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> alter session set tracefile_identifier='jeff';
Session altered.
SQL> select * from dual;
D
-
X
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
D:\oracle\product\10.2.0\admin\dabak\udump>dir
Volume in drive D is DATA
Volume Serial Number is 8052-754C
Directory of D:\oracle\product\10.2.0\admin\dabak\udump
06.09.2007 10:56 .
06.09.2007 10:56 ..
06.09.2007 10:56 47 dabak_ora_6108_jeff.trc
1 File(s) 47 bytes
2 Dir(s) 1.013.460.992 bytes free
The PX slave trace files (in background_dump_dest) don't have the relevant identified embedded in their names, so it's more difficult to tie them to the parent session.
See slides 9 and 12 ...
here
See slides 9 and 12 ...
here
I got it thank you for clarifying.
I missed the PX slaves part of the article :)
sorry for misunderstanding
Post a Comment
I missed the PX slaves part of the article :)
sorry for misunderstanding
Links to this post:
<< Home
Subscribe to Posts [Atom]