Logical standby Slow after starting auditing

Hi:
I have logical standby, which was keeping with the primary database, then we started auditing on the primary database(Database auditing.) , After starting auditing my Logical standby not keeping with primary, after doing reasearch we found out that there are so many sql statement from sys schema on AUD$ table, and they are doing full tablescan on it, which is of 3GB as off now. Also This table is own by sys and by default all sys objects should be excluded from logical standby apply. But this is not, when I tryed to skip it by my self, then apply process gives ora-600 and stops.
I think it is a bug or what ???
Any help on this will be appriciated.
Regards
Bhushan

Hi Guys:
After taking my time we decided to truncate the sys.AUD$ on the LOGICAL STANDBY and that solved our problem.Now LS is catching up fast as I can see the progree is verry fast.
Still if anybody from "ORACLE CORP" is reading this thread they should give us the reason why the sys.aud$ table is beging replicated on the LOGICAL STANDBY site. is this a BUG in oracle?
Regards
Bhushan

Similar Messages

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

Logic Pro slow after SSD and mountain lion update.

1 week ago i was mixing a project of 90 tracks, and every run really well, no "system overloads" at all.
Sometimes the 320gb 5400rpm HDD give away a message that it was running a little slow and had a hard time dealing with all the 90 tracks, but it still work'd well.
3 days ago i installed a new samsung 830 256GB SSD and updated from lion to mountain lion and wow!
Everything is really fast, except logic pro.
Im now running a project with only 35 audio tracks with EQ,compressor and 2 busses with reverb.
It should work fine, SSD with 2,3 dualcore i5 cpu and 8gb ram but no, i am only able to play a quarter of a secound before i get the anoying "system overload" message....
Does somebody know what could be wrong? Mixing is my job soo this is a real problem for me.
Thanks!

Are you getting sudden motion sensor related stops? It may be best to tern your SMS off, as there is no need for SMS in a drive with no moving parts.
They would look like the error here
https://discussions.apple.com/thread/3806031?start=0&tstart=0
if there is no mention of the SMS I wouldn't bother although, no harm would be done if you did anyway.
You disable SMS by doing the following:
Launch Terminal
Type the following at the command line: sudo pmset -a sms 0
Hit return and enter your password

Macbook Pro Gradually Slows After Start

Hey guys, I wanted to see if you could help me before I made the trip down to the apple store. I purchased the 2.4 GHz Intel Core 2 Duo with 2 GB of RAM. I have only recently noticed that after I am on my MBP for around 30 minutes it begins to slow down. Not to a crawl or anything I can just tell its slower then usual. I have the Istat pro widget and I have been monitoring my RAM usage the past week. I have noticed the first 10 to 15 minutes I run fine with a steady 1.56gb of free RAM. Keep in mind this is only with Firefox open.... I realize that Firefox is a memory hog so song tell me that a million times. Anyways after maybe 20 minutes of looking at news sites or whatever I'm searching that day I'll check my Istat and I only have 889mb left. How is this possible? should I not be able to open multiple windows and or programs all at once before my RAM is this low. Anyways even after I quit out of Firefox and no other program is on its stays at or around 889mb. What can be causing this? I dunno if you guys need some information on some of the programs I use but I use Photoshop CS3, Logic Express, and Final Cut Express Quite a lot. Most of the time I have Ichat running in the background, or Itunes. This RAM issue is just recent. Is there anything i can do to stop this?
Thanks for your time

iStat also reports Inactive ram yet you failed to report that value.

Creating logical standby database

Hi all,
10.2.0.1
Following this link
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm
Where do i need to issue these statements:
SQL> EXECUTE DBMS_LOGSTDBY.BUILD;
SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY db_name;
on physical standby or primary database.
I issued the first stament on primary and second on physical standby .
IN the alert log of standby,i have the following entries.
Wed Jan 20 15:34:28 2010
Converting standby mount to primary mount.
Wed Jan 20 15:34:28 2010
ACTIVATE STANDBY: Complete - Database mounted as primary (treasury)
*** DBNEWID utility started ***
DBID will be changed from 306589979 to new DBID of 330710340 for database
.........................I am trying to create a logical standby database after creating a physical standby database.
It seems standby changed to primary which was not desired.
Thanks

