针对不同版本的数据库需注释相关命令行。

启动数据库脚本：dbstart.cmd

@echo off

REM  ------ Common Commands -------
set ORAHOME="ORACLE_HOME_NAME"
set ORASID="ORACLE_SID"
net start Oracle%ORAHOME%TNSListener
net start OracleService%ORASID%

REM  ------ Commands For Oracle 8.x - 9.2 --------
REM net start Oracle%ORAHOME%HTTPServer
REM net start Oracle%ORAHOME%ClientCache
REM net start Oracle%ORAHOME%Agent
REM net start Oracle%ORAHOME%SNMPPeerEncapsulator
REM net start Oracle%ORAHOME%SNMPPeerMasterAgent
REM net start Oracle%ORAHOME%PagingServer
REM net start OracleMTSRecoverService

REM  ------ Commands For Oracle 10.x --------
REM net start OracleDBConsole%ORASID%
REM net start OracleJobScheduler%ORASID%
REM net start Oracle%ORAHOME%iSQL*Plus

REM  ------ Commands For Oracle 11.x --------
REM net start OracleDBConsole%ORASID%
REM net start OracleJobScheduler%ORASID%

关闭数据库脚本: dbshut.cmd

@echo off

REM  ------ Common Commands -------
set ORAHOME="ORACLE_HOME_NAME"
set ORASID="ORACLE_SID"
net stop Oracle%ORAHOME%TNSListener
net stop OracleService%ORASID%

REM  ------ Commands For Oracle 8.x - 9.2 --------
REM net stop Oracle%ORAHOME%HTTPServer
REM net stop Oracle%ORAHOME%ClientCache
REM net stop Oracle%ORAHOME%Agent
REM net stop Oracle%ORAHOME%SNMPPeerEncapsulator
REM net stop Oracle%ORAHOME%SNMPPeerMasterAgent
REM net stop Oracle%ORAHOME%PagingServer
REM net stop OracleMTSRecoverService

REM  ------ Commands For Oracle 10.x --------
REM net stop OracleDBConsole%ORASID%
REM net stop OracleJobScheduler%ORASID%
REM net stop Oracle%ORAHOME%iSQL*Plus

REM  ------ Commands For Oracle 11.x --------
REM net stop OracleDBConsole%ORASID%
REM net stop OracleJobScheduler%ORASID%

注：

ORACLE_HOME_NAME:

系统注册表HKLM\SOFTWARE\ORACLE\…下ORACLE_HOME_NAME键值。(9i为\HOME0, 10g为\KEY_OraDb10g_home1，11g为\KEY_OraDb11g_home1)

ORALCLE_SID:

为Oracle系统标识符。

WRAP语法

wrap iname=input_file [oname=output_file]

可省略文件扩展名，如以下的命令是等同的:
wrap iname=/mydir/myfile
wrap iname=/mydir/myfile.sql
输出文件默认的扩展名为.plb，当然你也可以指定不同的文件名和扩展名。
wrap iname=/mydir/myfile oname=/yourdir/yourfile.out
wrap主要是混淆PL/SQL语句的主体部分，如下CREATE语句可以被加密:

CREATE [OR REPLACE] FUNCTION function_name
CREATE [OR REPLACE] PROCEDURE procedure_name
CREATE [OR REPLACE] PACKAGE package_name
CREATE [OR REPLACE] PACKAGE BODY package_name
CREATE [OR REPLACE] TYPE type_name AS OBJECT
CREATE [OR REPLACE] TYPE type_name UNDER type_name
CREATE [OR REPLACE] TYPE BODY type_name

CREATE [OR REPLACE] TRIGGER语句不能被加密，但你可调用加密的过程。加密文件中除了语句头部和C风格(/*…*/)注释外，其它所有注释被删除。

输出的文件为文本文件，可以在SQL*Plus执行:

SQL> @myfile.plb;

DBMS_DDL子程序
DMBS_DDL包包含WRAP函数和CREATE_WRAPPED过程。CREATE_WRAPPED过程加密语句并创建PL/SQL单元。如下为使用DBMS_DDL.CREATE_WRAPPED加密包的例子:

