Replication partitioning corrupting target database

Hi,
Essbase v 11.1.3, solaris 10
My colleagues are having a serious problem with replicated partitions. The behaviour is as follows
"We are creating an Essbase partition by means of a MAXL script the creation of which is causing corruption in the Target database. From the point of running the script to generate the partition (not to replicate it), the partition is created successfully but the area of data targeted by the partition appears to be locked and no data can be submitted to the area via smartview. The first time the partition is replicated the data successfully replicates but any subsequent replication does not copy the data across and data in the affected area cannot be edited except by calculation scripts."
The following action has been done to work around the problem
•     Replicated the issue in development environment
•     Cleared Target database prior to creation of partition
•     Used different user account to run the partition
•     Used MAXL to drop all locks on the Target application – no locks exist to drop.
The essbase log had this entry 'Dangling Partition found' and a afew 'Client Commands are Currently Not Being Accepted'.
The members exist in both databases. The error is effecting more than one db.
Thanks,
Nathan

I'm sorry, I was being a little glib in my answer and it didn't really work. The real answer is in 9.3.1 ASO cubes can only be the source for a transparent partition. you have to wait until 11.1.1 for it to be used either way. For what you need you can have your historical data in ASO (or more than one ASO cube) and partition it to BSO for current data. Be careful if you have formulas in the BSO cube that reference ASO cube members. IT can really sow down retieivals. Try to have equivelent formulas in the ASO cube for the history

Similar Messages

Data is not replicated on target database - oracle stream

