ORACLE 9i-23ai

昨一好朋友问我开了审计，有些表但无审计记录。 下面我来还原这个问题 db_version oracle 10201 for linux SQL> show parameter audit NAME TYPE VALUE ———————————— ———– —————————— audit_file_dest string /u1/oracle/admin/ORCL/adump audit_sys_operations boolean FALSE audit_syslog_level string audit_trail string DB, EXTENDED audit select any table by access; SQL> select os_username,username,terminal,timestamp,owner,obj_name,audit_option from DBA_AUDIT_TRAIL order by 4; OS_USERNAM USERNAME TERMINAL TIMESTAMP OWNER OBJ_NAME AUDIT_OPTION ———- ———- ———- ——————- —————————— … Read more

1) Export the snapshots and then do a manual purge To purge the Table SYS.WRH$_ACTIVE_SESSION_HISTORY, you may first query the Snapshot History with the query below: select snap_id, begin_interval_time from sys.dba_hist_snapshot order by snap_id; Then, you choose the range of snapshot you want to delete, and you execute the following Procedure: exec dbms_workload_repository.drop_snapshot_range ( low_snap_id … Read more

有时出于安全考虑限制个别用户只允许特定程序连接或连接数，比如下面的例子是只允许ANBOB用户使用pl/sql dev连接此数据库。

Oracle Database provides a means for suspending, and later resuming,
the execution of large database operations in the event of space allocation failures.

Now I used segment advisor performs analysis on the segments and makes recommendations on how space can be reclaimed…

今天查看AWR时，发现有个sql占用的cpu很高而且也并不复杂，top 5 event出现了cpu,read by other sessions,而且sql中再次看到的hint index,随后从生产环境中拿到绑定变量参数值进行本地调试，发现hint index 选择了错误的索引一致读为93万，去掉hint立即降低到了36，随后服务器压力将了下来

The log file switch – checkpoint incomplete event tells you that Oracle wants to reuse a redo log file, but the current checkpoint position is still in that log file. This results in redo generation being stopped until the log switch is done.

sometimes we use ALTER SESSION statement to set or modify any of the conditions or parameters that affect your connection to the database. The statement stays in effect until you disconnect from the database. we can query current system Initialization parameter from v$parameter view,but where are able to confirm that the session-level parameter modification happened?