How to find out the TOMCAT version in LINUX

 cd tomcat/lib 

java -cp catalina.jar org.apache.catalina.util.ServerInfo

FAILED LOGIN ATTEMPTS ORACLE

 

! HPRD:atlas.ecp.priv:/dbapps/oracle> sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Tue Aug 18 02:40:33 2020

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> audit create session whenever not successful;

select os_username,  username, userhost,  to_char(timestamp,'mm/dd/yyyy hh24:mi:ss') 

logon_time,  action_name, returncode from dba_audit_session order by 4 desc;

LINUX SWITCH USER

 sudo visudo

oracle  ALL=(root) ALL

admrcavan   ALL=(applmgr) NOPASSWD:ALL

admrcavan@apollo's password:

Last login: Mon Aug 10 18:02:52 2020 from 10.162.91.247

[admrcavan@apollo ~]$ sudo -iu applmgr

 apollo:/dbapps/applmgr/HRD2/apps/apps_st/appl>

MANAGING UNIFIED_AUDIT_TRAIL

Archiving the Unified and Traditional Database Audit Trails

You should periodically archive and then purge the audit trail to prevent it from growing too large.

Archiving and purging both frees audit trail space and facilitates the purging of the database audit trail.

You can create an archive of the unified and traditional database audit trail by using Oracle Audit Vault and Database Firewall. You install Oracle Audit Vault and Database Firewall separately from Oracle Database.

After you complete the archive, you can purge the database audit trail contents.

• To archive the unified, traditional standard, and traditional fine-grained audit records, copy the relevant records to a normal database table.

  For example:

  INSERT INTO table SELECT ... FROM UNIFIED_AUDIT_TRAIL ...;
  INSERT INTO table SELECT ... FROM SYS.AUD$ ...;
  INSERT INTO table SELECT ... FROM SYS.FGA_LOG$ ...; 

Unable to perform application-aware processing of Oracle database Veeam Backup

Your database is running in noarchivelog that is the reason for this error

Microsoft SQL Server, Error: 15023

USE MY_DB;

EXEC sp_change_users_login 'Auto_Fix', 'sa_web';

The row for user 'sa_web' will be fixed by updating its login link to a login already in existence.
The number of orphaned users fixed by updating users was 1.
The number of orphaned users fixed by adding new logins and then updating users was 0.

How to purge audit logs on Oracle 11g

https://docs.oracle.com/cd/E11882_01/network.112/e36292/auditing.htm#DBSEG472

Manually Purging the Audit Trail

You can manually purge the audit trail right away, without scheduling a purge job. Similar to a purge job, you can purge audit trail records that were created before an archive timestamp date or all the records in the audit trail.

Note the following about the DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL PL/SQL procedure:

• Only the current audit directory is cleaned up when you run this procedure.
• On Microsoft Windows, because the DBMS_AUDIT_MGMT package does not support cleanup of Windows Event Viewer, setting the AUDIT_TRAIL_TYPE property to DBMS_AUDIT_MGMT.AUDIT_TRAIL_OS has no effect. This is because operating system audit records on Windows are written to Windows Event Viewer. The DBMS_AUDIT_MGMT package does not support this type of cleanup operation.
• On UNIX platforms, if you set the AUDIT_SYSLOG_LEVEL initialization parameter to a valid value as listed in Oracle Database Reference, then Oracle Database writes the operating system log files to syslog files. If you set the AUDIT_TRAIL_TYPE property to DBMS_AUDIT_MGMT.AUDIT_TRAIL_OS, then the procedure only removes .aud files under audit directory (This directory is specified by the AUDIT_FILE_DEST initialization parameter).
• When the AUDIT_TRAIL_TYPE parameter is set to DBMS_AUDIT_MGMT.AUDIT_TRAIL_XML, this procedure only cleans up XML audit files (.xml) in the current audit directory. Oracle Database maintains an index file, called adx_$ORACLE_SID.txt, which lists the XML files that were generated by the XML auditing. The cleanup procedure does not remove this file.

For database audit trails, you must initialize the cleanup infrastructure by running the DBMS_AUDIT_MGMT.INIT_CLEANUP procedure, and then purging the database audit trail by using the method described in "Purging a Subset of Records from the Database Audit Trail".

To manually purge the audit trail:

1. Follow these steps under "Scheduling an Automatic Purge Job for the Audit Trail":
   • Step 1: If Necessary, Tune Online and Archive Redo Log Sizes
   • Step 2: Plan a Timestamp and Archive Strategy
   • Step 3: Initialize the Audit Trail Cleanup Operation
   • Step 4: Optionally, Set an Archive Timestamp for Audit Records
   • Step 5: Create and Schedule the Purge Job
   • Step 6: Optionally, Configure the Audit Trail Records to be Deleted in Batches
2. Purge the audit trail records by running the DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL PL/SQL procedure.
   For example:

   BEGIN
     DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL(
      AUDIT_TRAIL_TYPE           =>  DBMS_AUDIT_MGMT.AUDIT_TRAIL_AUD_STD,
      USE_LAST_ARCH_TIMESTAMP    =>  TRUE );
   END;
   /
   

   In this example:
   • AUDIT_TRAIL_TYPE: Enter one of the following values:
     • DBMS_AUDIT_MGMT.AUDIT_TRAIL_AUD_STD: Standard audit trail table, AUD$
     • DBMS_AUDIT_MGMT.AUDIT_TRAIL_FGA_STD: Fine-grained audit trail table, FGA_LOG$
     • DBMS_AUDIT_MGMT.AUDIT_TRAIL_DB_STD: Both standard and fine-grained audit trail tables
     • DBMS_AUDIT_MGMT.AUDIT_TRAIL_OS: Operating system audit trail files with the .aud extension. (This setting does not apply to Windows Event Log entries.)
     • DBMS_AUDIT_MGMT.AUDIT_TRAIL_XML: XML audit trail files
     • DBMS_AUDIT_MGMT.AUDIT_TRAIL_FILES: Both operating system and XML audit trail files
     • DBMS_AUDIT_MGMT.AUDIT_TRAIL_ALL: All audit trail records, that is, both database audit trail and operating system audit trail types
   • USE_LAST_ARCH_TIMESTAMP: Enter either of the following settings:
     • TRUE: Deletes audit records created before the last archive timestamp. To set the archive timestamp, see "Step 4: Optionally, Set an Archive Timestamp for Audit Records". The default (and recommended) value is TRUE. Oracle recommends that you set USE_LAST_ARCH_TIMESTAMP to TRUE.
     • FALSE: Deletes all audit records without considering last archive timestamp. Be careful about using this setting, in case you inadvertently delete audit records that should have been deleted.

Purging a Subset of Records from the Database Audit Trail

You can manually remove records from the database audit trail tables. This method can be useful if you want to remove a specific subset of records. You can use this method if the database audit trail table is in any tablespace, including the SYSTEM tablespace.

For example, to delete audit records that were created later than the evening of February 28, 2009 but before March 28, 2009, enter the following statement:

DELETE FROM SYS.AUD$
   WHERE NTIMESTAMP# > TO_TIMESTAMP ('28-FEB-09 09.07.59.907000 PM') AND
   NTIMESTAMP# < TO_TIMESTAMP ('28-MAR-09 09.07.59.907000 PM');

Alternatively, to delete all audit records from the audit trail, enter the following statement:

DELETE FROM SYS.AUD$;

Only the user SYS or a user to whom SYS granted the DELETE privilege on SYS.AUD$ can delete records from the database audit trail.