지역 사회
배우다
도구 라이브러리
AI 도구
여가
찾다
한국어
목차
FAILED TO READ MORROR SIDE 1
Bug 属性
相关产品
집 데이터 베이스 MySQL 튜토리얼 FAILEDTOREADMORRORSIDE1

FAILEDTOREADMORRORSIDE1

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB
WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB
Jun 07, 2016 pm 03:54 PM

FAILED TO READ MORROR SIDE 1 问题描述： 环境： RAC p740 p550 -bash-3.2$ srvctl status database -d kmis Instance kmis1 is running on node p550 Instance kmis2 is not running on node p740 AIX -bash-3.2$ oslevel -r 6100-08 数据库 oracle 11.2.2

FAILED TO READ MORROR SIDE 1

问题描述：

环境：
RAC p740 p550
-bash-3.2$ srvctl status database -d kmis

Instance kmis1 is running on node p550
Instance kmis2 is not running on node p740

AIX
-bash-3.2$ oslevel -r
6100-08

数据库 oracle 11.2.2 

$ srvctl start database -d kmis

PRCR-1079 : Failed to start resource ora.kmis.db

CRS-5017: The resource action "ora.ARCHDG.dg start" encountered the following error:

ORA-15032: not all alterations performed

ORA-15017: diskgroup "ARCHDG" cannot be mounted

ORA-15063: ASM discovered an insufficient number of disks for diskgroup "ARCHDG"

ORA-15080: synchronous I/O operation to a disk failed

CRS-2674: Start of 'ora.ARCHDG.dg' on 'p740' failed

CRS-2632: There are no more servers to try to place resource 'ora.kmis.db' on that would satisfy its placement policy

$

$ srvctl start instance -d kmis -i kmis2 -o open;

PRCR-1013 : Failed to start resource ora.kmis.db

PRCR-1064 : Failed to start resource ora.kmis.db on node p740

CRS-5017: The resource action "ora.ARCHDG.dg start" encountered the following error:

ORA-15032: not all alterations performed

ORA-15017: diskgroup "ARCHDG" cannot be mounted

ORA-15063: ASM discovered an insufficient number of disks for diskgroup "ARCHDG"

ORA-15080: synchronous I/O operation to a disk failed

1

p550

ASMCMD> ls -lState Type Rebal NameMOUNTED EXTERN N ARCHDG/MOUNTED NORMAL N CRS/MOUNTED EXTERN N DATADG/ASMCMD> host

p740上

MOUNTED NORMAL N CRS/MOUNTED EXTERN N DATADG/挂载不上 ARCDG

一挂载就报错

odm：

单击此项可添加到收藏夹\ 通过电子邮件发送此文档的链接\ 可打印页\ 转到底部转到底部\
 
\
\ \
 
   

Bug 属性

    
 
B - Defect 12.1
2 - Severe Loss of Service 11.2.0.1
90 - Closed, Verified by Filer 212 - IBM AIX on POWER Systems (64-bit)
2010-12-22
2014-3-19 N/A
11.2.0.1 Generic
Oracle
\
 
   

相关产品

    
 
Oracle Database Products Oracle Database Suite
Oracle Database 5 - Oracle Database - Enterprise Edition
\ 
Hdr: 10422126 11.2.0.1 RDBMS 11.2.0.1 ASM PRODID-5 PORTID-212
Abstract: FAILED TO READ MORROR SIDE 1
 
<strong>*** 12/22/10 03:46 am ***</strong>
----
 
PROBLEM:
--------
Alert log spooling this error continously and filling up available space.
Here is the message.
-----------------------
WARNING: failed to read mirror side 1 of virtual extent 665 logical extent 0 
of file 280 in group [1.445758315] from disk ASM_ESBQA001_DATA1_0005 
allocation unit 75811 reason error; if possible,will try another mirror side
-----------------------
 
When the problem starts, errors spin in the alert log until disk space is 
exausted. We have found that the process that is refrenced in the trace is 
usually an orphaned ebiz form.
 
