Shutdown Logical Standby Server

How can I gracfully shutdown logical standby server and start it ? Please write the steps
Thanks

Hello,
$> sqlplus '/as sysdba'
$> shutdown immediate ;
or
$> shutdown;
$> startup force nomount
or
$> startup force nomount pfile='..../yourinitstandby.ora'
$> alter database mount standby database.Verify in alert.log file that standyby server started and mounted.
Regards

Similar Messages

Why FRA filling faster in logical standby server.

I have two standby servers one physical and one logical for my primary database. I have notice that on logical standby server the FRA is filling faster then physical standby server. Any one have some suggestions.
Thx

>
I have two standby servers one physical and one logical for my primary database. I have notice that on logical standby server the FRA is filling faster then physical standby server. Any one have some suggestions.
>
That is to be expected, because the logical standby not only creates archive logs on behalf of the transmission from the primary but also generates its own archivelogs on behalf of the filling (& archiving) of the local online logfiles. If you watch a logical standby applying, you may notice that the standby logs are getting archived and the online logs as well. That is significant for a logical standby and leads to (at least temporary) higher space consumption in the recovery area. Temporary, because the applied archive logs can get deleted (automatically, if you allow that).
Kind regards
Uwe
http://uhesse.wordpress.com

Logical standby server stopped applying changes

Hi
I set up a logical standby database with database guard and it worked fine for some time. But recently I had to use it again and discovered that applying changes from primary database to secondary database just stopped working. I see in V$ARCHIVED_LOG one entry per day. If I restart the logical standby then the changes from primary server are also applied. But if I just make a change on primary server and even call 'alter system switch logfile' then I see an entry in V$ARCHIVED_LOG on primary server but not on standby server (BTW in general there are much more entries in this view on the primary server). I checked pairs of log files indicated by the parameter *.log_file_name_convert in standby server's spfile: their last changed date is always the same.
I will paste spfile of my standby server (dh5). Primary server name is dh2.
dh2.__db_cache_size=79691776
dh5.__db_cache_size=96468992
dh2.__java_pool_size=4194304
dh5.__java_pool_size=4194304
dh2.__large_pool_size=4194304
dh5.__large_pool_size=4194304
dh2.__shared_pool_size=71303168
dh5.__shared_pool_size=54525952
dh2.__streams_pool_size=0
dh5.__streams_pool_size=0
*.audit_file_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/adump'
*.background_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/bdump'
*.compatible='10.2.0.1.0'
*.control_files='/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5/control01.ctl'
*.core_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='dh2','dh5'
*.db_name='dh7'
*.db_recovery_file_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.db_unique_name='dh5'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=dh2XDB)'
*.fal_client='dh5'
*.fal_server='dh2'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(dh2,dh5)'
*.log_archive_dest_1='LOCATION=/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5_local
VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=dh5'
*.log_archive_dest_2='SERVICE=dh2 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=dh2'
*.log_archive_dest_3='LOCATION=/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5
VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLES)
DB_UNIQUE_NAME=dh5'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_dest_state_3='ENABLE'
*.log_archive_format='%t_%s_%r.arc'
*.log_archive_max_processes=30
*.log_file_name_convert='oradata/dh2/redo01.log','flash_recovery_area/DH5/onlinelog/o1_mf_4_5x0o5grc_.log','oradata/dh2/r
edo02.log','flash_recovery_area/DH5/onlinelog/o1_mf_5_5x0o61mw_.log','oradata/dh2/redo03.log','flash_recovery_area/DH5/on
linelog/o1_mf_6_5x0o63gj_.log'
*.nls_language='AMERICAN'
*.open_cursors=300
*.pga_aggregate_target=311427072
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.undo_management='AUTO'
*.undo_retention=3600
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/udump'
Thanks in advance for any help.
JM

Hi,
Nice to hear you issue got resolved.
It is good practice to keep monitoring the progress of SQL apply on the logical standby on a regular basis.
You can mark my response as helpful if it has helped you.
Regards
Anudeep

Oracle 10gR2 Data guard physical or logical standby server?

Hi
We are planing to implement an Oracle 10gR2 data guard standby server for DR purposes, I found out that there are two type of standby server which is logical and physical standby server. I want to know which one is preferable? in term of complexity of setup and maintenance?
regards

Well it depends on what you mean by maintenance. I found the physical standby to be very little trouble at all ; however the logical standby has restrictions on it that the physical standby does not. In essence the physical standby merely digest archive logs; where as the logical standby uses logminer like functionality to process sql statements much like Oracle streams.
Hope that helps,
-JR jr.

Do I need ASM for logical standby server?