DECLARE
  package_text VARCHAR2(32767); — text for creating package spec & body 
  FUNCTION generate_spec (pkgname VARCHAR2) RETURN VARCHAR2 AS
  BEGIN
    RETURN ‘CREATE PACKAGE ‘ || pkgname || ‘ AS
      PROCEDURE raise_salary (emp_id NUMBER, amount NUMBER);
      PROCEDURE fire_employee (emp_id NUMBER);
      END ‘ || pkgname || ‘;’;
  END generate_spec;

  FUNCTION generate_body (pkgname VARCHAR2) RETURN VARCHAR2 AS
  BEGIN
    RETURN ‘CREATE PACKAGE BODY ‘ || pkgname || ‘ AS
      PROCEDURE raise_salary (emp_id NUMBER, amount NUMBER) IS
      BEGIN
        UPDATE employees
          SET salary = salary + amount WHERE employee_id = emp_id;
      END raise_salary;
      PROCEDURE fire_employee (emp_id NUMBER) IS
      BEGIN
        DELETE FROM employees WHERE employee_id = emp_id;
      END fire_employee;
    END ‘ || pkgname || ‘;’;
  END generate_body;

BEGIN
  — Generate package spec
  package_text := generate_spec(‘emp_actions’)

  — Create wrapped package spec
  DBMS_DDL.CREATE_WRAPPED(package_text);

  — Generate package body
  package_text := generate_body(‘emp_actions’);

  — Create wrapped package body
  DBMS_DDL.CREATE_WRAPPED(package_text);
END;

Cause: The table or view entered does not exist, a synonym that is not allowed here was used, or a view was referenced where a table is required. Existing user tables and views can be listed by querying the data dictionary. Certain privileges may be required to access the table. If an application returned this message, the table the application tried to access does not exist in the database, or the application does not have access to it.

Action: Check each of the following:

the spelling of the table or view name.

that a view is not specified where a table is required.

that an existing table or view name exists.

Contact the database administrator if the table needs to be created or if user or application privileges are required to access the table.

Also, if attempting to access a table or view in another schema, make certain the correct schema is referenced and that access to the object is granted.

但在SQL/PLUS中可以直接查询，并且正常返回结果。初步判断当前用户还是没有足够权限，于是进行明确的授权:

SQL> grant select on employee to wind;
Grant succeeded.

再次编译问题解决。

语法：
row_number() over(query_partition_clause order_by_clause)

SQL> delete from temp003

  2  where rowid in (

  3  select rid from

  4  (select rowid rid,row_number() over(partition by empno,deptno order by empno,deptno) rn

  5  from temp003)

  6  where rn>1)

  7  /

75 rows deleted

SQL> 

2.SQL语句

SQL> delete from temp003 a

  2  where rowid>(select min(rowid)

  3  from temp003 b

  4  where a.empno=b.empno

  5  and a.deptno=b.deptno)

  6  /

75 rows deleted

SQL> rollback;

Rollback complete

SQL> 

SQL> delete from temp003 a

  2  where rowid>any (select rowid

  3  from temp003 b

  4  where a.empno=b.empno

  5  and a.deptno=b.deptno)

  6  /

75 rows deleted

SQL> 

ORA-16038: log 1 sequence# 44 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: ‘/u01/app/oracle/oradata/test/redo01.log’

检查v$flash_recovery_area_usage和v$recovery_file_dest发现archivelog占了大部分空间. 利用RMAN的DELETE命令删除归档备份修复此错误.

RMAN> delete archivelog until sequence=41;

打开数据库, 查询如下语句会发现该故障的解决方法 :)

SQL> select reason,object_type,suggested_action from dba_outstanding_alerts;

REASON
——————————————————————————–
OBJECT_TYPE
—————————————————————-
SUGGESTED_ACTION
——————————————————————————–
db_recovery_file_dest_size of 2147483648 bytes is 98.46% used and has 33048064 remaining bytes available.
RECOVERY AREA
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN 
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.

官方解决方案:

1) Take frequent backup of recovery area using RMAN.
2) Consider changing RMAN retention policy.
3) Consider changing RMAN archivelog deletion policy.
4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
5) Delete files from recovery area using RMAN.

数据泵做为服务进程运行, 极大提高了性能(同原导入导出工具比较)因为数据不再由客户端程序处理, 数据泵还可并行运行, 更进一步增强了性能.

创建目录

数据泵要求为将创建和读取的数据文件和日志文件创建目录. 外部目录必须存在.