has set up streams replication on 2 databases running Oracle 10.1.0.2 on windows.
Steps for setting up one-way replication between two ORACLE databases using streams at schema level followed by the metalink doc
I entered a few few records in the source db, and the data is not getting replication to the destination db. Could you please guide me as to how do i analyse this problem to reach to the solution
setps for configuration _ steps followed by metalink doc.
==================
Set up ARCHIVELOG mode.
Set up the Streams administrator.
Set initialization parameters.
Create a database link.
Set up source and destination queues.
Set up supplemental logging at the source database.
Configure the capture process at the source database.
Configure the propagation process.
Create the destination table.
Grant object privileges.
Set the instantiation system change number (SCN).
Configure the apply process at the destination database.
Start the capture and apply processes.
Section 2 : Create user and grant privileges on both Source and Target
2.1 Create Streams Administrator :
connect SYS/password as SYSDBA
create user STRMADMIN identified by STRMADMIN;
2.2 Grant the necessary privileges to the Streams Administrator :
GRANT CONNECT, RESOURCE, AQ_ADMINISTRATOR_ROLE,DBA to STRMADMIN;
In 10g :
GRANT CONNECT, RESOURCE, AQ_ADMINISTRATOR_ROLE,DBA to STRMADMIN;
execute DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE('STRMADMIN');
2.3 Create streams queue :
connect STRMADMIN/STRMADMIN
BEGIN
DBMS_STREAMS_ADM.SET_UP_QUEUE(
queue_table => 'STREAMS_QUEUE_TABLE',
queue_name => 'STREAMS_QUEUE',
queue_user => 'STRMADMIN');
END;
Section 3 : Steps to be carried out at the Destination Database PLUTO
3.1 Add apply rules for the Schema at the destination database :
BEGIN
DBMS_STREAMS_ADM.ADD_SCHEMA_RULES(
schema_name => 'SCOTT',
streams_type => 'APPLY ',
streams_name => 'STRMADMIN_APPLY',
queue_name => 'STRMADMIN.STREAMS_QUEUE',
include_dml => true,
include_ddl => true,
source_database => 'REP2');
END;
3.2 Specify an 'APPLY USER' at the destination database:
This is the user who would apply all DML statements and DDL statements.
The user specified in the APPLY_USER parameter must have the necessary
privileges to perform DML and DDL changes on the apply objects.
BEGIN
DBMS_APPLY_ADM.ALTER_APPLY(
apply_name => 'STRMADMIN_APPLY',
apply_user => 'SCOTT');
END;
3.3 Start the Apply process :
DECLARE
v_started number;
BEGIN
SELECT decode(status, 'ENABLED', 1, 0) INTO v_started
FROM DBA_APPLY WHERE APPLY_NAME = 'STRMADMIN_APPLY';
if (v_started = 0) then
DBMS_APPLY_ADM.START_APPLY(apply_name => 'STRMADMIN_APPLY');
end if;
END;
Section 4 :Steps to be carried out at the Source Database REP2
4.1 Move LogMiner tables from SYSTEM tablespace:
By default, all LogMiner tables are created in the SYSTEM tablespace.
It is a good practice to create an alternate tablespace for the LogMiner
tables.
CREATE TABLESPACE LOGMNRTS DATAFILE 'logmnrts.dbf' SIZE 25M AUTOEXTEND ON
MAXSIZE UNLIMITED;
BEGIN
DBMS_LOGMNR_D.SET_TABLESPACE('LOGMNRTS');
END;
4.2 Turn on supplemental logging for DEPT and EMPLOYEES table :
connect SYS/password as SYSDBA
ALTER TABLE scott.dept ADD SUPPLEMENTAL LOG GROUP dept_pk(deptno) ALWAYS;
ALTER TABLE scott.EMPLOYEES ADD SUPPLEMENTAL LOG GROUP dep_pk(empno) ALWAYS;
Note: If the number of tables are more the supplemental logging can be
set at database level .
4.3 Create a database link to the destination database :
connect STRMADMIN/STRMADMIN
CREATE DATABASE LINK PLUTO connect to
STRMADMIN identified by STRMADMIN using 'PLUTO';
Test the database link to be working properly by querying against the
destination database.
Eg : select * from global_name@PLUTO;
4.4 Add capture rules for the schema SCOTT at the source database:
BEGIN
DBMS_STREAMS_ADM.ADD_SCHEMA_RULES(
schema_name => 'SCOTT',
streams_type => 'CAPTURE',
streams_name => 'STREAM_CAPTURE',
queue_name => 'STRMADMIN.STREAMS_QUEUE',
include_dml => true,
include_ddl => true,
source_database => 'REP2');
END;
4.5 Add propagation rules for the schema SCOTT at the source database.
This step will also create a propagation job to the destination database.
BEGIN
DBMS_STREAMS_ADM.ADD_SCHEMA_PROPAGATION_RULES(
schema_name => 'SCOTT',
streams_name => 'STREAM_PROPAGATE',
source_queue_name => 'STRMADMIN.STREAMS_QUEUE',
destination_queue_name => 'STRMADMIN.STREAMS_QUEUE@PLUTO',
include_dml => true,
include_ddl => true,
source_database => 'REP2');
END;
Section 5 : Export, import and instantiation of tables from
Source to Destination Database
5.1 If the objects are not present in the destination database, perform
an export of the objects from the source database and import them
into the destination database
Export from the Source Database:
Specify the OBJECT_CONSISTENT=Y clause on the export command.
By doing this, an export is performed that is consistent for each
individual object at a particular system change number (SCN).
exp USERID=SYSTEM/manager@rep2 OWNER=SCOTT FILE=scott.dmp
LOG=exportTables.log OBJECT_CONSISTENT=Y STATISTICS = NONE
Import into the Destination Database:
Specify STREAMS_INSTANTIATION=Y clause in the import command.
By doing this, the streams metadata is updated with the appropriate
information in the destination database corresponding to the SCN that
is recorded in the export file.
imp USERID=SYSTEM@pluto FULL=Y CONSTRAINTS=Y FILE=scott.dmp IGNORE=Y
COMMIT=Y LOG=importTables.log STREAMS_INSTANTIATION=Y
5.2 If the objects are already present in the desination database, there
are two ways of instanitating the objects at the destination site.
1. By means of Metadata-only export/import :
Specify ROWS=N during Export
Specify IGNORE=Y during Import along with above import parameters.
2. By Manaually instantiating the objects
Get the Instantiation SCN at the source database:
connect STRMADMIN/STRMADMIN@source
set serveroutput on
DECLARE
iscn NUMBER; -- Variable to hold instantiation SCN value
BEGIN
iscn := DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER();
DBMS_OUTPUT.PUT_LINE ('Instantiation SCN is: ' || iscn);
END;
Instantiate the objects at the destination database with
this SCN value. The SET_TABLE_INSTANTIATION_SCN procedure
controls which LCRs for a table are to be applied by the
apply process. If the commit SCN of an LCR from the source
database is less than or equal to this instantiation SCN,
then the apply process discards the LCR. Else, the apply
process applies the LCR.
connect STRMADMIN/STRMADMIN@destination
BEGIN
DBMS_APPLY_ADM.SET_SCHEMA_INSTANTIATION_SCN(
SOURCE_SCHEMA_NAME => 'SCOTT',
source_database_name => 'REP2',
instantiation_scn => &iscn );
END;
Enter value for iscn:
<Provide the value of SCN that you got from the source database>
Note:In 9i, you must instantiate each table individually.
In 10g recursive=true parameter of DBMS_APPLY_ADM.SET_SCHEMA_INSTANTIATION_SCN
is used for instantiation...
Section 6 : Start the Capture process
begin
DBMS_CAPTURE_ADM.START_CAPTURE(capture_name => 'STREAM_CAPTURE');
end;
/

