-
Jan22
PowerCmd v2.1 Serial Numbers
Posted in Something, 450 views
-
Name: Flynn1982
S/N:
PCMDA-TU3YB-3TBUY-CADPM
PCMDA-O86AF-6OF8A-CADPM
PCMDA-E56IC-6EC5I-CADPM
PCMDA-MFUU2-UM2FU-CADPM
PCMDA-MQG03-GM3Q0-CADPM
ÐCMDA-J5NBD-NJD5B-CADPM
PCMDA-KTDCK-DKKTC-CADPM
PCMDA-EBHNE-HEEBN-CADPM
PCMDA-N461Y-6NY41-CADPM
PCMDA-5LPZY-P5YLZ-CADPM -
No Comments » powercmd sn
-
Jan16
Mysql中的STRICT_TRANS_TABLES
Posted in Database, Program, 583 views
-
在调试php symfony,加载fixture数据时,遇到了错误:
SQLSTATE[HY000]: General error: 1366 Incorrect integer value: 'log' for column 'tasklog_id' at row 1
这是因为mysql5.5中默认启用了STRICT_TRANS_TABLES参数。
STRICT_TRANS_TABLES的工作方式:
· 对于事务性存储引擎,在语句中任何地方出现的不良数据值均会导致放弃语句并执行回滚。
· 对于非事务性存储引擎,如果错误出现在要插入或更新的第1行,将放弃语句。(在这种情况下,可以认为语句未改变表,就像事务表一样)。首行后出现的错误不会导致放弃语句。取而代之的是,将调整不良数据值,并给出告警,而不是错误。换句话讲,使用STRICT_TRANS_TABLES后,错误值会导致MySQL执行回滚操作,如果可以,所有更新到此为止。要想执行更严格的检查,请启用STRICT_ALL_TABLES。除了非事务性存储引擎,它与STRICT_TRANS_TABLES等同,即使当不良数据出现在首行后的其他行,所产生的错误也会导致放弃语句。这意味着,如果错误出现在非事务性表多行插入或更新过程的中途,仅更新部分结果。前面的行将完成插入或更新,但错误出现点后面的行则不然。
因此,解决方法就是在my.ini里把STRICT_TRANS_TABLES关掉
#Set the SQL mode to strict #sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" sql-mode="NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
-
No Comments » my.ini mysql php STRICT_TRANS_TABLES symfony
-
Jan04
Enterprise Architect 7 资源
Posted in Database, Program, 511 views
-
Enterprise Architect 7.5 汉化版下载:
http://9.gddx3.crsky.com:808/200907/ha_EnterpriseArchitect-v7.5.843fix.zipEnterprise Architect 7.5注册码
Name:whitehouse.net.cn
Company:eric
注册码:{67SC0O95-SZPS-LIG2-YQ8Q-8D2N-KWTD-0W6R-TWDD-KT6RB-1J}Enterprise Architect 7.1注册码
Name:whitehouse.net.cn
Company:whitehouse.net.cn
注册码:{GLAOMULN-N1F1-EGBC-XN52-9QC6-GJGJ-0W6R-TWDD-KT6RB-SQ} -
No Comments » ea Enterprise Architect 汉化 注册
-
Dec25
-
Congratulations! The transfer request for the following domain name(s) has been completed:
DBALIFE.COM
域名转移终于完成了,由edong.com转移到godaddy.com,彻底摆脱通信管理局的控制。
下一步再把万网的域名转移过来。
政府宣传了几千年大禹治水,现在依然只会一刀切,只会干这种万人唾骂的事,谁还记得疏优于堵?
堵吧,不知道最后哭的人是谁。
-
No Comments »
-
Nov23
Chrome Frame导致IE异常
Posted in Something, 402 views
-
访问Google Wave时,被要求安装Chrome Frame插件。
几天后发现IE出现了非常奇怪的问题,google reader的列表全部无法在新窗口打开,页面空白,标题类似:cf:attach_external_tab&71619392&3
这意味着用户只能看google reader里的摘要,而看不到全文
郁闷了好几天,终于发现是Chrome Frame(cf)的问题,将其禁用后,一些正常。
-
No Comments » chrome frame Google ie wave
-
Nov16
Oracle Trace Level Event Numbers
Posted in Database, 773 views
-
Oracle Trace Level Event Numbers
相关参考信息:
10000 control file debug event, name 'control_file' 10001 control file crash event1 10002 control file crash event2 10003 control file crash event3 10004 control file crash event4 10005 trace latch operations for debugging 10006 testing - block recovery forced 10007 log switch debug crash after new log select, thread %s 10008 log switch debug crash after new log header write, thread %s 10009 log switch debug crash after old log header write, thread %s 10010 Begin Transaction 10011 End Transaction 10012 Abort Transaction 10013 Instance Recovery 10014 Roll Back to Save Point 10015 Undo Segment Recovery 10016 Undo Segment extend 10017 Undo Segment Wrap 10018 Data Segment Create 10019 Data Segment Recovery 10020 partial link restored to linked list (KSG) 10021 latch cleanup for state objects (KSS) 10022 trace ktsgsp 10023 Create Save Undo Segment 10024 Write to Save Undo 10025 Extend Save Undo Segment 10026 Apply Save Undo 10027 latch cleanup for enqueue locks (KSQ) 10028 latch cleanup for enqueue resources (KSQ) 10029 session logon (KSU) 10030 session logoff (KSU) 10031 row source debug event (R*) 10032 sort end (SOR*) 10035 parse SQL statement (OPIPRS) 10036 create remote row source (QKANET) 10037 allocate remote row source (QKARWS) 10038 dump row source tree (QBADRV) 10039 type checking (OPITCA) 10040 dirty cache list 10041 dump undo records skipped 10042 trap error during undo application 10044 free list undo operations 10045 "free list update operations - ktsrsp, ktsunl" 10046 enable SQL statement timing 10047 trace switching of sessions 10048 Undo segment shrink 10049 protect library cache memory heaps 10050 sniper trace 10051 trace OPI calls 10052 don't clean up obj$ 10053 CBO Enable optimizer trace 10054 trace UNDO handling in MLS 10055 trace UNDO handing 10056 dump analyze stats (kdg) 10057 suppress file names in error messages 10058 use table scan cost in tab$.spare1 10060 CBO Enable predicate dump 10061 disable SMON from cleaning temp segment 10062 disable usage of OS Roles in osds 10063 disable usage of DBA and OPER privileges in osds 10064 "thread enable debug crash level %s, thread %s" 10065 limit library cache dump information for state object dump 10066 simulate failure to verify file 10067 force redo log checksum errors - block number 10068 force redo log checksum errors - file number 10069 Trusted Oracle test event 10070 force datafile checksum errors - block number 10071 force datafile checksum errors - file number 10072 protect latch recovery memory 10073 have PMON dump info before latch cleanup 10074 default trace function mask for kst 10075 CBO Disable outer-join to regular join conversion 10076 CBO Enable cartesian product join costing 10077 CBO Disable view-merging optimization for outer-joins 10078 CBO Disable constant predicate elimination optimization 10080 dump a block on a segment list which cannot be exchanged 10081 segment High Water Mark has been advanced 10082 free list head block is the same as the last block 10083 a brand new block has been requested from space management 10084 free list becomes empty 10085 free lists have been merged 10086 CBO Enable error if kko and qka disagree on oby sort 10087 disable repair of media corrupt data blocks 10088 CBO Disable new NOT IN optimization 10089 CBO Disable index sorting 10090 invoke other events before crash recovery 10091 CBO Disable constant predicate merging 10092 CBO Disable hash join 10093 CBO Enable force hash joins 10094 before resizing a data file 10095 dump debugger commands to trace file 10096 after the cross instance call when resizing a data file 10097 after generating redo when resizing a data file 10098 after the OS has increased the size of a data file 10099 after updating the file header with the new file size 10100 after the OS has decreased the size of a data file 10101 atomic redo write recovery 10102 switch off anti-joins 10103 CBO Disable hash join swapping 10104 dump hash join statistics to trace file 10105 CBO Enable constant pred trans and MPs w WHERE-clause 10106 CBO Disable evaluating correlation pred last for NOT IN 10107 CBO Always use bitmap index 10108 CBO Don't use bitmap index 10109 CBO Disable move of negated predicates 10110 CBO Try index rowid range scans 10111 Bitmap index creation switch 10112 Bitmap index creation switch 10113 Bitmap index creation switch 10114 Bitmap index creation switch 10115 CBO Bitmap optimization use maximal expression 10116 CBO Bitmap optimization switch 10117 CBO Disable new parallel cost model 10118 CBO Enable hash join costing 10119 QKA Disable GBY sort elimination 10120 CBO Disable index fast full scan 10121 CBO Don't sort bitmap chains 10122 CBO disable count(col) => count(*) transformation 10123 QKA Disable Bitmap And-EQuals 10145 test auditing network errors 10146 enable Oracle TRACE collection 10200 block cleanout 10201 consistent read undo application 10202 consistent read block header 10203 consistent read buffer status 10204 signal recursive extend 10205 row cache debugging 10206 transaction table consistent read 10207 consistent read transactions' status report 10208 consistent read loop check 10209 enable simulated error on control file 10210 check data block integrity 10211 check index block integrity 10212 check cluster integrity 10213 crash after control file write 10214 simulate write errors on control file 10215 simulate read errors on control file 10216 dump control file header 10217 debug sequence numbers 10218 dump uba of applied undo 10219 monitor multi-pass row locking 10220 show updates to the transaction table 10221 show changes done with undo 10222 row cache 10223 transaction layer - turn on verification codes 10226 trace CR applications of undo for data operations 10227 verify (multi-piece) row structure 10228 trace application of redo by kcocbk 10230 check redo generation by copying before applying 10231 skip corrupted blocks on _table_scans_ 10232 dump corrupted blocks symbolically when kcbgotten 10233 skip corrupted blocks on index operations 10234 trigger event after calling kcrapc to do redo N times 10235 check memory manager internal structures 10236 library cache manager 10237 simulate ^C (for testing purposes) 10238 instantiation manager 10239 multi-instance library cache manager 10240 dump dba's of blocks that we wait for 10241 dump SQL generated for remote execution (OPIX) 10243 simulated error for test %s of K2GTAB latch cleanup 10244 make tranids in error msgs print as 0.0.0 (for testing) 10245 simulate lock conflict error for testing PMON 10246 print trace of PMON actions to trace file 10247 Turn on scgcmn tracing. (VMS ONLY) 10248 turn on tracing for dispatchers 10249 turn on tracing for multi-stated servers 10250 Trace all allocate and free calls to the topmost SGA heap 10251 check consistency of transaction table and undo block 10252 simulate write error to data file header 10253 simulate write error to redo log 10254 trace cross-instance calls 10256 turn off multi-threaded server load balancing 10257 trace multi-threaded server load balancing 10258 force shared servers to be chosen round-robin 10259 get error message text from remote using explicit call 10260 Trace calls to SMPRSET (VMS ONLY) 10261 Limit the size of the PGA heap 10262 Don't check for memory leaks 10263 Don't free empty PGA heap extents 10264 Collect statistics on context area usage (x$ksmcx) 10265 Keep random system generated output out of error messages 10266 Trace OSD stack usage 10267 Inhibit KSEDMP for testing 10268 Don't do forward coalesce when deleting extents 10269 Don't do coalesces of free space in SMON 10270 Debug shared cursors 10271 distributed transaction after COLLECT 10272 distributed transaction before PREPARE 10273 distributed transaction after PREPARE 10274 distributed transaction before COMMIT 10275 distributed transaction after COMMIT 10276 distributed transaction before FORGET 10277 Cursor sharing (or not) related event (used for testing) 10281 maximum time to wait for process creation 10282 Inhibit signalling of other backgrounds when one dies 10286 Simulate control file open error 10287 Simulate archiver error 10288 Do not check block type in ktrget 10289 Do block dumps to trace file in hex rather than fromatted 10290 kdnchk - checkvalid event - not for general purpose use. 10291 die in dtsdrv to test controlfile undo" 10292 dump uet entries on a 1561 from dtsdrv" 10293 dump debugging information when doing block recovery" 10294 enable PERSISTENT DLM operations on non-compliant systems" 10300 disable undo compatibility check at database open 10301 Enable LCK timeout table consistency check" 10320 Enable data layer (kdtgrs) tracing of space management calls" 10352 report direct path statistics 10353 number of slots 10354 turn on direct read path for parallel query 10355 turn on direct read path for scans 10356 turn on hint usage for direct read 10357 turn on debug information for direct path 10374 parallel query server interrupt (validate lock value) 10375 turn on checks for statistics rollups 10376 turn on table queue statistics 10377 turn off load balancing 10379 direct read for rowid range scans (unimplemented) 10380 kxfp latch cleanup testing event 10381 kxfp latch cleanup testing event 10382 parallel query server interrupt (reset) 10383 auto parallelization testing event 10384 parallel dataflow scheduler tracing 10385 parallel table scan range sampling method 10386 parallel SQL hash and range statistics 10387 parallel query server interrupt (normal) 10388 parallel query server interrupt (failure) 10389 parallel query server interrupt (cleanup) 10390 Trace parallel query slave execution 10391 trace rowid range partitioning 10392 parallel query debugging bits 10393 print parallel query statistics 10394 allow parallelization of small tables 10395 adjust sample size for range table queues 10396 circumvent range table queues for queries 10397 suppress verbose parallel coordinator error reporting 10398 enable timeouts in parallel query threads 10399 use different internal maximum buffer size 10400 turn on system state dumps for shutdown debugging 10500 turn on traces for SMON 10510 turn off SMON check to offline pending offline rollbacksegment 10511 turn off SMON check to cleanup undo dictionary 10512 turn off SMON check to shrink rollback segments 10600 check cursor frame. allocation 10602 cause an access violation (for testing purposes) 10603 cause an error to occur during truncate (for testing purposes) 10604 trace parallel create index 10605 enable parallel create index by default 10606 trace parallel create index 10607 trace index rowid partition scan 10608 trace create bitmap index 10610 trace create index pseudo optimizer 10666 Do not get database enqueue name 10667 Cause sppst to check for valid process ids 10690 Set shadow process core file dump type (Unix only) 10691 Set background process core file type (Unix only) 10700 Alter access violation exception handler 10701 Dump direct loader index keys 10702 Enable histogram data generation 10703 Simulate process death during enqueue get 10704 Print out information about what enqueues are being obtained 10706 Print out information about instance lock manipulation 10707 Simulate process death for instance registration 10708 Print out Tracing information for skxf multi instance comms 10709 enable parallel instances in create index by default 10710 trace bitmap index access 10711 trace bitmap index merge 10712 trace bitmap index or 10713 trace bitmap index and 10714 trace bitmap index minus 10715 trace bitmap index conversion to rowids 10800 disable Smart Disk scan 10801 enable Smart Disk trace 10802 reserved for Smart Disk 10803 write timing statistics on OPS recovery scan 10804 reserved for ksxb 10805 reserved for row source sort 10900 extent manager fault insertion event #%s 10924 import storage parse error ignore event 10925 trace name context forever 10926 trace name context forever 10927 trace name context forever 10928 trace name context forever 10999 do not get database enqueue name
-
No Comments » 10046 level oracle trace
-
Oct10
vmware server 2.0 安装要点
Posted in Database, 757 views
-
vmware server 2.0采用web界面,初始用户和密码与宿主机器的系统用户相同,如administrator/xxxx。
但在登录时很可能遇到以下的问题:
- ErrorThe VMware Infrastructure Web Service at "http://localhost:8222/sdk" is not responding (Connection Refused).
检查:vmware host agent服务是否已经启动;在hosts文件中是否包含 127.0.0.1 localhost;登录用户是否拥有Administrator权限;登录用户是否属于_vmware_user_用户组 - The server was unable to process your log in request. Please check with your server administrator.
运行net user 用户名 /active:yes
- ErrorThe VMware Infrastructure Web Service at "http://localhost:8222/sdk" is not responding (Connection Refused).
-
No Comments » server vmware 登录
-
Sep24
sqlplus增强设置
Posted in Database, 453 views
-
更强的编辑器
sqlplus可以与vi整合,在sqlplus中调用vi编辑器。方法是在sqlplus中执行define_editor='vi',或将define_editor='vi'添加到/product/10.2/sqlplus/admin/glogin.sql文件中。
之后再登录sqlplus,可以输入edit命令编辑上一次执行的sql。
更人性化的提示符
在glogin.sql文件中添加:
set termout off
default gname=idle
column global_name new_value gname
SELECT lower(USER) || '@' ||upper(instance_name)||'('||nvl(UTL_INADDR.GET_HOST_ADDRESS, SYS_CONTEXT('userenv', 'ip_address'))||')' GLOBAL_NAME FROM v$instance;
set sqlprompt '&gname> '
set termout on这样每次登录SQLPLUS提示符会自动更改为“当前用户名@实例名(IP地址)> ”的形式。
10g以下版本在登录后切换用户的情况下,提示符不能自动更新。
-
No Comments » login prompt SQL sqlplus vi
-
Sep24
利用ROWID准确定位数据所在的BLOCK
Posted in Database, 363 views
-
SQL>select rowid,
2 dbms_rowid.rowid_relative_fno(rowid) RFILE#,
3 dbms_rowid.rowid_block_number(rowid) BLOCK#,
4 dbms_rowid.rowid_row_number(rowid) ROW#,
5 t.*
6 from testabc t
7 /ROWID RFILE# BLOCK# ROW# BANNER
------------------ ---------- ---------- ---------- ----------------------------------------------------------------
AAADUUAAEAAAAAMAAA 4 12 0 Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
AAADUUAAEAAAAAMAAB 4 12 1 PL/SQL Release 10.2.0.4.0 - Production
AAADUUAAEAAAAAMAAC 4 12 2 CORE 10.2.0.4.0 Production
AAADUUAAEAAAAAMAAD 4 12 3 TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
AAADUUAAEAAAAAMAAE 4 12 4 NLSRTL Version 10.2.0.4.0 - Production -
No Comments » block dbms rowid 定位
-
Sep17
Oracle10g 后台进程列表
Posted in Database, 432 views
-
$ ps -ef | grep ora_ | grep -v grep
oracle 14385 1 0 Oct10 ? 00:00:01 ora_pmon_WENDING
oracle 14387 1 0 Oct10 ? 00:00:00 ora_psp0_WENDING
oracle 14389 1 0 Oct10 ? 00:00:00 ora_mman_WENDING
oracle 14391 1 0 Oct10 ? 00:00:21 ora_dbw0_WENDING
oracle 14393 1 0 Oct10 ? 00:01:01 ora_lgwr_WENDING
oracle 14395 1 0 Oct10 ? 00:00:01 ora_ckpt_WENDING
oracle 14397 1 0 Oct10 ? 00:01:00 ora_smon_WENDING
oracle 14399 1 0 Oct10 ? 00:00:00 ora_reco_WENDING
oracle 14401 1 0 Oct10 ? 00:00:26 ora_cjq0_WENDING
oracle 14403 1 0 Oct10 ? 00:01:45 ora_mmon_WENDING
oracle 14405 1 0 Oct10 ? 00:00:37 ora_mmnl_WENDING
oracle 14409 1 0 Oct10 ? 00:00:04 ora_arc0_WENDING
oracle 14411 1 0 Oct10 ? 00:00:03 ora_arc1_WENDING
oracle 14415 1 0 Oct10 ? 00:00:00 ora_qmnc_WENDING
oracle 14421 1 0 Oct10 ? 00:00:15 ora_q000_WENDING
oracle 19027 1 0 Oct20 ? 00:00:00 ora_q002_WENDING
$一、后台进程包括1)Focused Background Processes
2)Utility Background Processes1. Focused Background Processes
PMON(Process Monitor) :
1)connection在不正常终止时,pmon负责释放资源,rollback未提交的事务;
2)监控后台进程,如果某些后台进程不正常终止,则会重启它(比如dispatcher),或者直接终止实例(比如lgmr终止时);
3)实例启动时,pmon负责注册实例到监听上,当实例启动时,pmon进程会检查默认监听器是否启动,如果使用非默认的监听器,需要设置local_listener参数。SMON(System Monitor:
1)clean up临时空间:真正的临时段不需要clean up,但某些操作,比如create index产生的临时段当create index的session不正常终止时,此时需要smon来清理。
2)Coalesces free space:如果使用字典管理表空间,smon负责将连续的空闲extent合并;
3)Recovers transactions active against unavailable files: 这个过程和实例启动时进行的instance crash recovery(自动前滚和回滚)相似,只不过由于实例启动时某些文件无法访问,而实例启动后的某个时间这些文件可以访问时,smon就会对其执行 recover;
4)Performs instance recovery of a failed node in RAC: 当rac的某个节点失败时,某个剩余的节点会打开失败节点对应的redo log,进行recover;
5)Cleans up OBJ$: obj$是个底层的数据字典,包括所有的数据库对象信息,很多时候,某些对象被删除时,由smon进程来clean up 该视图;
6)Shrinks rollback segments:如果设置了optimal size参数,smon进程负责执行回滚段的自动收缩
7)"Offlines" rollback segments:当用户offline某个回滚段,但此时该回滚断有active trancsaction,这是回滚段的状态其实是pending offline,而smon进程会定期的检查该回滚段的事务是否完成,完成即将其变为offline;
8)还有很多其它任务。RECO(Recovery Background Process)
1)reco有个主要工作,就是recover那些两阶段提交的但由于网络或其它原因造成状态为prepared 的挂起事务。
两阶段提交的概念:A 2PC is a distributed protocol that allows for a modification that affects many disparate databases to be committed automically. It attempts to close the window for distributed failure as much as possible before committing. In a 2PC between N databases, one of the databases—typically (but not always) the one the client logged into initially—will be the coordinator. This one site will ask the other N-1 sites if they are ready to commit. In effect, this one site will go to the N-1 sites and ask them to be prepared to commit. Each of the N-1 sites reports back its “prepared state” as YES or NO. If any one of the sites votes NO, the entire transaction is rolled back. If all sites vote YES,then the site coordinator broadcasts a message to make the commit permanent on each of the N-1 sites.
关于2pc的中文帖子说明:http://flyhorse2k.spaces.live.com/blog/cns!9C7106D3DF7B09DE!178.entry
2) 当某些节点反馈yes给事务协调器可以提交时,但事务协调器还未正式发出可以提交的最后指示时,由于网络的原因,这些节点失去了和事务协调节点的联系,此时这些事务就成为了an in-doubt distributed transaction。此时,RECO就负责定期的联系事务协调器,当联系到时,就会提交或者回滚这些事务了。
3)对于某些大的事务,如果使用reco的成本比较高,可以人为的干涉来处理掉这些事务
SQL> select local_tran_id,global_tran_id,state from dba_2pc_pending;
SQL> rollback force "";CKPT(Checkpoint):
1)CKPT 进程不是做checkpoint(A checkpoint is the writing of dirty (modified) blocks from the buffer cache to disk)的,而是在发生checkpoint时,修改数据文件头的。
2)在oracle8以前,CKPT的任务可以由LGWR进程来执行,因此CKPT进程可选,但从8.0开始,CKPT进程是必须的,LGWR也减少了执行负担。DBWR(Database Writer):
1)负责将dirty buffer写入到datafile中,目的是腾出sga空间和advance checkpoint;
2)Advance checkpoint后,oracle在做instance recover时,就从online redo file的新位置做为起点位置做恢复;
3)当发生log switch时,会出发checkpoint;
4)当online log file 需要被重用时,checkpoint还没有做完的话,警告文件里面会有checkpoint not complete的警告;
5)如果dbwr的性能低下,我们会发现很多free buffer waits和write complete waits的等待;
6)可以配置多个dbwr进程,比如dbw1,dbw2,...dbw9,...dbwj,最多20个,参数为db_writer_processes,这可以利用多个CPU的并行处理功能;
7)如果操作系统支持AIO,dbwr就可以不用等待操作系统写完,而继续下一个dbwr请求;
8)如果操作系统不支持AIO,可以利用dbwr slaves来模拟,参数为dbwr_io_slaves;LGWR(Log Writer):
1)将redo log buffer写入到redo log file中;
2)每3秒、commit、redo log buffer 1/3满时,都会触发lgwr写;
3)因此redo log buffer不需要太大;
4)lgwr采用sequenctial地写入,不像dbwr是scatter的写入,因此lgwr的性能要高很多;ASMB(Automatic Storage Manangement Background):
1)ASM实例与数据库实例通信的桥梁
2)与各实例更新和交换状态信息RBAL(Reblance):
1)当使用ASM存储database file时,启用该进程;
2)该进程负责当从ASM disk group中增加或减少disk时,rebalance数据。LMON(Lock monitor):
1)RAC下的进程;
2)负责监控RAC集群中的实例是否fail;
3)当RAC中实例增加或减少时,负责重新配置lock和其他资源;LMD(Lock mananger daemon):
1)RAC下的进程;
2)将global cache service(keep he block buffer consistent between instances)的锁请求发送给LMSn控制的队列中;LMSn(Lock managerserver):
1)RAC下的进程;
2)主要目的是通过cache-to-cache的方式,保证gloabal cache service;
3)每个Instance可以配置最多10gLMSn;LCK0(Lock):
1)RAC下的进程;
2)作用和LMD类似,但它不仅处理datablock buffer的请求,也处理其它的global resource;DIAG(Diagnosability daemon):
1)RAC下的进程;
2)监控各个实例是否health,并且在发生fail时,进行capture;2. Utility Background Processes
CJQ0 and Jnnn Processes:Job Queue
1)当配置job_queue_processes时,会有Jnnn和CJQ0进程;
2)Jnnn进程最多可有1000个;
3)Jnnn进程在job之间是共享的,但同时每个Jnnn只能执行一个job,并且它使用的内存是在UGA中;
4)物化试图的刷新一般要用到job;
5)streams一般用到AQ;
6)CJQ0,做为jnnn的coordinator,它来控制jnnn的启动和关闭;
7)Jnnn进程只会在有job需要处理时才会启动;QMNC and Qnnn Processes:Job Queue
1)用于AQ功能;
2)Qnnn处理每个message queue,QMNC做为Qnnn的coordinator;
3)如果配置了aq_tm_processes,就会启动QMNC和Qnnn进程,不论有没有queue要处理,Qnnn都会全部启动;EMNn:Event Monitor Processes
1)用于AQ功能;
2)用于监控queue,向订购者反馈消息。MMAN(Memory Manager):
1)当使用自动管理内存功能时,MMAN负责处理sga各组件的内存动态分配,包括有default buffer pool,shared pool,java pool,large pool。MMON(Memory Monitor):
1)与AWR功能配合,用于自动侦测数据库问题及调优。MMON写出AWR需要的统计信息MMNL(Memory Monitor Light):
1)与AWR协作,在必要时将所有统计信息buffer写入磁盘CTWR:Change Tracking Processes
1)负责维护new change tracking file。RVWR:Recovery Writer
1)负责维护flash recovery area中的before images数据。还有一些其他的utility process,比如为dataguard服务的,为streams服务的,为data pump服务的等等。
二、从进程包括
1)I/O slaves
2)Parallel query SlavesI/O Slaves
1)如果操作系统不支持AIO,可以利用io slaves模拟aio;
2)backup_tape_io_slaves为rman服务,设置为true的话,rman会根据需要自动启动一些slaves来完成与tape的相关读写操作;
3)dbwr_io_slaves为dbwr使用,当设置dbwr_io_slave大于0时,lgwr和arch会使用他们自己的slaves(最多4个);
4)dbwr的从进程为I1nn,lgwr的从进程为I2nn。Parallel Query Slaves
1)当执行某些语句时,会产生很多执行计划,这些执行其实可以并行执行,然后合并成一个输出结果;
2)可以利用并行查询功能来实现并行;
3)产生的并行查询进程名为Pnnn。 -
No Comments » oracle10g 列表 详解 进程

Comments