ORA-01152 -- When Bringing Up Standby Database

Hi All,
I'm trying to bring a standbye database on the same server as my primary database. i'm doing this to play around, hoping to do it with PRD using separate servers. I have found several good step by step references for doing this. I'm currently using:
http://www.dbaclick.com/modules.php?op=modload&name=News&file=article&sid=366&mode=thread&order=0&thold=0
I have tried several things to get this up. I have shutdown the primary db and manually copied the datafiles to the standby location and then created a standby control file. I have also tried taking an image copy of the datafiles using RMAN and then creating the standby control file. Both produce same result. I can startup mount the Standby db but when i try to open the standby db in read only mode i get the following:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1:
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\standby\SYSTEM01.DBF'
Does anyone have any idea as to why i'm getting this? Is there a preferred way to copy the primary db's datafiles to create standby. According to my instructions the manually copied datafiles shoudl be taken BEFORE the standby control file is generated. Any suggestions would be greatly appreciated... i've been wrestling with this for far too long.
Thanks,

i got it to go. I believe what i did wrong was not configure my parameters files correctly. LOG_ARCHIVE_DEST_2 was erroring out so the archive logs were not applied to the standby database. I manually copied and applied the archive logs to my Standbye. I was then able to open in read only. After that I had to create a password file for my standby which made the LOG_ARCIVE_DEST_2 parameter work.
I'm good to go... thanks

Similar Messages

ORA-01152 when restoring from RMAN backupset in NOARCHIVELOG mode

Hi all,
I got the error ORA-01152 when I tried restoring an Oracle 10g R1 database from an RMAN backupset into a new server. The error returned when it reached to the level of opening the database in resetlogs.
The database runs on NOARCHIVELOG mode and on Windows 2003 Server SP2 32-bit.
Following is what I did in RMAN:
set ORACLE_HOME=D:\oracle\product\10.1.0\db_1
set ORACLE_SID=DAWA
set PATH=D:\oracle\product\10.1.0\db_1\bin;%PATH%
cd %ORACLE_HOME%\bin
rman target sys/mypassword
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile=X:\temp\DawaPFILE.ORA
connected to target database (not started)
Oracle instance started
Total System Global Area 1048576000 bytes
Fixed Size 792200 bytes
Variable Size 551807352 bytes
Database Buffers 494927872 bytes
Redo Buffers 1048576 bytes
RMAN> restore controlfile from
'X:\temp\Flash_Rec\DAWA\AUTOBACKUP\2011_07_16\O1_
MF_S_756655133_7226R018_.BKP';
Starting restore at 19-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=270 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL01.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL02.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL03.CTL
Finished restore at 17-AUG-11
alter database mount;
database mounted
catalog backuppiece 'X:\temp\PUMHJATD_1_1';
catalog backuppiece 'X:\temp\PTMHJ91Q_1_1';
/* Rename the Redologfiles,so that they can be created in new locations
the database is opened in resetlogs */
SQL>conn sys as sysdba
-- get registered files from SELECT * FROM V$LOGFILE
SQL> alter database rename file
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO01.LOG' to
'X:\oracle\oradata\dawa\REDO01.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO02.LOG'
to 'X:\oracle\oradata\dawa\REDO02.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO03.LOG'
to 'X:\oracle\oradata\dawa\REDO03.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO04.LOG'
to 'X:\oracle\oradata\dawa\REDO04.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO05.LOG'
to 'X:\oracle\oradata\dawa\REDO05.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO06.LOG'
to 'X:\oracle\oradata\dawa\REDO06.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO07.LOG'
to 'X:\oracle\oradata\dawa\REDO07.LOG';
/* Now in RMAN: restore the datafiles
    to new locations and recover. */