You must have imported a JKM and after that these are the steps
1. Go to source datastrore and click on CDC --> Add to CDC
2. Click on CDC --> Start Journal
3. Now go to the interface Choose the source table and select Journalized data only and then click on ok
4. Now execute the interface
If still it doesn't work, are you using transactions in your interface ?

From RMAN - Not able to connect to the target database as sysdba

I wanted to configuring the backup server (rman catalog database server) to take RMAN
backups of the varius target databases. while connecting to the target database
from backup server, i am getting ORA-01031: insufficient privileges error.
I created password file and modified the init.ora file in the target server, but
still having connection issue.
I can over come this issue by keep trying many times while using sqlplus.
pbackup1$ sqlplus "sys/oracle @HCPRD as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Apr 25 17:02:56 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name:
ERROR:
ORA-01017: invalid username/password; logon denied
Enter user-name:
ERROR:
ORA-01017: invalid username/password; logon denied
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
pbackup1$ sqlplus "sys/oracle @HCPRD as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Apr 25 17:03:05 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
SQL>
-- finally, after few attempts, i can connect to the target database server as
sysdba ---
While connectiong thru RMAN, get the following error:
RMAN> connect target sys/oracle@HCPRD
RMAN-00571: ===========================================================
RMAN-00569: ========= ERROR MESSAGE STACK FOLLOWS
RMAN-00571: ===========================================================
ORA-01031: insufficient privileges
RMAN> connect target "sys/oracle @HCPRD as sysdba"
RMAN-00571: ===========================================================
RMAN-00569: ======== ERROR MESSAGE STACK FOLLOWS
RMAN-00571: ===========================================================
ORA-12154: TNS:could not resolve the connect identifier specified
Text continued in next action...

Hey,
Please take a look at URL below to see it can help you -
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcnctg002.htm#i1008102
or
http://www.lc.leidenuniv.nl/awcourse/oracle/server.920/a96566/rcmcnctg.htm#443912
regards,
Marcello.

Duplicate target database - is failed due to missing archive log

