How to shift Manual Standby Database to Primary Database

Hi all,
My Database edition is Oracle 10G standard Edition and runing 24X7 and configure Manual Stand by Database. if I were changing some iniliazation parameter and datafiles.
What can I do ?
i) How to swift the Manual Stand by Database to Primary Database.
ii) What is the procedure by step by step information need.
Regards.....

If you're using a Manual Standby Database I assume you are using a pfile to apply the archived logs transported from the primary database created while creating the Manual Standard. at that time you should have kept the spfile in place too.
If you have done this, then you can simply open an SQL*Plus session connect as sysdba and issue a simple STARTUP command.
This will use the SPFILE by default and your database will be opened normally.
But if you don't have an SPFILE you can always create one, just specify the necessary control files (not the standby control file) in your pfile, remove unwanted parameters and create the spfile, and use the same step as above and issue a STARTUP.
But once you open your standby database normally you will not be able to switch back to standby mode, you have to recreate it again from a cold backup and create a new standby control file.
Regards,
Tony

Similar Messages

Switchover of a manual standby database (no data guard)

Hi all,
I have a standby database .
I am using Oracle Standard Edition 10.2.0.4 / 10.2.0.5 so I have build a manual standby .
I am able to do a failover in the case something goes wrong; I was thinking if it is possible to do a manual switchover . and failback.
Do you thick that mounting the primary database and applying ALL archivelogs and online redolog to the standby database is enough ?
Do you think this is a supported operation?
How can I check the current scn of a mounted database? (v$database.current_scn shows 0 until the database is opened )
thnk you for every answer
Andrea

helter_skelter wrote:
hi,
You can see current_scn of standby database in v$database.current_scn. It is null only on primary database if it's in mount state.that's the problem: I am unable to mount both database and to check they have the same current_scn
not all changes are written to ARL so you can't recover standby database to exact the same SCN as primaryI thinks this is because the last changes are only recorder in online redolog, so I was thinking that a possible way to simulate a clean switchover could be as follow:
1 - shutdown immediate the primary database on server prod1
2 - shutdown abort the (manual) standby database on server dr2
3 - copy archivelog, controlfiles, tempfiles, onlinelogs from primary to the standby database
3 - copy controlfiles from standby database to primary database
4 - open the database on server dr2. It should open "read write" cleanly (mount + recover from archivelog + recover from onlinelog + open noresetlogs )
5 - mount the database on server prod1. It should mount as a physical standby database.
What do you think about it?
thanks,
andrea

Oracle manually standby database with standard edition

Hi, I want to have a plan for disaster. I'm triying with two virtual machines with oracle database 10g on suse linux. I follow these URLs
http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
http://oramdq.blogspot.com/2009/05/como-configurar-un-sistema-de-alta.html
and it look that work all right.
I know that with manually standby database we applied archived logs, and so, we don't propagate any physical changes to secondary database (standby), for example, if I create a new tablespace, or adding a new datafile to an existing tablespace, it don't work in the secondary database.
Anyone does know how is the better way to apply the physical changes??
Anyone have any scripts to do that?
Thanks in advance.

HI,
Add the STANDBY_FILE_MANAGEMENT = AUTO to the primary parameter file, it will solve it.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams209.htm]
Reagds,
Vijayaraghavan K
Edited by: Vijayaraghavan Krishnan on Feb 24, 2010 7:19 PM

Manual Standby Database

