Rman Backup&ORA-00245/RMAN-08132-程序员宅基地

技术标签： 网络  操作系统  数据库  

日常监控备份发现，有个库归档备份报错信息如下：
channel ch01: finished piece 1 at 2015-08-04 09:42:46
piece handle=al_4171_1_886843941 tag=TAG20150804T093221 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch01: backup set complete, elapsed time: 00:10:25
channel ch00: finished piece 1 at 2015-08-04 09:45:56
piece handle=al_4170_1_886843941 tag=TAG20150804T093221 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:13:35
Finished backup at 2015-08-04 09:45:56

Starting Control File and SPFILE Autobackup at 2015-08-04 09:45:57
piece handle=c-233800172-20150804-02 comment=API Version 2.0,MMS Version 5.0.0.0
Finished Control File and SPFILE Autobackup at 2015-08-04 09:46:22
ORA-00245: control file backup failed; target is likely on a local file system

RMAN-08132: WARNING: cannot update recovery area reclaimable file list

released channel: ch00
released channel: ch01
allocated channel: ch00
channel ch00: SID=295 instance=sscpdb2 device type=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.6 (2014042414)

Starting backup at 2015-08-04 09:46:27
channel ch00: starting full datafile backup set
channel ch00: specifying datafile(s) in backup set
including current control file in backup set
channel ch00: starting piece 1 at 2015-08-04 09:46:30
channel ch00: finished piece 1 at 2015-08-04 09:46:56
piece handle=cntrl_4173_1_886844787 tag=TAG20150804T094627 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:00:26
Finished backup at 2015-08-04 09:46:56

Starting Control File and SPFILE Autobackup at 2015-08-04 09:46:56
piece handle=c-233800172-20150804-03 comment=API Version 2.0,MMS Version 5.0.0.0
Finished Control File and SPFILE Autobackup at 2015-08-04 09:47:21

released channel: ch00
ORA-00245: control file backup failed; target is likely on a local file system
RMAN-08132: WARNING: cannot update recovery area reclaimable file list

RMAN> RMAN> 

Recovery Manager complete.
Script /usr/openv/nbuscripts/sscp-db2_oracle_db_arch_backup.sh
==== ended successfully on Tue Aug 4 09:47:25 CST 2015 ====


从报错日志可以看出数据库文件，归档日志，spfile和controlfile都备份完成，后面又出现一个controlfile失败，确实是控制文件快照备份失败的报错。


错误原因
RMAN creates a copy of the control file for read consistency, this is the snapshot controlfile. 
Due to the changes made to the controlfile backup mechanism in 11gR2 any instances 
in the cluster may write to the snapshot controlfile. Therefore, 
the snapshot controlfile file needs to be visible to all instances.
 
The same happens when a backup of the controlfile is created directly from 
sqlplus any instance in the cluster may write to the backup controfile file.
 
In 11gR2 onwards, the controlfile backup happens without holding the control file enqueue. 
For non-RAC database, this doesn't change anything. 
 
But, for RAC database, the snapshot controlfile location 
must be in a shared file system that will be accessible from all the nodes.
 
The snapshot controlfile MUST be  accessible by all nodes of a RAC database. 
文档表述rman的snapshot controlfile必须放在共享存储之上。


于是检查当前rman config环境：
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name SSCPDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabackup/sscpdb1/rman/20150316/sscpdb1_lev1_201503160300_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.4/db_1/dbs/snapcf_sscpdb1.f'; # default


RMAN> 


解决方法
The snapshot controlfile MUST be accessible by all nodes of a RAC database, 
if the snapshot controlfile does not reside in on a shared device this error will raise.
 
1. Check the snapshot controlfile location:
RMAN> show all;
2. Configure the snapshot controlfile to a shared disk:
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '<shared_disk>/snapcf_<DBNAME>.f';


处理结果：
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orabackup/snpcontrlfile/snapcf_sscpdb.f';
new RMAN configuration parameters:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orabackup/snpcontrlfile/snapcf_sscpdb.f';
new RMAN configuration parameters are successfully stored


RMAN>  show all;
RMAN configuration parameters for database with db_unique_name SSCPDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabackup/sscpdb1/rman/20150316/sscpdb1_lev1_201503160300_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orabackup/snpcontrlfile/snapcf_sscpdb.f';


