DBAORACLE

博客导航

博客日历

«	七月 2009					»
一	二	三	四	五	六	日
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31

今天收到Oracle寄来的OCP证书

发表人:dbaoracle | 发表时间: 2009年二月20日, 16:27

搞了7年的Oracle，到现在算是正式被Oracle认可了，收到了盼望已久的OCP证书。

去年11月份参加完OCP考试，在Oracle网站提交hands on后第9天收到Oracle的确认信，然后就是等待寄送证书了，可一直等了两个月还是没有消息。无奈之下向Oracle发了封邮件要求重寄，这次倒挺快，2月4日发的邮件，今天就收到了证书，DHL送过来的，为啥第一次就没送到呢？

Ten Principles of Economics__How The Economy as a Whole Works

发表人:dbaoracle | 发表时间: 2009年二月20日, 16:06

Principle#8: A Country's Standard of Living Depends on its Ability to Produce Goods and Services;

Principle#9: Prices Rise When the Government Prints Too Much Money;

Principle#10: Society Faces a Short-Run Tradeoff between Inflation and Unemployment.

Ten Principles of Economics__How People Interact

发表人:dbaoracle | 发表时间: 2009年二月20日, 16:01

Principle#5: Trade Can Make Everyone Better Off;

Principle#6: Markets Are Usually a Good Way to Organize Economic Activity;

Principle#7: Governments Can Sometimes Improve Market Outcomes;

Ten Principles of Economics__How People Make Decisions

发表人:dbaoracle | 发表时间: 2009年二月20日, 10:19

Principle#1: People Face Tradeoffs;

Principle#2: The Cost of Someting Is What You Give Up to Get It;

Principle#3: Rational People Think at the Margin;

Principle#4: People Respond to Incentives;

Using Flashback Drop and Managing the Recycle Bin

发表人:dbaoracle | 发表时间: 2007年三月13日, 11:39

这两天用到了10G的新特性flashback drop，特将Oracle文档中讲述关于如何管理和使用该特性的部分摘录如下，以备查考。

查看全文

多表插入中涉及sequence列的问题

发表人:dbaoracle | 发表时间: 2006年八月07日, 17:34

按照Oracle文档中的说法，当使用多表插入（Multi-table-insert）语句时子查询中不能使用sequence：
SQL> create sequence seq ;

序列已创建。

SQL> insert all
2 INTO T1
3 (C1)
4 VALUES
5 (C1)
6 INTO T2
7 (C1)
8 VALUES
9 (C1)
10 select seq.nextval AS C1 from EMP;
select seq.nextval AS C1 from EMP
*
ERROR 位于第 10 行:
ORA-02287: 此处不允许序号

我们可以通过使用一个函数来绕过该限制。

查看全文

SOX requirements for Database Change Management

发表人:dbaoracle | 发表时间: 2006年八月06日, 12:57

Changes to the database are widely communicated, and their impacts are known beforehand.
Installation and maintenance procedure documentation for the DBMS is current.
Data structures are defined and built as the designer intended them to be.
Data structure changes are thoroughly tested.
Users are apprised, and trained if necessary, when database changes imply a change in application behavior.
The table and column business definitions are current and widely known.
The right people are involved throughout the application development and operational cycles.
Any in-house tools are maintained and configured in a disciplined way.
Application impacts are known prior to the migration of database changes to production.
Performance is maintained at predefined and acceptable levels.
The database change request and evaluation system is rational.
Turn-around time on database changes is predictable.
Any change to the database can be reversed.
Database structure documentation is maintained.
Database system software documentation is maintained.
Migration through development, test, and especially, production environments is rational.
Security controls for data access is appropriate and maintained.
Database reorganizations are planned to minimize business disruption.