Recent Changes - Upgrade to 11.2.0.1
 
Over the weekend we have upgraded Production Database to 11.2.0.1.  We&#39;ve had 
2 occurrence of the issue on 2 of the RAC nodes.
 
The issue had happened in QA and we have tried to drop the disk and add new 
disk again, but it did not solve the problem.
 
One more thing to note is, when this happens, there was a "run-away" process 
that also generates the same error message in a trace file. As long as that 
session/process is killed, the error messages stops.  Please investigate.
 
DIAGNOSTIC ANALYSIS:
--------------------
This looks closely related to bug.10051315 and bug.10055063
But customer has applied these patches already, even then we still see the 
same warning messages.
 
We are still trying to get information from customer to understand how that 
session is being killed(not sure could be from database end --or application 
end).
 
Customer confirmed the following :
---------------
1.) Are they in-house scripts scheduled in database/os which are going to 
kill the inactive sessions at database/os level ?
-- There are not any scripts scheduled to kill sessions.  When this error 
starts happening, we kill the process manually.
 
2.) Is this happening only during specific intervals.
-- I cannot see a pattern as to when it is happening.  It seems random.
 
3.) Please confirm - the ASM instance is functional (one can connect to it, 
run queries on the various v$asm% views, like: v$asm_diskgroup, v$asm_disk)
-- Yes, ASM is functional during the error.  All other sessions continue to 
run without errors.
---------------
 
WORKAROUND:
-----------
As long as that session/process is killed, the error messages stops.
 
RELATED BUGS:
-------------
bug.10051315 and bug.10055063
 
REPRODUCIBILITY:
----------------
Its random.
 
TEST CASE:
----------
NA
 
STACK TRACE:
------------
Function List   (to Full stack)   (to Summary stack)
 
     ksedsts <- ksdxfstk <- ksdxcb <- sspuser <- f0
        <- sdbgrfucf_close_file <- sdbgrfcf_close_file <- dbgrlWriteTextOnly 
<- dbgrlWriteAlertDetail_int <- dbgrlWriteAlertDetail
         <- dbgrlWriteAlertText <- dbkrlWriteAlertText <- dbkrlPril <- ksdfmw 
<- ksdwrt
          <- kfioCompleteIO <- kfioWaitIO <- kfioRequestPriv <- kfioRequest 
<- ksfd_kfioRequest
           <- ksfd_osmio <- ksfd_io <- ksfdread <- kcfrbd1 <- kcbzib
            <- kcbgcur <- kturRollbackToSavepoint <- ktcrsp1 <- ksures <- 
ksuxds
             <- kssdel <- kssdch <- ksudlp <- opidcl <- opidrv
              <- sou2o <- opimai_real <- ssthrdmain <- main
 
SUPPORTING INFORMATION:
-----------------------
Customer&rsquo;s Management name:      Al Fischer
Customer&#39;s Management 24x7 contact number:      +1-616-648-6244
Customer&rsquo;s Management email:      al.fischer@amway.com
Primary Customer Email address:      eric.lai
Secondary Contact Name:      George Zhang
Secondary Contact Email:      (EMAIL ADDRESS)  george.zhang@alticor.com
 
24 HOUR CONTACT INFORMATION FOR P1 BUGS:
----------------------------------------
 
DIAL-IN INFORMATION:
--------------------
 
IMPACT DATE:
------------
" system at risk of crashing as alert logging is filling up; causing forms to 
hang at Call Center"
 
<strong>*** 12/22/10 03:57 am ***</strong>
<strong>*** 12/22/10 04:20 am ***</strong>
<strong>*** 12/22/10 04:21 am ***</strong>
<strong>*** 12/22/10 04:21 am *** (CHG: Sta->16)</strong>
<strong>*** 12/22/10 04:33 am ***</strong>
<strong>*** 12/22/10 05:35 am ***</strong>
<strong>*** 12/22/10 06:08 am ***</strong>
<strong>*** 12/22/10 06:09 am ***</strong>
<strong>*** 12/22/10 06:10 am ***</strong>
<strong>*** 12/22/10 08:06 am ***</strong>
<strong>*** 12/22/10 11:25 am *** </strong>
<strong>*** 12/22/10 11:25 am ***</strong>
<strong>*** 12/22/10 01:47 pm *** (CHG: Sta->10)</strong>
<strong>*** 12/22/10 01:47 pm ***</strong>
<strong>*** 12/22/10 07:46 pm ***</strong>
<strong>*** 12/22/10 07:58 pm ***</strong>
File versions form GI & RDBMS homes.
 