参考我2013年的帖子：
http://blog.itpub.net/13750068/viewspace-1064577/
Starting backup at 2015-08-04 10:05:23
current log archived
skipping archived logs of thread 1 from sequence 9157 to 9191; already backed up
skipping archived logs of thread 2 from sequence 9619 to 9653; already backed up
channel ch00: starting archived log backup set
channel ch00: specifying archived log(s) in backup set
input archived log thread=1 sequence=9192 RECID=18846 STAMP=886845932
channel ch00: starting piece 1 at 2015-08-04 10:05:33
channel ch01: starting archived log backup set
channel ch01: specifying archived log(s) in backup set
input archived log thread=2 sequence=9654 RECID=18845 STAMP=886845927
channel ch01: starting piece 1 at 2015-08-04 10:05:33
channel ch01: finished piece 1 at 2015-08-04 10:06:28
piece handle=al_4179_1_886845933 tag=TAG20150804T100533 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch01: backup set complete, elapsed time: 00:00:55

channel ch00: finished piece 1 at 2015-08-04 10:07:48
piece handle=al_4178_1_886845933 tag=TAG20150804T100533 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:02:15
Finished backup at 2015-08-04 10:07:48

Starting Control File and SPFILE Autobackup at 2015-08-04 10:07:48
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ch00 channel at 08/04/2015 10:07:49
ORA-01580: error creating control backup file /orabackup/snpcontrlfile/snapcf_sscpdb.f
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
Additional information: 1


检查主机：
[root@sscp-db2 ~]# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup01-LogVol00
                     153724820  38539792 107250260  27% /
/dev/cciss/c0d0p1       101086     21972     73895  23% /boot
tmpfs                 65977152    450044  65527108   1% /dev/shm
/dev/mapper/arch_mpath2
                     206424760  27722528 168216472  15% /arch2
135.148.73.45:/arch1 206424768  29320640 166618368  15% /arch1
135.148.73.45:/orabackup
                     464455456    202880 440659616   1% /orabackup
[root@sscp-db2 ~]# cat /etc/fstab
/dev/VolGroup01/LogVol00 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
/dev/VolGroup01/LogVol01 swap                    swap    defaults        0 0
/dev/mapper/arch_mpath2 /arch2                  ext3    defaults        0 0
[root@sscp-db2 ~]# cat /etc/exports
/arch2 135.148.73.45(rw,sync)
[root@sscp-db2 ~]# umount /orabackup
umount: /orabackup: device is busy
umount: /orabackup: device is busy
[root@sscp-db2 ~]# fuser -cuv /orabackup
                     USER        PID ACCESS COMMAND
/orabackup:          root      15379 ..c.. (root)bash
                     root      27441 ..c.. (root)bash
                     root      27656 ..c.. (root)su
                     root      32497 ..c.. (root)bash
[root@sscp-db2 ~]# fuser -ck /orabackup
/orabackup:          15379c 27441c 27656c 32497c
[root@sscp-db2 ~]# 
[root@sscp-db2 ~]# umount /orabackup
[root@sscp-db2 ~]# df 
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup01-LogVol00
                     153724820  38545720 107244332  27% /
/dev/cciss/c0d0p1       101086     21972     73895  23% /boot
tmpfs                 65977152    450044  65527108   1% /dev/shm
/dev/mapper/arch_mpath2
                     206424760  27722528 168216472  15% /arch2
135.148.73.45:/arch1 206424768  30184288 165754720  16% /arch1
[root@sscp-db2 ~]# 
[root@sscp-db2 ~]# mount -t nfs -o rw,bg,hard,nointr,rsize=32768,wsize=32768,nolock,proto=tcp,actimeo=0,vers=3,timeo=600 135.148.73.45:/orabackup /orabackup
[root@sscp-db2 ~]# 
[root@sscp-db2 ~]# df 
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup01-LogVol00
                     153724820  38547676 107242376  27% /
/dev/cciss/c0d0p1       101086     21972     73895  23% /boot
tmpfs                 65977152    450044  65527108   1% /dev/shm
/dev/mapper/arch_mpath2
                     206424760  27722528 168216472  15% /arch2
