Checkpoint interval

Hi All,
I m new in oracle can any one tell me what would be the correct answer of this question
you are attempting to increase the checkpoint interval on your database.Each of the following choices will affect the duaration/or frequency of checkpoint,except one.
A)size of redo log
B)number of datafile
C)LOG_CHECKPOINT_INTERVAL
D)LOG_CHECKPOINT_TIMEOUT
thanks in Advance .

Personally, I don't mind helping out with people doing tests, though I would have thought the answer to this was pretty darn'd obvious. I certainly don't see the point in taking the trouble to write to say you won't take the trouble to reply!
Parameters that have the word CHECKPOINT in them are likely to have an effect on the rate at which checkpoints happen, don't you think? So that rules out C and D.
To decide between A and B as the one that has no effect, it would help if you tried to remember what a checkpoint actually is, of course. It's the point in the lifetime of the database when DBWR decides to start flushing dirty buffers to disk. All sorts of things can trigger when that happens: shutting down the instance will do it, for example. So will putting a tablespace into hot backup mode. Dropping a table. Switching redo logs is another...
Oooh! Now there's a giveaway. If switching redo logs when one has filled up causes a checkpoint, then presumably it will take a lot longer to fill up a big redo log than a small one. Therefore, big logs must slow down the rate of checkpointing and smaller ones must speed it up.
Which rather means there's only one right answer left, doesn't it?

Similar Messages

Performance / stability issues with BDB 3.3.62 while checkpointing

Hi,
first of all: we use BDB 3.2 for more than a year within our application and we never had any performance or stability issues. Now we are about to release a new version of our software with BDB 3.3 and we found some problems during our release tests.
This is the situation: we have implemented some cleanup routines that make very heavy use of the BDB environment. The common usage pattern is to scan the database (about 300GB with >> 100 million items) and than delete a lot of items from the database. The first versions of our cleanup routine worked without any problem but during performance tuning of our code we suddenly and reproducible encountered segmentation faults in the com.sleepycat.je.recovery.Checkpointer thread. We analysed more that 10 VM crashes and ALL crashes were related to Checkpointer thread. (Linux 64 bit, JDK 1.5.0_013 / 1.6.0_06)
After we removed our performance tuning (only application logic – nothing BDB-related) the VM crashes disappeared – so it looks like some kind of problem which only occurs under high load conditions. Next thing we tried was enabling our performance tuning and setting Ceckpointer configuration to default (write a checkpoint after 20MB) before that we used time based checkpointing with 60 sec interval.
With Default Checkpointer configuration there were no VM-crashes but performance was very slow!
Finally my question: What Checkpointer configuration would you recommend for an environment that is under very high load with regard to delete operations? Would you recommend using “high priority Checkpointing”? Would you recommend time- or data-based checkpointing?
It looks like Checkpointing every 60 seconds was not a good idea but 20MB seems to be too slow.
This leads to another question: What does a longer Checkpointing interval mean for recovery time? Does recovery take substantially longer if checkpointing is done less fequently?
Any help would be very much apprechiated.
Here are two HS_ERR_PID
# An unexpected error has been detected by Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00002af3cbe47a27, pid=29834, tid=1170757984
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b23 mixed mode linux-amd64)
# Problematic frame:
# V [libjvm.so+0x5d8a27]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
--------------- T H R E A D ---------------
Current thread (0x00002aad7cd06800): JavaThread "Checkpointer" daemon [_thread_in_vm, id=30798, stack(0x0000000045b85000,0x0000000045c86000)]
siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000010
Registers:
RAX=0x00002aad7c942d80, RBX=0x00002aad7cd06800, RCX=0x00002aad7c943168, RDX=0x00002aad7c942d90
RSP=0x0000000045c84720, RBP=0x0000000045c84730, RSI=0x00002aabf193e230, RDI=0x0000000000000000
R8 =0x00002aad7dcf4380, R9 =0x000000000000784e, R10=0x00002af3cbb8e840, R11=0x0000000045c84810
R12=0x0000000000000000, R13=0x0000000045c84780, R14=0x0000000045c84838, R15=0x00002aad7cd06800
RIP=0x00002af3cbe47a27, EFL=0x0000000000010206, CSGSFS=0x0000000000000033, ERR=0x0000000000000004
TRAPNO=0x000000000000000e
Top of Stack: (sp=0x0000000045c84720)
0x0000000045c84720: 00002aad7cd06800 0000000000000000
0x0000000045c84730: 0000000045c84740 00002af3cbce3a9d
0x0000000045c84740: 0000000045c847b0 00002af3cbb8e896
0x0000000045c84750: 00002aad7dcf4380 00002aad7c942d80
0x0000000045c84760: 00002aad7c942d90 00002aad7c943168
0x0000000045c84770: 00002aad7cd06800 00002aad7cd06800
0x0000000045c84780: 00002aad7cd06800 0000000000000000
0x0000000045c84790: 000000002f7e8112 00002aabf193e1f9
0x0000000045c847a0: 0000000000000000 00002aad5fede569
0x0000000045c847b0: 0000000045c84810 00002aaaab25a0c7
0x0000000045c847c0: 00002aaaab253070 00002aaaab25a08b
0x0000000045c847d0: 0000000045c847d0 00002aad5fede569
0x0000000045c847e0: 0000000045c84838 00002aad5fedef50
0x0000000045c847f0: 00002aad601fedc0 00002aad5fede5b0
0x0000000045c84800: 0000000000000000 0000000045c84840
0x0000000045c84810: 0000000000010001 00002aaaab854744
0x0000000045c84820: 0000000000000000 0000000000000000
0x0000000045c84830: 0000000000000000 0000000000000000
0x0000000045c84840: 00002aad7cd06800 00002aaacd77a138
0x0000000045c84850: 00002aaaf27a8c90 00002aac00000001
0x0000000045c84860: 00002aaa00000000 00002af3cbd73369
0x0000000045c84870: 0000000145c848b0 000000002f7e8112
0x0000000045c84880: 00002aad7cd06800 00002aaaf39de2f0
0x0000000045c84890: 00002aabbee886d0 00002aab35552900
0x0000000045c848a0: 00002aaacd77a3c8 00002aaaf573a448
0x0000000045c848b0: 00002aaaee5aaab8 00002aaacd77a160
0x0000000045c848c0: 00002aab355887f0 00002aaaee643748
0x0000000045c848d0: 00002aaacd77a160 00002aac6a858558
0x0000000045c848e0: 0000000000000000 00002aaacd77a380
0x0000000045c848f0: 00002aad0000005b 0000000000000001
0x0000000045c84900: 0000000000000001 00002aaacd779328
0x0000000045c84910: 00002aabad0b62d8 00002aaaab7589c0
Instructions: (pc=0x00002af3cbe47a27)
0x00002af3cbe47a17: 89 f0 eb ea 90 66 66 66 90 55 48 89 e5 41 54 53
0x00002af3cbe47a27: 0f b7 57 10 48 89 fb 44 8d 62 01 49 63 fc e8 06
Stack: [0x0000000045b85000,0x0000000045c86000], sp=0x0000000045c84720, free space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x5d8a27]
V [libjvm.so+0x474a9d]
V [libjvm.so+0x31f896]
v ~BufferBlob::Interpreter
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
v ~BufferBlob::Interpreter
J com.sleepycat.je.recovery.Checkpointer.flushIN(Lcom/sleepycat/je/dbi/EnvironmentImpl;Lcom/sleepycat/je/dbi/DatabaseImpl;
Lcom/sleepycat/je/log/LogManager;Lcom/sleepycat/je/recovery/Checkpointer$CheckpointReference;Lcom/sleepycat/je/recovery/DirtyINMap;IIZJZLcom/sleepycat/je/recovery/Checkpointer$FlushStats;
Lcom/sleepycat/je/cleaner/LocalUtilizationTracker;Z)V
J com.sleepycat.je.recovery.Checkpointer.flushDirtyNodes(Lcom/sleepycat/je/dbi/EnvironmentImpl;Lcom/sleepycat/je/recovery/DirtyINMap;
Ljava/util/Map;ZJZLcom/sleepycat/je/recovery/Checkpointer$FlushStats;)V
v ~BufferBlob::Interpreter
v ~BufferBlob::Interpreter
v ~BufferBlob::Interpreter
v ~BufferBlob::Interpreter
v ~BufferBlob::StubRoutines (1)
# An unexpected error has been detected by Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00002b00816f2a27, pid=32743, tid=1162336608
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b23 mixed mode linux-amd64)
# Problematic frame:
# V [libjvm.so+0x5d8a27]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
--------------- T H R E A D ---------------
Current thread (0x00002aad7fa1c000): JavaThread "Checkpointer" daemon [_thread_in_vm, id=32646, stack(0x000000004537d000,0x000000004547e000)]
siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000010
Registers:
RAX=0x00002aad8082f9b0, RBX=0x00002aad7fa1c000, RCX=0x00002aad8082fd98, RDX=0x00002aad8082f9c0
RSP=0x000000004547c5e0, RBP=0x000000004547c5f0, RSI=0x00002aab73edc788, RDI=0x0000000000000000
R8 =0x00002aad7fa08d30, R9 =0x0000000000007f86, R10=0x00002b0081439840, R11=0x000000004547c6d0
R12=0x00002aaca950fcc8, R13=0x000000004547c640, R14=0x000000004547c6f8, R15=0x00002aad7fa1c000
RIP=0x00002b00816f2a27, EFL=0x0000000000010202, CSGSFS=0x0000000000000033, ERR=0x0000000000000004
TRAPNO=0x000000000000000e
Top of Stack: (sp=0x000000004547c5e0)
0x000000004547c5e0: 00002aad7fa1c000 00002aaca950fcc8
0x000000004547c5f0: 000000004547c600 00002b008158ea9d
0x000000004547c600: 000000004547c670 00002b0081439896
0x000000004547c610: 00002aad7fa08d30 00002aad8082f9b0
0x000000004547c620: 00002aad8082f9c0 00002aad8082fd98
0x000000004547c630: 00002aad7fa1c000 00002aad7fa1c000
0x000000004547c640: 00002aad7fa1c000 00002aaca950fcc8
0x000000004547c650: 000000004547c540 00002aab73edc751
0x000000004547c660: 00002aaca950fcc8 00002aad5fef5d49
0x000000004547c670: 000000004547c6d0 00002aaaab25a0c7
0x000000004547c680: 00002aaaab253070 00002aaaab25a08b
0x000000004547c690: 000000004547c690 00002aad5fef5d49
0x000000004547c6a0: 000000004547c6f8 00002aad5fef6730
0x000000004547c6b0: 00002aad600eed48 00002aad5fef5d90
0x000000004547c6c0: 0000000000000000 000000004547c700
0x000000004547c6d0: 0000000000010001 00002aaaaba46ac0
0x000000004547c6e0: 0000000000000000 0000000000000000
0x000000004547c6f0: 0000000000000000 0000000000000000
0x000000004547c700: 0001000100010005 00002aaa00000001
0x000000004547c710: 0010244e00432762 00002aab2ef43ff0
0x000000004547c720: 00002aaaf0635a00 00002aac5694a460
0x000000004547c730: 0000000100000000 00002aad7fa1c000
0x000000004547c740: 00002aabe0162870 00002aaaf0761bf0
0x000000004547c750: 00002aaaf07f20d0 00002aaadd628058
0x000000004547c760: 00002aaadd628ee0 00002aaa00000001
0x000000004547c770: 00002aaaeec996b8 0000000000000000
0x000000004547c780: 00002aab2ecc9890 00002aad00000000
0x000000004547c790: 00002aaadd627af0 00002aac5bc259c8
0x000000004547c7a0: 0000000000000000 00002aaadd628010
0x000000004547c7b0: 0000000000000001 00002aaaee4f8870
0x000000004547c7c0: 00000030f1218c01 00002aaae5222d38
0x000000004547c7d0: 0000000000010001 00002aaaab6cc928
Instructions: (pc=0x00002b00816f2a27)
0x00002b00816f2a17: 89 f0 eb ea 90 66 66 66 90 55 48 89 e5 41 54 53
0x00002b00816f2a27: 0f b7 57 10 48 89 fb 44 8d 62 01 49 63 fc e8 06
Stack: [0x000000004537d000,0x000000004547e000], sp=0x000000004547c5e0, free space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x5d8a27]
V [libjvm.so+0x474a9d]
V [libjvm.so+0x31f896]
v ~BufferBlob::Interpreter
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
v ~BufferBlob::Interpreter
J com.sleepycat.je.recovery.Checkpointer.flushIN(Lcom/sleepycat/je/dbi/EnvironmentImpl;
Lcom/sleepycat/je/dbi/DatabaseImpl;Lcom/sleepycat/je/log/LogManager;
Lcom/sleepycat/je/recovery/Checkpointer$CheckpointReference;Lcom/sleepycat/je/recovery/DirtyINMap;
IIZJZLcom/sleepycat/je/recovery/Checkpointer$FlushStats;Lcom/sleepycat/je/cleaner/LocalUtilizationTracker;Z)V
J com.sleepycat.je.recovery.Checkpointer.flushDirtyNodes(Lcom/sleepycat/je/dbi/EnvironmentImpl;Lcom/sleepycat/je/recovery/DirtyINMap;Ljava/util/Map;ZJZLcom/sleepycat/je/recovery/Checkpointer$FlushStats;)V
v ~BufferBlob::Interpreter
v ~BufferBlob::Interpreter
v ~BufferBlob::Interpreter
v ~BufferBlob::Interpreter
v ~BufferBlob::StubRoutines (1)