I am using ASM in production, when I created physical standby for it, system asked me create ASM file system on it else it is not possible. My question is do I need ASM file system for logical standby too.?
Thanks

You can have the primary database on ASM and the standby on filesystem if you want.
You just need to set db_file_name_convert and standby_file_management. I have tested this will physical, but not logical standby.

Resynchronization in primary and logical standby db

Hi,
I have implemented logical standby successfully first time.for testing i had shutdown logical standby server for last 60 hours.
when i start standby db and execute command
"ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;"
but it is not synchronized data for last 3 days
Please help me
Vaibhav Dixit

i suppossed that you did : alter database open resetlog; right?
In first place, try to see any error in redo transport:
alter system switch logfile;
select status, error from v$archive_dest where dest_id = 2;
any error?
for more information, please check:
http://www.idevelopment.info/data/Oracle/DBA_tips/Data_Guard/DG_45.shtml

Logical Standby Problem

My environment is Primary database is 11.1.0.7 64bit on Windows 2003 Enterprise 64bit. Logical is on the same platform and oracle version but a different server. I created a physical standby first and it applied the logs quickly without any issues. I received no errors when I changed it over to a Logical standby database. The problem that is happening is as soon as I issue the command "alter database start logical standby apply;" the CPU usage goes to 100% and the SQL apply takes a long time to apply a log. When I was doing this on 10G I never ran into this, as soon as the log was received, it was applied within a couple of minutes. I don't think it could be a memory issue since there is plenty on the Logical standby server. I just can't figure out why the SQL apply is so slow and the CPU usage skyrockets. I went through all of the steps in the guide "Managing a Logical Standby Database" from Oracle and I don't see anything wrong. The only difference between the two databases is that on the Primary I have Large Page support enabled, I don't on the Logical. Any help would be greatly appreciated, I need to use this Logical to report off of.

Thanks for the responses. I have found what is causing the problem. I kept noticing that the statements it was slowing down on were the ones where data was being written to the SYS.AUD$ table in the System tablespace on the Logical Standby database. A quick count of the records showed that I had almost 6 million records in that table. After I decided to truncate SYS.AUD$ on the Logical, the archive logs started to apply normally. I wonder why the Logical has a problem with this table and the Primary doesn't. I didn't even know auditing was turned on on the Primary database, it must be enabled by default. Now I know why my System table space has grown from 1gb to 2gb since November.
Now that I fixed it for now, I am unsure what to do to keep this from happening. Can I turn off Auditing on the Logical and keep it on for the Primary? Would this stop data from being written to the SYS.AUD$ table on the Logical? It doesn't appear that there is any kind of cleanup on this table that is offered by Oracle, I guess I can just clean out this table occasionally but that is just another thing to add to the list of maintenance tasks. I notice that you can also write this audit data to a file on the OS. Has anyone here done that?

Configuration of the Physical & Logical standby servers on the same machine

I've encoutered a problem to connect to one of the standby servers .
I created a DataGuard in 10.2. Primary on 1 machine, 1 physical standby and 1 logical standby on another machine (both phy and logical in same machine)
I first created a primary then a physical standby. I've got no problem at all.
But when I created a logical standby server on the same machine with the physical then I could not connect to both phy and logical . I can connect to either one of them.
According to DataGuard setup, the db_name must be the same in primary and all standby servers. This is fine when each of the primary or the standby installed in a separate machine.
The db_name of the physical = rolex
The db_name of the logical = rolex
When we have more than one instance in the same machine, we just set the ORACLE_SID = db_name ( or instance), then connect to it.
If I connect to the physical, then I try to connect to the logical, it goes to the physical or vice versus.
Does anyone have the solution ?
QN

DB_UNIQUE_NAME parameter will be the seperator.
give DB_UNIQUE_NAME parameters different names and set ORACLE_SID with DB_UNIQUE_NAME name you gave
DB_NAME is the primary instances database name DB_UNIQUE_NAME is given for standby instances database name

Archived log to standby server stopped

Hi,
I configured dataguard standby server few weeks ago,
I set log_archive_dest_2='SERVICE=JHRD0107_OFS1 OPTIONAL'
and log_archive_dest_state=ENABLE in primary server,
and very go fine until yesterday, I shutdown my standby server and set the log_archive_dest_state=DEFER,
when I tried to startup again the standby server, and set log_archive_dest_state=ENABLE again,
the archive stop sending the archived log to log_archive_dest_2.
No error was found in alert log of primary and standby server.
It seem that the primary server don't know there is another archive destination..
The database version is 10g 10.2.0.4
Anyone what could be the cause of this?
Thanks