Not tried myself, but you might want to have a look at this URL.
It appears to suggest that you need to change names of datafiles as well as value db_name explcitly on standby.

Create function as "/ as sysdba" not shipped/applied to logical standby

As the subject states, I was creating a password verify function and profile that used the function as sys "/ as sysdba" .
The function was not created on the logical standby and thus the profile create statement failed. The function was not even listed in the standby's alertlog, although the create profile statement was.
I created the function manually on the standby by connecting / as sysdba and creating the function and then restarted logical standby apply. The standby then created the profile and continued without error.
Is this a bug?
Should the SYS 'create function' be shipped and applied or not?
When the function create statement was run on the primary as a non-sys user with DBA privs, it created ok and was shipped and appeared on logical standby ok.
Any ideas DataGuard Gurus?
(9.2.0.7 on Solaris 8)

I logged a Tar. Oracle says:
"Ideally any object created on sys schema should get skipped automatically. sys is consider as internal schema and objects created in sys schema should get
skipped"
"But because of the internal Bug.3576307 "LOGICAL STANDBY IS NOT SKIPPING DDL IT SHOULD." it is not skipping the DDL executed on sys schema. This bug
is fixed in 10.2.
You can issue following statement to enable the DDL skip on sys schema.
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
SQL> EXECUTE DBMS_LOGSTDBY.SKIP_ERROR(SCHEMA_DDL, SYS, null, null)
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY;
After which all DDL errors encountered on any object in the SYS schema would be ignored and processing continued. This can render the TEST schema objects unusable and, if necessary, you can later recreate the tables
using the INSTANTIATE_TABLE procedure."
Makes sense now.

Logical Standby - Log auto delete

Hello Everybody,
We are having a logical standby database which is working fine.. But the only concern is with deletion of archive logs that are applied..
I wanted to auto delete the archives that are applied.. Till yesterday all the archives that had applied was getting deleted automatically.. But now some how its not getting deleted..
Nothing has been changed since yesterday and i even checked alert log no error has been recorded but it just simply doesn't delete the archives..
For a try i restarted SQL apply, its applying the archive logs but it doesn't delete the archives that are applied..
Please any help or suggestions would be great.
Thanks

Thanks for your response..
As per the links you provided, these links are for archive deletion policy for primary and physical standby which we configure using RMAN..
But in Logical Standby case archive logs are automatically deleted after its applied...
So when ever we start sql apply following are the alert entries and it should automatically delete archives after it gets applied..
ALTER DATABASE START LOGICAL STANDBY APPLY
Thu Aug 20 16:34:14 2009
ALTER DATABASE START LOGICAL STANDBY APPLY (oracle)
Thu Aug 20 16:34:14 2009
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=23, OS id=4715
Thu Aug 20 16:34:15 2009
LOGSTDBY Parameter: LOG_AUTO_DELETE = TRUE
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY
Thu Aug 20 16:34:15 2009
LOGSTDBY status: ORA-16111: log mining and apply setting up
Thu Aug 20 16:34:15 2009
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: session# = 1, reader process P000 started with pid=24 OS id=4717
LOGMINER: session# = 1, builder process P001 started with pid=25 OS id=4719
LOGMINER: session# = 1, preparer process P002 started with pid=26 OS id=4721
Thu Aug 20 16:34:15 2009
LOGMINER: Begin mining logfile: /u01/app/oracle/archive/oracle/ARCH_ORACL_1309_1_692680471.arc
Thu Aug 20 16:34:15 2009
LOGMINER: Turning ON Log Auto Delete
Thu Aug 20 16:34:15 2009But in my case its not deleting archives what could be the reason..
Please any help would be great

Logical standby setup

Hi,
i'm configuring logical standby database,after giving alter database start logical standby apply; database was altered.
but select name, value
from v$logstdby_stats
where name = 'coordinator state' 2 3 ;
is not showing the status applying .how much will it take to come to applying status.
SQL> alter database start logical standby apply;
Database altered.
SQL> select name, value
from v$logstdby_stats
where name = 'coordinator state' 2 3 ;
NAME
VALUE
coordinator state
INITIALIZING
please help me