Below is the info from GI_HOME.
 
[usax02w] $ ar -t -v -X32_64 $GI_HOME/lib/libserver11.a kfd.o
rw-rw-rw- 10000/1026  393236 Nov 15 13:29 2010 kfd.o
[usax02w] $ ar -t -v -X32_64 $GI_HOME/lib/libserver11.a kfdp.o
rw-rw-rw- 10000/1026  271741 Nov 15 13:29 2010 kfdp.o
[usax02w] $ ar -t -v -X32_64 $GI_HOME/lib/libserver11.a kfkio.o
rw-rw-rw- 10000/1026  103575 Nov 15 13:29 2010 kfkio.o
[usax02w] $ ar -t -v -X32_64 $GI_HOME/lib/libserver11.a kfksubs.o
rw-rw-rw- 10000/1026  166215 Nov 15 13:29 2010 kfksubs.o
 
 
 Below is the info from RDBMS_HOME
 
[usax02w] $ echo $ORACLE_HOME
/u01/apps/oracle/product/11.2.0/db_1
[usax02w] $ ar -t -v -X32_64 $ORACLE_HOME/lib/libserver11.a kfd.o
rw-rw-rw- 10000/1026  393236 Nov 15 13:29 2010 kfd.o
[usax02w] $ ar -t -v -X32_64 $ORACLE_HOME/lib/libserver11.a kfdp.o
rw-rw-rw- 10000/1026  271741 Nov 15 13:29 2010 kfdp.o
[usax02w] $ ar -t -v -X32_64 $ORACLE_HOME/lib/libserver11.a kfkio.o
rw-rw-rw- 10000/1026  103575 Nov 15 13:29 2010 kfkio.o
[usax02w] $ ar -t -v -X32_64 $ORACLE_HOME/lib/libserver11.a kfksubs.o
rw-rw-rw- 10000/1026  166215 Nov 15 13:29 2010 kfksubs.o
 
 
Regards,
Prathap
<strong>*** 12/22/10 08:01 pm *** (CHG: Sta->16)</strong>
<strong>*** 12/22/10 08:25 pm ***</strong>
<strong>*** 12/23/10 01:48 am ***</strong>
<strong>*** 12/23/10 02:46 am ***</strong>
<strong>*** 12/23/10 06:25 am *** (CHG: Sta->11)</strong>
<strong>*** 12/23/10 06:25 am ***</strong>
<strong>*** 12/23/10 06:26 am *** </strong>
<strong>*** 12/23/10 06:26 am ***</strong>
<strong>*** 12/24/10 01:43 am *** </strong>
<strong>*** 12/24/10 01:43 am ***</strong>
<strong>*** 12/27/10 11:33 am ***</strong>
<strong>*** 12/27/10 11:45 am ***</strong>
<strong>*** 12/27/10 11:51 am ***</strong>
<strong>*** 12/27/10 12:22 pm *** ESCALATED</strong>
<strong>*** 12/27/10 12:22 pm ***</strong>
<strong>*** 12/27/10 12:29 pm ***</strong>
<strong>*** 12/28/10 12:42 am *** (CHG: Sta->30)</strong>
<strong>*** 12/28/10 12:42 am ***</strong>
<strong>*** 12/28/10 05:00 am *** (CHG: Sta->16)</strong>
<strong>*** 12/28/10 05:00 am ***</strong>
<strong>*** 12/28/10 05:08 am *** (CHG: Sta->11)</strong>
<strong>*** 12/28/10 09:37 am ***</strong>
<strong>*** 12/29/10 02:51 am ***</strong>
<strong>*** 12/31/10 03:05 am ***</strong>
<strong>*** 01/02/11 08:28 pm ***</strong>
<strong>*** 01/04/11 01:43 am *** (CHG: Sta->30)</strong>
<strong>*** 01/04/11 01:43 am ***</strong>
<strong>*** 01/04/11 01:54 am ***</strong>
<strong>*** 01/04/11 04:50 am *** (CHG: Sta->11)</strong>
<strong>*** 01/04/11 04:50 am ***</strong>
<strong>*** 01/05/11 01:26 am *** (CHG: Sta->30)</strong>
<strong>*** 01/05/11 01:26 am ***</strong>
<strong>*** 01/10/11 10:46 am ***</strong>
<strong>*** 01/10/11 10:46 am *** (CHG: Sta->11)</strong>
<strong>*** 01/11/11 03:14 am ***</strong>
<strong>*** 01/13/11 11:32 pm ***</strong>
RELEASE NOTES:
]]  kfk SO is deleted, while there are still allocated sessions.
 
 
REDISCOVERY INFORMATION:
 The following error, even with fix 10051315:
 
 WARNING: IO Failed. group:1 disk(number.incarnation):5.0xe0d14bb7 
 disk_path:/dev/ASM_1457_4 
          AU:75811 disk_offset(bytes):79494299648 io_size:8192 operation:Read 
 type:synchronous 
          result:I/O error process_id:2338940 
          subsys:System iop:0x110939310 bufp:0x70000016f2ec000 
 osderr:0x434c5344 osderr1:0x0