135.148.73.45:/arch1 206424768  30184288 165754720  16% /arch1
135.148.73.45:/orabackup
                     464455456    202880 440659616   1% /orabackup
[root@sscp-db2 ~]# exit
logout


重新配置rman：
RMAN>  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orabackup/spcontf/snapcf_sscpdb.f';
old RMAN configuration parameters:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orabackup/snpcontrlfile/snapcf_sscpdb.f';
new RMAN configuration parameters:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orabackup/spcontf/snapcf_sscpdb.f';
new RMAN configuration parameters are successfully stored
RMAN> 
RMAN> show all;
RMAN configuration parameters for database with db_unique_name SSCPDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabackup/sscpdb1/rman/20150316/sscpdb1_lev1_201503160300_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orabackup/spcontf/snapcf_sscpdb.f';
Starting backup at 2015-08-04 10:46:17
channel ch00: starting full datafile backup set
channel ch00: specifying datafile(s) in backup set
including current control file in backup set
channel ch00: starting piece 1 at 2015-08-04 10:46:20
channel ch00: finished piece 1 at 2015-08-04 10:46:35
piece handle=cntrl_4184_1_886848377 tag=TAG20150804T104617 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:00:15
Finished backup at 2015-08-04 10:46:35


Starting Control File and SPFILE Autobackup at 2015-08-04 10:46:35
piece handle=c-233800172-20150804-05 comment=API Version 2.0,MMS Version 5.0.0.0
Finished Control File and SPFILE Autobackup at 2015-08-04 10:47:00
released channel: ch00
RMAN> RMAN> 
Recovery Manager complete.
Script /usr/openv/nbuscripts/sscp-db2_oracle_db_arch_backup.sh
==== ended successfully on Tue Aug 4 10:47:08 CST 2015 ====

参考：
Mount Options for Oracle files when used with NFS on NAS devices (文档 ID 359515.1)

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 12.1.0.1 [Release 10.1 to 12.1]
Solaris Cluster - Version 3.3U1 5/11 to 3.3U1 5/11 [Release 3.3]
Information in this document applies to any platform.
Oracle Clusterware, Oracle Real Application Clusters, NAS

Purpose

The options with which the NAS systems should be mounted are described. This note does not cover the new dNFS feature that was introduced in 11g.

Scope

This document is relevant to all environments using Oracle Clusterware & RAC.

Details

RAC including RACone and single instance RAC

In the table below
  • Binaries is the shared mount points where the Oracle Home and CRS_HOME is installed.
  • Datafiles includes Online Logs, Controlfile and Datafiles
  • nfsvers and vers are identical on those OS platforms that has nfsvers.  The ver option is an alternative to the nfsvers option. It is included for compatibility with other operating systems
  • Please note that the mount options on each of the following cells are applicable only to those type of files listed in the column heading.
  • For RMAN backup sets, image copies, and Data Pump dump files, the "NOAC" mount option should not be specified - that is because RMAN and Data Pump do not check this option and specifying this can adversely affect performance.

 

Operating System

Mount options for    Binaries ##

Mount options for Oracle Datafiles Mount options for CRS Voting Disk and OCR
Sun Solaris *

rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,noac,

vers=3,suid

rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,noac,
forcedirectio, vers=3 		rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,vers=3,
noac,forcedirectio
AIX (5L) **

rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,

vers=3,timeo=600

cio,rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,noac,
vers=3,timeo=600

cio,rw,bg,hard,intr,rsize=32768,
wsize=32768,tcp,noac,
vers=3,timeo=600

HPUX 11.23 ***  -- rw,bg,vers=3,proto=tcp,noac,
hard,nointr,timeo=600,
rsize=32768,wsize=32768,suid 		rw,bg,vers=3,proto=tcp,noac,
forcedirectio,hard,nointr,timeo=600,
rsize=32768,wsize=32768 		rw,bg,vers=3,proto=tcp,noac,
forcedirectio,hard,nointr,timeo=600
,rsize=32768,wsize=32768
Windows Not Supported Not Supported Not Supported
Linux x86
#
****

rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp, vers=3,
timeo=600, actimeo=0

rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,actimeo=0,
vers=3,timeo=600

rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,noac,actimeo=0,
vers=3,timeo=600

