Log switch must occur every 15 to 30 minutes: good practice or myth?

I often heard that it is recommended to size redo log files in a way that Oracle performs a log switch every 15 to 30 minutes.
I would like to know if it is true or if it is a myth ?
I would like to know the best way for sizing redo log files ?
What happen exactly in the database when a log switch occurs ?
Please help me to clarify these concepts.

So we can say that a log switch induces a full checkpoint. That's correct ?Well, no :-) . Indeed with a log switch the checkpoint event is generated requesting DBWR to flush the buffers from the checkpoint-queue to the data files but this is not a full checkpoint and it would not update the datafile and control file headers. The Full Checkpoint happens with the alter system checkpoint ( as shown) , database being shutdown properly.
Please see the below code which shows the same,
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select checkpoint_change# from V$datafile;
CHECKPOINT_CHANGE#
           3507400
           3507400
           3507400
           3507400
           3507400
           3507400
           3507400
7 rows selected.
SQL> select * from V$log;
    GROUP#    THREAD# SEQUENCE#      BYTES    MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIM
         1          1         91   52428800          1 NO CURRENT
      3507399 13-APR-10
         2          1         89   52428800          1 NO INACTIVE
      3486253 13-APR-10
         3          1         90   52428800          1 NO INACTIVE
      3486256 13-APR-10
SQL> alter system switch logfile;
System altered.
SQL> select * from V$log;
    GROUP#    THREAD# SEQUENCE#      BYTES    MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIM
         1          1         91   52428800          1 NO ACTIVE
      3507399 13-APR-10
         2          1         92   52428800          1 NO CURRENT
      3507906 13-APR-10
         3          1         90   52428800          1 NO INACTIVE
      3486256 13-APR-10
SQL> select checkpoint_change# from V$datafile;
CHECKPOINT_CHANGE#
           3507400
           3507400
           3507400
           3507400
           3507400
           3507400
           3507400
7 rows selected.
SQL> select checkpoint_change# from V$datafile;
CHECKPOINT_CHANGE#
           3507400
           3507400
           3507400
           3507400
           3507400
           3507400
           3507400
7 rows selected.
SQL> alter system checkpoint;
System altered.
SQL> select checkpoint_change# from V$datafile;
CHECKPOINT_CHANGE#
           3507936
           3507936
           3507936
           3507936
           3507936
           3507936
           3507936
7 rows selected.
SQL>HTH
Aman....

Similar Messages

Want to reduce Log switch time interval !!!

Friends ,
I know that the standard LOG SWITCH TIme interval is 20/30 minutes , i.e., every time it is better switch redolog 1 to redolog 2 (or redolog2 to redolog3) within 20/30 minutes.
But in my production server , Logfile switches within every 60 minutes every time in the peak hour . Now my question , How I can make a situation where my logfile should switch to another logfile between 20/30 minutes .
Here my database configuration is :
Oracle database 10g (10.2.0.1.0 version) in AIX 5.3 server
AND
SQL> show parameter fast_start_mttr_target
NAME TYPE VALUE
fast_start_mttr_target integer 600
My every redolog file size is = 50 MB
In this situation , give me advice plz how I can reduce my logswitch time interval ?

You could either
a. Recreate your RedoLog files with a smaller size --- which action I would not recommend
OR
b. Set the instance parameter ARCHIVE_LAG_TARGET to 1800
ARCHIVE_LAG_TARGET specifies (in seconds) the duration at which a log switch would be forced, if it hasn't been done so by the online redo log file being full.
You should be able to use ALTER SYSTEM to change this value.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Checkpoint and log switch

I would like to know if when a redo log is filled, the new redo log can be written in parallel with the chekpoint.
Or simply, what's the sequence for log switching:
1 - redo log is filled -> checkpoint -> new log writes. or
2 - redo log is filled -> checkpoint/new log writes (in parallel)
Best Regards,
Rogerio C. Schreiner
null

