Quantcast
Channel: MogDB Life
Viewing all 353 articles
Browse latest View live

警惕:Oracle中删除的分区不会进入回收站(Recyclebin)

$
0
0

作者:eygle 发布在 eygle.com

最近在『云和恩墨大讲堂』的微信群讨论中,有朋友提到分区的删除和闪回问题,我注意到很多人可能忽略了这个问题。

在Oracle数据库中,单个删除的分区并不会进入回收站,全表删除的分区才可能和全表一起放入回收站。这是因为单个分区删除之后,是无法通过简单的闪回加入原分区表中,既然无法保证一致性,这个分区就不会进入回收站中。

以下这个测试展示了这个过程:

SQL> select * from v$version;

BANNER CON_ID

-------------------------------------------------------------------------------- ----------

Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production 0

PL/SQL Release 12.2.0.1.0 - Production 0

CORE 12.2.0.1.0 Production 0

TNS for Linux: Version 12.2.0.1.0 - Production 0

NLSRTL Version 12.2.0.1.0 - Production 0

SQL> CREATE TABLE enmotech (

2 PartID integer not null,

3 CretTm date not null,

4 PartCD varchar2(2) not null

5 ) partition by list (partcd) automatic (

6 partition pBJ values ('BJ'),

7 partition pCD values ('CD'),

8 partition pGZ values ('GZ'),

9 partition pSH values ('SH')

10 );

Table created.

SQL> insert into enmotech values (1, sysdate, 'KM');

1 row created.

SQL> select partition_name from user_tab_partitions

2 where table_name = 'ENMOTECH';

PARTITION_NAME

--------------------------------------------------------------------

PBJ

PCD

PGZ

PSH

SYS_P281

SQL> alter table enmotech drop partition SYS_P281 purge;

alter table enmotech drop partition SYS_P281 purge

*

ERROR at line 1:

ORA-14048: a partition maintenance operation may not be combined with other operations

SQL> alter table enmotech drop partition PSH;

Table altered.

SQL> select * from user_recyclebin;

no rows selected

SQL> drop table enmotech;

Table dropped.

SQL> select object_name,original_name,type from user_recyclebin;

OBJECT_NAME ORIGINAL_NAME TYPE

---------------------------------------- -------------------- -------------------------

BIN$TflQLiTmWX7gUwo4qMBX+A==$0 ENMOTECH TABLE

BIN$TflQLiTmWX7gUwo4qMBX+A==$0 ENMOTECH Table Partition

BIN$TflQLiTmWX7gUwo4qMBX+A==$0 ENMOTECH Table Partition

BIN$TflQLiTmWX7gUwo4qMBX+A==$0 ENMOTECH Table Partition

BIN$TflQLiTmWX7gUwo4qMBX+A==$0 ENMOTECH Table Partition

很多时候,想当然的结果可能并不可信,实践操作方能出真知,多动手,是技术人的王道。

相关文章|Related Articles


Oracle数据库中 MISSING 文件名称的出现和处理

$
0
0

作者:eygle 发布在 eygle.com

在数据库中,异常情况下,你可能会看到某些文件带有MISSING的名称,这是如何出现的?又可以怎样处理呢?

SQL> select * from v$version;

BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE	11.2.0.3.0	Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production

SQL> create tablespace eygle datafile '/u01/app/oracle/oradata/enmot1/eygle01.dbf' size 10M;

Tablespace created.

SQL> create table enmo tablespace eygle as select * from dba_users;

Table created.

生成重建控制文件的脚本:

SQL> alter database backup controlfile to trace;

Database altered.

SQL> select name,value from v$diag_info where name='Default Trace File';

NAME
----------------------------------------------------------------
VALUE
-----------------------------------------------------------------------------
Default Trace File
/u01/app/oracle/diag/rdbms/enmot1/enmot1/trace/enmot1_ora_8511.trc

STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ENMOT1" RESETLOGS FORCE LOGGING ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 4674
LOGFILE
  GROUP 1 (
    '/u01/app/oracle/oradata/enmot1/redo01a.log',
    '/u01/app/oracle/oradata/enmot1/redo01b.log'
  ) SIZE 100M BLOCKSIZE 512,
  GROUP 2 (
    '/u01/app/oracle/oradata/enmot1/redo02a.log',
    '/u01/app/oracle/oradata/enmot1/redo02b.log'
  ) SIZE 100M BLOCKSIZE 512,
  GROUP 3 (
    '/u01/app/oracle/oradata/enmot1/redo03a.log',
    '/u01/app/oracle/oradata/enmot1/redo03b.log'
  ) SIZE 100M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '/u01/app/oracle/oradata/enmot1/system01.dbf',
  '/u01/app/oracle/oradata/enmot1/sysaux01.dbf',
  '/u01/app/oracle/oradata/enmot1/undotbs01.dbf',
  '/u01/app/oracle/oradata/enmot1/users02.dbf',
  '/u01/app/oracle/oradata/enmot1/rock01.dbf',
  '/u01/app/oracle/oradata/enmot1/xxx.dbf',
  '/u01/app/oracle/oradata/enmot1/minor.01.dbf',
  '/u01/app/oracle/oradata/enmot1/shghserol01.dbf',
  '/u01/app/oracle/oradata/enmot1/zdb.dbf',
  '/u01/app/oracle/oradata/enmot1/appmon.dbf',
  '/u01/app/oracle/oradata/enmot1/dbadata01.dbf',
  '/u01/app/oracle/oradata/enmot1/data01.dbf',
  '/u01/app/oracle/oradata/enmot1/data02.dbf',
  '/u01/app/oracle/oradata/enmot1/data03.dbf',
  '/u01/app/oracle/oradata/enmot1/data04.dbf',
  '/u01/app/oracle/oradata/enmot1/data05.dbf',
  '/u01/app/oracle/oradata/enmot1/data06.dbf',
  '/u01/app/oracle/oradata/enmot1/data07.dbf',
  '/u01/app/oracle/oradata/enmot1/data08.dbf',
  '/u01/app/oracle/oradata/enmot1/users03.dbf',
  '/u01/app/oracle/oradata/enmot1/undotbs02.dbf',
  '/u01/app/oracle/oradata/enmot1/users04.dbf',
  '/u01/app/oracle/oradata/enmot1/eygle01.dbf'
CHARACTER SET ZHS16GBK
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/arch2/arch_standby/1_1_791199500.arc';
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/arch2/arch_standby/1_1_912362625.arc';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
-- Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
-- No tempfile entries found to add.
--

重建控制文件,如果我们去掉最后一个新增的文件,启动数据库之后:

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP NOMOUNT
ORACLE instance started.

Total System Global Area  830967808 bytes
Fixed Size		    2232840 bytes
Variable Size		  742395384 bytes
Database Buffers	   83886080 bytes
Redo Buffers		    2453504 bytes

CREATE CONTROLFILE REUSE DATABASE "ENMOT1" RESETLOGS FORCE LOGGING ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 4674
LOGFILE
  GROUP 1 (
    '/u01/app/oracle/oradata/enmot1/redo01a.log',
    '/u01/app/oracle/oradata/enmot1/redo01b.log'
  ) SIZE 100M BLOCKSIZE 512,
  GROUP 2 (
    '/u01/app/oracle/oradata/enmot1/redo02a.log',
    '/u01/app/oracle/oradata/enmot1/redo02b.log'
  ) SIZE 100M BLOCKSIZE 512,
  GROUP 3 (
    '/u01/app/oracle/oradata/enmot1/redo03a.log',
    '/u01/app/oracle/oradata/enmot1/redo03b.log'
  ) SIZE 100M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '/u01/app/oracle/oradata/enmot1/system01.dbf',
  '/u01/app/oracle/oradata/enmot1/sysaux01.dbf',
  '/u01/app/oracle/oradata/enmot1/undotbs01.dbf',
  '/u01/app/oracle/oradata/enmot1/users02.dbf',
  '/u01/app/oracle/oradata/enmot1/rock01.dbf',
  '/u01/app/oracle/oradata/enmot1/xxx.dbf',
  '/u01/app/oracle/oradata/enmot1/minor.01.dbf',
  '/u01/app/oracle/oradata/enmot1/shghserol01.dbf',
  '/u01/app/oracle/oradata/enmot1/zdb.dbf',
  '/u01/app/oracle/oradata/enmot1/appmon.dbf',
  '/u01/app/oracle/oradata/enmot1/dbadata01.dbf',
  '/u01/app/oracle/oradata/enmot1/data01.dbf',
  '/u01/app/oracle/oradata/enmot1/data02.dbf',
  '/u01/app/oracle/oradata/enmot1/data03.dbf',
  '/u01/app/oracle/oradata/enmot1/data04.dbf',
  '/u01/app/oracle/oradata/enmot1/data05.dbf',
  '/u01/app/oracle/oradata/enmot1/data06.dbf',
  '/u01/app/oracle/oradata/enmot1/data07.dbf',
  '/u01/app/oracle/oradata/enmot1/data08.dbf',
  '/u01/app/oracle/oradata/enmot1/users03.dbf',
  '/u01/app/oracle/oradata/enmot1/undotbs02.dbf',
  '/u01/app/oracle/oradata/enmot1/users04.dbf'
CHARACTER SET ZHS16GBK
;

Control file created.

SQL> RECOVER DATABASE USING BACKUP CONTROLFILE
ORA-00279: change 709395945 generated at 05/26/2016 10:36:54 needed for thread 1
ORA-00289: suggestion : /u01/app/oracle/arch2/arch_standby/1_8_912362625.arc
ORA-00280: change 709395945 for thread 1 is in sequence #8


