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

Similar Messages

How to get RMAN catalog information from Target database?

Hi,
How to get RMAN catalog information from Target database because i don't know about catalog database? is it possible?
Thanks

If you run RMAN backups of a target database using a Catalog schema in another database, the target is not aware of the catalog.
The RMAN backup script would have the connection identifier for the Catalog.
Hemant K Chitale

Old atcsn value from target database

database version: 11.2.0.4.0
goldengate version: 12.1.0.2.0
OS: SunOs 5.10
Hello guys I have a scenario.
I start the primary extract & datapump extract
(primary extract)
          register extract <extract group name> database
          add extract <extract group name>, integrated tranlog, begin now
          add exttrail <extract trail path>, extract <extract name>
          start extract <extract group name>
(datapump extract)
          add extract <datapump extract name>, exttrailsource <extract trail path>
          add rmttrail <remote trail path>, extract <datapump extract name>
          start extract <datapump extract name>
and after I start the primary extract & datapump extract, for the initial load I take an export datapump with flashback_scn=<some_value> from the source database.
I import the data into the target database and I start the replicat
(replicat)
          add replicat <replicat group name>, integrated extrail <extract trail path>
          start replicat <replicat group name>, atcsn <flashback_scn value given in datapump export>
Now my question if I want to start the replicat after one week, and I start it with the atcsn taken during the export datapump for initial load (which was taken one week ago), how would the replicat start if that scn is not present in the source database?
Thank You

