Ò׽ؽØÍ¼Èí¼þ¡¢µ¥Îļþ¡¢Ãâ°²×°¡¢´¿ÂÌÉ«¡¢½ö160KB

oracle supportÒ»´ÎΣ»ú´¦Àí£¨Ö®Ò»£©

ÌìÓв»²â·çÔÆ£¬
IBM µÄÖж˴ÅÅÌÕóÁÐÕâ´ÎÓÖÈÇ»öÁË¡£ÔÚ΢ÂëÉý¼¶µÄʱºò£¬
DS4800 ·¢Éú¹ÊÕÏ¡£IBM¹¤³Ìʦ°ÑÕóÁйÊÕϻָ´ºó£¬ÅÄÅÄÆ¨¹É×ßÈË£¬ÁôÏÂÁËÕóÁÐÉϲ»Ò»ÖµÄÊý¾Ý¡£
û°ì·¨£¬ÕóÁÐÉϵÄÊý¾ÝÓÖµÃÎÒÃÇÀ´Ïë°ì·¨ÇÀ¾ÈÁË¡£¡£¡£¡£
»¹ºÃÓÐoracle supportµÄÖ§³ÖÎÒÃÇ×îÖÕ»¯½âÁËÕâ´ÎΣ»ú¡£ÏÂÎÄÏêϸ½éÉÜÁËÕû¸ö»Ö¸´µÄ¹ý³Ì¡£
 
 
oracle¹¤³Ìʦµ½´ïÏÖ³¡ºó£¬¸ù¾Ý´íÎóÐÅÏ¢£¬
 
ÎÊÌâÇé¿öÈçÏÂSRÐÅÏ¢Ëùʾ£º£¨HP-UX PA-RISC (64-bit)+ORACLE 9.2.0.8.0.+filesystem+no archivelog mode+no backup)
** Customer's Management 24x7 contact name:***************
** Customer's Management 24x7 contact number: ****************
** Primary Customer contact name: *******************
** Current Customer 24x7 voice phone number: ********************
** Current Customer E-mail address: ********************
** Current Customer Pager/Fax number: *****************
### Characteristics of Problem ###
This is a critical production system
Database is down and will not start
Data corruption issue and media recovery failed to fix the problem
 
### Note:28814.1 did not help because: ###
It did not have the needed information.
### Other: Note:28814.1 did not help because: ###
Sys owned objects corrupted
### The corruption was detected on: ###
Data file.
### Other: The corruption was detected on: ###
system tablespace
### The corruption affected a segment of type: ###
Table.
### Other: The corruption affected a segment of type: ###
TRANSACTION MANAGED DATA BLOCK
### The affected segment belongs to: ###
Database Dictionary.
### Other: The affected segment belongs to: ###
Database dictionary
### What error(s) and message(s) are Oracle reporting? ###
09:52:24 SQL> recover database allow 1 corruption;
ORA-00283: recovery session canceled due to errors
ORA-10562: Error occurred while applying redo to data block (file# 1, block# 1490)
ORA-10564: tablespace SYSTEM
ORA-01110: data file 1: '/oradata/yincang/rlv_system'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 201
ORA-00600:


Ïà¹ØÎĵµ£º

¹ØÓÚoracleµÄС֪ʶ

select trunc(sysdate ,'yyyy') from dual   --±¾Äê¶ÈµÚÒ»Ìì
              
select trunc(sysdate ,'mm') from dual     --±¾ÔµÚÒ»Ìì
           &nbs ......

Oracle ÈÕÆÚ²éѯÓï¾äС½á

²éѯÐÇÆÚ¼¸:
select to_char(sysdate,'day') from dual;
²éѯ¼¸ºÅ:
select to_char(sysdate,'dd') from dual;
²éѯСʱÊý:
select to_char(sysdate,'hh24') from dual;
²éѯʱ¼ä:
select to_char(sysdate,'hh24:mi:ss') from dual;
²éѯÈÕÆÚʱ¼ä:
select to_char(sysdate,'yyyy-mm-dd hh24:mi:ss') from dual;
²é ......

oracle ¹éµµÓë·Ç¹éµµÄ£Ê½

ÔÚ
Oracle
Êý
¾Ý¿â
ÖУ¬
Ö÷ÒªÓÐÁ½ÖÖ
ÈÕÖ¾
²Ù×÷ģʽ£¬·Ö±ðΪ·Ç¹é
µµÄ£Ê½Óë¹éµµÄ£Ê½¡£Ä¬ÈÏÇé¿öÏ£¬Êý¾Ý¿â
²É
ÓõÄÊǷǹ鵵ģʽ
¡£×÷Ϊһ¸öºÏ¸ñµÄÊý¾Ý¿â¹Ü
Àí
Ô±£¬Ó¦µ±ÉîÈëÁ˽âÕâÁ½ÖÖÈÕÖ¾²Ù×÷ģʽµÄÌØµã£¬²¢ÇÒÔÚÊý¾Ý¿â½¨Á¢Ê±£¬Ñ¡
ÔñºÏÊʵIJÙ×÷ģʽ¡£
¡¡¡¡±ÊÕß
½ñÌì¾Í̸̸×Ô¼º¶ÔÕâÁ½ÖÖ²Ù×÷ģʽµÄÀí½â£¬²¢ÇÒ¸ø³ö ......

Oracle dead lock deep research.

Update SQLS will lead dead lock exception. Because by default, it use optimistic lock but not pessimistic lock.
Below description is exceprted from the attachment(It exceeds my image that this blog can not upload the attachment,hehe)
Optimistic locking offers an elegant solution to the problems o ......

oracle¸ßˮλÏß

ʲôÊÇË®Ïß(High Water Mark)?
----------------------------
ËùÓеÄoracle¶Î(segments£¬ÔÚ´Ë£¬ÎªÁËÀí½â·½±ã£¬½¨Òé°Ñsegment×÷Ϊ±íµÄÒ»¸öͬÒå´Ê) ¶¼ÓÐÒ»¸öÔÚ¶ÎÄÚÈÝÄÉÊý¾ÝµÄÉÏÏÞ£¬ÎÒÃǰÑÕâ¸öÉÏÏÞ³ÆÎª"high water mark"»òHWM¡£Õâ¸öHWMÊÇÒ»¸ö±ê¼Ç£¬ÓÃÀ´ËµÃ÷ÒѾ­ÓжàÉÙûÓÐʹÓõÄÊý¾Ý¿é·ÖÅ䏸Õâ¸ösegment¡£HWMͨ³£Ôö³¤µÄ·ù¶ ......
© 2009 ej38.com All Rights Reserved. ¹ØÓÚE½¡ÍøÁªÏµÎÒÃÇ | Õ¾µãµØÍ¼ | ¸ÓICP±¸09004571ºÅ