Oralce 10.1.0.3 on Linux
Wed Aug 8 21:52:21 2007
LOGSTDBY status: ORA-16111: log mining and apply setting up
Wed Aug 8 21:52:22 2007
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 10M, Checkpoint interval = 50M
LOGMINER: StopMiningThreshold = 3M
Wed Aug 8 23:30:26 2007
Private_strands 2 at log switch
Thread 1 advanced to log sequence 18
Current log# 2 seq# 18 mem# 0: /u01/u10/LOGSTDBY/redo02.log
Wed Aug 8 23:30:26 2007
ARC0: Evaluating archive log 1 thread 1 sequence 17
Wed Aug 8 23:30:26 2007
ARC0: Beginning to archive log 1 thread 1 sequence 17 (0.160249:0.163193) (LOGSTDBY)
ARCH: Connecting to console port...
Wed Aug 8 23:30:26 2007
ARC0: Creating local archive destination LOG_ARCHIVE_DEST_1: '/u01/u10/LOGSTDBY/arch/1_17_630100862.arc' (thread 1 sequence 17)
(LOGSTDBY)
.Thu Aug 9 17:38:14 2007
ARC0: Creating local archive destination LOG_ARCHIVE_DEST_1: '/u01/u10/LOGSTDBY/arch/1_33_630100862.arc' (thread 1 sequence 33)
(LOGSTDBY)
ARCH: Connecting to console port...
Thu Aug 9 17:38:14 2007
ARC0: Closing local archive destination LOG_ARCHIVE_DEST_1: '/u01/u10/LOGSTDBY/arch/1_33_630100862.arc'
(LOGSTDBY)
ARCH: Connecting to console port...
can i know wat are the datagurard logfiles
Please reply ...

Logical standby process

Hi,
how can configure the logical standby process to start automatically after i restart database?
thanks

What do you consider the "logical standby process"? The process that copies log files from the primary to the standby? Or the process that applies the log files to the standby database?
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Create logical standby from existing physical standby on 9i

I have physical standby database 9i running.
I want to try to convert the physical standby to logical standby. i follow the step by step in metalink document no. 748595.1
But I cannot do the 6th step:
6. Issue command to switch physical standby to logical standby after changing db_name in pfile to logical standby name. Shutdown the standby database if mounted and mount the database again. In this configuration, logical standby database name is LGSTDBY.
sql>alter database recover to logical standby LGSTDBY;
alter database recover to logical standby LGSTDBY;
Error at line 1:
ORA-00905: missing keyword
I have tried to create pfile from spfile on stanby and change the db_name to lgstdby.
I started nomount using pfile. I still cannot run the command.
I tried to mount the standby database but error occured:
ORA-01103: database name 'PRIMARY' in controlfile is not 'LGSTDBY'
The document in metalink is for 10.2.0.4
Is it possible to do it at 9i??
Thx for the help...

FEDORA 6 & ORACLE 10.2.0
alert_stb.log:
alter database start logical standby apply
Wed Jun 17 22:46:58 2009
ALTER DATABASE START LOGICAL STANDBY APPLY (stb)
Wed Jun 17 22:46:58 2009
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=22, OS id=4156
Wed Jun 17 22:46:59 2009
Completed: alter database start logical standby apply
Wed Jun 17 22:47:01 2009
LOGSTDBY status: ORA-16111: log mining and apply setting up
Wed Jun 17 22:47:01 2009
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: session# = 1, reader process P000 started with pid=23 OS id=4158
LOGMINER: session# = 1, builder process P001 started with pid=24 OS id=4160
LOGMINER: session# = 1, preparer process P002 started with pid=25 OS id=4162
Wed Jun 17 22:47:02 2009
LOGMINER: Begin mining logfile: /u01/app/oracle/flash_recovery_area/STB/archivelog_3/1_3_689731882.arc
Wed Jun 17 22:47:02 2009
LOGMINER: Turning ON Log Auto Delete
Wed Jun 17 22:47:02 2009
LOGMINER: End mining logfile: /u01/app/oracle/flash_recovery_area/STB/archivelog_3/1_3_689731882.arc
LOGSTDBY Analyzer process P003 started with pid=26 OS id=4164
LOGSTDBY Apply process P008 started with pid=31 OS id=4174
LOGSTDBY Apply process P007 started with pid=30 OS id=4172
LOGSTDBY Apply process P004 started with pid=27 OS id=4166
LOGSTDBY Apply process P006 started with pid=29 OS id=4170
LOGSTDBY Apply process P005 started with pid=28 OS id=4168