WORKAROUND:
None
<strong>*** 01/13/11 11:44 pm *** </strong>
<strong>*** 01/13/11 11:44 pm *** </strong>
<strong>*** 01/13/11 11:44 pm *** (CHG: Sta->80)</strong>
<strong>*** 01/16/11 11:05 pm ***</strong>
<strong>*** 01/16/11 11:17 pm ***</strong>
<strong>*** 01/16/11 11:36 pm ***</strong>
<strong>*** 01/17/11 12:01 am ***</strong>
<strong>*** 01/17/11 07:09 am ***</strong>
<strong>*** 01/17/11 07:11 am ***</strong>
<strong>*** 01/17/11 09:25 am ***</strong>
<strong>*** 01/17/11 10:16 am ***</strong>
<strong>*** 01/17/11 11:14 pm ***</strong>
<strong>*** 01/18/11 05:06 am ***</strong>
<strong>*** 01/18/11 11:47 am ***</strong>
<strong>*** 01/18/11 11:52 pm ***</strong>
<strong>*** 01/19/11 02:05 am ***</strong>
<strong>*** 01/19/11 05:39 am ***</strong>
<strong>*** 01/19/11 05:45 am ***</strong>
<strong>*** 01/19/11 07:43 am ***</strong>
<strong>*** 01/19/11 08:44 am ***</strong>
<strong>*** 01/19/11 06:12 pm ***</strong>
<strong>*** 01/19/11 06:14 pm ***</strong>
<strong>*** 01/19/11 10:53 pm ***</strong>
<strong>*** 01/20/11 12:11 am ***</strong>
<strong>*** 01/20/11 04:04 am ***</strong>
<strong>*** 01/20/11 06:11 am ***</strong>
<strong>*** 01/20/11 06:59 am ***</strong>
<strong>*** 01/20/11 09:13 am ***</strong>
<strong>*** 01/20/11 10:44 am ***</strong>
<strong>*** 01/20/11 10:44 am ***</strong>
<strong>*** 01/20/11 11:00 am ***</strong>
<strong>*** 01/20/11 11:38 am ***</strong>
<strong>*** 01/20/11 04:58 pm ***</strong>
<strong>*** 01/21/11 04:05 am ***</strong>
<strong>*** 01/24/11 11:33 am ***</strong>
<strong>*** 01/25/11 02:17 am ***</strong>
<strong>*** 01/27/11 02:58 am ***</strong>
<strong>*** 01/27/11 03:16 am ***</strong>
<strong>*** 01/27/11 03:37 am ***</strong>
<strong>*** 01/27/11 03:49 am ***</strong>
<strong>*** 02/02/11 04:37 am ***</strong>
<strong>*** 02/04/11 08:25 pm ***</strong>
<strong>*** 02/05/11 02:46 am ***</strong>
<strong>*** 02/05/11 02:58 am ***</strong>
<strong>*** 02/05/11 02:59 am ***</strong>
<strong>*** 02/05/11 02:29 pm ***</strong>
<strong>*** 02/05/11 07:19 pm ***</strong>
<strong>*** 02/05/11 09:37 pm ***</strong>
<strong>*** 02/07/11 01:37 am ***</strong>
<strong>*** 02/07/11 06:14 am ***</strong>
<strong>*** 02/07/11 12:35 pm ***</strong>
<strong>*** 02/07/11 06:46 pm ***</strong>
<strong>*** 02/07/11 08:33 pm ***</strong>
<strong>*** 02/08/11 01:52 pm ***</strong>
<strong>*** 02/08/11 02:42 pm ***</strong>
<strong>*** 02/08/11 10:32 pm ***</strong>
<strong>*** 02/09/11 11:51 pm ***</strong>
<strong>*** 02/10/11 08:56 am ***</strong>
<strong>*** 02/10/11 08:59 am ***</strong>
<strong>*** 02/10/11 09:30 am ***</strong>
<strong>*** 02/11/11 11:52 pm ***</strong>
<strong>*** 02/12/11 05:10 pm ***</strong>
<strong>*** 02/15/11 02:55 am ***</strong>
<strong>*** 02/15/11 10:13 am ***</strong>
<strong>*** 02/16/11 01:07 am ***</strong>
<strong>*** 02/16/11 06:34 am ***</strong>
<strong>*** 02/18/11 01:39 am ***</strong>
<strong>*** 02/18/11 01:40 am ***</strong>
<strong>*** 02/24/11 07:20 am ***</strong>
<strong>*** 02/24/11 07:35 am ***</strong>
<strong>*** 02/25/11 12:34 am ***</strong>
<strong>*** 03/02/11 07:59 am ***</strong>
<strong>*** 03/02/11 08:25 am ***</strong>
<strong>*** 03/03/11 01:22 am ***</strong>
<strong>*** 03/03/11 03:34 pm ***</strong>
<strong>*** 03/07/11 11:54 am ***</strong>
<strong>*** 03/08/11 08:53 pm ***</strong>
<strong>*** 03/09/11 10:44 pm ***</strong>
<strong>*** 04/20/11 01:17 pm ***</strong>
<strong>*** 04/21/11 09:34 am ***</strong>
<strong>*** 04/21/11 01:46 pm ***</strong>
<strong>*** 04/22/11 03:47 pm ***</strong>
<strong>*** 04/29/11 12:33 pm ***</strong>
<strong>*** 04/29/11 01:21 pm ***</strong>
<strong>*** 05/02/11 07:53 am ***</strong>
<strong>*** 05/03/11 01:12 am ***</strong>
<strong>*** 05/03/11 01:37 am ***</strong>
<strong>*** 05/03/11 02:11 am ***</strong>
<strong>*** 05/11/11 03:00 am ***</strong>
<strong>*** 05/11/11 03:44 am ***</strong>
<strong>*** 05/16/11 08:07 am ***</strong>
<strong>*** 05/17/11 11:31 am ***</strong>
<strong>*** 05/17/11 11:34 am ***</strong>
<strong>*** 05/17/11 03:14 pm ***</strong>
<strong>*** 05/17/11 03:16 pm ***</strong>
<strong>*** 05/18/11 06:00 am ***</strong>
<strong>*** 05/18/11 06:11 am ***</strong>
<strong>*** 05/18/11 08:46 am ***</strong>
<strong>*** 06/09/11 12:44 pm ***</strong>
<strong>*** 06/10/11 10:21 am ***</strong>
<strong>*** 06/10/11 10:21 am ***</strong>
<strong>*** 06/11/11 04:44 am ***</strong>
<strong>*** 06/14/11 10:14 pm ***</strong>
<strong>*** 06/17/11 12:33 pm ***</strong>
<strong>*** 07/04/11 01:09 pm ***</strong>
<strong>*** 07/06/11 04:03 pm ***</strong>
<strong>*** 07/06/11 04:56 pm ***</strong>
<strong>*** 07/08/11 11:47 am ***</strong>
<strong>*** 07/08/11 12:16 pm ***</strong>
<strong>*** 07/12/11 07:28 am ***</strong>
<strong>*** 07/14/11 07:58 pm *** </strong>
<strong>*** 07/17/11 05:29 am ***</strong>
<strong>*** 07/17/11 05:30 am ***</strong>
<strong>*** 07/18/11 03:23 pm ***</strong>
<strong>*** 07/26/11 03:20 pm ***</strong>
<strong>*** 07/26/11 03:23 pm ***</strong>
<strong>*** 07/27/11 03:13 am ***</strong>
<strong>*** 07/27/11 03:15 am ***</strong>
<strong>*** 07/27/11 07:33 am ***</strong>
<strong>*** 08/02/11 01:34 pm ***</strong>
<strong>*** 08/03/11 01:03 am *** </strong>
<strong>*** 08/03/11 01:03 am ***</strong>
<strong>*** 08/03/11 01:15 am *** </strong>
<strong>*** 08/03/11 01:15 am ***</strong>
<strong>*** 08/05/11 08:00 am ***</strong>
<strong>*** 08/05/11 08:11 am ***</strong>
<strong>*** 08/05/11 10:42 am ***</strong>
<strong>*** 08/11/11 01:22 am ***</strong>
<strong>*** 08/12/11 04:00 am ***</strong>
<strong>*** 08/12/11 10:03 am ***</strong>
<strong>*** 08/18/11 12:46 pm ***</strong>
<strong>*** 08/22/11 12:14 pm ***</strong>
<strong>*** 09/07/11 04:49 am ***</strong>
<strong>*** 09/09/11 02:55 pm ***</strong>
<strong>*** 09/14/11 02:40 pm ***</strong>
<strong>*** 10/14/11 02:15 am ***</strong>
<strong>*** 10/14/11 02:15 am *** ESCALATION -> CLOSED</strong>
<strong>*** 10/14/11 02:15 am *** (CHG: Sta->90)</strong>
<strong>*** 10/14/11 02:21 am *** </strong>
<strong>*** 10/14/11 02:21 am ***</strong>
<strong>*** 10/14/11 09:56 am ***</strong>
<strong>*** 11/01/11 01:55 am ***</strong>
<strong>*** 11/01/11 10:49 am ***</strong>
<strong>*** 11/01/11 10:49 am ***</strong>
<strong>*** 11/27/11 01:15 am ***</strong>
<strong>*** 12/01/11 09:11 am ***</strong>
<strong>*** 01/17/12 03:29 pm ***</strong>
<strong>*** 01/23/12 08:26 pm ***</strong>
<strong>*** 01/23/12 08:26 pm ***</strong>
<strong>*** 03/14/12 01:07 am ***</strong>
<strong>*** 03/18/12 11:22 pm ***</strong>
<strong>*** 03/22/12 12:44 am ***</strong>
<strong>*** 04/02/12 06:10 am ***</strong>
<strong>*** 04/24/12 10:45 am ***</strong>
<strong>*** 01/26/13 08:03 am ***</strong>
<strong>*** 01/31/13 07:35 am ***</strong>
<strong>*** 02/24/13 11:27 pm ***</strong>
<strong>*** 04/16/13 02:14 am ***</strong>
<strong>*** 04/19/13 07:23 am ***</strong>
<strong>*** 05/12/13 09:12 pm ***</strong>
<strong>*** 05/20/13 06:28 am ***</strong>
<strong>*** 06/25/13 01:16 am ***</strong>
<strong>*** 07/08/13 09:41 pm ***</strong>
<strong>*** 07/09/13 09:44 pm ***</strong>
<strong>*** 07/09/13 10:24 pm ***</strong>
<strong>*** 07/17/13 03:02 am ***</strong>
<strong>*** 07/18/13 02:35 am ***</strong>
<strong>*** 08/12/13 03:54 am ***</strong>
<strong>*** 08/20/13 12:21 am ***</strong>
<strong>*** 09/30/13 12:26 pm ***</strong>
<strong>*** 10/23/13 05:08 pm ***</strong>
<strong>*** 10/29/13 08:22 am ***</strong>
<strong>*** 10/29/13 09:56 am ***</strong>
<strong>*** 10/29/13 09:56 am ***</strong>
<strong>*** 12/18/13 03:38 am ***</strong>
<strong>*** 01/23/14 09:24 pm ***</strong>
<strong>*** 02/11/14 09:58 am ***</strong>
<strong>*** 02/24/14 03:11 am ***</strong>
<strong>*** 02/24/14 06:02 am ***</strong>
<strong>*** 02/24/14 12:34 pm ***</strong>
<strong>*** 02/24/14 03:58 pm ***</strong>
<strong>*** 02/25/14 02:28 am ***</strong>
<strong>*** 03/18/14 04:34 am ***</strong>
<strong>*** 03/18/14 04:55 am ***</strong>
<strong>*** 03/18/14 05:09 am ***</strong>
<strong>*** 03/18/14 10:37 pm ***</strong>
<strong>*** 03/19/14 12:39 am ***</strong>
로그인 후 복사
본 웹사이트의 성명
본 글의 내용은 네티즌들의 자발적인 기여로 작성되었으며, 저작권은 원저작자에게 있습니다. 본 사이트는 이에 상응하는 법적 책임을 지지 않습니다. 표절이나 침해가 의심되는 콘텐츠를 발견한 경우 admin@php.cn으로 문의하세요.