I'm tempted to say 'don't worry about it', because L_C_T has been deprecated since 9i: instead use FAST_START_MTTR_TARGET to control the rate of checkpointing.
But that aside, L_C_T essentially says: "if a block was dirtied (changed) by a transaction whose redo was generated more that X seconds ago -where X is the number of seconds LCT is set to- then that block will be flushed to disk the next time DBWR wakes up on the '3 second rule'"
L_C_INTERVAL means something similar: "If a block was dirtied by a transaction whose redo can be found in the redo log more than Y redo blocks away from the current checkpoint marker, where Y is the setting for LCI, flush it next time DBWR wakes up"
A checkpoint does not always result in a log switch, but a log switch always results in a checkpoint.
You can't really answer your third question, because the LCT parameter doesn't mean "Every 1800 seconds, flush everything to disk" (as it used to in version 8.0). But if a block was dirtied more than 1800 seconds ago, it will be a candidate for flushing to disk next time DBWR wakes up. But that doesn't tell us when a log switch will occur: that will only happen when the redo log fills up and we have to switch to the next log to keep going. I can't tell anything about the size of your logs or the rate at which they will fill up from the parameters you list.
A parameter does exist which will force a log switch every so often. It's called ARCHIVE_LAG_TARGET, and it's set to a number of seconds. If that was set to 1800, I could say with confidence that you'd log switch every half hour. But that's not what you had in your question, of course!
You might care to read this slightly more technical description of the parameters:
http://www.jlcomp.demon.co.uk/faq/log_checkpoint.html
(though I think Jonathan's timelines are wrong, because the change to the effect of the parameters came in with 8i).
Message was edited by:
howardjr

Question about frequent log switches

I support an Oracle 10g database (10.2.0.4) and database activity has increase to the point that, during the heaviest parts of the day, log switches are occurring too frequently (15 - 20 times per hour!). We also utilize Data Guard to replicate the database to our DR site. We currently have 2 log groups with 2 membes in each group.
I understand that I can tackle this issue 2 ways: either to increase the size of my redo log files (they are currently at 50 Meg each), or I can add additional redo log groups to the database.
I would like to get some opinions on whether on solution is better than the other, or the pros and cons of each course of action.
Thank you in advance for your advice with my question!

CowTown_dba wrote:
Thanks for helping me to understand my true problem. The issue is that because of the frequent log switches, database performance is degrading.Maybe that's the cause, maybe it isn't.
Users are complaining about slow response. So if I add more groups it will buy the archiver extra time but it will not help with the slow response issue.Depends on the root cause of the slow response issue. That has yet to be determined. While it may be true that your car has a short in the electrical system and your car doesn't start, it doesn't necessarily follow that the car doesn't start because of the short in the electrical system.
>
I really appreciate everyone contributing to my understanding of the issue, and helping clarify the root problem so that I can fix it the first time around.
You guys rock!

Forcing log switch every minute.

Hi,
I want to force a log switch every one minute how can i do it?
What should be the value of fast_start_mttr_target?
Does a checkpoint force a log switch?
Do i need to only reduce the size of redo log to a small size?
How can i make sure that a log switch will happen after a particular time period for ex. 1Minute,2 minute.
I want to force a log switch every minute because i want to send the archive redo log to standby database so that not more than 1 minute changes in database are lost. I am using 10g R2 on windows 2003 server.
I am unable to find a solution. Any help?

Hi,
I want to force a log switch every one minute how
can i do it? yes with archive_lag_target parameter
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#sthref934
What should be the value of fast_start_mttr_target?incremental or normal checkpoint "fast instance recovery/downtime concerned" introduced from oracle 8, this feature is enabled with the initialization parameter FAST_START_MTTR_TARGET in 9i.
fast_start_mttr_target to database writer tries to keep the number of dirty blocks in the buffer cache low enough to guarantee rapid recovery in the event of a crash. It frequently updates the file headers to reflect the fact that there are not dirty buffers older than a particular SCN.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmtunin004.htm#sthref1110
Does a checkpoint force a log switch? log switch force to checkpoint ,checkpoint never force to log switch.
Do i need to only reduce the size of redo log to a
small size?depends yours SLA how far you can risk the data ,but it will effect yours database performance ,recommended to set the size of log which should imply the log swtich after filling to 20 mins,its a trade off risk vs perofrmance.
How can i make sure that a log switch will happen
after a particular time period for ex. 1Minute,2
minute.
want to force a log switch every minute because i
want to send the archive redo log to standby database
so that not more than 1 minute changes in database
are lost. I am using 10g R2 on windows 2003 server.
am unable to find a solution. Any help?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#sthref934Khurram

Is there any Harm to switch the log file of production every minute

Is there any Harm to switch the log file of production every minute as we r trying to build a replication process. We are plaining to swith the redologs everyminute and then FTP it and use it for replication to achive the relatime senario

Is there a reason that you're not using DataGuard and/or Streams here? It would seem a lot easier to use the tools Oracle provides than to roll your own solution...
Switching the log file every minute may have some negative performance implications in your environment.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Every 10-15 minutes Firefox 3.6 cannot load pages (from bookmarks or links) and must be re-started

Every 10-15 minutes I find that clicking a link in a webpage or selecting a bookmark will elicit the white error page message that the target page could not be loaded; usually (but not always) I will be told that my internet connection "does not seem to be working". Other programs accessing the internet are not affected. The problem usually solves itself if I close FF, wait 2 minutes, and start it again, which is not really practical. The problem occurs both on a home network (wireless) and an office network (ethernet). FF3.6 has been problematic since I updated to it (esp.: slow to open); I have tried un-installing and dropping back to 3.5, but FF has twice updated to the most recent version (6.7, then 6.8) without asking whether I wanted this.
== This happened ==
Every time Firefox opened
== I updated to Firefox 3.6

Just an addition: when the connection drops out, the Windows 'error' sound occurs.

Nor more Checkpoints at every log-switch in 10.2 ?

Hi,
i working with Oracle about 12 years but i havn´t seen this before:
REM There is no work/application in the database now:
select group#,status from v$log;
GROUP# STATUS
1 CURRENT
2 ACTIVE
4 ACTIVE
5 ACTIVE
6 ACTIVE
First as i know only one or two (for a short time) shiould be active.
OK wait 90 seconds:
SQL> /
GROUP# STATUS
1 CURRENT
2 ACTIVE
4 ACTIVE
5 ACTIVE
6 ACTIVE
Try a log switch:
alter system switch logfile;
SQL> select group#,status from v$log;
GROUP# STATUS
1 ACTIVE
2 CURRENT
4 ACTIVE
5 ACTIVE
6 ACTIVE
How can i now drop one of the redo-logs ?
=> Solution:
alter system checkpoint;
select group#,status from v$log;
GROUP# STATUS
1 INACTIVE
2 CURRENT
4 INACTIVE
5 INACTIVE
6 INACTIVE
Does anybody know what Oracle changed here ?
Thanks in advance
Marco

hi,
welcome to Oracle10g:
show paramater FAST_START_MTTR_TARGET
if it is '0', then auto-checking-pointing is DISABLED, this happens to be the default on Oracle XE (under review)
By default, Oracle 10g supports automatic checkpoint tuning by making the best effort to write out SGA buffer cache dirty buffers w/o impacting the throughput of runtime physical I/O, thus achieving reasonable crash recovery time.
Setting the FAST_START_MTTR_TARGET parameter to a non-zero value or not setting this parameter enables automatic checkpoint tuning. The STATISTICS_LEVEL must be TYPICAL OR ALL. After a period of time, see V$MTTR_TARGET_ADVICE for various value for this parameter.

My MacBook Pro keeps going back to the desktop every 10-15 minutes, no matter what program I am using at the time. I tried restarting but it still occurs.

Has this ever happened to anyone else? I don't know what else to do and it's very annoying and disruptive. It occurs every time I go full screen in any application.

Back up all data.
Triple-click anywhere in the line below on this page to select it:
defaults delete com.apple.dock single-app && killall Dock
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
Wait for a new line ending in a dollar sign (“$”) to appear. You can then quit Terminal. Test.

Redo log switching

11gR2
Found out log switched every a few mins (2, 3 mins) at peak periods. I will make the recommendation for larger redo logs such that switches will be every 20 to 30 mins .
Wanted to know what would be negative side of large redo logs?

>
11gR2
Found out log switched every a few mins (2, 3 mins) at peak periods. I will make the recommendation for larger redo logs such that switches will be every 20 to 30 mins .
Wanted to know what would be negative side of large redo logs?
>
Patience, grasshopper!
If it ain't broke, don't fix it. So first make sure it is broken, or about to break.
Unless you have an emergency on your hands you don't want to implement a change like that without careful examination of your current log file usage and history.
You need to provide more information such as typical size of your log files, number of log groups, number of members in each group, log archive policy, etc.
1. How often do these 'peak periods' occur? Do they occur fewer than 5 or 6 times a day? Or dozens of times?
2. How long do they last? A few minutes? Or a few hours?
3. What is the typical, non-peak rate of switches? This is really your base-line that you need to compare things to.
4. What has the switch pattern been over the last few weeks or months?
5. What has the growth in DB activity benn over the last few weeks or months? What do expect over the next few months?
6. What is your goal in reducing the frequency of log switches?
Basic negative sides include longer time to archive each log file (the fewer logs in each group the more impact here) and the length of time to recover in the event you need to. With large log files there is more for Oracle to wade through to find the relevant data for restoring the DB to a given point in time.
Your suggestion of every 20 - 30 minutes means 2 to 3 times per hour. If you currently switch 10 or 12 times per hour you are making a very big change.
Although you don't want to 'tweak' the logs unnecessarily you also don't want to make such large changes.
Everything in moderation. If your current switch rate is 10 or 12 times per hour you may want to first cut this to maybe 1/2 to 1/3: that is, to 4 or 5 time per hour. It all depends on the answers to questions like I ask above. If you post the answers to know if will be helpful to anyone trying to advise you.

Archive log switch

-rw-r-----   1 oracle     oinstall   13427712 May 20 02:00 o1_mf_1_90491_4341nt0b_.arc
-rw-r-----   1 oracle     oinstall   13420544 May 20 02:01 o1_mf_1_90492_4341oov9_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:02 o1_mf_1_90493_4341q45y_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:02 o1_mf_1_90494_4341qytf_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:03 o1_mf_1_90495_4341s2w8_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:03 o1_mf_1_90496_4341szog_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:04 o1_mf_1_90497_4341v16m_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:05 o1_mf_1_90498_4341wsbl_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:05 o1_mf_1_90499_4341y0ps_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:06 o1_mf_1_90500_4341yyj1_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:06 o1_mf_1_90501_4342044h_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:07 o1_mf_1_90502_434217j9_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 02:10 o1_mf_1_90503_43426g1z_.arc
-rw-r-----   1 oracle     oinstall   13424640 May 20 05:01 o1_mf_1_90504_434d70c6_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:22 o1_mf_1_90505_434fhm1b_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:23 o1_mf_1_90506_434fjrgr_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:24 o1_mf_1_90507_434fkxkf_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:24 o1_mf_1_90508_434flzfp_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:25 o1_mf_1_90509_434fnngh_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:26 o1_mf_1_90510_434fp67w_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:27 o1_mf_1_90511_434fqwks_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:28 o1_mf_1_90512_434fslyn_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:29 o1_mf_1_90513_434fvr3c_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:30 o1_mf_1_90514_434fxrsq_.arc
-rw-r-----   1 oracle     oinstall   13427712 May 20 05:31 o1_mf_1_90515_434fzr8h_.arc
-rw-r-----   1 oracle     oinstall   13438976 May 20 10:00 o1_mf_1_90516_434xrhf9_.arcmine is 10.2.0.1 database...my log switch is happening intermittently....log file size is 20 MB
log_checkpoint_interval              integer     0
log_checkpoint_timeout               integer     1800
log_checkpoints_to_alert             boolean     FALSEHow can I set to happen log file switch at every 30 Minutes...

These are two different issues.
1. There are frequent log switches so the log file size could [should] be increased.
2. However, there are, at times, gaps of 3 hours and 5 hours between two
log switches. I presume that Deepa wants to ensure that a log switch occurs
"at least every 30minutes". It may occur more frequently than that (twice a
minutes) but the maximum gap between two log switches is desired as 30minutes.
That is what ARCHIVE_LAG_TARGET does.
It is not necessary that only in Standby databases would a DBA want a
maximum duration between log switches. You might be using this in a database
(as we have in Deepa's case !) where there are long "idle" stretches of time
with very little activity as well. Say, you have a background job periodically
backing up archivelogs using OS based methods (not RMAN) -- to tape
or to an NFS mount point or an offsite storage facility. ARCHIVE_LAG_TARGET
will help you ensure that the maximum data loss is 30minutes (even if there
was only 1 transaction of 1 row in those 30minutes) because that is what
your SLA might specify. This would be part of your media recovery / DR
requirements.
log_checkpoint_timeout is not to do with archiveloging but with checkpoints.
that is a complete different requirement -- that is for instance recovery not
media recovery / backup-restore / DR requirements.

I purchased bioshock 2 on the app store on my macbook pro (running lion) and it shows 'an error has occured' every time I try to download the app. How do I install it properly, I have restarted my mac and reset the app on the debug menu?

I purchased bioshock 2 on the app store on my macbook pro (running lion) and it shows 'an error has occured' every time I try to download the app. How do I install it properly, I have restarted my mac and reset the app on the debug menu?

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Select "/var/log/install.log" from the file list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar. Then select the messages from the last installation or update attempt, starting from the time when you initiated it. If you're not sure when that was, start over and note the time. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

Dataguard- scheduling manual log switch to have minimal lag

Hi,
I need some suggestion..
Recentry I had configured a physical standby for my 10g production database in maximum performance mode.
Now , to reduce the lag between the primary and standby , I put one cron job which will do a manual log switch(alter system switch logfile) in every 30 minutes.
and it is doing the job..!
Does this have any impact on my databases...?
Looking forward for your invaluable responce...
Regards
Noushad
DBA

Maybe you should let Oracle do it's job, configure this parameter which signifies that no buffer will remain dirty (in the cache) for more than 1800 (or whatever you want) seconds:
LOG_CHECKPOINT_TIMEOUT = 1800:p

Redo logs switches too frequent after migrating the db to different server

Dear Experts,
A couple of days back, we migrated our database (belonging to EBusiness Suite) to a different server, to get good performance benefit. The database is 10.2.0.4 and it was migrated from AIX 5.3 to Linux x86 64.
Users are happy with the performance, but I am getting below errors in the alert logs
a) Thread 1 cannot allocate new log, sequence 498
b) Private strand flush not complete
c) ORACLE Instance PROD - Can not allocate log, archival requiredOracle support is saying the issue is coming because of too frequent log switches. I am wondering how the log switches has become frequent in the new server. In the old server it was about 10 mins for every switch, now it is as frequent as 1 minute?
Any idea, what could be the reason behind this? Do you agree this issue is coming because frequent log switches?
Thanks
ARS

