Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

DB Audit Log Files

MUHAMar 21 2018 — edited Mar 21 2018

Hello,

I have oracle 12c installed on Linux and i enabled audit 8 months ago, all audit actions can be accessed from database ($AUD)

i have an issue now that

/oracle/admin/orcl/adump directory is increasing on a daily basis and i have to remove audit files by the below command:

rm -f orcl_ora_*_20180316*.aud

below my audit configuration:

SQL> show parameter audit;

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

audit_file_dest                      string      /oracle/admin/orcl/adump

audit_sys_operations                 boolean     TRUE

audit_syslog_level                   string

audit_trail                          string      DB

unified_audit_sga_queue_size         integer     1048576

i need to create a job to delete old logs automatically

Appreciate your support

Regards

This post has been answered by Roxana - Oracle-Oracle on Mar 21 2018
Jump to Answer

Comments

unknown-791521
Firstly. thank you for providing that amount of data.
It is refreshing to have enough information to begin to help.
I know you have examined it, but I see no obvious problems in what you copied to here.
No blatant failures found by POST.
The OBP firmware on the I/O board is below everything else (rev 27 versus rev 30),
but that would not specifically cause the system to fail to function.

The "internal" SCSI path to the removable media bay in those systems,
(optical drive and DDS tape drive if it is installed)
does not rely on any external cabling. Your CD drive may simply be dead.
Substitute another one to make sure.


A disk board is treated in the same fashion as an external MultiPak or Array.
You must have a SCSI cable connected to it from your I/O board if you hope
to establish a data path to the drives. No cable? No disks.
POST sees the disk drives, so despite no output from probe-scsi-all,
I think you are okay in that respect. That suggests the cable is indeed fine as you thought.

Unfortunately, I have no magic answer why the OBP probe failed to see the diskboard.

Here is a link to the E4500's resource page in the SSH.
http://sunsolve.sun.com/handbook_pub/Systems/E4500/E4500.html
just in case you haven't found it yet, and so that the link is here for others that
read this thread in the future.


As for the lights you see on the system ...
E4000/E4500 LED patterns and meanings (3rd party web site)
If the only active light is the wrench light, then you may consider
that it needs to be replaced. (another trip out to Ebay, perhaps?)

=======
Thinking more and more on this, and just before I click on "Post the reply" ...
... internal SCSI needs to use the SCSI chipset on an I/O board ...
... your disk board needs to use the SCSI chipset on your I/O board ...
... probe didn't find any SCSI devices of any sort ...

I realize the I/O board passed POST without error, but it may be a bad board.

Perhaps other forum contributors can jump in here with their thoughts.
807559
Thank you for your help and I am sorry to answer so lately.

I have succeed to boot with a Sftp connection and an image of Ubuntu ( my goal is to install solaris ! but i did not get an boot image ).

I decided to buy a new SCSI I/O board card as I think the SCSI interface is dead. I am going to install it next week.
Now I have spare parts, so I can check everything. This is an interesting point to learn more about my new server.

I will let you know what s going on.
Thanks again for your answer, I deeply appreciate.

Regards.
Seb
807559
I finally found the solution :
I used a bad SCSI terminator ... the terminator was a differencial SCSI and the system needs a SEMI-ENDED SCSI terminator.

So the symptomes are clear :
the SCSI bus is present but not devices are recognized.

Shame on me ...

I changed the terminator by a good one and now it works : my station works very well

--Seb
1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Apr 18 2018
Added on Mar 21 2018
7 comments
7,173 views