핫 AI 도구

Undresser.AI Undress

Undresser.AI Undress

사실적인 누드 사진을 만들기 위한 AI 기반 앱

AI Clothes Remover

AI Clothes Remover

사진에서 옷을 제거하는 온라인 AI 도구입니다.

Undress AI Tool

Undress AI Tool

무료로 이미지를 벗다

Clothoff.io

Clothoff.io

AI 옷 제거제

AI Hentai Generator

AI Hentai Generator

AI Hentai를 무료로 생성하십시오.

더보기

인기 기사

R.E.P.O. 에너지 결정과 그들이하는 일 (노란색 크리스탈)
2 몇 주 전 By 尊渡假赌尊渡假赌尊渡假赌
스플릿 소설을이기는 데 얼마나 걸립니까?
1 몇 달 전 By DDD
R.E.P.O. 최고의 그래픽 설정
2 몇 주 전 By 尊渡假赌尊渡假赌尊渡假赌
어 ass 신 크리드 그림자 : 조개 수수께끼 솔루션
1 몇 주 전 By DDD
R.E.P.O. 아무도들을 수없는 경우 오디오를 수정하는 방법
2 몇 주 전 By 尊渡假赌尊渡假赌尊渡假赌
더보기

뜨거운 도구

메모장++7.3.1

