purgerecyclebin之后dba_segments仍然有BIN$段
现象: purge recyclebin之后dba_segments仍然有BIN$段。 如下,执行了purge recyclebin之后: SQL select segment_name,SEGMENT_TYPE from dba_segments where tablespace_name like 'USERS' and owner='ZHOU186' 2 ; SEGMENT_NAME SEGMENT_TYPE -----------
现象:purge recyclebin之后dba_segments仍然有BIN$段。
如下,执行了purge recyclebin之后:
SQL> select segment_name,SEGMENT_TYPE from dba_segments where tablespace_name like 'USERS' and owner='ZHOU186'
2 ;
SEGMENT_NAME SEGMENT_TYPE
--------------------------------------------------------------------------------- ------------------
BIN$xd87Y+adofPgQAB/AQB9yA==$0 TABLE
BIN$xd87Y+acofPgQAB/AQB9yA==$0 TABLE
ZHOU_WORK_UNITE_??? TABLE
ZHOU_WORK_UNITE_??? TABLE
ZHOU_WORK_UNITE_?? TABLE
BIN$0QhC65ubuMzgQAB/AQBaBg==$0 TABLE
ZHOU_WORK_UNITE_??? TABLE
ZHOU_WORK_UNITE_??? TABLE
BIN$wJ9k2G65qpDgQAB/AQAj+g==$0 TABLE
ZHOU_WORK_UNITE_??? TABLE
BIN$0QhC65uauMzgQAB/AQBaBg==$0 TABLE
ZHOU_WORK_UNITE_??? TABLE
BIN$0QhC65uduMzgQAB/AQBaBg==$0 TABLE
BIN$0QhC65ucuMzgQAB/AQBaBg==$0 TABLE
SQL> desc ZHOU186."BIN$xd87Y+adofPgQAB/AQB9yA==$0";
Name Null? Type
----------------------------------------------------------------------------------------------------------------- -------- ----------------------------------------------------------------------------
BEGIN_DATE VARCHAR2(10)
BEGIN_TIME VARCHAR2(10)
END_DATE VARCHAR2(10)
END_TIME VARCHAR2(10)
POSITION1 VARCHAR2(30)
PRG_NUM VARCHAR2(30)
WORK_TIME FLOAT(126)
FIRST_CHECK NUMBER(38)
PERSON_NUMBER VARCHAR2(20)
JOB_BIN VARCHAR2(20)
JOB_BINNUMBER NUMBER(38)
分析:
客户的操作步骤大致是:
[oracle@MESZHOUDB ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Thu May 16 09:55:40 2013
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
SQL> alter session set current_schema=ZHOU186;
Session altered.
SQL> purge recyclebin;
Recyclebin purged.
SQL>
SQL>
SQL> select segment_name from dba_segments where tablespace_name like 'USERS' and owner='ZHOU186'
2 ;
SEGMENT_NAME
--------------------------------------------------------------------------------
BIN$xd87Y+adofPgQAB/AQB9yA==$0
BIN$xd87Y+acofPgQAB/AQB9yA==$0
ZHOU_WORK_UNITE_???
ZHOU_WORK_UNITE_???
ZHOU_WORK_UNITE_??
BIN$0QhC65ubuMzgQAB/AQBaBg==$0
ZHOU_WORK_UNITE_???
ZHOU_WORK_UNITE_???
BIN$wJ9k2G65qpDgQAB/AQAj+g==$0
ZHOU_WORK_UNITE_???
BIN$0QhC65uauMzgQAB/AQBaBg==$0
SEGMENT_NAME
--------------------------------------------------------------------------------
ZHOU_WORK_UNITE_???
BIN$0QhC65uduMzgQAB/AQBaBg==$0
BIN$0QhC65ucuMzgQAB/AQBaBg==$0
BIN$0QhC65ueuMzgQAB/AQBaBg==$0
ZHOU_WORK_UNITE_???
BIN$w2uuBw1tJa/gQAB/AQB7Eg==$0
BIN$w2uuBw1sJa/gQAB/AQB7Eg==$0
BIN$w2uuBw1uJa/gQAB/AQB7Eg==$0
BIN$w2uuBw1vJa/gQAB/AQB7Eg==$0
Oracle文档的说明:
The CURRENT_SCHEMA parameter changes the current schema of the session to the specified schema. Subsequent unqualified references to schema objects during the session will resolve to objects in the specified schema.
This setting offers a convenient way to perform operations on objects in a schema other than that of the current user without having to qualify the objects with the schema name. This setting changes the current schema, but it does not change the session user or the current user, nor does it give the session user any additional system or object privileges for the session.
For example:
The table "T1" is owned by user "TEST" and user "SCOTT" doesn't have a table named "T1":
SQL>CONNECT TEST/TEST
SQL>GRANT SELECT ON T1 TO SCOTT;
SQL>CONNECT scott/tiger
SQL>SELECT * FROM SCOTT.T1; SQL>ALTER SESSION SET CURRENT_SCHEMA = test;
SQL>SELECT * FROM T1;
After the session set CURRENT_SCHEMA = test, the only change is that the user "SCOTT" can access the table "TEST.T1" without specifying the table prefix.
The current user is still "TEST", This time when you perform a "purge recyclebin", it just purges the recyclebin in user "TEST", not "SCOTT".
For more details, please refer to:
Oracle? Database SQL Reference
10g Release 2 (10.2)
B14200-02
http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_2012.htm#SQLRF00901
一句话总结:都是基本概念没过关,很多事情想当然的去理解,Oracle文档还是值得很多人细细的读。

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.