Hello,
I know your request is a bit old but I have exactly the same error on a jboss server but no HS_ERR_PID was create...
Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b23 mixed mode linux-amd64)
# Problematic frame:
# V [libjvm.so+0x5d8a27]
Do you remember how you solve your problem?
regards
Arnaud

DB Recovery takes a long time even after checkpointing

We observe that DB recovery takes a long time after application recovery even if we keep doing checkpoints at frequent(30 secs) intervals. These are the parameters that we use to open the environment:
env_flags =
DB_CREATE | /* Create the environment if it does not exist */
DB_RECOVER | /* Run normal recovery. */
DB_INIT_LOCK | /* Initialize the locking subsystem */
DB_INIT_LOG | /* Initialize the logging subsystem */
DB_INIT_TXN | /* Initialize the transactional subsystem. This
* also turns on logging. */
DB_INIT_MPOOL | /* Initialize the memory pool (in-memory cache) */
DB_THREAD | /* Cause the environment to be free-threaded */
DB_REGISTER |
DB_INIT_REP | /* Cause the environment to be replicated */
DB_SYSTEM_MEM ;
Our understanding was that recovery time should be proportional to the checkpoint interval. Can anyone please give some insights into what might be happening and how the recovery process works. It seems like DB is going back far in time while traversing the logs. We do not remove any log files as part of our regular process flows.
Secondly, we observe that recovery times increase proportionately with the size of our database even with checkpointing. Any insights into this are also welcome.
We are using DB 4.7.25 C API on HP-UX 11i.

try to burn recovery dvds and use it.
also perform disk check.
http://support.microsoft.com/kb/315265

Log file switch (checkpoint incomplete)

