Error in duplicating dataguard, RMAN-04006: error from auxiliary,ORA-12514

Hi All,
Trying to duplicate using rman and facing below issue
rman TARGET sys/oracle@pawsdb AUXILIARY sys/oracle@adpaws
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jun 19 20:47:09 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: PAWSDB (DBID=3014417093)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
TNS on aux looks like this
ADPAWS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.210.23.227)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = adpaws)
Listener under grid home  (ASM) on aux looks like this
# listener.ora Network Configuration File: /home/oracle/app/oracle/product/11.2.0/grid/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /home/oracle/app/oracle/product/11.2.0/grid)
(SID_NAME = adpaws)
(GLOBAL_DBNAME= adpaws.example.com)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = cuscmetl.hillscte.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
ADR_BASE_LISTENER = /home/oracle/app/oracle
output of lsnrctl on aux looks like this
LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 19-JUN-2012 20:53:49
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=cuscmetl.hillscte.com)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date 19-JUN-2012 20:53:42
Uptime 0 days 0 hr. 0 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/oracle/app/oracle/product/11.2.0/grid/network/admin/listener.ora
Listener Log File /home/oracle/app/oracle/diag/tnslsnr/cuscmetl/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=cuscmetl.hillscte.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "adpaws.example.com" has 1 instance(s).
Instance "adpaws", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
TNS on target is also configured properly, both are tnsping successful from each other, running this command from aux server results in failure
Please help
thanks

Thanks for reply, below are the last 50 lines from listener log
<msg time='2012-06-19T21:10:13.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:13 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56363)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:13.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:13 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56364)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:18.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:18 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56366)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:18.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:18 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56367)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:23.126-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:23 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56368)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:23.159-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:23 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56369)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:28.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:28 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56371)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:28.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:28 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56372)) * establish * etldb * 0
</txt>
</msg>

