oracle transparent geteways,文档中心-CSDN博客

javascript parseInt is broken

I was debugging some strange errors in a date conversion function I was writing, and I stumbled upon something that amazed me... a strange bug in parseInt

>>>parseInt('06')

>>>parseInt('07')

>>>parseInt('08')

>>>parseInt('09')

>>>parseFloat('08')

>>>parseFloat('09')

Clearly for the strings '08' and '09' parseInt fails to return the right value. One workaround is easy, use parseFloat.

Why does this happen and where should I report this? I find it extremely odd that it happens in both Firefox and Internet Explorer 6 & 7; there must be some explanation right?

You can test it out for yourself using the FireBug javascript console), or by using one of these two links

alert(parseInt('07')+' == 7 ?')

alert(parseInt('08')+' == 8 ?')

Ok, Ok, so now that I explained how you would expect it to work (and clearly how I expected it to work) I'm going to answer my own question ......

--删除空的表空间，但是不包含物理文件

drop tablespace tablespace_name;

--删除非空表空间，但是不包含物理文件

drop tablespace tablespace_name including contents;

--删除空表空间，包含物理文件

drop tablespace tablespace_name including datafiles;

--删除非空表空间，包含物理文件

drop tablespace tablespace_name including contents and datafiles;

--如果其他表空间中的表有外键等约束关联到了本表空间中的表的字段，就要加上CASCADE CONSTRAINTS

drop tablespace tablespace_name including contents and datafiles CASCADE CONSTRAINTS;

......

我们知道,在Oracle数据库中,可以通过kill session的方式来终止一个进程,其基本语法结构为:

alter system kill session 'sid,serial#' ;

被kill掉的session,状态会被标记为killed,Oracle会在该用户下一次touch时清除该进程.

我们发现当一个session被kill掉以后，该session的paddr被修改，如果有多个session被kill，那么多个session

的paddr都被更改为相同的进程地址:

SQL> select saddr,sid,serial#,paddr,username,status from v$session where username is not null;

SADDR SID SERIAL# PADDR USERNAME STATUS

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

542E0E6C 11 314 542B70E8 EYGLE INACTIVE

542E5044 18 662 542B6D38 SYS ACTIVE

SQL> alter system kill session '11,314';

System altered.

SQL> select saddr,sid,serial#,paddr,username,status from v$session where username is not null;

SADDR SID SERIAL# PADDR USERNAME ......

--名词说明：源——被同步的数据库

-- 目的——要同步到的数据库

/*一、创建dblink：*/

--1、在目的数据库上，创建dblin

drop database link dblink_anson;

Create public

database link dblink_anson

Connect to lg identified by lg using 'SDLGDB';

--源数据库的用户名、密码、服务器名k

/*二、创建快照：*/

--1、在源和目的数据库上同时执行一下语句，创建要被同步的表

drop table tb_anson;

create table tb_anson(c1 varchar2(12));

alter table tb_anson add constraint pk_anson primary key (C1);

--2、在目的数据库上，测试dblink

select * from tb_anson@dblink_anson;

select * from tb_anson;

--3、在目的数据库上，创建要同步表的快照日志

Create snapshot log on tb_anson;

--4、创建快照，快照(被同步(源)数据库服务必须启动)

Create snapshot sn_anson as select *&nbsp ......

oracle通过透明网关(Oracle Transparent Geteways)，访问ms sql server和其他数据库

环境：

1、在安装有oracle服务器端，ms sql server的客户端，通过oracle的透明网关访问ms sql server数据库

2、在ms sql server服务器上创建用户conn_ora,并且要能访问ms sql server数据库msdb

安装Oracle Transparent Geteways：

1、'开始'菜单的'Oracle Installation Products'下的'Universal Installer'

\\127.0.0.1\e$\oracle9.2\ORANT920\ORA92_1\NT\I386\stage\products.jar

下一步－

2、选择安装类型：

自定义，下一步

3、选择可用产品组件：

将 'Oracle Transparent Geteways 9.2.0.1.0'下的'Oracle Transparent Geteways for&n ......

Oracle Flashback Technology

Oracle Flashback Technology reduces recovery time from hours to minutes.

from: http://www.oracle.com/technology/deploy/availability/htdocs/Flashback_Overview.htm

According to many studies, 40% of application outages are caused by operator or user errors. Part of being human is making mistakes. But these errors are extremely difficult to avoid and can be particularly difficult to recover from without advance planning and the right technology. Such errors can result in "logical" data corruption, or cause downtime of one or more components of the IT infrastructure. While it is relatively simple to rectify the failure of an individual component, detection and repair of logical data corruption, such as accidental deletion of valuable data, is a time consuming operation that causes enormous loss of business productivity. Typical user-errors may include accidental deletion of valuable data, deleting the wrong data, and dropping the wrong table.

Guarding Aga ......