vendredi 15 novembre 2013

Error ORA-16664 enabling Datagurd Configuration - ID Mismatch

Hi,

Recently I lost hours with this Issue, when trying to enable my Dataguard Configuration.

At Oracle Support -"Metalink" you will find some recommendations to solve this.
All recommendations leads to :
1- Set DG_BROKER_START=FALSE
2 - Delete the Dataguard Broker configuration  Files
3-Recreate Configuration

That's what I did consistently, and I got several errors such  as :

  1. Error  ORA-16664
  2. Error  ORA-16603
  3. Error  ORA-12520
What's was missing in that recommendation is that we need to recreate the Standby.
In Prod Site 
1 - Set DG_BROKER_START=FALSE in Prod
2 - Remove Dataguard Configuration Files 
In STBY Site
3 - Stop and Delete all Standby datafiles
4 - Remove Dataguard Configuration Files in Standby Site
5 - Recreate Standby 
And no more pb.
Hope this may help




mercredi 24 juillet 2013

Error: ORA-16525: the Data Guard broker is not yet available / Error: ORA-16625: cannot reach database


DGMGRL> show configuration;

Configuration - CMOVEL

  Protection Mode: MaxPerformance
  Databases:
    CMOVP   - Primary database
      Error: ORA-16778: redo transport error for one or more databases

    CMOVPDG - Physical standby database
      Error: ORA-16525: the Data Guard broker is not yet available

Fast-Start Failover: DISABLED

Configuration Status:
ERROR

DGMGRL> show database "CMOVPDG" 'InconsistentLogXptProps';
Error: ORA-16525: the Data Guard broker is not yet available
Error: ORA-16625: cannot reach database "CMOVPDG"

RESUME :
After recreate the standby and re-configure the Datagurad Broker I got the Message above

SOLUTION:
Shutdown the standby Database and restart the recovery process.
Disable and Enable the Dataguard Broker Configuration
Startup Standby Site and Restart the Recovery process






mardi 19 février 2013

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UPATE_TD_


Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "DBADM"."SYS_IMPORT_FULL_03" successfully loaded/unloaded
Starting "DBADM"."SYS_IMPORT_FULL_03":  dbadm/******** full=y directory=imp_dir dumpfile=exptestcmovel.dmp exclude=statistics content=DATA_ONLY logfile=imptest.log
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UPATE_TD_ROW_IMP [62]
TABLE_DATA:"AGENTCOMM"."COMMISSION_EXCLUSION_LIST"
ORA-31603: object "COMMISSION_EXCLUSION_LIST" of type TABLE not found in schema "AGENTCOMM"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 8170


(one of the )Problem : content=DATA_ONLY

 dbadm/******** full=y directory=imp_dir dumpfile=exptestcmovel.dmp exclude=statistics content=DATA_ONLY logfile=imptest.log

(one of the) SOLUTION do not uset Content Data Only

dbadm/******** full=y directory=imp_dir dumpfile=exptestcmovel.dmp exclude=statistics logfile=imptest.log


Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "DBADM"."SYS_IMPORT_FULL_04" successfully loaded/unloaded
Starting "DBADM"."SYS_IMPORT_FULL_04":  dbadm/******** full=y directory=imp_dir dumpfile=exptestcmovel.dmp exclude=statistics logfile=imptest.log
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
.
.
.









RMAN-06004: ORACLE error from recovery catalog database: ORA-03113: end-of-file on communication channel


.
.

channel ORA_DISK_2: finished piece 7 at 19-FEB-13
piece handle=/backup/oracle/CMOVP/rman/25o2bs8k_7_1 tag=TAG20130219T105516 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 01:01:21
Finished backup at 19-FEB-13

Starting backup at 19-FEB-13
current log archived

Starting backup at 19-FEB-13
current log archived
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 02/19/2013 12:12:21
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database: ORA-03113: end-of-file on communication channel
Process ID: 27169
Session ID: 133 Serial number: 6861
ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE

Problem : The RMAN REPOSITORY was in a diffrent platform (Linux) Target - (Solaris) Repository
Solution : Do not use the Respoitory

mardi 12 février 2013

/usr/bin/xauth: file /home/oracle/.Xauthority does not exist


In My Case :
IF ERROR on LOGIN :
/usr/bin/xauth:  file /home/oracle/.Xauthority does not exist

Check The /etc/passwd

oinstall:x:1001:1001::/home/oinstall:/bin/sh
oracle:x:1002:1001::/home/oracle:/bin/sh

REPLACE /bin/sh with /bin/bash
oinstall:x:1001:1001::/home/oinstall:/bin/bash
oracle:x:1002:1001::/home/oracle:/bin/bash

mercredi 30 janvier 2013

How Delete Applied Standby Archived Logs Manually

On 11g2

When backups of archived redo log files are taken on the Primary database:

 



CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

2.     Issue the following command on the primary database:

Usually by Default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

 

When backups of archived redo log files are taken on the standby database:

  1. Issue the following command on the primary database:


CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

  1. Issue the following command on the standby database:


CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

 
Then :

On Primary Site :
Connect with sys and :
SQL>Alter system set  "_log_deletion_policy" = 'ALL' scope=both;

The Archivelogs will be deleted on stanby site when a "Backup Database occurs in Primary Site" !!! To be confirmed

ON 10G

Create Shell Script:

#!/bin/bash
export ORACLE_SID=cmovelproddr
export ORACLE_HOME=/export/home/oracle/product/11.2.0/cmovelproddr
rman target=/  cmdfile=del_dg_arch.rcv log=delarchdr.log
exit

Create a RMAN rcv file  del_dg_arch.rcv

CROSSCHECK ARCHIVELOG ALL;
DELETE NOPROMPT ARCHIVELOG ALL completed before 'SYSDATE-2/24';

ORA: 16664 - configure your Listener to Avoid error with Datagurd Configuration


CONFIGURE your Listener with
 
LISTENER_CMOVP =

  (DESCRIPTION_LIST =

    (DESCRIPTION =

      (ADDRESS_LIST =

        (ADDRESS = (PROTOCOL = TCP)(HOST = server1)(PORT = 1521))

      )

     (ADDRESS_LIST =

        (ADDRESS = (PROTOCOL = TCP)(HOST = server1)(PORT = 1526))

      )

      (ADDRESS_LIST =

        (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))

      )

    )

  )

 

SID_LIST_LISTENER_CMOVP =

  (SID_LIST =

    (SID_DESC =

      (GLOBAL_DB_NAME=db01_DGMGRL)  ## Put db_name_DGMGRL

      (ORACLE_HOME = /opt/app/oracle/product/11.2.0/db0)

      (SID_NAME = db01)

    )

  )