Hi, Below is the parameter related to archive in my primary server
SQL> alter system set log_archive_dest_state_2=enable;
System altered.
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string LOCATION=I:\OFSDB\OFS1\archive
MANDATORY REOPEN=300
log_archive_dest_10 string LOCATION=USE_DB_RECOVERY_FILE_
DEST OPTIONAL REOPEN=300
log_archive_dest_2 string SERVICE=JHRD0107_OFS1 OPTIONAL
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
NAME TYPE VALUE
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
NAME TYPE VALUE
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string ARC%S_%R.%T
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
NAME TYPE VALUE
standby_archive_dest string %ORACLE_HOME%\RDBMS
Thanks for your response.
Vincent

Stop/start logical standby db

Version 10203 on AIX
Have to stop/start logical standby db, new to data guard, Please confirm these are the steps to do that
on primary db
SQL > alter system switch logfile ;
SQL > alter system archive log current ; ( to make sure current transactions come thru)
check tail of alert log of standby to make sure these redologs shipped & mined
standby db
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY; (stop SQL Apply)
SQL> shutdown immediate;
Lsnrctl stop listener_corp_remrpt-haprimary db
SQL > shutdown immediate ;
Lsnrctl stop listener_corp_remprd-ha
Dont shutdown abort for any case, if both dbs are going down, first stop SQL apply on standby, take primary down and then take standby down)
Startup
primary
SQL>startup;
Lsnrctl start listener_corp_remprd-ha
Standby
SQL > startup
SQL > alter database start logical standby apply immediate ;
Lsnrctl start listener_corp_remrpt-ha

Hi
As you posted ,you are using Real Time Sql apply,So,it is LGWR who transfer changes to standby site.It is very safe to follow these steps for new user.
1.Stop logical standby apply(Standby Database).
2.Shutdown Primary Database.
3.Shutdown logical standby Database.
At startup
1.Start Logical Standby Database.
2.Start Primary Database.
3.Start logical standby apply.
At the case when primary database is taking long time to shutdown processed ,You can also use
shutdown abort,but before doing abort be sure you have stop logical standby apply.When your primary database started,it automatically perform instance recovery.Primary site have to resolve gap in this case.
At the case when you must have to perform shutdown abort at primary database,you can do it.By doing it you will not loose anything.Primary database has to resolve gap and it will take time to be consistent with primary site.
Tinku

Oracle Logical Standby as data source

Post Author: garyreit
CA Forum: Data Connectivity and SQL
Has anyone succesfully used an Oracle Logical Standby server as a
data source? When I try I get "table not found" for all the
tables in Crystal reports, but the report runs fine. When I run
the same report in BOE, The report fails with the error:Error in File D:\Program Files\Business Objects\BusinessObjects
Enterprise
11.5\Data\procSched\biapp1.reportjobserver\~tmp1c4c50845f07b62.rpt:
Error in formula <Record Selection>.
'{PS_CANC_TERM_CLASS.BATCH_ID} = {?Batch ID} and
This field name is not known.
Details: errorKind We are using BOE XI R2 sp2 and Oracle 10g with an ODBC using the Oracle connector.
Any Ideas?Thanks

Post Author: udasgupta
CA Forum: Data Connectivity and SQL
I am getting a similar problem. Did you get a solution? If so, could you please let me know.
Thanks in advance,
Uma

Logical standby issue after adding a new user at production db server

Hello Experts,
I am facing a issue related to logical standby db server where after adding a new user at production db server logical standby has stopped sql apply. Can anybody give some idea to find out the root cause and give some tips to resolve the issue.
tried below .....
SELECT EVENT_TIME, STATUS, EVENT FROM DBA_LOGSTDBY_EVENTS
ORDER BY EVENT_TIMESTAMP, COMMIT_SCN, CURRENT_SCN;
got error
ORA-16227: DDL skipped due to missing object
ORA-01403: no data found
ORA-00942: table or view does not exist
OS : RHEL 4 (IBM P5)
DB : Oracle 10g (10.2.0.1)
Achyot

Please let me know if can skip the DDL at which it is failing.
ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Use EXECUTE DBMS_LOGSTDBY.SKIP
ALTER DATABASE START LOGICAL STANDBY APPLY;
Thanks,
Renu

How do shutdown the weblogic server from the command line prompt using web logic 8.1

I%u2019m currently using weblogic 6.1, but I will upgrade to weblogic 8.1. In weblogic 6.1, the following statements will shutdown the weblogic instance from the command line:
java weblogic.Admin -url t3://hostname:port -username system -password abc SHUTDOWN
How do I shutdown the weblogic server from the command line prompt using web logic 8.1.
Any help will be greatly appreciated.
Maria

