Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1]
Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1][@more@]
Step By Step Guide On Creating Physical Standby Using RMAN Duplicate In ASM Filesystem For ASM Prima
Step By Step Guide On Creating Physical Standby Using RMAN Duplicate In ASM Filesystem For ASM Primary [ID 837102.1][@more@]
【转】dd 和unix 管道完成复制
有时候前后划分的lv方式不同,比如第一批划分的预留了4k给操作系统,而第二批划分的时候没有预留。这样,如果直接使用dd复制第一批的lv到第二批,则lv由于文件头有os的信息无法被oracle识别出来,所以需要在复制的时候把这部分预留块忽略掉。然后,一般预留块大小都比较小,大部分都是4k,而如果使用4k作为dd的blocksize明显效率会比较慢。下面是利用管道的方式,input时使用4k的bs并忽略第一个4k,而output使用256k的bs:dd bs=4k skip=1 if=/dev/rtest1vg_lv001|dd of=/dev/rtest2vg_lv001 bs=256k经测试显示明显要比直接使用4k作为bs来
How to Move Tablespaces Across Platforms Using Transportable Tablespaces With RMAN [ID 371556.1]
How to Move Tablespaces Across Platforms Using Transportable Tablespaces With RMAN [ID 371556.1][@more@]
10g : Transportable Tablespaces Across Different Platforms [ID 243304.1]
10g : Transportable Tablespaces Across Different Platforms [ID 243304.1][@more@]
How to determine if a tablespace can be transported [ID 1071511.6]
For users wanting to determine if a tablespace can be transported.RELATED DOCUMENTSNote:76670.1 ALERT Transportable Tablespaces can corrupt target databaseNote:77523.1 Lists some known restrictions to transporting a tablespaceNote:132545.1 Transported Tablespace with UNUSED Columns Leads to Unreadableor wrong dataTo check whether a tablespace can be transported and whether a tablespaceis self contained, run: dbms_tts.transport_set_checkThe dbms_tts package is owned by sys, so to execute as anoth
dataguard的备端 dba_temp_files中无记录
dataguard的备端 dba_temp_files中无记录[@more@]
dbua 9208升级到10.2.0.5失败--升级猛如虎。
Error appears on upgrade of database : 9.2.0.8 -> 10.2.0.5 ,在dbua的运行过程中报错: ORA-00600: internal error code, arguments: [kqludp2], [0x7000000C5F874D0], [0],之后,dbua断开。之后,用9208的oracle_home起库,alert日志直接报:ORA-00704: bootstrap process failureORA-00604: error occurred at recursive SQL level 1ORA-01406: fetched column value was truncatedError 704 happened during db open, shutting down databaseUSER: terminating instance due to error 704Instance terminated by USER, pid = 20
修改db2的归档路径
db2 update db cfg for sdwst using logarchmeth1 disk:/db2data/db2log[@more@]
Supported OGG Monitor versions prior to 11.1.1.1.1 [ID 1361236.1]
GoalThe Monitor Admin Guide and Release notes state that Monitor can only be used with Oracle GoldenGate release 11.1.1.1.1 and later.But we see that OGG v11.1.1.1.0 has the required agent and seem to work with Monitor. Is this supported?SolutionThe OGG Monitor agent was provided with OGG v11.1.1.1.0. But the agent was found to have issues so only OGG v11.1.1.1.1 and later are currently supported with Monitor.[@more@]
OGG Director status reporting [ID 1345697.1]
Applies to: Management Pack for Oracle GoldenGate - Version: 2.0.0.0 and later [Release: 2.0 and later ]Information in this document applies to any platform.GoalHow do we enable reporting for GoldenGate Director, so that the reports can be published to the teams?SolutionOGG Director has no functionality to generate reports. Director does keep the current status of each monitored OGG process in the repository. You can query the Director repository to get the current status of processes monitor
在RHEL5.5x64上安装Oracle10gR2的简单步骤
Requirements For Installing Oracle10gR2 On RHEL 5/OEL 5 (x86_64) [ID 421308.1]1. Hardware Requirementsi) Physical Memory # grep MemTotal /proc/meminfoii) Swap Space # grep SwapTotal /proc/meminfo2. Kernel Requirements # uname -r The system must be running the following kernel version (or a later version) 2.6.18-8 SELinux disable 3. Installing required packages rpm -qa | grep binutils-2.17.50.0.6-2 (x86_64)rpm -qa | grep compat-db-4.2.52-5.1 (x86_64)rpm -qa | grep compat-libstdc++-296-2.96-138
linux下查询asm磁盘和linux的分区的对应关系
[root@leitest ~]# oracleasm querydisk DATADisk "DATA" is a valid ASM disk[root@leitest ~]# oracleasm querydisk /dev/sdb1Device "/dev/sdb1" is marked an ASM disk with the label "DATA"[root@leitest ~]# oracleasm querydisk -d dataDisk "DATA" is a valid ASM disk on device /dev/sdb1[8,17][root@leitest ~]# oracleasm querydisk /dev/sdc1Device "/dev/sdc1" is not marked as an ASM disk[@more@]
Oracle NUMA Usage Recommendation [ID 759565.1]
Applies to: Oracle Server - Standard Edition - Version: 10.2.0.1 to 11.1.0.7 - Release: 10.2 to 11.1Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.7 [Release: 10.2 to 11.1]Information in this document applies to any platform. Oracle Database Description Oracle NUMA (Non Uniform Memory Architecture) support can be used with large SMP multiprocessor environments with NUMA hardware. When enabled Oracle NUMA support facilitates efficient use of underlying NUMA har
How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows [ID 403522.1]
How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows [ID 403522.1][@more@]
win下oracle9201当前日志组损坏的修复过程
在pfile里添加_allow_resetlogs_corruption=true_corrupted_rollback_segments='_SYSSMU1$','_SYSSMU2$','_SYSSMU3$','_SYSSMU4$','_SYSSMU5$','_SYSSMU6$','_SYSSMU7$','_SYSSMU8$','_SYSSMU9$','_SYSSMU10$'加第一个隐含参数,报错Errors in file d:oracleadminoracleudumporacle_ora_820.trc:ORA-00600: 内部错误代码,参数: [2662], [0], [24912535], [0], [24917934], [8388617], [], []之后,在mount状态下,SQL> alter session set events '10015 trace name ADJUST_SCN level 1';会话已更改。之后,open库时,报:Errors in fi
【原创】sqlserver2005 数据库表损坏处理一例:
sqlserver2005 数据库表损坏处理一例:sqlserver2005中有个cwbase1数据库,此库中有lc0019999.xsfp表,select * from lc0019999.xsfp时,一开始还能查询出点记录,后来直接就报824错误,看到824错误,就知道是表有损坏了。处理步骤:1.DBCC CHECKTABLE ( 'lc00X9999.xsfp ',REPAIR_REBUILD) 反馈如下:lc0019999.XSFP的 DBCC 结果。消息 8928,级别 16,状态 1,第 1 行对象 ID 1414296098,索引 ID 1,分区 ID 374162285789184,分配单元 ID 92687309078528 (类型为 In-row data): 无法处理页 (1:20184)。有关详细信息,请参阅其他
hpux下主机资源监控的工具glance
hpux下主机资源监控的工具glance[@more@]
aix/linux下监控主机资源(cpu 内存等)使用的工具nmon
http://www.ibm.com/developerworks/cn/aix/library/analyze_aix/http://www.ibm.com/developerworks/wikis/display/WikiPtype/nmonhttp://www.alidba.net/index.php/archives/227http://hi.baidu.com/qiaobincs/blog/item/00b8dac3c93ced59b319a8ce.html[@more@]
startup upgrade 时报错ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1]
原因是 把老oracle_home下的spfile.ora文件以root用户上传到新oracle_home下的dbs目录了,这样权限就不对了。ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [27091], [], [], [], [], [], [] ORA-27091: unable to queue I/O ORA-27072: File I/O error [@more@]