Livecache - Redo log management activation query
Hi,
A livecache system is in use with redo management deactivated status over one month.
Now planning to activate it and ON the LOG WRITING
what is the best procedure can be followed. if I activate them now , can the livecache/maxdb data get affected?
I would like to get clarified these doubts. Please guide and provide your inputs
Thanks in advance
Hello,
the liveCache/Maxdb data will be not affected after you will activate the log writing.
Please review the SAP note 869267 - FAQ: SAP MaxDB Log area:
Starting the log writer:
Set
the database to the operational state ADMIN. Execute the following DBM
command:
util_execute SET LOG WRITER ON
Create a complete data
backup in the ADMIN or ONLINE operation status."
After the databackup will be created, activate the auto-save logbackup. Manage the logbackup archiving, see SAP note 1377148 - FAQ: SAP MaxDB backup / recovery < 10. & 11. >
Regards, Natalia Khlopina
Similar Messages
-
When occurs crash recovery,why use active online redo log not archived log?
If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
Quote:
Re: v$log : How redo log file can have a status ACTIVE and be already archived?
Hemant K Chitale
If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
TanelPoder
Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).Aman.... wrote:
John,
Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
Regards
Aman....
That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
Sorry I wasted your time, I'll try to be less ambiguous in future -
Can we have more than more than one Redo Log with Active status.
Or Oracle always completes earlier check point before going to perform another check point. ( Error - Can not check point).Can we have more than more than one Redo Log with Active status.
Or Oracle always completes earlier check point before going to perform another check point. ( Error - Can not check point). -
All Redo Log groups are active.
Hi All,
In one of our production database now a days we are seeing that all redo logs become active and then everything just get hang. It happens for 15-20 minutes and after that they come normal. Database size is over 4.5 TB and it's OLTP cum MIS database. As per Unix Team at server and storage level everything is fine so what could be other reason for this?
Database version is 9.2.0.5 and O/S is AIX 5.3 Power System.
select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIME
1 1 435847 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
2 1 435848 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
3 1 435850 1,342,177,280 2 NO CURRENT 1.1782E+13 13-MAR-10
4 1 435844 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
5 1 435845 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
6 1 435846 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
7 1 435843 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
8 1 435849 1,342,177,280 2 YES ACTIVE 1.1782E+13 13-MAR-10
9 1 435842 1,342,177,280 2 YES INACTIVE 1.1782E+13 13-MAR-10
9 rows selected.
VMSTAT output:
vmstat 2 10
kthr memory page faults cpu
r b avm fre re pi po fr sr cy in sy cs us sy id wa
35 13 23262385 48530 0 0 0 0 0 0 27910 531516 111964 54 7 12 26
30 12 23270696 26769 0 0 0 4277 19644 0 28759 604423 106619 53 7 14 25
26 12 23269357 25691 0 0 0 8899 38750 0 28620 552550 103736 55 7 15 23
32 14 23263410 31111 0 0 0 10778 47248 0 29722 690889 112674 53 7 16 24
27 17 23268835 25011 0 0 0 10267 51727 0 30321 779933 116936 58 8 13 21
30 20 23274592 25181 0 0 0 13569 59742 0 28290 731707 109167 59 7 13 22
33 10 23280476 30823 0 0 0 15259 66334 0 28942 774600 107692 65 7 8 20
36 13 23280770 26040 0 0 0 7199 33048 0 29351 687375 98487 63 7 10 20
35 16 23277780 27758 0 0 0 7250 33003 0 30699 622788 97172 65 6 10 19
31 13 23277431 25107 0 0 0 8521 37996 0 29746 596172 89831 63 6 11 20
select event, count(*) from v$session_wait group by event order by 2;
EVENT COUNT(*)
PL/SQL lock timer 2
SQL*Net more data from client 2
jobq slave wait 3
direct path read 5
rdbms ipc message 8
enqueue 11
log file sync 11
db file parallel write 12
latch free 12
pipe get 22
PX Deq: Execution Msg 27
buffer busy waits 33
db file scattered read 39
db file sequential read 169
SQL*Net message from client 2120Hi,
Complete output would be so long so just putting tail of that.
RECID STAMP
NAME
DEST_ID THREAD# SEQUENCE# RESETLOGS_CHANGE# RESETLOGS_TIME FIRST_CHANGE# FIRST_TIME NEXT_CHANGE# NEXT_TIME BLOCKS BLOCK_SIZE CREATOR REGISTR STA ARC APP DEL S COMPLETION_TIME
DIC DIC END BACKUP_COUNT ARCHIVAL_THREAD# ACTIVATION#
711558 713531894
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435868 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711559 713531942
/arch/ora/prod/PRODDB_1_00135869.arc
1 1 435869 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711560 713531994
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435869 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711561 713532090
/arch/ora/prod/PRODDB_1_00135870.arc
1 1 435870 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711562 713532149
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435870 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711563 713532276
/arch/ora/prod/PRODDB_1_00135871.arc
1 1 435871 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711564 713532322
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435871 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711565 713532449
/arch/ora/prod/PRODDB_1_00135872.arc
1 1 435872 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711566 713532506
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435872 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711567 713532607
/arch/ora/prod/PRODDB_1_00135873.arc
1 1 435873 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711568 713532662
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435873 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711569 713532773
/arch/ora/prod/PRODDB_1_00135874.arc
1 1 435874 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711570 713532832
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435874 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711571 713532933
/arch/ora/prod/PRODDB_1_00135875.arc
1 1 435875 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711572 713532980
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435875 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711573 713533101
/arch/ora/prod/PRODDB_1_00135876.arc
1 1 435876 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711574 713533178
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435876 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711575 713533258
/arch/ora/prod/PRODDB_1_00135877.arc
1 1 435877 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711576 713533323
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435877 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711577 713533366
/arch/ora/prod/PRODDB_1_00135878.arc
1 1 435878 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711578 713533419
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435878 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES YES NO A 13-MAR-10
NO NO NO 0 1 2142322718
711579 713533497
/arch/ora/prod/PRODDB_1_00135879.arc
1 1 435879 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711580 713533537
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435879 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711581 713533678
/arch/ora/prod/PRODDB_1_00135880.arc
1 1 435880 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711582 713533737
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435880 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711583 713533841
/arch/ora/prod/PRODDB_1_00135881.arc
1 1 435881 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711584 713533919
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435881 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711585 713533983
/arch/ora/prod/PRODDB_1_00135882.arc
1 1 435882 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH NO YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718
711586 713534050
(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=ilerpstdby)(PORT=1540)))(CONNECT_DATA=(SID=ILPROD)(SERVER=DEDICATED)))
2 1 435882 8.6960E+12 24-SEP-03 1.1782E+13 13-MAR-10 1.1782E+13 13-MAR-10 2621438 512 ARCH ARCH YES YES NO NO A 13-MAR-10
NO NO NO 0 1 2142322718 -
Nightmare with Log Writer, active files please explain !
Hi
Can anybody explain how many redo log groups server may need in no-archiving mode ?
The documentation from Oracle web site says:
If you have enabled archiving, Oracle cannot re-use or overwrite an active online log file until ARCn has archived its contents. If archiving is disabled, when the last online redo log file fills, writing continues by overwriting the first available active file.
From this it looks only 2 groups are needed. I dont get how is it possible to overwrite active file ??? I think I should be written by dbw and become inactive first. Is that the reason I get "checkpoint has not completed" warnings in the log and pure performance ?
AndriusI believe the minimum required by oracle is 2 groups.
Obviously, this won't cut it in ARCHIVELOG mode for most databases. But then, you were referring to NOARCHIVELOG mode. I tend to go with 3 in this type of scenario.
As for the 2nd part. Only one redo log is 'ACTIVE' at a time. When a log switch occurs, it goes to the next INACTIVE redo log and starts writing to that. Thus, overwriting what was previously in it. DBWn doesn't write redo entries, that is handled by LGWR. As far as Oracle8i, the only part DBWn had on redo logs was triggering log writting by LGWR. -
환경 : 8.1.7.3.0 (no archive log 모드)
log_checkpoint_timeout = 0
log_checkpoint_interval = 999999999
redo log size = 200M
현재 check point는 log switch 상태에서만 가능하도록 설정된 것 같습니다.
거래량이 적어서 그런지 log switch는 30시간 주기입니다.
제가 실행한 것은 아래 4번째 로그가 current일때
alter system checkpoint를 하고 조금 있다가..
alter system switch logfile를 하여 1번째가 current가 된 상황입니다.
3/16일 14시 까지도 계속 active상태입니다...
1. 문제가 생긴건지요??? 도움부탁합니다...
2. no archive log mode에서도 switch 주기를 줄이는 것이 복구에 도움이 되나요...?
===========================================
STATUS , FIRST_CHANGE#,FIRST_TIME
CURRENT , 8846777646687,2007-03-15 16:57:55
INACTIVE, 8846777587798,2007-03-14 10:34:40
INACTIVE, 8846777609448,2007-03-14 17:17:38
ACTIVE , 8846777643690,2007-03-15 16:01:22no archivemode에서 정상복구를 바라는 것인지요?
잘못된 정책이란 생각이 듭니다.
no archive mode에서 v$log의 first_change# 중에 가장 작은 것
이 v$recover_file의 change# 보다 크거나 같다면 복구불능입니다.
배치작업이라도 있어서 log switch가 한번의 cycle을 돌게 되면 이전
백업으로는 복구불능입니다. archive mode로 지금 바로 바꾸시지요..
log_checkpoint_timeout은 checkpoint에 대한 timeout 시간값을
지정하는 것입니다.
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.
checkpoint는 아시는 바와 같이 데이터파일과
리두로그 컨트롤파일의 SCN을 일치시키는 것입니다. 주요한 것은
DBWR프로세스가 데이터파일에 write를 하겠구요.
물론 checkpoint와 인스턴스 복구는 관련이 있습니다. checkpoint timeout을
적당히주면 instance recovery에서 좀 더 빠르게 instance 복구후 DB가
open되겠습니다. 만약 설정하신대로 하신다면 DB를 abort로
내리고 open하게 되면
instance recovery시에 더 많은 시간이 필요하겠습니다.
게다가 트랜잭션으로 인한 log switch하는 시간이 30시간보다
작다면 timeout을 준들 영향을 주지 않겠지요. redo log가 꽉
차게 되면 log switch를 자동으로 하게 되는데 log switch를
하기전에 checkpoint를 주게 되어 있으니까요.
그런데 checkpoint와 물리적/논리적 복구와는 다른 개념입니다.
checkpoint는 위에서 말씀드린 instance recovery와 관련이 있고
물리적/논리적 복구에서는 archive file이 떨어져 있는가 current redo log가
존재하는가에 따라서 복구가능여부를 결정되는 것이지요..
그리고 ACTIVE 상태라는 것은 문서상의 정의에서는 archive mode일 경우
archiving이 되는 중일 경우, 그리고 이 상태는 complete recovery시에 redo log
적용시 필요한 정보가 있다는 것입니다.
no archive mode에서 복구정책을 적용 하겠다는 것은 위험한 발상인 것 같습니다.
물론 DSS시스템의 경우에는 이미 정책을 no archive mode로
만들어두고 주말마다 offline backup을 하기도 합니다.
하지만 DSS에서는 하루에 300번 이상의 log switch가 일어나는
경우가 있을 정도이니 아무리 백업이 되어 있다 한들 완전복구는
불능이겠지요. offline backup을 했을 때까지만 복구가 됩니다.
$LOG
This view contains log file information from the control files.
Column Datatype Description
GROUP#
NUMBER
Log group number
THREAD#
NUMBER
Log thread number
SEQUENCE#
NUMBER
Log sequence number
BYTES
NUMBER
Size of the log (in bytes)
MEMBERS
NUMBER
Number of members in the log group
ARCHIVED
VARCHAR2(3)
Archive status (YES |NO)
STATUS
VARCHAR2(16)
Log status:
UNUSED - Online redo log has never been written to. This is the state of a redo log that was just added, or just after a RESETLOGS, when it is not the current redo log.
CURRENT - Current redo log. This implies that the redo log is active. The redo log could be open or closed.
ACTIVE - Log is active but is not the current log. It is needed for crash recovery. It may be in use for block recovery. It might or might not be archived.
CLEARING - Log is being re-created as an empty log after an ALTER DATABASE CLEAR LOGFILE statement. After the log is cleared, the status changes to UNUSED.
CLEARING_CURRENT - Current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch such as an I/O error writing the new log header.
INACTIVE - Log is no longer needed for instance recovery. It may be in use for media recovery. It might or might not be archived.
no archive mode에서도 복구하는 여러가지 방법들이 있기는 합니다.
예를들어 current redo log가 깨졌을 때에 recovery 방법이라던지
등등이 문서에 있긴하지요. 하지만 no archivemode에서 백업을 붓고
복구하는 방법은 찾아보기 힘드실 것입니다. 위에서도 말씀드렸듯이
no archive mode에서
v$recover_file의 CHANGE# > v$logl의 minimum FIRST_CHANGE# 이면 데이터파일은 복구가능합니다.
그러나 CHANGE# <= minimum FIRST_CHANGE# 이면 복구 불가능합니
다. 그러니 백업을 붓고 복구를 하는 방법에 대한 문서는 거의
찾기 힘듭니다. advance 방법에 대한 문서에서만 adjust_scn을 쓴다던지 하는 등이 나와있을 뿐입니다.
글 수정:
민천사(민연홍)
아무래도 졸면서 썼나봅니다.;;
interval과 timeout은 엄연히 다른데요. 왜 timeout과 interval을
혼동했는지..;;
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.
LOG_CHECKPOINT_TIMEOUT specifies (in seconds) the amount of time that has passed since the incremental checkpoint at the position where the last write to the redo log (sometimes called the tail of the log) occurred. This parameter also signifies that no buffer will remain dirty (in the cache) for more than integer seconds. -
How to know the delay in redo log apply on Active Dataguard 11g
Hello All,
How to know the delay in redo log apply on Active Dataguard 11g...
Do we need to wait till log switch occurs?
Or is it recommended to schedule a log switch every 15 min, no matter data is updated/inserted or not in primary?
Please suggest...
Oracle : oracle 11g Release 2
OS : RHEL 5.4
Thanks
Edited by: user1687821 on Feb 23, 2012 12:02 AMHello CKPT,
Thank you for the valuable information...
We have not configured databroker.
Output of the query
SELECT * FROM (
SELECT sequence#, archived, applied,
TO_CHAR(completion_time, 'RRRR/MM/DD HH24:MI') AS completed
FROM sys.v$archived_log
ORDER BY sequence# DESC)
WHERE ROWNUM <= 10
Primary...
SEQUENCE# ARCHIVED APPLIED COMPLETED
29680 YES YES 2012/02/23 01:11
29680 YES NO 2012/02/23 01:11
29679 YES NO 2012/02/22 23:11
29679 YES YES 2012/02/22 23:11
29678 YES YES 2012/02/22 23:11
29678 YES NO 2012/02/22 23:11
29677 YES YES 2012/02/22 22:32
29677 YES NO 2012/02/22 22:32
29676 YES YES 2012/02/22 22:02
29676 YES NO 2012/02/22 22:02
Standby...
SEQUENCE# ARC APP COMPLETED
29680 YES YES 2012/02/23 01:11
29679 YES YES 2012/02/22 23:11
29678 YES YES 2012/02/22 23:11
29677 YES YES 2012/02/22 22:32
29676 YES YES 2012/02/22 22:02
29675 YES YES 2012/02/22 21:24
29674 YES YES 2012/02/22 19:24
29673 YES YES 2012/02/22 18:59
29672 YES YES 2012/02/22 17:42
29671 YES YES 2012/02/22 17:41
Primary shows yes as well as no...
Next,
From primary:-
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
THREAD# MAX(SEQUENCE#)
1 29680
From standby:-
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
THREAD# MAX(SEQUENCE#)
1 29680
What is the redo transport service you are using? is it LGWR or ARCH ?
Output of query select * from v$parameter where name like 'log_archive_dest_2' shows below value...
SERVICE=b_stdb LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=b_stdb
So is it lgwr already configured...? if yes then how do i see the delay in both servers..
Yes, the network is good as they both resides in same LAN within same rack
Thanks... -
Open database if an active online redo log is missing
Hi,
Sorry for the rather long post, but I specified all the steps I performed and couldn't make it shorter :-(
I need an advice on how to open the database if an active online redo log is missing.
For test purposes I intentionally performed a shutdown abort when the redo log group 1 was in active state and then renamed its only member (REDO01.LOG) so that the database couldn't perform crash recovery using it. Then upon startup I obviously got the message:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.Ok, so I checked the state of the logs:
{noformat}
SQL>SELECT a.GROUP#, first_change#, SEQUENCE#, a.status, SUBSTR(b.MEMBER, 1, 40) MEMBER, b.status mem_status, a.archived
2 FROM v$log a, v$logfile b
3 WHERE a.GROUP# = b.GROUP#
4 ORDER BY a.GROUP#, b.MEMBER;
GROUP# FIRST_CHANGE# SEQUENCE# STATUS MEMBER MEM_STA ARC
1 592134 29 ACTIVE H:\ORADATA\TESTDB\REDO01.LOG YES
2 592268 30 CURRENT C:\ORADATA\TESTDB\REDO02.LOG NO
3 592129 28 ACTIVE C:\ORADATA\TESTDB\REDO03.LOG YES
{noformat}Since opening the database to perform a log switch and thus change the status of the redo log group 1 from ACTIVE to INACTIVE to recreate the member isn't possible, I performed database recovery.
SQL>recover database until cancel;
ORA-00279: change 592129 generated at 02/04/2009 10:31:15 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_%U_.ARC
ORA-00280: change 592129 for thread 1 is in sequence #28
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 592134 generated at 02/04/2009 10:31:28 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_%U_.ARC
ORA-00280: change 592134 for thread 1 is in sequence #29
ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_4RLR3JS9_.ARC' no longer needed for this rec
overy
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC'
ORA-00279: change 592268 generated at 02/04/2009 10:32:03 needed for thread 1
ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_30_%U_.ARC
ORA-00280: change 592268 for thread 1 is in sequence #30
ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC' no longer needed for this rec
overy
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'C:\ORADATA\TESTDB\REDO02.LOG'
Log applied.
Media recovery complete.
SQL>So for log sequence #28 I accepted the proposed archived redo log in the FRA, for sequence #29 (that's the online redo log that is missing!) I manually specified its archived copy, and for sequence #30 I specified the CURRENT online redo log. And as it seems the media recovery was successful.
Next I tried to open the database but again got the error:
SQL>alter database open noresetlogs;
alter database open noresetlogs
ERROR at line 1:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
The status of the log groups and its members is exactly as it was in the first query I wrote above, i.e. the redo log group 1 is still ACTIVE, so it's needed for crash recovery (which I had already done manually if I understand correctly how Oracle works!). I also checked if the datafiles are inconsistent (described in metalink doc id 1015544.102):
SQL>SELECT DISTINCT CHECKPOINT_CHANGE#, FUZZY FROM V$DATAFILE_HEADER;
CHECKPOINT_CHANGE# FUZ
592269 NOSo, everything seems ok as far as datafile consistency is concerned.
My question is: how can I rename/drop/clear/whatever the member of redo log group 1 to open the database?
I tried to rename the log file member, to add another member to it, to open the database with resetlogs, to clear the logfile group 1, but all without success:
1)
SQL>alter database clear logfile group 1;
alter database clear logfile group 1
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of instance testdb (thread 1)
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
2)
SQL>alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
3)
SQL>alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG';
alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG'
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01512: error renaming log file H:\ORADATA\TESTDB\REDO01.LOG - new file C:\ORADATA\TESTDB\REDO01.LOG not found
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
4)
SQL>alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1;
alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1
ERROR at line 1:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.Sorry again for the long post and thank you in advance for any suggestion.
Regards,
JureYou could check if the recovery was complete by (re)creating the controlfile with the resetlogs option.
<CREATE CONTROLFILE REUSE DATABASE define_db_name RESETLOGS NOARCHIVELOG
...>Thanks for the hint. If possible, could you only check if the steps I'm going to perform are ok.
I did an "alter database backup controlfile to trace;" and then extracted the create controlfile definition part. So in essence I should run the following statements:
CREATE CONTROLFILE REUSE DATABASE "TESTDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 'C:\ORADATA\TESTDB\REDO01.LOG' SIZE 20M,
GROUP 2 'C:\ORADATA\TESTDB\REDO02.LOG' SIZE 20M,
GROUP 3 'C:\ORADATA\TESTDB\REDO03.LOG' SIZE 20M
-- STANDBY LOGFILE
DATAFILE
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF'
CHARACTER SET EE8MSWIN1250
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\TEMP01.DBF' REUSE;Is that correct?
About the RMAN backups: Wouldn't a 'CATALOG RECOVERY AREA' populate the controlfile with backup information again (I'm not using a recovery catalog in this case)?
Thanks for the help!
Regards,
Jure -
Question about how Oracle manages Redo Log Files
Good morning,
Assuming a configuration that consists of 2 redo log groups (Group A and B), each group consisting of 2 disks (Disks A1 & A2 for Group A and Disks B1 and B2 for group B). Further, let's assume that each redo log file resides by itself in a disk storage device and that the device is dedicated to it. Therefore in the above scenario, there are 4 disks, one for each redo log file and, each disk contains nothing else other than a redo log file. Furthermore, let's assume that the database is in ARCHIVELOG mode and that the archive files are stored on yet another different set of devices.
sort of graphically:
GROUP A GROUP B
A1 B1
A2 B2The question is: When the disks that comprise Group A are filled and Oracle switches to the disks in Group B, can the disks in Group A be taken offline, maybe even physically removed from the system if necessary, without affecting the proper operation of the database ? Can the Archiver process be temporarily delayed until the disks (that were removed) are brought back online or is the DBA forced to wait until the Archiver process has finished creating a copy of the redo log file into the archive ?
Thank you for your help,
John.Hello,
Dropping Log Groups
To drop an online redo log group, you must have the ALTER DATABASE system privilege. Before dropping an online redo log group, consider the following restrictions and precautions:
* An instance requires at least two groups of online redo log files, regardless of the number of members in the groups. (A group is one or more members.)
* You can drop an online redo log group only if it is inactive. If you need to drop the current group, first force a log switch to occur.
* Make sure an online redo log group is archived (if archiving is enabled) before dropping it. To see whether this has happened, use the V$LOG view.
SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
GROUP# ARC STATUS
1 YES ACTIVE
2 NO CURRENT
3 YES INACTIVE
4 YES INACTIVE
Drop an online redo log group with the SQL statement ALTER DATABASE with the DROP LOGFILE clause.
The following statement drops redo log group number 3:
ALTER DATABASE DROP LOGFILE GROUP 3;
When an online redo log group is dropped from the database, and you are not using the Oracle Managed Files feature, the operating system files are not deleted from disk. Rather, the control files of the associated database are updated to drop the members of the group from the database structure. After dropping an online redo log group, make sure that the drop completed successfully, and then use the appropriate operating system command to delete the dropped online redo log files.
When using Oracle-managed files, the cleanup of operating systems files is done automatically for you.
Your Database wont be affected as you can operate with 2 redo log files in each group as The minimum number of redo log files required in a database is two because the LGWR (log writer) process writes to the redo log files in a circular manner. so the process will hang becuase you are having 2 only groups if you want to remove 1 add a third one and make it the current group then remove the one you want to be offline.
Please refer to:
http://download.oracle.com/docs/cd/B10500_01/server.920/a96521/onlineredo.htm#7438
Kind regards
Mohamed
Oracle DBA -
Archive all the active online redo logs
Hi,
in 9.2.0 and in archivelog mode, how can I archive all the active online redo logs ?
Thank you.Is ur database already running in archivelog mode?? If yes and if automatic archiving is enabled then ur redo will be archived automatically. I think first you need to check whether ur DB is in archive log mode or not?? Post the output of (from sqlplus):
archive log list
Daljit Singh -
Hello dear gurus!
After shutting database with option "abort"
we have unconsisten state of datafiles.
I ask to explain :
1) - does the ARCH background processes flash whole redo buffer into redolog ?
(In other words how reached consistency if all redo log groups was in active state before shutting down ?)
2) Where buffer contents in this case are dumped ?
Thanks and best regards,
Pavel
Edited by: Pavel on Jul 19, 2012 9:49 PMPavel wrote:
Hello dear gurus!
After shutting database with option "abort"
we have unconsisten state of datafiles.That's expected as checkpoint didn't happen. Issue a startup and instance recovery should take care of everything.
I ask to explain :
1) - does the ARCH background processes flash whole redo buffer into redolog ?ARCH process or LGWR? How does this relates to your current question?
(In other words how reached consistency if all redo log groups was in active state before shutting down ?)As I said, issue a startup of the instance and it should take care of the things.
2) Where buffer contents in this case are dumped ?Which case? Your questions are a bit fuzzy you see. Let's stick to one question at one time and follow it shall we?
Aman.... -
10G redo log switchs with no activity
We have been testing 8i to 10G migrations and two things I have noticed that are different bwteeen the 2 databases are:
1) redo log switching occurring even though the database has no users and just sitting there. This is not happeniong in our 8i databases.
2) trace files of format instance_m001_ and instance_m000_ in ../bdump. Our 8i bdump's normally do not have trc files unless a problem occurs.
Is it normal for 10G to automatically switch redo logs with no activity and are these .trc files also normal? In general I get nervous with trc files. -quinnStill haven't figured out the redo log switches, they seem to be slowing down, but the excess trace files are apparently cuased by a bug and can be fixed with Patch 3432729.
-
DB version:11.2
Platform : Solaris 10
We create RAC DBs manually. Below is a log of the DB creation from Node1 . Instance in Node2 is not yet created (only binary is installed in Node2).
SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup nomount pfile=/u03/oracle/11.2/db_1/dbs/initnehprd1.ora
ORACLE instance started.
Total System Global Area 1252643278 bytes
Fixed Size 2219208 bytes
Variable Size 771752760 bytes
Database Buffers 469762048 bytes
Redo Buffers 8929280 bytes
SQL> CREATE DATABASE nehprd MAXINSTANCES 8 MAXLOGFILES 16 MAXLOGMEMBERS 4 MAXDATAFILES 1024
2 CHARACTER SET AL32UTF8 NATIONAL CHARACTER SET AL16UTF16
3 DATAFILE '+DG_DATA01/nehprd/nehprd_system01.dbf' SIZE 1000m EXTENT MANAGEMENT LOCAL
4 SYSAUX DATAFILE '+DG_DATA01/nehprd/nehprd_sysaux01.dbf' SIZE 600m
5 DEFAULT TEMPORARY TABLESPACE temp
6 TEMPFILE '+DG_DATA01/nehprd/nehprd_temp01.dbf' SIZE 2000m EXTENT MANAGEMENT LOCAL UNIFORM SIZE 5m
7 UNDO TABLESPACE undotbs11 DATAFILE '+DG_DATA01/nehprd/nehprd_undotbs1101.dbf' SIZE 700m
8 LOGFILE
9 GROUP 1 ('+DG_DATA01/nehprd/nehprd_log01.dbf') SIZE 150m,
10 GROUP 2 ('+DG_DATA01/nehprd/nehprd_log02.dbf') SIZE 150m,
11 GROUP 3 ('+DG_DATA01/nehprd/nehprd_log03.dbf') SIZE 150m
12 /
Database created.
Elapsed: 00:00:18.95
SQL> CREATE UNDO TABLESPACE undotbs12 DATAFILE '+DG_DATA01/nehprd/nehprd_undotbs1201.dbf' SIZE 700m;
Tablespace created.
Elapsed: 00:00:01.30
SQL> ALTER DATABASE ADD LOGFILE thread 2 GROUP 4 '+DG_DATA01/nehprd/nehprd_log04.dbf' SIZE 150m;
Database altered.
Elapsed: 00:00:00.25
SQL> ALTER DATABASE ADD LOGFILE thread 2 GROUP 5 '+DG_DATA01/nehprd/nehprd_log05.dbf' SIZE 150m;
Database altered.
Elapsed: 00:00:00.43
SQL> ALTER DATABASE ADD LOGFILE thread 2 GROUP 6 '+DG_DATA01/nehprd/nehprd_log06.dbf' SIZE 150m;
Database altered.But after the above activity, the following log files are created in the DB.
6 log groups for each Instance and they all are on the same location +DG_DATA01/nehprd !
INST_ID GROUP# STATUS TYPE MEMBER IS_
1 1 ONLINE +DG_DATA01/nehprd/nehprd_log01.dbf NO
1 2 ONLINE +DG_DATA01/nehprd/nehprd_log02.dbf NO
1 3 ONLINE +DG_DATA01/nehprd/nehprd_log03.dbf NO
1 4 ONLINE +DG_DATA01/nehprd/nehprd_log04.dbf NO
1 5 ONLINE +DG_DATA01/nehprd/nehprd_log05.dbf NO
1 6 ONLINE +DG_DATA01/nehprd/nehprd_log06.dbf NO
2 1 ONLINE +DG_DATA01/nehprd/nehprd_log01.dbf NO
2 2 ONLINE +DG_DATA01/nehprd/nehprd_log02.dbf NO
2 3 ONLINE +DG_DATA01/nehprd/nehprd_log03.dbf NO
2 4 ONLINE +DG_DATA01/nehprd/nehprd_log04.dbf NO
2 5 ONLINE +DG_DATA01/nehprd/nehprd_log05.dbf NO
2 6 ONLINE +DG_DATA01/nehprd/nehprd_log06.dbf NO How was redo log group 4,5,6 created for thread 1 and how was redo log group 1,2,3 created for thread 2 ?Hi,
To make things worse, when you query v$logfile , It will show 6 redo logfiles belonging to 6 redo groups for each instance.The fact that it shows all groups of redo does not mean it belongs to that instance. Try to query v$database or v$datafile, this means that database/datafiles belongs to only one instance, of course not.
Isn't this a bit of a bug ?Of course not. It's concept.
To understand it you need understand the difference between instance and database. An database (i.e files) can be opened by many instances.
An Oracle database server consists of a database and at least one database instance (commonly referred to as simply an instance). Because an instance and a database are so closely connected, the term Oracle database is sometimes used to refer to both instance and database. In the strictest sense the terms have the following meanings:
Database
A database is a set of files, located on disk, that store data. These files can exist independently of a database instance.
Database instance
An instance is a set of memory structures that manage database files. The instance consists of a shared memory area, called the system global area (SGA), and a set of background processes. An instance can exist independently of database files.
Database: (v$database)
CONTROLFILE (v$controlfile)
DATAFILE (v$datafile)
ONLINELOG (v$logfile,v$log)
ARCHIVELOG (v$archivelog)
SPFILE
These views above will show the same values in either instance, because if the file (database) is changed it is modified in all instances. That's means you not need use gv$ because the information are the same in all instances, also you not need get info connecting in each instance querying theses v$ because the inf are the same independent of the instance
Instances: (v$instance)
PARAMETERS (v$parameter)
MEMORY STRUCTURE (e.g v$session)
The view v$session will show information about sessions from that instance only. In RAC each instance have you own info about session so you will need query gv$session because it get information about session from others instances.
The fact that each instance assign its own REDO/UNDO not mean they are part of the instances, REDO/UNDO are part of Database. They can be write by assigned instance and read by all instance (just it)
It's not a bug when you query v$datafile, v$logfile, v$controlfile in all instances you will get same result, because it's the DATABASE. (An database (i.e files) can be opened by many instances).
Levi Pereira -
How can I check the contents of the redo log files?
I recently install 10g. We haven't used the db yet, but the redo logs are very active.
Is there a query to determine what activity is filling the redo log files?
Thank you for any help.
Take Care.
SThe Automatic Workload Repository takes snapshots of
statistics, via scheduled job, at hourly intervals.
This is probably responsible for some of the redo.
You can see if this feature is turned on by checking
the job queue (simply: select * from dba_jobs).
The default settings on AWR can be managed using the
DBMS_WORKLOAD_REPOSITORY built-in package.
Hope this helps.
Kailash. -
I publish this question here, Due to the similarity between the technologies, and I know for you this is very familiar.
I have a dowstreams which has four standbys redo log groups. One of these groups is still in a redo of the day 23/04/2010. This old redo is not filed, always there.
this implies that the database downstreams only work with three groups of redo log and some oacaciones all these are in active status and at that time the view v $ archived_dest returns error for that destination (downstreams).
The question is:
how I can eliminate that standby redo log which is not being archived.
Thank you very much for your attentionI run this query
SELECT GROUP#, THREAD#, SEQUENCE#, ARCHIVED, STATUS,FIRST_TIME FROM V$STANDBY_LOG;
and it returns me
GROUP#____THREAD#__SEQUENCE#__ARC__STATUS__________FIRST_TIME
4___________ 1__________0_________NO____UNASSIGNED
5 ___________1_________2760_______YES_____ACTIVE__________04/05/10
6____________1________2328 _______YES______ACTIVE__________27/04/10 --> The stubborn redo
7____________1__________0_________NO_____UNASSIGNED
Maybe you are looking for
-
Hey Adobe, I need Rotate View in Illustrator please!
Same as in Photoshop, preferably silky smooth. thank you
-
Report parameter is not populated with exact value in stacked column click throughs
I have stacked column chart to show below opportunity data. Category axis: Month of created date Series: sales stage Aggregate: runningvalue of revenue on sales stage group. data set has below fields. 1. opportunity id 2. created date 3. revenue 4.
-
Organizing photos in events that match originals
I cleaned up(crop, delete bad ones, rename files) my photos in "events" but it didn't change in "originals". how do i get that to match?
-
Summarize items in crystal report
Hi all Any idea how to summarize Inventory Items of the same Item Code for printing in Crystal Report Design? The same item codes may appear in the same Sales Order or different Sales Order. Kedalene
-
Is the current Macbook ok to buy?
I have been recently wanting to buy the Macbook, 2.0GHz, White. I heard they were having a lot of problems with the previous models and was wondering if Apple has solved all these problems. First of the battery problem, of having it heat up too much