SQL> create directory DPXFER as ‘/Temp/DataPumpXfer’;
Directory created.
SQL> grant read, write on directory DPXFER to rjb;
Grant succeeded.

启动任务

可通过PARFILE参数在expdp中使用参数文件(参数说明通过expdp help=y查看).
如创建一个名为dp_exp.par的文件:
directory=dpxfer
dumpfile=metadata_only.dmp
content=metadata_only

$ expdp ljf/ljf parfile=dp_exp.par

注: 相同目录中已存在的DUMP文件不会被覆盖, 除非使用REUSE_DUMPFILES参数.

停止和重启动任务

通过在导出过程中按CTRL-C进入expdb提示符:
Export>

退出
Export> exit_client

重启动并连接正在运行的任务
expdp ljf/ljf attach=SYS_EXPORT_SCHEMA_01

显示正运行任务的状态
Export> continue_client

挂起任务
Export> stop_job

重运行任务
Export> start_job

备份策略应包含物理和逻辑备份, 生产库以物理备份为主, 逻辑备份为辅.

Logical Backups

Data Pump Export 与Data Pump Import , 使用XML文件.

注: Oracle Import和Export工具在11g中仍可以安装, 但鼓励使用Data Pump Export与Data Pump Import代替.

全库导出将导出数据库的所有对象, 包含表空间, 数据文件和用户, 可从导出数据中导入部分或者全部数据, 在做全库导入时这些对象都将被创建, 利用表空间和用户的重建有利于重新指定数据库对象的物理分布. 如果从导出文件中导入部分数据, 需要在导入前设置好表空间, 数据文件和数据的所有者.

Physical Backups

Offline Backups

在数据库正常关闭情况下, 即shutdown命令使用normal, immediate或transactional选项.当数据库脱机时, 备份下面文件:

所有的数据文件
所有的控制文件
所有归档重做日志文件
init.ora文件或SPFILE

Online Backups

数据库必须为ARCHIVELOG模式. 提供完整的时间点恢复以及在文件系统备份期间保持数据库打开状态.

将每个表空间设为备份状态, 备份数据文件, 恢复表空间为正常状态.
注: 如果使用RMAN工具, 则不需要手动设置表空间为备份状态. RMAN读取数据块方式类似于ORACLE的查询.
备份如下文件:
所有数据文件
所有归档重做日志
控制文件, 使用alter database backup controlfile
SPFILE

RMAN在备份整个数据库或者SYSTEM表空间时自动备份控制文件与SPFILE.

[Rac10g01][/home/oracle]$ srvctl start asm -n rac10g01
PRKS-1009 : 无法启动节点 "rac10g01", [PRKS-1009 : 无法启动节点 "rac10g01", [CRS-1028: Dependency analysis failed because of:
CRS-0223: Resource 'ora.rac10g01.ASM1.asm' has placement error.] 上的 ASM 实例 "+ASM1"] 上的 ASM 实例 "+ASM1"
  [PRKS-1009 : 无法启动节点 "rac10g01", [CRS-1028: Dependency analysis failed because of:
CRS-0223: Resource 'ora.rac10g01.ASM1.asm' has placement error.] 上的 ASM 实例 "+ASM1"]

试着采用如下方法解决:
[Rac10g01][/home/oracle]$ export ORACLE_SID=+ASM1
[Rac10g01][/home/oracle]$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.1.0 – Production on Tue Sep 9 02:27:08 2008

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup
ASM instance started

Total System Global Area   92274688 bytes
Fixed Size                  1217884 bytes
Variable Size              65890980 bytes
ASM Cache                  25165824 bytes
ASM diskgroups mounted
SQL> exit 
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – Production
With the Partitioning, Real Application Clusters, Oracle Label Security, OLAP
and Data Mining Scoring Engine options
[Rac10g01][/home/oracle]$ srvctl status asm -n rac10g01
ASM 实例 +ASM1 正在节点 rac10g01 上运行。

启动数据库成功.

还可以采用crs相关命令解决:

1. ./crs_stat -t
ora….SM1.asm application ONLINE UNKNOWN
状态为UNKNOWN

./crsctl check crs
CSS appears healthy
CRS appears healthy
EVM appears healthy
正常

2. 执行:
./crs_stop -all
./crs_start -all
./crs_stat -t
ora….SM1.asm application ONLINE OFFLINE

3. 启动ASM
srvctl start asm -n rac10g01 -i +ASM1