DBA2008 wrote:
oracle:tulpcorpadb03$ rman TARGET sys/*****@wcmp AUXILIARY /
Recovery Manager: Release 9.2.0.8.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
I findout this, this is prod db and not allowed to bounce to change, any other workaround to make rman duplicate work without changing this?
SQL> show parameter password
NAME TYPE VALUE
remote_login_passwordfile string NONE
SQL> connect /as sysdba;
Connected.
SQL> select * from v$pwfile_users;
no rows selectedYou are trying to connect from remote host to target host as SYSDBA. It will not be possible unless you have setup password file at target host.(remote_login_passwordfile=EXCLUSIVE). As RMAN automatically tries to connect as SYSDBA, you will fail.
I recommend, you execute duplication command from target host:
rman TARGET sys/***** AUXILIARY sys/password@AUX_TNS

Remove RMAN information from target database control file

Dear Gurus,
Can any one inform me that how I can remove RMAN related information from Target database control file without recreating the control file.
Regards,
asif

I want to remove all RMAN related infromation from control file including the destination specification where backup sets were being created becuase that destination is no more available,
configuration information also need to be removed from control file without recreating the control file.
kindly help,
regards,
asif

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>

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 Duplicating Target Database

Dear DBA's
RH 4
Oracle 9.2.0.8
When I start duplicating my target database with script below everything goes fine until the recover :
RMAN> run
2> {
3> allocate auxiliary channel ch1 type sbt;
4> set newname for datafile 1 to '/u02/oradata/SIEBDEV/system/system01.dbf';
5> set newname for datafile 2 to '/u02/oradata/SIEBDEV/system/undotbs01.dbf';
6> set newname for datafile 3 to '/u03/oradata/SIEBDEV/index/tbs_igd_index01.dbf';
7> set newname for datafile 4 to '/u01/oradata/SIEBDEV/data/dm_casebase_docbase_01.dbf';
8> set newname for datafile 5 to '/u01/oradata/SIEBDEV/data/dm_imdoc_audit_01.dbf';
9> set newname for datafile 6 to '/u01/oradata/SIEBDEV/data/dm_imdoc_docbase_01.dbf';
10> set newname for datafile 7 to '/u01/oradata/SIEBDEV/data/tbs_siebdw_data_01.dbf';
11> set newname for datafile 8 to '/u01/oradata/SIEBDEV/data/tbs_dwhview_01.dbf';
12> set newname for datafile 9 to '/u01/oradata/SIEBDEV/data/tbs_igd_01.dbf';
13> set newname for datafile 10 to '/u01/oradata/SIEBDEV/data/igd_eim_01.dbf';
14> set newname for datafile 11 to '/u01/oradata/SIEBDEV/data/TBS_SIEBEL_EMPTY.dbf';
15> set newname for datafile 12 to '/u01/oradata/SIEBDEV/data/tbs_siebel_data_01.dbf';
16> set newname for datafile 13 to '/u01/oradata/SIEBDEV/data/tools_01.dbf';
17> set newname for datafile 14 to '/u01/oradata/SIEBDEV/data/users_01.dbf';
18> set newname for datafile 15 to '/u01/oradata/SIEBDEV/data/perfstat_01.dbf';
19> set newname for datafile 16 to '/u03/oradata/SIEBDEV/index/tbs_siebdw_index_01.dbf';
20> set newname for datafile 17 to '/u03/oradata/SIEBDEV/index/tbs_siebbig_index01.dbf';
21> set newname for datafile 18 to '/u03/oradata/SIEBDEV/index/dm_casebase_index_01.dbf';
22> set newname for datafile 19 to '/u03/oradata/SIEBDEV/index/dm_imdoc_index_01.dbf';
23> set newname for datafile 20 to '/u03/oradata/SIEBDEV/index/tbs_siebel_index_01.dbf';
24> set newname for datafile 21 to '/u01/oradata/SIEBDEV/data/dm_casebase_audit_01.dbf';
25> set newname for datafile 22 to '/u01/oradata/SIEBDEV/data/tbs_siebview_01.dbf';
26> set newname for datafile 23 to '/u01/oradata/SIEBDEV/data/invoice_app_data01.dbf';
27> set newname for datafile 24 to '/u03/oradata/SIEBDEV/index/tbs_invoice_index01.dbf';
28> DUPLICATE TARGET DATABASE TO SIEBDEV
29> NOFILENAMECHECK
30> PFILE = $ORACLE_BASE/admin/SIEBDEV/initSIEBDEV.ora
31> LOGFILE GROUP 1 ('/u01/oradata/SIEBDEV/rdo/sibdevredog1m1.log',
32> '/u02/oradata/SIEBDEV/rdo/sibdevredog1m2.log',
33> '/u03/oradata/SIEBDEV/rdo/sibdevredog1m3.log') SIZE 104857600,
34> GROUP 2 ('/u01/oradata/SIEBDEV/rdo/sibdevredog2m1.log',
35> '/u02/oradata/SIEBDEV/rdo/sibdevredog2m2.log',
36> '/u03/oradata/SIEBDEV/rdo/sibdevredog2m3.log') SIZE 104857600,
37> GROUP 3 ('/u01/oradata/SIEBDEV/rdo/sibdevredog3m1.log',
38> '/u02/oradata/SIEBDEV/rdo/sibdevredog3m2.log',
39> '/u03/oradata/SIEBDEV/rdo/sibdevredog3m3.log') SIZE 104857600;
40> }
executing command: SET until clause
Starting recover at 20-APR-10
starting media recovery
archive log thread 1 sequence 19 is already on disk as file /u03/archive/SIEBTEST/SIEBTEST_19.arc
archive log thread 1 sequence 20 is already on disk as file /u03/archive/SIEBTEST/SIEBTEST_20.arc
archive log thread 1 sequence 21 is already on disk as file /u03/archive/SIEBTEST/SIEBTEST_21.arc
channel ch1: starting archive log restore to default destination
Finished recover at 20-APR-10
printing stored script: Memory Script
shutdown clone;
startup clone nomount pfile= '$ORACLE_BASE/admin/SIEBDEV/initSIEBDEV.ora';
executing script: Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 3410991136 bytes
Fixed Size 747552 bytes
Variable Size 1040187392 bytes
Database Buffers 2348810240 bytes
Redo Buffers 21245952 bytes
input datafilecopy recid=23 stamp=716818426 filename=/u03/oradata/SIEBDEV/index/tbs_invoice_index01.dbf
printing stored script: Memory Script
Alter clone database open resetlogs;
executing script: Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel clone_default
RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 and serial=:2
RMAN-10002: ORACLE error: ORA-03113: end-of-file on communication channel
RMAN-03002: failure of Duplicate Db command at 04/20/2010 12:13:53
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database:
ORA-01092: ORACLE instance terminated. Disconnection forced
I don't understand what is wrong?
When I check the Alert.log it shows the tablespace UNDOTBS1 doesn't exist !!!!!!!
Tue Apr 20 12:13:51 2010
SMON: enabling cache recovery
Tue Apr 20 12:13:52 2010
Errors in file /u01/app/oracle/admin/SIEBDEV/udump/siebdev_ora_14220.trc:
ORA-30012: undo tablespace 'UNDOTBS1' does not exist or of wrong type
Tue Apr 20 12:13:52 2010
Error 30012 happened during db open, shutting down database
USER: terminating instance due to error 30012
Instance terminated by USER, pid = 14220
ORA-1092 signalled during: alter database open resetlogs...
Please Help...
This dupliaction took me 1 week and crashed me the Test Databases.
Thxs if you can Help.
Bests Carlos

But The UNDOTBS1 is in the ispfile
SQL> startup mount
ORACLE instance started.
Total System Global Area 3410991136 bytes
Fixed Size 747552 bytes
Variable Size 1040187392 bytes
Database Buffers 2348810240 bytes
Redo Buffers 21245952 bytes
Database mounted.
SQL> show parameters undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 18000
undo_suppress_errors boolean TRUE
undo_tablespace string UNDOTBS1
SQL>
SQL>
SQL> select INSTANCE_NAME,STATUS,DATABASE_STATUS,INSTANCE_ROLE from v$instance;
INSTANCE_NAME STATUS DATABASE_STATUS INSTANCE_ROLE
SIEBDEV MOUNTED ACTIVE PRIMARY_INSTANCE
SQL> select NAME,CREATED,OPEN_MODE,ACTIVATION# from v$database;
NAME CREATED OPEN_MODE ACTIVATION#
SIEBDEV 20-APR-10 MOUNTED 2834443258
SQL> r
1* select FILE#,STATUS,ENABLED,NAME from v$datafile
FILE# STATUS ENABLED NAME
1 SYSTEM DISABLED /u02/oradata/SIEBDEV/system/system01.dbf
2 ONLINE DISABLED /u02/oradata/SIEBDEV/system/undotbs01.dbf
3 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_igd_index01.dbf
4 ONLINE DISABLED /u01/oradata/SIEBDEV/data/dm_casebase_docbase_01.dbf
5 ONLINE DISABLED /u01/oradata/SIEBDEV/data/dm_imdoc_audit_01.dbf
6 ONLINE DISABLED /u01/oradata/SIEBDEV/data/dm_imdoc_docbase_01.dbf
7 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_siebdw_data_01.dbf
8 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_dwhview_01.dbf
9 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_igd_01.dbf
10 ONLINE DISABLED /u01/oradata/SIEBDEV/data/igd_eim_01.dbf
11 ONLINE DISABLED /u01/oradata/SIEBDEV/data/TBS_SIEBEL_EMPTY.dbf
FILE# STATUS ENABLED NAME
12 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_siebel_data_01.dbf
13 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tools_01.dbf
14 ONLINE DISABLED /u01/oradata/SIEBDEV/data/users_01.dbf
15 ONLINE DISABLED /u01/oradata/SIEBDEV/data/perfstat_01.dbf
16 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_siebdw_index_01.dbf
17 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_siebbig_index01.dbf
18 ONLINE DISABLED /u03/oradata/SIEBDEV/index/dm_casebase_index_01.dbf
19 ONLINE DISABLED /u03/oradata/SIEBDEV/index/dm_imdoc_index_01.dbf
20 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_siebel_index_01.dbf
21 ONLINE DISABLED /u01/oradata/SIEBDEV/data/dm_casebase_audit_01.dbf
22 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_siebview_01.dbf
FILE# STATUS ENABLED NAME
23 ONLINE DISABLED /u01/oradata/SIEBDEV/data/invoice_app_data01.dbf
24 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_invoice_index01.dbf
As you can see datafiles are there.
I don't get why the recover Fails.
Any clues?
thxs

Views to check the catalog database name from target database.

Hi,
Please help me to find view to check the catalog database name which is connected to my target database because I am new to the current environment where I am working now and the previous DBA have done the set up having 2 catalog database. I want view to check from target database, which can show the catalog database name to which it is connected to.
We can check the catalog database name from the following ways but I want views to check it from target database.
1.TNSnames.ora
2.Any backup script connecting to catalog database.
3.From catalog database we can use rc_database view to check the databases registered with the catalog database.

Please help me to find view to check the catalog database name which is connected to my target databaseYou can check for any RMAN backup jobs that been scheduled on the server.
In the scheduled script check rman command.
You can then identify the database alias (of the catalog db) that is used in the rman backup script.
Once you have found the database alias, check for the database alias entry in tnsnames.ora file present in your target database server.
Once the entry is found, you can find the IP address and catalog db name from the tns entry.
Edited by: st. osh on Nov 22, 2012 11:38 PM

Query to identify the recovery catalog database name from target database

Hi,
How to get the recovery catalog database name from the registered target database?
i dont know my recovery catalog database for my target database.
I know we can use the query
select * from rc_database;
from recovery catalog database to know all the registered database with the recovery catalog but I want to know is there any way or query to identify the recovery catalog database name from target database to which the target database is registered
With Regards
Boobathi P

You can check the backup scripts which you use to backup your target database to get the catalog database name.
And check the corresponding connect string in TNSNAMES.ORA file or tnsping to get the server details of the catalog database.
Edited by: gopal on Apr 12, 2013 12:59 PM

Error: The target database JDBC driver class cannot be loaded

Hi
We have a GTC DB connector deployed and configured in one environment. We are able to provision the users to DB table in that environment.
Then we have taken export of all related data objects(like IT Resource, Resource Obj, Process Defs, Adapter tasks, etc) and imported to another environment.
In this environment we changed the conn parameters in IT resource and made sure that all the files has been copied to respective folders under Xellerate.
When ever we try to provision user to the DB it throws an error message as The target database JDBC driver class cannot be loaded as a response and the create user task is rejected.
Database: MS SQL Server.
App Server: WebSphere App Server 6.1
OIM: 9.1.0.1
Does any one faced this type of issue??
Thanks

Thanks lot for the quick response.
I have copied the sqljdbc.jar file to the ThirdParty folder and restarted in App server. Now that the earlier error "The target database JDBC driver class cannot be loaded" is not appearing while provisioning in the rejected task.
I am getting a new error "GCPROV.ProvTransportProvider.DBProvisioningTransport.DB_GET_CONNECTION_ERROR".
Can you please let me know the reason for this. All the connections parameters are correct to connect to the target databse.
Waiting for the response.

AUXILIARY database update using full backup from target database

Hi,
I am now facing the problem with how to implement AUXILIARY database update to be consistent with the target database during a certain period (a week). I did a fully backup on our target database everyday using rman. I know it is possible to use expdp to realize it but i want to use the current fully backup to do it. Does anybody has idea or experience with that? Thanks in advance!
Regards,
lik

That's OK. If you don't use RMAN to clone your database. You can create a database just using the cold backup of the primary database simply.
Important things are
1) you must catalog all datafiles as image copy level 0 in the cloned database
RMAN> connect catalog rman/rman@rcvcat (in host 1)
RMAN> connect target sys/manager@clonedb (in host 2)
RMAN> catalog datafilecopy
'/oracle/oradata/CLONE/datafile/abc.dbf',
'/oracle/oradata/CLONE/datafile/def.dbf',
'/oracle/oradata/CLONE/datafile/ghi.dbf'
level 0 tag 'CLONE';
2) You need to make incrementals of the primary database to refresh the clone database.Make sure that you need to specify a tag for the incremental and the name of tag is the exactly same as the one used step (1).
RMAN> connect catalog rman/rman@rcvcat (in host 1)
RMAN> connect target sys/manager@prod (in host 3)
RMAN> backup incremental level 1 tag 'CLONE' for recover of copy with tag 'CLONE' database format '/backup/%u';
3) Copy the newly created incrementals (in host 3) to the clone database site (host 2). Make sure the directory must be exactly same.
$ rcp /backup/<incr_backup> /backup/
-- rcp <the loc of a incremental in host 3> <the loc of a incremental in host 2>
4) Apply incrementals to update the clone database. Make sure you provide the tag you specified.
RMAN> connect catalog rman/rman@rcvcat
RMAN> connect target sys/manager@clone
RMAN> recover copy of database with tag 'CLONE';
5) After update the clone database, then delete the incremental backups and uncatalog the image copies
RMAN> delete backup tag 'CLONE';
RMAN> change copy like '/oracle/oradata/CLONE/datafile/%' uncatalog;
*** As you can see, you can clone a database using any methods. The key is you have to catalog the clone database when you refresh it. After finishing it, then uncatalog..

Version Rman catalog higher than target database

Hi,
I have a database 10.1.0.2, but I couldn´t upgrade it to 10.1.0.3 or 10g R2 because this database is used by a application that needs this Oracle database version.
I have the catalog in another host with the same Oracle version, and I want to upgrade this database to 10.1.0.3 at least.
Is there any problem if I do the backups with a catalog with a version higher than the target database?
Thanks a lot.
Laura.

There should not be any problem in backup after upgrade of catalog database.
Cheers
Vignesh

RMAN target database Connectivity problem

Error while connecting to target database also tried as sys user but same error
C:\>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Sep 10 11:06:31 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges

You can try like this
rman target 'DBNAME'
or set ORACLE_SID=DBNAME
then rman target /
Do you multiple oracle homes?
Is it in windows or in Unix
IF it is unix you should login as ORACLE user and execute the commands
Theuser should have the SYSDBA privilge
In windows the user excuting the command the user should be a part of the ORA_DBA group
Edited by: Maran Viswarayar on Sep 10, 2008 1:34 PM

Connecting to Catalog & Target Database

I am trying to register a target database with a recovery catalog. RMAN database and the catalog table space were created. When trying to connect to target with the SID set to the instance name and simply connecting as username/password, I am getting connected to the target. If I try to connect using the connect string, I get the following error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database: ORA-12154: TNS:could not resolve service name
But the TNS names have been properly configured and I am able to connect from sql*plus using the connect string.
Similarly I set the SID to RMAN database and try to connect catalog with username/password I am able to connect to Catalog and if I use connect string for the target, I am getting the same error as mentioned above.
I really do not know, How to resolve this and to connect to Target and RMAN databases simultaneously.

I suggest you do the following to see if the connect strings are really working, either:
1) Change ORACLE_SID to be of the catalog database, now do:
% sqlplus "<user>/<pwd>@<target string> as sysdba"
Does that work? If as I suspect it does not work or connects you to the catalog database (not the target), then it is a missconfiguration of the network files.
2) Do the same for connection to the catalog, set ORACLE_SID to be the one of the target database and do:
% sqlplus "<user>/<pwd>"
Does that connects you to the catalog?

RMAN-04005: error from target database:

Similar Messages

Maybe you are looking for