Linux x86-64 #
**** 		rw,bg,hard,nointr,rsize=32768,
 wsize=32768,tcp,vers=3,
timeo=600, actimeo=0 		rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,actimeo=0,
vers=3,timeo=600 		rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,noac,vers=3,
timeo=600,actimeo=0
Linux - Itanium rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,vers=3,
timeo=600, actimeo=0 		rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,actimeo=0,
vers=3,timeo=600 		rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,noac,vers=3,
timeo=600,actimeo=0

* NFS mount option “forcedirectio” is required on Solaris platforms when mounting the OCR/CRS files when using Oracle 10.1.0.4 or 10.2.0.2 or later (Oracle unpublished bug 4466428)
** AIX is only supported with NAS on AIX 5.3 TL04 and higher with Oracle 10.2.0.1 and later
*** NAS devices are only supported with HPUX 11.23 or higher ONLY 


# These mount options are for Linux kernels 2.6 and above. For older kernels please check Note 279393.1

## The stated mount options for binaries are applicable only if the ORACLE HOME is shared.

Due to Unpublished bug 5856342, it is necessary to use the following init.ora parameter when using NAS with all versions of RAC on Linux (x86 & X86-64 platforms) until 10.2.0.4. This bug is fixed and included in 10.2.0.4 patchset.
filesystemio_options = DIRECTIO

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/13750068/viewspace-1761109/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/13750068/viewspace-1761109/
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/cppg67031/article/details/100264685

智能推荐

从零开始搭建Hadoop_创建一个hadoop项目-程序员宅基地

文章浏览阅读331次。第一部分：准备工作1 安装虚拟机2 安装centos73 安装JDK以上三步是准备工作，至此已经完成一台已安装JDK的主机第二部分：准备３台虚拟机以下所有工作最好都在root权限下操作1 克隆上面已经有一台虚拟机了,现在对master进行克隆,克隆出另外2台子机;1.1 进行克隆21.2 下一步1.3 下一步1.4 下一步1.5 根据子机需要,命名和安装路径1.6 ..._创建一个hadoop项目

心脏滴血漏洞HeartBleed CVE-2014-0160深入代码层面的分析_heartbleed代码分析-程序员宅基地

文章浏览阅读1.7k次。心脏滴血漏洞HeartBleed CVE-2014-0160 是由heartbeat功能引入的，本文从深入码层面的分析该漏洞产生的原因_heartbleed代码分析

java读取ofd文档内容_ofd电子文档内容分析工具（分析文档、签章和证书）-程序员宅基地

文章浏览阅读1.4k次。前言ofd是国家文档标准，其对标的文档格式是pdf。ofd文档是容器格式文件，ofd其实就是压缩包。将ofd文件后缀改为.zip，解压后可看到文件包含的内容。ofd文件分析工具下载：点我下载。ofd文件解压后，可以看到如下内容： 对于xml文件，可以用文本工具查看。但是对于印章文件(Seal.esl)、签名文件(SignedValue.dat)就无法查看其内容了。本人开发一款ofd内容查看器，..._signedvalue.dat

基于FPGA的数据采集系统（一）_基于fpga的信息采集-程序员宅基地

文章浏览阅读1.8w次，点赞29次，收藏313次。整体系统设计本设计主要是对ADC和DAC的使用，主要实现功能流程为：首先通过串口向FPGA发送控制信号，控制DAC芯片tlv5618进行DA装换，转换的数据存在ROM中，转换开始时读取ROM中数据进行读取转换。其次用按键控制adc128s052进行模数转换100次，模数转换数据存储到FIFO中，再从FIFO中读取数据通过串口输出显示在pc上。其整体系统框图如下：图1：FPGA数据采集系统框图从图中可以看出，该系统主要包括9个模块：串口接收模块、按键消抖模块、按键控制模块、ROM模块、D.._基于fpga的信息采集

微服务 spring cloud zuul com.netflix.zuul.exception.ZuulException GENERAL-程序员宅基地

文章浏览阅读2.5w次。1.背景错误信息：-- [http-nio-9904-exec-5] o.s.c.n.z.filters.post.SendErrorFilter : Error during filteringcom.netflix.zuul.exception.ZuulException: Forwarding error at org.springframework.cloud..._com.netflix.zuul.exception.zuulexception