메모장++7.3.1

사용하기 쉬운 무료 코드 편집기

SublimeText3 중국어 버전

SublimeText3 중국어 버전

중국어 버전, 사용하기 매우 쉽습니다.

스튜디오 13.0.1 보내기

스튜디오 13.0.1 보내기

강력한 PHP 통합 개발 환경

드림위버 CS6

드림위버 CS6

시각적 웹 개발 도구

SublimeText3 Mac 버전

SublimeText3 Mac 버전

신 수준의 코드 편집 소프트웨어(SublimeText3)

더보기

뜨거운 주제

Gmail 이메일의 로그인 입구는 어디에 있나요?
7404
15
자바 튜토리얼
1630
14
Cakephp 튜토리얼
1358
52
라라벨 튜토리얼
1268
25
PHP 튜토리얼
1218
29
더보기
Related knowledge
Alter Table 문을 사용하여 MySQL에서 테이블을 어떻게 변경합니까? Alter Table 문을 사용하여 MySQL에서 테이블을 어떻게 변경합니까? Mar 19, 2025 pm 03:51 PM

이 기사는 MySQL의 Alter Table 문을 사용하여 열 추가/드롭 테이블/열 변경 및 열 데이터 유형 변경을 포함하여 테이블을 수정하는 것에 대해 설명합니다.