hello,
Lately, I have a lot of update/delete work on my OLTP production database. Generally this database is heavy loaded with much inserts especially at the daytime so I do my work at nights :) However, this work cause some contention. I have run AWR raport and I see "log file switch (checkpoint incomplete)" on a second place in wait events. I have a six redo log groups, each file 400MB, redo log buffer 12MB, mttr 0, checkpoint interval 0 and checkpoint timeout 1800 so checkpoints are usually "made by" log switches. Normally I have 2-5 switches per hour, but when I am doing my work it's abut 15-20 switches/hour. Can I speed it up by resizing redo files or by adding more groups ? I don't have test environment to test it so I am wondering if somone has experiense with that?
thanks
10gr2, linux

Hi Helter,
i have expirienced the same problem only with smaller log files and 3 groups, the solution you suggested helped me solve the issue, eversince i don't have any "checkpoint incomplete" error masaages in the alert log file.
i have enlarged each group to be 100 mb (initially was 50 mb) and added 2 more groups.
hope this solution will help you too.
dBarak

Process dbwriter and checkpoint

Hi,
It is known that when the redo log buffer is full at the third(1/3) , the datas which are in the redolog buffer are sent to the database's redo log files .
What happens then with the dbwriter process and the checkpoint process?Is there a new sequence number( SCN=system change number) created when the redo log buffer is sent to the database ?
Secondly, concerning the log_check_point_interval, can you explain to me what means that "in the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks."
LOG_CHECKPOINT_INTERVAL specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks.
I don't exactly understand when occurs a log_checkpoint and what means that it concerns operating system blocks and not database blocks.
Does it mean it concerns the redo log buffer?
Thanks a lot for your answer.
Best regards.
Nathalie

DBWR does not write dirty buffers to the corresponding disk blocks until the Redo for those blocks (i.e. the changes made to the blocks) has been written by LGWR to the online redo log files. Therefore, Redo is always written to disk before modified blocks (whether they be table or index or undo blocks) are rewritten to disk.
The block size for online redo log files is NOT the database block size (which is specified by the instance parameter db_block_size). Redo log files are written direct to the OS and use the OS's block size -- which is typically 512bytes.
Thus, specifying LOG_CHECKPOINT_INTERVAL of, say, 100000 is an instruction to Oracle that "when the current online redo log file is about 50MB (100000 512byte blocks is 48.82125MB) written, issue a Checkpoint to DBWR so that DBWR also writes dirty buffers to disk". That way, every checkpoint interval is actually smaller than the actual online redo log file (a checkpoint will still be issued when the online redo log file is full and a switch logfile occcurs).
Hemant K Chitale

Capture streaming does not work after upgrade of the source database.

Hello,
We have a complex system with 2 X RAC databases 10.2.0.4 (source) and 2 X single databases (target) 11.2.0.2
Streaming is running only from source to target.
After upgrading RAC databases to 11.2.0.2 , streaming is working only from one RAC to one single database.
First RAC streaming is flowing to first single database only, and second RAC to second single only.
First source-target is streaming fine, second capture are aborted just after starting with following errors:
Streams CAPTURE CP05 for STREAMS started with pid=159, OS id=21174
Wed Mar 28 10:41:55 2012
Propagation Sender/Receiver (CCA) for Streams Capture and Apply STREAMS with pid=189, OS id=21176 started.
Wed Mar 28 10:43:05 2012
Streams APPLY AP05 for STREAMS started with pid=134, OS id=21696
Wed Mar 28 10:43:06 2012
Streams Apply Reader for STREAMS started AS0G with pid=191 OS id=21709
Wed Mar 28 10:43:06 2012
Streams Apply Server for STREAMS started AS04 with pid=192 OS id=21711
Wed Mar 28 10:43:30 2012
Streams CAPTURE CP05 for STREAMS with pid=159, OS id=21174 is in combined capture and apply mode.
Capture STREAMS is handling 1 applies.
Streams downstream capture STREAMS uses downstream_real_time_mine: TRUE
Starting persistent Logminer Session with sid = 621 for Streams Capture STREAMS
LOGMINER: Parameters summary for session# = 621
LOGMINER: Number of processes = 3, Transaction Chunk Size = 1
LOGMINER: Memory Size = 10M, Checkpoint interval = 1000M
LOGMINER: SpillScn 0, ResetLogScn 7287662065313
LOGMINER: summary for session# = 621
LOGMINER: StartScn: 12620843936763 (0x0b7a.84eb6bfb)
LOGMINER: EndScn: 0
LOGMINER: HighConsumedScn: 12620843936763 (0x0b7a.84eb6bfb)
LOGMINER: session_flag 0x1
LOGMINER: LowCkptScn: 12620843920280 (0x0b7a.84eb2b98)
LOGMINER: HighCkptScn: 12620843920281 (0x0b7a.84eb2b99)
LOGMINER: SkipScn: 12620843920280 (0x0b7a.84eb2b98)
Wed Mar 28 10:44:53 2012
LOGMINER: session#=621 (STREAMS), reader MS00 pid=198 OS id=22578 sid=1148 started
Wed Mar 28 10:44:53 2012
LOGMINER: session#=621 (STREAMS), builder MS01 pid=199 OS id=22580 sid=1338 started
Wed Mar 28 10:44:53 2012
LOGMINER: session#=621 (STREAMS), preparer MS02 pid=200 OS id=22582 sid=1519 started
LOGMINER: Begin mining logfile for session 621 thread 1 sequence 196589, /opt/app/oracle/admin/singledb/stdbyarch/singledb_1_196589_569775692.arc
Errors in file /opt/app/oracle/diag/rdbms/singledb/singledb/trace/singledb_ms00_22578.trc (incident=113693):
ORA-00600: internal error code, arguments: [krvxruts004], [11.2.0.0.0], [10.2.0.4.0], [], [], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/diag/rdbms/singledb/singledb/incident/incdir_113693/singledb_ms00_22578_i113693.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
krvxerpt: Errors detected in process 198, role reader.
We have 5 streaming processes running.
When we rebuilded one of them, everything works fine, but other are too big for rebuilding.
Has anybody met with such a behaviour ?
Oracle development is already working on it but we need faster solution.
Thanks
Jurrai

wwn wrote:I got this after a former kernel update and I can give you only a typical windows advice: reinstall all the Bumblebeestuff after uninstallation and after a reboot. Sounds strange but worked for me.
What exactly did you reinstall? I am experiencing the same problem.

Logical standby stuck at initializing SQL apply only coordinator process up

Hi
OS: solaris 5.10
Hardware: sun sparc
Oracle database: 11.2.0.1.0
Primary database name: asadmin
Standby database name: test
I had been trying to convert a physical standby to logical standby database. Both the primary and standby reside on the same machine.
The physical standby was created with a hot backup of primary.
I had been following document id 278371.1 to convert the physical to logical standby and used the following steps:
Relevant init parameters on primary:
*.db_name='asadmin'
*.db_unique_name='asadmin'
*.log_archive_config='dg_config=(asadmin,test)'
*.log_archive_dest_1='location=/u01/asadmin/archive valid_for=(all_logfiles,all_roles) db_unique_name=asadmin'
*.log_archive_dest_2='SERVICE=test async valid_for=(online_logfiles,primary_role) db_unique_name=test'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.fal_client='asadmin'
*.fal_server='test'
*.remote_login_passwordfile='EXCLUSIVE'
Relevant init parameters on standby database:
*.db_name='test' -- Was asadmin before I renamed the DB during conversion to logical standby
*.db_unique_name='test'
*.log_archive_dest_1='location=/u01/test/archive valid_for=(all_logfiles,all_roles) db_unique_name=test'
*.log_archive_dest_2='service=asadmin async valid_for=(online_logfiles,primary_role) db_unique_name=asadmin'
*.log_archive_dest_state_1=enable
*.log_archive_dest_state_2=defer
*.remote_login_passwordfile='EXCLUSIVE'*.fal_server=test
*.fal_client=asadmin
Steps on primary:
1) alter system set log_archive_dest_state_2=defer;
2) shutdown immediate;
3) Made sure that the physical standby has applied all of the redo sent to it following the shutdown.
4) startup mount;
5) ALTER DATABASE BACKUP CONTROLFILE to '/home/oracle/control01.ctl';
6) ALTER SYSTEM ENABLE RESTRICTED SESSION;
7) ALTER DATABASE OPEN;
8) Verified that the supplemental logging is on.
9) ALTER SYSTEM ARCHIVE LOG CURRENT;
10) Checked for the checkpoint change no. at this point which is 72403818 and is present in archive log file 1_62_775102253.dbf
11) EXECUTE DBMS_LOGSTDBY.BUILD;
12) ALTER SYSTEM ARCHIVE LOG CURRENT;
13) Checked for the archive log containing dictionary build which is 1_64_775102253.dbf
14) ALTER SYSTEM DISABLE RESTRICTED SESSION;
Details of archive logs and related checkpoint change nos:
NAME FIRST_CHANGE# NEXT_CHANGE#
/u01/asadmin/archive/1_61_775102253.dbf 72402901 72403817
/u01/asadmin/archive/1_62_775102253.dbf 72403817 72404069
/u01/asadmin/archive/1_63_775102253.dbf 72404069 72404211
/u01/asadmin/archive/1_64_775102253.dbf 72404211 72405700
Steps on standby:
1) shutdown immediate;
2) Copy the archivelog file 61(was created at primary after apply stopped at standby), 62(contains checkpoint no. 72403818), 63 and 64(contains dictionary build). Copy the backup controlfile from step 5 above to the controlfile location in standby init.
3) startup mount;
4) Rename all datafiles and redo log files (including standby redo log files) to the correct path on standby.
5) alter database recover automatic from '/u01/test/archive' until change 72405700 using backup controlfile; -- This completed error-free
6) alter database guard all; -- this completed error free
7) alter database open resetlogs; -- this completed error free.
8) nid target=sys/oracle12 dbname=test
9) Changed the db_name in init file to new name test.
10) Added a tempfile to temp tablespaces.
11) ALTER DATABASE REGISTER LOGICAL LOGFILE '/u01/test/archive/1_61_775102253.dbf'; -- ORA-16225: Missing LogMiner session name for Streams
12) ALTER DATABASE START LOGICAL STANDBY APPLY INITIAL 72405700; -- This completed error free.
Also enabled the log_archive_dest_state_2 on primary.
After this output from some views:
SQL> SELECT SESSION_ID, STATE FROM V$LOGSTDBY_STATE;
SESSION_ID STATE
1 INITIALIZING
SQL> SELECT SID, SERIAL#, SPID, TYPE FROM V$LOGSTDBY_PROCESS;
SID SERIAL# SPID TYPE
587 22 15476 COORDINATOR
SELECT PERCENT_DONE, COMMAND
FROM V$LOGMNR_DICTIONARY_LOAD
WHERE SESSION_ID = (SELECT SESSION_ID FROM V$LOGSTDBY_STATE);
PERCENT_DONE
COMMAND
0
SQL> SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
TYPE HIGH_SCN STATUS
COORDINATOR ORA-16111: log mining and apply setting up
SQL> SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN NEWEST_SCN
72405700 72411501
SELECT THREAD#, SEQUENCE#, FILE_NAME FROM DBA_LOGSTDBY_LOG L
WHERE NEXT_CHANGE# NOT IN
(SELECT FIRST_CHANGE# FROM DBA_LOGSTDBY_LOG WHERE L.THREAD# = THREAD#)
ORDER BY THREAD#,SEQUENCE#;
no rows selected
SQL> SELECT EVENT_TIME, STATUS, EVENT
FROM DBA_LOGSTDBY_EVENTS
ORDER BY EVENT_TIMESTAMP, COMMIT_SCN; 2 3
EVENT_TIME STATUS EVENT
14-FEB-12 02:00:50 ORA-16111: log mining and apply setting up
14-FEB-12 02:00:50 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 02:20:11 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 02:20:39 ORA-16111: log mining and apply setting up
14-FEB-12 02:20:39 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 02:54:15 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 02:57:38 ORA-16111: log mining and apply setting up
EVENT_TIME STATUS EVENT
14-FEB-12 02:57:38 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 03:01:36 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 03:13:44 ORA-16111: log mining and apply setting up
14-FEB-12 03:13:44 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 04:32:23 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 04:34:17 ORA-16111: log mining and apply setting up
14-FEB-12 04:34:17 Apply LWM 72405699, HWM 72405699, SCN 72405699
EVENT_TIME STATUS EVENT
14-FEB-12 04:36:16 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 04:36:21 ORA-16111: log mining and apply setting up
14-FEB-12 04:36:21 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 05:15:22 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 05:15:29 ORA-16111: log mining and apply setting up
14-FEB-12 05:15:29 Apply LWM 72405699, HWM 72405699, SCN 72405699
I also greped for lsp and lcr processes and found that lsp is up but do not see any lcr.
The logs are getting transported to the archive destination on standby whenever they are archived on primary but are not getting applied to standby.
Also in case the standby is down while a log is generated on primary it is not automatically transported to standby once the standby is up, means gap resolution is also not working.
I see the following in alert log every time I try to restart the log apply, everything seems to be stuck at initialization.
ALTER DATABASE START LOGICAL STANDBY APPLY (test)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
Tue Feb 14 05:15:28 2012
LSP0 started with pid=28, OS id=23391
Completed: alter database start logical standby apply immediate
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 0, ResetLogScn 0
-- NOTHING AFTER THIS

Hello;
I noticed some of your parameters seem to be wrong.
fal_client - This is Obsolete in 11.2
You have db_name='test' on the Standby, it should be 'asadmin'
fal_server=test is set like this on the standby, it should be 'asadmin'
I might consider changing VALID_FOR to this :
VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)Would review 4.2 Step-by-Step Instructions for Creating a Logical Standby Database of Oracle Document E10700-02
Document 278371.1 is showing its age in my humble opinion.
-----Wait on this until you fix your parameters----------------------
Try restarting the SQL Apply
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEI don't see the parameter MAX_SERVERS, try setting it to 8 times the number of cores.
Use these statements to trouble shoot :
SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS;
SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME LIKE ;TRANSACTIONS%';
SELECT COUNT(1) AS IDLE_PREPARERS FROM V$LOGSTDBY_PROCESS WHERE
TYPE = 'PREPERER' AND STATUS_CODE = 16166;Best Regards
mseberg
Edited by: mseberg on Feb 14, 2012 7:37 AM

9.2.0.4 Upgrade to 10.2.0.1

Primary (9.2.0.4) ----Logical apply----> Logical Standby (9.2.0.4)
Status: Perfectly working logical apply
Primary (9.2.0.4) ----Logical Apply Stopped----> Logical Standby (Upgrade 9.2.0.4 to 10.2.0.1)
Status: Perfectly done upgrade with following alerts in log:
Database is working fine....but....
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_SESSION$ have been marked unusable
Some indexes or index [sub]partitions of table SYS.LOGMNR_BUILDLOG have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNRC_GTCS have been marked unusable
Primary (9.2.0.4) ----Logical apply Started again----> Logical Standby (10.2.0.1)
Primary (9.2.0.4) ----Logical apply----> Logical Standby (9.2.0.4)
Status: Perfectly working logical apply
Primary (9.2.0.4) ----Logical Apply Stopped----> Logical Standby (Upgrade 9.2.0.4 to 10.2.0.1)
Status: Logical Apply process started and failed with following:
ALTER DATABASE START LOGICAL STANDBY APPLY (xxxx)
Sun Jun 10 05:18:15 2007
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=21, OS id=26006
LOGSTDBY status: ORA-16111: log mining and apply setting up
Sun Jun 10 05:18:15 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=26008
LOGMINER: session# = 1, preparer process P002 started with pid=24 OS id=26012
Sun Jun 10 05:18:16 2007
Errors in file /oracle01/app/oracle/admin/xxxx/bdump/xxxx_lsp0_26006.trc:
ORA-00600: internal error code, arguments: [krvsgoa1], [201], [], [], [], [], [], []
Sun Jun 10 05:18:16 2007
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY
CAN ANYONE HELP ME IN THIS REGARD, PLEASE......

Hi Yingkuan,
That is a good document and I'm following almost the same procedure. Is there any other fully detailed document.
The idea is that i get the downtime only for once and that too just to build logminer dictionary.
So, thereafter I need to upgrade the logical first and that too with primary continuing up and running in that window.
Now I guess you understood my problem. So, any ideas?

What is mapLN and why is it eating all our space :)

here's a DbPringLog from a few months ago:
<pre>
[xoopit@xda-004 ###]$ java -jar ~/###/je-3.3.74.jar DbPrintLog -s 0x00000000 -e 0x0000000a -S
<DbPrintLog>
Log statistics:
type total provisional total min max avg entries
count count bytes bytes bytes bytes as % of log
LN_TX 219,704 0 26,803,878 117 132 121 44.7
MapLN 14 0 956 59 72 68 0
NameLN_TX 4 0 292 69 79 73 0
DupCountLN_TX 73,025 0 5,915,025 81 81 81 9.9
DupCountLN 211 211 11,816 56 56 56 0
FileSummaryLN 10 0 69,506 91 26,681 6,950 0.1
IN 2,033 76 8,213,996 67 6,368 4,040 13.7
BIN 4,064 3,957 12,297,614 57 6,319 3,025 20.5
DIN 799 54 253,737 197 687 317 0.4
DBIN 1,334 1,333 3,626,993 166 6,389 2,718 6
Root 4 0 326 62 88 81 0
Commit 73,238 0 2,783,044 38 38 38 4.6
CkptStart 2 0 81 39 42 40 0
CkptEnd 3 0 256 84 87 85 0
BINDelta 35 0 19,110 75 975 546 0
FileHeader 7 0 266 38 38 38 0
key/data 13,621,638 (22.7)
Total bytes in portion of log read: 59,996,896
Total number of entries: 374,487
Per checkpoint interval info:
lnTxn ln mapLNTxn mapLN end-end end-start start-end maxLNReplay ckptEnd
0 0 0 1 1,345 563 782 0 0x0/0x541
20,529 0 0 7 5,516,716 4,949,678 567,038 20,529 0x0/0x5432ed
128,339 0 0 6 34,716,133 54,481,939 0 128,339 0x7/0x392d2
70,836 0 0 0 19,765,806 19,765,806 0 70,836 0xa/0x0
</DbPrintLog>
</pre>
then a few days ago:
<pre>
[xoopit@xda-004 ###]$ java -jar ~/###/je-3.3.74.jar DbPrintLog -s 0x003ca27f -e 0x003cb06b -S
<DbPrintLog>
Log statistics:
type total provisional total min max avg entries
count count bytes bytes bytes bytes as % of log
LN_TX 534 0 51,086 86 108 95 0.1
LN 267,341 0 22,505,538 77 93 84 25.3
MapLN 9 0 668,956 74,226 74,539 74,328 0.8
DupCountLN_TX 178 0 11,393 63 65 64 0
DupCountLN 22 0 912 40 42 41 0
FileSummaryLN 7,669 0 693,427 72 2,462 90 0.8
IN 9,182 166 33,886,067 81 6,428 3,690 38.1
BIN 7,731 491 24,977,397 49 6,478 3,230 28.1
DIN 909 9 2,468,396 144 6,445 2,715 2.8
DBIN 619 56 3,555,037 136 6,494 5,743 4
Root 1 0 8,260 8,260 8,260 8,260 0
Commit 178 0 6,230 35 35 35 0
CkptStart 7 0 224 32 32 32 0
BINDelta 153 0 21,740 42 1,284 142 0
DupBINDelta 14 0 4,686 74 1,324 334 0
Trace 114 0 20,812 76 306 182 0
FileHeader 10 0 380 38 38 38 0
key/data 13,167,649 (14.8)
Total bytes in portion of log read: 88,880,541
Total number of entries: 294,671
Per checkpoint interval info:
lnTxn ln mapLNTxn mapLN end-end end-start start-end maxLNReplay ckptEnd
534 267,341 0 9 30,270,000,000 30,258,643,275 0 267,875 0x3cb06b/0x0
</DbPrintLog>
</pre>
and from today:
<pre>
xoopit@xda-004 ###]$ java -jar ~/###/je-3.3.74.jar DbPrintLog -s 0x004207c0 -e 0x004207c9 -S
<DbPrintLog>
Log statistics:
type total provisional total min max avg entries
count count bytes bytes bytes bytes as % of log
LN 44 0 3,507 78 93 79 0
MapLN 32 0 76,040,837 295,485 8,572,698 2,376,276 96.7
FileSummaryLN 156 0 9,362 30 220 60 0
IN 36 2 110,580 46 6,178 3,071 0.1
BIN 43 43 88,914 79 6,478 2,067 0.1
Root 11 0 2,405,444 218,657 218,708 218,676 3.1
CkptStart 1 0 31 31 31 31 0
CkptEnd 1 0 71 71 71 71 0
Trace 13 0 1,146 51 282 88 0
FileHeader 10 0 380 38 38 38 0
key/data 1,967 (0)
Total bytes in portion of log read: 78,660,272
Total number of entries: 347
Per checkpoint interval info:
lnTxn ln mapLNTxn mapLN end-end end-start start-end maxLNReplay ckptEnd
0 44 0 22150,110,853,335150,109,212,264 1,641,071 44 0x4207c6/0xd0557
0 0 0 10 29,146,665 29,146,665 0 5 0x4207c9/0x0
</DbPrintLog>
</pre>
as you can see 96.7% of our store is taken up by these mapLN entries. we haven't found any documentation as to what these things are. this is killing one of our BDB stores because in the last 24 hours we've generated around 10,000 new .jdb files when we used to have a few hundred...
we're using je-3.3.74
we upgraded to je-3.3.74 (from 3.3.62) on November 3rd but this particular issue didn't show up until around 24 hours ago.
thanks for taking a look ~j
Edited by: jules | xoopit on Nov 13, 2008 11:59 AM
Edited by: jules | xoopit on Nov 13, 2008 1:11 PM

Hi All,
We've been working on this with the Xoopit folks and I wanted to follow up and post the resolution, since it potentially impacts everyone using JE 3.3.x.
There is a bug in JE 3.3.74 and earlier, in all versions of the 3.3.x product. The fix for this is in JE 3.3.75, which currently is available on request. We haven't decided when we'll update our download site with this updated release. If you would like the updated release, please send email to mark.hayes at the obvious .com (oracle).
Here's the change log entry for the bug, which should explain what you need to know:
Fix a bug that caused the space taken by internal metadata in JE log files to increase over a long period of time. The rate of increase was slow in most cases, but in at least one observed case became rapid after a long time period and after the log cleaner became backlogged. To determine whether your JE log exhibits this problem, run
java -jar je.x.y.z.jar DbPrintLog -h DIR -S
and examine the line labeled MapLN on the left. If the amount of the log taken by MapLNs is 10% or greater, or if you see this number increasing steadily over time, then your application is probably experiencing this problem.
By installing JE 3.3.75 or later, the excess disk space will automatically be reclaimed over time, as ordinary checkpoints and log cleaning occur. If you wish to recreate your database rather than wait for this to occur gradually, you can use DbDump and DbLoad to do so.
We'd like to express our appreciation and sincere thanks to Jules and the other folks at Xoopit who reported this problem and helped us to diagnose it. We would not have found or fixed this problem as quickly as we did without their help.
For reference, the support ticket # for this problem is: #16610
If you have further questions, please reply to this forum post.
Thanks,
--mark

Sql Apply issue in logical standby database--(10.2.0.5.0) x86 platform

Hi Friends,
I am getting the following exception in logical standby database at the time of Sql Apply.
After run the command alter database start logical standby apply sql apply services start but after few second automatically stop and getting following exception.
alter database start logical standby apply
Tue May 17 06:42:00 2011
No optional part
Attempt to start background Logical Standby process
LOGSTDBY Parameter: MAX_SERVERS = 20
LOGSTDBY Parameter: MAX_SGA = 100
LOGSTDBY Parameter: APPLY_SERVERS = 10
LSP0 started with pid=30, OS id=4988
Tue May 17 06:42:00 2011
Completed: alter database start logical standby apply
Tue May 17 06:42:00 2011
LOGSTDBY status: ORA-16111: log mining and apply setting up
Tue May 17 06:42:00 2011
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 4, Transaction Chunk Size = 201
LOGMINER: Memory Size = 100M, Checkpoint interval = 500M
Tue May 17 06:42:00 2011
LOGMINER: krvxpsr summary for session# = 1
LOGMINER: StartScn: 0 (0x0000.00000000)
LOGMINER: EndScn: 0 (0x0000.00000000)
LOGMINER: HighConsumedScn: 2660033 (0x0000.002896c1)
LOGMINER: session_flag 0x1
LOGMINER: session# = 1, preparer process P002 started with pid=35 OS id=4244
LOGSTDBY Apply process P014 started with pid=47 OS id=5456
LOGSTDBY Apply process P010 started with pid=43 OS id=6484
LOGMINER: session# = 1, reader process P000 started with pid=33 OS id=4732
Tue May 17 06:42:01 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1417, X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
Tue May 17 06:42:01 2011
LOGMINER: Turning ON Log Auto Delete
Tue May 17 06:42:01 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
Tue May 17 06:42:01 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1418, X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
LOGSTDBY Apply process P008 started with pid=41 OS id=4740
LOGSTDBY Apply process P013 started with pid=46 OS id=7864
LOGSTDBY Apply process P006 started with pid=39 OS id=5500
LOGMINER: session# = 1, builder process P001 started with pid=34 OS id=4796
Tue May 17 06:42:02 2011
LOGMINER: skipped redo. Thread 1, RBA 0x00058a.00000950.0010, nCV 6
LOGMINER: op 4.1 (Control File)
Tue May 17 06:42:02 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1419, X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1420, X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1421, X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
LOGSTDBY Analyzer process P004 started with pid=37 OS id=5096
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
LOGSTDBY Apply process P007 started with pid=40 OS id=2760
Tue May 17 06:42:03 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
LOGSTDBY Apply process P012 started with pid=45 OS id=7152
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1422, X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1423, X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1424, X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
LOGMINER: session# = 1, preparer process P003 started with pid=36 OS id=5468
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
Tue May 17 06:42:04 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1425, X:\TANVI\ARCHIVE2\ARC01425_0748170313.001
LOGSTDBY Apply process P011 started with pid=44 OS id=6816
LOGSTDBY Apply process P005 started with pid=38 OS id=5792
LOGSTDBY Apply process P009 started with pid=42 OS id=752
Tue May 17 06:42:05 2011
krvxerpt: Errors detected in process 34, role builder.
Tue May 17 06:42:05 2011
krvxmrs: Leaving by exception: 600
Tue May 17 06:42:05 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
LOGSTDBY status: ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
Tue May 17 06:42:06 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_lsp0_4988.trc:
ORA-12801: error signaled in parallel query server P001
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
Tue May 17 06:42:06 2011
LogMiner process death detected
Tue May 17 06:42:06 2011
logminer process death detected, exiting logical standby
LOGSTDBY Analyzer process P004 pid=37 OS id=5096 stopped
LOGSTDBY Apply process P010 pid=43 OS id=6484 stopped
LOGSTDBY Apply process P008 pid=41 OS id=4740 stopped
LOGSTDBY Apply process P012 pid=45 OS id=7152 stopped
LOGSTDBY Apply process P014 pid=47 OS id=5456 stopped
LOGSTDBY Apply process P005 pid=38 OS id=5792 stopped
LOGSTDBY Apply process P006 pid=39 OS id=5500 stopped
LOGSTDBY Apply process P007 pid=40 OS id=2760 stopped
LOGSTDBY Apply process P011 pid=44 OS id=6816 stopped
Tue May 17 06:42:10 2011

Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []submit an SR to ORACLE SUPPORT.
refer these too
*ORA-600/ORA-7445 Error Look-up Tool [ID 153788.1]*
*Bug 6022014: ORA-600 [KRVXBPX20] ON LOGICAL STANDBY*

Asking for your help to Connect 4 Servers Toghether!

Hi. for more than 3 days i'm trying to build multi server's cast Based on the attached model.
Everything I've tried have not helped me.
can you kindly help me to build the right " vhost " file for each server as described in the attached model ???
I really appreciate it
Thank you very much
Elad.
----- THE VHOST -----
<VirtualHost>
          
          <AliasList>
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    <Alias name="alias1"></Alias>
          </AliasList>
          
          
          
          
          
          
          
          <AppsDir>${VHOST.APPSDIR}</AppsDir>







          
          
          <ResourceLimits>
                    
                    
                    <MaxConnections>-1</MaxConnections>
                    
                    
                    <MaxEdgeConnections>-1</MaxEdgeConnections>
                    
                    <MaxAppInstances>15000</MaxAppInstances>
                    
                    <MaxStreams>250000</MaxStreams>
                    
                    <MaxSharedObjects>50000</MaxSharedObjects>
                    
                    <AppInstanceGC>1</AppInstanceGC>
          </ResourceLimits>
          <VirtualKeys>
                    
                    
                    
                    
                    
                    
                    
          </VirtualKeys>
          
          
          
          
          
          
          
          
          
          
          
          
          
          <VirtualDirectory>
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    <Streams></Streams>
          </VirtualDirectory>
          
          
          
          <DNSSuffix></DNSSuffix>
          
          
          
          
          
          
          
          
          
          
          <Allow>all</Allow>
          <Proxy>
                    
                    
                    
                    
                    
                    
                    
                    <Mode>local</Mode>
                        
        
        
        
                        <RequestTimeout>2</RequestTimeout>
                    
                    
                    
                    
                    <Anonymous>false</Anonymous>
                    
                    <CacheDir enabled="false" useAppName="true">
                              
                      
                               
                              
                              <Path></Path>
                              
                              
                  
                              
                              <MaxSize>32</MaxSize>
                    </CacheDir>
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    <LocalAddress></LocalAddress>
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    <RouteTable protocol="rtmp">
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              <RouteEntry>1.1.1.1:1935;2.2.2.2:1935</RouteEntry>
                    </RouteTable>
                    
                    
                    
                    
                    
                    <EdgeAutoDiscovery>
                              
                              
                              <Enabled>true</Enabled>
                              
                              
                              
                              <AllowOverride>true</AllowOverride>
                              
                              
                              
                              
                              <WaitTime>1000</WaitTime>
                    </EdgeAutoDiscovery>
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    
                    <AggregateMessages enabled="true">
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                              
                    </AggregateMessages>
          </Proxy>
          
          <Logging>
                    
                    <Access>
                              
                              
                              
                              
                              
                              
                              
                    </Access>
          </Logging>
</VirtualHost>

You've now posted at least three times now and have been given the same answer every time. You've also had your posts editied for personal information every time.
We cannot help you get past the Activation Lock, only the person to whom it is locked can. We cannot help you unlock the phone from a carrier; only the carrier to which it is locked can.

Logical Standby....

Hi, I have Created Logical Standby data base on my windows 2003 Advance Server Machine and Oracle 10.2.0.3.
now I am having some problem that my LOGSTDBY is not in sync with the Primary DB from few days and in alertlog it is showing this error....
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, builder process P001 started with pid=18 OS id=2820
LOGMINER: session# = 1, reader process P000 started with pid=17 OS id=2816
LOGSTDBY Analyzer process P003 started with pid=20 OS id=2828
LOGSTDBY Apply process P005 started with pid=39 OS id=2984
LOGSTDBY Apply process P006 started with pid=40 OS id=2988
Fri Aug 21 11:56:17 2009
LOGMINER: Begin mining logfile: G:\ORACLE\ORADATA\SOS\ARCHIVE\SOST001S63660.ARC
Fri Aug 21 11:56:17 2009
LOGMINER: Turning ON Log Auto Delete
LOGSTDBY Apply process P004 started with pid=22 OS id=2980
LOGSTDBY Apply process P008 started with pid=42 OS id=2996
LOGMINER: session# = 1, preparer process P002 started with pid=19 OS id=2824
LOGSTDBY Apply process P007 started with pid=41 OS id=2992
Fri Aug 21 11:56:26 2009
Errors in file d:\oracle\admin\sos\bdump\logstdby_p004_2980.trc:
ORA-00604: error occurred at recursive SQL level 2
ORA-00955: name is already used by an existing object
Fri Aug 21 11:56:26 2009
LOGSTDBY status: ORA-00955: name is already used by an existing object
LOGSTDBY Apply process P004 pid=22 OS id=2980 stopped
Fri Aug 21 11:56:29 2009
Errors in file d:\oracle\admin\sos\bdump\logstdby_lsp0_2944.trc:
ORA-12801: error signaled in parallel query server P004
ORA-00955: name is already used by an existing object
LOGSTDBY Apply process P006 pid=40 OS id=2988 stopped
LOGSTDBY Analyzer process P003 pid=20 OS id=2828 stopped
LOGSTDBY Apply process P005 pid=39 OS id=2984 stopped
LOGSTDBY Apply process P007 pid=41 OS id=2992 stopped
LOGSTDBY Apply process P008 pid=42 OS id=2996 stopped
Fri Aug 21 11:58:50 2009
Redo Shipping Client Connected as PUBLIC
Plz rply ASAP

Here are the steps to identify the object in question:
1) Start the replication on logical standby
2) Once the replication starts it will show you the same error in the alert log file as you mentioned above.
3) Query DBA_LOGSTDBY_EVENTS order by EVENT_TIMESTAMP. The last event will capture the name of the object that is creating the problem.
4) Based on your knowledge of database /application objects, you can skip that table using DBMS_LOGSTADBY.SKIP and start the replication again without any issue.
5) If you dont need that object in the logical DB to be replicated then let it be skipped, otherwise reinstate the object again in logical standby.
Amar.

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.

