虚拟机ORACLE10G Data Guard(DG) Physical Standby Database
今天小测了一下10g的physical DG,参考首选官方文档
dgsource :192.168.1.100
dgtarget:192.168.1.245
提供综合数据库运维服务与优化方案(不限Oracle、MySQL、PG及国产数据库), 微信/Tel:(+86)134-365-60330
数据库oracle
今天小测了一下10g的physical DG,参考首选官方文档
dgsource :192.168.1.100
dgtarget:192.168.1.245
今天测试dg,用sys +tnsnames 中指定别名文件远程服务怎么也连不上,ORA-01031: insufficient privileges
查看oracle10g官方文档没发现这个格式问题(可能是我大意了),orapwd file的格式是有限制的,
1,只读表空间可不可以后来创建表
2,只读表空间里先创建的表能不能删除
3,read only 是不是只禁用dml?
…
ORACLE加WIN计划任务实现ORACLE数据的定时压缩包形式备份。
网络上很多份关于透明网关的资料。但是真正通过实践能够配置成功,目前只发现了这一份。
实践出真知!
今天看oracle11g新特性发现宣称11G,用了新的zlib算法在压缩上改变很多,可以比oracle10g压缩算法快40%,空间减少20%,准不准不先不说,测试看应用有什么变化吧…
oracle 11G 对 现有表增加指定默认值列方式发生了很大变化,无论是存储方式上,还是效率上,下面看一个简单的实验
不知道你有没有遇到过开发的需求导一份生产库的数据到测试库,但库表中有敏感信息如手机、身份证号等等等等,如果你全部把真实的数据给他们是不是太不负责人了(当然很多都这么做了),少导列可能会影响测试准确性,最好是用其它掩码覆盖…
SQL> create table testblob(id int,comm blob);
Table created.
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at “WMSYS.WM_CONCAT_IMPL”, line 30
今天发现用dbms_errlog可以捕获错误日志,很给力,直接看实验
[oracle@orazhang ~]$ sqlplus anbob/anbob
Today I read foreign blog,I think I learned the true knowledge
One of most operations we are performing is “Deleting many rows from oracle big tables” ;
declare
maxrows number default 1000;
row_id_table dbms_sql.Urowid_Table;
currcount_table dbms_sql.number_Table;
cursor cur_t2 is….
If you delete the line “FOR EACH ROW” from the trigger, it becomes a statement trigger which is not subject to this restriction, and the trigger.
By default, RMAN creates all backups as backup sets, on tape or on disk. You can change the default backup type for disk backups to be image copies using the CONFIGURE command. Backups to tape can only be backup sets.
同一实例下,不同用户之间的数据同步导入
1,exp from a user,imp to b user,
2,impdp network_link,不生成dump文件直接导入
…
Extent Header:: spare1: 0 spare2: 0 #extents: 4 #blocks: 32
last map 0x00000000 #maps: 0 offset: 2716
Highwater:: 0x02400391 ext#: 3 blk#: 8 ext size: 8
接上一篇,
如果丢失数据库默认表空间的任一数据文件,数据库会不会shutdown?
Your database is having two control files, three redo log file groups with two members in each group. Failure of which file would cause an instance to shut down
Your database is configured in NOARCHIVELOG mode. All the control files have been lost due to a hard disk failure but the data files are not lost. You have the closed whole database backup available to you…