机器处理ORA01031差错差错
机器 用户 比拟 称号 岗位 同事 状况 类型 时间 数据
Chu∴Li∴ORA01031Cha∴Cuo--快过年了 同事都闪了 呵呵 我还正在据守岗位 --有时间就做做训练--用同事机器 c:gt。show user USER 为"SCOTT" c:gt。create table te !describe varchar2)。 表已创立 1.c:gt。insert into te select object_id!object_name!test from user_objects。 --最好用sys_objects 行数比拟多 c:gt。desc user_segments。 称号 能否为空 类型 ----------------------------------------- -------- ----------------------- SEGMENT_NAME VARCHAR2 PARTITION_NAME VARCHAR2 SEGMENT_TYPE VARCHAR2 TABLESPACE_NAME VARCHAR2 BYTES NUMBER BLOCKS NUMBER EXTENTS NUMBER INITIAL_EXTENT NUMBER NEXT_EXTENT NUMBER MIN_EXTENTS NUMBER MAX_EXTENTS NUMBER PCT_INCREASE NUMBER FREELISTS NUMBER FREELIST_GROUPS NUMBER BUFFER_POOL VARCHAR2 2.c:gt。select from user_segments where segment_name like TE。 SEGMENT_NAME -------------------------------------------------- ------------------------- PARTITION_NAME SEGMENT_TYPE TABLESPACE_NAME ------------------------------ ------------------ ------------------------- BYTES BLOCKS EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS ---------- ---------- ---------- -------------- ----------- ----------- MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUPS BUFFER_ ----------- ------------ ---------- --------------- ------- TE TABLE USERS 65536 16 1 65536 1 2147483645 1 1 DEFAULT --能够我们的数据会不壹样 --重复施行 1. 用2.检查变化 --大约拔出了约600多万行数据时 机器挂了 shutdown 也不好用了 只好重启机器了 --发动后 出现以下状况 SQLgt。 conn sys/sys as sysdba ERROR: ORA-01031: insufficient privileges 检查 &oracle_homeNETWORKADMINsqlnet& SQLNET.AUTHENTICATION_SERVICES= --os认证 --baidu壹下 connect / as sysdba is current syntax which replaces the older connect internal syntax! and has exactly the same function. This syntax is used to connect to the Oracle database with very powerful privileges. In particular! it allows the user to stop and start the database. When it is used! Oracle does not check the password held for the user in the databases data-dictionary but instead checks that the current operating system userid is defined in the ORA_DBA group or the "dba" group . If the user is in this group! then he is allowed to connect. If he isnt in this group! he will get a ORA-01031: insufficient privileges error message! or an Enter password prompt. The reason the data dictionary password is not used is that Oracle needs some mechanism of checking that the user is sufficiently authorised to start the database which works even when the database is down. Being a member of this group is sufficient proof that you are authorised to stop and start the database! since only the system administrator can add users to this group. The connect / as sysdba technique can therefore be used as a method of logging in as SYS or SYSTEM when youve forgotten both their passwords: Use connect / as sysdba to connect as SYS! ! then change the SYS and SYSTEM passwords. --本来远程登录的用户没有正在dba用户组中 手动加上就好--快过年了 同事都闪了呵呵我还正在据守岗位 --有时间就做做训练--用同事机器 c:gt。show user USER 为"SCOT
非凡教程网 http://www.ffjc.info
Chu∴Li∴ORA01031Cha∴Cuo--快过年了 同事都闪了 呵呵 我还正在据守岗位 --有时间就做做训练--用同事机器 c:gt。show user USER 为"SCOTT" c:gt。create table te !describe varchar2)。 表已创立 1.c:gt。insert into te select object_id!object_name!test from user_objects。 --最好用sys_objects 行数比拟多 c:gt。desc user_segments。 称号 能否为空 类型 ----------------------------------------- -------- ----------------------- SEGMENT_NAME VARCHAR2 PARTITION_NAME VARCHAR2 SEGMENT_TYPE VARCHAR2 TABLESPACE_NAME VARCHAR2 BYTES NUMBER BLOCKS NUMBER EXTENTS NUMBER INITIAL_EXTENT NUMBER NEXT_EXTENT NUMBER MIN_EXTENTS NUMBER MAX_EXTENTS NUMBER PCT_INCREASE NUMBER FREELISTS NUMBER FREELIST_GROUPS NUMBER BUFFER_POOL VARCHAR2 2.c:gt。select from user_segments where segment_name like TE。 SEGMENT_NAME -------------------------------------------------- ------------------------- PARTITION_NAME SEGMENT_TYPE TABLESPACE_NAME ------------------------------ ------------------ ------------------------- BYTES BLOCKS EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS ---------- ---------- ---------- -------------- ----------- ----------- MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUPS BUFFER_ ----------- ------------ ---------- --------------- ------- TE TABLE USERS 65536 16 1 65536 1 2147483645 1 1 DEFAULT --能够我们的数据会不壹样 --重复施行 1. 用2.检查变化 --大约拔出了约600多万行数据时 机器挂了 shutdown 也不好用了 只好重启机器了 --发动后 出现以下状况 SQLgt。 conn sys/sys as sysdba ERROR: ORA-01031: insufficient privileges 检查 &oracle_homeNETWORKADMINsqlnet& SQLNET.AUTHENTICATION_SERVICES= --os认证 --baidu壹下 connect / as sysdba is current syntax which replaces the older connect internal syntax! and has exactly the same function. This syntax is used to connect to the Oracle database with very powerful privileges. In particular! it allows the user to stop and start the database. When it is used! Oracle does not check the password held for the user in the databases data-dictionary but instead checks that the current operating system userid is defined in the ORA_DBA group or the "dba" group . If the user is in this group! then he is allowed to connect. If he isnt in this group! he will get a ORA-01031: insufficient privileges error message! or an Enter password prompt. The reason the data dictionary password is not used is that Oracle needs some mechanism of checking that the user is sufficiently authorised to start the database which works even when the database is down. Being a member of this group is sufficient proof that you are authorised to stop and start the database! since only the system administrator can add users to this group. The connect / as sysdba technique can therefore be used as a method of logging in as SYS or SYSTEM when youve forgotten both their passwords: Use connect / as sysdba to connect as SYS! ! then change the SYS and SYSTEM passwords. --本来远程登录的用户没有正在dba用户组中 手动加上就好--快过年了 同事都闪了呵呵我还正在据守岗位 --有时间就做做训练--用同事机器 c:gt。show user USER 为"SCOT
非凡教程网 http://www.ffjc.info
攻击者如何躲藏和伪装Ap
文件系统Linux之in