Kanchana Devasurendra wrote:
Hi ARS,
Please check the following item in your new database.
1. log_archive_max_processes Most properbly value set for this parameter is low ( may be it's set to 1.) Please increase up ( 4)I am curious to know what makes you think 4 is the right magic number for log_archive_max_processes - after all, he's only got one archive destination.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
A general reminder about "Forum Etiquette / Reward Points": http://forums.oracle.com/forums/ann.jspa?annID=718
If you never mark your questions as answered people will eventually decide that it's not worth trying to answer you because they will never know whether or not their answer has been of any use, or whether you even bothered to read it.
It is also important to mark answers that you thought helpful - again it lets other people know that you appreciate their help, but it also acts as a pointer for other people when they are researching the same question, moreover it means that when you mark a bad or wrong answer as helpful someone may be prompted to tell you (and the rest of the forum) what's so bad or wrong about the answer you found helpful.

OS completely stalls for 1-2 minutes about every 5-10 minutes

Hi there,
I find that my OS completely stalls for 1-2 minutes about every 5-10 minutes and not clear why. I am running "top -o cpu" from the shell and dont see a process that is hogging the CPU. One issue is that top even stalls with the entire machine.
I am using an MBP duo core 2 with 2GB of memory.
rebooted from the OSX DVD, ran disk check, and the disk is fine.
What is a suggested way to isolate the trouble.
Cheers,
Noah

Disk Utility First Aid doesn't do as thorough a job checking as Alsoft Disk Warrior.
Use SuperDuper to copy your drive to another drive. Try running off that to test things out.
Also, if there are changes to Disk Utility in 10.5.2, using the DVD is fine if you must, but better to run off a hard drive.
Safari's cache grows huge and needs to be reset or deleted from time to time
~/Library/Caches - those are all rebuilt if needed.
Most system stability problems with cache though are in
/Library
Try a new user account after you clean out as much temp files, logs and 'junk' as you can.
You might also install OS X to a small 20-30GB partition just for repairs and emergencies, in addition to a bootable working copy.
If you don't want SuperDuper, Carbon Copy Cloner is also a good option for backup and cloning.
Disk Warrior though is the best way to keep a drive healthy, used regularly for preventative drive repairs along with backups.
Onyx and Tiger Cache Cleaner are designed to help with numerous system maintenance tasks. Buit-in help, terminal command 'man' pages and more.
And try a Safe Boot into your "test" account AFTER you have backups and make sure your drive really is A-OK.

Log switch must occur every 15 to 30 minutes: good practice or myth?

Similar Messages

Maybe you are looking for