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

智能推荐

Zotero6.0来了，内容丰富，适合初学者（插件安装，翻译器更新）_v1.4.2 latest updated for zotero 6-程序员宅基地

文章浏览阅读3.1w次，点赞52次，收藏120次。Zotero，一款非常好的文献管理软件，丰富的插件库，以及更新后的PDF阅读器，给正在做科研的你带来无限的可能！！！这篇文章可以解决你在使用时候的所有问题，插件安装，翻译器更新，抓取学位论文等等_v1.4.2 latest updated for zotero 6

float拆分_float 详细使用说明，高度塌陷等问题-程序员宅基地

文章浏览阅读146次。float在网页布局作用很大， 但也不需要如此泛用。 最后结果只有是清除浮动都不知道在什么地方下手。 这几天也自己查找了各个关于float资料， 加深对其认识，免得出现不必要的麻烦！浮动介绍(2篇)float 是 css 的定位属性。在传统的印刷布局中，文本可以按照需要围绕图片。一般把这种方式称为“文本环绕”。在网页设计中，应用了CSS的float属性的页面元素就像在印刷布局里面的被文字包围的图片..._按钮样式 float 怎么分开

洪涝有源淹没算法及淹没结果分析【转】-程序员宅基地

文章浏览阅读1.4k次。http://blog.csdn.net/giser_whu/article/details/41288761洪涝模拟仿真的实现方法主要有两种：一种是基于水动力学的洪水演进模型；另一种是基于DEM的洪水淹没分析。具体分析如下：我是GIS从业者，从我们的专业角度出发，选择基于DEM的洪水淹没分析来做洪涝的模拟仿真。而基于DEM的洪水淹没分析方法主要分为有源淹没和无源淹没。本篇...

Java Selenium Actions模拟鼠标拖动dragAndDrop总结_selenium actions.draganddropby-程序员宅基地

文章浏览阅读1.2w次。鼠标拖动APIActions action = new Actions(webdriver);##source-要拖动的元素A，target-拖动元素A到达的目标元素action.dragAndDrop(source, target);##source-要拖动的元素A,拖动元素移动多少,标准以元素A左上角为准,拖动元素相对元素A移到右边是x是正值，左边是负值，拖动元素相对元素A移到上_selenium actions.draganddropby

amd显卡RX560控制功耗问题_a卡560功耗-程序员宅基地

文章浏览阅读4.2w次。前言现在显卡市场可以说就是 amd 和 英伟达 的双雄会。经过漫长的发展，英伟达显然技高一筹，在核心技术上牢牢压了AMD一头。价格就是最有力的证明。比如说今天我要说的RX560D。都说rx560可以媲美1050ti，但是却比1050ti便宜了一半，为什么？是amd为了消费者，所以他们有商业道德，不屑于赚取多余的金钱？我想应该不会有这样的商家存在吧。遗憾的是rx560只要不是xt，或..._a卡560功耗

springboot停车场车辆定位管理可视化分析系统的设计与实现 毕业设计-附源码101702-程序员宅基地

文章浏览阅读111次。该系统采用Springboot框架、JSP技术、Ajax技术进行业务系统的编码及其开发，实现了本系统的全部功能。本系统采取组件化的方式对系统进行拆分，并对数据库中各个表的增删查改、表与表之间的约束关系进行分析与设计，最终实现符合用户需求功能的商业级应用。

随便推点

wps生成正态分布的随机数_如何用excel批量生成正态分布的随机数？-程序员宅基地

文章浏览阅读3.4k次。昨天的文章提到《如何不留痕迹做批量 "假"数据？》提到用rand函数批量生成随机数，这是最简单最快速的方法，但同时也有一个缺陷，就是rand函数生成的是均匀分布的随机数，在区间范围内会分布得比较均匀，不符合日常生活中数据的按照正态分布的特点，这样也就留下了明显的痕迹。比如我用rand函数生成0-100的100个随机数，用Minitab自动生成直方图，频数是下面这样的：大家可以看到，大致上每个区间分..._wps生成正态分布的随机数

java开发命名规范总结_java命名规范-程序员宅基地

文章浏览阅读1.7k次。驼峰命名法（Camel-Case）: 当变量名或方法名是由一个或多个单词连结在一起，而构成的命名时；首字母以小写开头，每个单词首字母大写（第一个单词除外）。_java命名规范

当前线程不在单线程单元中，因此无法实例化 ActiveX 控件解决办法_当前线程不在单线程单元中,因此无法实例化 activex 控件-程序员宅基地

文章浏览阅读3.3w次，点赞2次，收藏6次。(一)引经据典(MSDN):1.单元是进程内部具有相同线程访问要求的对象的逻辑容器。同一单元中的所有对象都可以接收从该单元中的任何线程发出的调用。.NET Framework 不使用单元，托管对象自己负责以线程安全的方式使用所有共享资源。由于 COM 类使用单元，因此公共语言运行库需要在 COM interop 的情况下调用 COM 对象时创建并初始化一个单元。托管线程可以创建并进入只允许有一个线程的单线程单元 (STA) 或者包含一个或多个线程的多线程单元 _当前线程不在单线程单元中,因此无法实例化 activex 控件

Python 获取多维数组数据_robotframework 获取 多维数组-程序员宅基地

文章浏览阅读533次。几种常用获取数据的方法。_robotframework 获取 多维数组

C++11的一些新特性|右值引用|STL中的一些变化_stl中有移动赋值-程序员宅基地

文章浏览阅读340次，点赞2次，收藏2次。如果没有自己实现移动构造，且没有实现析构，拷贝构造，拷贝赋值重载中的任意一个，那么编译器会自己生成一个默认移动构造。在类中增加移动构造，移动构造本质上是将参数右值的资源窃取，占为己有，那么就不用做深拷贝，所以叫它移动构造，就是窃取别人的资源来构造自己。原来c++类中，有6个默认成员函数：构造，析构，拷贝构造，拷贝赋值，取地址重载，const取地址重载。传统的c++语法中就有引用的语法，而c++11中新增了右值引用的语法特性，无论是左值引用还是右值引用，都是给对象取别名。可以让你更好的控制要使用的默认函数。_stl中有移动赋值

Playground v2.5最新的文本到图像生成模型，官方宣称V2.5的模型优于 SDXL、Playground v2、PixArt-α、DALL-E 3 和 Midjourney_playgrouind v2.5-程序员宅基地

文章浏览阅读724次。Playground在去年发布Playground v2.0之后再次开源新的文生图模型Playground v2.5。新版本提升了图像的美学质量，增强了颜色和对比度、改进了多纵横比图像生成，可以生成各种比例图像以及人像细节的提升。官方宣称：根据用户研究表明，V2.5的模型优于 SDXL、Playground v2、PixArt-α、DALL-E 3 和 Midjourney 5.2。_playgrouind v2.5

推荐文章

热门文章

相关标签