Hi,
"duplicate target database to " is failed due to required archive log is not found on tape.
After mounting the right tape, how to proceed , please suggest
ERROR:-->
RMAN>
connect catalog *******
connect auxiliary /
connect target ******
Run {
set until time '16-NOV-2008 23:50';
allocate auxiliary channel t1 type 'sbt_tape' parms ....
duplicate target database to mydb;
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/30/2008 10:27:00
RMAN-03015: error occurred in stored script Memory Script
ORA-19501: read error on file "orcl_ARCHIVES_BACKUP_0811160110_u0jvq7vt_1
_1", blockno 1 (blocksize=512)
ORA-27190: skgfrd: sbtread2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1314E (RC14) File data currently unavailable on server
Recovery Manager complete.
Thanks In Advance,

This is basically not a RMAN problem,but a media management issue,which has to be addressed to the TSM staff:
ANS1314E
File data currently unavailable on server
Explanation:
The file data is currently unavailable on the server. A retrieve or restore operation was attempted. Possible causes are:
Data was corrupted at the server
Server found a read error
File is temporarily involved in a reclaim operation at the server
Server requested a tape volume that was marked unavailable.
System action:
Processing stopped.
User response:
Retry the operation. If the problem continues, see your system administrator to determine the problem from the server console or the activity log. Check whether any requests were made for a tape volume that was unavailable. A tape volume may be marked unavailable if prior read errors were encountered or the volume is checked out of the tape library.
Werner

TARGET database is not compatible with this version of RMAN

I am trying to register a database (version 8.0.4) on my catalog database which is version 8.1.7.
I get the following error:
RMAN-06185: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
Does this mean that my RMAN database has to be 8.0.4 ?
What happens if my RMAN database is 8.0.4 and target is 8.1.7 ?
Thanks for any help,
Sameer

check RMAN compatibility matrix
Target/Auxiliary Database|| RMAN Executable|| Catalog Database ||Catalog Schema
8.0.3 8.0.3 >=8.x 8.0.3
8.0.4 8.0.4 >=8.x >= 8.0.4, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.5 8.0.5 >=8.x >= 8.0.5, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.6 8.0.6 >=8.x 8.0.6
8.0.6 8.0.6 >=8.1.x >=8.1.x
8.1.5 8.1.5 >=8.1.x >= 8.1.5
8.1.6 8.0.6.1 >=8.x 8.0.6
8.1.6 8.0.6.1 >=8.1.x >= 8.1.x
8.1.6 8.1.x >=8.1.x >= RMAN executable
8.1.7 8.0.6.1 >=8.x 8.0.6
8.1.7 8.0.6.1 >=8.1.x >=8.1.x
8.1.7 8.1.x >=8.1.x >= RMAN executable
9.0.1 >=9.0.1 >=8.1.x >= RMAN executable
In other words to backup 8.0.4 version u need a separate schema in catalog database and which will be only used for 8.0.4

TARGET database is not compatible with RMAN version

Hi all,
we have an issue related to RMAN version.
A few weeks ago we update our 10.2.0.1 Oracle Database to 10.2.0.4 using 6810189 pacth set.
Now when we try to execute RMAN this is the output:
Recovery Manager : Release 11.1.0.6.0 - Production on Jue Nov 20 12:20:57 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.4 needed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
(I translate the spanish message, maybe the words is not exactly the same in the english version)
As is shown in the output the RMAN version installed by the pacthset is higher than database version, is there a way to downgrade RMAN or to solve this issue?
Thanks in advance,
Alex

I'm pretty sure patchset 6810189 does not install RMAN executable 11g. I did several patchings to 10.2.0.4 and that never happened. Patching may sometimes leave components at a lower level than the patchset,but never the opposite is true. That would be definitely a bug. So you (or someone else) installed 11g software.
Werner

RMAN-06429: TARGET database is not compatible with this version of RMAN

he Hi,
how can i solve this issue . how i will upgrade the Rman. My production database details are below
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
while i'm configuring rman i'm getting below error . please help me.
C:\Documents and Settings\vj.dcruz>rman target / catalog rman01/rman01@upp
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 08:18:02 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
rgds,
john

Johnvd wrote:
Hi Hemant,
i'm doing same thing login 10.2.0.0 database and configure the rman but while connect target its saying that my Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 09:04:59 2011
how its happening is there any where i have to change the path.
Regards,
johnJohn, you need to use the RMAN binary which is located in bin folder of Oracle Database (ie /u01/oracle/product/10.2/db1/bin). You shouldn't use "rman which comes with Oracle 11g client".
If you are using windows, run the following commands in command prompt and then copy/paste the output:
echo 5ORACLE_HOME%
echo %PATH%
If you are using unix, run the following commands in terminal and then copy/paste the output:
echo $ORACLE_HOME
echo $PATH
Regards
Gokhan

Duplicate target database for standby failing with below error

Hello All, Need your assistance
We are creating a physical standby database (standalone) from 2 node RAC database, OS =RHEL5 and DB =11gR2
What we did: We took RMAN backup of primary DB along with archives and copied to standby server in same location. We have modified necessory prameters on primary as well as standby too.
The command we used :
RMAN>connect target sys/pwd@primary auxiliary sys/pwd@stdby
RMAN> run {
allocate auxiliary channel ch1 type disk;
duplicate target database for standby dorecover nofilenamecheck;
release channel ch1;
Note we tried : duplicate target database for standby as well as duplicate target database for standby nofilenamecheck methods too....But no luck..we are getting following error.
channel ch1: reading from backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
channel ch1: ORA-19870: error while restoring backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
ORA-19501: read error on file "/u01/BDB/BWFCCPRD_5fmpdvce_1_1", block number 121856 (block size=8192)
ORA-27072: File I/O error
Additional information: 4
Additional information: 121856
Additional information: 1036288
failover to previous backup
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/20/2011 09:16:11
RMAN-05501: aborting duplication of target database
RMAN-05556: not all datafiles have backups that can be recovered to SCN 41855007833
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
could you pease help to resolve this ....?
Note : Creating standby using RMAN 11g new feature : duplicate target database for standby from active database is not possible in our environment since the network bandwith is tooooo low, We have tried and not able to succeed because of n/w issue, So we are doing this alternate method...!!!
Looking for your valuable advises...
Thanks in Advance....

Take the fresh backup and also check the space crunch. The below clink may help you
ORA-27072: File I/O error Additional information: 2
--neeraj
Edited by: Vishen on Oct 20, 2011 2:14 PM

Duplicate target database not working

Hi All,
I want to clone my exisitng DB to other.
I was refering the below link to do the same.
[http://web.njit.edu/info/limpid/DOC/backup.102/b14191/rcmdupdb006.htm|http://web.njit.edu/info/limpid/DOC/backup.102/b14191/rcmdupdb006.htm]
OS:Solaris 10
Oracle version:10.2.0.4.0
What I did tilll now:-
1) Created a database MYDB1 in archive mode
2) Created one tablespace, user and 1 table in DB
3) Registered the MYDB1 in RMAN Db.
4)Created a Pfile from MYDB1 database and changed db value and other values of MYDB1 to MYDB2(Database name to be duplicate)
5)Created a password file
6)Startup MYDB2 in NOMOUNT stage.
7) At RMAN prompt I have done below things to but i have getting the error
rman:rman:>rman target sys/mydb1@mydb1 catalog rman/rman auxiliary sys/mydb2@mydb2
Recovery Manager: Release 10.2.0.4.0 - Production on Fri Sep 7 12:20:22 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: MYDB1 (DBID=3867673817)
connected to recovery catalog database
connected to auxiliary database: MYDB2 (not mounted)
RMAN> DUPLICATE TARGET DATABASE TO mydb2;
Starting Duplicate Db at 07-SEP-12
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=162 devtype=DISK
WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
contents of Memory Script:
   set until scn 911233;
   set newname for datafile 1 to
