| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: my ORA-1079 gift for christmas and happy new year; thanx
--0-1273911899-978454157=:10897
Content-Type: text/plain; charset=us-ascii
Doc ID: Note:112011.1Subject: ALERT: RESIZE or AUTOEXTEND can "Over-size" Datafiles and Corrupt the DictionaryType: ALERTStatus: PUBLISHEDContent Type: TEXT/PLAINCreation Date: 07-JUN-2000Last Revision Date: 05-JUL-2000Language: USAENG
Oracle can allow OVERSIZED Datafiles in the Database~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This alert covers: [BUG:568232] [BUG:925105] and [BUG:813983] All SQL in this note should be run when connected as the SYS user. eg: connect internal, connect / as sysdba or connect sys/sys_passwordVersions Affected ~~~~~~~~~~~~~~~~~ The problems described here affects many Oracle releases thus: 7.1 to 7.3.4.5 inclusive 8.0 to 8.0.6.1 inclusive 8.1.5 to 8.1.6.1 inclusive The individual problems are addressed in various releases but are not all are fixed until the following Oracle release: 8.1.7.0 Individual fix versions are described below in the "Patches" section. Platforms Affected ~~~~~~~~~~~~~~~~~~ GENERIC - these problems can affect all platforms except OS/390 which does NOT support datafile resizing. Description ~~~~~~~~~~~ There are three bugs covered by this alert but all three can result in the same form of dictionary corruption. Th! e underlying problem is that an Oracle datafile can have, at most, 4194303 Oracle datablocks. But, certain operations allow this value to be exceeded resulting in corruption to the data dictionary and subsequent ORA-600 errors. Likelihood of Occurrence ~~~~~~~~~~~~~~~~~~~~~~~~ An 'oversized' file is one with more than 4194303 Oracle data blocks. As the DB_BLOCK_SIZE is set at database creation time the actual maximum file size for a given database (barring any port specific limits, notably 2Gb) can be found using the statement: SELECT to_char(4194303*value,'999,999,999,999')||' bytes' MAX_FILE_SIZE FROM v$parameter WHERE name='db_block_size'; The following operations can cause a file to contain too many Oracle blocks: Bug:813983 ~~~~~~~~~~ Resizing a datafile allows you to resize to a size larger than Oracle should allow. Eg: ALTER DATABASE DATAFILE 'xxxx' RESIZE xxxM; Bug:568232 ~~~~~~~~~~ It is possible to set AUTOEXTEND on a datafile ! with a MAXSIZE which exceeds the maximum allowable size. Eg: ALTER DATABASE DATAFILE 'xxxx' AUTOEXTEND ON MAXSIZE xxxM; Bug:925105 ~~~~~~~~~~ It is possible to issue an 'ADD DATAFILE' command without specifying a size (eg: on a RAW device or if a file already exists with the name being added). On some platforms this sets the file size to a default value of 4 billion blocks which is above the maximum 4194303 blocks. Eg: ALTER TABLESPACE test ADD DATAFILE '/dev/rdsk/dummy'; (the lack of a SIZE on this command can cause the problem) Workaround ~~~~~~~~~~ The workaround for all of the above problems is not to use the commands described in this alert with sizes above the maximum for your database DB_BLOCK_SIZE. As sizes are often specified in "K" or "M" never try to use file sizes greater than the values given by the following select: SELECT to_char(4194303*value,'999,999,999,999') MAX_BYTES, to_char(trunc(4194303*value/10! 24),'999,999,999')||' Kb' MAX_KB, to_char(trunc(4194303*value/1024/1024),'999,999')||' Mb' MAX_MB FROM v$parameter WHERE name='db_block_size'; For convenience the table below shows the maximum sizes for common DB_BLOCK_SIZES: DB_BLOCK_SIZE Max Mb value to use in any command ~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2048 8191 M 4096 16383 M 8192 32767 M 16384 65535 M Note: For a 2K (2048 byte) DB_BLOCK_SIZE an 8Gb datafile is TOO LARGE. An 8Gb file would be 8192Mb which is more than 4194303 DB blocks.Possible Symptoms ~~~~~~~~~~~~~~~~~ The symptoms of an oversized datafile include any of the following internal errors: ORA-600 [25012] ORA-600 [3292] ORA-600 [4375] ORA-600 [2847] Errors typically occur during: ALTER DATABASE DATAFILE '...' RESIZE ...M; or DROP TABLESPACE ...; or When a user session tries to use space beyond the 4194303 block mark in the file. Note that the above ORA-600 errors do not mean you have hit one ! of these bugs as there are other possible causes for these errors. Checking for Problem Files~~~~~~~~~~~~~~~~~~~~~~~~~~ The following statements will show if you have a problem due to one of the above bugs: 1. Check for Oversized files: SELECT f.ts#, f.file#, f.status$, f.blocks, v.name FROM file$ f, v$datafile v WHERE f.blocks > 4194303 AND f.file#=v.file# ; If this shows any rows then go to the section below entitled "What to do if I have an oversized file". If no rows are returned go the step 2. 2. Check for files that could extend too far: SELECT x.file#, x.maxextend , v.name FROM filext$ x, v$datafile v WHERE x.maxextend > 4194303 and v.file#=x.file# ; If this reports ORA-942 then you have no files which can over-extend. (If filext$ does not exist you have no files with AUTOEXTEND set) If this reports "no rows selected" then you have no files which can over-extend. If there are rows returned then reset the maximum file! size for the file. Eg: ALTER DATABASE DATAFILE 'filename' AUTOEXTEND ON MAXSIZE xxxM; where 'xxxM' is less than the maximum allowed (see the select in "Workaround" above).What to do if I have an 'oversized' file~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Once a file has been 'over-sized' in the database then there are three possible options as described below. In ALL cases it is advisable to take a full backup of your current situation before proceeding. a. If there have been no ORA-600 errors and no space has been allocated in the illegal part of the file then you should be able to drop the tablespace including its existing contents. ie: If the select below returns NO ROWS then you can attempt to drop the tablespace including contents: SELECT * FROM uet$ WHERE block#+length-1 > 4194303; NOTE-A: You should extract any required data from the tablespace before you drop it. b. The second option is to recover the entire database to a point! in time BEFORE the problem was introduced. For this you need to examine the alert log and find the earliest time when any file extended / resized / got added to the database which was oversized. Perform point in time recovery to a time before any file became oversized. c. Consult Oracle Support Services with all the information collected so far and ask them to refer to this alert.Patches~~~~~~~ Please contact Oracle Support to find out if a patch is available for your platform / version or consider upgrading to 8.1.7 if available. The individual bugs are fixed in releases as below: Bug:813983 8.1.6.0 onwards Bug:568232 8.0.5.0 onwards (including 8.0.6.X and 8.1.X) Bug:925105 8.1.7.0 onwards None of the bugs are fixed in any 7.3 patch set.References~~~~~~~~~~ Manual RESIZE allows more than 4 million DB Blocks [BUG:813983] Autoextend MAXSIZE can be set above 4 million DB blocks [BUG:568232] ADD DATAFILE with no SIZE can add a bad diction! ary entry [BUG:925105] 2Gb or not 2Gb (2Gb related issues) [NOTE:62427.1]
Philippe Siquin <philippe.siquin_at_informatique.gov.pf> wrote:
subject: my ORA-1079 gift for christmas and happy new year; thanx Oracle! :-)
hello,
while trying to 'startup' my database, i have the following message:
ORA-01079: ORACLE database was not properly created, operation aborted SVRMGR> I tried to recreate a controlfile as said in the doc :
SVRMGR> create controlfile reuse
2> database FISCD
3> logfile
4> '/ora01/oraredo/FISCD/redoFISCD11.log' size 1M,
5> '/ora01/oraredo/FISCD/redoFISCD21.log' size 1M,
6> '/ora01/oraredo/FISCD/redoFISCD31.log' size 1M
7> noresetlogs
8> datafile
9> '/ora01/oradata/FISCD/sys01.dbf' size 50M
10> maxinstances 8
11> maxlogfiles 32
12> /
alter database open
*
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/ora01/oradata/FISCD/sys01.dbf'
aaaaaaaaaaahhhh!!!!!!!!!
ok, I recover datafile :
PROD_sfx [SOFIX]:/home/oracle> oerr ora 1113
01113, 00000, "file %s needs media recovery"
// *Cause: An attempt was made to online or open a database with a file that
// is in need of media recovery.
// *Action: First apply media recovery to the file.
SVRMGR> select * from v$recover_file ;
FILE# ONLINE ERROR CHANGE# TIME
---------- ------- ------------------ ---------- ---------
1 ONLINE 149111 28/12/00
1 row selected.
SVRMGR> recover datafile '/ora01/oradata/FISCD/sys01.dbf' Media recovery complete.
Super! it works :-))))))
SVRMGR> alter database open ;
alter database open
*
ORA-00600: internal error code, arguments: [25012], [1], [2], [], [], [], [], []
:-((((( F*ck !
oerr ora 600
00600, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Cause: This is the generic internal error number for Oracle program
// exceptions. This indicates that a process has encountered an // exceptional condition.
any ideas ?
PS: i'm not an Oracle-guru (as you can see...:-)
PS2: Happy new year from Tahiti (French Polynesia)!
*
|
|
* | *
\ | /
\ . /
\ a /
\ .@. /
@@@
* - - - - - `@@@@@@@@@@@@@' - - - - - *
`@@@@@@@'
/ @@@@ @@@@ \
/ @@@ @@@ \
/ @@ + @@ \
' "X" `
"XXX"
"XXXXX"
"GOD JUL"
"BUON ANNO"
"FELIZ NATAL"
"JOYEUX NOEL"
"VESELE VANOCE"
"MELE KALIKIMAKA"
"NODLAG SONA DHUIT"
"BLWYDDYN NEWYDD DDA"
"""""""BOAS FESTAS"""""""
"FELIZ NAVIDAD"
"MERRY CHRISTMAS"
"KALA CHRISTOUGENA"
"VROLIJK KERSTFEEST"
"FROHLICHE WEIHNACHTEN"
"BUON NATALE-GODT NYTAR"
"HUAN YING SHENG TAN CHIEH"
"WESOLYCH SWIAT-SRETAN BOZIC"
"MOADIM LESIMHA-LINKSMU KALEDU"
"HAUSKAA JOULUA-AID SAID MOUBARK"
"""""""'N PRETTIG KERSTMIS"""""""
"ONNZLLISTA UUTTA VUOTTA"
"Z ROZHDESTYOM KHRYSTOVYM"
"NADOLIG LLAWEN-GOTT NYTTSAR"
"FELIC NADAL-GOJAN KRISTNASKON"
"S NOVYM GODOM-FELIZ ANO NUEVO"
"GLEDILEG JOL-NOELINIZ KUTLU OLSUM"
"EEN GELUKKIG NIEUWJAAR-SRETAN BOSIC"
"KRIHSTLINDJA GEZUAR-KALA CHRISTOUGENA"
"SELAMAT HARI NATAL - LAHNINGU NAJU METU"
"""""""SARBATORI FERICITE-BUON ANNO"""""""
"ZORIONEKO GABON-HRISTOS SE RODI"
"BOLDOG KARACSONNY-VESELE VIANOCE "
"MERRY CHRISTMAS AND HAPPY NEW YEAR"
"ROOMSAID JOULU PUHI -KUNG HO SHENG TEN"
"FELICES PASUAS - EIN GLUCKICHES NEUJAHR"
"PRIECIGUS ZIEMAN SVETKUS SARBATORI VESLLE"
"BONNE ANNEBLWYDDYN NEWYDD DDADRFELIZ NATAL"
"""""""""""""""""""""""""""""""""""""""""""""""""
XXXXX
XXXXX
XXXXX
XXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
---------------------------------
<P> <TABLE border=0 cellPadding=0 cellSpacing=0> <TBODY> <TR> <TD vAlign=top><STRONG>Doc ID: </STRONG></TD> <TD>Note:112011.1</TD></TR> <TR> <TD vAlign=top><STRONG>Subject: </STRONG></TD> <TD>ALERT: RESIZE or AUTOEXTEND can "Over-size" Datafiles and Corrupt the Dictionary</TD></TR> <TR> <TD vAlign=top><STRONG>Type: </STRONG></TD> <TD>ALERT</TD></TR> <TR> <TD vAlign=top><STRONG>Status: </STRONG></TD> <TD>PUBLISHED</TD></TR></TBODY></TABLE> <TABLE border=0 cellPadding=0 cellSpacing=0> <TBODY> <TR> <TD vAlign=top><STRONG>Content Type: </STRONG></TD> <TD>TEXT/PLAIN</TD></TR> <TR> <TD vAlign=top><STRONG>Creation Date: </STRONG></TD> <TD>07-JUN-2000</TD></TR> <TR> <TD vAlign=top><STRONG>Last Revision Date: </STRONG></TD> <TD>05-JUL-2000</TD></TR> <TR> <TD vAlign=top><STRONG>Language: </STRONG></TD> <TD>USAENG</TD></TR></TBODY></TABLE><PRE>Oracle can allow OVERSIZED Datafiles in the Database ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~This alert covers: [BUG:568232] [BUG:925105] and <A href="http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_id=813983&p_database_id=BUG" target=new>[BUG:813983]</A>
All SQL in this note should be run when connected as the SYS user. eg: connect internal, connect / as sysdba or connect sys/sys_password Versions Affected
7.1 to 7.3.4.5 inclusive 8.0 to 8.0.6.1 inclusive 8.1.5 to 8.1.6.1 inclusive
The individual problems are addressed in various releases but are not all are fixed until the following Oracle release:
8.1.7.0
Individual fix versions are described below in the "Patches" section.
Platforms Affected
except OS/390 which does NOT support datafile resizing.
Description
The underlying problem is that an Oracle datafile can have, at most, 4194303 Oracle datablocks. But, certain operations allow this value to be exceeded resulting in corruption to the data dictionary and subsequent ORA-600 errors.
Likelihood of Occurrence
SELECT to_char(4194303*value,'999,999,999,999')||' bytes' MAX_FILE_SIZE FROM v$parameter WHERE name='db_block_size';
The following operations can cause a file to contain too many Oracle blocks:
Bug:813983
Resizing a datafile allows you to resize to a size larger than Oracle should allow. Eg: ALTER DATABASE DATAFILE 'xxxx' RESIZE xxxM;
Bug:568232
It is possible to set AUTOEXTEND on a datafile with a MAXSIZE which exceeds the maximum allowable size. Eg: ALTER DATABASE DATAFILE 'xxxx' AUTOEXTEND ON MAXSIZE xxxM;
Bug:925105
It is possible to issue an 'ADD DATAFILE' command without
specifying a size (eg: on a RAW device or if a file already
exists with the name being added).
On some platforms this sets the file size to a default value of
4 billion blocks which is above the maximum 4194303 blocks.
Eg: ALTER TABLESPACE test ADD DATAFILE '/dev/rdsk/dummy';
(the lack of a SIZE on this command can cause the problem)
Workaround
SELECT to_char(4194303*value,'999,999,999,999') MAX_BYTES,
to_char(trunc(4194303*value/1024),'999,999,999')||' Kb' MAX_KB,
to_char(trunc(4194303*value/1024/1024),'999,999')||' Mb' MAX_MB
FROM v$parameter WHERE name='db_block_size';
For convenience the table below shows the maximum sizes for common DB_BLOCK_SIZES:
DB_BLOCK_SIZE Max Mb value to use in any command ~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2048 8191 M 4096 16383 M 8192 32767 M 16384 65535 M Note: For a 2K (2048 byte) DB_BLOCK_SIZE an 8Gb datafile is TOO LARGE. An 8Gb file would be 8192Mb which is more than 4194303 DB blocks.
Possible Symptoms
ORA-600 [25012] ORA-600 [3292] ORA-600 [4375] ORA-600 [2847]
ALTER DATABASE DATAFILE '...' RESIZE ...M; or
DROP TABLESPACE ...;
or
When a user session tries to use space beyond the 4194303 block mark in the file.
Note that the above ORA-600 errors do not mean you have hit one of these bugs as there are other possible causes for these errors.
Checking for Problem Files
SELECT f.ts#, f.file#, f.status$, f.blocks, v.name
FROM file$ f, v$datafile v
WHERE f.blocks > 4194303
AND f.file#=v.file#
;
If this shows any rows then go to the section below entitled
"What to do if I have an oversized file". If no rows are returned
go the step 2.
2. Check for files that could extend too far:
SELECT x.file#, x.maxextend , v.name
FROM filext$ x, v$datafile v
WHERE x.maxextend > 4194303
and v.file#=x.file#
;
If this reports ORA-942 then you have no files which can over-extend.
(If filext$ does not exist you have no files with AUTOEXTEND set)
If this reports "no rows selected" then you have no files which can
over-extend.
If there are rows returned then reset the maximum file size for the
file.
Eg: ALTER DATABASE DATAFILE 'filename' AUTOEXTEND ON MAXSIZE xxxM;
where 'xxxM' is less than the maximum allowed (see the
select in "Workaround" above).
What to do if I have an 'oversized' file
SELECT * FROM uet$ WHERE block#+length-1 > 4194303;
NOTE-A: You should extract any required data from the tablespace before you drop it. b. The second option is to recover the entire database to a point in time BEFORE the problem was introduced. For this you need to examine the alert log and find the earliest time when any file extended / resized / got added to the database which was oversized. Perform point in time recovery to a time before any file became oversized. c. Consult Oracle Support Services with all the information collected so far and ask them to refer to this alert.Patches
Bug:813983 8.1.6.0 onwards
Bug:568232 8.0.5.0 onwards (including 8.0.6.X and 8.1.X)
Bug:925105 8.1.7.0 onwards
None of the bugs are fixed in any 7.3 patch set.
References
Manual RESIZE allows more than 4 million DB Blocks <A href="http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_id=813983&p_database_id=BUG" target=new>[BUG:813983]</A> Autoextend MAXSIZE can be set above 4 million DB blocks <A href="http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_id=568232&p_database_id=BUG" target=new>[BUG:568232]</A> ADD DATAFILE with no SIZE can add a bad dictionary entry <A href="http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_id=925105&p_database_id=BUG" target=new>[BUG:925105]</A> 2Gb or not 2Gb (2Gb related issues) [NOTE:62427.1]</PRE><PRE><BR> <B>Philippe Siquin <philippe.siquin_at_informatique.gov.pf></B> wrote: <BR></PRE>
<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px"><FONT face="Courier New, Courier">subject: my ORA-1079 gift for christmas and happy new year; thanx Oracle! :-)<BR><BR>hello,<BR><BR>while trying to 'startup' my database, i have the following message:<BR><BR><B>ORA-01079: ORACLE database was not properly created, operation aborted<BR>SVRMGR> <BR><BR></B>I tried to recreate a controlfile as said in the doc :<BR><BR><B>SVRMGR> create controlfile reuse<BR> 2> database FISCD<BR> 3> logfile<BR> 4> '/ora01/oraredo/FISCD/redoFISCD11.log' size 1M,<BR> 5> '/ora01/oraredo/FISCD/redoFISCD21.log' size 1M,<BR> 6> '/ora01/oraredo/FISCD/redoFISCD31.log' siz! e 1M<BR> 7> noresetlogs<BR> 8> datafile<BR> 9> '/ora01/oradata/FISCD/sys01.dbf' size 50M<BR> 10> maxinstances 8<BR> 11> maxlogfiles 32<BR> 12> /<BR>Statement processed.<BR><BR></B>alter database open <BR>*<BR>ORA-01113: file 1 needs media recovery<BR>ORA-01110: data file 1: '/ora01/oradata/FISCD/sys01.dbf'<BR><BR><BR><B>aaaaaaaaaaahhhh!!!!!!!!!<BR></B>ok, I recover datafile :<BR><BR><BR>PROD_sfx [SOFIX]:/home/oracle> oerr ora 1113<BR>01113, 00000, "file %s needs media recovery"<BR>// *Cause: An attempt was made to online or open a database with a file that<BR>// is in need of media recovery.<BR>// *Action: First apply media recovery to the file.<BR><BR><BR>SVRMGR> select * from v$recover_file ;<BR>FILE# &nb! sp; ONLINE ERROR CHANGE# TIME <BR>---------- ------- ------------------ ---------- ---------<BR> 1 ONLINE 149111 28/12/00 <BR>1 row selected.<BR><BR><BR><B>SVRMGR> recover datafile '/ora01/oradata/FISCD/sys01.dbf'<BR>Media recovery complete.<BR><BR><BR></B>Super! it <B>works </B>:-))))))<BR><BR><BR><BR>SVRMGR> alter database open ;<BR>alter database open <BR>*<BR><B>ORA-00600: internal error code, arguments: [25012], [1], [2], [], [], [], [], []<BR><BR><BR></B>:-((((( F*ck !<BR><BR>oerr ora 600<BR>00600, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"<BR>// *Cause: This is the generic internal error nu!mber for Oracle program<BR>// exceptions. This indicates that a process has encountered an<BR>// exceptional condition.<BR>// *Action: Report as a bug - the first argument is the internal error number<BR><BR>any ideas ?<BR>PS: i'm not an Oracle-guru (as you can see...:-)<BR>PS2:<B> Happy new year from Tahiti (French Polynesia)!<BR><BR></B><X-SIGSEP><BR>
<P></X-SIGSEP> *<BR> |<BR> |<BR> * | *<BR> &! nbsp; \ | /<BR> \ . /<BR> \ a /<BR> \ .@. /<BR> &n! bsp; @@@<BR> * - - - - - `@@@@@@@@@@@@@' - - - - - *<BR> `@@@@@@@'<BR> / @@@@ @@@@ \<BR> / @@@ @@@ \<BR>  ! ; / @@ + @@ \<BR> ' "X" `<BR> "XXX"<BR> "XXXXX"<BR> &nbs! p; "GOD JUL"<BR> "BUON ANNO"<BR> "FELIZ NATAL"<BR> "JOYEUX NOEL"<BR> "VESELE VANOCE"<BR> &nb! sp; "MELE KALIKIMAKA"<BR> "NODLAG SONA DHUIT"<BR> "BLWYDDYN NEWYDD DDA"<BR> """""""BOAS FESTAS"""""""<BR> "FELIZ NAVIDAD"<BR> &n! bsp; "MERRY CHRISTMAS"<BR> "KALA CHRISTOUGENA"<BR> "VROLIJK KERSTFEEST"<BR> "FROHLICHE WEIHNACHTEN"<BR> "BUON NATALE-GODT NYTAR"<BR> "HUAN YING SHENG TAN CHIEH"<BR>  ! ; "WESOLYCH SWIAT-SRETAN BOZIC"<BR> "MOADIM LESIMHA-LINKSMU KALEDU"<BR> "HAUSKAA JOULUA-AID SAID MOUBARK"<BR> """""""'N PRETTIG KERSTMIS"""""""<BR> "ONNZLLISTA UUTTA VUOTTA"<BR> "Z ROZHDESTYOM KHRYSTOVYM"<BR> &nb! sp; "NADOLIG LLAWEN-GOTT NYTTSAR"<BR> "FELIC NADAL-GOJAN KRISTNASKON"<BR> "S NOVYM GODOM-FELIZ ANO NUEVO"<BR> "GLEDILEG JOL-NOELINIZ KUTLU OLSUM"<BR> "EEN GELUKKIG NIEUWJAAR-SRETAN BOSIC"<BR> "KRIHSTLINDJA GEZUAR-KALA CHRISTOUGENA"<BR> ! "SELAMAT HARI NATAL - LAHNINGU NAJU METU"<BR> """""""SARBATORI FERICITE-BUON ANNO"""""""<BR> "ZORIONEKO GABON-HRISTOS SE RODI"<BR> "BOLDOG KARACSONNY-VESELE VIANOCE "<BR> "MERRY CHRISTMAS AND HAPPY NEW YEAR"<BR> "ROOMSAID JOULU PUHI -KUNG HO SHENG TEN"<BR> "FELICES PASUAS - EIN GLUCKICHES NEUJAHR"<B! R> "PRIECIGUS ZIEMAN SVETKUS SARBATORI VESLLE"<BR> "BONNE ANNEBLWYDDYN NEWYDD DDADRFELIZ NATAL"<BR> """""""""""""""""""""""""""""""""""""""""""""""""<BR> XXXXX<BR> XXXXX<BR> &n! bsp; XXXXX<BR> XXXXXXXXXXXXX<BR>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<BR><BR></FONT></P></BLOCKQUOTE><p><br><hr size=1><b>Do You Yahoo!?</b><br>Received on Tue Jan 02 2001 - 10:49:17 CST
 |
 |