Oracle 高级技术
都帮忙看看吧，看上去很严重的样子......
墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年，写一次发全网
我也要 关注 + 加入社区[oracle@ibmserver2 ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Apr 3 09:56:24 2014
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
sys@orcl>create tablespace tianyu_cms datafile '/oracle/oradata/orcl/tianyu_cms.ora' size 100M reuse autoextend on next 10M maxsize unlimited default storage(initial 128k next 128k minextents 2 maxextents unlimited);
create tablespace tianyu_cms datafile '/oracle/oradata/orcl/tianyu_cms.ora' size 100M reuse autoextend on next 10M maxsize unlimited default storage(initial 128k next 128k minextents 2 maxextents unlimited)
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [25015], [141], [135], [134], [], [], [], []
sys@orcl>
sys@orcl>
sys@orcl>create temporary tablespace tianyu_cms_temp tempfile '/oracle/oradata/orcl/tianyu_cms_temp.dbf' size 50m autoextend on next 50m maxsize 20480m extent management local;
Tablespace created.
sys@orcl>create tablespace tianyu_cms logging datafile '/oracle/oradata/orcl/tianyu_cms_data.dbf' size 100m autoextend on next 50m maxsize 20480m extent management local;
create tablespace tianyu_cms logging datafile '/oracle/oradata/orcl/tianyu_cms_data.dbf' size 100m autoextend on next 50m maxsize 20480m extent management local
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [25015], [141], [135], [134], [], [], [], []
sys@orcl>exit;
ERROR:
ORA-03135: connection lost contact
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options (with complications)
[oracle@ibmserver2 ~]$
...全文
相关推荐
bug严重等级划分
bug严重等级划分，包括缺陷分类、缺陷严重登记、缺陷等级划分参考、缺陷状态
Bug严重程度优先级定义
功能测试中定义的BUG严重程度等级，优先级等级详细说明
缺陷严重级别定义缺陷严重级别定义
缺陷严重级别定义 缺陷严重级别定义 缺陷严重级别定义
bug严重等级分类
有关于测试当中的bug严重等级分类，可以分为以下四大类：严重，中，低，建议
Bug 的严重程度和优先级定义
严重程度: Blocker, Critical, Major, Minor 优先级: Immediate, Urgent, High, Normal 对Bug进行分配，标注处理意见，给定优先级（发版前必须三方：需求、开发、产品共同确定）。问题分配时，应尽可能将咨询类、理解错误类等问题处理掉，而不是留给开发人员。有可能是需求的问题，分配给需求人员。定期对Bug库分析，找出常出错的模块，进行代码审查