"+disk2";
   set newname for datafile 2 to
"+disk2";
   set newname for datafile 3 to
"+disk2";
   set newname for datafile 4 to
"+disk2";
   set newname for datafile 5 to
"+disk2";
   restore
   check readonly
   clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 07-SEP-12
using channel ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/07/2012 12:21:01
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
745933 B F A DISK        07-SEP-12       1       1       NO         FULL_BACKUP
745934 B F A DISK        07-SEP-12       1       1       NO         FULL_BACKUP
RMAN> list backup of database;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
745933 Full    549.12M    DISK        00:01:19     07-SEP-12
        BP Key: 745935   Status: AVAILABLE Compressed: NO Tag: FULL_BACKUP
        Piece Name: /backup/oracle_backup/test_dir/rman_bkp/mydb1_0gnkjokf_1_1
List of Datafiles in backup set 745933
File LV Type Ckp SCN    Ckp Time Name
1       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/system.256.793120373
2       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/undotbs1.258.793120373
3       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/sysaux.257.793120373
4       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/users.259.793120373
5       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/tbs_umesh.266.793207735
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup/oracle_backup/test_dir/rman_bkp/mydb1_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/software/oracle/product/10.2.0/database/dbs/snapcf_mydb1.f'; # default
RMAN> exit
Recovery Manager complete.
@rman:rman:>Please Suggest where i am going wrong..
Regards
Umesh Gupta

WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
You must check DB_FILE_NAME_CONVERT parameter on MYDB2 database
or I think you must add DB_FILE_NAME_CONVERT, LOG_FILE_NAME_CONVERT to DUPLICATE Command.
DUPLICATE TARGET DATABASE TO MYDB2
SPFILE
SET
"DB_FILE_NAME_CONVERT"="+DATA/MYDB1/","+DATA/MYDB2"
... Regards
Mahir M. Quluzade
www.mahir-quluzade.com

Issue in OWB mapping - when changing source and target database