Similar Messages

  • RMAN-06136: ORACLE error from auxiliary database

    Dear All,
    When i start to recover a tablespace(TSPITR) using RMAN, getting below errors. Could any guide me
    RMAN-03002: failure of recover command at 02/07/2013 14:12:30
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01119: error in creating database file '/rman/SHFLCLN/oradata'
    ORA-27056: could not delete file
    IBM AIX RISC System/6000 Error: 1: Not owner
    RMAN-06956: create datafile failed; retry after removing /rman/SHFLCLN/oradata from OS

    01119, 00000, "error in creating database file '%s'"
    // *Cause:  Usually due to not having enough space on the device.
    // *Action:                                                                                                                                                                                                                                                                       

  • ORACLE error from auxiliary database: ORA-01152: file 2 was not restored fr

    Hello,
    i'm trying to clone a database. It is in archive log mode.
    I took a full back using below command
    run {
      backup
         tag 'DAILY_WHOLE'
         format 'FULL_backup_%s_%p_%c.bkp'     database
         plus archivelog
         tag 'DAILY_WHOLE'
         delete all input;
      backup
         current controlfile
         format 'FULL_backup_%s_%p_%c.bkp'     tag 'WHOLE'
         spfile
         format 'FULL_backup_%s_%p_%c.bkp'     tag 'WHOLE';
    }then i issue a duplicate database command
    RUN
    DUPLICATE DATABASE TO TEST_DB
              NOFILENAMECHECK
               NOREDO
              BACKUP LOCATION '/disk10/flash_recovery_area/PROD';
    }at the very end I got this error.
    contents of Memory Script:
       Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/15/2013 11:59:21
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01152: file 2 was not restored from a sufficiently old backup
    ORA-01110: data file 2: 'sysaux.dbf'Can anyone help me? I would appreciate it. thanks

    NOREDO would be used when you have a Consistent Backup (i.e. backup taken when the database is MOUNTed but not OPEN) and so, no archivelogs need to be applied. (This would also be the case for a NOARCHIVELOG database).
    See the notes on NOREDO in the DUPLICATE command documentation in the Backup and Recovery Reference.
    http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724
    Hemant K Chitale

  • Error RMAN connection to auxiliary database ORA- 12514

    Hi,
    I'm trying to make a clone of my database in another server but when I'm trying to connect as follow the RMAN return
    to me the error ORA-12514.
    C:\Documents and Settings\joses.morales>rman TARGET sys/pass@iswgen nocatalog
    AUXILIARY sys/[email protected]
    Recovery Manager: Release 8.1.7.4.1 - Production
    RMAN-06005: connected to target database: ISWGEN (DBID=2348350645)
    RMAN-06009: using target database controlfile instead of recovery catalog
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
    For more information:
    - the auxiliary database is started whit nomount option.
    - this is my listener.ora in the auxiliary host
         LISTENER =
         (DESCRIPTION =
         (ADDRESS = (PROTOCOL = TCP)(HOST = WSSP61)(PORT = 1521))
         SID_LIST_LISTENER =
         (SID_LIST =
         (SID_DESC =
         (GLOBAL_DBNAME = oracle8)
         (ORACLE_HOME = C:\oracle\ora81)
         (SID_NAME = iswgen)
         (SID_DESC =
         (GLOBAL_DBNAME = oracle8)
         (ORACLE_HOME = C:\oracle\ora81)
         (SID_NAME = oracle8)
    - this is my tnsnames.ora in the auxiliary host
         ISWGEN =
         (DESCRIPTION =
         (ADDRESS_LIST =
         (ADDRESS = (PROTOCOL = TCP)(HOST = wssp61)(PORT = 1521))
         (CONNECT_DATA =
         (SERVICE_NAME = iswgen)
         ORACLE8 =
         (DESCRIPTION =
         (ADDRESS_LIST =
         (ADDRESS = (PROTOCOL = TCP)(HOST = WSSP61)(PORT = 1521))
         (CONNECT_DATA =
         (SERVICE_NAME = oracle8)
    - this is my tnsnames.ora in the target host
    iswgen =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = gdcoracle)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = iswgen)
         iswgen.wssp61 =
         (DESCRIPTION =
         (ADDRESS_LIST =
         (ADDRESS = (PROTOCOL = TCP)(HOST = wssp61)(PORT = 1521))
         (CONNECT_DATA =
         (SERVICE_NAME = iswgen)
    - target server: gdcoracle
    - auxiliary server: wssp61
    - global name in auxiliary: Oracle8
    - intances in auxiliary: Oracle8 & Iswgen
    I was expecting the follow message:
    connected to target database: ISWGEN (DBID=519338572)
    using target database control file instead of recovery catalog
    connected to auxiliary database: ISWGEN.WSSP61 (not mounted)
    Can anybody help me to resolve this error ORA-12514??
    Thanks

    I'm try to connect to the auxiliary server at SQLPLUS and I get the follow:
    C:\Documents and Settings\joses.morales>sqlplus /nolog
    SQL*Plus: Release 8.1.7.0.0 - Production on Sex Jun 1 12:26:09 2007
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    SQL> conn sys@iswgen
    Informe a senha:
    ERROR:
    ORA-12514: TNS:listener nao conseguiu resolver o SERVICE_NAME fornecido no
    descitor de conexao
    SQL> conn sys@iswgen as sysdba
    Informe a senha:
    ERROR:
    ORA-12514: TNS:listener nao conseguiu resolver o SERVICE_NAME fornecido no
    descitor de conexao
    SQL> conn internal as sysdba
    Conectado.
    SQL>
    Any sugestions?
    Thanks everyone and regards

  • ORA-02068: following severe error from ....

    Hi,
    we have a dataguard setup for 10g databases on AIX platform as below.
    host1(TALON) host2(CATALINA)
    TICSPROD (PRIMARY ) TICSPROD(STANDBY)
    PLSPROD (STANDBY) PLSPROD (PRIMARY)
    We have decided to recreate PLSPROD STANDBY(because of some setup issues) this weekend and last night we just disabled the PLSPROD STANDBY.Means now only PLSPROD PRIMARY is working.
    Last night, suddenly in the PRIMARY TICSPROD alert log file we see the below error.Is it because of the dataguard issue or any other issue.Please help as we have no clue how to resolve this.
    ORA-02050: transaction 4.34.2844973 rolled back, some remote DBs may be in-doubt
    ORA-02068: following severe error from PLSPROD
    ORA-03113: end-of-file on communication channel

    We have decided to recreate PLSPROD STANDBY(because of some setup issues) this weekend and last night we just disabled the PLSPROD STANDBY.Means now only PLSPROD PRIMARY is working.
    Last night, suddenly in the PRIMARY TICSPROD alert log file we see the below error.Is it because of the dataguard issue or any other issue.Please help as we have no clue how to resolve this.
    ORA-02050: transaction 4.34.2844973 rolled back, some remote DBs may be in-doubt
    ORA-02068: following severe error from PLSPROD
    ORA-03113: end-of-file on communication channel
    What are the parameters of standby
    post
    show parameter dest_2
    show parameter state_2ORA-02050:
         transaction string rolled back, some remote DBs may be in-doubt
    Cause:      network or remote failure in 2PC.
    Action:      Notify operations; remote DBs will automatically re-sync when the failure is repaired.
    defer the destination state 2 also refer the below link
    http://www.orafaq.com/forum/t/67115/2/

  • How to remove error from propagation and verify replication is ok?

    Have a one-way schema level streams setup and the target DB is 3-node RAC (named PDAMLPR1). I run a large insert at source DB (35million rows). After committing on source, I made a failure test on the target DB by shutting down the entire database. The streams seems stopped as the heartbeat table sequence (it inserts a row each min) on target is still reflecting last night. We get the error in the dba_propagation:
    ORA-02068: following severe error from PDAMLPR1
    ORA-01033: ORACLE initialization or shutdown in progress
    ORA-06512: at "SYS.DBMS_AQADM_SYS", line 1087
    ORA-06512: at "SYS.DBMS_AQADM_SYS", line 7639
    ORA-06512: at "SYS.DBMS_AQADM", line 631
    ORA-06512: at line 1
    08-FEB-10
    while capture, propagation, and apply are all in enabled status. I restarted capture and propagation at source DB. But still see the error message above. My questions are:
    1. How to delete the error from dba_propagation?
    2. How to verify the streams is still running fine?
    In normal test, during such large insert, the heartbeat table added a row in an hour. Very slow.
    thanks for advice.

    Well, if I can give you my point of view: I think that 35 millions LCR is totally unreasonnable. Did you really post a huge insert of 35 millions then committed that single utterly huge transaction? Don't be surprised it's going to work very very hard for a while!
    With a default setup, Oracle recommends to commit every 1000 LCR (row change).
    There are ways to tune Streams for large transaction but I have not done so personnaly. Look on Metalink, you will find information about that (mostly documents id 335516.1, 365648.1 and 730036.1).
    One more thing: you mentionned about a failure test. Your target database is RAC. Did you read about queue ownership? queue_to_queue propagation? You might have an issue related to that.
    How did you setup your environment? Did you give enough streams_pool_size? You can watch V$STREAMS_POOL_ADVICE to check what Oracle think is good for your workload.
    If you want to skip the transaction, you can remove the table rule or use the IGNORETRANSACTION apply parameter.
    Hope it helps
    Regards,

  • ORA-02068: following severe error from LNK -(Prob with HS ODBC pls. help)

    HI Every one...
    Please help me out...
    Problem in d/b link using generic connectivity of oracle to connect MS Access here are the details ...
    ORACLE VERSION - Oracle8i Release 8.1.7.0.0
    OS - WINDOWS 2000 Service Pack 3
    MSAccess 2000
    I sussessfully created System DSN steps....
    ODBC Data Source Administrator -> System DSN -> ADD -> (select) Microsoft Access
    Driver [*.mdb] Version- 4.00.6200.00 -> ODBC Microsoft Access Setup (Data Source
    Name = dbq and selected the MS Access database file. and OK -> OK
    HS parameter file...
    Location .... D:\oracle\ora81\hs\admin
    Name........ initdbaccess.ora
    HS_FDS_CONNECT_INFO =dbq
    HS_FDS_TRACE_LEVEL =off
    listener.ora
    Location.... D:\oracle\ora81\network\ADMIN
    (SID_DESC =
    (SID_NAME = dbaccess)
    (ORACLE_HOME = D:\oracle\ora81)
    (PROGRAM = hsodbc)
    TNSNames.ora
    Location.... D:\oracle\ora81\network\ADMIN
    DBACCESS =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (CONNECT_DATA =
    (SID = dbaccess)
    (HS = OK)
    I stop the listener and start it again.... then on sqlplus.....
    SQL> connect qu3/qu3@mysys
    Connected.
    SQL> create database link lnk using 'DBACCESS';
    Database link created.
    SQL> select * from t_emp_main@lnk;
    select * from t_emp_main@lnk
    ERROR at line 1:
    ORA-02068: following severe error from LNK
    ORA-03114: not connected to ORACLE
    Why this Error is comming.... any solution pls......
    Thanks in advance....
    SMG

    Help please... problem still pending ....

  • ORA-02068: following severe error from db link

    Hi,
    I have the following piece of code which gives an error.
    FOR items IN (SELECT DISTINCT item FROM ccm_items@caav_link a)
    LOOP
    itemtrans.process_item@manuf_link(items.item);
    END LOOP;
    Procedure process_item may take several hours to complete execution. Hence after processing one or two items, I get an error "ORA-02068: following severe error from caav_link
    ORA-03113: end-of-file on communication channel"
    I guess this occurs due to some timeout issue. Can you please give some pointers on why this issue occurs and how to avoid it? Also note that I need to use the same link after the loop. So a timeout could cause a problem there also.
    Thanks,
    Blesson

    May be this link will be useful:
    http://www.dba-oracle.com/t_ora_02068_following_severe_error_from_stringstring.htm

  • ORA-02068: following severe error from - How to handle the overgiven Except

    Hello again ^^,
    hope its okay to write the follwnig question into a new Thread...
    I sometimes get errors from remote dbs.
    ORA-02068: following severe error from DBLINK
    ORA-01089: immediate shutdown in progress - no operations are permitted
    ORA-02068: following severe error from DBLINK
    ORA-03113: end-of-file on communication channelThese are in one sqlerm. Is it possible to handle the second errors without string operations?
    Thanks and regards
    Edited by: user10283133 on 28.10.2008 08:33
    Try to force the headline

    The remote db is accessible from 6 am to 6 pm. When querring longer than given time span I get the Error ORA-02068. In the sqlerm for this Error is a second Errormessage from an second different Error concatenated.
    Now I will tell what I think is happening:
    I think the remote db say: >>I will go sleep now<< an throws Error A (ORA-01089 (or ORA-03113, or what else)). This Error A goes to the local db. The local db get the Error A and throw a new Error (Error B = ORA-02068). This Error B is independet from Error A. And I see a String which is "Error B + Error A"
    I recieve also three possible Errormessages:
    ORA-02068: following severe error from DBLINK
    ORA-03113: end-of-file on communication channel
    ORA-02068: following severe error from DBLINK_ODS_STBY
    ORA-01089: immediate shutdown in progress - no operations are permitted
    ORA-02068: following severe error from DBLINK_ODS_STBY
    ORA-whatelse: what elseI can handle the ORA-02068. But my questions is, can I handle the second Error (thus Error A) without string operations?
    The Relase is 10g2. Please tell me which information you still need ...
    Thank you very much.
    regrads

  • ORA-02068: following severe error from dblink

    Dear friends,
    My database (oracle 9.2.0.8.0) will call another database's (oracle 9i cluster) view through DB Link to get some data.
    If we are to access the data for the first time in a particular session, it gives the output within a second.
    But if we access the data after 45mins in the same session(already connection is open), the query is running for 9 mins it throws an oracle error.
    There is no network issue also(solaris 5.8 server).
    select * from <synonym> where <column_name>=<Value>;
    synonym is created in my database for remote database view (schema_name.view_name@dblink_name)
    please find the Oracle error below:
    ORA-02068: following severe error from RAMBOMAX
    ORA-03113: end-of-file on communication channel
    SID EVENT STATE WAIT_TIME SECONDS_IN_WAIT P1 P2 P3 SQL_HASH_VALUE
    547 SQL*Net message to client WAITED KNOWN TIME -1 0 1413697536 1 0 951575186
    283 SQL*Net message from dbli WAITING 0 441 675562835 1 0 3503340408
    298 SQL*Net message from dbli WAITING 0 199 675562835 1 0 3503340408
    572 SQL*Net message from dbli WAITING 0 485 675562835 1 0 3503340408
    632 SQL*Net message from dbli WAITING 0 358 675562835 1 0 3503340408
    634 SQL*Net message from dbli WAITING 0 250 675562835 1 0 3503340408
    581 SQL*Net message from dbli WAITING 0 208 675562835 1 0 3503340408
    561 SQL*Net message from dbli WAITING 0 376 675562835 1 0 3503340408
    520 SQL*Net message from dbli WAITING 0 413 675562835 1 0 3503340408
    What could be the reason for this? could some one please help me on this?
    Thanks,
    Prathap

    user8724104 wrote:
    Dear friends,
    What could be the reason for this? could some one please help me on this?
    Thanks,
    PrathapHi Prathap,
    you should focus your research for solution on [ORA-03113|http://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-03113+link&objID=f61&dateRange=all&userID=&numResults=15]

  • RMAN Restore - continue from a failed point?

    Hi All,
    While cloning a db using RMAN, We get
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/10/2008 01:53:12
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-00344: unable to re-create online log '/rcatsi/oradata/data02/data03/log1a.dbf'
    ORA-27040: file create error, unable to create file
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Recovery Manager complete.
    I realized that, I had given an incorrect location for the logfile. The database is restored, control file created, while opening the db I see this error. Is it possible to continue with the clone using rman without having to restart the whole clone. I know it can be done manually using create control file and manually applying the archives. However, Is there a way to continue the clone in rman by specifying the correct location for the logfile?
    -Ritesh

    The directory name was incorrect. I corrected it and re-ran the script. But it started the clone right from the scratch....Instead of continuing from the point it failed..
    Did you use LOG_FILE_NAME_CONVERT (possibly
    incorrectly)? Is that directory name correct? You
    have data02 and data03 beneath it?

  • NSV0: Failed to connect to remote database orcl. Error is ORA-12514

    sGetting error on data guard broker configuration. redologs shiping properly, withot any problems.
    Database: 11gR2 , Linux 64-bit
    [root@redhat ~]# su - oracle
    [oracle@redhat ~]$ sqlplus /nolog
    SQL*Plus: Release 11.2.0.1.0 Production on Fri Jun 18 17:39:07 2010
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    SQL> connect /as sysdba
    Connected.
    SQL> connect sys/oracle@primarydb as sysdba
    Connected.
    SQL> connect sys/oracle@physicaldb as sysdba
    Connected.
    SQL>
    */etc/hosts file contents on all nodes*
    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    127.0.0.1     localhost.localdomain     localhost
    192.168.1.232     redhat          redhat
    192.168.1.234 rac1          rac1
    primary database (drcorcl.log)
    2010-06-18 17:41:39.972 02010001 1362743835 DMON: CTL_GET_STATUS forwarded to site physicaldb for processing
    2010-06-18 17:41:41.044 NSV1: Site physicaldb returned ORA-16664.
    2010-06-18 17:41:41.045 02010001 1362743821 DMON: Database physicaldb returned ORA-16664
    2010-06-18 17:41:41.045 02010001 1362743821 for opcode = CTL_GET_STATUS, phase = NULL, req_id = 1.1.1362743821
    2010-06-18 17:41:41.045 02010001 1362743821 DMON: CTL_GET_STATUS operation completed
    2010-06-18 17:41:41.050 01000000 1362743836 DMON: MON_PROPERTY operation completed
    2010-06-18 17:41:41.054 01010001 1362743837 DMON: MON_PROPERTY operation completed
    2010-06-18 17:41:41.058 01010001 1362743838 DMON: MON_PROPERTY operation completed
    2010-06-18 17:41:41.062 01010001 1362743839 DMON: CTL_GET_STATUS operation completed
    2010-06-18 17:41:56.045 NSV1: Site physicaldb returned ORA-16664.
    2010-06-18 17:41:56.045 02010001 1362743835 DMON: Database physicaldb returned ORA-16664
    2010-06-18 17:41:56.045 02010001 1362743835 for opcode = CTL_GET_STATUS, phase = NULL, req_id = 1.1.1362743835
    2010-06-18 17:41:56.046 02010001 1362743835 DMON: CTL_GET_STATUS operation completed
    physical standby database (drcorcl.log)
    2010-06-17 00:41:30.410 drcx: could not find task req_id=1.1.1362743821 for PROBE.
    2010-06-17 00:41:45.411 drcx: could not find task req_id=1.1.1362743835 for PROBE.
    2010-06-17 00:42:00.546 NSV0: Failed to connect to remote database orcl. Error is ORA-12514
    2010-06-17 00:42:00.547 NSV0: Failed to send message to site orcl. Error code is ORA-12514.
    2010-06-17 00:42:00.547 DMON: Database orcl returned ORA-12514
    2010-06-17 00:42:00.547 for opcode = HEALTH_CHECK, phase = BEGIN, req_id = 1.1.1362743840
    2010-06-17 00:42:15.414 drcx: could not find task req_id=1.1.1362743840 for PROBE.
    2010-06-17 00:43:15.548 NSV0: Failed to connect to remote database orcl. Error is ORA-12514
    2010-06-17 00:43:15.549 NSV0: Failed to send message to site orcl. Error code is ORA-12514.
    2010-06-17 00:43:15.549 DMON: Database orcl returned ORA-12514
    2010-06-17 00:43:15.549 for opcode = HEALTH_CHECK, phase = BEGIN, req_id = 1.1.1362743841
    Standby Lintener file contents
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = rac1)(PORT = 1521))
    ADR_BASE_LISTENER = /oradisk/oracle
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DNAME = physicaldb)
    (ORACLE_HOME = /oradisk/oracle/product/11.2.0/db)
    (SID_NAME = orcl)
    (SID_DESC =
    (GLOBAL_DNAME = physicaldb_DGMGRL)
    (ORACLE_HOME = /oradisk/oracle/product/11.2.0/db)
    (SID_NAME = ORCL)
    Primary database Listener contents
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.232)(PORT = 1521))
    ADR_BASE_LISTENER = /oradisk/oracle
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DNAME = orcl)
    (ORACLE_HOME = /oradisk/oracle/product/11.2.0/db)
    (SID_NAME = orcl)
    (SID_DESC =
    (GLOBAL_DNAME = orcl_DGMGRL)
    (ORACLE_HOME = /oradisk/oracle/product/11.2.0/db)
    (SID_NAME = orcl)
    TNSNAMES.ora on all nodes
    PRIMARYDB =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.232)(PORT = 1521)))
    (CONNECT_DATA =(SID = orcl))
    LISTENER_PHYSICALDB =(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.234)(PORT = 1521))
    PHYSICALDB =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.234)(PORT = 1521)) )
    (CONNECT_DATA =(SID = orcl))
    ORCL =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.232)(PORT = 1521)))
    (CONNECT_DATA =(SERVER = DEDICATED)(SID = orcl) )
    )

    Don't use the old syntax 'SID=...' in tnsnames.ora, use 'SERVICE_NAME=...' . Make sure 'SERVICE_NAME' is exactly the same returned by 'lsnrctl status' on both nodes.
    Primary and standby cannot talk to each other currently through the listener:
    ORA-16664: unable to receive the result from a database
    Cause: During execution of a command, a database in the Data Guard broker
    configuration failed to return a result.
    Action: Check Data Guard broker logs for the details of the failure. Fix any
    possible network problems and try the command again.
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
    Action: - Wait a moment and try to connect a second time.
    - Check which services are currently known by the listener by executing: lsnrctl services <listener name>
    - Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.
    - If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.
    - Check for an event in the listener.log file.
    Werner

  • ORA-12514 error: Instant Client 11 connect to remote Oracle 8i

    I encountered a problem that I have spent hours fixing that. Here is the problem:
    I am trying to connect to a remote Oracle 8i server using Oracle 11 instant client: here is my connection string in PHP:
    *$conn = oci_connect('db_user', 'db_pass', "db_ip/db_service");*
    db_ip is the ip of the server, such as "12.34.56.78". db_service is the service of server, such as "test".
    The error shown is "*ORA-12514:* TNS:listener does not currently know of service requested in connect descriptor"
    I could use the same client to connect to another oracle 10g server. The php code is same, only change the db_user or db_pass or db_ip. db_service is not provided.
    I dont use tnsnames.ora for either oracle *10g s*erver or oracle 8i server. I just use the simple IP of server. Does this matter?
    Server using: Windows Server 2008 R2
    PHP: php 5.2.17
    Oracle Instant Client: 11_2
    Any ideas will be appreciated.
    Best, Sam

    Pl do not post duplicates - PHP 5.2.17 and Oracle 8i

  • RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

    Good Morning All,
    One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
    ==================================================================================================
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

    This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
    ====================================================================================================
    Recovery Manager: Release 9.2.0.6.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    RMAN>
    connected to recovery catalog database
    RMAN>
    connected to target database: CUSTPR (DBID=525071053)
    RMAN>
    RMAN> #########################################################################
    2> # LEVEL 0 BACKUP #
    3> #########################################################################
    4>
    5> # Configure backups to be written to disk.
    6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    old RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
    2> # RMAN retains all backups needed to recover the database to any point in time
    3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
    4> # backups that are no longer required by the retention policy. To exclude a
    5> # backup from consideration by the policy, you can use KEEP option with the
    6> # BACKUP command.
    7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
    2> # maintenance operations.
    3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    old RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write disk backups to the /backup directory.
    2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
    3> # backup set number, and %p with the backup piece number.
    4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    old RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to back up the control file after each backup.
    2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
    2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
    2> # RMAN won't backup an archivelog or datafile if there already exists a backup
    3> # of that file. The FORCE option can be used to override optimization on a
    4> # specific BACKUP command.
    5> CONFIGURE BACKUP OPTIMIZATION ON;
    old RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Use the SHOW ALL command to see the current configuration settings.
    2> SHOW ALL ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
    RMAN>
    RMAN> # The following commands are run each day to start the backup cycle.
    2> # The steps are:
    3> # - Take an incremental level 0 backup of the database. A level 0 backup is
    4> # a complete backup of the entire file which can be used as the basis
    5> # for a subsequent incremental backup.
    6> # - Backup all archivelogs that have not already been backed up.
    7> # - Delete on-disk archivelogs older than seven days.
    8>
    9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
    10> DATABASE maxsetsize 33G
    11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
    12> delete all input;
    Starting backup at 12/30/2008 22:01:40
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=11 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
    input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
    input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
    input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
    input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
    input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
    input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
    channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
    channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
    piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
    archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
    archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
    archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
    archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
    archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
    archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
    Finished backup at 12/30/2008 22:03:47
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Recovery Manager complete.

  • RMAN-04005: error from target database:

    Hi,
    when I want register my target by
    ]$ rman catalog prdrman/prdrman@PRD target sys/manager@DEV
    I receive this :
    RMAN-04005: error from target database:
    ORA-01031: insufficient privileges
    Do you have any idea ?
    Many thanks before.

    Here are some further hints from documentation:
    ORA-01031: insufficient privileges
    When : SQL> connect sym/sym as SYSDBA
    Additional : init.ora remote_login_passwordfile=EXCLUSIVE or SHARED
    Cause : Username/password is not correct (if the user is added by granting
    SYSDBA to the user, this user is added to the passwordfile with the
    password from the data dictionary)
    or:
    Password file has
    -> incorrect name orapw<name_of_database>
    -> is not in $ORACLE_HOME/dbs
    -> has wrong privileges
    They should be -rwSr-----
    For example:
    -rwSr----- 1 server sdb 1536 Mar 25 08:12 orapwv901
    Solve : You can set the correct privileges (Unix) by issueing
    $ chmod 4640 passwordfile
    As a last resort, recreate the password file and remind to add
    additional privileged (sysdba or sysoper) users