Large import on dataguard (logical standby) 11.2

The action I'll like to perform is to do a large import on the production enviroment without that this import will be applied on the logical-standby environment (because its to large for the standby envoriment to keep it up) and after that I will do this same import on the logical standby.
What the most common way to do this large import on logical standby enviroment after this is performed on the produnction ?
something like ;
alter session disable guard;
do the import
alter session enable guard;
alter database start logical standby apply skip failed transaction;
thanks in adv

if the table you are importing will have changes made to it AFTER the import and you want those changes replicated to the logical standby then you have to actually re-sync the table FROM primary.
Step 1. Skip the table DML on logical
EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', schema_name => 'schema', object_name =>'table_name');
Step 2. Import the table into primary
Step 3. Stop Logical Standby apply
alter database recover managed standby database cancel;
Step 4. Get the restart_scn on Logical Standby to use for the flashback scn with exp_dp
SELECT RESTART_SCN FROM V$LOGSTDBY_PROGRESS;
Step 5. On Primary export the table using the restart_scn from logical
expdp DIRECTORY=DP_DIR DUMPFILE=sync_table.dmp LOGFILE=sync_table.log tables=schema.table_name flashback_scn=6146375299983
Step 6. On Logical import the table
impdp DIRECTORY=DP_DIR dumpfile=sync_table.dmp TABLE_EXISTS_ACTION=REPLACE
Step 7. Unskip the table and start the apply on logical standby
EXECUTE DBMS_LOGSTDBY.UNSKIP(stmt => 'DML', schema_name => 'schema', object_name =>'table_name');
alter database start logical standby apply immediate;
Now the tables should both be synced up and any new changes made to the table on primary will replicate correctly to logical.
Note that oracle must maintain a read consistent copy of the table as of the SCN you specified, depending on how long it takes to export you may run into rollback segment issues. I'd plan on doing this during the least busy time on your db and increase undo to avoid ORA-01555

Logical Standby Scenario..!!

Hello,
We are having dataguard setup with Primary, Physical standby and Logical Standby databases located on three different machines..
Oracle Version : 10.2.0.1
OS : RHEL 4 on (x86 32-Bit)
Following are our initialization parameters for all the three instances..
Primary Database Parameters--_
*.db_unique_name='betapri'
*.fal_client='BETAPRI'
*.fal_server='BETAPHYSTDBY'
*.instance_name='oracle'
*.log_archive_config='DG_CONFIG=(betapri,betaphystdby,betalogstdby)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/archive/oracle VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=betapri MANDATORY'
*.log_archive_dest_2='SERVICE=BETAPHYSTDBY LGWR VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=betaphystdby'
*.log_archive_dest_3='SERVICE=BETALOGSTDBY LGWR SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=betalogstdby'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_dest_state_3='ENABLE'
*.standby_archive_dest='/u01/app/oracle/archive/oracle'
*.standby_file_management='AUTO'
*.remote_login_passwordfile='EXCLUSIVE'
Physical standby Database Parameters--_
*.db_unique_name='betaphystdby'
*.fal_client='BETAPHYSTDBY'
*.fal_server='BETAPRI'
*.instance_name='oracle'
*.log_archive_config='DG_CONFIG=(betapri,betaphystdby,betalogstdby)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/archive/oracle VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=betaphystdby'
*.log_archive_dest_2='SERVICE=BETAPRI LGWR VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=betapri'
*.log_archive_dest_3='SERVICE=BETALOGSTDBY VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=betalogstdby'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_dest_state_3='ENABLE'
*.standby_archive_dest='/u01/app/oracle/archive/oracle'
*.standby_file_management='AUTO'
*.remote_login_passwordfile='EXCLUSIVE'*Logical Standby Database Parameters *_
*.db_unique_name='betalogstdby'
*.instance_name='oracle'
*.log_archive_config='DG_CONFIG=(betapri,betaphystdby,betalogstdby)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/archive/betalogstdby VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=betalogstdby'
*.log_archive_dest_2='LOCATION=/u01/app/oracle/archive/oracle VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=betalogstdby'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.standby_archive_dest='/u01/app/oracle/archive/oracle'
*.standby_file_management='AUTO'
*.remote_login_passwordfile='EXCLUSIVE'Whole data guard setup is working properly as per the configuration.. But just for testing purpose i did FAILOVER_ and made our physical standby as new primary database and using Flashback i made my old primary as new physical standby and haven't made any changes to logical standby database since as per my init parameters i guess logical standby should remain in sync and keep applying the logs..
But performing this scenario logical standby seems to be messed up.. My new primay database does generate archives to logical standby but logical standby logmnr doesn't apply the changes to the database.. So once i issue "ALTER DATABASE START LOGICAL STANDBY APPLY" following message gets displayed in alert log *"Fatal Error: LogMiner processed beyond new branch scn."*
Tue Sep 29 18:55:14 2009
alter database start logical standby apply
Tue Sep 29 18:55:14 2009
ALTER DATABASE START LOGICAL STANDBY APPLY (oracle)
Tue Sep 29 18:55:14 2009
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=16, OS id=18308
LOGSTDBY status: ORA-16111: log mining and apply setting up
Tue Sep 29 18:55:14 2009
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
Tue Sep 29 18:55:14 2009
Fatal Error: LogMiner processed beyond new branch scn.
LOGSTDBY status: ORA-01346: LogMiner processed redo beyond specified reset log scn
Tue Sep 29 18:55:14 2009
Errors in file /u01/app/oracle/admin/oracle/bdump/oracle_lsp0_18308.trc:
ORA-01346: LogMiner processed redo beyond specified reset log scn
LOGSTDBY status: ORA-16222: automatic Logical Standby retry of last action
LOGSTDBY status: ORA-16111: log mining and apply setting up
Tue Sep 29 18:55:14 2009
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
Tue Sep 29 18:55:14 2009
Fatal Error: LogMiner processed beyond new branch scn.
LOGSTDBY status: ORA-01346: LogMiner processed redo beyond specified reset log scn
Tue Sep 29 18:55:14 2009
Errors in file /u01/app/oracle/admin/oracle/bdump/oracle_lsp0_18308.trc:
ORA-01346: LogMiner processed redo beyond specified reset log scn
Tue Sep 29 18:55:14 2009
ORA-16210 signalled during: alter database start logical standby apply... Note : I am having flashback enabled only on one database which was my old primary..
Please any comments, help or suggestions would be great..
Thanks - HP

Appreciate your kind reply Robert..
Would it be the only option left for me to re instantiate the logical standby..? Or what if i enable flashback on logical standby and then try to flashback till "standby_became_primary_scn" and then try to start logical standby apply.. Will this work in my scenario?
Any suggestions or comments are most welcome.
Thanks - HP

Logical standby apply won't apply logs

RDBMS Version: Oracle 10.2.0.2
Operating System and Version: Red Hat Enterprise Linux ES release 4
Error Number (if applicable):
Product (i.e. SQL*Loader, Import, etc.): Oracle Dataguard (Logical Standby)
Product Version:
Hi!!
I have problem logical standby apply won't apply logs.
SQL> SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
TYPE HIGH_SCN
STATUS
COORDINATOR 288810
ORA-16116: no work available
READER 288810
ORA-16240: Waiting for logfile (thread# 1, sequence# 68)
BUILDER 288805
ORA-16116: no work available
TYPE HIGH_SCN
STATUS
PREPARER 288804
ORA-16116: no work available
ANALYZER 288805
ORA-16116: no work available
APPLIER 288805
ORA-16116: no work available
TYPE HIGH_SCN
STATUS
APPLIER
ORA-16116: no work available
APPLIER
ORA-16116: no work available
APPLIER
ORA-16116: no work available
TYPE HIGH_SCN
STATUS
APPLIER
ORA-16116: no work available
10 rows selected.
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME, DICT_BEGIN, DICT_END FROM DBA_LOGSTDBY_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIM NEXT_TIME DIC DIC
66 11-JAN-07 11-JAN-07 YES YES
67 11-JAN-07 11-JAN-07 NO NO
SQL> SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME = 'coordinator state';
NAME
VALUE
coordinator state
IDLE
SQL> SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN NEWEST_SCN
288803 288809
INITPRIMARY.ORA
DB_NAME=primary
DB_UNIQUE_NAME=primary
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
service_names=primary
instance_name=primary
UNDO_RETENTION=3600
LOG_ARCHIVE_CONFIG='DG_CONFIG=(primary,standy)'
LOG_ARCHIVE_DEST_1=
'LOCATION=/home/oracle/primary/arch1/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=primary'
LOG_ARCHIVE_DEST_2=
'SERVICE=standy LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=standy'
LOG_ARCHIVE_DEST_3=
'LOCATION=/home/oracle/primary/arch2/
VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE)
DB_UNIQUE_NAME=primary'
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
FAL_SERVER=standy
FAL_CLIENT=primary
DB_FILE_NAME_CONVERT='standy','primary'
LOG_FILE_NAME_CONVERT=
'/home/oracle/standy/oradata','home/oracle/primary/oradata'
STANDBY_FILE_MANAGEMENT=AUTO
INITSTANDY.ORA
db_name='standy'
DB_UNIQUE_NAME='standy'
REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
SERVICE_NAMES='standy'
LOG_ARCHIVE_CONFIG='DG_CONFIG=(primary,standy)'
DB_FILE_NAME_CONVERT='/home/oracle/primary/oradata','/home/oracle/standy/oradata'
LOG_FILE_NAME_CONVERT=
'/home/oracle/primary/oradata','/home/oracle/standy/oradata'
LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_DEST_1=
'LOCATION=/home/oracle/standy/arc/
VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=standy'
LOG_ARCHIVE_DEST_2=
'SERVICE=primary LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=primary'
LOG_ARCHIVE_DEST_3=
'LOCATION=/home/oracle/standy/arch2/
VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE)
DB_UNIQUE_NAME=standy'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
LOG_ARCHIVE_DEST_STATE_3=ENABLE
STANDBY_FILE_MANAGEMENT=AUTO
FAL_SERVER=primary
FAL_CLIENT=standy
Alert Log Banco "Standy" desde a inicialização do SQL Apply
Thu Jan 11 15:00:54 2007
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
Thu Jan 11 15:01:00 2007
alter database add supplemental log data (primary key, unique index) columns
Thu Jan 11 15:01:00 2007
SUPLOG: Updated supplemental logging attributes at scn = 289537
SUPLOG: minimal = ON, primary key = ON
SUPLOG: unique = ON, foreign key = OFF, all column = OFF
Completed: alter database add supplemental log data (primary key, unique index) columns
LOGSTDBY: Unable to register recovery logfiles, will resend
Thu Jan 11 15:01:04 2007
LOGMINER: Error 308 encountered, failed to read missing logfile /home/oracle/standy/arch2/1_68_608031954.arc
Thu Jan 11 15:01:04 2007
LOGMINER: Error 308 encountered, failed to read missing logfile /home/oracle/standy/arch2/1_68_608031954.arc
Thu Jan 11 15:01:04 2007
ALTER DATABASE START LOGICAL STANDBY APPLY (standy)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
LSP0 started with pid=21, OS id=12165
Thu Jan 11 15:01:05 2007
LOGSTDBY Parameter: DISABLE_APPLY_DELAY =
LOGSTDBY Parameter: REAL_TIME =
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
Thu Jan 11 15:01:07 2007
LOGSTDBY status: ORA-16111: log mining and apply setting up
Thu Jan 11 15:01:07 2007
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: session# = 1, reader process P000 started with pid=22 OS id=12167
LOGMINER: session# = 1, builder process P001 started with pid=23 OS id=12169
LOGMINER: session# = 1, preparer process P002 started with pid=24 OS id=12171
Thu Jan 11 15:01:17 2007
LOGMINER: Begin mining logfile: /home/oracle/standy/arch2/1_66_608031954.arc
Thu Jan 11 15:01:17 2007
LOGMINER: Turning ON Log Auto Delete
Thu Jan 11 15:01:26 2007
LOGMINER: End mining logfile: /home/oracle/standy/arch2/1_66_608031954.arc
Thu Jan 11 15:01:26 2007
LOGMINER: Begin mining logfile: /home/oracle/standy/arch2/1_67_608031954.arc
Thu Jan 11 15:01:26 2007
LOGMINER: End mining logfile: /home/oracle/standy/arch2/1_67_608031954.arc
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusable
Thu Jan 11 15:01:33 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ have been marked unusable
Thu Jan 11 15:02:05 2007
Indexes of table SYSTEM.LOGMNR_ATTRCOL$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_ATTRIBUTE$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_CCOL$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_CDEF$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_COL$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_COLTYPE$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_DICTIONARY$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_ICOL$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_IND$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_INDCOMPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_INDPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_INDSUBPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_LOB$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_LOBFRAG$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_OBJ$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TAB$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TABCOMPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TABPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TABSUBPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TS$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TYPE$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_USER$ have been rebuilt and are now usable
LSP2 started with pid=25, OS id=12180
LOGSTDBY Analyzer process P003 started with pid=26 OS id=12182
LOGSTDBY Apply process P008 started with pid=20 OS id=12192
LOGSTDBY Apply process P007 started with pid=30 OS id=12190
LOGSTDBY Apply process P005 started with pid=28 OS id=12186
LOGSTDBY Apply process P006 started with pid=29 OS id=12188
LOGSTDBY Apply process P004 started with pid=27 OS id=12184
Thu Jan 11 15:02:48 2007
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 12194
RFS[1]: Identified database type as 'logical standby'
Thu Jan 11 15:02:48 2007
RFS LogMiner: Client enabled and ready for notification
Thu Jan 11 15:02:49 2007
RFS LogMiner: RFS id [12194] assigned as thread [1] PING handler
Thu Jan 11 15:02:49 2007
LOGMINER: Begin mining logfile: /home/oracle/standy/arch2/1_66_608031954.arc
Thu Jan 11 15:02:49 2007
LOGMINER: Turning ON Log Auto Delete
Thu Jan 11 15:02:51 2007
LOGMINER: End mining logfile: /home/oracle/standy/arch2/1_66_608031954.arc
Thu Jan 11 15:02:51 2007
LOGMINER: Begin mining logfile: /home/oracle/standy/arch2/1_67_608031954.arc
Thu Jan 11 15:02:51 2007
LOGMINER: End mining logfile: /home/oracle/standy/arch2/1_67_608031954.arc
Please, help me more time!!!!
Thanks.

Hello!
thank you for the reply.
The archive 1_68_608031954.arc that error of reading occurred, did not exist in the date of the error sees below:
$ ls -lh /home/oracle/standy/arch2/
total 108M
-rw-r----- 1 oracle oinstall 278K Jan 11 15:00 1_59_608031954.arc
-rw-r----- 1 oracle oinstall 76K Jan 11 15:00 1_60_608031954.arc
-rw-r----- 1 oracle oinstall 110K Jan 11 15:00 1_61_608031954.arc
-rw-r----- 1 oracle oinstall 1.0K Jan 11 15:00 1_62_608031954.arc
-rw-r----- 1 oracle oinstall 2.0K Jan 11 15:00 1_63_608031954.arc
-rw-r----- 1 oracle oinstall 96K Jan 11 15:00 1_64_608031954.arc
-rw-r----- 1 oracle oinstall 42K Jan 11 15:00 1_65_608031954.arc
-rw-r----- 1 oracle oinstall 96M Jan 13 06:10 1_68_608031954.arc
-rw-r----- 1 oracle oinstall 12M Jan 13 13:29 1_69_608031954.arc
$ ls -lh /home/oracle/primary/arch1/
total 112M
-rw-r----- 1 oracle oinstall 278K Jan 11 14:21 1_59_608031954.arc
-rw-r----- 1 oracle oinstall 76K Jan 11 14:33 1_60_608031954.arc
-rw-r----- 1 oracle oinstall 110K Jan 11 14:46 1_61_608031954.arc
-rw-r----- 1 oracle oinstall 1.0K Jan 11 14:46 1_62_608031954.arc
-rw-r----- 1 oracle oinstall 2.0K Jan 11 14:46 1_63_608031954.arc
-rw-r----- 1 oracle oinstall 96K Jan 11 14:55 1_64_608031954.arc
-rw-r----- 1 oracle oinstall 42K Jan 11 14:55 1_65_608031954.arc
-rw-r----- 1 oracle oinstall 4.2M Jan 11 14:56 1_66_608031954.arc
-rw-r----- 1 oracle oinstall 5.5K Jan 11 14:56 1_67_608031954.arc
-rw-r----- 1 oracle oinstall 96M Jan 13 06:09 1_68_608031954.arc
-rw-r----- 1 oracle oinstall 12M Jan 13 13:28 1_69_608031954.arc
Alert log
hu Jan 11 15:01:00 2007
SUPLOG: Updated supplemental logging attributes at scn = 289537
SUPLOG: minimal = ON, primary key = ON
SUPLOG: unique = ON, foreign key = OFF, all column = OFF
Completed: alter database add supplemental log data (primary key, unique index) columns
LOGSTDBY: Unable to register recovery logfiles, will resend
Thu Jan 11 15:01:04 2007
LOGMINER: Error 308 encountered, failed to read missing logfile /home/oracle/standy/arch2/1_68_608031954.arc
Thu Jan 11 15:01:04 2007
LOGMINER: Error 308 encountered, failed to read missing logfile /home/oracle/standy/arch2/1_68_608031954.arc
You it would know as to help me?
Would be a BUG of the Oracle 10g?
Thanks.

Create logical standby.

Hi.
I've created physical standby database on the same machine.
Standby apply archivelogs.
I strugle with convert physical standby into logical one.
When I try create controlfile for logical get:
SYS@stb>ALTER DATABASE CREATE LOGICAL STANDBY CONTROLFILE AS '/tmp/stbl.ctl';
ALTER DATABASE CREATE LOGICAL STANDBY CONTROLFILE AS '/tmp/stbl.ctl'
ERROR at line 1:
ORA-06550: line 1, column 36:
PLS-00201: identifier 'DBMS_LOGMNR_D.STORE_IN_REDO_LOGS' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
pls

FEDORA 6 & ORACLE 10.2.0
alert_stb.log:
alter database start logical standby apply
Wed Jun 17 22:46:58 2009
ALTER DATABASE START LOGICAL STANDBY APPLY (stb)
Wed Jun 17 22:46:58 2009
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=22, OS id=4156
Wed Jun 17 22:46:59 2009
Completed: alter database start logical standby apply
Wed Jun 17 22:47:01 2009
LOGSTDBY status: ORA-16111: log mining and apply setting up
Wed Jun 17 22:47:01 2009
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: session# = 1, reader process P000 started with pid=23 OS id=4158
LOGMINER: session# = 1, builder process P001 started with pid=24 OS id=4160
LOGMINER: session# = 1, preparer process P002 started with pid=25 OS id=4162
Wed Jun 17 22:47:02 2009
LOGMINER: Begin mining logfile: /u01/app/oracle/flash_recovery_area/STB/archivelog_3/1_3_689731882.arc
Wed Jun 17 22:47:02 2009
LOGMINER: Turning ON Log Auto Delete
Wed Jun 17 22:47:02 2009
LOGMINER: End mining logfile: /u01/app/oracle/flash_recovery_area/STB/archivelog_3/1_3_689731882.arc
LOGSTDBY Analyzer process P003 started with pid=26 OS id=4164
LOGSTDBY Apply process P008 started with pid=31 OS id=4174
LOGSTDBY Apply process P007 started with pid=30 OS id=4172
LOGSTDBY Apply process P004 started with pid=27 OS id=4166
LOGSTDBY Apply process P006 started with pid=29 OS id=4170
LOGSTDBY Apply process P005 started with pid=28 OS id=4168

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

Logical standby Slow after starting auditing

Similar Messages

Maybe you are looking for