Maria <[email protected]> wrote:
How do I shutdown the weblogic server from the
command line prompt using weblogic 8.1?Greetings Maria! Use this document, located here:
http://edocs.bea.com/wls/docs81/admin_ref/cli.html#1131733
Hope this helps...
Brian J. Mitchell
Systems Administrator, TRX
email: [email protected]
office: +1 404 327 7238
mobile: +1 678 283 6530

Logical standby in noarchive mode

Hello,
does anybody know if it is possible to run a logical standby (10gR2) in noarchivelog mode?
For my understanding it should be possible, why not... But I can't find a piece of documentation which prove this.
Thanks in advance,
Boris...

I also was curious if setting up a Logical Standby in noarchivelog mode was possible. It looks like it is...
We use this simply as a reporting copy of our data. Our analysts do not change any of this data. They just need it to be fairly current (~3 days). At this point, there isn't any need to generate archivelogs so we want to disable the feature to minimize our maintenance and our storage requirements.
STANDBY DB:
SQL> select log_mode, open_mode from v$database;
LOG_MODE     OPEN_MODE
ARCHIVELOG   READ WRITE
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Database mounted.
SQL> alter database noarchivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Database altered.Then I created an object on the production server:
SQL> create table testuser.noarchivelog_testing as select * from dba_objects;
Table created.
SQL> alter system switch logfile;
System altered.
Mon Jun 22 11:13:26 2009
Beginning log switch checkpoint up to RBA [0xe6.2.10], SCN: 1031235046
Mon Jun 22 11:13:26 2009Now I see it on the standby:
Mon Jun 22 11:13:43 2009
RFS LogMiner: RFS id [25920] assigned as thread [1] PING handler
RFS[1]: Archived Log: '/oracle/LH1/oraarch/LH1arch_1_229_680639127.arc'
Mon Jun 22 11:13:46 2009
RFS LogMiner: Registered logfile [/oracle/LH1/oraarch/LH1arch_1_229_680639127.arc] to LogMiner session id [1]
Mon Jun 22 11:13:48 2009
LOGSTDBY status: ORA-16204: DDL successfully applied
Mon Jun 22 11:13:51 2009
LOGMINER: End mining logfile: /oracle/LH1/oraarch/LH1arch_1_229_680639127.arc
SQL> select count(*) from testuser.noarchivelog_testing;
COUNT(*)
     24444

Best practice on using Flashback and Logical Standby

Hello,
I'm testing a fail-back scenario where I first need to activate a logical standby, then do some dummy transactions before I flashback this db and resme the redo apply. Here is what the steps look like:
1)     Ensure logical standby is in-sync with primary
2)     Enable flashback on standby
3)     Create a flashback guaranteed restore point
4)     Defer log shipping from primary
5)     Activate the logical standby so it’s fully open to read-write
6)     Dummy activities against the standby (which is now fully open)
7)     Flashback the database to the guaranteed checkpoint
8)     Resume log shipping on primary
9)     Resume redo apply on secondary
In the end, i can see the log shipping is happening but the logical standby does not apply any of these..and there is no error in the alert log on Standby side. But the following query could explains why the standby is idle:
SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
TYPE HIGH_SCN STATUS
COORDINATOR ORA-16240: Waiting for log file (thread# 2, sequence# 0)
ORA-16240: Waiting for log file (thread# string, sequence# string)
Cause: Process is idle waiting for additional log file to be available.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
I dont understand why it's looking for sequence #0 after the flashback.
Thanks for the help.

Hello;
I hesitate to answer your question because you are not doing a good job of keeping the forum clean :
Total Questions: 13 (13 unresolved)
Please consider closing some of you old answered questions and rewarding those who helped you.
No action necessary.
Do you really have a thread 2? ( Redo thread number )
Quick check
select applied_scn,latest_scn from v$logstdby_progress;Use the DBA_LOGSTDBY_LOG View if you don't have a thread 2 then the sequence# is meaningless.
COLUMN DICT_BEGIN FORMAT A10;
SELECT FILE_NAME, SEQUENCE#, FIRST_CHANGE#, NEXT_CHANGE#,
TIMESTAMP, DICT_BEGIN, DICT_END, THREAD# AS THR# FROM DBA_LOGSTDBY_LOG
ORDER BY SEQUENCE#;Logical Standby questions are difficult, not a lot of them out there I'm thinking.
Check
http://docs.oracle.com/cd/E14072_01/server.112/e10700/manage_ls.htm
"Waiting On Gap State" ( However I still believe you don't have a 2nd thread# )
OR
http://psilt.wordpress.com/2009/04/29/simple-logical-standby/
Best Regards
mseberg
Edited by: mseberg on Apr 26, 2012 5:13 PM

Shutdown Logical Standby Server

Similar Messages

Maybe you are looking for