MySQL 연결에 대한 SSL/TLS 암호화를 어떻게 구성합니까? MySQL 연결에 대한 SSL/TLS 암호화를 어떻게 구성합니까? Mar 18, 2025 pm 12:01 PM

기사는 인증서 생성 및 확인을 포함하여 MySQL에 대한 SSL/TLS 암호화 구성에 대해 설명합니다. 주요 문제는 자체 서명 인증서의 보안 영향을 사용하는 것입니다. [문자 수 : 159]

MySQL에서 큰 데이터 세트를 어떻게 처리합니까? MySQL에서 큰 데이터 세트를 어떻게 처리합니까? Mar 21, 2025 pm 12:15 PM

기사는 MySQL에서 파티셔닝, 샤딩, 인덱싱 및 쿼리 최적화를 포함하여 대규모 데이터 세트를 처리하기위한 전략에 대해 설명합니다.

인기있는 MySQL GUI 도구는 무엇입니까 (예 : MySQL Workbench, Phpmyadmin)? 인기있는 MySQL GUI 도구는 무엇입니까 (예 : MySQL Workbench, Phpmyadmin)? Mar 21, 2025 pm 06:28 PM

기사는 MySQL Workbench 및 Phpmyadmin과 같은 인기있는 MySQL GUI 도구에 대해 논의하여 초보자 및 고급 사용자를위한 기능과 적합성을 비교합니다. [159 자].