Hi,
I need help for resolution of the issue I am facing when moving mapping from development environment to QA.
Here is situation,
We develop ETL using one source, one staging and one target database.
In development we use one control_center for Source to staging and another control center staging to target.
All works fine in development.
Now I have created new runtime repository and imported all OWB projects (with full dependencies, exact replica of development). Now I need to change source and staging and target as different database.
I have created new database location connections and defined/attached DB connectors with stage and target location.
Now issues are
1.     Two Staging mapping are not able to bound with source table (giving different error
a.     One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b.     Other mapping show error for source table/object not bound to repository
2.     All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
Not sure how to proceed from here.
I have recreated new repository and re-imported all project/mappings and defined all connection but still same issue.
Thanks in advance,
Vipin

1. Two Staging mapping are not able to bound with source table (giving different error
a. One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b. Other mapping show error for source table/object not bound to repository
The above error were resolved when re-synchronized the table (for few I have to reimport the table) and mapping.
2. All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
The above error still pending. My target mapping are not able to deployed/compiled.
For the above I have defined one Staging location to one target target location and target location have connector to staging (not sure if I have to define connector name same as staging location, as I have created DB connector with different name but reference database is same as staging location).
Mapping are assoicated with desired data locatoin and meta data.
control center is also have that data location.
Mapping are configured for the desired location.

RMAN duplicate target database for standby from active fails to create newname for system tablespace/datafile

When executing 'duplicate target database for standby from active' the system tablespace/datafile (datafile 1) is not cloned. All other datafiles clone successfully. The RMAN process aborts with the following errors while attempting to clone the system tablespace/datafile.
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03135: connection lost contact
Here are the details:
Primary is 11.2.0.2 RAC database on an Exadata platform
Standby is 11.2.0.2 Single Instance database (same patch level as primary) on a Red Hat Linux box
This is an ASM to ASM duplication.
This is not unique to this database. We tried another database and go the same behavior - all datafiles clone successfully with the exception of the system tablespace/datafile.
We have traced the RMAN execution and it seems to fail when it is trying to assign a NEWNAME to the system tablespace/datafile.
We even issued an explicit SET NEWNAME command but RMAN ignored it.
We also shutdown the primary and started is up in mount mode thinking that something had ahold of the System Tablespace/datafile.
We also opened up the network firewall to allow permit any,any traffic.
We increased the max_server_processes
and added TCP.NODELAY=yes to the sqlnet.ora file.
There seems to be some artifact present in our Primary System tablespace/data file that is preventing it form being cloned.
checked all alert files grid, asm, and dbhome - no abnormal messages.
We are in the process of restoring the database from a backup but we would prefer to get this working using the 'Active Database' methodology

I successfully created the standby database using RMAN backup and recovery.
I started the managed recovery. Archive logs are being sent from the primary to the standby ( I can see them in ASM), but the standby is not applying them.
I get the following messages in the standby alert log...
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:19:58 2013
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Tue Nov 26 16:20:01 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:11 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:22 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:32 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
I don't see any MRP processes:
select process,
status,
    thread#,
    sequence#,
   block#,
blocks
7     from v$managed_standby;
PROCESS   STATUS          THREAD# SEQUENCE#     BLOCK#     BLOCKS
ARCH      CLOSING               2     154363          1        132
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  1     145418        121          1
RFS       IDLE                  0          0          0          0
PROCESS   STATUS          THREAD# SEQUENCE#     BLOCK#     BLOCKS
RFS       IDLE                  0          0          0          0
12 rows selected.
SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
   THREAD# SEQUENCE# APPLIED
         2     154356 NO
         2     154357 NO
         1     145411 NO
         2     154358 NO
         2     154360 NO
         2     154361 NO
         1     145414 NO
         1     145415 NO
         2     154362 NO
         2     154363 NO
         1     145416 NO
11 rows selected.
I do have the archive logs that cover sequences 154158-154257
Crosschecked 38 objects
Crosschecked 62 objects
Finished implicit crosscheck backup at 26-NOV-13
Starting implicit crosscheck copy at 26-NOV-13
using channel ORA_DISK_1
using channel ORA_DISK_2
Crosschecked 2 objects
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154377.344.832521989 RECID=29 STAMP=832521990
validation succeeded for archived log
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154378.346.832521991 RECID=31 STAMP=832521993
Crosschecked 31 objects

Problem with duplicate target database from active database

Hi all,
i try duplicate database from active database
- I have von target and auxiliary the same SYS Password
- tnsping wogks in both directions fine
- sqlplus to target and auxilairy works from both server
- Metalink Solution 1056174.1 not help
but in the Rman log become this error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on a1 channel at
ORA-17629: Cannot connect to the remote database server
ORA-17629: Cannot connect to the remote database server
i do do :
rman target sys/PASSWD@TARGET auxiliary sys/PASSWD
run
ALLOCATE CHANNEL a1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL d1 DEVICE TYPE DISK;
duplicate target database to XXXXX
from active database
DB_FILE_NAME_CONVERT ('/XXXX/XXXX/XXXXXX','/XXXXX/XXXXXX/XXXXX/')
spfile
parameter_value_convert '/XXXX/','/XXXXX/'
set log_file_name_convert '/XXXXX/','/XXXXX/'
any Idea ?
Best Regards

Don't know if this will help, but I use the connect string below to connect, then run the command below. This is, of course, after the rman backup from the prod system has been copied to the flash_recovery_area of the aux database. All file paths are the same between the two systems. Works like a charm most nights. The local tnsnames file on the rman catalog server has working entries for @SDPROD, @rman and @SDSTB.
[Connect String]
rman TARGET SYS/xxxxx@SDPROD CATALOG rman/xxxxx@rman AUXILIARY SYS/xxxxx@SDSTB cmdfile D:\cladmin\Scripts\DuplicateSD.rcv LOG=D:\cladmin\Logs\DuplicateSD.f
[Command file block]
RUN{
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE TO DATABASENAME
NOFILENAMECHECK;
Edited by: user522620 on Jun 27, 2011 6:36 PM

How to un-register target database in Catalog DB?

I am using 8.0.5. I create a Catalog database and register a target database with it for online backup. How do I un-register a target database from the Catalog DB if I do not want to continue taking backup? Is there any 'unregister' command?
Thanks in advance
- Sanchayan RoyChoudhury
Bangalore, India
null

Let me try...
If u know your dbid (which can be found out by just logging into rman with the target databasse)
login ot the catalog database throught sqlpplus as the catalog schema owner...
run the following query..
SELECT db_key, db_id FROM db WHERE db_id ="dbid just found";
then run
execute dbms_rcvcat.unregisterdatabase(db_key, db_id);
This will unregister your database from the catalog. however keep in mind that you will lose all records of your old backups..
HTH
null

Mapping 2 source structures to a single target database

Hi Experts, My scenario is a Proxy to JDBC in which I need to send data from 2 source structures to 1 target table.
Source structures :                                           Target:
ABC                                                                 XYZ
row1                                                                 InsertStatement
    Item1                                                                  DBTable
                                                                    Action
   (Fields)                                                     Table
                                                                                acess
DEF                                                                              -
row2                                                                          -
   item2                                                                         -
(Fields)
(Fields)
Please let me know how to map the 2 source nodes to the target access node to transfer data from the source tables to target database.
Regards,
Krishna

You should make use of BPM to collect the two source structures.
One of the BPM examples mentioned in IR --> SAP BASIS ---> SystemPatterns can be referred for this purpose.
Once the messages are collected, perform a 2:1 mapping (two Proxies as source message and one JDBC message as target).
If you want the mapping logic then please provide a proper format of both your Source and Target messages and the expected mapping, so that someone from SDN can help you out.
The target structure provided is a bit confusing.
Are you going to receive two different proxy messages (i.e. two different calls) or just one Proxy call and there you will have two different nodes within the same message??? ...... me confused
Regards,
Abhishek.
Edited by: abhishek salvi on Sep 25, 2009 11:51 AM

Unable to connect my target database

I am trying to create a clone of my database named proddb using my production RMNA backup,
so when i export ORACLE_SID=proddb
and then try to connect to my rman using
rman target /
its showing connected to target database clonedb
i have checked the servicxes and there are no services named clonedb and their is no entry in my tnsnames or listner as clonedb......

user9038728 wrote:
oracle@localhost ~]$ export ORACLE_SID=proddb
[oracle@localhost ~]$ export ORACLE_HOME=/home/oracle/app/oracle/product/11.2.0/dbhome_1/
[oracle@localhost ~]$ rman target sys/password
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Jan 6 11:27:13 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: CLONEDB (not mounted)
RMAN>
this is the output which i am getting.......Your target/source/Production database should be in OPEN status & your new/clone/auxiliary instance should be in started/not mounted status.
You have to connect as below
$rman target sys/*****@prod auxiliary /
Then target will be production, you have to export SID of auxiliary and test the TNS connectivity to primary.

Replication partitioning corrupting target database

Similar Messages

Maybe you are looking for