[EN] ORA-19706: invalid SCN

ERROR:

During a select through a database link we got the following error;

===> select sysdate from dual@TARGET_DBX
select sysdate from dual@TARGET_DBX
                         *
Error at line 1
ORA-19706: invalid SCN
ORA-02063: önceki line, kaynağı TARGET_DBX Script Terminated on line 1.

Also we noticed the following message in the alert.log;

*********************************************************************************
Rejected the attempt to advance SCN over limit by 8 hours worth to 0x0ca5.1y0772c8, by distributed transaction remote logon, remote DB: TARGET_DBX.WORLD.
 Client info : DB logon user USERX, machine hostx program JDBC Thin Client, and OS user app_usr1 *********************************************************************************

[EN] ORA-28030: Server encountered problems accessing LDAP directory service

After IDM entegration, we got

"ORA-28030: Server encountered problems accessing LDAP directory service"

error during logon to database via TOAD.

[EN] ORA-00245 control file backup failed; target is likely on a local file system

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

At the end of a full backup of our database we got the following error during control file and spfile file autobackup;

piece handle=TRYY_ARCH.9up06jbt_1_1 tag=TAG20140209T130029 comment=API Version 2.0,MMS Version 1.1.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:10
channel ORA_SBT_TAPE_2: finished piece 1 at 09-FEB-14
piece handle=TRYY_ARCH.9vp06jc0_1_1 tag=TAG20140209T130029 comment=API Version 2.0,MMS Version 1.1.0.0
channel ORA_SBT_TAPE_2: backup set complete, elapsed time: 00:00:07
Finished backup at 09-FEB-14

Starting Control File and SPFILE Autobackup at 09-FEB-14
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script GLOBAL_TRYY_FULL_BACKUP
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_SBT_TAPE_1 channel at 02/09/2014 13:00:58
ORA-00245: control file backup failed; target is likely on a local file system

Recovery Manager complete.

[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

[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: