Below you can find one of the available solutions that can be applied to solve this issue: PRI select max(sequence#) from v$archived_log where applied=’YES’; STBY select max(sequence#) from v$archived_log where applied=’YES’; SQL> select * from v$archive_gap; THREAD# LOW_SEQUENCE# HIGH_SEQUENCE# ———- ————- ————– 1 285 285 RMAN> list ARCHIVELOG FROM SEQUENCE 286 until SEQUENCE…
Once I got the mentioned issue and the solution was pretty simple: Log shipping user authentication problem Error 1031 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby ‘DB_STANDBY’. Error is 1031. ORA-01031: insufficient privileges SOLUTION copy password file again from PRIMARY to STANDBY
First we need to get the name of the CAPTURE process and the actual value and then start tuning it: col capture_name format a30 col parameter format a50 col value format a50 col set_by_user format a3 select capture_name,parameter, value,set_by_user from Dba_Capture_Parameters where capture_name like upper(‘&capture_name’); BEGIN dbms_capture_adm.set_parameter(capture_name => ‘&capture_name’, parameter => ‘_SGA_SIZE’, VALUE …
The error encountered is ORA-24247: network access denied by access control list (ACL) ORA-06512: at “OWNER.LDAP_NTFY”, line 410 ORA-06512: at line 2 And the solution is this: column acl format a30 column host format a20 column principal format a20 column privilege format a10 column is_grant format a8 set lines 1000 select acl , host ,…
Some time ago I had this issue and below is what I did to fix it: sql>conn [email protected]_REP sql>exec emd_maintenance.submit_em_dbms_jobs; ./emctl stop agent ./emctl start agent
Useful scripts to grab stats for partitions: set serveroutput on DECLARE LV_SQL VARCHAR2(1000); CURSOR C1 IS SELECT TABLE_NAME T , PARTITION_NAME P , LAST_ANALYZED L FROM USER_TAB_PARTITIONS WHERE LAST_ANALYZED is null AND TABLE_NAME = ‘&TABLE_NAME’ and partition_name like (‘&PART_NAME’); BEGIN FOR I IN C1 LOOP dbms_output.put_line(‘Gathering stats for :’||I.P); LV_SQL:= ‘BEGIN ‘;…
select s1.username || ‘@’ || s1.machine || ‘ ( SID=’ || s1.sid || ‘ ) is blocking ‘ || s2.username || ‘@’ || s2.machine || ‘ ( SID=’ || s2.sid || ‘ ) ‘ AS blocking_status from v$lock l1, v$session s1, v$lock l2, v$session s2 where s1.sid=l1.sid and s2.sid=l2.sid and…
The following statements should give us more indication about the TEMP usage and what is using it: col username format a10 col osuser format a8 col SID_SERIAL format a8 col PROCESS format 9999999 col tablespace format a7 col status format a9 col size_mb format 9999999999999 set lin 300 SELECT b.TABLESPACE –, b.segfile# –,…
col PROPERTY_NAME format a50 col PROPERTY_VALUE format a50 col DESCRIPTION format a50 set lin 300 SELECT PROPERTY_NAME,PROPERTY_VALUE,DESCRIPTION FROM DATABASE_PROPERTIES where PROPERTY_NAME=’DEFAULT_TEMP_TABLESPACE’;
Let’s determine the optimal size for UNDO: col “ACTUAL UNDO SIZE [MByte]” format 999999 col “UNDO RETENTION [Sec]” format 99999 col “OPTIMAL UNDO RETENTION [Sec]” format 999999 SELECT d.undo_size/(1024*1024) “ACTUAL UNDO SIZE [MByte]”, SUBSTR(e.value,1,25) “UNDO RETENTION [Sec]”, ROUND((d.undo_size / (to_number(f.value) * g.undo_block_per_sec))) “OPTIMAL UNDO RETENTION [Sec]” FROM ( SELECT SUM(a.bytes)…