드롭 테이블 문을 사용하여 MySQL에서 테이블을 어떻게 드롭합니까? 드롭 테이블 문을 사용하여 MySQL에서 테이블을 어떻게 드롭합니까? Mar 19, 2025 pm 03:52 PM

이 기사에서는 Drop Table 문을 사용하여 MySQL에서 테이블을 떨어 뜨리는 것에 대해 설명하여 예방 조치와 위험을 강조합니다. 백업 없이는 행동이 돌이킬 수 없으며 복구 방법 및 잠재적 생산 환경 위험을 상세하게합니다.

JSON 열에서 인덱스를 어떻게 생성합니까? JSON 열에서 인덱스를 어떻게 생성합니까? Mar 21, 2025 pm 12:13 PM

이 기사에서는 PostgreSQL, MySQL 및 MongoDB와 같은 다양한 데이터베이스에서 JSON 열에서 인덱스를 작성하여 쿼리 성능을 향상시킵니다. 특정 JSON 경로를 인덱싱하는 구문 및 이점을 설명하고 지원되는 데이터베이스 시스템을 나열합니다.

외국 키를 사용하여 관계를 어떻게 표현합니까? 외국 키를 사용하여 관계를 어떻게 표현합니까? Mar 19, 2025 pm 03:48 PM

기사는 외국 열쇠를 사용하여 데이터베이스의 관계를 나타내고 모범 사례, 데이터 무결성 및 피할 수있는 일반적인 함정에 중점을 둡니다.

일반적인 취약점 (SQL 주입, 무차별 적 공격)에 대해 MySQL을 어떻게 보호합니까? 일반적인 취약점 (SQL 주입, 무차별 적 공격)에 대해 MySQL을 어떻게 보호합니까? Mar 18, 2025 pm 12:00 PM

기사는 준비된 명령문, 입력 검증 및 강력한 암호 정책을 사용하여 SQL 주입 및 무차별 적 공격에 대한 MySQL 보안에 대해 논의합니다 (159 자)

See all articles