5 Ekim 2013 Cumartesi

[EN] ORA-24005: must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables


-- ERROR --

SQL> drop user GENX cascade;
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-24005: must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables

-- SOLUTION --

SQL> select * from dba_queue_tables where owner = 'GENX';
no rows selected

SQL> select * from dba_queues where owner = 'GENX';
no rows selected

5 Eylül 2013 Perşembe

[EN] Solaris IPMP group fail-over consistency check Failure - 11.2.0.3 Cluster GI installation prerequest check phase

--------------
-- ERROR --
--------------

During 11.2.0.3 cluster GI installation prerequest check phase, we got the following warning on both (2) nodes:

INFO: INFO: Solaris IPMP group fail-over consistency check: This is a check to verify the current selection of public and private network classifications is consistent with network interfaces in fail-over dependency of an IPMP group
INFO: INFO: Severity:CRITICAL
INFO: INFO: OverallStatus:VERIFICATION_FAILED

There was 2 interfaces configured for public interface on both nodes.

--node1
vnet0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
       inet 10.86.233.11 netmask ffffffe0 broadcast 10.86.233.31
       groupname net1
vnet1: flags=69000842<BROADCAST,RUNNING,MULTICAST,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 0 index 3
       inet 0.0.0.0 netmask 0 
       groupname net1
--node2
vnet0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.86.233.12 netmask ffffffe0 broadcast 10.86.233.31
        groupname net1
vnet1: flags=69000842<BROADCAST,RUNNING,MULTICAST,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 0 index 3
        inet 0.0.0.0 netmask 0 
        groupname net1

When active/passice IPMP configured, you got this error during 11.2.0.3 cluster GI installation prerequest check phase. But we can ignore this warning and continue installation. After installation completes you can fix this with the following steps:

16 Mayıs 2013 Perşembe

[EN] ORA-00600: internal error code, arguments: [kcfrbd_3], [239], [3652081], [1], [2949120], [2949120], [], []

ERROR:

SQL> alter table INFRA.TBL_XXX drop partition PART_25;
ERROR at line 1:
ORA-00600: internal error code, arguments: [kcfrbd_3], [239], [3652081], [1], [2949120], [2949120], [], []

SOLUTION:

If the datafile with number 239 belong to the active UNDO tablespace, then try to reduce the size of this datafile. And then increase to its original size if you like. If you can not  reduce the size of this datafile; then create a new UNDO tablespace, switch to this new UNDO tbalespace and then drop the old one.
This should fix the problem.

If not; as a workaround you can first move and then drop the partition.

[EN] ORA-00600: internal error code, arguments: [4097], [], [], [], [], [], [], []

ERROR:

SQL> alter table INFRA.TABLEXXX split partition PART15 at (7030081) into (partition PART16 tablespace TBS_XXX, partition  PART15);
ERROR at line 1:
ORA-00600: internal error code, arguments: [4097], [], [], [], [], [], [], []

SOLUTION:
alter session set events '14525 trace name context forever, level 1';
SQL> alter table INFRA.TABLEXXX split partition PART15 at (7030081) into (partition PART16 tablespace TBS_XXX, partition  PART15);

3 Nisan 2013 Çarşamba

[TR] BLOCK CHANGE TRACKING

-----------------------------------------
-- BLOCK CHANGE TRACKING ---
-----------------------------------------

-----------------
-- Genel Bilgi --
-----------------

"Block Change Tracking" özelliği; incremental backup stratejisinde, incremental backupları hızlandırmak için kullanılır. Aksi halde incremental yedekleri alınan dbf'ler komple okunur. Block change tracking dosyası binay bir dosyadır ve ister primary ister standby db'lerde aktif hale getirilebilir. Yalnız standby db'lerde kullanılabilmesi için, "Oracle Active Data Guard" lisansının satın alınmış olması gerekir. Varsayılanda
kapalı olarak gelir. Etkisi özellikle çok fazla blok değişikliği olmayan db'lerde daha ciddidir. RMAN komutlarında değişiklik gerektirmez.

bct dosyasında sadece "BACKUP INCREMENTAL ..." komutuyla alınmış yedeklerin bilgisi tutulur. Yani;
INCREMENTAL LEVEL 0
INCREMENTAL LEVEL 1 DIFFERENTIAL
INCREMENTAL LEVEL 1 CUMULATIVE
Diğer yedekler tutulmaz.

[EN] 11G RAC ARCHIVELOG/NOARCHIVELOG MODE TRANSITION

ARCHIVELOG/NOARCHIVELOG mode transition is a little different in a RAC db than a standalone db.

You can see a transition example below;

11G NOARCHIVELOG to ARCHIVELOG mode transition


[DDD1]/u01/app/oracle/admin $ sqlplus / as sysdba
SQL> alter system set log_archive_dest_1= 'LOCATION=+ARCHIVE' scope=SPFILE sid='*';
SQL> alter system set log_archive_format = 'ddd_%t_%s_%r.arc' scope=SPFILE sid='*';