邻接矩阵-建立图-程序员宅基地

文章浏览阅读358次。1.介绍图的相关概念　　图是由顶点的有穷非空集和一个描述顶点之间关系-边（或者弧）的集合组成。通常，图中的数据元素被称为顶点，顶点间的关系用边表示，图通常用字母G表示，图的顶点通常用字母V表示，所以图可以定义为:　　G=(V,E)其中，V(G)是图中顶点的有穷非空集合，E(G)是V(G)中顶点的边的有穷集合1.1 无向图：图中任意两个顶点构成的边是没有方向的1.2 有向图：图中..._给定一个邻接矩阵未必能够造出一个图

随便推点

MDT2012部署系列之11 WDS安装与配置-程序员宅基地

文章浏览阅读321次。（十二）、WDS服务器安装通过前面的测试我们会发现，每次安装的时候需要加域光盘映像，这是一个比较麻烦的事情，试想一个上万个的公司，你天天带着一个光盘与光驱去给别人装系统，这将是一个多么痛苦的事情啊，有什么方法可以解决这个问题了？答案是肯定的，下面我们就来简单说一下。WDS服务器，它是Windows自带的一个免费的基于系统本身角色的一个功能，它主要提供一种简单、安全的通过网络快速、远程将Window..._doc server2012上通过wds+mdt无人值守部署win11系统.doc

python--xlrd/xlwt/xlutils_xlutils模块可以读xlsx吗-程序员宅基地

文章浏览阅读219次。python–xlrd/xlwt/xlutilsxlrd只能读取，不能改,支持 xlsx和xls 格式xlwt只能改，不能读xlwt只能保存为.xls格式xlutils能将xlrd.Book转为xlwt.Workbook，从而得以在现有xls的基础上修改数据，并创建一个新的xls，实现修改xlrd打开文件import xlrdexcel=xlrd.open_workbook('E:/test.xlsx') 返回值为xlrd.book.Book对象,不能修改获取sheett_xlutils模块可以读xlsx吗

关于新版本selenium定位元素报错：‘WebDriver‘ object has no attribute ‘find_element_by_id‘等问题_unresolved attribute reference 'find_element_by_id-程序员宅基地

文章浏览阅读8.2w次，点赞267次，收藏656次。运行Selenium出现'WebDriver' object has no attribute 'find_element_by_id'或AttributeError: 'WebDriver' object has no attribute 'find_element_by_xpath'等定位元素代码错误，是因为selenium更新到了新的版本，以前的一些语法经过改动。..............._unresolved attribute reference 'find_element_by_id' for class 'webdriver

DOM对象转换成jQuery对象转换与子页面获取父页面DOM对象-程序员宅基地

文章浏览阅读198次。一：模态窗口//父页面JSwindow.showModalDialog(ifrmehref, window, 'dialogWidth:550px;dialogHeight:150px;help:no;resizable:no;status:no');//子页面获取父页面DOM对象//window.showModalDialog的DOM对象var v=parentWin..._jquery获取父window下的dom对象

什么是算法？-程序员宅基地

文章浏览阅读1.7w次，点赞15次，收藏129次。算法（algorithm）是解决一系列问题的清晰指令，也就是，能对一定规范的输入，在有限的时间内获得所要求的输出。 简单来说，算法就是解决一个问题的具体方法和步骤。算法是程序的灵 魂。二、算法的特征1.可行性 算法中执行的任何计算步骤都可以分解为基本可执行的操作步，即每个计算步都可以在有限时间里完成（也称之为有效性） 算法的每一步都要有确切的意义，不能有二义性。例如“增加x的值”，并没有说增加多少，计算机就无法执行明确的运算。 _算法

【网络安全】网络安全的标准和规范_网络安全标准规范-程序员宅基地

文章浏览阅读1.5k次，点赞18次，收藏26次。网络安全的标准和规范是网络安全领域的重要组成部分。它们为网络安全提供了技术依据，规定了网络安全的技术要求和操作方式，帮助我们构建安全的网络环境。下面，我们将详细介绍一些主要的网络安全标准和规范，以及它们在实际操作中的应用。_网络安全标准规范

推荐文章

热门文章

相关标签