SYSAUX TABLESPACE IS TOO LARGE BECAUSE OF OPTIMIZER STATISTICS ADVISOR TASK DATA
Due to a bug in 12.2 and 18c databases, the SYSAUX tablespace grows rapidly and consumes lots of space in the database. The SM/ADVISOR option is involved.
CLEAN UP DATABASE FROM THE SESSHIS USER AND HIS OBJECTS
Removing all custom objects that were created through 2 posts : ALTERNATIVE TO V$ACTIVE_SESSION_HISTORY VIEW IN STANDARD EDITION and/or DUMPING SQL EXECUTION HISTORY INFORMATION SNAPSHOTS IN STANDARD EDITION
DUMPING SQL EXECUTION HISTORY INFORMATION SNAPSHOTS IN STANDARD EDITION
A way to catch and store every single SQL ever executed in a Standard Edition database. Creation SQL execution snapshots for later analysis.
ALTERNATIVE TO V$ACTIVE_SESSION_HISTORY VIEW IN STANDARD EDITION
A way to catch and store every single SESSION ever connected to a Standard Edition database. Creation SESSION HISTORY snapshots for later analysis.
TOO HIGH ELAPSED TIME FOR ENTERPRISE MANAGER QUERIES BECAUSE OF AUDIT RECORDS
The Enterprise Manager Queries are on the top of CPU/TIME consuming queries in statspack reports. The post offers some methods to handle it.
SYSAUX TABLESPACE IS TOO LARGE BECAUSE OF OPTIMIZER STATISTICS HISTORY
The SYSAUX tablespace keeps growing because of storing old table statistics. A purging of history data is required.
ERRORS ORA-39150 AND ORA-08186 DURING DATAPUMP IMPORT WHEN USING FLASHBACK_TIME OPTION
A datapump session fails with the error “bad flashback time” because of the specified FLASHBACK_TIME parameter. It fails even if parameter is correct.
ENTERPRISE MANAGER AGENT IS IN THE “COLLECTIONS_HALTED” STATUS
By the following steps in this post, you can fix the Oracle Management Agent status when it’s stopped working and doesn’t send any data to the OMS anymore.
HOW TO GRANT THE SELECT PRIVILEGE ON A VIEW TO THIRD PARTY USERS
Granting SELECT privilege on a view to other users when underlying objects of such a view do not belong to the owner of the view.
ORA-29516: AURORA ASSERTION FAILURE: ASSERTION FAILURE AT OEX.C:359
It describes a situation with the very specific issue when the PSU post-step script fails because of multiple running jobs that consume lots of SGA memory.
Categories
- Linux (8)
- Iptables (2)
- Memory Usage (1)
- Postfix (1)
- Yum (4)
- Networker (2)
- Oracle (70)
- Account (2)
- AWR (4)
- Database Errors (7)
- Database Performance (10)
- Datapump (4)
- DBMS_SCHEDULER (2)
- Enterprise Manager (25)
- Enterprise Manager Metrics (4)
- Environments (4)
- High CPU Usage (3)
- High IO Load (4)
- Historical Session Information (3)
- Initialization Parameters (5)
- job_queue_processes (1)
- Processes (3)
- NLS (1)
- Objects (1)
- Objects DDL (2)
- OJVM/PSU/DRU Patches (1)
- Optimizer Statistics Advisor (1)
- PL/SQL (5)
- UTL_FILE (4)
- Prerequisites (1)
- Privileges (1)
- Profile (1)
- Queries (2)
- Redologs (1)
- Resource Limits (1)
- Segment Shrink (1)
- Session (6)
- Spfile (3)
- SQL PLUS (1)
- Spooling (1)
- Standard Queries (7)
- Statistics (3)
- Tablespaces (2)
- Temporary Tablespace (2)