DML CHANGES ARE NOT REFLECTING

Hello members,
I am new to oracle dataguard and I had configured a logical stand by database for testing purpose.
after successful implementation I am testing it on my test environment.
Since two days I am facing very strange error.
LOGSTDBY stmt: REVOKE SYSDBA FROM my username*
LOGSTDBY status: ORA-01031: insufficient privileges
LOGSTDBY id: XID 0x0006.007.00000208, hSCN 0x0000.0015acc3, lSCN 0x0000.0015acc3, Thread 1, RBA 0x00b3.000040cb.10, txnCscn 0x0000.0015acc6, PID 5184, ORACLE.EXE (P004)
LOGSTDBY Apply process P004 pid=26 OS id=5184 stopped
I did restart logical standby database, an than after I start logical standby at first attempt it starts without ay problem
but after this error standby automatically get shutdown.
My work environment.
O/S: windows server 2003, sp2.
oracle version 10.2.0.
alert.log file contains:
Sat Aug 25 11:16:41 2012
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
Sat Aug 25 11:16:41 2012
ORA-16239 signalled during: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE...
Sat Aug 25 11:16:57 2012
alter database start logical standby apply
Sat Aug 25 11:16:57 2012
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=23, OS id=2576
LOGSTDBY status: ORA-16111: log mining and apply setting up
Sat Aug 25 11:16:57 2012
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=5232
LOGMINER: session# = 1, preparer process P002 started with pid=26 OS id=5924
LOGMINER: session# = 1, builder process P001 started with pid=25 OS id=5584
LOGSTDBY Analyzer process P003 started with pid=27 OS id=5468
LOGSTDBY Apply process P006 started with pid=30 OS id=5448
LOGSTDBY Apply process P008 started with pid=34 OS id=1164
LOGSTDBY Apply process P007 started with pid=33 OS id=5992
LOGSTDBY Apply process P004 started with pid=28 OS id=5064
Sat Aug 25 11:16:57 2012
LOGMINER: Begin mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_178_791922278.ARC
Sat Aug 25 11:16:57 2012
LOGMINER: Turning ON Log Auto Delete
Sat Aug 25 11:16:57 2012
LOGMINER: End mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_178_791922278.ARC
Sat Aug 25 11:16:57 2012
LOGMINER: Begin mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_179_791922278.ARC
Sat Aug 25 11:16:57 2012
Completed: alter database start logical standby apply
LOGSTDBY Apply process P005 started with pid=29 OS id=460
Sat Aug 25 11:16:59 2012
LOGSTDBY stmt: REVOKE SYSDBA FROM VS
LOGSTDBY status: ORA-01031: insufficient privileges
LOGSTDBY id: XID 0x0006.007.00000208, hSCN 0x0000.0015acc3, lSCN 0x0000.0015acc3, Thread 1, RBA 0x00b3.000040cb.10, txnCscn 0x0000.0015acc6, PID 5064, ORACLE.EXE (P004)
LOGSTDBY Apply process P004 pid=28 OS id=5064 stopped
Sat Aug 25 11:16:59 2012
Errors in file d:\oracle\product\10.2.0\admin\stby\bdump\stby_lsp0_2576.trc:
ORA-12801: error signaled in parallel query server P004
ORA-01031: insufficient privileges
LOGSTDBY Apply process P005 pid=29 OS id=460 stopped
LOGSTDBY Apply process P006 pid=30 OS id=5448 stopped
LOGSTDBY Apply process P007 pid=33 OS id=5992 stopped
LOGSTDBY Apply process P008 pid=34 OS id=1164 stopped
LOGSTDBY Analyzer process P003 pid=27 OS id=5468 stopped
Sat Aug 25 11:17:04 2012
LOGSTDBY status: ORA-16222: automatic Logical Standby retry of last action
LOGSTDBY status: ORA-16111: log mining and apply setting up
Sat Aug 25 11:17:04 2012
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, builder process P001 started with pid=25 OS id=5584
LOGMINER: session# = 1, reader process P000 started with pid=24 OS id=5232
LOGMINER: session# = 1, preparer process P002 started with pid=26 OS id=5924
LOGSTDBY Analyzer process P003 started with pid=27 OS id=5468
LOGSTDBY Apply process P007 started with pid=33 OS id=5992
LOGSTDBY Apply process P005 started with pid=29 OS id=460
LOGSTDBY Apply process P008 started with pid=34 OS id=1164
LOGSTDBY Apply process P004 started with pid=28 OS id=5064
LOGSTDBY Apply process P006 started with pid=30 OS id=5448
Sat Aug 25 11:17:05 2012
LOGMINER: Begin mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_178_791922278.ARC
Sat Aug 25 11:17:05 2012
LOGMINER: Turning ON Log Auto Delete
Sat Aug 25 11:17:05 2012
LOGMINER: End mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_178_791922278.ARC
Sat Aug 25 11:17:05 2012
LOGMINER: Begin mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_179_791922278.ARC
Sat Aug 25 11:17:05 2012
LOGSTDBY stmt: REVOKE SYSDBA FROM VS
LOGSTDBY status: ORA-01031: insufficient privileges
LOGSTDBY id: XID 0x0006.007.00000208, hSCN 0x0000.0015acc3, lSCN 0x0000.0015acc3, Thread 1, RBA 0x00b3.000040cb.10, txnCscn 0x0000.0015acc6, PID 5064, ORACLE.EXE (P004)
LOGSTDBY Apply process P004 pid=28 OS id=5064 stopped
Sat Aug 25 11:17:05 2012
Errors in file d:\oracle\product\10.2.0\admin\stby\bdump\stby_lsp0_2576.trc:
ORA-12801: error signaled in parallel query server P004
ORA-01031: insufficient privileges
LOGSTDBY Apply process P006 pid=30 OS id=5448 stopped
LOGSTDBY Apply process P005 pid=29 OS id=460 stopped
LOGSTDBY Apply process P008 pid=34 OS id=1164 stopped
LOGSTDBY Apply process P007 pid=33 OS id=5992 stopped
LOGSTDBY Analyzer process P003 pid=27 OS id=5468 stopped
Sat Aug 25 12:05:20 2012
RFS[2]: Possible network disconnect with primary database
Closing latent archivelog for thread 1 sequence 183
EOF located at block 7520 low SCN 0:1489453 next SCN 0:1492554
Latent archivelog 'D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_183_791922278.ARC'
If you wish to failover to this standby database, you should use the
following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGICAL LOGFILE 'D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_183_791922278.ARC';
Sat Aug 25 12:18:09 2012
ALTER DATABASE START LOGICAL STANDBY APPLY
Sat Aug 25 12:18:09 2012
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=21, OS id=6020
LOGSTDBY status: ORA-16111: log mining and apply setting up
Sat Aug 25 12:18:09 2012
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, builder process P001 started with pid=23 OS id=5464
LOGMINER: session# = 1, preparer process P002 started with pid=24 OS id=3428
LOGMINER: session# = 1, reader process P000 started with pid=22 OS id=3204
Sat Aug 25 12:18:09 2012
LOGMINER: Begin mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_178_791922278.ARC
Sat Aug 25 12:18:09 2012
LOGMINER: Turning ON Log Auto Delete
Sat Aug 25 12:18:09 2012
LOGMINER: End mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_178_791922278.ARC
LOGSTDBY Analyzer process P003 started with pid=25 OS id=6016
LOGSTDBY Apply process P004 started with pid=26 OS id=5184
LOGSTDBY Apply process P005 started with pid=27 OS id=3572
LOGSTDBY Apply process P007 started with pid=29 OS id=4764
Sat Aug 25 12:18:09 2012
LOGMINER: Begin mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_179_791922278.ARC
LOGSTDBY Apply process P008 started with pid=30 OS id=2576
Sat Aug 25 12:18:09 2012
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY
LOGSTDBY Apply process P006 started with pid=28 OS id=4188
Sat Aug 25 12:18:11 2012
LOGSTDBY stmt: REVOKE SYSDBA FROM VS
LOGSTDBY status: ORA-01031: insufficient privileges
LOGSTDBY id: XID 0x0006.007.00000208, hSCN 0x0000.0015acc3, lSCN 0x0000.0015acc3, Thread 1, RBA 0x00b3.000040cb.10, txnCscn 0x0000.0015acc6, PID 5184, ORACLE.EXE (P004)
LOGSTDBY Apply process P004 pid=26 OS id=5184 stopped
Sat Aug 25 12:18:11 2012
Errors in file d:\oracle\product\10.2.0\admin\stby\bdump\stby_lsp0_6020.trc:
ORA-12801: error signaled in parallel query server P004
ORA-01031: insufficient privileges
LOGSTDBY Apply process P005 pid=27 OS id=3572 stopped
LOGSTDBY Apply process P006 pid=28 OS id=4188 stopped
LOGSTDBY Apply process P008 pid=30 OS id=2576 stopped
LOGSTDBY Apply process P007 pid=29 OS id=4764 stopped
LOGSTDBY Analyzer process P003 pid=25 OS id=6016 stopped
Sat Aug 25 12:18:16 2012
LOGSTDBY status: ORA-16222: automatic Logical Standby retry of last action
LOGSTDBY status: ORA-16111: log mining and apply setting up
Sat Aug 25 12:18:16 2012
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, preparer process P002 started with pid=24 OS id=3428
LOGMINER: session# = 1, reader process P000 started with pid=22 OS id=3204
LOGMINER: session# = 1, builder process P001 started with pid=23 OS id=5464
LOGSTDBY Analyzer process P003 started with pid=25 OS id=6016
LOGSTDBY Apply process P006 started with pid=28 OS id=4188
LOGSTDBY Apply process P005 started with pid=27 OS id=3572
LOGSTDBY Apply process P004 started with pid=26 OS id=5184
LOGSTDBY Apply process P007 started with pid=29 OS id=4764
LOGSTDBY Apply process P008 started with pid=30 OS id=2576
Sat Aug 25 12:18:17 2012
LOGMINER: Begin mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_178_791922278.ARC
Sat Aug 25 12:18:17 2012
LOGMINER: Turning ON Log Auto Delete
Sat Aug 25 12:18:17 2012
LOGMINER: End mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_178_791922278.ARC
Sat Aug 25 12:18:17 2012
LOGMINER: Begin mining logfile: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\STBY\ARCHIVELOG\STANDBYARCH_1_179_791922278.ARC
Sat Aug 25 12:18:17 2012
LOGSTDBY stmt: REVOKE SYSDBA FROM VS
LOGSTDBY status: ORA-01031: insufficient privileges
LOGSTDBY id: XID 0x0006.007.00000208, hSCN 0x0000.0015acc3, lSCN 0x0000.0015acc3, Thread 1, RBA 0x00b3.000040cb.10, txnCscn 0x0000.0015acc6, PID 5184, ORACLE.EXE (P004)
LOGSTDBY Apply process P004 pid=26 OS id=5184 stopped
Sat Aug 25 12:18:17 2012
Errors in file d:\oracle\product\10.2.0\admin\stby\bdump\stby_lsp0_6020.trc:
ORA-12801: error signaled in parallel query server P004
ORA-01031: insufficient privileges
LOGSTDBY Apply process P005 pid=27 OS id=3572 stopped
LOGSTDBY Apply process P008 pid=30 OS id=2576 stopped
LOGSTDBY Apply process P006 pid=28 OS id=4188 stopped
LOGSTDBY Apply process P007 pid=29 OS id=4764 stopped
LOGSTDBY Analyzer process P003 pid=25 OS id=6016 stopped
Kindly Help me out.
Edited by: Nisarg Upadhyay on Aug 28, 2012 4:23 AM

Sorry for replying late,
No, its not giving any error in alert.log.
select type,status from v$logstdby_process query shows following output
type status
COORDINATOR     ORA-16116: no work available
READER             ORA-16240: Waiting for logfile (thread# 1, sequence# 343)
BUILDER     ORA-16116: no work available
PREPARER     ORA-16116: no work available
ANALYZER     ORA-16116: no work available
APPLIER     ORA-16116: no work available
APPLIER     ORA-16116: no work available
APPLIER     ORA-16116: no work available
APPLIER     ORA-16116: no work available
APPLIER     ORA-16116: no work available
Note.
When logical standby was in working condition status of READER process was no work available**
Thanks

Checkpoint interval

Similar Messages

Maybe you are looking for