You're right. I didn't read Mohammed's email thoroughly enough. Although after
reading all the replies, he verifies that his trace file is in fact located in
the one fixed directory that serves as both background_dump_dest and
user_dump_dest, from which RDS's API-based log fetching is pulling. However, he
is using the rdsadmin.* stored procedures to get the files, instead of the AWS
CLI. Both should work.
Also, Mohamed noted that there is a directory object named BDUMP that points to
/rdsdbdata/log/trace. However, this is just a symlink to the same directory as
I tested this on my own 126.96.36.199 instance on RDS, and I have no trouble
generating a trace file and seeing it. Furthermore, the user_dump_dest,
background_dump_dest and diagnostic_dest are not modifiable on RDS, either at
the session or the system level, and all point to the same place
(/rdsdbdata/log/diag/rdbms/orcl_a/ORCL/trace). I would ask the original poster
to reach out to me at my Amazon address (jeremiah@xxxxxxxxxx) and I will assist
further with figuring out where things are going awry.
SQL> select value from v$parameter where name = 'user_dump_dest';
SQL> alter session set events '10046 trace name context forever, level 12';
SQL> select * from dual;
SQL> alter session set events '10046 trace name all off';
SQL> select tracefile from v$session s, v$process p where s.paddr = p.addr and
s.audsid = sys_context('userenv','sessionid');
$ aws rds describe-db-log-files --db-instance-identifier jworcl1
DESCRIBEDBLOGFILES 1492229825000 trace/ORCL_ora_9274.trc 5600
DESCRIBEDBLOGFILES 1492229825000 trace/ORCL_ora_9274.trm 126
$ aws rds download-db-log-file-portion --db-instance-identifier jworcl1
Trace file /rdsdbdata/log/diag/rdbms/orcl_a/ORCL/trace/ORCL_ora_9274.trc
Oracle Database 11g Enterprise Edition Release 188.8.131.52.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /rdsdbbin/oracle
PARSING IN CURSOR #46912551160152 len=18 dep=0 uid=35 oct=3 lid=35
tim=1492229812377300 hv=942515969 ad='758ab380' sqlid='a5ks9fhw2v9s1'
select * from dual
END OF STMT
SQL> alter session set user_dump_dest='/rdsdbdata/log/trace';
alter session set user_dump_dest='/rdsdbdata/log/trace'
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
From: "Gus Spier" <gus.spier@xxxxxxxxx>
To: "Jeremiah Cetlin Wilton" <jcwilton93@xxxxxxxxxxx>
Cc: "mohammed bhatti1" <mohammed.bhatti1@xxxxxxxxx>, "gogala mladen"
<gogala.mladen@xxxxxxxxx>, "Oracle Mailing List" <oracle-l@xxxxxxxxxxxxx>
Sent: Friday, April 14, 2017 6:52:21 PM
Subject: Re: Retrieving Trace Files for Oracle on AWS
I speak under correction, because I am not in any way a skilled RDS Database
It appears to me that the underlying problem is the trace file is NOT in the
BDUMP directory. Is it possible that this particular trace file is the moral
equivalent of the USER_BACKGROUND_DUMP_DEST. Does anyone know if RDS has an
Oracle directory object already configured to this "UDUMP" location? If one
does not already exist, is there an RDS equivalent to "CREATE DIRECTORY UDUMP
..." Oracle statement?
On Fri, Apr 14, 2017 at 2:41 PM, Jeremiah Cetlin Wilton <
jcwilton93@xxxxxxxxxxx > wrote:
Have you just tried listing the trace files using the AWS CLI or the console?
In the console:
- Select the instance (checkbox)
- Instance Actions -> See Details
- Recent Events and Logs Tab
- Scroll down to find your log, or use the search box
- Click view, watch or download
In the CLI:
aws rds describe-db-log-files --db-instance-identifier myinstance1
aws rds download-db-log-file-portion --db-instance-identifier myinstance1
--log-file-name trace/ORCL_j001_37382.trc --starting-token 0 --output text
You might want to also look at the docs for both of these CLI commands, since
they have lots of other useful options.
Let me know if you need any further assistance and the docs don't provide what
you need. I work for AWS and can get you help if needed.
From: "Mohammed Bhatti" < mohammed.bhatti1@xxxxxxxxx >
To: "gogala mladen" < gogala.mladen@xxxxxxxxx >
Cc: "Oracle Mailing List" < oracle-l@xxxxxxxxxxxxx >
Sent: Friday, April 14, 2017 7:08:32 AM
Subject: Re: Retrieving Trace Files for Oracle on AWS
I have not, but I will look into. Thanks Mladen.
On Fri, Apr 14, 2017 at 6:36 AM, Mladen Gogala < gogala.mladen@xxxxxxxxx >
Have you tried ADRCI utility?
On 04/13/2017 04:42 PM, Mohammed Bhatti wrote:
Thanks for your input. I tried that query and I was unable to locate the trace
file. It's frustrating.
I checked background_dump_dest and it point to
I then run this query:
FROM v$session s
JOIN v$process p ON s.paddr = p.addr
WHERE s.sid = 649;
Which shows me that the file generated is in
I then exec rdsadmin.manage_tracefiles.refresh_tracefile_listing;
Then run the following:
select filename, mtime
order by mtime;
But my file doesn't show up.
I also checked dba_directories and it shows that BDUMP points to
So, I'm confused because BDUMP points to a location that is not the same as the
tracefile location. I've tried creating a directory to that location but I get
insufficient privileges and I'm logged on as awssys.
Anyway, the regular DBA gets back next week, and this wasn't critical, and I'm
very new to Oracle on RDS, but it's just bugging me. Why can't I get to my
Thanks again Vijay.
On Thu, Apr 13, 2017 at 4:06 PM, vijayrsehgal < vijaysehgal21@xxxxxxxxx >
I am also new to AWS and learning, I used the below query to list the file and
then I logged in AWS console to download the file. There are other ways as
well, you can see if below query lists your file.
select * from table(rdsadmin.rds_file_util.listdir('BDUMP'));
On Thu, Apr 13, 2017 at 12:39 PM, Mohammed Bhatti < mohammed.bhatti1@xxxxxxxxx