Specify log: {=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
*
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u01/app/oracle/oradata/enmot1/system01.dbf'


SQL> select member from v$logfile;

MEMBER
---------------------------------------------
/u01/app/oracle/oradata/enmot1/redo03a.log
/u01/app/oracle/oradata/enmot1/redo03b.log
/u01/app/oracle/oradata/enmot1/redo02a.log
/u01/app/oracle/oradata/enmot1/redo02b.log
/u01/app/oracle/oradata/enmot1/redo01a.log
/u01/app/oracle/oradata/enmot1/redo01b.log

6 rows selected.

SQL> RECOVER DATABASE USING BACKUP CONTROLFILE
ORA-00279: change 709395945 generated at 05/26/2016 10:36:54 needed for thread 1
ORA-00289: suggestion : /u01/app/oracle/arch2/arch_standby/1_8_912362625.arc
ORA-00280: change 709395945 for thread 1 is in sequence #8


Specify log: {=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/enmot1/redo03a.log
Log applied.
Media recovery complete.
SQL> ALTER DATABASE OPEN RESETLOGS;

Database altered.

这是数据库中会出现一个 MISSING 文件,也就是数据字典中存在,但是控制文件中丢失了,数据库自动增加一个MISSING的命名:

SQL> col name for a120
SQL> select name from v$datafile where name like '%MISSING%';

NAME
------------------------------------------------------------------------------------------------------------------------
/u01/app/oracle/product/11.2.0/dbhome_1/dbs/MISSING00023

Thu May 26 10:42:15 2016
SMON: enabling cache recovery
Incremental checkpoint up to RBA [0x1.3.0], current log tail at RBA [0x1.3.0]
ARCt: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
[9722] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:2296415402 end:2296416042 diff:640 (6 seconds)
Dictionary check beginning
Tablespace 'TEMP' #3 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Tablespace 'TEMP_TEST' #13 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Tablespace 'TEMP_TEST02' #14 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Tablespace 'TEMP_TEST03' #15 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Tablespace 'EYGLE' #27 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Thu May 26 10:42:21 2016
File #23 found in data dictionary but not in controlfile.
Creating OFFLINE file 'MISSING00023' in the controlfile.
This file can no longer be recovered so it must be dropped.
Dictionary check complete
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
*********************************************************************SMON: enabling tx recovery

WARNING: The following temporary tablespaces contain no files.
         This condition can occur when a backup controlfile has
         been restored.  It may be necessary to add files to these
         tablespaces.  That can be done using the SQL statement:
 
         ALTER TABLESPACE <tablespace_name> ADD TEMPFILE
 
         Alternatively, if these temporary tablespaces are no longer
         needed, then they can be dropped.
           Empty temporary tablespace: TEMP
           Empty temporary tablespace: TEMP_TEST
           Empty temporary tablespace: TEMP_TEST02
           Empty temporary tablespace: TEMP_TEST03
*********************************************************************
Database Characterset is ZHS16GBK
Opening with Resource Manager plan: MIXED_WORKLOAD_PLAN 
Thu May 26 10:42:22 2016
Starting background process VKRM
Thu May 26 10:42:22 2016
VKRM started with pid=59, OS id=9875 
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Thu May 26 10:42:23 2016
QMNC started with pid=60, OS id=9877 
LOGSTDBY: Validating controlfile with logical metadata
LOGSTDBY: Validation complete

通过重命名,恢复,如果日志齐全,可以将文件重新加回到数据库中:

SQL> select * from v$recover_file;

     FILE# ONLINE  ONLINE_ ERROR			     CHANGE# TIME
---------- ------- ------- ------------------------------ ---------- -----------------------
	23 OFFLINE OFFLINE FILE MISSING 			   0

SQL> alter database rename file '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/MISSING00023' to '/u01/app/oracle/oradata/enmot1/eygle01.dbf';
dbf';

Database altered.

SQL> recover tablespace eygle;
ORA-00279: change 709395945 generated at 05/26/2016 10:36:54 needed for thread 1
ORA-00289: suggestion : /u01/app/oracle/arch2/arch_standby/1_8_912362625.arc
ORA-00280: change 709395945 for thread 1 is in sequence #8


Specify log: {=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/arch/enmot1/1_8_912362625.arc
Log applied.
Media recovery complete.
SQL> alter tablespace eygle online;

Tablespace altered.

SQL> select count(*) from enmo;

  COUNT(*)
----------
	59

简单的测试,仅供参考。

相关文章|Related Articles

在Mac上通过Docker部署Oracle Database 12.2版本

$
0
0

作者:eygle 发布在 eygle.com

Oracle 已经宣布支持了Docker部署,这也让我们在Mac上部署 Oracle 数据库有了多一个选择,这是我的第一个Docker应用,非常简便快速的就完成了部署,简捷是最直接的体验。

首先要做的是准备工作,备好需要的软件,安装Docker环境,这些极其简单。

下载一个Docker的稳定版本,『Docker Community Edition for Mac』即可:

以下链接:

https://store.docker.com/editions/community/docker-ce-desktop-mac

选择稳定版本:

https://download.docker.com/mac/stable/Docker.dmg

这也是我第一次安装Docker,看着熟悉的小鲸鱼游进文件夹,第一步的准备工作基本就做好了:

DockerInstall.jpg

接下来还需要在Github上下载Oracle的Docker Image文件(下载之后的文件是 docker-images-master.zip ):

https://github.com/oracle/docker-images

OracleOnGitHub.jpg

此外,你还需要最新的Oracle 12.2 数据库安装包,可以从OTN下载(安装文件是 linuxx64_12201_database.zip):

http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

在成功安装了Docker之后,就可以部署Oracle数据库了

在Docker中部署Oracle数据库,简化到只需要一个核心命令。

我将整个过程概括为3个环节:

第一步:准备安装程序

主要是 docker-images-master.zip 和 linuxx64_12201_database.zip ,解压Docker的主体文件,然后将Oracle的安装文件加入到OracleDatabase/dockerfiles的相应目录下,准备工作就就绪了。

准备工作基本上就两条命令,把准备好的安装文件解压,最好建一个顶级目录,如Docker:

unzip docker-images-master.zip

mv linuxx64_12201_database.zip docker-images-master/OracleDatabase/dockerfiles/12.2.0.1/

简单点的日志如下:

bogon:~ eygle$ cd Docker/

bogon:Docker eygle$ ls -l

-rw-r--r--@ 1 eygle staff 4291538 May 16 15:52 docker-images-master.zip

-rw-r--r--@ 1 eygle staff 3453696911 Apr 19 12:04 linuxx64_12201_database.zip

bogon:Docker eygle$ unzip docker-images-master.zip

Archive: docker-images-master.zip

e4dbd20bd3ef245767f37641b5c37d6e918a5f97

creating: docker-images-master/

extracting: docker-images-master/.gitattributes

bogon:Docker eygle$ mv linuxx64_12201_database.zip docker-images-master/OracleDatabase/dockerfiles/12.2.0.1/

第二步:构建数据库的Docker镜像

这个环节就只需要一条命令,需要执行 docker-images-master/OracleDatabase/dockerfiles 下的build脚本

./buildDockerImage.sh -v 12.2.0.1 -e

在这个步骤中首先需要安装 OEL的 Slim 版本:oraclelinux:7-slim 。需要从网上下载文件,所以安装过程中必须保持网络的连通。整个过程有16个步骤,简单抽取出来,就是类似如下的过程,全部是自动执行的:

Step 1/16 : FROM oraclelinux:7-slim

Step 2/16 : MAINTAINER Gerald Venzl <gerald.venzl@oracle.com>

Step 3/16 : ENV ORACLE_BASE /opt/oracle ORACLE_HOME /opt/oracle/product/12.2.0.1/dbhome_1 INSTALL_FILE_1 "linuxx64_12201_database.zip" INSTALL_RSP "db_inst.rsp" CONFIG_RSP "dbca.rsp.tmpl" PWD_FILE "setPassword.sh" PERL_INSTALL_FILE "installPerl.sh" RUN_FILE "runOracle.sh" START_FILE "startDB.sh" CREATE_DB_FILE "createDB.sh" SETUP_LINUX_FILE "setupLinuxEnv.sh" CHECK_SPACE_FILE "checkSpace.sh" CHECK_DB_FILE "checkDBStatus.sh" INSTALL_DB_BINARIES_FILE "installDBBinaries.sh"

Step 4/16 : ENV INSTALL_DIR $ORACLE_BASE/install PATH $ORACLE_HOME/bin:$ORACLE_HOME/OPatch/:/usr/sbin:$PATH LD_LIBRARY_PATH $ORACLE_HOME/lib:/usr/lib CLASSPATH $ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib

Step 5/16 : COPY $INSTALL_FILE_1 $INSTALL_RSP $PERL_INSTALL_FILE $SETUP_LINUX_FILE $CHECK_SPACE_FILE $INSTALL_DB_BINARIES_FILE $INSTALL_DIR/

Step 6/16 : COPY $RUN_FILE $START_FILE $CREATE_DB_FILE $CONFIG_RSP $PWD_FILE $CHECK_DB_FILE $ORACLE_BASE/

Step 7/16 : RUN chmod ug+x $INSTALL_DIR/*.sh && sync && $INSTALL_DIR/$CHECK_SPACE_FILE && $INSTALL_DIR/$SETUP_LINUX_FILE

Step 8/16 : USER oracle

Step 9/16 : RUN $INSTALL_DIR/$INSTALL_DB_BINARIES_FILE EE

Step 10/16 : USER root

Step 11/16 : RUN $ORACLE_BASE/oraInventory/orainstRoot.sh && $ORACLE_HOME/root.sh && rm -rf $INSTALL_DIR

Step 12/16 : USER oracle

Step 13/16 : WORKDIR /home/oracle

Step 14/16 : VOLUME $ORACLE_BASE/oradata

Step 15/16 : EXPOSE 1521 5500

Step 16/16 : CMD exec $ORACLE_BASE/$RUN_FILE

执行的起点类似如下:

bogon:Docker eygle$ cd docker-images-master/OracleDatabase/dockerfiles

bogon:dockerfiles eygle$ ./buildDockerImage.sh -v 12.2.0.1 -e

完成的终点日志类似:

Oracle Database Docker Image for 'ee' version 12.2.0.1 is ready to be extended:
--> oracle/database:12.2.0.1-ee

Build completed in 52755 seconds.

第三步:创建和运行数据库

完成了安装之后,你拥有了两个镜像,一个是OEL 7-slim 版本,大约114MB,一个 oracle/database 大约14.8GB。

bogon:OracleDocker eygle$ docker images

REPOSITORY TAG IMAGE ID CREATED SIZE

oracle/database 12.2.0.1-ee dcfea9f4f145 3 hours ago 14.8 GB

oraclelinux 7-slim 442ebf722584 3 weeks ago 114 MB

启动数据库只需要一个命令:

docker run --name oracle -p 1521:1521 -p 5500:5500 -v /Users/eygle/oradata:/opt/oracle/oradata oracle/database:12.2.0.1-ee

这个命令有几个主要参数:-p 指定端口映射,主机到Docker的端口对应;-v 指定数据库的对应存储路径,我指定了一个Docker之外的本地存储,将数据库独立出来。

完成这个命令,会在本地完成数据库的构建并启动数据库,同时输出告警日志的监控。

注意这一段的日志:

#########################
DATABASE IS READY TO USE!
#########################
The following output is now a tail of the alert.log:

这里数据库事实上创建完成,显示的是日志的tail信息,中断之后数据库会停止,重启数据库就好了。

由于数据库缺省会指定用户口令,所以我们可以通过如下命令来修改口令:

docker exec oracle ./setPassword.sh youpassword

其他的必备命令是:

docker start oracle

docker stop oracle

docker logs oracle

docker ps

接下来就可以在 SQL Developer 里配置和连接这个数据库了:

DockerOracleConfig.jpg

DockerOracleConnect.jpg

当然如果你不想剥离数据库文件出来,也可以用类似以下命令来构建数据库:

docker run -p 1521:1521 --name eygle oracle/database:12.2.0.1-ee

想一想我们第一次安装数据库时的场景,再看看今天的简易程度,我们必须承认,技术在进步,学习越来越简单。Oracle 的今天越加开放和自由,乐趣会越来越多起来!

补充的知识FAQ

1.Docker 的镜像在哪里

在MAC上,位于以下目录,用户换成你的就找到:

/Users/eygle/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2


附录:以下是最后一个步骤,创建数据库的日志输出:

bogon:dockerfiles eygle$ docker run --name oracle -p 1521:1521 -p 5500:5500 -v /Users/eygle/oradata:/opt/oracle/oradata oracle/database:12.2.0.1-ee
ORACLE PASSWORD FOR SYS, SYSTEM AND PDBADMIN: 2fjRrW5zy8Y=1
LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 17-MAY-2017 01:28:54
Copyright (c) 1991, 2016, Oracle. All rights reserved.
Starting /opt/oracle/product/12.2.0.1/dbhome_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 12.2.0.1.0 - Production
System parameter file is /opt/oracle/product/12.2.0.1/dbhome_1/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/cfb8b54eab11/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=0.0.0.0)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 12.2.0.1.0 - Production
Start Date 17-MAY-2017 01:28:56
Uptime 0 days 0 hr. 0 min. 2 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/product/12.2.0.1/dbhome_1/network/admin/listener.ora
Listener Log File /opt/oracle/diag/tnslsnr/cfb8b54eab11/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=0.0.0.0)(PORT=1521)))
The listener supports no services
The command completed successfully
[WARNING] [DBT-11209] Current available physical memory is less than the required physical memory (2,048MB) for creating the database.
[WARNING] [DBT-10102] The listener configuration is not selected for the database. EM DB Express URL will not be accessible.
CAUSE: The database should be registered with a listener in order to access the EM DB Express URL.
ACTION: Select a listener to be registered or created with the database.
Copying database files
1% complete
13% complete
25% complete
Creating and starting Oracle instance
26% complete
30% complete
31% complete
35% complete
38% complete
39% complete
41% complete
Completing Database Creation
42% complete
43% complete
44% complete
46% complete
47% complete
50% complete
Creating Pluggable Databases
55% complete
75% complete
Executing Post Configuration Actions
100% complete
Look at the log file "/opt/oracle/cfgtoollogs/dbca/ORCLCDB/ORCLCDB.log" for further details.
SQL*Plus: Release 12.2.0.1.0 Production on Wed May 17 01:37:44 2017
Copyright (c) 1982, 2016, Oracle. All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
SQL> 
System altered.
SQL> 
Pluggable database altered.
SQL> Disconnected from Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
#########################
DATABASE IS READY TO USE!
#########################
The following output is now a tail of the alert.log:
Completed: alter pluggable database ORCLPDB1 open
2017-05-17T01:37:42.901045+00:00
ORCLPDB1(3):CREATE SMALLFILE TABLESPACE "USERS" LOGGING DATAFILE
'/opt/oracle/oradata/ORCLCDB/ORCLPDB1/users01.dbf' SIZE 5M REUSE AUTOEXTEND ON NEXT 1280K
MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
ORCLPDB1(3):Completed: CREATE SMALLFILE TABLESPACE "USERS" LOGGING
DATAFILE '/opt/oracle/oradata/ORCLCDB/ORCLPDB1/users01.dbf' SIZE 5M REUSE AUTOEXTEND ON NEXT 1280K
MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
ORCLPDB1(3):ALTER DATABASE DEFAULT TABLESPACE "USERS"
ORCLPDB1(3):Completed: ALTER DATABASE DEFAULT TABLESPACE "USERS"
2017-05-17T01:37:44.419029+00:00
ALTER SYSTEM SET control_files='/opt/oracle/oradata/ORCLCDB/control01.ctl' SCOPE=SPFILE;
ALTER PLUGGABLE DATABASE ORCLPDB1 SAVE STATE
Completed: ALTER PLUGGABLE DATABASE ORCLPDB1 SAVE STATE
2017-05-17T01:47:17.595752+00:00
ORCLPDB1(3):Resize operation completed for file# 10, old size 337920K, new size 358400K

2017-05-17T02:58:14.118529+00:00
Warning: VKTM detected a backward time drift.
Time drifts can result in unexpected behavior such as time-outs.
Please see the VKTM trace file for more details:
/opt/oracle/diag/rdbms/orclcdb/ORCLCDB/trace/ORCLCDB_vktm_1723.trc
2017-05-17T03:07:19.070128+00:00
Resize operation completed for file# 3, old size 471040K, new size 481280K
^CStopping container.
SIGINT received, shutting down database!
SQL*Plus: Release 12.2.0.1.0 Production on Wed May 17 04:06:49 2017
Copyright (c) 1982, 2016, Oracle. All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
SQL> 2017-05-17T04:06:49.354297+00:00
Shutting down instance (immediate) (OS id: 3434)
2017-05-17T04:06:51.079839+00:00
Stopping background process SMCO
2017-05-17T04:06:52.262508+00:00
Shutting down instance: further logons disabled
2017-05-17T04:06:52.290158+00:00
Stopping background process CJQ0
Stopping background process MMNL
2017-05-17T04:06:53.432719+00:00
Stopping background process MMON
2017-05-17T04:06:53.671235+00:00
OS process OFSD (ospid 1739) idle for 30 seconds, exiting
2017-05-17T04:06:54.534515+00:00
alter pluggable database all close immediate
2017-05-17T04:06:54.578363+00:00
ORCLPDB1(3):JIT: pid 3434 requesting stop
Pluggable database ORCLPDB1 closed
Completed: alter pluggable database all close immediate
PDB$SEED(2):JIT: pid 3434 requesting stop
License high water mark = 18
Dispatchers and shared servers shutdown
2017-05-17T04:06:56.956473+00:00
ALTER DATABASE CLOSE NORMAL
2017-05-17T04:06:57.038966+00:00
Stopping Emon pool
alter pluggable database all close immediate
Completed: alter pluggable database all close immediate
Stopping Emon pool
2017-05-17T04:06:57.139148+00:00
Shutting down archive processes
2017-05-17T04:06:57.141700+00:00
TT00: Gap Manager exiting (PID:1797)
Database closed.
Database dismounted.
2017-05-17T04:06:58.151422+00:00
Archiving is disabled
2017-05-17T04:06:58.155611+00:00
Thread 1 closed at log sequence 2
Successful close of redo thread 1
2017-05-17T04:06:58.461910+00:00
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Completed: ALTER DATABASE DISMOUNT
2017-05-17T04:06:59.516713+00:00
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
2017-05-17T04:07:00.533039+00:00
JIT: pid 3434 requesting stop
2017-05-17T04:07:01.593570+00:00
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
JIT: pid 3434 requesting stop
2017-05-17T04:07:01.638769+00:00
Stopping background process VKTM
ORACLE instance shut down.
2017-05-17T04:07:12.390203+00:00
Instance shutdown complete (OS id: 3434)
SQL> Disconnected from Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 17-MAY-2017 04:07:15
Copyright (c) 1991, 2016, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
The command completed successfully

参考文档:

https://sqlmaria.com/2017/04/27/oracle-database-12c-now-available-on-docker/

https://blogs.oracle.com/developer/creating-an-oracle-database-docker-image

相关文章|Related Articles

云和恩墨 Oracle Database 12.2 体系结构图海报发布

$
0
0

作者:eygle 发布在 eygle.com

在 2017 DTCC - 数据库大会的现场,我们发布了『Oracle Database 12.2 体系结构图』海报,这张体系结构图,涵盖了 Oracle 最新的 12.2 核心技术,大到多租户、In-Memory、Sharding,小到Recovery Buddy和LMS的变化,尽皆涵盖。

1920x1080dpi.jpg

各种大小的桌面图,和原始图,请在「数据和云」公众号回复 122ARCH 获得下载链接:

https://mp.weixin.qq.com/s/JisneEItduIa87gcg4cJdA

如果想获得印刷版本的海报,也请在公众号找到快递方式。

相关文章|Related Articles

Oracle 11.2.0.4 最终版本发布以来的 Oracle PSU 列表

$
0
0

作者:eygle 发布在 eygle.com

Oracle 11g R2 是目前客户的主流版本,这个版本后续发布了一系列的补丁,今天列表整理一下,供大家参考。

云和恩墨的Bethune平台具有自动的补丁推荐检查,免费使用,可以参考:https://bethune.enmotech.com .

首先明确两个概念和Oracle的补丁规格:

Critical Patch Update (CPU):每季度发布一次,用来修复安全方面的一些补丁,是累积型的。现在更名为Security Patch Update (SPU)。
点击下面的链接查看各个CPU所修复的具体问题:
http://www.oracle.com/technetwork/topics/security/alerts-086861.html

Patch Set Update (PSU):每季度发布一次,修复比较严重的一些问题,包含每季的CPU,是累积型的。虽然在描述PSU的时候会用到数据库版本第5位,比如Database PSU 11.2.0.3.5,但实际上打完PSU后并不会真正改变数据库的版本,从v$version中看到的版本还是4位的(11.2.0.3.0),第5位仍然是0(后来有补丁修正这个问题,可以在数据字典显示小版本号)。注意,Windows上没有CPU和PSU,Oracle的集群软件和数据库软件使用不同的PSU。

以下MOS文档了解每个季度的CPU、PSU、Windows Bundle Patch的具体补丁号:
Note 1454618.1 Quick Reference to Patch Numbers for Database PSU, SPU(CPU), Bundle Patches and Patchsets。

注意,由于PSU是累积的,所以每一个先前发布的PSU都会被后一个所替代,文档中描述就是:superseded 。引用中包含了MOS文章的原文链接,方便直接点击了解这些BUG的描述。


Bug 24732075 11.2.0.4.170418 (Apr 2017) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:24732075 The content was last updated on: 18-APR-2017
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.170418 (Apr 2017) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:24732075
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.161018 (Oct 2016) Patch Set Update (bug 24006111)
 
 - Plus all fixes which are included in the Security Patch Update for 
   April 2017 - for details see Note:2228898.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:2229037.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.170418 (Apr 2017) Database Patch Set Update (DB PSU)


Advance Queuing
24560906 High CPU usage for Background q0 processes with fix for bug 21286665

Oracle Multimedia
25093656 update db 11.2.0.4 ordim jar signatures to work with latest jre updates
 

Bug 24006111 11.2.0.4.161018 (Oct 2016) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:24006111
The content was last updated on: 18-APR-2017
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:24732075

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.161018 (Oct 2016) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:24006111
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.160719 (Jul 2016) Patch Set Update (bug 23054359)
 
 - Plus all fixes which are included in the Security Patch Update for 
   October 2016 - for details see Note:2171485.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:2171489.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.161018 (Oct 2016) Database Patch Set Update (DB PSU)


Oracle Security
24316947 ORA-07445 and ORA-00600 after applying 11.2.0.4/12.1.0.1/12.1.0.2 April DB PSU or DB Bundle Patch

Oracle Virtual Operating System Services
22243719 Several Internal Errors due to Shared Pool Memory Corruptions in 11.2.0.4 and later. Instance may Crash

Miscellaneous Issues
6599380 Fix for bug 6599380
22148226 Fix for bug 22148226
22657942 Fix for bug 22657942
 

Bug 23054359 11.2.0.4.160719 (Jul 2016) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:23054359
The content was last updated on: 18-OCT-2016
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:24006111

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.160719 (Jul 2016) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:23054359
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.160419 (Apr 2016) Patch Set Update (bug 22502456)
 
 - Plus all fixes which are included in the Security Patch Update for 
   July 2016 - for details see Note:2136219.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:2136772.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.160719 (Jul 2016) Database Patch Set Update (DB PSU)


Miscellaneous Issues
22296366 Fix for bug 22296366
22380919 Fix for bug 22380919
22507210 Fix for bug 22507210
22507234 Fix for bug 22507234
23177648 database security patch update 11.2.0.4.160719
23330119 db-11.2.0.4-molecule-045-cpujul2016
23330124 db-11.2.0.4-molecule-046-cpujul2016
23536835 db-11.2.0.4-molecule-047-cpujul2016
 

Bug 22502456 11.2.0.4.160419 (Apr 2016) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:22502456
The content was last updated on: 19-JUL-2016
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:23054359

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.160419 (Apr 2016) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:22502456
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.160119 (Jan 2016) Patch Set Update (bug 21948347)
 
 - Plus all fixes which are included in the Security Patch Update for 
   April 2016 - for details see Note:2102148.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:2104845.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.160419 (Apr 2016) Database Patch Set Update (DB PSU)


Advance Queuing
16596890 AQ Qnnn trace messages "kwqicgpc: cursor close error 604" with fix for bug 14764829 present
21286665 "Streams AQ: enqueue blocked on low memory" waits with fix 18828868

Automatic Storage management
21983325 ACFS filesystem crashes when resized beyond 128Tb

Generic
21387964 Drop user with Editioned objects / triggers fails with ORA-604 / ORA-4045 / ORA-942

High Availability
21868720 RMAN-6054 on backup based duplicate

Oracle Portable ClusterWare
20439705 Voting disk TOC Corruption

Oracle Virtual Operating System Services
18093615 Add new make target "patchset_opt_all" for use by opatch

Server Manageability
19258504E Need to have write IO throughput statistics in AWR

Miscellaneous Issues
20596234 Fix for bug 20596234
21756661 Fix for bug 21756661
21756677 Fix for bug 21756677
 

Bug 21948347 11.2.0.4.160119 (Jan 2016) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:21948347
The content was last updated on: 18-APR-2016
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:22502456

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.160119 (Jan 2016) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:21948347
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.8 (Oct 2015) Patch Set Update (bug 21352635)
 
 - Plus all fixes which are included in the Security Patch Update for 
   January 2016 - for details see Note:2074802.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:2076277.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.160119 (Jan 2016) Database Patch Set Update (DB PSU)


Enterprise Manager Database Control
21168487 Fix for bug 21168487

Enterprise Manager Grid Control
20861693 Fix for bug 20861693
21330264 Fix for bug 21330264
21343775 Fix for bug 21343775
21343838 Fix for bug 21343838
21343897 Fix for bug 21343897
21351877 Fix for bug 21351877
21453153 Fix for bug 21453153

High Availability
20509791 RMAN-04006: ORA-12638: Credential retrieval failed on RMAN RESTORE on Windows

Oracle Virtual Operating System Services
21847223 ORA-7445 [ksusig] or ORA-7445 [kghxcu] from PMON after killing RMAN hang

Workspace Manager
19032867 Fix for bug 19032867

XML Utilities
17655240 Fix for bug 17655240
21517440 Xslt transform security enhancement
21668627 Internal XSLT fix

XML database
21526048 Fix for bug 21526048
21787056 Fix for bug 21787056

Miscellaneous Issues
17551063 Fix for bug 17551063
21756699 Fix for bug 21756699
 

Bug 21352635 11.2.0.4.8 (Oct 2015) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:21352635
The content was last updated on: 18-JAN-2016
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:21948347

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.8 (Oct 2015) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:21352635
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.7 (Jul 2015) Patch Set Update (bug 20760982)
 
 - Plus all fixes which are included in the Security Patch Update for 
   October 2015 - for details see Note:2037108.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:2037751.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.8 (Oct 2015) Database Patch Set Update (DB PSU)


Enterprise Manager Grid Control
20448824 Fix for bug 20448824

Generic
16065166 Small CPU overhead in KGL with fix 13853126

XML database
20925795 Fix for bug 20925795

Miscellaneous Issues
20441797 Fix for bug 20441797
 

Bug 20760982 11.2.0.4.7 (Jul 2015) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:20760982
The content was last updated on: 19-OCT-2015
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:21352635

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.7 (Jul 2015) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:20760982
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.6 (Apr 2015) Patch Set Update (bug 20299013)
 
 - Plus all fixes which are included in the Security Patch Update for 
   July 2015 - for details see Note:2005667.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:2006079.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.7 (Jul 2015) Database Patch Set Update (DB PSU)


Buffer Cache Management
20777150 Fix for bug 20777150

Enterprise Manager Database Control
20004021 Fix for bug 20004021
20004087 Fix for bug 20004087
20334344 Fix for bug 20334344

Generic
18260550 ORA-600 [kgltti-no-dep1] occurs when dropping an Edition
18331812 "CREATE EDITION" / "ALTER USER ENABLE EDITIONS" leave incorrect entries in the library cache
20067212 Wrong values in error logging table with fix 17397545 present
21067387 Object name in some V$ views is truncated to 20 chars after 11.2.0.4.6 DB PSU applied

Oracle OLAP
20558005 Fix for bug 20558005

PL/SQL
18440047 ORA-600 [kglGetSO-null-parent] while invalidating objects in an Editioned database

Miscellaneous Issues
19699191 Fix for bug 19699191
20331945 Fix for bug 20331945
20657441 Fix for bug 20657441
 

Bug 20299013 11.2.0.4.6 (Apr 2015) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:20299013
The content was last updated on: 19-MAY-2016
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:20760982

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.6 (Apr 2015) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:20299013
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.5 (Jan 2015) Patch Set Update (bug 19769489)
 
 - Plus all fixes which are included in the Security Patch Update for 
   April 2015 - for details see Note:1967243.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:1967572.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.6 (Apr 2015) Database Patch Set Update (DB PSU)


Advance Queuing
17848897 AQ propagation reports ORA-22337 with different database timezones or character sets
18084625 Deadlock / library cache pin on queue objects with AQ/streams
19393542 Dependency timestamp mismatches on RULE SET and EVALUATION CONTEXT objects

Automatic Storage management
16870214 DB startup fails with ORA-17510 if spfile is in 4k sector size diskgroup
18317531 ASM gets terminated in the event of storage split in the stretch cluster

Enterprise Manager Database Control
17246576 EM dbcontrol does not start

Enterprise Manager Grid Control
8322815 Warning messages in install log while installing agent
19788842 emdbconsole issue "Global symbol "$EM_SOL_JAVA" requires explicit package name"

Generic
14368995 Dump in memcpy() under qerfxFetch() from query on fixed view
16668584 V$SQL.SQL_FULLTEXT may show "garbled" SQL for some statements > 1000 bytes long - superseded
17082983 Memory corruption querying some fixed tables / views (ORA-4029 / ORA-600 [17147] / ORA-600 [kghfrmrg:nxt])
17156148 Wrong results with query result cache using bind variable
17957017E Diagnostic enhancement to produce more information for ORA-600 [qesmaGetTblSeg1] errors
18051556 Wrong results from SQL using materialized "WITH" clause, COALESCE and TO_CLOB
18331850 ORA-600 due to stale entries left by "CREATE/ENABLE EDITIONS" DDLs
18362222 Memory leak from OCIStmtExecute in a loop against an IOT
18384391 Assorted ORA-600 errors possible with fix for bug 16402712 present
18384537 Process spin in opipls() / ORA-4030 for "kgh stack" memory
18704244 ORA-7445 [kgligl] can occur
18856999 Wrong results (wrong cursor) with schema table masking public synonym

High Availability
12611721 Archivelog deletion policy backed up N times to 'sbt_tape' ignored
12982566 ORA-7445 and/or ORA-6550 DBMS_DRS package does not exist on new standby DB after switchover
13829543 In DG auto resync from standby overwrites the standby controlfile - can cause resync/backup errors
14015842 ORA-600 [kjbrfixres:stalew] or similar in RAC LMS process
16384983 RMAN bad backup - causes recovery to fail with ORA-600 [3020]
16579084 LMS crashes instance with ORA-600 [kjbmprlst:shadow]
17348614 Logminer generates unsupported LCRs when mining XMLType table with out-of-line storage and LOB
17634921 ORA-22926 for direct path operation on table with LOBS in Logical Standby
17877323 ORA-600 [krbi_init_fra_metadata_not_backup_ctl] from active duplicate on standby database
17889549 OGG Integrated Extract does not correctly replicate Nested Table columns
17889583 OGG extract abends with OGG-1112
18091059 OGG parameter ALLOWNONVALIDATEDKEYS not working
18316692 LMS may hit ORA-4030 due to huge "KJC PGA send buffer" memory
18430495 Contention for "ges group table" latches even with fix 18306487 present
18456514 ORA-12705 in Logical Standby database after upgrade to 11.2.0.4
18765602 OGG IE fails during dictionary load
18783224 Logical Standby Database LSP2 consuming CPU in query against LOGSTDBY_SUPPORT_TAB_10_1 or LOGSTDBY_SUPPORT_TAB_10_2

Oracle Security
18325460 EXEMPT ACCESS POLICY not working correctly in RAC
19013183 Wrong results with context sensitive VPD policy in PL/SQL block

Oracle Space management
18000422 ORA-7445 [memcpy] under kdd* functions processing chained inline LOB
18607546* ORA-600 [kdblkcheckerror]..[6266] corruption with self-referenced chained row. ORA-600 [kdsgrp1] / Wrong Results / ORA-8102
18619917 Block corruption / ORA-600 [kdBlkCheckError]..[6110] on insert to OLTP compressed table
18723434 DBA_TABLESPACE_USAGE_METRICS.tablespace_size can be incorrect for ASM tablespaces after applying 11.2.0.4
18868646 Space metadata corruption / ORA-600 [ktsptrn_fix-extmap]

Oracle Streams
16194160 OGG inbound server does not honor set_table_instantiation
16306373 OGG Lightweight capture fails with ORA-600 [knlogcPackColList:101]
17201159 OGG Integrated Replicat abends with ORA-26808 error
17346091 OGG Integrated extract abends with OGG-2077 extract encountered error code 15012
17649265 OGG IR direct mode skips DML handler execution
17694209 OCI-21500 [knclprstr:str] from OGG
17798953 OGG abend with OGG-2030 "failed to set logmining server parameters"
17816865 OGG IR creates multiple error entries for eager error
17852463 OGG streams_apply info in alert showing 0 for applied_message_number
17853456 OGG parse error or missing data for XML replicated to target
17853498 OGG EXCLUDETAG capture parameter does not allow plus sign (+)
17945983 OGG unnecessary progress table cleanup when optimize_progress_table enabled
18155762 OGG does not assemble LOBs when conflict/reperror handlers configured
18193833 Logical Standby: SQL apply error ORA-10655 reported for shrink space check statement
18762750 OGG cloned integrated extract fails with ORA-600 [knlogcStartLogminer: logminer start scn > captured_scn]

Oracle Transaction Management
16571443 ORA-60 deadlock inserting to SECUREFILE with FDA enabled
17360606 Wrong results for materialized subquery factoring (WITH clause) on Data Guard

Oracle Virtual Operating System Services
13837378 "alter system kill session immediate" does not kill QC sessions

PL/SQL
17811789 ORA-7445 [pevm_ncal_trace] or similar with fix 16471888 present

Server Manageability
16903536 ORA-12751 in MMON during regular AWR purge

XML Utilities
17762296 Fix for bug 17762296

XML database
19358317 Fix for bug 19358317

Miscellaneous Issues
14692762 Some patch scripts required DV to be disabled
16091637 alter table update indexes parallel still raises an audit error in audit_trail$
19915271 Fix for bug 19915271
20296213 Make jox_on fails with error after applying PSU
 

Bug 19769489 11.2.0.4.5 (Jan 2015) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:19769489
The content was last updated on: 31-AUG-2015
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:20299013

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.5 (Jan 2015) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:19769489
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.4 (Oct 2014) Patch Set Update (bug 19121551)
 
 - Plus all fixes which are included in the Security Patch Update for 
   January 2015 - for details see Note:1942215.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:1942910.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.5 (Jan 2015) Database Patch Set Update (DB PSU)


Advance Queuing
18828868 Too Many Qxxx Processes Maxing Out the Number of Processes with fix for bug 14602788 present

Automatic Storage management
14106803 ORA-600 [kcbzwb_4] can occur
17274537 ASM disk group force dismounted due to slow I/Os
18273830 ORA-7445 [kge_is_oserr] mounting diskgroup if ora.asm asm_diskstring>1024

Buffer Cache Management
16344544 Deadlock and hang possible in RAC env between 'gc current request' and 'gc cr multi block request'

Generic
12816846 ORA-600 [kktget2: no updcol] updating Updatable Join View over Editioning View
13558557 ORA-7445 [qksbgParseList] from CREATE TABLE as SELECT
14354737 Unexpected PLSQL compilation errors, such as PLS-206
15990359 ORA-600 [qeslinit1:null_colnum] from DROP table with logging
16422541 ORA-7445 [kghssapage] reported while updating table containing a CLOB
16538760 ORA-600 [17014] or similar can occur
16777840 ORA-600 [kkdlGetOnDiskDefVal : no MODV] from CREATE MATERIALIZED VIEW over a database link
16934803 Some analytic functions do not honour session NLS_SORT
17215560 Scheduler jobs may not start after passed scheduled intervals
17258090 Recursive SQL fails with ORA-1008 even with fix for bug 14458214
17835048 Parallel UTL_RECOMP hangs after DB startup
17891943 CASE expressions result in high child cursor counts due to BIND_MISMATCH
17912217 PLS-201 and/or ORA-600 errors with Editions
18092127 Wrong results (or serial execution or PQ parse errors) for parallel query from PLSQL - superseded
18098207 TEMP space leak from SQL using temp table transformation in a PLSQL REF cursor
18189036 ORA-600 [qkaffsindex3] from SQL Tuning task / advisor
18244962 Parallel UTL_RECOMP hangs with Edition Based redefinition
18282562 ORA-4063 from query against view with ADT column in Editioned enviroment
18306996 Wrong SORT order for SQL with ORDER BY including partition column
18315328 ORA-1866 after upgrade to 11.2.0.4
18334586 ORA-7445 [kglUnLock] can occur
18554763 PMON crashes instance with ORA-600 [kksMutexRecovery-Bad-Opcode]
18674024 Rowcache deadlock using Editions
18964939 ORA-7445 [memcpy] from DBMS_AQADM.CREATE_QUEUE_TABLE with Editions
19615136 ORA-600 [rwoirw: check ret val] from aggregate on fixed view in 11.2.0.4.2-4
19730508 Orphan subscribers / ORA-600 [kwqdlprochstentry:ltbagi] on SYS$SERVICE_METRICS_TAB in RAC with fix of bug 14054676 present

High Availability
11883252E Redo transport streaming not supported with all mixed version configurations
14034426 ORA-600 [kjbrfixres:stalew] in LMS in RAC
17025461 ORA-600 [krbbsThrottle_ zero_total_size] on RMAN backup
17835627 Poor Logminer / OGG extract performance for large MERGE SQL
17851160 Hang / poor performance of logminer dictionary queries - superseded
17922254 ORA-26726 during convert to standby due to prior downstream capture session
18339044E Support encryption on oracle public cloud sbt library in standard edition
18674047 Very high CPU usage mining IOT index redo

Oracle JVM
19827973 ORA-600 [psd_validate:argc] during upgrade from 11.2 with October 2014 DB PSU (or equivalent) installed

Oracle OLAP
19309466 Fix for bug 19309466

Oracle Portable ClusterWare
19680952E Include ORACHK in database installations

Oracle Security
17184721 QSMA specific public synonyms are present after upgrade from 10.2
17308789 Memory leak / Session spin when using JDBC with Database Links
18441944 ORA-2002/ORA-22921 from audit of CLOB variables > 512 bytes

Oracle Space management
15913355 Supplementally logged column values incorrect for clustered tables
18202441 Logminer shows incorrect value in WHERE clause due to corrupted supplemental redo for chained rows
18235390 ORA-600 [kghstack_underflow_internal_3] ... [kttets_cb - autoextfiles_kttetsrow] after applying patch 17897511
18356166 ORA-600:[kdblkcheckerror][x][x][18020] possible in ASSM

Oracle Streams
17571039 OGG EXCLUDEUSER may nnot work on the apply user
17936109 Lob data missing from XA transaction in Streams replicated environment
18228645 XStream capture REQUIRED_CHECKPOINT_SCN does not change
18293054 ORA-1426 when querying DBA_CAPTURE / V$GOLDENGATE_CAPTURE
18471685 ORA-7445 [knalkcdoce_fcfhdlrs] stopping OGG integrated replicat with handlers
18482502 OGG IR hang on eager restart
18747196 Large trace of LCR dump after waiting more than 3 seconds

Oracle Transaction Management
12364061 Flashback Versions query fails intermittently with ORA-30054
16901385 RECO process may get ORA-600:[k2vdrv: valid branch]

Oracle Utilities
16595641 Import fails with ORA-2261 when SUPPLEMENTAL logging is on the table column

Oracle Virtual Operating System Services
17302277 A process may spin on CPU in skgfr_suspend64
18135678 Oracle background processes may parent multiple sh zombie processes
18508861+ Create datafile on RAW can produce a corrupt file header / causes ORA-17515 and crash in 11.2.0.4

PL/SQL
17282229 SQL developer hangs when debugging PL/SQL
18614015 utl_recomp does not compile invalid Materialized Views
18641451 Fix for bug 18641451
18641461 Fix for bug 18641461

Patch Automation
20074391 PSU post-deinstallation catbundle returns ORA-20000 / ORU-10027

Server Manageability
16833527 Inconsistent data in V$WAITCLASSMETRIC / V$WAITCLASSMETRIC_HISTORY

Workspace Manager
19006849 Fix for bug 19006849

XML Utilities
19197175 Fix for bug 19197175

Miscellaneous Issues
18436647 Fix for bug 18436647
 

Bug 19121551 11.2.0.4.4 (Oct 2014) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:19121551
The content was last updated on: 20-JAN-2015
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:19769489

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.4 (Oct 2014) Database Patch Set Update (DB PSU).
This Patch Set Update can be downloaded here: Patch:19121551
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.3 (Jul 2014) Patch Set Update (bug 18522509)
 
 - Plus all fixes which are included in the Security Patch Update for 
   October 2014 - for details see Note:1912224.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:1911774.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.4 (Oct 2014) Database Patch Set Update (DB PSU)


Advance Queuing
14764829 ORA-600[kwqicgpc:cursta] can occur using AQ

Automatic Storage management
13955826 ORA-15133 and ORA-600 [kfgFinalize_2] in ASM

Buffer Cache Management
12747740 Node join reconfiguration does not scale with more LMS's
16494615 ADG may suffer significant buffer waits
17390160 Small CPU overhead in ksusws->kcblsyncio for shared server sessions
17586955 ORA-600 [ktspfmdb:objdchk_kcbnew_3] in RAC
17951233 ORA-600 [kcblin_3] [103] after setting _pga_max_size > 2Gb

Enterprise Manager Database Control
18673304 Fix for bug 18673304
18673325 Fix for bug 18673325
18673342 Fix for bug 18673342
19211724 Fix for bug 19211724

Generic
9756271 Dump on kditpin
14245531 Excessive temp space used for SORT operation / ORA-1652
16042673 Database hang when system trying to add interval partition to the table
17037130 Excess shared pool "PRTMV" memory use / ORA-4031 with partitioned tables
17040527 Altering a partitioned table storage parameter (buffer_pool keep) does not work immediately
17242746 ORA-4025 on recursive SQL from PLSQL
17267114 ORA-1403 from DBMS_PICKLER calls
17449815 ORA-8102 ORA-1499 after ORA-1/ORA-2291 by MERGE with DML ERROR LOGGING
17570240 CPU overhead in MTS under kpospfdrv due to use of sprintf()
17587063 ORA-600 [qerghFetch:inc] reported on query with CURSOR_SHARING=force
17705023 ORA-600 [kkzuasid] on MV refresh
17824637 A context sensitive cursor may be incorrectly shared leading to wrong results or errors
17842825 SGA memory corruption caused by killed/sniped session writing ORA-600/ORA-7445 tracefile
17891946 PMON may crash with kglOnErrorMutexCleanup on the stack
17982555 ORA-4020 deadlock / ORA-4021 creating a PLSQL package
18199537 RAC database becomes almost hung when large amount of row cache are used in shared pool
18230522 ORA-7445 [kkpamCheckTransJoin] from full partition-wise join on REFERENCE partitioned object
18436307 A trigger with a 'WHEN' condition that is created on an Editioned View (EV) does not fire when the EV has a VPD policy defined on it
18973907 Memory corruption / various ORA-600/ORA-7445 using database links between 11.2.0.4/12.1.0.1 and earlier versions - superseded

High Availability
14285317 RMAN duplicate fails ORA-1507 if source has archivelog mode and cold backup
16692232 RMAN backup archivelog all not backed up / delete all input does not work as expect
17006183 DB hang as Archiver confuses destinations for EOR archivelog upon role change to primary
17232014 RAC startup with large buffer cache reserves too little space for GCS causing shared pool issues
17237521 LGWR needlessly waits at least 1 second for ARC process to start
18009564 RMAN overestimates backup size twice as much (False RMAN-3009 possible)
18280813 Process hangs in 'gc current request'

Oracle JVM
19289642 Fix for bug 19289642

Oracle Multimedia
18262334 ProcessCopy to JPEG image fails for index color image

Oracle Security
18264060 ORA-600 [kzaxpsqbnd:ENCD-lxgcnv] occurs with AUDIT_TRAIL=XML,EXTENDED / Incorrect bind audit data with 18136988 fix

Oracle Space management
14829250 ORA-7445 [ktbdbh] during diagnostic IOT output

Oracle Transaction Management
11733603 ORA-54 with select statement using NOWAIT clause with no concurrent active transaction
17787259E Excessive "minact-scn" trace in MMON

Oracle Utilities
17036973 NULL resilts from CLUSTER_PROBABILITY or CLUSTER_SET

Oracle Virtual Operating System Services
14657740 ORA-600 [510] ... [cache buffers chains]
17299889 Excess CPU in kghfrempty (especially with fix of bug 17009013 present)
18191164 Performance issue with direct NFS due to spin in reconnect code path
18328509 Fix for bug 18160822 can cause unexpected unconditional errorstack traces - superseded

PL/SQL
18641419 Fix for bug 18641419

Patch Automation
17343514 Remove Java code from catbundle
19727057 Internal fix to handle jvmpsu.sql in catbundle.sql

Server Manageability
14084247 Failed AWR purge can lead to continued SYSAUX space use
17042658 ORA-600 [kewrsp_split_partition_2] after upgrade from 11.2 to 12.1

XML database
16198143 ORA-7445 [qmxsaxCreateDocTypeXob]

Miscellaneous Issues
16524926 ORA-1031 from LOB writes in stored Java (JDBC KPRB) in definers rights
19458377 Internal check to ensure compatibility of "Oracle JavaVM Component Database PSU" patches
19554106 Internal fix required to support "Database PSU for Oracle JavaVM Component" Patches
 

Bug 18522509 11.2.0.4.3 (Jul 2014) Database Patch Set Update (DB PSU)

This note gives a brief overview of Patch:18522509
The content was last updated on: 14-OCT-2014
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:19121551

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.3 (Jul 2014) Database Patch Set Update (PSU).
This Patch Set Update can be downloaded here: Patch:18522509
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.2 (Apr 2014) Patch Set Update (bug 18031668)
 
 - Plus all fixes which are included in the Security Patch Update for 
   July 2014 - for details see Note:1666884.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:1666896.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.3 Database Patch Set Update


Advance Queuing
14602788 Q00* process spin when buffered messages spill

Automatic Storage management
13951456 ASMCMD does not use bind variables in its SQL - affects shared pool
17786518 Memory leak from oak_init in ASM
18247991E Enhancement for ASM to use OAK API for appliance attributes / more diagnostics for ORA-15405
18277454 ASM should get the "_asm_hbeatiowait" attribute from OAKLIB

Buffer Cache Management
17767676 ORA-600 [kcbchg1_28] possible on temporary ASSM segment

Generic
13645875 ORA-7445[qerixFetchFastFullScan] on update of IOT with secondary index
13853126 Dispatchers/new PQ slaves can get mutex with same session id - SGA memory corruption
14054676 SYS.SYS$SERVICE_METRICS_TAB queue table fills up when a RAC node is down
14458214 Unexpected ORA-1008 from select on composite partitioned table
15861775 ORA-1000 cursor leak from some V$ / X$ table accesses
16268425 Memory corruption / ORA-7445 / ORA-600 gathering statistics in parallel for table with virtual column/s
16855292 Select on REFERENCE partitioned table using full piecewise joins spins during parse
17393915 ora-600 [kqrcmt] / ora-600 [kqrhsh]
17397545 ORA-600 [kdtigetrow-2] from MERGE statement with LOG ERRORS INTO
17478145 ORA-6540/ORA-900 when dropping library unit in old Edition
17571306 Self deadlock on CREATE OR REPLACE SYNONYM SQL
17588480 library cache mutex/shared pool latch deadlock
17614134 ORA-600 [kglgtbo1] can occur reading a LOB in an Editioned environment
17752995 ORA-4031 from explain of SQL with many subqueries and OR expansion
17883081 ORA-7445 [kkdcnco] when Editioned objects are used
17892268 ORA-600 [koklread1-callback with conv flg] using 10.1 PLSQL client
18018515 High CPU in qctHasFakeBind (can cause 'cursor: pin S wait on X' waits)

High Availability
13498382 ORA-1122 ORA-1208 RMAN Duplicate overwrites datafiles at original location despite db_create_file_dest
14565184 LogMiner unconditional tracing floods trace files
16392068 ORA-600 [kjbmpocr:dsb] from LMS / instance crash
17011832 RMAN-6023, RMAN-6026 on tablespace point in time recovery
17227277 ORA-1741 during LogMining certain DDLs
17238511 RAC instance crash due to ORA-600 [kjbmpcrtpi:md]
17311728 Incomplete supplementally logged columns in OGG
17381384 ORA-1427 from multiple logminer sessions loading data for tables with REF columns
17477958 Logminer dictionary build can take very long time for large databases
17596908 OGG integrated extract issues a fetch for NULL LOB/UDT columns
17655634 ORA-7445 [krvxInvokeCallbacks] from Logminer running under GoldenGate
18996843 Apply fails with ORA-7445 [kghfre] with fix for bug 16472716 present

Oracle JVM
17600719 ORA-7445 from repeat calls to DBMS_UTILITY.invalidate which compiles Java objects

Oracle Secure Files
13609098 Datapump Import of small Securefile Lobs is slow

Oracle Security
16360112 ORA-28365 when querying TDE table even if wallet is already open in RAC env

Oracle Space management
17648596 ORA-64307 from query on Hcc Compressed Table Stored On ZFS 7420
17672719 ORA-600 [kclgclks_3] with fix 17382536 present

Oracle Streams
17297939 OGG cursor leak during apply with Integrated Replicat

Oracle Transaction Management
17165204 Self deadlock while updating HCC compressed tables

Oracle Virtual Operating System Services
15979965 RMAN is aborted by resource manager with ORA-40
16315398 PMON not cleaning ksfv slaves
16542886 Huge trace files with dNFS "CH OUT of ORDER" messages
17754782 ORA-7445 [kgnfs_check_for_timedout_requests] during startup

PL/SQL
16992075 Cannot drop package in ancestor Edition if package references a dead DB link
17174582 ORA-600 [kkt_ginfo_fobjn : missing trigger] during DROP EDITION

Miscellaneous Issues
16314254 Wrong results from query using multiblock scan for an OLTP compressed block
17006570 Fix for bug 17006570
17786278 Fix for bug 17786278
18061914 Fix for bug 18061914
18096714 Fix for bug 18096714
18554871 Fix for bug 18554871
19049453 Fix for bug 19049453
 

Bug 18031668 11.2.0.4.2 (Apr 2014) Database Patch Set Update (PSU)

This note gives a brief overview of Patch:18031668
The content was last updated on: 21-APR-2015
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:18522509

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.2 (Apr 2014) Database Patch Set Update (PSU).
This Patch Set Update can be downloaded here: Patch:18031668
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes from the 11.2.0.4.1 (Jan 2014) Patch Set Update (bug 17478514)
 
 - Plus all fixes which are included in the Security Patch Update for 
   April 2014 - for details see Note:1618213.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:1615893.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.2 Database Patch Set Update


Automatic Storage management
16618694 PST placement on ODA does not take into consideration the diskgroup redundancy
16875449 GMON tries to optimize metadata (PST) placement in an infinite loop
17071721 ORA-600 [723] from GMON in ASM for *skgdll..." memory
17296856 ORA-15405 from disk ADD if drop forcing disk already present
17385178 ORA-600 [kfgpSet3] during ASM reconfiguration with force dropping disks
17783588 ORA-15001 keep being raised

Buffer Cache Management
17323222 ORA-1555 / ORA-3170: deadlocked on readable physical standby (undo segment x) on ADG
17437634 ORA-1578 or ORA-600 [6856] transient in-memory corruption on TEMP segment during transaction recovery / ROLLBACK (eg: after Ctrl-C)
17752121+E ORA-600 [kclchkblkdma_3] ORA-600 [3020] RAC diagnostic/fix to avoid a block being modified in Shared Mode and prevent corruption
17761775+ ORA-600 [kclchkblkdma_3] ORA-600 [3020] or ORA-600 [kcbchg1_16] Join of temp and permanent table in RAC might lead to corruption - superseded

Generic
16180763 ORA-600 [pmuocons#9: unhandled type] in PLSQL with user defined objects
16731148 ORA-1882 using TIMESTAMP literals over a database link
16929165 ORA-900 / ORA-4045 compiling PLSQL if error position > 32767
17050888 ORA-600 compiling object in Edition after dropping covered objects
17325413 Drop column with DEFAULT value and NOT NULL definition ends up with dropped column data hitting disk leading to corruption
17346671 ORA-3106 when selecting an empty LOB over the long interface
17468141 ORA-7445 [kglobcl] with client side PLSQL (such as Forms)

High Availability
14133975 ORA-600 [kjbmiclo:creq] in LMS / instance crash
16220077 ORA-600 [kdlx_logmnr_decompress : incorrect unit length passed]
16228604 ORA-600 [kglUnlock-bad-lock] on restarting OGG Extract with missing/deleted REDO logs
16399083 Transport lag suddenly gets a high value as seen in V$TRANSPORT_LAG or query on V$DATAGUARD_STATS hangs
16472716 ORA-22920 occurs when applying piece-wise lob operation in Logical standby - superseded
17186905 Flashback database on standby reports ORA-38861 unnecessarily
17284817 Switchover to standby hang using broker via Siteguard
18094246 Internal fix

Oracle Security Service
17865671 Fix for bug 17865671

Oracle Space management
10136473 Memory corruption / ORA-7445 [kaf4F0rst9ir2srp1] from HCC compression
14010183 ORA-600 [ktspfundo:objdchk_kcbgcur_3] in SMON after failed temp segment merge load
16785708 ORA-600 [6122] following use of DBMS_REDEFINITION on a table with a LOB column

Oracle Storage Server Service Layer
13364795 Smart Scan may fail sporadically in Standby
16837842 Memory leak and assorted Dumps and Internal errors on KCFIS*
16863422 ORA-600 [kxdam_notify_cell:ioctlFailed] in Exadata
17080436E Diagnostic enhancement to write out OSS map elements in Exadata
17265217 Inconsistent asmdeactivationoutcome during scrub resilvering
17465741 ORA-600 [KCFIS_DECR_OVERHEADMEM_LEN_1] with large file creation / high redundancy
17546761 Exadata griddisk resilvering takes a long time
17602269 DISKMON master hang due to self deadlock
17614227 Exadata ASM rebalance takes a long time after flash failure / cell reboot
17726838 TCP connect error is incorrectly caught in libcell

Oracle Streams
14338435 ORA-7445 [knasald] / memory corruption from Streams apply AS process
16912439 OGG-2028 failed to attach: knlciDumpCaptureVDollarViewInfo err 1403
16943711 OGG XStream inbound encounters ORA-60 deadlock error on EHCC tables
16956380 ORA-7445 [knalsalex] during LOB assembly error for integrated replicat
17016369 ORA-1 against SYS.STREAMS$_APPLY_ERROR_TXN_UNQ from Streams
17027426 OGG IR does not abend when null values are used for delta resolution in cdr
17040764 OGG may not get the direct path apply setting
17082359 ORA-60 deadlock from OGG apply (IR) into securefile columns with deduplicate on
17205719 OGG: IR shows incorrect DML stats not matching with actual DMLs applied
17235750 OGG IR hangs after eager error
17341326 Various ORA-600 / ORA-7445 from OGG replicat with XStreams
17344412 OGG IR hangs after an abort of an eager transaction that is resent
17375354 OGG IR apply slaves log 'knalsglcr:nil lcr pointer' in as traces
17389192 OGG IR abends due to ORA-600 [knlqglcr:2] during repeated collisions handling
17390431 Downstream capture for OGG may downgrade to non RTM mode unnecessarily
17393683 OGG: IR reports negative daily/hourly stats & eventually total stats mistmatch
17441661 OGG IR repeatedly abends due to ORA-26808/ORA-7445 [knasplcr]
17545847 IEV2 capture aborts with ORA-7445 [knluCompareNumberArrayKnlpar] when EXCLUDEUSERID is specified
17546973 OGG XStream DML handler does not honor reperror handlers
17622427 OGG outbound server core dump

Oracle Universal Storage Management
16613964 Unwanted "Exadata" messages in ASM and DB alert logs on startup

Oracle Virtual Operating System Services
17313525 Core dump from "orion"
18180390 Unexpected "Warning: odm_mkdir not found in ODM library" tracefile entries with DB PSU 11.2.0.4.1 / 11.2.0.4 Exadata Bundle 2-4

Server Manageability
14852021 "spawrio" script shows wrong %Reads and %Opt values

Miscellaneous Issues
17716305 Fix for bug 17716305
17721717 Fix for bug 17721717
 


Bug 17478514 11.2.0.4.1 (Jan 2014) Database Patch Set Update (PSU)

This note gives a brief overview of Patch:17478514
The content was last updated on: 15-APR-2014
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Critical Patch Update)
Version/s this patch is for
Platforms affected Generic (all / most platforms affected)

Note that this fix has been superseded by the fix in Bug:18031668

Symptoms:

Related To:

  • (None Specified)
  • (None Specified)

Description

This is a marker bug for the 11.2.0.4.1 (Jan 2014) Database Patch Set Update (PSU).
This Patch Set Update can be downloaded here: Patch:17478514
( Please note that there is no 11.2.0.4.1 GI PSU - see Note:1611875.1 )
 
For information about Patch Set Updates please read Note:854428.1 .
 
This Patch Set Update includes:
 
 - All fixes which are included in the Security Patch Update for 
   January 2014 - for details see Note:1594621.1
 
 - Plus a number of other fixes (listed below)
 
For a cumulative list of fixes in the latest 11.2.0.4 PSU see Note:1611785.1
 
This PSU supports "composite patching" - see Note:1376691.1 for more details.
 
Known Issues
 See Note:1593200.1 for details of Known Issues with this Patch Set Update.
 

Fixes added in the 11.2.0.4.1 Database Patch Set Update


Automatic Storage management
12905058 Rare ASM corruption after disk resync
16850630 Excessive "kfOdaAppliance" tracing in GMON
17443671 Exadata block repair may invalidate cache lines

Generic
17332800 Wrong results with IOTs and fix of bug 13705338 present

High Availability
16069901 Hang/spin in RAC looking up object affinity

Oracle Storage Server Service Layer
17446237 kcfis block repair should be suppressed upon getting 'block to be resilvered'

Oracle Streams
16285691 Capture crashes when diag_dde_enabled is set

Oracle Utilities
17288409 Unexpected "EVENT or _TRACE_EVENT" warning from utlu112i/utlu112x/DBUA

Oracle Virtual Operating System Services
17501491I ODM API version is not correct for odm_mkdir call in 11.2.0.4
17612828 Private memory corruption can occur due to wrong buffer allocation size for replay in ksfdss*

PL/SQL
17610798 PLSQL clients may get stale error handle (ORA-65020 in RMAN)

Patch Automation
13866822 catbundle rollback does not update registry$history correctly

XML Utilities
17239687 ORA-31061 / ORA-19202 during database upgrade of multibyte database

Miscellaneous Issues
13944971 Fix for bug 13944971
16450169 Fix for bug 16450169
16721594 Fix for bug 16721594
17088068 Fix for bug 17088068
 

相关文章|Related Articles

Mac微信客户端的备份恢复功能和备份文件存储

$
0
0

作者:eygle 发布在 eygle.com

在MAC的微信客户端中(其他平台应该是相同的),具有一项微信聊天记录的备份恢复功能,对于我们更换手机或者备份数据很有帮助。

在客户端左下角就有这个功能选项:

WxBack01.jpg

可以选择备份,然后恢复到指定的手机:

WxBack02.jpg

备份文件,在MAC上存储在用户目录的Library下,我的电脑存储的位置是,其中的Backup目录存储的是备份文件:

/Users/eygle/Library/Containers/com.tencent.xinWeChat/Data/Library/Application\ Support/com.tencent.xinWeChat/2.0b4.0.9

不同版本和平台可能略有不同。记录供参考。

相关文章|Related Articles

Oracle 11.2.0.4 和 12c 安装 INS-30131 临时位置权限解决

$
0
0

作者:eygle 发布在 eygle.com

好久没安装数据库,今天在Windwos上安装11.2.0.4版本的数据库,遇到了这个看来闻名遐迩的错误:

12204.Instanll.png

[INS-30131]"错误"请确保当前用户具有访问临时位置所需的权限"

这个错误的文档描述也非常明确:

[INS-30131] Initial setup required for the execution of installer validations failed

Cause: Failed to access the temporary location

Action: Ensure that the current user has required permissions to access the temporary location.

要确保对于安装的临时目录有权限。但是事实上Windows上,很多人给出的解决方法是增加磁盘的 C$ 共享。

但是在我的环境没效果,而我已知临时目录没有问题。那么在命令行进入安装软件目录,通过命令行启动安装程序,设置 ignorePrereq 检查,此时数据库软件可以启动安装,是否会出现错误,就看忽略的检查是否关键,对于本案例中的临时空间问题,数据库无误安装:

F:\database>dir

Directory of F:\database

2017-07-03 09:21 <DIR> install
2013-10-25 09:09 29,747 readme.html
2013-10-25 09:06 <DIR> response
2013-10-25 09:06 345,480 setup.exe
2017-07-03 12:57 <DIR> stage
2013-10-25 09:09 500 welcome.html
3 File(s) 377,291 bytes
3 Dir(s) 88,050,397,184 bytes free

F:\database>setup.exe -ignorePrereq -ignorePrereq -J"-Doracle.install.db.validate.supportedOSCheck=false"

这样的办法,简单粗暴,但是有时候很有效。

相关文章|Related Articles

Oracle Mutex 等待事件之: cursor pin S

$
0
0

作者:eygle 发布在 eygle.com

cursor: pin S 等待事件说明,当一个会话(session)试图去更新一个共享的 Mutex Pin,同时已经有其他会话正在更新(updating)同一个 Shared Mutex Pin。注意,Pin S 的Mutex位于子游标上,是动态创建的,无法从等待事件中获得,但是可以在竞争出现的情况下,通过观察 x$mutex_sleep_history 来获得。

文档说明如下:

A session waits on this event when it wants to update a shared mutex pin and another session is currently in the process of updating a shared mutex pin for the same cursor object. This wait event should rarely be seen because a shared mutex pin update is very fast.

Wait Time: Microseconds

ParameterDescription

P1

Hash value of cursor

P2

Mutex value (top 2 bytes contains SID holding mutex in exclusive mode, and bottom two bytes usually hold the value 0)

P3

Mutex where (an internal code locator) OR'd with Mutex Sleeps

在实践中,当大量会话对某一个Cursor进行并发的软解析时,这一等待会被观察到。

此前的一篇文档说明在这里:AWR报告分析之三:cursor: pin S 的原理与案例分析

相关文章|Related Articles


Oracle Mutex 等待事件之: cursor pin X

$
0
0

作者:eygle 发布在 eygle.com

在 Oracle 官方文档,关于 cursor pin X 等待事件的说明是:

A session waits on this event when it is requesting an exclusive mutex pin for a cursor object and it must wait because the resource is busy. The mutex pin for a cursor object can be busy either because a session is already holding it exclusive, or there are one or more sessions which are holding shared mutex pin(s). The exclusive waiter must wait until all holders of the pin for that cursor object have released it, before it can be granted. Wait Time: Microseconds

翻译过来就是:

当一个会话对一个 cursor 对象请求 排他模式的 Mutex pin 时,因为该对象已有 X 或者 S 模式的 Mutex pin 存在,所以必须处于等待。直至所有 X 或 S 模式的 pin 被释放后,才能够获得 X pin。

cursor pin X 等待有三个参数,第一个参数就是 cursor 的 hash value。

ParameterDescription

P1

Hash value of cursor

P2

Mutex value (top 2 bytes contains SID holding mutex in exclusive mode, and bottom two bytes usually hold the value 0)

P3

Mutex where (an internal code locator) OR'd with Mutex Sleeps


需要对 Cursor 执行 Pin X 的操作包括:

  • 会话在某些串行化操作时需要获得 X 模式的 Pin,例如构建一个子游标;
  • 在Cursor 上执行排他操作,如 dbms_shared_pool.purge, keep/unkeep 等;
  • 一个或多个进程正在reference 该Mutex (shared mutex pin)

相关文章|Related Articles

Oracle Mutex 等待事件之: cursor: mutex S

$
0
0

作者:eygle 发布在 eygle.com

Cursor: Mutex S 等待事件是指,一个会话以共享模式请求一个Mutex,而其他会话以排他模式正在持有Cursor 上的 Mutex。

文档说明可以看到,此处的Mutex是位于 Cursor 对象上的固有 Mutex,也就是针对 Parent Cursor 的。这个等待的第一个参数会披露出 SQL 的 Hash Value。

A session waits on this event when it is requesting a mutex in shared mode, when another session is currently holding a this mutex in exclusive mode on the same cursor object.

ParameterDescription

P1

Hash value of cursor

P2

Mutex value (top 2 bytes contain SID holding mutex in exclusive mode, and bottom two bytes usually hold the value 0)

P3

Mutex where (an internal code locator) OR'd with Mutex Sleeps

相关文章|Related Articles

Oracle Mutex 等待事件之: cursor mutex X

$
0
0

作者:eygle 发布在 eygle.com

Cursor Mutex X 是当会话对某个 Cursor 请求排他模式锁,但是该Cursor 上已经有 S 或 X 模式的锁定,因而产生的等待。

The session requests the mutex for a cursor object in exclusive mode, and it must wait because the resource is busy. The mutex is busy because either the mutex is being held in exclusive mode by another session or the mutex is being held shared by one or more sessions. The existing mutex holder(s) must release the mutex before the mutex can be granted exclusively.

ParameterDescription

P1

Hash value of cursor

P2

Mutex value (top 2 bytes contain SID holding mutex in exclusive mode, and bottom two bytes usually hold the value 0)

P3

Mutex where (an internal code locator) OR'd with Mutex Sleeps

需要持有 Cursor Mutex X 的操作主要有:

  • 在父游标下创建新的子游标,但是这类操作在11.2之后被 Build Lock 替代,不再需要;
  • 捕获SQL中的绑定变量;
  • 更新、生成 SQL 统计信息,主要是 V$SQLSTATS 的内容;
  • Cursor Mutex X 主要指对于父游标的操作;
  • Building a new cursor under a parent
    • Although this operation is cheaper, building many cursors under a parent cursor is not recommended.
  • Capture SQL bind data
  • Build or Update statistics blocks
  • Mutex is in the parent cursor.

以下是在生产环境中观察到的实际现象,注意在获取 cursor:mutex X 的过程中,调用的底层函数是kkscsAddChildNode 这是增加子游标的操作,需要进一步的获取排他Mutex ,使用的函数是 kgxExclusive :

SQL> select sid,event,p1,p2,p3 from v$session where username='EYGLE' and sid=135;
       SID EVENT				      P1	 P2	  P3
---------- ---------------------------------- ---------- ---------- ----------
       135 cursor: mutex X		       978779761 1.6063E+12 1.4603E+11

SQL> oradebug short_stack;
ksedsts()+461<-ksdxfstk()+32<-ksdxcb()+1876<-sspuser()+112<-__sighandler()<-semtimedop()+10
<-skgpwwait()+160<-ksliwat()+1865<-kslwaitctx()+163<-ksfwaitctx()+14<-kgxWait()+650
<-kgxExclusive()+295<-kkscsAddChildNode()+337<-kkscscid_opt_eval()+1290<-kkscsCheckCriteria()+211
<-kkscsCheckCursor()+783<-kkscsSearchChildList()+1262<-kksfbc()+12105<-kkspsc0()+1173
<-kksParseCursor()+116<-opiosq0()+1588<-opipls()+11479<-opiodr()+916<-rpidrus()+211
<-skgmstack()+148<-rpiswu2()+638<-rpidrv()+1384<-psddr0()+473<-psdnal()+457<-pevm_EXIM()+308
<-pfrinstr_EXIM()+53<-pfrrun_no_tool()+63<-pfrrun()+627<-plsql_run()+649<-peicnt()+301
<-kkxexe()+525<-opiexe()+17785<-kpoal8()+2224<-opiodr()+916<-ttcpip()+2755<-opitsk()+1717
<-opiino()+966<-opiodr()+916<-opidrv()+570<-sou2o()+103<-opimai_real()+133
<-ssthrdmain()+252<-main()+201<-__libc_start_main()+253<-_start()+36

关于Mutex 的使用一直在变化之中。

相关文章|Related Articles

Oracle SQL和PL/SQL中字符串单引号的处理

$
0
0

作者:eygle 发布在 eygle.com

在 Oracle 的查询中,经常因为字符串要添加单引号,但是单引号的位置和个数往往不易把握。很多朋友都问过这样的问题。

请看以下查询,最外层的两个单引号作为引号操作符,第二个作为转义符号,随意第三个单引号是真实的数据输出,所以,以下查询输出的是第三个单引号:

SQL> select '''' from dual;

'
-
'

进一步的,如果我们希望在字符串中也留有单引号,那么会是这一个样子的:

SQL> select '''YUNHE''ENMO' from dual;

'''YUNHE''E
-----------
'YUNHE'ENMO

SQL> select '''YUNHE''''ENMO' from dual;

'''YUNHE''''
------------
'YUNHE''ENMO

SQL> select '''YUNHE''''ENMO''' from dual;

'''YUNHE''''E
-------------
'YUNHE''ENMO'

总之,只要理解转义符号的存在,处理单引号就不复杂了。

相关文章|Related Articles

Oracle中如何获取给定SQL的SQL_ID - dbms_sqltune_util0

$
0
0

作者:eygle 发布在 eygle.com

在 Oracle 数据库中,如何得到给定SQL的 SQL_ID ? 这是曾经被广泛讨论的一个问题。
现在,在Oracle 11g中,Oracle 给出了一个系统包,通过 dbms_sqltune_util0 可以简便的计算出给定SQL的SQL_ID。

SQL> desc dbms_sqltune_util0 FUNCTION EXTRACT_BIND RETURNS SQL_BIND Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- BIND_DATA RAW IN BIND_POS BINARY_INTEGER IN FUNCTION EXTRACT_BINDS RETURNS SQL_BIND_SET Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- BIND_DATA RAW IN FUNCTION GET_BINDS_COUNT RETURNS BINARY_INTEGER Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- BIND_DATA RAW IN FUNCTION IS_BIND_MASKED RETURNS NUMBER Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- BIND_POS BINARY_INTEGER IN MASKED_BINDS_FLAG RAW IN DEFAULT FUNCTION SQLTEXT_TO_SIGNATURE RETURNS NUMBER Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- SQL_TEXT CLOB IN FORCE_MATCH BINARY_INTEGER IN DEFAULT FUNCTION SQLTEXT_TO_SQLID RETURNS VARCHAR2 Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- SQL_TEXT CLOB IN FUNCTION VALIDATE_SQLID RETURNS BINARY_INTEGER Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- SQL_ID VARCHAR2 IN
函数 sqltext_to_sqlid 用于实现这个功能,以下测试使用了一个简单的SQL查询。
注意Oracle在SQL最后加入一个 chr(0) 的不可见字符,我们需要补齐:
SQL> select dbms_sqltune_util0.sqltext_to_sqlid('select sysdate from dual'||chr(0)) sql_id from dual;

SQL_ID
-------------------------------------------------------
7h35uxf5uhmm1

接下来看一下执行这个查询,数据库中自动生成的SQL_ID,与通过函数转换生成的完全一致:
SQL> select sysdate from dual;

SYSDATE
------------
07-AUG-17

SQL> select sql_id from v$sql where sql_text='select sysdate from dual';

SQL_ID
-------------
7h35uxf5uhmm1

Oracle 的改进一点点向前。

相关文章|Related Articles

恩墨学院DBA实战培训全新启航

$
0
0

作者:enmotech 发布在 eygle.com

默认标题_自定义px_2017.08.31.png

毫无疑问,当今时代早已经迈入了『数据时代』,数据无处不生、无处不在,也正以前所未有的方式在改变我们的生活。

  • Oracle数据库的地位

而在IT技术领域,数据无疑落地存储在各种各样的数据库之中,在关系型数据库领域,Oracle 数据库是当之无愧的王者,经过40多年的发展,Oracle数据库在RDBMS领域占据了近50%的市场份额,其从业空间无疑是巨大了。下图展示了2015年的IDC调查数据,其中,中国市场Oracle数据库占有率高达56%,高出亚太区52%、全球43.9%的市场占有率。

DBA

时至今日,Oracle DBA的发展也经过了几个阶段,从最初以基本操作和命令行为主的DBA 1.0 时代,到以诊断工具、图形工具为主的DBA 2.0时代,再发展到今天以大规模集中管理、云化管理的 DBA 3.0 时代,Cloud DBA已经成为新的认知共识。从我们近期总结的『Oracle优化方法进化论』也可以看出时代的不断进步。

恩墨学院

  • Oracle DBA向何处去?

有人说,今天 Oracle DBA 的生存空间变差了,收入待遇上缺乏吸引力了,这个认识是相当片面的,事实上,随着一个行业从业人员的增加,职业生存空间上也必然出现分层,分层的结果是,行业供给关系和回报趋于合理,同时职业纵深也必然加大。这是正常的行业进步,给入行者提出了挑战,但是也给予奋斗者和领先者更多的机遇。

从Oracle DBA们20年探索而言,已经成型的道路非常广阔:

1.甲方,凭一技之长,可以怡然自得,守企业数据安危;

2.乙方,解用户疑难,可以快速成长,成技术领域专家;

3.于技术,转型架构师、设计师,引领团队和应用进步;

4.于管理,可以领一彪人马,以数据驱动革新业务形态;

5.创业,以产品服务、数据分析种种可能另辟一番蹊径;

而在任何一个方向,我们都能找到成功的典范,学习先行者的成功经验,校正自己的职业生涯。右图是我们曾经总结的DBA成长树,直至今日,这个历程并未改变。

然而,我们这个时代,也的确提高了对于入行者的门槛,以前凭借自学命令操作安装部署,就能闯出一条道路,可是今天,OCP、OCM都成为入行的基本配置,对于初学者的入行要求提高了几个量级。技术时代快速变化,我们的时间也更加宝贵,这都要求我们能够快速去找到进阶之路。

  • 何以解忧?唯有实践!

虽然很多DBA早早通过了认证考试,但是缺乏实践经验往往让大家在面对挑战时败下阵来。

如何解决这样的困境?如何解决面试和工作时经验的不足?

恩墨学院凭借团队专家服务全国500多家企业客户的实践积累,将企业中遇到的真实案例采集、整理、脱敏、重现出来,将这些真实案例以场景化方式在培训中重演。同时,以服务于企业的工程师进行现身说法,让大家在真实的实践场景中学习成长,并且在培训后期,学员可以通过实习参与到真实的企业服务当中去,通过安全的步骤、标准的方法、进展的实践,让学员真正的实现全程实战化培训。

在过去恩墨学院的实战培训班中,已经有30位以上的学员,在培训后直接入职云和恩墨,走上数据生涯的起点!

恩墨学院的实战课程,既遵循了Oracle数据库的标准知识体系,又融合了来自实战不断更新的企业案例,形成了6大课程体系,81个企业实战案例,360学时的集中培训,让学员一次性超越重重障碍,抵达职业生涯的真实起点!下图是部分课程设计的大纲内容,真实的实战再现是整个课程体系的核心。

恩墨学院

恩墨学院

恩墨学院的课程体系,从学员的角度出发,为不同水平的Oracle学习者制定最适合自身发展的学习计划,加上雄厚的师资力量,帮助学员更快更好地走入数据领域。

以下是在实战班毕业季收到的来自学员的感谢信,他们在恩墨学院经过两个多月的学习成长,最终坚定而自信地迈入职场,也希望将自己的经验与祝福传送给更多的学弟学妹。

"转眼间培训班的课程已经结束,经过2个月的学习,收获了很多知识。感觉参加云和恩墨的DBA实战班是非常有意义的,非常有必要的,因为他不仅让我充实了理论知识,更多的收获了实战经验。从上课老师的理论讲解到课余的实战操作都让我有所收获。与来自全国各地的同学们汇聚一堂,相互交流学习经验,思路方法,全面提高了自己的理论水平和学习能力。"

--恩墨学员 李雄

"如何入门是许多初学者最头疼的事情。Oracle涉及的方面太多了,SQL、管理、优化、备份恢复......那么从哪开始学好呢?如果学过数据库理论,或有一定的数据库基础自然很好;如果没有的话,真的是个大问题。经过了几个月自学,我感觉自学比较茫然,很多东西不知该怎么学,从哪里下手,同时又没有试验环境,有些知识理解起来很困难,学习效率也很低,综合考虑,我决定去参加培训。众所周知,现在的培训机构很多,师资力量也是参差不齐。经过一段时间的搜素和咨询,试听了几家的课程,最终选择了恩墨学院。恩墨学院的课程都是独自研发,理论部分有恩墨学院ACE专家团队编写,训练任务有云和恩墨一线工程师贡献,真实再现DBA工作场景。培训过程以实操训练为主,理论学习为辅,是恩墨学院着力打造的精品特色课程。教辅人员全程指导训练,主讲老师随时答疑解惑,通过考试便可获得云和恩墨一线实习机会,表现优异者直接留用。几个月的学习,印证了我选择的正确性,在老师的帮助下,我建立起了一套完整的学习体系,明白了应该先学什么后学什么,整个学习思路豁然开朗。学习中我补充了我自学无法学到的东西,结业时对ORACLE已经有了一个清晰的理解。"

--恩墨学员 刘正保

『原理通透,思路清晰,操作娴熟,这是恩墨学院实战体系一直遵循的理念,源于实践,学于实战,成于未来』,恩墨学院院长侯圣文如是说。

理论+实践,场景+实习,恩墨学院全流程的实战培训,助力学员开启数据职业生涯,赢在起跑线!

恩墨学院简介

恩墨学院隶属于云和恩墨(北京)信息技术有限公司,Oracle WDP 合作伙伴,致力于提供专业、高水准的数据库培训服务,发掘与培养数据库专业人才,打造数据库精英圈子, 探索数据库培训新模式。恩墨学院讲师团队云集了业内顶尖的技术专家,首席讲师侯圣文(网名 Secooler)、李轶楠(网名 ORA-600)、盖国强(eygle)、张乐奕(kamus)、杨廷琨(yangtingkun)、熊军(老熊)为 ACE Director,强大的讲师团队堪称业内翘楚。目前, 恩墨学院提供包括个人实战技能培训、个人认证培训、企业内训在内全方位数据库技术培训。

相关文章|Related Articles

DBA将要彻底失业吗?Oracle推出Autonomous自治数据库

$
0
0

作者:eygle 发布在 eygle.com

在9月19日,接受媒体采访和为Oracle OpenWorld预热时,Larry Ellision透漏了Oracle未来的数据库变革方向,这就是:Autonomous Database - 自治数据库。

在接受采访时,Oracle创始人、现任首席技术官Larry Ellison透露,该公司将在OOW宣布首个"完全自治"的数据库云服务,埃里森说:结合机器学习,这个新版本不再需要人的管理或数据库调校

Autonomous Database之前,Oracle数据库中和 Autonomous 极大相关的是另外一个词:Autonomous transaction - 自治事务,该特性允许我们创建一个"事务中的事务",自治事务能独立于父事务提交或回滚。而现在,自治数据库如果真的能够实现自主管理、自主优化调节,那么DBA的工作量将会大大减少,甚至在未来,我们将不再那么需要DBA了!

Forbes 的报道进一步说明,Oracle计划即将推出的云数据库具有99.995%的系统可用性,这意味着每年计划中或计划外停机时间少于30分钟。Larry Ellison表示,为了达到这种可靠性,Oracle的数据库必须在系统运行时自动调整,修补和升级(automatically tune, patch, upgrade)

Ellison表示,从AWS的Redshift数据库迁移到Oracle的自治数据库的客户可以将成本降低至少一半,Oracle将提供SLA,以保证节省成本。

在Oracle的官方网站上这样介绍这个变革:

Oracle正在通过引入世界上第一个"自动驾驶"数据库,彻底改变数据的管理方式。 开创性的Oracle自主数据库具备:自我管理,自我调整,自我保护和自我修复等功能,它减少了操作数据库所需的人力,从而大大降低了成本并提高了可靠性。

Oracle用了一连串的 Self 词汇来形容这个愿景:self-managing, self-tuning, self-securing, and self-repairing 。

企业正在为迎接爆炸性需求而奋斗,这些需求包括更多数据和更佳的分析结果。 传统的数据库技术的运行越来越复杂和昂贵,因为它需要大量的人力劳动和手动的,容易出错的过程。 Oracle自治数据库有助于消除维护时间,降低管理成本,使IT能够专注于创新。

在旧金山时间10月1日开始的Oracle OpenWorld大会上,Larry Ellison 和 Andrew Mendelsohn 的演讲预告已经表明,这将是Oracle Database的一个重要变化,但是目前看起来这一变化仍然是首要在云上发生的。

Screen Shot 2017-09-29 at 9.13.44 PM.jpgScreen Shot 2017-09-29 at 4.40.34 PM.jpg

那么未来的DBA会失业吗?狼来了已经喊了很久,从DBA 3.0到Cloud DBA,DBA的突围之路也从未停止。前路漫漫,作为DBA,要做好准备,努力变革,无畏前行。

相关文章|Related Articles


拉里·埃里森亲自支招,数据库自动化之后,DBA何去何从?

$
0
0

作者:eygle 发布在 eygle.com

在旧金山时间10月1日的Oracle全球大会开幕主旨演讲中,Oracle公司的创始人,现任CTO,Larry Ellison宣布全球第一款能够『自动驾驶』的『自治数据库』即将发布

这款结合了机器学习的产品,将会具备自我管理、自我调节、自我安全、自我修复等功能(Self-managing, Self-tuning, Self-securing, and Self-repairing),这些功能将极大的降低企业的人力成本,极大的提高产品的稳定性和持续运行能力,具备了自治能力,这些自动化的工作都可以在线完成,包括打补丁和数据库升级。

IMG_20171001_181759R.jpg

对于数据仓库版本,将在2017年12月发布,而针对OLTP的版本,则将在2018年6月发布。新的版本号将会是 18c ,如果你不了解为什么从 12c 跃迁到 18c ,请看『Oracle版本号发布策略改变

Autonomous Database之前,Oracle数据库中和 Autonomous 极大相关的是另外一个词:Autonomous transaction - 自治事务,该特性允许我们创建一个"事务中的事务",自治事务能独立于父事务提交或回滚。而现在,自治数据库如果真的能够实现自主管理、自主优化调节,那么DBA的工作量将会大大减少,甚至在未来,我们将不再那么需要DBA了!

既然数据库实现了极大的自维护性和自我优化能力,DBA的大量基础性工具将变得简单和高效,那么DBA的未来向何处去?

在大会的演讲中,Larry在一页PPT中提出了他的建议,既然DBA可以减少基本管理工作的时间,不再花更多的精力在基础设施、补丁升级、高可用保障和调节工作上,那么就可以将时间花在创新上,用更多的时间和精力关注数据库设计、进行数据分析、制定数据策略、加强数据安全

newskills.jpg

这些建议非常中肯,也是多年以来恩墨学院在培训中一直倡议的,要完成由DBA向DA - 数据分析师 和 数据架构师 转变,将数据库管理能力上升为数据能力,从而成为企业的数据科学家,这其中当然需要付诸努力,但是集成了机器学习算法的Oracle Database 18c为我们做出了一个示范,在历史车轮滚滚向前的旅程中,所有拒绝变革的企业或个人,终将被时代远远的抛在身后。

machinelearning.jpg

关于这个自治数据库的性能,Larry 在以下这一页中做了展示,4倍的In-Memory OLTP访问性能提升,5倍高竞争OLTP环境下RAC性能改进,Grid打补丁的0影响,并且NVRAM已经为行式存储和列式存储准备就绪;而针对分析型业务,能够提供2倍的内存列式存储加速,100倍的外部表加速(其实是实现了In-Memory的外部表),100倍的近似查询处理(这是对12c,近似查询计算的增强)。

18cauto.jpg

针对我们最关注的自动优化功能,Larry列出了一些功能概要,其中包括,自动优化索引、缓存、统计信息、并行执行等;自治数据库可以根据数据量的增长数据分布的改变,持续进行优化调节(这应该是优化器来做到的)。

autodb18c.png

抛去产品因素,Oracle最重要的还有创始人因素。当Larry登场时,我第一个想到的词是『神采奕奕』,这位出生于1944年的创始人已经73岁,而这位73岁的斗士,每年都为Oracle选择一个假想敌,然后推动整个公司努力超越,在我参加OOW这些年,在Oracle前进道路上的假想敌包括IBM、EMC、Salesforce,现在则是AWS,正是这样一位斗士,使得Oracle能够不断充满活力的奋斗在IOE队伍的风口浪尖之上,屹立不倒,创新前行。也正是因为有了这样一位神采奕奕、壮心不已的斗士,Oracle才能够在今天不断推陈出新,引领潮流。

Untitled.png

当然Larry从未改调侃竞争对手的的本色,在他的字典里,Amazon的账单要比Oracle高16倍:

WechatIMG47.jpeg

如果用一个词来概括Larry今天的演讲,我的字典里跳出的就是:神采奕奕。这家40年的数据库公司,在云的时代浪潮里,不仅没有被大浪淘沙,反而是披沙拣金,经过几年的拼搏,焕发出新的神采。

而作为数据技术的从业者,在上一个时代成长起来的DBA们,我们也必须认识到,数据库自动驾驶的年代即将到来,让我们一起拥抱变化,努力改变吧!

相关文章|Related Articles

Oracle Database 18c new features 之10大新特性一览

$
0
0

作者:eygle 发布在 eygle.com

在 2017 Oracle OpenWorld大会上,关于 Oracle 18c 的一系列新特性已经被披露出来,借助分散在各个会场的公开分享主题和内容、OOW提供PPT下载,我们和大家抢鲜分享一下 18c 中极具吸引力的新特性。

注意:标题里提到的10仅为约数,文章中提到的新特性不仅10个,分列也只是为了阅读便利,这些特性可能随着版本发布发生改变,仅供参考。

1.自治数据库 - Autonomous Database

首先,从最高级别上,Oracle 18c 将是一个『自治数据库 - Autonomous Database』,这由Larry Ellison首先发布,而在此框架下,一系列的设计由此展开。

oow1701.jpg

2.云级别可用性增强 - Cloud-Scale Availability

这其中包含了一系列的新特性,包括:

支持跨地域和混合云的自动的Sharding能力;

RAC Sharding支持;

在ADG中支持Nologging数据的复制同步;

ADG自动重定向update操作到主库(这个特性对于读写分离很有用);

Grid Infrastructure 打补丁的零影响;

建议的瞬时逻辑备库滚动升级;

18c010.png

3.In-Memory 内存选件增强

内存选件获得了大量的增强,包括:

自动In-Memroy管理,这应该指自动选择适合In-Memory的对象并压缩提速等;

支持In-Memory的内存表,这个特性很有用;

In-Memory 支持 NVRAM 内存架构;

针对数据仓库的特定增强,In-Memory 动态扫描;优化算法等;

oow1703.jpg

4.In-Memory的外部表和InLine外部表支持

这个特性值得独立说明,外部表使得Oracle对外部数据操作更加灵活,并且基于内存列式存储压缩,能够更快的支持大数据量的运算,对于数据仓库环境将会是极大的增强。并且由于外部表的数据基本处于静态,更适合使用In-Memory来处理,Oracle声称这一改进将会带来100倍的提升,接下来就要看我们如何将外部表用的更好了。

oow1704.jpg

Inline外部表,可以通过SQL直接调用,无需创建仅需一次使用的外部表,这使得开发灵活了很多,也减少了大量元数据的处理:

oow1705.jpg

5.近似查询 - Approximate Query 和 Top-N 近似聚合

这是Oracle 12c 的新特性,经过12.2 的增强,已经非常好用了,可以参考我之前的一篇文章:从Approx_Count_Distinct到M7的CPU集成 。而新增的Top-N近似聚合,则可以对类似如下问题进行近似聚合,比如:

上一周,Top 5的Blog文章阅读量;

每个区域Top 50客户的近似消费;

Oracle能够以小于 0.5% 的误差率,提供近似聚合,这个功能也将极其有助于对精确度要求不高的聚合查询,相应的我们获得的是性能的巨大提升。

oow1706.jpg

oow1707.jpg

6.机器学习算法新特性

Oracle Advanced Analytics 18.1,话说机器学习是 18c 的重头戏,所以功能极多,这一页大约提到了 18c 引入的算法:

•新的可扩展机器学习算法(SQL API)

- 随机森林分类

- 神经网络用于分类和回归

- 显式语义分析ML算法扩展到支持分类

- 通过指数平滑的时间序列

- 基于CUR分解的算法,用于属性和行重要性

•能够将ML模型导出到C和Java以进行应用程序部署

oow1708.jpg

分析视图是其中的一个重要功能组件,其实也是12.2 才引入的新特性,实现了将底层各种数据对接,形成分析视图,在提供给简化SQL访问,最终输出给应用,将复杂性通过分析视图遮蔽:

oow1709.jpg

oow1710.jpg

在18c中,新增的特性还包括多维表达式查询支持:

oow1711.jpg

7.多态表支持

这是 18c 引入的新特性,支持自描述,全动态SQL。是ANSI 2016标准的一部分。

多态表封装复杂的算法:

- 隐藏算法的实现

- 利用强大的,动态的SQL功能

- 通过任何表格列进行处理

- 返回SQL行集(表,JSON,XML文档等)

oow1712.png

8.多租户增强

这也是一组新特性,包括 Per-PDB 的主备库Switchover,这是更进一步的特性,很有用。此外还有可传输备份、快照转移、快速升级等新特性。

oow1713.png

9.基于NVRAM的多级缓存增强

Andrew在多次演讲中提到,Oracle基于NVRAM做了很多研发,现在新特性已经披露,在数据库中NVRAM又被作为一级高性能缓存用于加速数据库,这是非常强大的软硬结合优化。

oow1715.png

这一特性应该率先被用于Exadata环境,Exadata将NVRAM放置在了Flash Memory前面,计算节点可以通过RDMA协议,绕过软件栈,实现高性能的访问,较传统协议路径提速20倍。NVRAM用作Cache和作为直接存储使用,综合能力提升了10倍:

oow1716.png

10.安全增强

安全是Larry重点强调的内容,在18c中,关于安全的增强主要有,和Active Directory的集成,PDB的密钥存储和无密码(无缺省密码)的Schema创建。

oow1817.png

想了解更多Oracle Database 18c 的技术细节?快报名参加11.17 ~ 11.18在北京举行的『数据技术嘉年华』,限时免费报名中

时间:2017年11月17日-18日(周五 & 周六)

地址:北京丽都皇冠假日酒店(北京市朝阳区将台路6号)

相关文章|Related Articles

数据架构:从AT&T到青海移动的多租户数据整合实践

$
0
0

作者:enmotech 发布在 eygle.com

在数据库的世界里,我们经常面对的一个现实就是:分久必合,合久必分。大多数企业都在这样一个轮回中不断革新比如国内的银行,早期多数是按省市分布式布局,随着技术发展进步,慢慢建立了区域中心,全国中心,将数据库合并起来。而很多互联网企业,比如支付宝,数据库是从单台发展状大,又不得不进行拆分,变成分布式架构去支撑海量并发。

提示:获取下文AT&TPPT,可以关注本公众号(OraNews),回复:2017OOW找到)

41.jpg

除了业务压力负载的原因,很多企业早期粗放式的IT建设也是形成这样问题的原因之一,一个业务一套系统在企业级存在了很久,而今天在硬件能力不断提升,成本压力不断趋重的情况下,很多企业开始选择进行整合,在使用甲骨文数据库的场景下,整合带来的成本消减是非常显着的。

42.jpg

在Oracle 11g中,整合只能采用多用户的模式,往往多库之间存在的用户冲突就会带来很多工作量。但是从村落式走向集约化,已经成为企业数据架构规划的必由之路。

43.jpg

为了应对用户的整合聚集需求,降低整合或者拆分的复杂度,Oracle 12c推出了多租户这一新特性,可以提供便捷的数据库分分合合。

44.jpg

但是整合的前提是要有好的硬件基础架构支撑青海移动作为中国移动的西部省份,对于简化运维,降低成本的要求尤为迫切,早在2015年,青海移动就联合云和恩墨,通过基于X86的分布式存储架构,替换了原来的小型机和集中式存储,实现了去IE的分布式演进。同时数据库采用了12c的多租户,将原来的分散式部署的数据库,全部集中整合起来

即实现了成本节约,又实现了性能提升,做到了『降成本,增效能』的设计目标:

45.jpg

通过以ZDATA为核心的分布式存储一体机,客户既实现了弹性的灵活扩展,又实现了资源的充分利用,软硬件成本和运维成本都获得了显着的降低。两年来客户应用不断成熟,已经将统计,结算,电渠,计费等核心数据库全部融合起来,构成多租户数据库云平台,系统的高可用性也获得了极大提升

46.jpg

在今年的Oracle OOW大会上,AT&T也公布了其基于多租户的架构实践。非常值得参考,AT&T在2017年5月和Oracle签订战略协议,将逐步将其2000多个Oracle数据库全部迁移到Oracle Cloud上来

对于AT&T来说,他们看中的是多租户的以下收益,包括快速部署,简化管理,成本优化等:

47.jpg

同样,AT&T自从2015年开始采用多租户,其中myAT&T销售平台就运行在多租户环境之上,该系统共使用了3个CDB,超过50个PDB,部署概要如下:

  1. Container1由16 GB SGA的24个PDB;

  2. Container2由22 GB SGA的21个PDB;

  3. Container3由15GB SGA的7个PDB;

开发和测试可以借助多租户快速克隆生产环境,用于功能测试和准生产测试,由于多租户的稳定性和性能,资源使用率更佳,并且使得DBA团队的工作效率提升了4倍以上。

48.jpg

当前AT&T正在将其超过2000个数据库,近10PB的数据量迁移到Oracle的Cloud平台上。

49.jpg

目前,他们的分层模型大致是这样的:

50.jpg

迁移步骤是这样的:

51.jpg

获取AT&T以上内容的PPT,可以关注本公众号(OraNews),回复:2017OOW,找到这个文档。

了解多租户的特性,参考文章如下:

12C多租户数据库的创建,克隆与复制

看了这篇文章,少踩12C多租户很多坑

下附青海移动客户案例介绍

IT基础架构变更在路上
青海移动的去 "IE" 之旅

1

近两年一场由互联网企业掀起的86化浪潮已呈蔓延之势,迅速波及到传统行业。

2

传统的小型机和集中式存储的架构越来越不适应当前业务需要IT快速响应的要求。基础架构云化是简化IT架构,降低IT系统建设和运维成本,实现业务需求敏捷响应的必由之路。

3

IT系统的云化意味着对底层架构的改造,这将是一个漫长的过程。如何规划好技术路线,如何扎实地走出第一步,非常关键,也是一个不容易决策的过程。

4

青海移动由于地理位置原因,IT人才相对匮乏。对于传统集中式架构越来越不适应当前需求以及较高的运维成本,他们有更深刻的体会,对改造IT基础架构的愿望也更为迫切。基于这些原因,青海移动启动了IT基础架构的变革路线,并在2014年6月份迈出了关键一步。


下定决心去 "IE"

青海移动刚刚实现了将统计库从原来小型机和EMC存储迁移到了基于分布式存储的甲骨文数据库上,这个项目的成功对他们而言意义重大。青海移动的大部分系统都是运行在小型机和集中式存储上。小型机和传统的磁盘阵列在硬件可靠性上比较占优势,但随着技术的发展特别是集群技术和软件方法的改进以及资源池化概念的再次提出,86平台在应用软件风险的规避和分散上已经有了长足的进步。

虽然青海移动此前也利用过虚拟化技术建设了86平台云资源池,但主要是用来运行一些应用软件,并没有在其上承载生产系统的数据库。在现代软件技术的运用下,应用软件系统几乎都是模块化的,非中心化的部署,硬件基本不会影响应用软件的运行。但是作为IT系统核心的数据库,是属于绝对中心化的部分。如果数据库或数据出现问题,将会严重影响生产的运行。

在此之前,青海移动对于x86的服务器运行数据库几乎没有经验,将甲骨文数据库迁移到x86的服务器上,如何保障系统的长期可靠,稳定运行?青海移动有着非常大的顾虑。在此种情况下,青海移动决定选择与国内数据库服务商云和恩墨合作,正式启动迁移项目。从项目开始到正式迁移历经了半年时间,并在今年5月实现了统计库从传统架构迁移到x86的分布式存储平台。到目前为止,系统运行非常稳定。可以说,青海移动成功地完成了的Oracle数据库去 "I(BM)E(MC)" 的第一步。

性能,成本,运维:去"IE"给青海移动带来积极效果

在青海移动看来,这次成功的去 "IE" 项目,实现了以下两个目标:

1. 成本的大量降低。原来的小型机已经超期服役,磁盘阵列的存储容量也已经不能满足需求,需要更换小型机和进行存储扩容。而使用新的架构,其成本大幅低于原有架构。从长期的运维来看,TCO成本还会更低。

2. 性能的大幅提升。迁移后,系统的各个业务模块的性能普遍都得到提升,不少业务性能甚至获得了十倍以上的提升

比较重要的是,通过一个多月的实际感受,业务人员反映系统变得更快,更流畅了,并希望将其他系统也迁移到新的环境中。业务部门的正面反馈和积极配合,对于推动青海移动IT基础架构的真正变革将起到非常重要的作用。据了解,青海移动已经着手将结算系统迁移到新的基于分布式存储架构的x86的平台上,并与原来的统计库实现整合,从而达到减少的Oracle数据库分割管理数量的目的。而这正是业界针对 "去IOE" 口号的另一种声音,即 "去IE减○" 的实际践行。

青海移动前景规划

以下青海移动项目负责人对未来的一些规划,以及如何付诸实现,表明了其对IT基础架构改造的决心和信心:

1. 将边缘系统迁移到x86的平台上,从0开始构造新的基础架构,并实现去"IE"方案的验证和经验积累。

2. 逐步将周边系统迁移到新的架构上,在此过程中实现数据库整合,实现"减O"的方案的验证和经验积累。

3. 将一些重要系统迁移到新的架构上,最终形成数据库云平台的架构模式。

在前期项目成功的基础上,青海移动通过构建分布式存储架构上的数据库,实现更多系统的甲骨文数据库整合迁移。如此一来,实现数据库私有云架构模式的探索就呈现出平稳但快速推进的态势。对于运营商而言,这样的方式无疑是见效最显着却又最安全的方式。

对于运维,新的架构模式下又会出现哪些变化呢针对这个问题,青海移动业务支撑中心IT基础架构和运维的负责人表示,新的平台确实跟以住有很大的不同,现在都是开放式的标准化软硬件,在新平台上扩容为结算库的整合作准备时,不用再请专业的存储工程师来做,只需要走集中采购,购买标准的硬盘,PC服务器,接到分布式存储的网络上,安装分布式存储软件,通过简单的命令就实现了存储的扩容因为都是标准化的开放式的设备:PC服务器,SAS硬盘,SSD硬盘,任何一个搞IT的技术人员都能很快熟悉这些设备并进行维护,不再需要像以前那样订购专门的硬件,并在故障时刻等待专门的主机和大型存储设备工程师到场维护,这对于运维的要求,运维的成本,都得到了大幅降低,而且运维响应度又得到了提升。甚至不再需要像以往那样,要做长期 。容量规划,因为新的分布式存储架构下,存储容量和计算能力都可以做到即插即用原来的容量规划,要么资源闲置,造成成本浪费;要么资源不足,系统能力受到影响。

采用全新存储架构

青海移动在这次项目中尝试了一套全新的分布式存储架构架构 - zData,云和恩墨西区负责人熊军深入了解了zData的技术架构情况并展示了如下的体系架构图。

熊军介绍,云和恩墨的分布式存储架构zData是整合了标准化x86服务器,40 / 56Gb Infiniband高速网络,闪存卡,SAS盘,SSD盘和分布式存储软件形成的超融合解决方案。

该方案通过灵活的软件解决方案创建虚拟SAN,大幅降低了成本和复杂性,基于的PCIe的闪存存储提供了极高的性能和超低延迟等优点来加快数据库的整体性能。通过方便灵活地搭配不同存储介质,能够以较低的成本应对以下这些应用场景:

1.使用少量的SSD盘和闪存卡,加上大容量低成本的SAS硬盘和SATA硬盘,满足如数据仓库这样的大数据量,密集IO的系统。单个数据库节点高达每秒12GB的吞吐,可以轻松应对100TB级别的数据仓库。

2.使用全闪存卡和SSD盘,满足对高并发,低延时OLTP类系统的需求。单个数据库节点超过100万IOPS,单个IO延时在0.6毫秒以下足以满足交易型系统极端性能要求。

3. SSD盘,闪存卡和SAS硬盘分层设计应用,形成不同IO需求的应用,应对数据库整合的混合IO要求。

面对去IE项目的成功实践,青海移动负责人表示:"IT基础架构的简化,让我们不用花太多精力在单个设备,单个系统上,而是让我们的精力可以更多聚焦在业务需求上,甚至实现IT驱动业务的目标。这就是IT基础架构变革带来的好处,青海移动也将继续在这条变革之路上探索,前行"。

000.jpg

相关文章|Related Articles

百花齐放:十二大亮点抢鲜看,数据技术嘉年华11.17日北京盛放

$
0
0

作者:enmotech 发布在 eygle.com

毫无疑问,数据库领域已经进入了一个百花齐放的时代,一方面甲骨文公司携甲骨文和的MySQL的的两大数据库产品独占鳌头,一方面各种开源分支蓬勃发展衍生无数;一方面国外产品攻城略地,一方面国产数据库独树一帜。而随着数据库技术的发展,云化平台的广泛应用,数据智能化,运维智能化正在成为现实。我们相信未来企业都将是数据企业,而运未来维也。都将的英文智能运维。

2017年数据技术嘉年华大会,秉承汇聚专家,分享前沿技术,引领行业发展的理念,第七次盛放北京。(文末有详细的日程表与嘉宾主题介绍)

本次数据技术嘉年华大会,以『数据价值,未来智胜』为主旨,以『云,数据,智能』为核心议题,汇聚行业专家,共同探讨在云时代,如何让数据驱动业务,走向更加智能的数据时代

在大会即将拉开帷幕之际,让我总结大会日程亮点,向大家预告11.17〜11.18两日的精彩嘉年华。

1,风起云涌,云领未来 - 汇聚云技术的实践和创新

在云计算的下半场,云技术已经进入细分领域的落地阶段。本次大会汇聚了来自各个领域的技术前沿和客户应用实践,包括甲骨文,阿里云,腾讯云,京东云,EasyStack,云和恩墨,数人云,袋鼠云,上海富麦等企业的创新技术,也包括来自恒丰银行恒丰金融云,海通证券海通云的最佳实践。

众多专家齐集探讨云未来,{甲骨文副词总裁吴承杨将分享倍受关注的甲骨文的的PaaS的IaaS的战略,状语从句:恩云墨创始人盖国强将分享云恩状语从句:墨对于云时代,数据驱动及智能化运维大未来的理解和实践;阿里云的专家张云扬分享阿里云的下一代数据库PolarDB,腾讯专家李海翔分享金融云分布式数据库的事务处理技术;京东云专家王向飞将分享京东云数据库架构实践。

而来自国内云领域的创业企业,谷原歌数架构师人云王璞博士,开源的开栈领域的创新企业EasyStack总裁{副词周崇毅,他们将为大家带来关于容器化的云技术架构创新,云和恩墨产品状语从句:研发负责人熊军,也将分享云和恩墨集团团队专家和基于对数据行业的深入理解打造的zCloud数据库的PaaS云平台,来自袋鼠云的技术专家镇伟将分享基于阿里云的数据库云解决方案。

恒丰银行科技的服务管理部副总经理郑淼,他将和大家分析恒丰金融云探索实践,来自海通证券的云架构师王朝阳将大家状语从句:海分享通证券金融云思考与实践,上海来自富麦架构师的鲍琳将分享构建金融级数据库云的的实践经验。

11.JPG

2,数据时代,各取所需 - 12大数据库产品,汇聚精华前

本次嘉年华大会,设置『云时代的数据库』专场,汇聚国内外领先和广泛应用的数据库产品和解决方案,让大家各取所需,了解数据库领域的前沿。除了甲骨文公司的三大产品的甲骨文,MySQL,Timesten之外,国产数据库包括KDB,OceanBase,PolarDB,TDSQL,SequoiaDB,TiDB,Oushu数据库(HAWQ),还有广泛应用的开源产品ElasticDB,CockroachDB。

阿里在ElasticSearch数据库的使用上大有创新,更将之打造为具有搜索能力的分布式OLTP数据库,程实将首次对外分享这些创新;而CockroachDB作为受到谷歌的扳手项目启发而诞生的OLTP数据库,在百度内部已然被广泛应用,_来自_百度专家的严龙将分享小强数据库的应用实践。

12.JPG

数据时代,百花齐放,也给了用户更多的自由,可以各取所需,大会分享的大多数产品都是在中国特有的双11大考之后,来到大会分享最新的第一手经验,这必将是精彩纷呈的饕餮盛宴!菜已备好,客官请赶早!

3,创新创业,国际一流 - 国产数据库各展风流;

在本次嘉年华大会上,第一次有许多国产数据库的身影汇聚,而且各具代表性,KDB是传统关系型数据库,SequoiaDB是NoSQL的,TiDB是NewSQL分布式关系型数据库,Oushu数据库是源自HAWQ的企业级MPP数据库。当然这其中还包括MySQL的的PolarDB,TDSQL,以及阿里研发的Oceanbase。其实我们发现,国产数据库已经能够覆盖传统的关系型应用的NoSQL,NewSQL,MPP大数据库处理,以及几乎支撑中国互联网的整个江山。

这一次来自KDB数据库的人掌门江豫京,SequoiaDB巨杉数据库的创始人王涛,Oushu数据库的创始人常雷博士,TiDB总裁{副词申砾,首席架构师唐刘齐聚一堂。江豫京来自浪潮,代表了国产数据库传统模式的突围,王涛出自IBM,代表了DB2的理念的革新,而常雷博士曾任EMC高级研究员,EMC / Pivotal研发部总监,是Apache HAWQ创始人,申砾和唐刘都是国际开源项目的活跃者,从国内到国际,又从国际到国内,说英雄,谁是英雄?看数据,谁是数据之王?快来数据技术嘉年华!

13.jpg

4,两大VP,五位专家 - 尽展18c,MySQL 8.0理念 ;

次本嘉年华大会邀请了甲骨文公司{副词总裁及大中华区技术产品事业部总经理吴承杨先生状语从句:甲骨文来自总部的{副词总裁安德鲁霍尔兹沃思,为大家分享的甲骨文的18C产品创新,甲骨文的IaaS 2.0战略,同时还有来自甲骨文研发的宋利兵分享MySQL 8.0新技术,内存数据库产品经理杨琳分享了最新技术,此外还有Oracle首席云架构师郑军分享Oracle Cloud架构和最佳实践;除此之外,安德鲁牵头的RWP团队将再次线上精彩演出,曲卓,董志平一起带来精彩的18C展示分享和论坛。

5,阿里巴巴,双11 总结 - 蚂蚁金服,阿里云节后首秀;

今年的嘉年华大会,我们特别将时间定在双11之后,希望也由此可以获得最新鲜的年终大考总结。这其中所有游戏来自蚂蚁金服专家韩富晟的OceanBase主题,来自阿里云的专家张云扬分享阿里云的下一代数据库PolarDB,来自以及阿里巴巴运维团队的王佳毅,为大家分享双11的运维实践,阿里巴巴的CloudDBA-数据库智能优化理念探索也深受行业关注胡航丽将为大家分享这一产品设计理念和突出成果。


6,腾讯金融,京东金融 - 互联网金融集齐,分享创新变革;

本次大会,非常荣幸的邀请汇聚到来自主流互联网金融企业的技术专家,分享其大平台之后的数据架构,运维实现,产品理念。这其中包括来自腾讯的Oracle ACE,姜承尧先生分享MySQL在腾讯金融支付的应用实践,财付通也是最早就使用开源的MySQL数据库系统支撑整个金融支付业务的平台,这个主题将包括大家最感兴趣的微信支付,手Q支付,红包转账,商业支付等后台架构;同样来自的腾讯专家李海翔,将分析金融云分布式数据库的事务处理技术,在这个主题中,海翔将和大家分享腾讯的TDSQL是如何应对挑战,以技术推动互联网金融业务发展的。而来自京东金融的团队数据库人负责高新刚将大家状语从句:分享京东金融MySQL的运维的高可用与自动化,智能化实践,以及京东金融的后台数据库架构,上再加蚂蚁金服专家韩富晟的OceanBase主题,一次获取主流互联网金融企业 的核心经验,就在数据技术嘉年华大会。

技术百花齐放,各路专家齐聚一堂,你是否也想来加入他们?心动不如行动,第七届数据技术嘉年华,目前限免报名中。

时间: 2017年11月17日 - 18日

地址:北京丽都皇冠假日酒店

识别二维码申请免费参会

更多技术亮点

7,传统企业,电信金融 -互联网+历程和技术创新 ;

互联网金融的蓬勃发展,带来了一轮蓬勃的互联网+浪潮,众多企业逐浪其中。本次大会还邀请了这些企业的代表,分享其业务创新,技术革命,互联网不独其美,传统企业各领风骚

作为国内数据技术的深度应用和领先企业,我们还邀请了最有发言权的电信企业客户,农历来自联通软件研究院院长耿向东将大家状语从句:主在分享会场关于农历联通的数据应用经验状语从句:创新,浙江参与来自移动的架构师钟储建分享『后IOE时代的数据平台架构实践』。农历来自翼电信支付数据库团队负责人张小虎,将和大家分享他们带领团队的上云改造,全力打造的具有金融属性的甜橙云数据库智能运维体系

恒丰来自银行的科技服务管理部副总经理郑淼,他将和大家分析恒丰金融云探索实践,恒丰银行近年在金融创新上的举措行业瞩目,其成果和经验尽在此时分享;来自福建农信社的架构师谢方恺,分享基于金融核心系统的SQL审核和应用质量管控实践;来自海通证券的云架构师王朝阳将状语从句:大家分享,海通证券金融云思考与实践;而来自渤海保险的卢彬彬将和大家分享渤海财险数据架构智能化演进,保险行业处于快速发展的黄金时代,来自保险行业的技术架构创新也非常值的关注;九鼎来自借贷宝的技术专家谭怀远,将和大家分享甲骨文数据库在互联网金融行业的应用实践,借贷宝的独特互联网金融创新模式,一直倍受关注,这一次我们可以一窥其数据平台的技术架构

TIM截图20171106103036.png

8,数据安全,固若磐石 - 安全守护数据价值;

数据承载着企业的核心信息,数据安全的重要性也不言而喻,在本次大会,我们精心组织了一系列关于数据备份和数据安全的主题和专场,帮助企业构建核心数据的防护战线。浪擎科技的CTO 郑战伟 先生将和我们分享云计算、大数据下灾备行业发展和解决方案,郑总身出华为,带领团队创建了全融合灾备云平台;而国内复制软件的杰出企业迪思杰创始人 韩宏坤 先生,也带来了基于数据复制的 DSG 复制云解决方案;在MySQL技术领域,数据安全同样引人瞩目,CRUG创始人 强昌金 将为我们分享MySQL数据安全体系,而老一辈的Oracle ACE、平民科技创始人 楼方鑫,出自Ebay、支付宝的经历,使他从Oracle转向MySQL并构建了一系列基于Proxy的产品体系,这次他带来的正是过去的积累在Oracle数据库网关生产实践;而这一次来自企业端的客户也将为我们带来真实场景中的安全实践,来自云南电网的 彭晓平 先生将和我们分享电力企业在数据安全方面的创新和安全实践,云和恩墨的数据安全产品经理 刘振宇,将和大家分享在四川电信客户每月4亿条安全审计日志的生产实践。海量数据,高速网络,来自Mellanox的专家 张辉 也将和大家分享在大数据时代网络加速和一体机的核心加速之路。

9、自动运维,智能运维 - 从自动化到智能化,告别人力时代;

Oracle在2017年10月的OOW大会,宣布推出了全球第一款自治数据库 - Oracle 18c,引起了行业的广泛关注,而关于运维自动化和智能化的发展,已经成为所有科技企业的共识,本次大会,我们邀请了来自阿里、京东、去哪儿网、云和恩墨、美团等企业专家,共同分享和探讨自动化和智能化运维的现状和未来。这其中包括来自阿里巴巴 胡航丽 的『CloudDBA-数据库智能优化服务』主题,去哪儿网数据库总监、Oracle ACED、ACMUG主席 周彦伟 先生,分享『利用开源工具,实现MySQL优雅运维』的主题,云和恩墨互联网事业部总经理 郑隐,分享『基于大数据分析和机器学习的数据库智能诊断平台』主题,京东金融 高新刚 的『稳中求进-打造京东金融MySQL运维的高可用与自动化』主题,云和恩墨应用研发部总经理 张中靖 分享『基于事前优化的MZ3 SQL诊断优化平台的DevOps最佳实践』,来自美团的数据库专家 龙雪刚,分享『SQL优化利器之SQLAdvisor』。

10、DBA时代,职业规划 - Cloud DBA和DBA 3.0,DBA何去何从;

数据库自动化之后,DBA何去何从?Oracle 18c的自治数据库推出之后,Larry Ellison曾经亲自为DBA们指点迷津,这一次大会,我们也专门邀请了几位专家,畅谈各自经验履历,指点数据库职业生涯,他们分别是Oracle领域的 侯圣文,新浪微博的MySQL技术专家 肖鹏,Oracle ACE、源于Oracle转型MySQL的 杨建荣,以及云和恩墨的MySQL技术专家 田朋。来自恩墨学院院长、Oracle ACED 侯圣文 的『从RDBMS向大数据演进的未来职场必备技能』主题;新浪微博的元老专家 肖鹏 将为大家解读『MySQL的核心技术和职业演进』,想了解那些明星引发的峰值挑战,这一场你不能错过;来自竞技世界 杨建荣 的主题『Oracle和MySQL DBA的进阶之路』,则为跨界的DBA们指出一条进阶之路,云和恩墨的MySQL技术专家 田朋 则将为大家分享来自实践的MySQL DBA案例和实战经验。

11、性能优化,诊断案例 - DevOps时代一线经验总结;

产品再佳,也要实战为王,所以我们组织了来自生产实战的优化案例、诊断案例分享,希望以实战予以大家经验,这其中包括来自Oracle ACE 李真旭 的『细致入微:Oracle 经典案例分享』,以十数个生产案例与大家分享实战;来自云和恩墨招商银行服务团队的专家 曾令军,分享『RAC 性能优化实战』;来自ITPUB全国SQL大赛冠军得主 罗海雄 的『Oracle数据库统计信息的秘密』,通过大量核心客户SQL案例解读统计信息的内部秘密;来自前Oracle ACS高级顾问、云和恩墨二线专家 邝志辉 的 『系统级跟踪诊断方法及案例』;以及 SQL优化专家 怀晓明 的 『拨云见日-深入解析 TX 行锁』,这是来自中国移动核心系统的一系列精彩案例。在SQL优化专场,你还可以看到来自 江苏移动服务专家 刘旭 关于SQL审核的实战分享,云和恩墨西区技术专家 黄廷忠 关于『子查询优化的最佳实践』。

企业的SQL开发团队、性能优化团队,来听这两个场次就没错了!

12、专注专业,专家云集 - Oracle ACE大集结;

数据技术嘉年华大会,是一次Oracle ACE大集结的盛会,这其中包括几乎国内所有的ACED。感谢Oracle社区的专家们:MySQL ACED 周彦伟,MySQL ACE 姜承尧王朝阳 ; Oracle ACED 盖国强,熊军杨廷琨侯圣文,Oracle ACE 李真旭杨建荣 ;前Oracle ACE 楼方鑫

心动不如马上行动,大会现在限时开放免费注册申请中:

时间: 2017年11月17日 - 18日

地址:北京丽都皇冠假日酒店

识别二维码申请免费参会

最新日程表

2017-11-06_102626.jpg

知己知彼,创新求变,才不至于被淘汰!

愿我们都在奋斗的路上,与时代一起成长。

数据

相关文章|Related Articles

千丝万缕:Oracle扩展统计信息虚拟列引发OGG 1161错误

$
0
0

作者:eygle 发布在 eygle.com

昨天有朋友在微信群提出一个问题,Oracle 12c GoldenGate 在复制时出现错误 OGG-01161 。

提示在 Trail 文件中,本应有 79 列,事实上出现了 93 列。

错误信息如下:

Bad column index (93) specified for table T_INITIAL_PREM, max columns = 79.

在检查数据表时,的确发现多出来很多列,这些列以 SYS_STS 开头,如果以 SYS_STS% 过滤,可以找到这些列:

WechatIMG12.png

那么这些列是怎么得来的?

查了一下文档确认:这是扩展统计信息生成的虚拟列 - Extended Stats Column 。

删除扩展统计信息,这些列就被清除了:

DBMS_STATS.DROP_EXTENDED_STATS(OWNNAME => 'MISBI',TABNAME => 'T_INITIAL_PREM',EXTENSION =>'("SALE_SVC_ID","SALECHNL","CTFLAG","CTVALIDATE","BANK_SELL_TYPE")');

这个案例提示我们,要注意学习Oracle的新特性,也要认真思考这些新特性可能带来的级联影响,按照六度关系理论,数据库中任何的修改都可能快速的关联到整个系统的核心稳定性上。

相关文章|Related Articles

Viewing all 353 articles
Browse latest View live