1
2
3

login deny
telnet deny
ftp deny

2. 执行’inetd -c’命令以便重新初始化inet daemon。
解除用户登录的限制：
1. 在/var/adm/inetd.sec文件中删除或注释掉上面的所加的几行。
2. 执行’inetd -c’

1

CREATE USER monadm IDENTIFIED BY monadm;

赋权：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

GRANT resource,CONNECT,select_catalog_role TO monadm;
GRANT SELECT ON v_$DATABASE TO monadm;
GRANT SELECT ON v_$INSTANCE TO monadm;
GRANT SELECT ON sys.props$ TO monadm;
GRANT SELECT ON v_$sysstat TO monadm;
GRANT SELECT ON v_$parameter TO monadm;
GRANT SELECT ON v_$sga TO monadm;
GRANT SELECT ON v_$rowcache TO monadm;
GRANT SELECT ON v_$librarycache TO monadm;
GRANT SELECT ON dba_data_files TO monadm;
GRANT SELECT ON v_$log TO monadm;
GRANT SELECT ON dba_tablespaces TO monadm;
GRANT SELECT ON dba_free_space TO monadm;
GRANT SELECT ON dba_segments TO monadm;
GRANT SELECT ON v_$resource_limit TO monadm;
GRANT SELECT ON v_$bgprocess TO monadm;
GRANT SELECT ON v_$session TO monadm;
GRANT SELECT ON v_$lock TO monadm;
GRANT SELECT ON v_$sqltext TO monadm;

/usr/local/webserver/nginx/sbin/nginx
/usr/local/webserver/nginx/sbin/nginx: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory

从错误看出是缺少lib文件导致，进一步查看下

[root@vps1 pcre-8.30]# ldd $(which /usr/local/webserver/nginx/sbin/nginx)

linux-vdso.so.1 => (0x00007fff5dd56000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa8c1857000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fa8c161f000)
libpcre.so.1 => not found
libssl.so.6 => /lib64/libssl.so.6 (0x00007fa8c13d3000)
libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00007fa8c1082000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fa8c0e7e000)
libz.so.1 => /lib64/libz.so.1 (0x00007fa8c0c6a000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa8c0912000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa8c1a72000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007fa8c06e4000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007fa8c044f000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fa8c024d000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007fa8c0028000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007fa8bfe20000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fa8bfc1e000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa8bfa09000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fa8bf7f1000)
libsepol.so.1 => /lib64/libsepol.so.1 (0x00007fa8bf5ab000)

可以看出 libpcre.so.1 => not found 并没有找到，进入/lib64目录中手动链接下

[root@vps1 lib64]# ln -s libpcre.so.0.0.1 libpcre.so.1

之后启动正常。

冰层在冬天，一日一日的加厚
那厚度似乎要与春天抗衡
可是，春天毕竟要融化整个冬天的
就这样，在这时，春天早早的要来了

区别：

1. 如果丢失丢失当前控制文件，用冷备份的控制文件恢复的时候。用来告诉oracle，不要以controlfile中的scn作为恢复的终点；
2. 如果丢失current/active redo的时候。手动指定终点。
3. 如果 丢失当前controlfile并且current/active redo都丢失，会先去 自动 应用归档日志,可以实现最大的恢复；
4. 如果 丢失当前controlfile并且current/active redo都丢失，以旧的redo中的scn为恢复终点。因为没有应用归档日志，所有会丢失数据。

要理解recover database using backup controlfile，先理解 recover database，也就是说，不加using backup controlfile的情况。在普通的recover database 或者 recover tablespace, recover datafile时， Oracle会以当前controlfile所纪录的SCN为准，利用archive log和 redo log的redo entry, 把相关的datafile 的 block恢复到“当前controlfile所纪录的SCN”而某些情况下，Oracle需要把数据恢复到比当前controlfile所纪录的SCN还要靠后的位置（比如说，control file是backup controlfile , 或者 controlfile是根据trace create的。）,这时候，就需要用using backup controlfile. 恢复就不会受“当前controlfile所纪录的SCN”的限制。这时候的限制就来自于你的语句(until time , until scn)，或者可用的archive log(until cancel)