¹ØÓÚoracleËÀËø
Èç¹û½ö½öÊÇlock£¬ÒÔÏÂÓï¾ä¿ÉÒÔ·¢ÏÖËùÓÐÓû§Ëø :
SELECT s.username,
decode(l.type, 'TM', 'TABLE LOCK', 'TX', 'ROW LOCK', NULL) LOCK_LEVEL,
o.owner,
o.object_name,
o.object_type,
s.sid,
s.serial#,
s.terminal,
s.machine,
s.program,
s.osuser
from v$session s, v$lock l, all_objects o
WHERE l.sid = s.sid
AND l.id1 = o.object_id(+)
AND s.username is NOT Null
Èç¹ûÓÐËøµÈ´ý»òËÀËø£¬¿ÉÒÔͨ¹ýÒÔÏÂÓï¾ä·¢ÏÖ:
select lpad(' ', decode(l.xidusn, 0, 3, 0)) || l.oracle_username User_name,
o.owner,
o.object_name,
o.object_type
from v$locked_object l, dba_objects o
where l.object_id = o.object_id
order by o.object_id desc
Ïà¹ØÎĵµ£º
alter system set nls_length_semantics='BYTE' scope=both
sql>show parameter length
NAME TYPE
------------------------------------ --------------------- ......
About parent vs child latches. There is no fundamental low level difference between parent and child latches, they are all small regions of memory modified with atomic test-and-set style opcodes.
You see parent (and solitary) latches from x$ksll ......
Õâ¸öOracleµÄ·ÖÒ³ÏÔʾ¾Ý˵ÊÇ×îÂé·³µÄ£¨MySQL×î¼òµ¥£©£¬µ«ÊÇÕâ¸ö·ÖÒ³ÏÔʾºÜÓÐÓá£ÏÖÔںܶàÍøÕ¾ÉϵÄÌõÄ¿¶¼·Ç³£¶à£¬ÀýÈçÐÂÎÅ£¬¿ÉÄܾ͸ոüеľÍÓÐÉϰÙÌõ£¬ÔÙ¼ÓÉÏÒÔǰµÄ£¬Ò»ÕÅÒ³Ãæ¿Ï¶¨¾ÍÊǷŲ»ÏÂÁË£¬ËùÒÔ·ÖÒ³µÄºÃ´¦¾ÍÊÇ¿ÉÒÔ½â¾öÕâ¸öÎÊÌâ¡£
ÏÂÃæÒ»ÅÅÅŵĽÐÄãÑ¡ÔñµÚ¼¸Ò³£¬Ò»Ñ¡Ôñ£¬Ö±½Ó¾ÍÌøµ½ºóÃæµÄ¼¸Ò³È¥ÁË£¬²»ÓÃÕâÑù´ÓÉÏÒ ......
ÅäÖÃÎļþ£º
<hibernate-mapping>
<class name="vo.SshPost" table="ssh_post" >
<!-- <cache usage="read-write"/>-->
<id name="postId" type="java.lang.String">
......
INTERVAL DAY TO SECONDÊý¾ÝÀàÐÍ
OracleÓï·¨:
INTERVAL '{ integer | integer time_expr | time_expr }'
{ { DAY | HOUR | MINUTE } [ ( leading_precision ) ]
| SECOND [ ( leading_precision [, fractional_seconds_precision ] ) ] }
[ TO { DAY | HOUR | MINUTE | SECOND [ (fractional_seconds_precision) ] } ......