RMAN> run{
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS201' TO
'D:\oracle\oradata\dawa\UNDOTBS201';
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS202' TO
'D:\oracle\oradata\dawa\UNDOTBS202';
restore database;
switch datafile all;
alter database open resetlogs;
.../* alter database open resetlogs returned the errors: */
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 08/18/2011 08:44:45
ORA-01152: file 2 was not restored from a sufficiently old backup
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DAWA\UNDOTBS206'Thanks in advance.

SYS @ DAWA> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SYS @ DAWA> startup mount
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size                   792200 bytes
Variable Size             551807352 bytes
Database Buffers          494927872 bytes
Redo Buffers                1048576 bytes
Database mounted.
SYS @ DAWA> recover database using backup controlfile until cancel;
ORA-00279: change 329012 generated at 03/08/2005 16:24:46 needed for thread 1
ORA-00289: suggestion :
X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC
ORA-00280: change 329012 for thread 1 is in sequence #6
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'X:\ORACLE\ORADATA\DAWA\SYSTEM01.DBF'You can download the alert log from here:
http://ahmedbaraka.com/temp/alertdawa.log

Encountering ORA-01152 when implementing DataGuard

Working of a 2-node cluster hosting 11.1.0.7 on a Linux RH4 platform, and attempting to implement DataGuard on a single node with same OS and same DB version, and followed document http://www.oracle.com/technology/deploy/availability/pdf/dataguard11g_rac_maa.pdf
The "duplicate target " command works successfully, and having recreated the sp file on the standby node, when I attempt to startup the standby database I get the following error.
SQL> startup
ORACLE instance started.
Total System Global Area 534462464 bytes
Fixed Size 2161400 bytes
Variable Size 314574088 bytes
Database Buffers 209715200 bytes
Redo Buffers 8011776 bytes
Database mounted.
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+DATA/abcdg/datafile/system.258.697912407'
I have re-tried several times without success - any ideas anybody?

I've skimmed the PDF and I think what has happened is that you may have slightly diverged from the sequence shown by issuing "startup" instead of "startup mount", the difference being that "startup" tries to open the standby database in read only mode, which is when ORA-01152 is thrown.
I'm assuming here that the rman duplicate operation does not include a recovery phase, if that is true then the restored datafiles will need recovering to a consistent state before the database can be opened in read-only mode.
In short you probably just need to issue:
recover managed standby database disconnect;and let managed recovery run the archive logs in. Once it is consistent then subsequent "startup" commands should work without error.
If you don't actually want it open read-only then you can just leave it in a mount state and running managed recovery.

ORA-01031 WHEN CONNECTING TO AUXILIARY DATABASE

Hi
i am currently trying to to create a standby database using RMAN using the ORACLE RMAN Backup and recovery book.
I get the ORA-01031 when i connect to the auxiliary database.
i do the following:
RMAN> connect target sys/password@primary
connected to target
RMAN > connect auxiliary sys/password@aux1
ORA-01031.............insufficient privileges
obviously the database aux1 hasnt been created yet but i have configured the tns and listener and both work fine, also created a password file and created a pfile from the spfile in the primary database as instructed by the book. I also started the aux1 database in nomount mode as well.
does any one have any ideas where i maybe going wrong?
thanks

conn sys/pwd@aux1 as sysdba ,what happens to this
in sqlplus
add an entry to your TNSNAMES.ora
SQLNET.AUTHENTICATION_SERVICES = (NTS)
We dont need this entry this is for OS authenicarion sorry
then try again
Version and OS?
Message was edited by:
Maran Viswarayar
Message was edited by:
Maran Viswarayar

Error - when creating a standby database with EM 10g Grid Control

Hi,
I am experiencing some problems when I want to create through the EM 10g Grid Control a standby database from a allready existing db. At step 2 when the files should be generated and copied to the other system, I am always getting the error that there isn't enough disk space on the other system. This can't be because there is at least 30GB free and the installer is asking for less than 1GB. I was searching the whole internet for a solution to this issue, but there was just nothing that could help me out with that point...
Has someone an idea at this point? Thanks for helping...
I am working on a Windows 2003 Server - Enterprise Edition for every system (Grid Control, Primary DB and Standby DB).
Best regards,
Patrick.

Check that filesystem space using GC under targets>hosts on which you are trying to create standby. Do you have any specific error message from GC ? If GC shows proper size under host filesystem section then there shuld be no such problem. Double chk ur locations too.
Regards,
http://askyogesh.com

"failed to read POST response" when adding a standby database

Hello everybody,
I've got a problem ...
I try to create a standby db using the Oracle Grid Manager. When running the job, it is broken in step "httpOneDatafile" with message "failed to read POST response".
In metalink, I found the one-off patch 6670069. As it is only applicable to Oracle agent 10.2.0.4, I've de-installed the agent 10.2.0.5 and tried to install patch 6670069 to this version, but all I get is this error:
Prerequisite check "CheckApplicable" failed.
The details are:
Patch 6670069: Required component(s) missing : [ oracle.sysman.top.agent, 10.2.0.4.0 ]
ApplySession failed during prerequisite checks: Prerequisite check "CheckApplicable" failed.
I tried with different ORACLE_HOMEs (<path_to_db_home> or <agent_home>) and different PATH (<path_to_db_home>/bin or <agent_home>/bin) variables, but anytime, I get the same message when trying to patch the agent.
Does someone have an idea, what's going wrong?
Environment:
Primary Database : 10.2.0.4 on HPUX 64 Itanium
Standby DB: 10.2.0.4 on HPUX 64 PA-Risc (this combination is ok as we used it in a former config with two 10.2.0.2 DBs for the last 2 years...)
Oracle agents: 10.2.0.3 up to 10.2.0.5
As I'm trying for 1 week now, any (ANY!) idea is very welcome...
Regards,
Roland

JVM is probably not the correct forum for this post. JVM is for issues related to the RDBMS resident Oracle proprietary java VM, which isn't involved in what you are doing here.

ORA-24544 When Creating a Standby From RAC One Node

I have a RAC One Node database running on node A and am attempting to create a Data Guard standby on node B using the following RMAN command -
duplicate target database for standby from active database
Error returned is -
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/10/2015 11:11:06
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-24544: Oracle RAC One Node instance is already running.
Can anyone advise ?
Thanks in advance

Hi,
ORA-24544: Oracle RAC One Node instance is already running.
Cause: An instance startup failed because an instance of the Oracle RAC One Node database was already running on one of the cluster nodes.
Action: In Oracle RAC One Node, avoid any attempt to start a second instance by any means while the instance is already running.
I have never used One Node RAC, but it looks like RMAN trying to start an offline instance of current One Node RAC on Node B.
HTH,
Pradeep

ORA-27102 when creating a new database

I have a 10.2.0.4 RAC database on 64-bit Redhat Enterprise Linux AS Release 4.
We have 32GB on both machines in this cluster. Currently there are 5 databases running, each with 1GB SGA and 256M SGA. When I try to create a new database, with the same memory requirements, I get an ORA-27102. I am sure we have set up our OS fine, according to suggestions from Oracle. Linux returns: Linux-X86_64 Error: 28: No space left on device
$> sysctl -a
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.shmmax = 4294967295
kernel.sem = 256 32000 100 128
$> free
total used free shared buffers cached
Mem: 32890432 8599000 24291432 0 58084 6003368
-/+ buffers/cache: 2537548 30352884
Swap: 8385792 0 8385792
So, why am I getting an "out of memory" message... I see 20+GB free...
Edited by: jbednarz on Jan 14, 2009 3:08 PM

jbednarz wrote:
, I get an ORA-27102. Linux returns: Linux-X86_64 Error: 28: No space left on deviceIs that the complete error stack, from alert.log?
kernel.shmall = 2097152This could be "it". This is system wide total, in pages. What is your page size?
There might be other parameters that need increasing as you add instances. Check Oracle and linux documentation.

Getting ORA-01031 when attempting to Create Database

I am attempting to issue a CREATE DATABASE statement via JDBC but I am getting a "ORA-01031: insufficient privileges" error. I am logged in as an administrator and I have no trouble creating tables. I am also receiving the same error when attempting this from SQLPlus. I'm stumped.
Thanks,
Pino

Pino,
I haven't verified this, but only the SYS user can create a DATABASE in Oracle, and you also need to use a special login (when going via SQL*Plus) which JDBC cannot handle. Hence your failures both via JDBC and SQL*Plus.
By the way, if you are new to Oracle, but have experience in another database, then the Oracle idea of a DATABASE is probably different than what you're used to. That's probably why you're stumped. If you haven't already done so, I suggest reading the Oracle Database Concepts volume of the Oracle documentation, which is available from:
http://tahiti.oracle.com
Good Luck,
Avi.

ORA-2020 when trying to verify database links

I have a problem with verifying database links. I want to create a procedure for checking all database links. this is done like the following:
declare
xRefCursor sys_refcursor;
cursor cDBLinks is
select db_link
from user_db_links;
nDummy number;
begin
for rL in cDBLinks loop
begin
open xRefCursor for 'select 1 from dual@'||rL.db_link;
fetch xRefCursor into nDummy;
close xRefCursor;
dbms_output.put_line(rL.db_link||' established');
exception
when others then
if xRefCursor%isopen then
close xRefCursor;
end if;
dbms_output.put_line(rL.db_link||' error '||sqlerrm);
end;
end loop;
end;
when running the procedure, I get a ORA-2020 : too many database links in use
Cause: The current session has exceeded the INIT.ORA OPEN_LINKS maximum.
Action: Increase the OPEN_LINKS limit, or free up some open links by committing or rolling back the transaction and canceling open cursors that reference remote databases
exact after the count of database links specified in the OPEN_LINKS parameter. As you can see I don't issue any transaction, and also I close every cursor I open...so there should be just one db link active in time. note that increasing the OPEN_LINKS parameter will not be a good solution, as I can't tell how much links are existing for a user.
any suggestions?
regards
Christian
oh, forgot to mention: tried this with 9.2.0.6 and 10.2.0.3 on WINDOWS (so I believe this also occurs in 9.2.0.6 <= DBVersion <= 10.2.0.3)
Message was edited by:
W1zard

As you can see I don't issue any transaction, and also I close every cursor I
open...so there should be just one db link active in time.This is wrong assumption. The closing of the cursor does not mean DB link will be closed too. You have to close database link explicitly.
See:
Managing Database Link
Rgds.

Bringing a Physical Standby database online without (a) tablespace(s)

Dear all,
Is it possible to create a kind of "dblink" in a physical standby database residing in a remote host (another host than the primary production database)? We want to make this standby DB to be online without one tablespace.
Our database consists of 2 parts: a core part (around 55 Gb) - stored in 2 tablespaces, residing in one mounted disk - and an "attachment" part (around 550 Gb) - stored in one tablespace, residing in 2 mounted disks. The attachment part is of less importance. We would like to make a standby DB for the core part and exclude the attachment part (because of its extensive size) to be online.
Currently we can not put this physical standby DB online, since it requires the attachment datafiles to be available.
Would it be a problem if we NFS mount these 2 disks on the host where the standby database resides?
The best solution would be if we can tell the standby DB that there is no need to update the attachment tablespace.
Thanx a lot for anyone reading, thinking and most of all give the solution for my problem...
Agape
Thanx in advance.

Hi Sybrand,
Since we only will use the standby DB in read only mode, maybe the use of a Logical one will be usefull afterall.
Can you please explain how to configure this need (having a standby DB without this one large TB) in a Logical standby DB?
Your help will be highly appreciated.
Thanx
Solution found: Bringing physical standby database to online

ORA-02303 when creating database on Exadata using template with BP12

I get ORA-02303 when creating a RAC database on Exadata. Logs indicate that error happened when applying bundle patch BP12 and probably when running following script: /u01/app/oracle/product/11.2.0.4/dbhome_1/rdbms/admin/catsnap.sql
CREATE OR REPLACE TYPE SYS.RewriteMessage AS OBJECT(
Check the following file for errors:
/u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/catbundle/catbundle_EXA_ACSES01_GENERATE_2014Dec17_13_07_45.log
Apply script: /u01/app/oracle/product/11.2.0.4/dbhome_1/rdbms/admin/catbundle_EXA_ACSES01_APPLY.sql
Rollback script: /u01/app/oracle/product/11.2.0.4/dbhome_1/rdbms/admin/catbundle_EXA_ACSES01_ROLLBACK.sql
Executing script file...
Processing Oracle Database Packages and Types...
CREATE OR REPLACE TYPE SYS.RewriteMessage AS OBJECT(
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents
CREATE OR REPLACE TYPE SYS.ExplainMVMessage AS OBJECT (
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents
Anyone experienced the same issue??

Metalink search points to few bugs. May be opening a SR is a good idea.

Create ONLINE logfile in physical standby database

We have created a physical standby database with rman duplicate command on a remote server
"duplicate target database for standby dorecover nofilenamecheck"
When I see the standby server...Online logfiles are not created however its relevant entries are there in V$LOG and V$LOGFILE views.
I guess it is the default behaviour of duplicate command in RMAN and we can not specify LOGFILE clause when we create standby database.
Now the problem is we could not drop the online logfile on standby database since it's status is "CURRENT", "ACTIVE".
Since the ONLINE LOGFILE are not actually created , "ALTER DATABASE CLEAR LOGFILE GROUP " command returns with error as it could not find the file in the server.
So How we can drop the current/active online logfile and add new ones in standby db?

I'm assuming you have physical standby. Here are step I did in the past.
1) create a backup control file
2) bring the database back using the "recreate control file" it the trace file BUT you need to remove or comment out the line that has the corrupt or missing redo log file. And don't forget to add the tempfile after you recreate the controlfile
example:
alter database backup controlfile to trace;
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS FORCE LOGGING ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/oracledata/orcl/redo01.log' SIZE 200M,
GROUP 2 '/oracledata/orcl/redo02.log' SIZE 200M,
GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M,
# GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M
-- STANDBY LOGFILE
-- GROUP 10 '/oracledata/orcl/redostdby04.log' SIZE 200M,
-- GROUP 11 '/oracledata/orcl/redostdby05.log' SIZE 200M
DATAFILE
'/oracledata/orcl/system01.dbf',
'/oracledata/orcl/undotbs01.dbf',
'/oracledata/orcl/sysaux01.dbf',
'/oracledata/orcl/users01.dbf'
CHARACTER SET WE8ISO8859P1
If you just want to add the standby redo log then using this command.
alter database add standby logfile
'/<your_path>/redostdby01.log' size 200M reuse,

How to change COMPATIBLE with a physical standby database?

Hello.
The obvious answer is do it on both the primary and the standby at the same time... since the reference manual says : "When using a standby database, this parameter must have the same value on both the primary and standby databases.".
However, I was wondering, I have a 10.2.0.3 DB with compatible=9.2.0.5. What will happen if I leave the parameter to 9.2.0.5 on the standby and just make the change to 10.2.0.3 on the primary? Would I be able to continue to apply the logs on the physical standby? Would I be able to open it ? (I understand that the transport won't probably work anymore and that I won't be able to switchover)
I guess those 2 questions are stupid but I haven't found any clear statement yet.
Please stay tolerant. Thank you.
Gregory
PS: I know what are the alternatives.

So the answer is obviously: We cannot do that. That completely makes sense btw. I tried with 10.2.0.1 to 10.2.0.4 and I got:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/22/2008 18:35:55
RMAN-11003: failure during parse/execution of SQL statement: alter
database recover logfile '/u01/app/oracle/oradata/WHITE/redo02.log'
ORA-00331: log version 10.2.0.4.0 incompatible with ORACLE version 10.2.0.1.0
ORA-00334: archived log: '/u01/app/oracle/oradata/WHITE/redo02.log'
I should have think about it before I asked. That would have meant we could revert the database from 10g to 9i any time... And the bootstrap changes are not stored in the redo log...
Gregory

Skip table during automatic standby database

We would like to skip a table from being replicated into a standby database.
We do the following on the standby database
startup nomount;
alter database mount standby database;
recover automatic standby database;
and cancel the process.
and then bring the standby database up to date at night for example.
And during the day we would like to use it as a report database, to see if that is possible.
To be able to do that, we do this:
alter database open read only;
But the problem is, there is one reporting table that we do not like to replicate.
We want to create a database link in the standby (report) database, that links to the table in the live database.
Because we need that data from the live database to be update to date in that table.
That table does not contain data that needs to be stored, so it is no problem if it does not end up in the standby report database.
Problem is that we cannot get Oracle to skip to replicate this REPORTPARAM table.
We tried this
execute dbms_logstdby.skip(stmt => 'SCHEMA_DDL',
schema_name => 'ABSSOLUTE',
object_name => 'REPORTPARAM',
use_like => FALSE);
exectue dbms_logstdby.skip(stmt => 'DML',
schema_name => 'ABSSOLUTE',
object_name => 'REPORTPARAM',
use_like => FALSE);
And when we check SELECT * FROM DBA_LOGSTDBY_SKIP
we see the values in there.
But still this table is being replicated.
How can we stop Oracle from doing that?
( And can when we stopped Oracle from doing that, create a database link with alias to the same table in the live database,
that will be the next step. )

This is the output from select * from dba_logstdby_skip
ERROR     STATEMENT_OPT     OWNER     NAME     USE_LIKE     ESC     PROC
N     SCHEMA_DDL     ABSSOLUTE     REPORTPARAM     N
N     DML          ABSSOLUTE     REPORTPARAM     N
N     INTERNAL      SCHEMA     SI_INFORMTN_SCHEMA     %     N
N     INTERNAL     SCHEMA     APEX_030200     %     N
N     INTERNAL     SCHEMA     XS$NULL     %     N
N     INTERNAL     SCHEMA     ORDPLUGINS     %     N
N     INTERNAL     SCHEMA     APPQOSSYS     %     N
N     INTERNAL     SCHEMA     ORACLE_OCM     %     N
N     INTERNAL     SCHEMA     XDB     %     N
N     INTERNAL     SCHEMA     WMSYS     %     N
N     INTERNAL     SCHEMA     DIP     %     N
N     INTERNAL     SCHEMA     OUTLN     %     N
N     INTERNAL     SCHEMA     EXFSYS     %     N
N     INTERNAL     SCHEMA     ANONYMOUS     %     N
N     INTERNAL     SCHEMA     CTXSYS     %     N
N     INTERNAL     SCHEMA     ORDSYS     %     N
N     INTERNAL     SCHEMA     ORDDATA     %     N
N     INTERNAL     SCHEMA     MDSYS     %     N
N     INTERNAL     SCHEMA     SYSTEM     %     N
N     INTERNAL     SCHEMA     SYS     %     N
N     INTERNAL     SCHEMA     MGMT_VIEW     %     N
N     INTERNAL     SCHEMA     SYSMAN     %     N
N     INTERNAL     SCHEMA     DBSNMP     %     N
The second select however
SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
returns no rows.

ORA-01152 -- When Bringing Up Standby Database

Similar Messages

Maybe you are looking for