通过shell检查Oracle分区表中是否含有默认分区
在大数据量的系统中,分区表是很常见的,分区有多种类型,可以根据业务来选择自己需要的分区,不过为了数据的兼容性,需要考虑对于分
在大数据量的系统中,分区表是很常见的,分区有多种类型,可以根据业务来选择自己需要的分区,不过为了数据的兼容性,需要考虑对于分区表设定一个默认的表分区,如果数据在插入表分区的时候,,没有符合条件的分区,就会插入默认的表分区中。
这个可以根据自己的需要来设定,如果确实对数据有严格的要求,甚至可以要求不加入默认的分区。
以下的脚本会去"扫描"分区的信息,如果检测到没有默认的分区,就会生成对应的脚本。
可以根据自己的情况来决定是否需要加入分区。
sqlplus -s $1/$2@$SH_DB_SID set head off
set pages 100
set linesize 200
/* bad performance
select name,Count(*)from user_part_key_columns where object_type='TABLE' and name in
(
select table_name from user_tables where partitioned='YES'
minus
(select distinct table_name
from user_tab_partitions where partition_name like '%MAX%'
)
)
group by name;
*/
select 'alter table '||table_name||' add partition PMAXVALUE values less than ('||
decode(col_count, 1, 'MAXVALUE',
2,'MAXVALUE,MAXVALUE',
3,'MAXVALUE,MAXVALUE,MAXVALUE',
4,'MAXVALUE,MAXVALUE,MAXVALUE,MAXVALUE','partition out of range')||');'
from
(
(
select t1.table_name,count(t2.name) col_count from user_tables t1,user_part_key_columns t2
where t1.partitioned='YES'
and t1.table_name=t2.name
and t2.object_type='TABLE'
group by t1.table_name
)
minus
(
select t2.name table_name,count(t2.name)col_count
from user_tab_partitions t1,user_part_key_columns t2
where t1.partition_name like '%MAX%'
and t1.table_name=t2.name
and t2.object_type='TABLE'
group by t2.name
)
)
/
EOF
exit
简单运行一下,可以看到有一些分区表是灭有默认的分区的。可以根据自己的情况来定夺。
[ora11g@rac1 dbm_lite]$ ksh getmaxpar.sh system Oracle
alter table LOGMNRC_GSBA add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNRC_GSII add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNRC_GTCS add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNRC_GTLO add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNRP_CTAS_PART_MAP add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_ATTRCOL$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_ATTRIBUTE$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_CCOL$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_CDEF$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_COL$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_COLTYPE$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_DICTIONARY$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_DICTSTATE$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_ENC$ add partition PMAXVALUE values less than (MAXVALUE);
alter table LOGMNR_ICOL$ add partition PMAXVALUE values less than (MAXVALUE);
浅谈Oracle分区表之范围分区
Oracle分区表迁移
Oracle分区表使用实例
Oracle分区表 (Partition Table) 的创建及管理
本文永久更新链接地址:

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.

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.

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.

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 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.

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 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.