Maybe you are looking for

  • Use parameter to define location of xml-file

    Hi, here is a question about importing data from a xml-file using the xfa.host.importdata A tool we use generates a copy of a 'template'-pdf an put it into a unique folder. This unique folder will contain: (1) a Batch-file (2) a fillable, certified,

  • No audio from HDMI output because High Definition Audio Driver cannot start (Envy 17 Quad)

    Ever since I first bought this laptop two months ago, the audio from the HDMI output has always been inconsistent. I remember it working a couple times, but there were more times when my audio driver didn't recognize that an HDMI cable was plugged in

  • Cannot change user passwords in System Prefs

    They just don't "take." I can change passwords as root in terminal using passwd no problem but not in System Prefs pane. The secure.log hints that something happens: Apr 20 19:08:01 Dualie com.apple.SecurityServer: Succeeded authorizing right system.

  • PSE9 Installation problems

    I've just purchased a tablet that comes with a host of programs, one of which is PSE9, which I am trying to install, with no luck. The installation almost completes but stops at "Shared Technologies" and rolls back the installation. I've tried multip

  • Rate routing std values not appearing during backflush

    Hi , Rate routing is defined from REM product. The REM profile has check to post activities. In MFBF when I try to do assembly backflush the activities are not proposed from rate routing when "Post with correction ". What could be the reason for this