安全检查中...
请打开浏览器的javascript，然后刷新浏览器
< 浏览器安全检查中...
还剩 5 秒&后使用快捷导航没有帐号？
请完成以下验证码
&&&&&全站 说: 为什么把重新编辑帖子的功能去掉了
唉，发现资源更新又要开新楼？17小时前全站 说: 谁有昨日青空。百度
21小时前全站 说: 好累..好困..不想更新...你们听说过小穷帽么?1天前全站 说: 别急，现在有也是枪版，画质和音质差，看了枪版别说烟花做的差
1天前全站 说:
谁有烟花动画电影。。。。。。。
1天前全站 说:
开了会员之后体验极佳，爽到2天前全站 说:
谁有烟花动画电影我找不到。。
2天前全站 说: 来自逗比牛盘内部群的表示，，，这么抽风好几年了，一直很坚挺不会跑路
2天前全站 说:
牛盘偶尔一个时间段会炸掉，之后就会恢复了，还是耐心等待下吧2天前全站 说: 牛盘全挂了，度盘还要另外收费，不厚道啊
3天前全站 说: 厉害咯不过我感觉牛盘要跑路了
3天前全站 说:
牛盘炸了？我买了一个月会员他就炸了？？？3天前全站 说: 所以说现在都不管管么,牛盘炸裂还往牛盘上传
3天前全站 说:
啊西吧。3天前全站 说: 牛盘都下不了了还一直发牛盘〉〉〉〉《〈〈〈
3天前全站 说: 牛盘为什么无法访问啊，是浏览器的原因还是什么3天前全站 说: 牛盘为啥全是文件同步中，请稍候进行下载呀？
3天前全站 说: 兄弟们，现在的牛盘资源都是显示文件正在同步中。都挂了，在下边补一个度盘吧==
3天前全站 说: :兄弟们，现在的牛盘资源都是显示文件正在同步中。都挂了，在下边补一个度盘吧==3天前全站 说: 兄弟们，现在的牛盘资源都是显示文件正在同步中。都挂了，在下边补一个度盘吧==。3天前
阅读权限200
在线时间159 小时
萝莉币2958
精华帖子积分
萝莉币: 2958
节操: 1984
胖次: 1594
查看: 4800|回复: 354
快来注册/登录领取福利~
才可以下载或查看，没有帐号？
本帖最后由 gujiya 于
04:07 PM 编辑
声明，汉化版本人所有，禁止转载
游戏里的密码& & 1546
终于是汉化完了，说点闲话，这个游戏里的&&yes，ok，yeah之类的词都没汉化，因为感觉翻出来太别扭了，还有就pussy这个词， 翻译软件会翻成 **，**，猫咪几个意思，因为我对**这个词不太太喜欢，翻成**和猫咪的我都没改过来，其实我个人喜欢翻成猫咪，有种朦胧的意境
汉化补丁下载解压，再覆盖原文件就行，我放了两个下载地址，因为我之前发过一个未完全汉化的帖子了，所以补丁地址直接显示了，我还担心有人会说我故意用完整 汉化骗牛盘下载量，就放了两个地址，& &唉，建议多用牛盘地址啊，&&哈哈
PgP1qd1.jpg (218.88 KB, 下载次数: 3)
10:36 PM 上传
QQ截图18.jpg (84.38 KB, 下载次数: 2)
10:36 PM 上传
QQ截图10.jpg (144.77 KB, 下载次数: 0)
10:36 PM 上传
链接： 密码：pnvz
完整汉化补丁& &&&直接覆盖原文件，下载了之前未完全汉化版，下载这个就行了，虽然也不是太多内容，唉，也是用了两天啊
/file-349275.html
链接： 密码：718h
完整汉化版
游客，如果您要查看本帖隐藏内容请
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限20
在线时间26 小时
精华帖子积分
萝莉币: 130
变身萝莉, 积分 163, 距离下一级还需 37 积分
变身萝莉, 积分 163, 距离下一级还需 37 积分
悄悄的把萌主抱走，带回家嘿嘿嘿嘿嘿~
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限200
在线时间177 小时
萝莉币2257
精华帖子积分
萝莉币: 2257
节操: 4474
胖次: 2328
哥特萝莉社的资源就是多，好开心2333
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限60
在线时间62 小时
精华帖子积分
萝莉币: 574
女仆萝莉, 积分 525, 距离下一级还需 75 积分
女仆萝莉, 积分 525, 距离下一级还需 75 积分
哥特萝莉社的资源就是多，好开心2333
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限200
在线时间645 小时
萝莉币3363
精华帖子积分
萝莉币: 3363
节操: 3177
胖次: 1734
哥特萝莉社，只做最专业的二次元资源中心
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限40
在线时间13 小时
精华帖子积分
萝莉币: 37
腹黑萝莉, 积分 398, 距离下一级还需 2 积分
腹黑萝莉, 积分 398, 距离下一级还需 2 积分
我要包养萌主~快跟我回家mua~
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限200
在线时间154 小时
萝莉币3105
精华帖子积分
萝莉币: 3105
节操: 3308
胖次: 1465
哥特萝莉社的资源就是多，好开心2333
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限80
在线时间516 小时
精华帖子积分
萝莉币: 176
胖次: 1026
贵族萝莉, 积分 726, 距离下一级还需 74 积分
贵族萝莉, 积分 726, 距离下一级还需 74 积分
悄悄的把萌主抱走，带回家嘿嘿嘿嘿嘿~
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限40
在线时间152 小时
精华帖子积分
萝莉币: 184
腹黑萝莉, 积分 345, 距离下一级还需 55 积分
腹黑萝莉, 积分 345, 距离下一级还需 55 积分
自从看了萌主的贴 营养越来越跟不上了~
哥特萝莉社官方QQ群：
群主是大蠢萌~
阅读权限200
在线时间113 小时
萝莉币2319
精华帖子积分
萝莉币: 2319
节操: 4032
胖次: 1005
哥特萝莉社的资源就是多，好开心2333
哥特萝莉社官方QQ群：
群主是大蠢萌~
哥特萝莉MC服
哥特萝莉MC服
Powered by今天玩VM，发现数据库不能启动了：
[oracle@lunar1 test]$ ss
SQL*Plus: Release 11.2.0.3.0 Production on Mon Jun 24 05:32:01 2013
Copyright (c) , Oracle.
All rights reserved.
Connected to an idle instance.
SQL& startup
ORACLE instance started.
Total System Global Area
Fixed Size
2230952 bytes
Variable Size
Database Buffers
Redo Buffers
7532544 bytes
ORA-03113: end-of-file on communication channel
Process ID: 12878
Session ID: 125 Serial number: 3
检查alert日志，报错如下：
Mon Jun 24 05:32:16 2013
ORACLE_BASE from environment = /u01/app/oracle
Mon Jun 24 05:32:16 2013
ALTER DATABASE
NOTE: Loaded library: System
ORA-15025: could not open disk &/dev/asm-diske&
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
ORA-15025: could not open disk &/dev/asm-diskf&
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
SUCCESS: diskgroup ASMDATA was mounted
ERROR: failed to establish dependency between database lunar and diskgroup resource ora.ASMDATA.dg
Errors in file /u01/app/oracle/diag/rdbms/lunar/lunar1/trace/lunar1_ckpt_12857.trc
(incident=4945):
ORA-00600: internal error code, arguments: [kfioTranslateIO03], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/lunar/lunar1/incident/incdir_4945/lunar1_ckpt_1.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Mon Jun 24 05:32:19 2013
Sweep [inc][3746]: completed
Sweep [inc][3745]: completed
Sweep [inc2][3746]: completed
Sweep [inc2][3745]: completed
Dumping diagnostic data in directory=[cdmp_21], requested by (instance=1, osid=12857 (CKPT)), summary=[incident=4945].
Errors in file /u01/app/oracle/diag/rdbms/lunar/lunar1/trace/lunar1_ckpt_12857.trc
(incident=4946):
ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/lunar/lunar1/incident/incdir_4946/lunar1_ckpt_1.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ERROR: unrecoverable error ORA-600 raised in ASM I/O terminating process 12857
Dumping diagnostic data in directory=[cdmp_23], requested by (instance=1, osid=12857 (CKPT)), summary=[incident=4946].
Mon Jun 24 05:32:24 2013
PMON (ospid: 12823): terminating the instance due to error 469
System state dump requested by (instance=1, osid=12823 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/lunar/lunar1/trace/lunar1_diag_12833.trc
Mon Jun 24 05:32:25 2013
Dumping diagnostic data in directory=[cdmp_24], requested by (instance=1, osid=12823 (PMON)), summary=[abnormal instance termination].
Instance terminated by PMON, pid = 12823
很久没玩这个VM，隐约记得上次好像测试修改权限了
然后，根据报错查询官网：
ORA-00600: internal error code, arguments: [kfioTranslateIO03], [], [], [], [], [], [], [], [], [], [], []
果然是权限问题，因此检查相关权限并修改。
[oracle@lunar1 ~]$ cd $ORACLE_HOME/bin/
[oracle@lunar1 bin]$ ll oracle
-rwsr-x--x 1 oracle asmadmin 222M May
3 15:11 oracle
[oracle@lunar1 bin]$ chmod 6751 oracle
[oracle@lunar1 bin]$ ll oracle
-rwsr-x--x 1 oracle asmadmin 222M May
3 15:11 oracle
[oracle@lunar1 bin]$
使用root：
[root@lunar1 bin]# chmod 6751 oracle
[root@lunar1 bin]# ll oracle
-rwsr-s--x 1 oracle asmadmin
3 15:11 oracle
[root@lunar1 bin]#
现在启动数据库就不报错了：
[oracle@lunar1 test]$ ss
SQL*Plus: Release 11.2.0.3.0 Production on Mon Jun 24 05:48:33 2013
Copyright (c) , Oracle.
All rights reserved.
Connected to an idle instance.
SQL& startup
ORACLE instance started.
Total System Global Area
Fixed Size
2230952 bytes
Variable Size
Database Buffers
Redo Buffers
7532544 bytes
Database mounted.
Database opened.
在Double-E之间（比如，两个Exadata，或者1个Exadata和1个Exaligic之间），我们可以使用IB来连接
比如两个Exadata之间互相做灾备（ADG）
再比如，Exalogic上有大量的空间，即使是1/4配置的Exalogic上也有几十T的容量空闲（没有部署应用的空间）。
有时候我们会见可以购买了Double-E的客户用这个空间来做Exadata上的数据库的ADG。
为了充分利用IB的传输速度块，低延迟和CPU消耗少等优点，Double-E之间的互联，一般建议通过SDP协议访问Exadata上的数据库
文档建议（Exadata X2和X3），Exadata和Exalogic使用8个IB线进行连接（4跟的话也可以，但是没有冗余，一般不建议）
Exadata 1/4 rack和Exalogic 1/4 rack上分别都有2个叶IB交换机（半配的会有第三个主IB交换机，从Exadata X3开始，出厂时缺省没有最下的主交换机了）
这4个交换机如下：
Exadata-IB1
Exadata–IB2
Exalogic-IB1
Exalogic–IB2
连接方式：
Exadata-IB1——-Exalogic–IB2
Exadata-IB1——-Exalogic–IB1
Exadata-IB2——-Exalogic–IB1
Exadata-IB2——-Exalogic–IB2
配置方式具体如下：
1、修改db node上的/etc/infiniband/openib.conf：
SDP_LOAD=yes
2、在/etc/ofed/libsdp.conf中添加：
use tcp server * *:*
use tcp client * *:*
3、在/etc/modprobe.conf都添加并且reboot节点：
options ib_sdp sdp_zcopy_thresh=0 recv_poll=0
配置Double-E（比如Exadata和ExalogicIB，或者Exadata和Exadata之间的）网络上配置监听：
192.168.10.21 dm01db01- dm01db01-ibvip
192.168.10.22 dm01db02- dm01db02-ibvip
添加network2（for IB）：
[root@dm01db01 ~]# srvctl add network -k 2 -S 192.168.8.0/255.255.252.0/bondib0
[root@dm01db01 ~]#
验证添加结果：
[root@dm01db01 ~]# crsctl stat res -t | grep net
ora.net1.network
ora.net2.network
-- Output indicating new Network resource
[root@dm01db01 ~]#
[root@dm01db01 ~]# srvctl config network -k 2
Network exists: 2/192.168.8.0/255.255.252.0/bondib0, type static
[root@dm01db01 ~]#
[root@dm01db01 ~]# srvctl add vip -n dm01db01 -A dm01db01-ibvip/255.255.252.0/bondib0 -k 2
[root@dm01db01 ~]# srvctl add vip -n dm01db02 -A dm01db02-ibvip/255.255.252.0/bondib0 -k 2
[root@dm01db01 ~]#
检查vip是否可以正常启动：
[root@dm01db01 ~]# srvctl start vip -i dm01db01-ibvip
[root@dm01db01 ~]#
[root@dm01db02 ~]# srvctl start vip -i dm01db02-ibvip
[root@dm01db02 ~]#
添加这个IB网络的监听（LISTENER_IB）：
[root@dm01db01 ~]# srvctl add listener -l LISTENER_IB -k 2 -p TCP:1522,/SDP:1522
[root@dm01db01 ~]# srvctl start listener -l LISTENER_IB
[root@dm01db01 ~]#
[grid@dm01db01 ~]$ lsnrctl status listener_ib
LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 18-DEC-:15
Copyright (c) , Oracle.
All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_IB)))
STATUS of the LISTENER
------------------------
LISTENER_IB
TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date
18-DEC-:03
0 days 0 hr. 2 min. 11 sec
Trace Level
ON: Local OS Authentication
Listener Parameter File
/u01/app/11.2.0.3/grid/network/admin/listener.ora
Listener Log File
/u01/app/oracle/diag/tnslsnr/dm01db01/listener_ib/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER_IB)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.21)(PORT=1522)))
The listener supports no services
The command completed successfully
[grid@dm01db01 ~]$
配置tnsnames.ora
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01-scan)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dbfs)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01-scan)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = LUNARDB)
#the following are for IB
LISTENER_IBREMOTE=
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01db02-)(PORT = 1522))
LISTENER_IBLOCAL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01db01-)(PORT = 1522))
(ADDRESS = (PROTOCOL = SDP)(HOST = dm01db01-)(PORT = 1522))
LISTENER_IPLOCAL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dm0101-)(PORT = 1521))
LISTENER_IPREMOTE=
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01-)(PORT = 1521))
LUNARDB_IB =
(DESCRIPTION =
(LOAD_BALANCE=on)
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01db01-ibvip)(PORT = 1522))
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01db02-ibvip)(PORT = 1522))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = LUNARDB)
修改数据库参数listener_networks：
SQL& alter system set listener_networks='((NAME=network2) (LOCAL_LISTENER=LISTENER_IBLOCAL)(REMOTE_LISTENER=LISTENER_IBREMOTE))', '((NAME=network1)(LOCAL_LISTENER=LISTENER_IPLOCAL)(REMOTE_LISTENER=LISTENER_IPREMOTE))' scope=
System altered.
测试连接，使用oracle用户：
conn sys/oracle@LUNARDB
conn sys/oracle@LUNARDB_IB
在客户端（Exalogic或者其他需要连接db的主机上），需要配置 如下连接串：
LUNARDB_IB =
(DESCRIPTION =
(LOAD_BALANCE=on)
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01db01-ibvip)(PORT = 1522))
(ADDRESS = (PROTOCOL = TCP)(HOST = dm01db02-ibvip)(PORT = 1522))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = LUNARDB)
好了，这样Exalogic就可以使用IB连接Exadata了。
===========================================
单进程，每分钟： 16G（每小时960G）
7分钟，导完LUNAR_P
请注意下面的过程 parallel=1，表示单进程测试
（只能测试单进程，是因为跟我同事的导出方式有关系，明天测试多进程……）
===========================================
[oracle@dm01db01 lunar]$ nohup impdp LUNAR/passwd content=DATA_ONLY DIRECTORY=lunar JOB_NAME=impdp_LUNAR_P parallel=1 TABLES=LUNAR.LUNAR DUMPFILE=LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp REMAP_TABLE=LUNAR.LUNAR:LUNAR_P logfile=impdp_LUNAR_P.log &
[oracle@dm01db01 lunar]$ nohup: ignoring input and appending output to `nohup.out'
[oracle@dm01db01 lunar]$ jobs
nohup impdp LUNAR/passwd content=DATA_ONLY DIRECTORY=lunar JOB_NAME=impdp_LUNAR_P parallel=1 TABLES=LUNAR.LUNAR DUMPFILE=LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp REMAP_TABLE=LUNAR.LUNAR:LUNAR_P logfile=impdp_LUNAR_P.log &
[oracle@dm01db01 lunar]$ jobs
nohup impdp LUNAR/passwd content=DATA_ONLY DIRECTORY=lunar JOB_NAME=impdp_LUNAR_P parallel=1 TABLES=LUNAR.LUNAR DUMPFILE=LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp REMAP_TABLE=LUNAR.LUNAR:LUNAR_P logfile=impdp_LUNAR_P.log &
[oracle@dm01db01 lunar]$ tail -f nohup.out
Import: Release 11.2.0.4.0 - Production on Thu Apr 23 00:05:53 2015
Copyright (c) , Oracle and/or its affiliates.
All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Master table &LUNAR&.&IMPDP_LUNAR_P& successfully loaded/unloaded
Starting &LUNAR&.&IMPDP_LUNAR_P&:
LUNAR/******** content=DATA_ONLY DIRECTORY=lunar JOB_NAME=impdp_LUNAR_P parallel=1 TABLES=LUNAR.LUNAR DUMPFILE=LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp REMAP_TABLE=LUNAR.LUNAR:LUNAR_P logfile=impdp_LUNAR_P.log
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
导入过程中进行检测：
可以看到exadata聪明的选择了直接裸盘，没有走Flashcache，每秒钟吞吐量大概460MB左右（一起开始时候会有一个高峰大概有2倍的这个值，猜测是由于分配空间等等）
Current Time: Thu Apr 23 00:06:30 CST 2015
ONLY RECEIVED DATA FROM 4 NODES, INSTEAD OF 5 NODES!
&---------------Disks------------------&&---------------Flash------------------&&--------CPU----------&&-----------Memory-------&
MBRead Reads RSize MBWrit Writes WSize
MBRead Reads RSize MBWrit Writes WSize
User Sys Wait Irq Run
FreeMB SwapMB SwIn SwOut
TotalIO: 708 MB/s;
DiskRead: 0 MB/s;
DiskWrite: 708 MB/s;
FlashRead: 0 MB/s;
FlashWrite: 0 MB/s;
Average CPU: 5%;
&--------CPU----------&&---------------Disks------------------&&-----------Memory-------&
User Sys Wait Irq Run
MBRead Reads RSize MBWrit Writes WSize
FreeMB SwapMB SwIn SwOut
Average CPU: 3%;
大概2~3分钟后，存储节点总的吞吐量稳定在每秒钟460MB：
Current Time: Thu Apr 23 00:08:24 CST 2015
ONLY RECEIVED DATA FROM 4 NODES, INSTEAD OF 5 NODES!
&---------------Disks------------------&&---------------Flash------------------&&--------CPU----------&&-----------Memory-------&
MBRead Reads RSize MBWrit Writes WSize
MBRead Reads RSize MBWrit Writes WSize
User Sys Wait Irq Run
FreeMB SwapMB SwIn SwOut
TotalIO: 464 MB/s;
DiskRead: 0 MB/s;
DiskWrite: 464 MB/s;
FlashRead: 0 MB/s;
FlashWrite: 0 MB/s;
Average CPU: 3%;
&--------CPU----------&&---------------Disks------------------&&-----------Memory-------&
User Sys Wait Irq Run
MBRead Reads RSize MBWrit Writes WSize
FreeMB SwapMB SwIn SwOut
Average CPU: 2%;
===========================================
测试结果：
在数据库中实测的数据（按照每分钟这个表的增长大小来计算）
单进程，导入速度每分钟： 16G
7分钟，导完LUNAR_P，该表大概309GB（按照这个测试，每小时大概2.5TB左右）
===========================================
SYS@lunar1&set timing on
SYS@lunar1&set time on
00:07:25 SYS@lunar1&col segment_name format a45 heading &Segment Name&
00:07:32 SYS@lunar1&select sum(bytes)/24
&Size In GB&
from dba_segments
where owner in upper('LUNAR')
order by 1;
Size In GB
----------------
Elapsed: 00:00:00.13
Size In GB
----------------
Elapsed: 00:00:00.03
00:08:31 SYS@lunar1&
。。。。。
00:13:25 SYS@lunar1&/
Size In GB
----------------
--------------改表总共309GB
Elapsed: 00:00:00.03
00:13:27 SYS@lunar1&
[oracle@dm01db01 lunar]$ tail -f nohup.out
Import: Release 11.2.0.4.0 - Production on Thu Apr 23 00:05:53 2015
Copyright (c) , Oracle and/or its affiliates.
All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Master table &LUNAR&.&IMPDP_LUNAR_P& successfully loaded/unloaded
Starting &LUNAR&.&IMPDP_LUNAR_P&:
LUNAR/******** content=DATA_ONLY DIRECTORY=lunar JOB_NAME=impdp_LUNAR_P parallel=1 TABLES=LUNAR.LUNAR DUMPFILE=LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp REMAP_TABLE=LUNAR.LUNAR:LUNAR_P logfile=impdp_LUNAR_P.log
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported &LUNAR&.&LUNAR_P&:&LUNAR_P&
. . imported &LUNAR&.&LUNAR_P&:&LUNAR_P&
. . imported &LUNAR&.&LUNAR_P&:&LUNAR_P&
. . imported &LUNAR&.&LUNAR_P&:&LUNAR_P&
. . imported &LUNAR&.&LUNAR_P&:&LUNAR_P&
Job &LUNAR&.&IMPDP_LUNAR_P& successfully completed at Thu Apr 23 00:12:55 2015 elapsed 0 00:07:02
nohup impdp LUNAR/passwd content=DATA_ONLY DIRECTORY=lunar JOB_NAME=impdp_LUNAR_P parallel=1 TABLES=LUNAR.LUNAR DUMPFILE=LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp,LUNAR_P.dmp REMAP_TABLE=LUNAR.LUNAR:LUNAR_P logfile=impdp_LUNAR_P.log
[oracle@dm01db01 lunar]$
===========================================
注意上面： elapsed 0 00:07:02
也就是说，7分钟导入数据309GB
Exadata上配置万兆非常简单，就是设置一下网卡，然后绑定即可
根据文档描述，万兆光口对应的接口如下：
Exadata Database Machine X5-2的eth4和eth5
不同的机器，可能接口名称不同，可以在机器上看，也可以核对文档来识别。
（1）Exadata上，有两个光口，是千兆万兆自适应的，但是10Gib模块需要单独购买。
（2）Exadata上，4个电口是百兆，千兆，万兆自适应的
下面的是一个例子：
例如，电口的eth0（用于连接内置的Cisco）：
[root@dm01db02 ~]# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:
100baseT/Full
1000baseT/Full
10000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:
100baseT/Full
1000baseT/Full
10000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
Transceiver: external
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Current message level: 0x)
drv probe link
Link detected: yes
[root@dm01db02 ~]#
连接了万兆的eth4：
[root@dm01db01 ~]# ethtool eth4
Settings for eth4:
Supported ports: [ FIBRE ]
Supported link modes:
10000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: No
Advertised link modes:
10000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10000Mb/s
------------这里显示为万兆
Duplex: Full
-----------全双工
Port: Other
Transceiver: external
Auto-negotiation: off
Supports Wake-on: d
Wake-on: d
Current message level: 0x)
drv probe link
Link detected: yes
[root@dm01db01 ~]#
然后设置一下IP，按照linux上绑定网卡的方法将eth4和eth5绑定即可。
万兆配置好了，测试了一下万兆的效率（还没时间做测试跨机房）：
下载了iperf安装在exadata上：
[root@dm01db01 tmp]# mkdir lunar
[root@dm01db01 tmp]# mv iperf-3.0.tar.gz lunar/
[root@dm01db01 tmp]# cd lunar/
[root@dm01db01 lunar]# ls
iperf-3.0.tar.gz
[root@dm01db01 lunar]# tar zxvf iperf-3.0.tar.gz
[root@dm01db01 lunar]# cd iperf
[root@dm01db01 iperf]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
..................
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking for library containing nanosleep... none required
checking for library containing hstrerror... none required
checking for an ANSI C-conforming const... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/config.h
config.status: src/config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
[root@dm01db01 iperf]# make && make install
Making all in src
make[1]: Entering directory `/tmp/lunar/iperf/src'
make[2]: Entering directory `/tmp/lunar/iperf/src'
gcc -DHAVE_CONFIG_H -I.
-g -O2 -MT cjson.o -MD -MP -MF .deps/cjson.Tpo -c -o cjson.o cjson.c
mv -f .deps/cjson.Tpo .deps/cjson.Po
gcc -DHAVE_CONFIG_H -I.
-g -O2 -MT iperf_api.o -MD -MP -MF .deps/iperf_api.Tpo -c -o iperf_api.o iperf_api.c
mv -f .deps/iperf_api.Tpo .deps/iperf_api.Po
gcc -DHAVE_CONFIG_H -I.
-g -O2 -MT iperf_error.o -MD -MP -MF .deps/iperf_error.Tpo -c -o iperf_error.o iperf_error.c
mv -f .deps/iperf_error.Tpo .deps/iperf_error.Po
gcc -DHAVE_CONFIG_H -I.
-g -O2 -MT iperf_client_api.o -MD -MP -MF .deps/iperf_client_api.Tpo -c -o iperf_client_api.o iperf_client_api.c
。。。。。。。。。。。。。。。。
/usr/bin/install -c -m 644 'iperf_api.h' '/usr/local/include/iperf_api.h'
test -z &/usr/local/share/man/man1& || /bin/mkdir -p &/usr/local/share/man/man1&
/usr/bin/install -c -m 644 './iperf3.1' '/usr/local/share/man/man1/iperf3.1'
test -z &/usr/local/share/man/man3& || /bin/mkdir -p &/usr/local/share/man/man3&
/usr/bin/install -c -m 644 './libiperf.3' '/usr/local/share/man/man3/libiperf.3'
make[2]: Leaving directory `/tmp/lunar/iperf/src'
make[1]: Leaving directory `/tmp/lunar/iperf/src'
make[1]: Entering directory `/tmp/lunar/iperf'
make[2]: Entering directory `/tmp/lunar/iperf'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/tmp/lunar/iperf'
make[1]: Leaving directory `/tmp/lunar/iperf'
[root@dm01db01 iperf]# which iperf3
/usr/local/bin/iperf3
[root@dm01db01 iperf]#
测试了一下，每秒基本上可以达到7Gb(大概7Gb/8≈700MB/s)：
[root@dm01db01 modprobe.d]# iperf3 -c 10.10.10.12 -n 30G
Connecting to host 10.10.10.12, port 5201
4] local 10.10.10.11 port 42491 connected to 10.10.10.12 port 5201
[ ID] Interval
Retransmits
619 MBytes
5.19 Gbits/sec
696 MBytes
5.84 Gbits/sec
680 MBytes
5.70 Gbits/sec
746 MBytes
6.26 Gbits/sec
741 MBytes
6.22 Gbits/sec
750 MBytes
6.29 Gbits/sec
783 MBytes
6.57 Gbits/sec
838 MBytes
7.03 Gbits/sec
838 MBytes
7.03 Gbits/sec
9.00-10.00
838 MBytes
7.03 Gbits/sec
10.00-11.00
827 MBytes
6.94 Gbits/sec
11.00-12.00
898 MBytes
7.53 Gbits/sec
12.00-13.00
905 MBytes
7.59 Gbits/sec
13.00-14.00
1.01 GBytes
8.71 Gbits/sec
14.00-15.00
967 MBytes
8.11 Gbits/sec
15.00-16.00
933 MBytes
7.83 Gbits/sec
16.00-17.00
1.01 GBytes
8.65 Gbits/sec
17.00-18.00
913 MBytes
7.66 Gbits/sec
18.00-19.00
1018 MBytes
8.54 Gbits/sec
19.00-20.00
928 MBytes
7.79 Gbits/sec
20.00-21.00
1.01 GBytes
8.66 Gbits/sec
21.00-22.00
1.03 GBytes
8.81 Gbits/sec
22.00-23.00
1.02 GBytes
8.73 Gbits/sec
23.00-24.00
1.03 GBytes
8.82 Gbits/sec
24.00-25.00
928 MBytes
7.78 Gbits/sec
25.00-26.00
805 MBytes
6.75 Gbits/sec
26.00-27.00
944 MBytes
7.92 Gbits/sec
27.00-28.00
929 MBytes
7.79 Gbits/sec
28.00-29.00
1.02 GBytes
8.74 Gbits/sec
29.00-30.00
1020 MBytes
8.56 Gbits/sec
30.00-31.00
926 MBytes
7.77 Gbits/sec
31.00-32.00
1.02 GBytes
8.80 Gbits/sec
32.00-33.00
1.01 GBytes
8.68 Gbits/sec
33.00-33.86
879 MBytes
8.59 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval
Retransmits
0.00-33.86
30.0 GBytes
7.61 Gbits/sec
0.00-33.86
30.0 GBytes
7.61 Gbits/sec
iperf Done.
[root@dm01db01 modprobe.d]#
昨天Exadata上发出了一封靓丽的告警邮件，如下图：
没见过这么漂亮的邮件，清晰的告诉你是什么部件（可惜我还不认识那个大大的就是CPU……汗……）
又惊又喜的傻Lunar以为硬件坏了，高兴的是，SUN的ILOM的告警做的真棒啊
但是奇怪的是才用了没多久啊，而且比较爱惜的，怎么回事？
后来，在oracle官网搜索这个硬件, 发现是CPU边上的一个部件，貌似PCIe“故障”了。系统组的同事log了SR，等待回复。
晚上回家，按照以往的管理，我也到ILOM上搜索了一下，然后按照官方文档收集了ILOM的snapshot和一些必要信息传到SR上，SR的回复我没看懂：
也就是说，33%的可能是是硬件损坏……
在oracle官网找到如下方法判断，下面的输出是ILOM 3.2以上的输出（老版本的输出本文后面有例子）
-& start /SP/faultmgmt/shell
Are you sure you want to start /SP/faultmgmt/shell (y/n)? y
faultmgmtsp& fmadm faulty
------------------- ------------------------------------ -------------- --------
------------------- ------------------------------------ -------------- --------
/15:13:42 xxxxxxx-xxxxx-xxxx-xxx-xxxxxxxxx xxxX86A-xxxx-xxx Critical
Problem Status
Diag Engine
Manufacturer
: Oracle Corporation
: Exadata X5-2
Part_Number
: Exadata X5-2
System Component
Manufacturer
: Oracle Corporation
: ORACLE SERVER X5-2
----------------------------------------
Suspect 1 of 3
Fault class
: fault.io.intel.iio.pcie-fatal
: /SYS/MB/RISER2/PCIE2
----------这个就是文档中说的那个拗口的“PCIe 竖隔板”，2表示槽位2
: /SYS/MB/RISER2/PCIE2
Manufacturer
: Oracle Corporation
: ORACLE SERVER X5-2
----------------------------------------
Suspect 2 of 3
Fault class
: fault.io.intel.iio.pcie-fatal
: /SYS/MB/P0
------------这个表示是CPU
: /SYS/MB/P0
: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
Manufacturer
: Oracle Corporation
: ORACLE SERVER X5-2
----------------------------------------
Suspect 3 of 3
Fault class
: fault.io.intel.iio.pcie-fatal
-------------这个表示是主板
Manufacturer
: MiTAC International Corporation
: ASM,MOTHERBOARD,1U
Manufacturer
: Oracle Corporation
Description : An integrated I/O (II0) fatal error in a downstream PCIE
device has been detected.
: The service-required LED on the chassis is illuminated.
: The server will reset, however the affected processor is not
disabled to allow the host OS to boot up and operate in the
presence of a faulty processor.
: Please refer to the associated reference document at
/msg/SPX86A-8002-RK for the latest
service procedures and policies regarding this diagnosis.
faultmgmtsp&
收集的信息，跟SR上老外的回复差不多，也是每个部件都有33%的可能性是硬件损坏……
按照以往的理解，猜测是“先兆损坏”，通常这种情况，工程师可能会把硬件进行一次插拔，如果没问题就算了，如果有问题，可能就是硬件损坏。
于是又到ILOM上检查，什么硬件，根据文档说明和ILOM的指示，大概知道是什么东西了（虽然每个东西长什么样子，我没见过……基本上从毕业后就没有拆过机箱，摸过螺丝的Lunar感觉很无奈……）：
————-这个表示是主板
/SYS/MB/P0
————这个表示是CPU
/SYS/MB/RISER2/PCIE2
———-这个就是文档中说的那个拗口的“PCIe 竖隔板”，2表示槽位2
找到硬件工程师问了一下，这个问题是因为我们插入万兆模块的时候，报的告警，不过奇怪的是为什么oracle文档中没有写明“更换万兆模块需要关机？”
行了，知道了不是硬件问题，clear即可，这个文档上有，照做即可：
-& start /SP/faultmgmt/shell
Are you sure you want to start /SP/faultmgmt/shell (y/n)? y
faultmgmtsp& fmadm repair xxxxxxxx-xxxx-xxxxxx-xxxxxxxxx
faultmgmtsp& fmadm repair /SYS/MB
faultmgmtsp&
检查清除结果：
faultmgmtsp& fmadm faulty
No faults found
faultmgmtsp&
顺便介绍一下老版本的ILOM输出（ILOM 3.2以前）：
—举例1： 输出类似 FRU : /SYS/FANBD/FM0，这个就指出了损坏的FRU是具体对应到主机上的哪一个物理组件（full physical path）
—”/SYS”
底架（chassis），我理解可能是主机架，就是拆开挡板后，所有东西都插在上面的那个主机箱的含义。
—”FANBD” 风扇模块 （fan board）
—”FM0″
具体哪一个风扇模块（Fan Module）
—举例2： 输出类似 FRU : /SYS/MB，这个就指出了损坏的FRU是具体对应到主机上的哪一个物理组件（full physical path）
—”/SYS” 底架（chassis），我理解可能是主机架，就是拆开挡板后，所有东西都插在上面的那个主机箱的含义。
—’/MB’ 表示主板（ Mother Board）
帮一个朋友整理的，顺便发到blog。
使用duplicate克隆数据库： 将宝宝数据库科隆为Lunar数据库
这部分东西不是新东西，clone在8i就是可以手工做的，在9i还是10g（忘记了），就被封装成duplicat命令了。
之前的测试参见
不过一般我更喜欢手工用rman做，每一步都透明，每一步都可控可回退可追查可修改。
duplicate自动化了，但是出问题后就是整体全部重来，万一有问题，比较耽误时间。
具体步骤如下：
在备库创建目录：
mkdir -p /u01/app/oracle/admin/lunar/adump
mkdir -p /u01/app/oracle/admin/lunar/bdump
mkdir -p /u01/app/oracle/admin/lunar/cdump
mkdir -p /u01/app/oracle/admin/lunar/udump
mkdir -p /u01/app/oracle/oradata/lunar
mkdir -p /u01/app/oracle/diag/rdbms/lunar/lunar
mkdir -p /u01/app/oracle/oradata/lunar
宝宝数据库的参数文件：
*.audit_file_dest='/u01/app/oracle/admin/lunar/adump'
*.audit_trail='none'
*.compatible='11.2.0.3.0'
*.control_files='/u01/app/oracle/oradata/lunar/control01.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='bb'
*.diagnostic_dest='/u01/app/oracle'
*.open_cursors=300
*.pga_aggregate_target=
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=
*.undo_tablespace='UNDOTBS1'
*.job_queue_processes=10
*.db_unique_name='bb'
*.log_archive_dest_1='location=/u01/archive/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=lunar'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_max_processes=5
Lunar数据库使用的参数文件：
*.audit_file_dest='/u01/app/oracle/admin/lunar/adump'
*.audit_trail='none'
*.compatible='11.2.0.3.0'
*.control_files='/u01/app/oracle/oradata/lunar/control01.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='lunar'
*.diagnostic_dest='/u01/app/oracle'
*.open_cursors=300
*.pga_aggregate_target=
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=
*.undo_tablespace='UNDOTBS1'
*.job_queue_processes=10
*.db_unique_name='lunar'
*.log_archive_dest_1='location=/u01/archive/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=lunar'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_max_processes=5
创建监听：
[oracle@lunar admin]$ cat listener.ora
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0.3/dbhome_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.58.66)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = bb)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/dbhome_1)
(SID_NAME = bb)
(SID_DESC =
(GLOBAL_DBNAME = lunar)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/dbhome_1)
(SID_NAME = lunar)
ADR_BASE_LISTENER = /u01/app/oracle
创建tnsnames.ora文件
[oracle@lunar admin]$
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.66)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = bb)
(SID_NAME = bb)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.99)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = lunar)
(SID_NAME = lunar)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.66)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = lunar)
(SID_NAME = lunar)
测试连接：
[oracle@lunar lunardb]$ . ~/lunar.env
[oracle@lunar lunardb]$ ss
SQL*Plus: Release 11.2.0.3.0 Production on Mon Jan 28 00:53:25 2013
Copyright (c) , Oracle.
All rights reserved.
Connected to an idle instance.
SQL& startup nomount pfile=/test/lunardb/pfilelunar.ora
ORACLE instance started.
Total System Global Area
Fixed Size
2230024 bytes
Variable Size
Database Buffers
Redo Buffers
7962624 bytes
[oracle@lunar ~]$ . bb.env
[oracle@lunar ~]$ ss
SQL*Plus: Release 11.2.0.3.0 Production on Mon Jan 28 01:03:35 2013
Copyright (c) , Oracle.
All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL& connect sys/oracle@bb as sysdba
Connected.
SQL& connect sys/oracle@lunar as sysdba
Connected.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
创建口令文件：
[oracle@lunar admin]$ cd $ORACLE_HOME/dbs
[oracle@lunar dbs]$ ls
10o0goff_1_1
11o0gogi_1_1
hc_lunar.dat
snapcf_bb.f
spfilebb.ora
[oracle@lunar dbs]$ cp orapwbb orapwlunar
[oracle@lunar dbs]$
开始duplicate：
[oracle@lunar lunar]$ . ~/lunar.env
[oracle@lunar lunar]$ ss
SQL*Plus: Release 11.2.0.3.0 Production on Mon Jan 28 01:36:58 2013
Copyright (c) , Oracle.
All rights reserved.
Connected to an idle instance.
SQL& startup nomount pfile=/test/lunardb/pfilelunar.ora
ORACLE instance started.
Total System Global Area
Fixed Size
2230024 bytes
Variable Size
Database Buffers
Redo Buffers
7962624 bytes
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@lunar lunar]$ rman target sys/oracle@bb auxiliary sys/oracle@lunar
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Jan 28 01:37:25 2013
Copyright (c) , Oracle and/or its affiliates.
All rights reserved.
connected to target database: BB (DBID=)
connected to auxiliary database: lunar (not mounted)
RMAN& run{
2& set newname for datafile 1 to '/test/lunardb/SYSTEM01.DBF';
3& set newname for datafile 2 to '/test/lunardb/undotbs01.DBF';
4& set newname for datafile 3 to '/test/lunardb/sysaux01.DBF';
5& set newname for datafile 4 to '/test/lunardb/users01.DBF';
6& set newname for datafile 5 to '/test/lunardb/temp01.DBF';
7& duplicate target database to lunar nofilenamecheck logfile
8& '/test/lunardb/redo01.log' size 10m,
9& '/test/lunardb/redo02.log' size 10m,
10& '/test/lunardb/redo03.log' size 10m;
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 28-JAN-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=134 device type=DISK
contents of Memory Script:
sql clone &create spfile from memory&;
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area
Fixed Size
2230024 bytes
Variable Size
Database Buffers
Redo Buffers
7962624 bytes
contents of Memory Script:
sql clone &alter system set
''BB'' comment=
''Modified by RMAN duplicate'' scope=spfile&;
sql clone &alter system set
db_unique_name =
''lunar'' comment=
''Modified by RMAN duplicate'' scope=spfile&;
startup clone force nomount
restore clone
executing Memory Script
sql statement: alter system set
''BB'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set
db_unique_name =
''lunar'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area
Fixed Size
2230024 bytes
Variable Size
Database Buffers
Redo Buffers
7962624 bytes
Starting restore at 28-JAN-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=133 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /u01/app/oracle/product/11.2.0.3/dbhome_1/dbs/11o0gogi_1_1
channel ORA_AUX_DISK_1: piece handle=/u01/app/oracle/product/11.2.0.3/dbhome_1/dbs/11o0gogi_1_1 tag=TAG847
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/u01/app/oracle/oradata/lunar/control01.ctl
Finished restore at 28-JAN-13
database mounted
contents of Memory Script:
set until scn
set newname for datafile
&/test/lunardb/SYSTEM01.DBF&;
set newname for datafile
&/test/lunardb/undotbs01.DBF&;
set newname for datafile
&/test/lunardb/sysaux01.DBF&;
set newname for datafile
&/test/lunardb/users01.DBF&;
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 28-JAN-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /test/lunardb/SYSTEM01.DBF
channel ORA_AUX_DISK_1: restoring datafile 00002 to /test/lunardb/undotbs01.DBF
channel ORA_AUX_DISK_1: restoring datafile 00003 to /test/lunardb/sysaux01.DBF
channel ORA_AUX_DISK_1: restoring datafile 00004 to /test/lunardb/users01.DBF
channel ORA_AUX_DISK_1: reading from backup piece /u01/app/oracle/product/11.2.0.3/dbhome_1/dbs/10o0goff_1_1
channel ORA_AUX_DISK_1: piece handle=/u01/app/oracle/product/11.2.0.3/dbhome_1/dbs/10o0goff_1_1 tag=TAG847
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:55
Finished restore at 28-JAN-13
contents of Memory Script:
executing Memory Script
datafile 1 switched to datafile copy
input datafile copy RECID=11 STAMP= file name=/test/lunardb/SYSTEM01.DBF
datafile 2 switched to datafile copy
input datafile copy RECID=12 STAMP= file name=/test/lunardb/undotbs01.DBF
datafile 3 switched to datafile copy
input datafile copy RECID=13 STAMP= file name=/test/lunardb/sysaux01.DBF
datafile 4 switched to datafile copy
input datafile copy RECID=14 STAMP= file name=/test/lunardb/users01.DBF
contents of Memory Script:
set until scn
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 28-JAN-13
using channel ORA_AUX_DISK_1
starting media recovery
archived log for thread 1 with sequence 43 is already on disk as file /u01/archive/1_43_.dbf
archived log file name=/u01/archive/1_43_.dbf thread=1 sequence=43
media recovery complete, elapsed time: 00:00:00
Finished recover at 28-JAN-13
Oracle instance started
Total System Global Area
Fixed Size
2230024 bytes
Variable Size
Database Buffers
Redo Buffers
7962624 bytes
contents of Memory Script:
sql clone &alter system set
''lunar'' comment=
''Reset to original value by RMAN'' scope=spfile&;
sql clone &alter system reset
db_unique_name scope=spfile&;
executing Memory Script
sql statement: alter system set
''lunar'' comment= ''Reset to original value by RMAN'' scope=spfile
sql statement: alter system reset
db_unique_name scope=spfile
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area
Fixed Size
2230024 bytes
Variable Size
Database Buffers
Redo Buffers
7962624 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE &lunar& RESETLOGS ARCHIVELOG
MAXLOGFILES
MAXLOGMEMBERS
MAXDATAFILES
MAXINSTANCES
MAXLOGHISTORY
1 '/test/lunardb/redo01.log' SIZE 10 M ,
2 '/test/lunardb/redo02.log' SIZE 10 M ,
3 '/test/lunardb/redo03.log' SIZE 10 M
'/test/lunardb/SYSTEM01.DBF'
CHARACTER SET AL32UTF8
contents of Memory Script:
set newname for tempfile
&/u01/app/oracle/oradata/bb/temp01.dbf&;
catalog clone datafilecopy
&/test/lunardb/undotbs01.DBF&,
&/test/lunardb/sysaux01.DBF&,
&/test/lunardb/users01.DBF&;
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /u01/app/oracle/oradata/bb/temp01.dbf in control file
cataloged datafile copy
datafile copy file name=/test/lunardb/undotbs01.DBF RECID=1 STAMP=
cataloged datafile copy
datafile copy file name=/test/lunardb/sysaux01.DBF RECID=2 STAMP=
cataloged datafile copy
datafile copy file name=/test/lunardb/users01.DBF RECID=3 STAMP=
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP= file name=/test/lunardb/undotbs01.DBF
datafile 3 switched to datafile copy
input datafile copy RECID=2 STAMP= file name=/test/lunardb/sysaux01.DBF
datafile 4 switched to datafile copy
input datafile copy RECID=3 STAMP= file name=/test/lunardb/users01.DBF
Reenabling controlfile options for auxiliary database
Executing: alter database add supplemental log data
Executing: alter database force logging
contents of Memory Script:
Alter clone dat
executing Memory Script
database opened
Finished Duplicate Db at 28-JAN-13
克隆完成，创建临时文件：
[oracle@lunar lunar]$ . ~/lunar.env
[oracle@lunar lunar]$ ss
SQL*Plus: Release 11.2.0.3.0 Production on Mon Jan 28 01:40:32 2013
Copyright (c) , Oracle.
All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL& select NAME,OPEN_MODE from v$
------------------ ----------------------------------------
READ WRITE
SQL& ALTER DATABASE TEMPFILE '/u01/app/oracle/oradata/bb/temp01.dbf' DROP
INCLUDING DATAFILES;
Database altered.
SQL& ALTER TABLESPACE temp ADD TEMPFILE '/test/lunardb/temp01.DBF' SIZE 10M;
Tablespace altered.
帮一个朋友整理的，顺便发到blog。
数据库克隆操作文档
一．前提说明:
1. 本测试是在同一台机器上完成，而在同一台机器中ORACLE_SID不可相同，所以涉及到克隆库修改ORACLE_SID问题
2. 为了使得本次操作能够更好的让客户了解其过程，使用了传统的rman备份来实现,而没有使用duplicate相关命令实现
如果在不同机器上使用rman备份做异机恢复，就不用修改SID，保持跟以前一样就可以（步骤差不多，比同机克隆更简单）
二．整体思路:
1. 关闭lunar
2，使用pfile.lunar.bak（DB_NAME=lunar）nomount database
3，恢复控制文件
4，恢复数据文件（SET NEWNAME）
5，shutdown abort（lunar）
6，export ORACLE_SID=lunar
7，使用pfile.lunar.bak（DB_NAME=lunar）nomount database
8，重建控制文件（SET DATABASE “lunar”）
9，catalog start with
10，recover database
11，alter database open resetlogs
三．详细步骤
1，备份数据库lunar
rman target /
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
CONFIGURE DEVICE TYPE DISK PARALLELISM 12 BACKUP TYPE TO BACKUPSET;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/lunartest/databasefiles_%d_%U_%s'
plus archivelog FORMAT '/lunartest/archivelogs_%d_%U_%s_%T'
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/lunartest/controlfile_%d_%U_%s';
2，创建lunar的spfile
[oracle@gg lunartest]$ cat pfile.lunar.bak
*.aq_tm_processes=0
*.audit_file_dest='/home/oracle/product/admin/lunar/adump'
*.background_dump_dest='/home/oracle/product/admin/lunar/bdump'
*.compatible='11.2.0.2.0'
*.control_files='/home/oracle/product/oradata/lunar/controlfile/o1_mf_3sfb1t6n_.ctl'
*.core_dump_dest='/home/oracle/product/admin/lunar/cdump'
*.db_block_size=8192
*.db_create_file_dest='/home/oracle/product/oradata'
*.db_domain=''
*.db_file_multiblock_read_count=8
*.db_name='lunar'
*.db_recovery_file_dest='/home/oracle/product/flash_recovery_area'
*.db_recovery_file_dest_size=
*.job_queue_processes=0
*.open_cursors=300
*.pga_aggregate_target=
*.processes=150
*.recyclebin='OFF'
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/home/oracle/product/admin/lunar/udump'
#db_name = &lunar&
#instance_name = lunar
#service_names = lunar
3，关闭lunar实例
[oracle@com lunartest]$ ps -ef|grep pmon
00:00:03 ora_pmon_lunar
0 22:18 pts/2
00:00:00 grep pmon
[oracle@com lunartest]$ export ORACLE_SID=lunar
[oracle@com lunartest]$
[oracle@com lunartest]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.2.0 - Production on Sun Sep 23 22:19:24 2012
Copyright (c) , Oracle.
All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL& shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
4，使用pfiel.lunar.ora把lunar实例nomount
mkdir -p /home/oracle/oracle/product/admin/lunar/adump
mkdir -p /home/oracle/oracle/product/admin/lunar/bdump
mkdir -p /home/oracle/oracle/product/oradata/lunar/controlfile/o1_mf_3sfb1t6n_.ctl
mkdir -p /home/oracle/oracle/product/admin/lunar/cdump
mkdir -p /home/oracle/oracle/product/oradata
mkdir -p /home/oracle/oracle/product/flash_recovery_area
mkdir -p /home/oracle/oracle/product/admin/lunar/udump
nomount数据库：
[oracle@com lunartest]$ ss
SQL*Plus: Release 10.2.0.2.0 - Production on Sun Sep 23 22:36:22 2012
Copyright (c) , Oracle.
All rights reserved.
Connected to an idle instance.
SQL& startup nomount pfile=pfile.lunar.ora
ORACLE instance started.
Total System Global Area
Fixed Size
1218316 bytes
Variable Size
Database Buffers
Redo Buffers
2973696 bytes
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
[oracle@com lunartest]$
5， 恢复控制文件
allocate channel c1
restore controlfile from '/lunartest/c--';
release channel c1;
6， 恢复数据文件
allocate channel c1
set newname for datafile 1 to '+DATA_DM01' ;
set newname for datafile 2 to '+DATA_DM01' ;
set newname for datafile 3 to '/home/oracle/product/oradata/lunar/datafile/sysaux01.dbf' ;
set newname for datafile 4 to '/home/oracle/product/oradata/lunar/datafile/users01.dbf' ;
set newname for datafile 5 to '/home/oracle/product/oradata/lunar/datafile/example01.dbf' ;
set newname for datafile 6 to '/home/oracle/product/oradata/lunar/datafile/inventory01.dbf' ;
set newname for datafile 7 to '/home/oracle/product/oradata/lunar/datafile/odi_default.dbf' ;
set newname for datafile 8 to '/home/oracle/product/oradata/lunar/datafile/test1-01.dbf' ;
set newname for datafile 9 to '/home/oracle/product/oradata/lunar/datafile/system1.dbf' ;
set newname for datafile 10 to '/home/oracle/product/oradata/lunar/datafile/rman01.dbf' ;
release channel c1;
7， 修改pfile文件（这一步只有同机克隆采用，异机恢复不用）
[oracle@gg lunartest]$ cat pfile.lunar.bak
*.aq_tm_processes=0
*.audit_file_dest='/home/oracle/product/admin/lunar/adump'
*.background_dump_dest='/home/oracle/product/admin/lunar/bdump'
*.compatible='10.2.0.1.0'
*.control_files='/home/oracle/product/oradata/lunar/controlfile/o1_mf_3sfb1t6n_.ctl'
*.core_dump_dest='/home/oracle/product/admin/lunar/cdump'
*.db_block_size=8192
*.db_create_file_dest='/home/oracle/product/oradata'
*.db_domain=''
*.db_file_multiblock_read_count=8
*.db_name='lunar'
*.db_recovery_file_dest='/home/oracle/product/flash_recovery_area'
*.db_recovery_file_dest_size=
*.job_queue_processes=0
*.open_cursors=300
*.pga_aggregate_target=
*.processes=150
*.recyclebin='OFF'
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/home/oracle/product/admin/lunar/udump'
db_name = &lunar&
instance_name = lunar
service_names = lunar
8， 重建控制文件
CREATE CONTROLFILE SET DATABASE &lunar& RESETLOGS
ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
'/home/oracle/product/oradata/lunar/datafile/redo01.log'
) SIZE 50M,
'/home/oracle/product/oradata/lunar/datafile/redo02.log'
) SIZE 50M,
'/home/oracle/product/oradata/lunar/datafile/redo03.log'
) SIZE 50M
'/home/oracle/product/oradata/lunar/datafile/system01.dbf',
'/home/oracle/product/oradata/lunar/datafile/undotbs01.dbf',
'/home/oracle/product/oradata/lunar/datafile/sysaux01.dbf',
'/home/oracle/product/oradata/lunar/datafile/users01.dbf',
'/home/oracle/product/oradata/lunar/datafile/example01.dbf',
'/home/oracle/product/oradata/lunar/datafile/inventory01.dbf',
'/home/oracle/product/oradata/lunar/datafile/odi_default.dbf',
'/home/oracle/product/oradata/lunar/datafile/test1-01.dbf',
'/home/oracle/product/oradata/lunar/datafile/system1.dbf',
'/home/oracle/product/oradata/lunar/datafile/rman01.dbf'
CHARACTER SET US7ASCII
9， 应用归档日志
catalog start with ‘/lunartest/’;
10， 打开数据库
11， 添加临时文件
alter tablespace temp add tempfile ‘/home/oracle/product/oradata/lunar/datafile/temp01.dbf’ size 10m autoextend on next 10m maxsize 10g;
OGG的DDL功能真是坑，今天在测试库尝试升级，被OGG的DDL给坑了（以前没摸过这个库，不知道有这个东西……）
以后，做任何大操作以前，一定要仔细检查数据库，是否曾经开启过OGG的DDL功能。
这个功能有很多隐患：
因为OGG的DDL是建立在SYS用户下面的， 与其他普通用户的trigger不同：
1，数据库文件offline后，如果有OGG的DDL曾经被开启，可能因此打不开数据库（先disable ogg ddl才行）
2，升级过程中，如果没有disable ddl trigger，可能出现一些升级后的异常
3，OGG用户删除后，并不能删除OGG的DDL trigger，因为他的属主是SYS，且属于internal trigger，会导致大量SYS用户的对象失效和DDL功能失效。
升级数据库，从11.2.0.1到11.2.0.4，升级过程中，没有报错，但是数据库启动后，报错：
Errors in file /u01/oracle/app/diag/rdbms/gpsdb3/gpsdb3/trace/gpsdb3_ora_19939.trc:
ORA-04045: errors during recompilation/revalidation of SYS.OLAPISTARTUPTRIGGER
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06512: at line 904
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLR
Completed: ALTER DATABASE OPEN
尝试删除OGG用户，报错：
SQL& drop user GGUSR;
drop user GGUSR
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 904
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
检查报错的OLAP过程，为INVALID状态：
SQL& select owner, object_type, status from all_objects where object_name='OLAPIHISTORYRETENTION';
OBJECT_TYPE
------------------------------ ------------------- -------
但是升级后，检查所有数据库组件是VALID状态：
SQL& set pages 9999
SQL& set linesize 1000
SQL& col comp_id for a14
SQL& col comp_name for a36
SQL& col version for a14
SQL& select COMP_ID, COMP_NAME, VERSION, STATUS from dba_
-------------- ------------------------------------ -------------- ----------------------
11.2.0.1.0
Oracle Application Express
3.2.1.00.10
OLAP Catalog
11.2.0.4.0
11.2.0.4.0
Oracle Multimedia
11.2.0.4.0
Oracle XML Database
11.2.0.4.0
Oracle Text
11.2.0.4.0
Oracle Expression Filter
11.2.0.4.0
Oracle Rules Manager
11.2.0.4.0
Oracle Workspace Manager
11.2.0.4.0
Oracle Database Catalog Views
11.2.0.4.0
Oracle Database Packages and Types
11.2.0.4.0
JServer JAVA Virtual Machine
11.2.0.4.0
Oracle XDK
11.2.0.4.0
Oracle Database Java Packages
11.2.0.4.0
OLAP Analytic Workspace
11.2.0.4.0
Oracle OLAP API
11.2.0.4.0
17 rows selected.
理论上，升级后，组件都是正常的，为什么出现这种情况？
SQL& select owner, trigger_name, status from dba_triggers where trigger_name like '%OLAPI%';
TRIGGER_NAME
------------------------------ ------------------------------ --------
OLAPISTARTUPTRIGGER
OLAPISHUTDOWNTRIGGER
尝试disable 这两个trigger，也报错：
SQL& ALTER TRIGGER SYS.OLAPISTARTUPTRIGGER DISABLE;
ALTER TRIGGER SYS.OLAPISTARTUPTRIGGER DISABLE
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06512: at line 904
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called: &GGUSR.DDLREPLICATION&
貌似所有的DDL都失效了：
SQL& create user lunar
create user lunar identified by lunar
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 904
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
再一查SYS的无效对象，800多个：
SQL& select count(*) from dba_objects where status='INVALID';
----------
使用utlrp编译，也报错：
SQL& @?/rdbms/admin/utlrp
COMP_TIMESTAMP UTLRP_BGN
The following PL/SQL block invokes UTL_RECOMP to recompile invalid
objects in the database. Recompilation time is proportional to the
number of invalid objects in the database, so this command may take
a long time to execute on a database with a large number of invalid
Use the following queries to track recompilation progress:
1. Query returning the number of invalid objects remaining. This
number should decrease with time.
SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
2. Query returning the number of objects compiled so far. This number
should increase with time.
SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
This script automatically chooses serial or parallel recompilation
based on the number of CPUs available (parameter cpu_count) multiplied
by the number of threads per CPU (parameter parallel_threads_per_cpu).
On RAC, this number is added across all RAC nodes.
UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
recompilation. Jobs are created without instance affinity so that they
can migrate across RAC nodes. Use the following queries to verify
whether UTL_RECOMP jobs are being created and run correctly:
1. Query showing jobs created by UTL_RECOMP
SELECT job_name FROM dba_scheduler_jobs
WHERE job_name like 'UTL_RECOMP_SLAVE_%';
2. Query showing UTL_RECOMP jobs that are running
SELECT job_name FROM dba_scheduler_running_jobs
WHERE job_name like 'UTL_RECOMP_SLAVE_%';
ERROR at line 1:
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 904
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at &SYS.UTL_RECOMP&, line 865
ORA-06512: at line 4
COMP_TIMESTAMP UTLRP_END
DOC& The following query reports the number of objects that have compiled
DOC& with errors.
DOC& If the number is higher than expected, please examine the error
DOC& messages reported with each object (using SHOW ERRORS) to see if they
DOC& point to system misconfiguration or resource constraints that must be
DOC& fixed before attempting to recompile these objects.
DOC& The following query reports the number of errors caught during
DOC& recompilation. If this number is non-zero, please query the error
DOC& messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC& are due to misconfiguration or resource constraints that must be
DOC& fixed before objects can compile successfully.
CREATE OR REPLACE FUNCTION local_enquote_name (str varchar2)
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 904
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ERROR at line 1:
ORA-00904: &LOCAL_ENQUOTE_NAME&: invalid identifier
ORA-06512: at line 27
DROP function local_enquote_name
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 904
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-04045: errors during recompilation/revalidation of GGUSR.DDLREPLICATION
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06512: at line 1027
ORA-04067: not executed, package body &GGUSR.DDLREPLICATION& does not exist
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
ORA-06508: PL/SQL: could not find program unit being called:
&GGUSR.DDLREPLICATION&
FAILED CHECK FOR INDEXTYPE CONTEXT
Warning: XDB now invalid, could not find xdbconfig
PL/SQL procedure successfully completed.
最后一行提示XDB组件有问题:
SQL& SELECT substrb(Comp_ID,1,10)Comp_ID,
substrb(Status,1,8)Status,
substrb(Version,1,12)Version,
substrb(Comp_Name,1,35)Comp_Name
FROM DBA_Registry
WHERE comp_id = 'XDB';
---------- -------- ------------ -----------------------------------
11.2.0.4.0
Oracle XML Database
diable OGG的trigger，然后删除ogg用户后，再次使用utlrp编译，已经正常了：
SQL& @?/rdbms/admin/utlrp
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN
1 row selected.
The following PL/SQL block invokes UTL_RECOMP to recompile invalid
objects in the database. Recompilation time is proportional to the
number of invalid objects in the database, so this command may take
a long time to execute on a database with a large number of invalid
Use the following queries to track recompilation progress:
1. Query returning the number of invalid objects remaining. This
number should decrease with time.
SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
2. Query returnin
