Few errror/doubts in Primary and Standby server - Need Help

Question

Hi All,
I am having below doubts/errors. I need help to solve all the below questions.
I configured Dataguard successfully. Now the sync is upto date using the below parameters (using 11g):
at primary:
log_archive_dest_1=
log_archive_dest_2='SERVICE=standby.123 arch'
standby_file_management=auto
at sandby:
log_archive_dest_1=
standby_file_management=auto
Still i face below messages in the alertliog. Can anybody clearly explain me all the points.
Primary:
ORA-1652: unable to extend temp segment by 640 in tablespace NEWTEMP
I get this error when my archvie destination got filled up, later we released the enough space, the archived are generating. Still i see this message once in between. Need to solve this.
Primary:
Checkpoint not complete ( i see this message very often, want to get rid of this)
standby:
kcrrvslf: active RFS archival for log thread 1 sequence (sometimes i see this KCRRVSLF)
standby:
check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large enough to maintain afequate log switch information to resolve archivelog gaps. (also get this message in between the alertlog file in standby)
Standby:
FAL[client]: Error fetching gap sequence, no FAL server specified (this is very often message. How to remove this, what needs to be added. Do i need to add the below parameters)
FAL_CLIENT
FAL_SERVER
Thanks in advance.
Pas Moh
[email protected]

Answer 1

Pas Moh wrote:
Hi All,
I am having below doubts/errors. I need help to solve all the below questions.
I configured Dataguard successfully. Now the sync is upto date using the below parameters (using 11g):
at primary:
log_archive_dest_1=
log_archive_dest_2='SERVICE=standby.123 arch'
standby_file_management=auto
at sandby:
log_archive_dest_1=
standby_file_management=auto
Still i face below messages in the alertliog. Can anybody clearly explain me all the points.
Primary:
ORA-1652: unable to extend temp segment by 640 in tablespace NEWTEMP
I get this error when my archvie destination got filled up, later we released the enough space, the archived are generating. Still i see this message once in between. Need to solve this.This error has absolutely nothing to do with the handling of archive logs, the status of archivelog destination, or primary/standby. Any relation you thought you saw was pure coincidence.
>
>
Primary:
Checkpoint not complete ( i see this message very often, want to get rid of this)
Here is the very first hit I got when I googled "oracle checkpoint not complete". Tom says it better than I would have.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:69012348056
standby:
kcrrvslf: active RFS archival for log thread 1 sequence (sometimes i see this KCRRVSLF)
A quick google of that one, and it looks like it is not even an error, but rather simply an informative
>
standby:
check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large enough to maintain afequate log switch information to resolve archivelog gaps. (also get this message in between the alertlog file in standby)
In that case I would check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large enough to maintain adequate log switch information to resolve archivelog gaps.
How big is that? Well, at least bigger than it is now. Beyond that, it would have to be "large enough to maintain adequate log switch information to resolve archivelog gaps" Just play with it until you get the result you want.
>
Standby:
FAL[client]: Error fetching gap sequence, no FAL server specified (this is very often message. How to remove this, what needs to be added. Do i need to add the below parameters)
FAL_CLIENT
FAL_SERVER
Thanks in advance.
Pas Moh
[email protected]