Hi,
I have ORACLE 10.2.0.3.0 64 bit SE1 running on a RHEL4 server. I have a backup server on which I need to create a manual standby database for a (poor man's) high availability environment. We have explored RAC, Dataguard etc and given them up for cost considerations. We understand the potential of up to 15 minutes data loss. I know the general steps necessary to set up the manual standby server. For example, I know I need a cold (or hot) backup of the primary to reset my standby database. Then I need to create the standby control file. I need to write deamon processes to ship the archive logs to the standby server and apply those logs to the database. I am new to ORACLE and would appreciate some specific advice.
(1) Should I use DBCA to create the database on the standby server first? My impression is that using DBCA will set up the enterprise manager, isqlplus and the relevevant entries in oratab etc on the standby server. If I simply install ORACLE 10g on the standby and copy the backup files from the primary server, I will not have access to the database tools that come with ORACLE 10g.
(2) Can someone please share the scripts you may have written? or point me to some skeleton scripts?
(3) What are the failure points for manual standby databases? What do I need to pro-actively monitor? For example, if the logs are not being applied properly to the standby database for a prolonged period, I would like to know about it.
(4) What are the procedures for recovering from a failed master database?
(5) Where can I learn more about the subject? I will need specific commands to setup the standby. Are these procedures documented somewhere?
Thanks!
- Rajesh

Try this one Manual Standby Database under Oracle Standard Edition
Or search the subject on google, many results.
No, you will not create "standby" using DBCA, you need to use primary's backup to restore on standby server and constantly recover.

How to convert logical standby database to Physical Standby Database

Hi,
Does anyone know how to convert logical standby database(10.2.0.3) to Physical Standby Database(10.2.0.3)? Is this possible? If so,please give me steps for it.
Thanks.
Regards,
RJ.

I don't believe this to be possible. One of the steps invloved in the creation of a logical standby is the following:
ALTER DATABASE OPEN RESETLOGS;
This makes the logical standby a different incarnation of the db from the primary.
A physical standby is a binary copy of a primary db, a logical standby is a completely seperate db that just happens to get sql statements applied to it that are generated from a primary db, but is open read/write.
One avenue, though would be if you had flashback database enabled and you flashed back all the way to when the db was a physical standby and then rolled forward with the archived redo logs.
It's somewhat unlikely you are in that situation, but that is a possibility.
Indeed the 11g snapshot standby does this sort of thing:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/manage_ps.htm#sthref740
jason.
http://jarneil.wordpress.com

If the production database i down, how to switch to standby database using the replication environment in ASsE

This question is in Business Continuity Plan (BCP)
if the production database is down, how to switch to standby database using the replication environment in ASE

Assuming you're referring to Sybase's Replication Server (repserver) product ...
Repserver moves data changes from one database to another.
Repserver can't 'switch' your application to use a different database; something outside of repserver has to do the actual switching.
If your application happens to be connecting to your ASE via Sybase's OpenSwitch (or similar) product, then OpenSwitch would be responsible for switching your application to use the standby database. Whether you have OpenSwitch perform the switch automatically, or via a manual command, is up to your BCP requirements.
If your application connects directly to ASE then you'll have to decide how/when to get your application to switch to the standby database. In the simplest form this would require shutting down the application, making sure replication is quiesced (ie, all in-flight transactions have been applied to the standby database), modify the interfaces/sql.ini file (used by your application) to point to the standby database, make any customized changes to the standby dataserver/database (eg, unlock application logins, take databases out of 'dbo use only' mode, etc), and startup the application (at this point it should connect to the standby database per the changes to the interfaces/sql.ini file).

How to create a standby database?

I am running Oracle 8.1.5 on Sun Solaris. How to create a standby database? Can somebody tell me the step-by-step procedure?

Can you tell what version of Oracle you are running, because the steps can vary depending on your version.

How to create physical standby database without dataguard

Hi,
Can anyone please help me how to create Physical Standby Database without dataguard. As i am using Oracle 10.2.0.1 Standard Edition for production databases.
Please find the specifications of my server :
Database : Oracle 10.2.0.1(Standard Edition)
Server : Linux 4.0(32 bit machine)
As we know that Dataguard cannot be created in Standard Edition as we dont have that option in this edition. So please help me how to create the physical standby database.
Thanks in advance.
Regards,
Farooq

Hello,
I hope this link helps you out...
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm
http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
Thanks & Regards
Pratik Lakhpatwala
Jr Oracle DBA
Edited by: Pratik.L on Dec 31, 2009 12:03 PM

Manual Standby Database from EE to SE1

Can I do a Manual Standby Database from Oracle Enterprise edition (EE) to Oracle Standard Edition One (SE1)?

Hi,
You can created a manual standby for EE, But you need to purchase a seperate licence for standby database also.
See oracle licencing manul in oracle documentation.
Thanks and Regards,
Satish.G.S

Manual Standby Database not in sync with missing archivelogs

Hello,
OS: Solaris
DB: Oracle 11.2.0.1 EE
Not Using ASM or RAC
I have a Production database that is in archivelog mode and a Standby DR server.
Both servers (Prod, Standby) have exact same structure and db name/version.
We manually scp archive logs and recover them to a manual standby database via SQL Scripts "cron". (I.E. set autorecovery on; recover standby database;)
We recently got out of sync with our log files and have not been applying them to the standby. As part of Prod Maintenance, these log files were deleted and are not available anymore.
I've tried several ways to "rebuild" our standby database. I have tried to Shutdown prod, backup all the db files and scp them to standby, re-create standby controlfile and startup mount and recover standby.
Every time I try to apply a new archive log via recover standby, these are the errors:
ORA-00279: change 211077622 generated at 1/27/2012 12:18:42 needed for thread 1
ORA-00289: suggestion : /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
ORA-00280: change 211077622 for thread 1 is in sequence #69486
ORA-00308: cannot open archived log '/oradump/arch/PROD/PROD_arch_1_69486_736618850.arc'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-10879: error signaled in parallel recovery slave
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: '/oradevices/PROD/oraPRODsystem1.dbf'
When I check v$log_history, the new logs have not been applied.
I've also tried the "Restore from incremental backup via SCN" method with same results.
Is there a way to re-create the standby clean and ensure that the log chain that is currently broken gets fixed or reset?
I would eventually like to get DataGuard in here, but that's not the case at the moment.
Thanks for your suggestions.
-Dav

if you are using the cold backup to create the standby database, Check that have you followed the following steps or not.
1. remove
all the datafiles and controlfiles from the standby database.
2. Create a new standby controlfile of the production for standby using the following cmd
'alter database create standby controlfile as 'Location';'
3. move the new controlfile to standby database server location as specified in initialization parameter file.
4. Restore all the datafiles to its appropriate loaction which was taken through cold backup.
5. startup nomount
6. alter database mount standby database;
7. recover standby database.
scp the archive log sequence that is asked by the database, from production.
You can try this steps.

How to sync the standby database with the primary?

Hi..We have dataguard setup for our production databases(10.2.0.3).
I need one clarification regarding the standby database sync with primary.We identified one of our databases is not in sync with the primary and for longtime the archives are not getting applied at the secondary.
We decided to take the incremental (from SCN)backup from primary and use that at the standby to resolve the gap as described in the book "Oracle dataguard concepts and administration".
But, before doing that,we observed couple of structural changes were not applied at the standby(ex:some tablespaces were not created in secondary where as they were there in primary).
How to apply these changes at the secondary as the standby is in mount state.(Can I open this database and create those tablespaces ?? or do you suggest any other way.
Thanks for your reply.

This points to a setup problem. Something missing, a parameter set wrong etc.
While your question is asking something different - How to correct, I would consider how to prevent. Unless you have a gap or logs not applied you have a deeper issue.
If you have a gap or logs not applied then correct it and check to see if the missing object are present.
The key parameters for Oracle 10 are :
FAL_SERVER=STANDBY
FAL_CLIENT=PRIMARY
STANDBY_FILE_MANAGEMENT=AUTO
DB_FILE_NAME_CONVERT='STANDBY','PRIMARY'
LOG_FILE_NAME_CONVERT='STANDBY','PRIMARY'
log_archive_dest_1='LOCATION=/u01/app/oracle/oradata/PRIMARY/archive VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARY'
log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
LOG_ARCHIVE_MAX_PROCESSES=30
Check them on both sides for issues.
If your standby is really trashed consider using RMAN to duplicate it. You might end up saving time. I have Oracle 11 short notes on this but it will work on Oracle 10 too.
http://www.visi.com/~mseberg/duprman.html
Otherwise use statements like this to resolve you gap.
ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/oradata/STANDBY/archive/PRIMARY_1_20_716110538.arc';
ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/oradata/STANDBY/archive/PRIMARY_1_21_716110538.arc';See Section 5.8 Managing Archive Gaps of oracle document B14239-05
Best Regards
mseberg
CKPT is correct, sorry I missed the Welcome to OTN!
Edited by: mseberg on Jul 5, 2011 10:34 AM

How to Create Manual Standby for a Oracle 11g RAC with ASM to Single Instan

Hi All,
I have a task to configure a Single Instance Standby Database with ASM for 2-node Primary RAC+ASM database.
Version using : 11.1.0.6 Oracle 11g --- *" STANDARD EDITION "* Please note datagaurd will not be supported in standard edition.
Primary database - 2 -Node RAC using ASM storage (All datafiles, redologs, controfile and archive logs)
Need to setup a single instance standby database manually and than using scripts to transfer the archive logs from primary server to standby server to do recovery time to time.
Please let me know if there are any configuration document(s) which can help me to set the manual standby? or need your kind help to give your valuable ideas how to go in above situation.
Thanks in advance

Niall Litchfield wrote:
El DBA wrote:
Well if the archive logs are stored in ASM on the primary nodes, you almost definitely want to be using RMAN to access them. Then to transfer between primary and standby there are many options, this is essentially the step that Data Guard takes care of - so if you (and I) are running Standard Edition, this is the part to "worry" about.
I'm not really sure what you mean by this:
As in standard edition the archive destination will be on ASMI don't think the Edition of Oracle (Standard or Enterprise) dictates where and how you store your archive logs, but it's possible I've misunderstood what you mean...SE dictates that database storage for RAC will be ASM, including archive log files. Anything else is not officially supported. I haven't tested but it may be that you can use LOG_ARCHIVE_DUPLEX_DEST to specify a local filesystem for archive log files as well.
If that doesn't work you'll have to script rman "backup as copy" jobs regularly and then transport the results of that.
Niall Litchfield
http://www.orawin.info/
By the way, it seems Robert has been pretty helpful, it's polite to give him some points dude. And since this is your thread, not mine, give him a "helpful" from me too :p
El DBA
Incidentally if you are forced down the RMAN backup as copy route then this will likely throw your current backup retention strategy somewhat, you'll need to think carefully about when an archivelog can be deleted following backup, how many times it might be backed up and so on. I do understand, and have argued for, the use of SE RAC. I also understand and have argued for and implemented manually managed standby a number of times. However by the time your primary database is a RAC instance and you need a standby for DR etc then you really have to look very seriously at whether Standard Edition is still the right investment or not. You will be spending a lot of DBA time managing and troubleshooting this, and you will find that it is less reliable than the off the shelf solution. I suspect that you are very close to the point where an EE installation becomes a worthwhile investment here.
Niall Litchfield
http://www.orawin.info/

Datafile issues in manual standby database

Hi all,
oracle - 10gR2
OS - RHEL 2.6
We have primary and standby database setup using manual methods('rsync') to send archive logs from primary to standby database and they are applied there. Today I have created a new datafile in primary and seen that the same is not replicated in standby( i was not aware of the functionality of this kind of setup) later I have seen that "standby_file_management parameter is set to MANUAL".
I have seen the following message in standby alert log(not disabled the archive log application script in satndby),
"Media Recovery Log /u01/app/oracle/oradata/bmprod/archivelog/1_1761_703415336.arc
File #6 added to control file as 'UNNAMED00006' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail"
Later I have copied the required file from primary to standby database(now I have disabled the archive log application script in standby), and renamed the datafile 'UNNAMED00006' to 'desired one' and restarted the archive log application script. I have seen the following messages,
"ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 6 needs more recovery to be consistent
ORA-01110: data file 6: '/u02/app/oracle/oradata/bmprod/BMTEST.dbf'"
Now I am unable to figure out what I should do to come out of this situation. Atleast tell me this condition is not worse than I thought(I think that the standby database should be recreated).
Any help is appreciated.......
regards
Edited by: techfeud on Jan 18, 2010 11:26 PM

Hi,
when you set the standby_file_management parameter as mannual then , if you create any datafile or adding it to the tablespace then you should mannaully run the command on the standby side , if its auto then auto matically it will create the file over in the respective locationa and with the name what you have used to create the datafile on the primary side,
as the parameter value is mannual ypu need to create the datafile over the standby side and then performt the recovery,
Farhan.

Manual Standby Database (10.2.0.2.0) on Windows 2003 R2

Hi,
We are setting up a standby database on a remote site for a simple oracle DB. As we already have a standby/master for another Oracle DB (from SAP) we want to stay as close as possible as what already exist.
For the SAP Oracle standby, we are copying manualy all archive to the stand by and apply them with brarchive. All is working fine.
For the new standby, we can not use brarchive as there is no SAP install on the standby but we stay with the "manual" copy of the archive from the master to the standby (using robocpy). It means all archive are on the standby (K:\oracle\oradata\archive).
The creation of the standby DB seems to be OK as i can open it, but i can't manage to apply de redo logs.
I'm quite new to oracle, so it's maybe a very basic issue, but i've already spent 3 days on it...
To start the DB, we lauch a bat script :
sqlplus /nolog @c:\backup\standby.sql
pause
the standby.sql:
connect /@TECDB01 as sysdba
startup nomount;
alter database mount standby database;
exit;
Then i connect to sqlplus and enter:
alter database recover managed standby database;
In another sqlplus session :
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
wich give me :
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MR(fg) WAIT_FOR_GAP 1 45400 0 0
RFS IDLE 0 0 0 0
The sequence 45400 seems to be ok regarding the time of the backup restored on the standby.
The archive is well on the server, but it won't apply it.
The Alert_TECDB01.log :
Fri Oct 29 11:03:43 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =121
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes                = 999
sga_target               = 7214202880
control_files            = I:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, J:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, K:\ORACLE\ORADATA\CNTRL\STANDBY.CTL
db_block_size            = 8192
compatible               = 10.2.0.2.0
log_archive_dest_1       = LOCATION=K:\oracle\oradata\archive
log_archive_dest_2       = SERVICE=TECDB01
log_archive_dest_state_1 = enable
log_archive_dest_state_2 = enable
standby_archive_dest     = K:\oracle\oradata\archive
archive_lag_target       = 1800
db_file_multiblock_read_count= 16
undo_management          = AUTO
undo_tablespace          = RBS
undo_retention           = 10800
recyclebin               = OFF
remote_login_passwordfile= EXCLUSIVE
db_domain                = WORLD
dispatchers              = (ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)
shared_servers           = 100
local_listener           = (ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))
session_cached_cursors   = 300
utl_file_dir             = \\srvuniway.vrithoff.srwt.tec-wl.be\hotspots
job_queue_processes      = 10
audit_file_dest          = I:\ORACLE\ADMIN\TECDB01\ADUMP
background_dump_dest     = I:\ORACLE\ADMIN\TECDB01\BDUMP
user_dump_dest           = I:\ORACLE\ADMIN\TECDB01\UDUMP
core_dump_dest           = I:\ORACLE\ADMIN\TECDB01\CDUMP
db_name                  = TECDB01
open_cursors             = 3000
pga_aggregate_target     = 1086324736
PMON started with pid=2, OS id=4012
PSP0 started with pid=3, OS id=3856
MMAN started with pid=4, OS id=3580
DBW0 started with pid=5, OS id=1084
LGWR started with pid=6, OS id=576
CKPT started with pid=7, OS id=3516
SMON started with pid=8, OS id=508
RECO started with pid=9, OS id=3068
CJQ0 started with pid=10, OS id=2448
MMON started with pid=11, OS id=2840
MMNL started with pid=12, OS id=3024
Fri Oct 29 11:03:44 2010
starting up 4 dispatcher(s) for network address '(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))'...
starting up 100 shared server(s) ...
Fri Oct 29 11:03:45 2010
alter database mount standby database
Fri Oct 29 11:03:51 2010
Setting recovery target incarnation to 2
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=118, OS id=3584
Fri Oct 29 11:03:51 2010
ARC0: Archival started
ARC1 started with pid=119, OS id=3688
Fri Oct 29 11:03:51 2010
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Fri Oct 29 11:03:51 2010
ARC0: Becoming the 'no FAL' ARCH
Fri Oct 29 11:03:51 2010
Successful mount of redo thread 1, with mount id 3987142355
Fri Oct 29 11:03:51 2010
ARC0: Becoming the 'no SRL' ARCH
Fri Oct 29 11:03:51 2010
ARC1: Becoming the heartbeat ARCH
Fri Oct 29 11:03:51 2010
Physical Standby Database mounted.
Completed: alter database mount standby database
Fri Oct 29 11:04:06 2010
alter database recover managed standby database
Fri Oct 29 11:04:06 2010
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 7 processes
Media Recovery Waiting for thread 1 sequence 45400
Fetching gap sequence in thread 1, gap sequence 45400-45499
+FAL[client]: Error fetching gap sequence, no FAL server specified+
Fri Oct 29 11:04:37 2010
+FAL[client]: Failed to request gap sequence+
GAP - thread 1 sequence 45400-45499
DBID 3776455083 branch 670241032
+FAL[client]: All defined FAL servers have been attempted.+
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Fri Oct 29 11:04:51 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3452
RFS[1]: Identified database type as 'physical standby'
Fri Oct 29 11:04:51 2010
RFS LogMiner: Client disabled from further notification
The tecdb01_arc1_3688.trc :
Dump file i:\oracle\admin\tecdb01\bdump\tecdb01_arc1_3688.trc
Fri Oct 29 11:03:51 2010
ORACLE V10.2.0.2.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Windows NT Version V5.2 Service Pack 2
CPU                 : 8 - type 8664, 2 Physical Cores
Process Affinity    : 0x0000000000000000
Memory (Avail/Total): Ph:7467M/9215M, PhPgF:2454M/10796M+
Instance name: tecdb01
Redo thread mounted by this instance: 1
Oracle process number: 119
Windows thread id: 3688, image: ORACLE.EXE (ARC1)
*** SERVICE NAME:() 2010-10-29 11:03:51.177
*** SESSION ID:(1088.1) 2010-10-29 11:03:51.177
kcrrwkx: nothing to do (start)
*** 2010-10-29 11:04:51.129
Redo shipping client performing standby login
*** 2010-10-29 11:04:51.176 64529 kcrr.c
Logged on to standby successfully
Client logon and security negotiation successful!
kcrrwkx: nothing to do (end)
*** 2010-10-29 11:05:51.285
kcrrwkx: nothing to do (end)
*** 2010-10-29 11:06:51.300
kcrrwkx: nothing to do (end)
The initTECDB01.ora :
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# Archive
archive_lag_target=1800
log_archive_dest_1='LOCATION=K:\oracle\oradata\archive'
# Cache and I/O
db_block_size=8192
db_file_multiblock_read_count=16
# Cursors and Library Cache
open_cursors=3000
session_cached_cursors=300
# Database Identification
db_domain=WORLD
db_name=TECDB01
# Diagnostics and Statistics
background_dump_dest=I:\oracle\admin\TECDB01\bdump
core_dump_dest=I:\oracle\admin\TECDB01\cdump
user_dump_dest=I:\oracle\admin\TECDB01\udump
# File Configuration
control_files=("I:\oracle\oradata\cntrl\standby.ctl", "J:\oracle\oradata\cntrl\standby.ctl", "K:\oracle\oradata\cntrl\standby.ctl")
# Job Queues
job_queue_processes=10
# Miscellaneous
compatible=10.2.0.2.0
recyclebin=OFF
# Processes and Sessions
processes=999
# SGA Memory
sga_target=6880M
# Pools
#java_pool_size=150M
# Security and Auditing
audit_file_dest=I:\oracle\admin\TECDB01\adump
remote_login_passwordfile=EXCLUSIVE
# Shared Server
shared_servers=100
dispatchers="(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)"
#dispatchers="(PROTOCOL=TCP) (SERVICE=TECDB01XDB)"
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=1036M
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_retention=10800
undo_tablespace=RBS
local_listener="(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))"
# NIDA - 28.10.2010 - redo apply
log_archive_dest_state_1=enable
log_archive_dest_2 = 'SERVICE=TECDB01'
log_archive_dest_state_2=enable
#standby_file_management=auto
standby_archive_dest=K:\oracle\oradata\archive
And the TNSNAMES.ora :
# tnsnames.ora Network Configuration File: C:\oracle\102\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
#this is the standby
TECDB01.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.92)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = TECDB01)
# This file is written by Oracle Services For MSCS
# on Sat Nov 08 10:44:27 2008
#this is the master
PRIMARY.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.246)(PORT = 1521))
(CONNECT_DATA =
(SID = TECDB01)
EXTPROC_CONNECTION_DATA.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = TECDB01))
(CONNECT_DATA =
(SERVICE_NAME = TECDB01)
Hope you have all information to bring me in the right way.
Regards,
Nicolas

Hi,
The recover automatic is working fine, but I still have problems with the recover managed
Here is the Alert log :(the 46626 was there at 11:30)
Mon Nov 15 11:31:13 2010
alter database recover managed standby database using current logfile
Managed Standby Recovery starting Real Time Apply
parallel recovery started with 7 processes
Media Recovery Waiting for thread 1 sequence 46626
Mon Nov 15 16:36:01 2010
alter database recover managed standby database cancel
Mon Nov 15 16:36:05 2010
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Mon Nov 15 16:36:06 2010
Media Recovery user canceled with status 16037
ORA-16043 signalled during: alter database recover managed standby database using current logfile...
Mon Nov 15 16:36:07 2010
Completed: alter database recover managed standby database cancel
Mon Nov 15 16:36:37 2010
ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
Mon Nov 15 16:36:37 2010
Media Recovery Start
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 7 processes
Mon Nov 15 16:36:39 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46626_0670241032.001
Mon Nov 15 16:36:45 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46627_0670241032.001
Mon Nov 15 16:37:11 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46628_0670241032.001
Mon Nov 15 16:37:30 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46629_0670241032.001
Mon Nov 15 16:37:48 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46630_0670241032.001
Mon Nov 15 16:37:59 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46631_0670241032.001
Mon Nov 15 16:38:15 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46632_0670241032.001
Mon Nov 15 16:38:28 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46633_0670241032.001
Mon Nov 15 16:38:47 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46634_0670241032.001
Mon Nov 15 16:39:34 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46635_0670241032.001
Mon Nov 15 16:40:43 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46636_0670241032.001
Mon Nov 15 16:42:03 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46637_0670241032.001
Mon Nov 15 16:43:18 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46638_0670241032.001
Mon Nov 15 16:44:38 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46639_0670241032.001
Mon Nov 15 16:45:45 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46640_0670241032.001
Mon Nov 15 16:46:37 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46641_0670241032.001
Mon Nov 15 16:47:48 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46642_0670241032.001
Mon Nov 15 16:49:07 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46643_0670241032.001
Mon Nov 15 16:50:04 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46644_0670241032.001
Mon Nov 15 16:51:13 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46645_0670241032.001
Mon Nov 15 16:52:16 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46646_0670241032.001
Mon Nov 15 16:53:07 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46647_0670241032.001
Mon Nov 15 16:54:28 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46648_0670241032.001
Mon Nov 15 16:55:47 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46649_0670241032.001
Mon Nov 15 16:56:35 2010
Incomplete Recovery applied until change 4037420604
Completed: ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
I don't catch why the system wait for a sequence that is available...
Regards,
Nico

How to remove logical standby database configuration cleanly

Hello,
We are on RHL with 11.2.0.3 DB version. Due to various unknown reasons we would like to recreate logical standby database and for that purpose I would like to cleanly remove/uninstall/drop LOGICAL STANDBY DATABASE from the DATA GUARD configuration we have.
The DG setup already has 1 PHYSICAL STANDBY DATABASE which is working fine. PRIM,PHYSICAL, and LOGICAL all are on different HOSTS. Could you please guide or suggest us exact MOS Doc id regarding this? I have found one MOS Doc id which is close enough but its steps include removing dg configuration completely which I don't want. Only Logical Standby database needs to be remove cleanly so that it can be installed again properly.
We are using GRID CONTROL and DATA GUARD BROKER.
Bundle of thanks in advance.
Best Regards

Hello;
I would review this Oracle note:
How to remove a Data Guard Configuration from Primary Database (Doc ID 733794.1)
Best Regards
mseberg

How to shift Manual Standby Database to Primary Database

Similar Messages

Maybe you are looking for