Partitioned views in Standard Edition

We have are SQL 2014 Standard edition, I have a situation where-in I plan to partition a table now since table partition is not supported in standard version I thought about Partitioned views however now I am stuck where I cant make the view writable because
of the identity column in the base table.
Do I have any other option in this case ?
Let me know your thoughts
Regards
Vishal
VG

Identity columns are problematic for a partitioned view. If any of the tables include an identity column, you can delete but not insert or update via the view. You could instead use a sequence to generate the surrogate key values, but that may require
significant application changes.
The real question is why you want to partition. There are specialized use cases where partitioning may improve performance (e.g. parallel scans) but you will generally get more benefit from index and query tuning. Partitioning (view
or table) can actually degrade performance depending on the queries and workload. That being said, partitioning always improves manageability.
Be aware that there is additional overhead of partitioned views compared to partitioned tables. Each table within the view may be indexed differently so there is considerable more work for the optimizer to do to generate an efficient plan.
This increases compilation time and can result in suboptimal plans, particularly if the view contains many tables. If your table is so large that partitioning is compelling, you might start making the business case for Enterprise Edition in order
to meet performance and availability SLAs.
I think the Database Engine forum is a better fit for this question so I'll move this thread there.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Similar Messages

Partitioning option in standard edition

Dear all,
Our company procured license for 10.2 standard edition db. Can we use partitioning option in this edition

Hello,
Do you really need Partitioning ? What is the size of your Tables ?
Please, find enclosed a useful link about Oracle editions:
http://www.oracle.com/us/products/database/product-editions-066501.html
It may help you to decide to choose Enterprise Edition.
Partitioning not only require Enterprise Edition but it's also an option which needs a specific license.
Best regards,
Jean-Valentin

Enterprise edition and standard edition

ORACLE 10.2.0.1.0 /REDHAT 5.1 - Enterprise linux 2.6.18
we would like to MIGRATE from enterprise edition to standard edition .
can we use dataguard,partitioning,flashback in standard edition .
santhanam.

Hi,
Yes, there are so many options not available with standard edition. like as you said dataguard and flashback database
like
1)online rebuilding/reorganization of tables
2)multiple channels in RMAN
3)only basic materialized view..
4)tuning&diagnostic packs
there are so many..
read http://www.dba-oracle.com/art_so_oracle_standard_enterprise_edition.htm
http://searchoracle.techtarget.com/answer/Standard-vs-Enterprise-Editions-of-Oracle

Partition option for Oracle 9i Enterprise/Standard Edition

Hello All,
could you help me please.
I'd like to download Oracle9i Database Release 2 Enterprise/Standard Edition for HP 9000 Series HP-UX for demonstration purposes.
Tell me please does it mean that this Enterprise Edition includs Partition option?

Installing Oracle is not easy for the beginner. Please consider asking Oracle Sales to assist you, as they have technical consultants who can do that for free.
All Oracle software that can be downloaded if available from http://otn.oracle.com ... look for the Downloads link at the top.
Partitioning Option is included in the Enterprise Edition software, but using Partitioning Option requires purchasing a separate license for the option. It can NOT be licensed for use with the Standard Edition.

What do you recommend to resize a partition on Windows Server 2003 R2 Standard Edition SP2?

I am running Windows Server 2003 R2 Standard Edition SP2 and only have 2.74GB of hard drive space left on a 11.9 GB hard drive. My D:\ drive has 37.5GB of free space left on a 124GB Hard drive. I would like to know what software is
recommended to repartition drive size or another way to repartition drive.
Thanks

You just need to shrink partition D and get some unallocated space, and then you can extend the system drive with the Unallocated space. There is no need to delete or format partitions.
The most important is guarantee data security. I have such experience resizing partitions.
The partition tool required reboot to process, after a while power off in my office, I know the Server must be damaged. Later, when I turn it on, I cannot believe, it continue to process and reboot to desktop several minutes later. What a lucky man.
A guide I've bookmarked
how to resize windows 2003 server partitions

Partition view on 10g and 11g

Hi All,
I am on 10.2 Standard edition and 11.1 Standard edition (2 databases in the application, one on 10g, another on 11g).
Being on standard edition, cannot use many common features e.g. partitioning, bitmap indexes etc.
I use to think that, partitioned view are no more supported by Oracle. But I can see that it works. I created 3 tables TEMP1, TEMP2 and TEMP3, all with exact same structure (columns and indices). Then created a view TEMP_VIEW, which is like
select col1, col2, col3 .... from temp1
union all
select col1, col2, col3 .... from temp2
union all
select col1, col2, col3 .... from temp3Here are the query execution and plans
/* ----------------- 10g execution plan ----------------------- */
SQL> select * from temp_view where object_id=2620 and branch_cd = 'XYZ';
OWNER                          OBJECT_NAME                    SUBOBJECT_NAME                  OBJECT_ID DATA_OBJECT_ID
OBJECT_TYPE         CREATED   LAST_DDL_ TIMESTAMP           STATUS T G S BRANC
SYS                            LOADER_TRIGGER_INFO                                                 2620
VIEW                18-FEB-09 16-APR-09 2009-02-18:10:07:57 VALID   N N N XYZ
Elapsed: 00:00:00.29
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=2 Card=1 Bytes=132)
   1    0   VIEW OF 'TEMP_VIEW' (VIEW) (Cost=2 Card=1 Bytes=132)
   2    1     UNION-ALL (PARTITION)
   3    2       TABLE ACCESS (BY INDEX ROWID) OF 'TEMP1' (TABLE) (Cost=2 Card=1 Bytes=132)
   4    3         INDEX (UNIQUE SCAN) OF 'TEMP1_PK' (INDEX (UNIQUE)) (Cost=1 Card=1)
   5    2       TABLE ACCESS (BY INDEX ROWID) OF 'TEMP2' (TABLE) (Cost=2 Card=1 Bytes=132)
   6    5         INDEX (UNIQUE SCAN) OF 'TEMP2_PK' (INDEX (UNIQUE)) (Cost=1 Card=1)
   7    2       TABLE ACCESS (BY INDEX ROWID) OF 'TEMP3' (TABLE) (Cost=2 Card=1 Bytes=132)
   8    7         INDEX (UNIQUE SCAN) OF 'TEMP3_PK' (INDEX (UNIQUE)) (Cost=1 Card=1)
/* ----------------- 11g execution plan ----------------------- */
SQL> select * from temp_view where object_id=2620 and branch_cd = 'XYZ';
OWNER                          OBJECT_NAME                    SUBOBJECT_NAME                  OBJECT_ID DATA_OBJECT_ID
OBJECT_TYPE         CREATED   LAST_DDL_ TIMESTAMP           STATUS T G S BRANC
PUBLIC                         GV$XML_AUDIT_TRAIL                                                  2620
SYNONYM             16-NOV-09 16-NOV-09 2009-11-16:16:36:08 VALID   N N N XYZ
Elapsed: 00:00:00.03
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=6 Card=3 Bytes=396)
   1    0   VIEW OF 'TEMP_VIEW' (VIEW) (Cost=6 Card=3 Bytes=396)
   2    1     UNION-ALL
   3    2       TABLE ACCESS (BY INDEX ROWID) OF 'TEMP1' (TABLE) (Cost=2 Card=1 Bytes=102)
   4    3         INDEX (UNIQUE SCAN) OF 'TEMP1_PK' (INDEX (UNIQUE)) (Cost=1 Card=1)
   5    2       TABLE ACCESS (BY INDEX ROWID) OF 'TEMP2' (TABLE) (Cost=2 Card=1 Bytes=102)
   6    5         INDEX (UNIQUE SCAN) OF 'TEMP2_PK' (INDEX (UNIQUE)) (Cost=1 Card=1)
   7    2       TABLE ACCESS (BY INDEX ROWID) OF 'TEMP3' (TABLE) (Cost=2 Card=1 Bytes=102)
   8    7         INDEX (UNIQUE SCAN) OF 'TEMP3_PK' (INDEX (UNIQUE)) (Cost=1 Card=1)Questions
1) I am expecting same behaviour on Oracle enterprise edition, will that be the case ?
2) On 10g, execution plan shows "UNION-ALL (PARTITION)", but on 11g it says, "UNION-ALL". What does that imply?
3) Which Oracle parameter can affect this behaviour? the old partition_view_enable parameter does not exist
4) If I go ahead and use this partitioned view, in which cases this can cause problems? At this point, it looks all good if I access the view using indexed columns (of the tables and all tables involved have exactly same indexes).
Thanks in advance

Billy Verreynne is an expert in this area and has been introducing people for years to 'partition views' and you can find many of his previous posts about how and when to use them (including example code) right here in these forums (most of them will be in the SQL and PL/SQL forum).
This feature has been around since Oracle 7 and the 7.3 document that details the info is still at
http://docs.oracle.com/cd/A57673_01/DOC/server/doc/A48506/partview.htm
Here is just one of his many other threads with more example code using five tables.
Table name in from clause

Failover in 10g Standard Edition tips

Hi guys,
We have an Oracle 10.2.0.5 Standard Edition Database in a Windows Server 2008 x64, and we were looking for a Failover solution. The idea is when the primary server could have a problem, automatically open in read/write mode the standby DB, and after repairing the primary DB, propagate the changes from the standby to the primary.
After researching, we had decided to create a Manual Physical Standby Database in another server, following this guide
We are now testing it and seems to work with no problems, but we like to know some tips or advices for that solution, or if it exists one better option for Failover in Standard Edition, from some experienced dbas from this forums. Can somebody help us with that?
Thanks in advance!
Juan Alvarez

user13325846 wrote:
How to programatically partition table in 10G standard Edition ?I had no idea (reading this thread) that 7.3's partition views were still supported. At the time (back in the mid 90's), we were explicitly told not to use this option for a large OPS data warehouse, by Oracle experts that assisted us in building and tuning the system. So never really used this option and thought it deprecated ifo proper partitioning introduced with v8.
I currently roll a my own partition-like feature on 10g SE - using dynamic SQL where a function is used to determine the table name. As all access to the tables are done via PL/SQL, this works fine (and bind variables are used all the way). On the client reporting side, we use APEX. APEX has the option of using a function (supplying the SQL) for reporting region, instead of coding the actual SQL. Again, PL/SQL is used to construct the source SQL (for the appropriate table) and given to APEX to parse and bind and execute as a report.
Of course, this is not nearly as flexible as the Enterprise partitioning feature, but it works fine for the (limited) job required.

(V7.3) PARTITION VIEWS IN RELEASE 7.3

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
SCOPE
8~10g Standard Edition 에서는 Partitioning Option 은 지원하지 않는다.
1. 소개
Partition view 는 Oracle Release 7.3 에서 대용량 테이블(예를 들면, data
warehousing에서 주로 사용함)을 지원하기 위해서 추가된 새로운 방법이다.
Partition View는 대용량 테이블에 대한 관리성 및 가용성을 향상시키고, 이들
테이블에 대한 질의 속도를 향상시킬 수 있다.
Partition view 의 예를 보면,
create view SALES as
          select * from jan_sales
     union all
          select * from feb_sales
     union all
          select * from dec_sales;
1월에서 12월까지의 sales table 들을 합한 뷰가 'SALES' 이다. 이들 월별
테이블들은 column name, data type, index가 모두 같아야 한다. 또한 이들
월별 테이블들은 partition column 에 check constraint 가 반드시 존재해야
하는데, 위의 예를 통해서 보면 jan_sales 의 date column 의 값들은 1월
1일에서 31일 사이의 date 만이 가능하도록 check constraint 가 있어야
한다.
Base table, indexes, constraints 뿐 만 아니라 UNION-ALL view 의 정의는
DBA에 의해 생성된다.
2. 관리성 및 가용성에 대한 장점
Partition view 는 대용량 테이블의 관리를 매우 쉽게 해 준다. 예를 들면,
위에서 정의한 'SALES' 라는 대용량 테이블을 살펴보자. 매월마다 DBA 는 새로운
달의 sales data 를 'SALES' 에 추가해야 한다. 따라서, DBA 는 'SALES' 에 대한
모든 index 들을 drop 하고, 새로운 데이타를 추가한 후에 index 를 재생성해야
할 것이다. 더구나, 'SALES'가 큰 테이블이므로 이 작업 시간도 상당히 오래 걸릴
것이다. 또한, 이 작업 동안 'SALES' 테이블은 사용할 수 없게 된다.
그러나, Partition view 를 사용한다면, 새로운 달의 테이타를 새로운
Partition을 만들어 추가하고, 이 새로운 Partition 에 index 를 생성하는 동안
현재 사용 중인 Partition 을 계속 사용할 수 있다. 따라서, 새로운 Partition 과
index 가 완성되었을 때, DBA 는 이 새로운 Partition 을 포함하는 UNION-All
view 를 재생성하면 된다. 이 UNION-ALL view 를 재생성하는 짧은 시간 동안만
'SALES' 가 사용 불가능하게 된다.
3. Partition view 의 성능 향상
Release 7.3 부터 제공하는 UNION-ALL view 를 사용하면, 단일 테이블 접근보다
적어도 같거나 대부분의 경우 더 좋은 성능 향상을 얻을 수 있다.
단, 모든 Partition들은 반드시 같은 column에 check constraint가 있어야 하고,
column 정의와 index가 같아야 성능 향상의 효과를 얻을 수 있다.
Partition view 에는 다음 두 가지의 성능이 향상되었다.
① Partition 제거
② UNION-ALL view 의 Parallel 수행
먼저, Partition 제거란 다음과 같다. 위에서 생성된 'SALES' partition view
에 대한 임의의 질의들은 일부의 Partition들로부터 데이타를 가져온다.
예를 들어,
select sum(revenues) from SALES
where sales_date between '15-JAN-96' and '15-FEB-96';
와 같은 질의는 Partition view 로 처리될 경우, JAN partition view와 FEB
partition view 만으로 산출된다. 즉, 나머지 10개의 Partition은 접근하지
않는다. 이것을 Partition 제거라고 한다. Partition 제거는 Partition column
에 대한 질의에서만 사용될 수 있다. 위의 예에서는 sales_date column 이
partition column 이다.이러한 제약 사항은 있지만, 속도 향상은 주목할 만
한다. 위의 예에서 보듯이 12개 중 10개의 Partition 을 제외하여 6배의
성능 향상을 얻었다.
Partition view 를 사용 했을 때, 또 다른 장점은 UNION-ALL view 를 parallel
수행한다는 것이다. Parallel Query Option 이 설치된 경우, 모든 UNION-ALL
view 에 대한 질의는 parallel 로 수행된다. 이점은 다른 경쟁 회사들의
parallel query 구조(이들 제품들은 데이타 partition의 물리적 구조가
parallelism 을 결정한다)와는 다르게 parallelism degree 와는 독립적으로
수행된다는 점은 매우 특이하다. 오라클은 UNION-ALL view 의 데이타를
모든 parallel query processes에게 동적으로 균등하게 배분하고, 위에서
언급한 partition 제거 또한 parallelism degree에 영향을 주지 않는다.
* Partition view 의 제약 사항
Partition view 는 DML 연산을 제공하지 않는다. 따라서, READ-ONLY
application (data warehousing 등등) 에 적합하다.

Spoke to Apple support and they basically suggest I play ping pong with Microsoft, on the basis that all works under OSX, but MS say it is up to Apple to supply the drivers for the hardware, just great. So looks like I shall continue as is for now.

(V7.3) PARTITION VIEW 테스트 REPORT

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
SCOPE
8~10g Standard Edition 에서는 Partitioning Option 은 지원하지 않습니다.
1. 개요
대용량 Database를 구축하고 관리하는 데 있어서 필연적으로 나타날 수 있는
문제는 시간적 증가 또는 지역적으로 확대됨에 따라 어느 TABLE의 SIZE가
증가함에 따라 이에 따른 관리 방법의 효율화일 것이다.
이는 주기적인 재편성(Re-Organization) 뿐만 아니라 Backup, Index의 비대화
등에 따른 Query의 효율 저하 등 여러가지 문제를 야기시킬 수 있다.
이에 대한 해결책인 Partition View(Ver.7.3 이상)를 실무적용 사례를 통해서
구축방법, Partition View의 효율적 사용방법, 주의할 점 등을 알아보고자 한다.
2. 구축과정
1) Partition View를 위한 Parameter
init$ORACLE_SID.ora 화일에 다음의 Parameter를 Setting
partition_view_enabled=TRUE
2) Partition View 대상 Table 및 Partition Column을 선정
이는 물리적 설계 시 결정
Partition Column의 주요 후보는 일시, 지역 등 명확히 구분되는
Column이어야 함
3) Table Create --> Partition Column에 반드시 해당 범위의 Check
Constraint를 반드시 주어야 함.
( 주의 사항 )
Partition Column의 DATATYPE을 CHAR로 하지 말 것
(BUG) --> VARCHAR2 사용 ( BUG로 등록되어 있음 )
Partition View를 구성하는 모든 Table Scheme는 완전히 동일해야 함
(Column의 갯수, Datatype, Null허용 여부 등)
실제로 비씨카드에서 TYPE의 불일치로 문제가 발생했었음.
1996.01월 Table(TBCARDUSE_199601)의 한 Column의 Type이 다른
Table은 모두 VARCHAR(9)였는데 이 Table만 VARCHAR2(10)로
되어 있어서 Partition View를 JOIN하면 VIEW 내의 모든 TABLE이
FULL TABLE SCAN을 함. DATATYPE을 동일하게 해준 후 정상적으로
동작
4) Index Create --> 모든 Table이 반드시 동일한 Index를 가져야 함.
Partition Column에 Index가 반드시 필요한 것은 아님.
5) 각 Table에 ANALYZE TABLE을 수행(가능한 한 COMPUTE STATISTICS로)
6) Partition 내의 모든 Table을 UNION ALL 한 Partition View를 생성
3. 구축 사례
TBCARDUSE_199507 - TBCARDUSE_199609 ( 15개 Table )
각 Table의 예상 Row 수는 최소 1,200 만 이상으로 15개월을 보관함을
원칙으로 하여 총 Row는 2억건 정도이다.
CREATE TABLE TBCARDUSE_199507
(USE_NO varchar2(8) not null,
CARD_NO varchar2(16) not null,
REQ_REJ_CLSS char(1) not null,
LO_AB_CLSS char(1) not null,
MER_MGMT_NO varchar2(9) not null,
AUTH_CLSS char(2) not null,
AUTH_DATE varchar2(8) not null,->Partition Column
AUTH_TIME char(6) not null,
AUTH_AMT number(13,2) not null,
EN_MODE char(2) not null,
AUTH_REQ_MTHD char(2) not null,
AUTH_REQ_CLSS char(1) not null,
SALE_REF_PL char(2) ,
REQ_MER_MGMT_NO varchar2(9) ,
SALE_PL_NO varchar2(12) ,
REQ_VALD_LIM char(6) ,
USE_AMT number(11) ,
RCP_AMT number(11) ,
MER_RCP_FEE number(11) ,
RCP_DATE char(8) ,
POS_CODE char(2) ,
CONSTRAINT C_AUTH_DATE_199507
CHECK (AUTH_DATE BETWEEN '19950701' AND '19950731'))
---> Partition Column Constraint
TABLESPACE TS_TUNING01
PCTFREE 10
STORAGE(INITIAL 100M NEXT 100M PCTINCREASE 0
MAXEXTENTS UNLIMITED FREELISTS 10);
* Index 정보
Index 1 : CARD_NO
CREATE INDEX TBCARDUSE_199507_IDX1
ON TBCARDUSE_199507(CARD_NO)
TABLESPACE TS_TUNING_I01
STORAGE(INITIAL 50M NEXT 50M PCTINCREASE 0
MAXEXTENTS UNLIMITED)
PARALLEL (DEGREE 4);
Index 2 : USE_NO
CREATE INDEX TBCARDUSE_199507_IDX2
ON TBCARDUSE_199507(USE_NO)
TABLESPACE TS_TUNING_I01
STORAGE(INITIAL 50M NEXT 50M PCTINCREASE 0
MAXEXTENTS UNLIMITED)
PARALLEL (DEGREE 4);
Index 3 : AUTH_DATE + MER_MGMT_NO
CREATE INDEX TBCARDUSE_199507_IDX3
ON TBCARDUSE_199507(AUTH_DATE,MER_MGMT_NO)
TABLESPACE TS_TUNING_I01
STORAGE(INITIAL 50M NEXT 50M PCTINCREASE 0
MAXEXTENTS UNLIMITED)
PARALLEL (DEGREE 4);
Index 4 : MER_MGMT_NO + AUTH_DATE
CREATE INDEX TBCARDUSE_199507_IDX4
ON TBCARDUSE_199507(MER_MGMT_NO, AUTH_DATE)
TABLESPACE TS_TUNING_I01
STORAGE(INITIAL 50M NEXT 50M PCTINCREASE 0
MAXEXTENTS UNLIMITED)
PARALLEL (DEGREE 4);
* Table Analyzing
analyze table TBCARDUSE_199507 compute statistics;
* Partition View Creation
CREATE OR REPLACE VIEW PV_TBCARDUSE
AS
SELECT * FROM TBCARDUSE_199507
UNION ALL
SELECT * FROM TBCARDUSE_199508
UNION ALL
SELECT * FROM TBCARDUSE_199509
UNION ALL
SELECT * FROM TBCARDUSE_199510
UNION ALL
SELECT * FROM TBCARDUSE_199511
UNION ALL
SELECT * FROM TBCARDUSE_199512
UNION ALL
SELECT * FROM TBCARDUSE_199601
UNION ALL
SELECT * FROM TBCARDUSE_199602
UNION ALL
SELECT * FROM TBCARDUSE_199603
UNION ALL
SELECT * FROM TBCARDUSE_199604
UNION ALL
SELECT * FROM TBCARDUSE_199605
UNION ALL
SELECT * FROM TBCARDUSE_199606
UNION ALL
SELECT * FROM TBCARDUSE_199607
UNION ALL
SELECT * FROM TBCARDUSE_199608
UNION ALL
SELECT * FROM TBCARDUSE_199609
4. Test Procedure
1) Partition View의 동작 여부 확인
(1) Partition Column이 '='로 비교 되었을 때
SELECT CARD_NO,USE_NO,AUTH_DATE,AUTH_AMT
FROM PV_TBCARDUSE
WHERE USE_NO = '00002037'
AND AUTH_DATE = '19960723';
Rows Execution Plan
0 SELECT STATEMENT GOAL: CHOOSE
1 VIEW OF 'PV_TBCARDUSE'
1 UNION-ALL (PARTITION)
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199507'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199507_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199508'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199508_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199509'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199509_IDX2'
0 FILTER ---> Access 불 필요 Skip Operation
0 TABLE ACCESS OF 'TBCARDUSE_199510'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199511'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199511_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199512'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199512_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199601'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199601_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199602'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199602_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199603'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199603_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199604'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199604_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199605'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199605_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199606'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199606_IDX2'
1 TABLE ACCESS OF 'TBCARDUSE_199607'
2 INDEX (RANGE SCAN) OF 'TBCARDUSE_199607_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199608'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199608_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199609'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199609_IDX2'
( 설명 ) Partition View의 가장 일반적인 사용 Case로 Partition
Column이 *=*로 비교 되었을 때는 Access 불 필요
Table은 Skip하는 Operation (FILTER)이 동작 함.
(2) Partition Column이 " BETWEEN ~ AND ~ "로 비교 될 때
SELECT CARD_NO,USE_NO,AUTH_DATE,AUTH_AMT
FROM PV_TBCARDUSE
WHERE USE_NO = '00002037'
AND AUTH_DATE BETWEEN '19960701' AND '19960731'
Rows Execution Plan
0 SELECT STATEMENT GOAL: CHOOSE
1 VIEW OF 'PV_TBCARDUSE'
1 UNION-ALL (PARTITION)
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199507'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199507_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199508'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199508_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199509'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199509_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199510'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199511'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199511_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199512'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199512_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199601'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199601_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199602'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199602_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199603'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199603_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199604'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199604_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199605'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199605_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199606'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199606_IDX2'
1 TABLE ACCESS OF 'TBCARDUSE_199607'
2 INDEX (RANGE SCAN) OF 'TBCARDUSE_199607_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199608'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199608_IDX2'
0 FILTER
0 TABLE ACCESS OF 'TBCARDUSE_199609'
0 INDEX (RANGE SCAN) OF 'TBCARDUSE_199609_IDX2'
( 설명 ) Partition Column이 BETWEEN~AND~ 로 비교 되었을 때는
Access 불 필요 Table은 Skip하는 Operation(FILTER)이
동작 함
(3) Partition Column이 " LIKE "로 비교 될 때
SELECT CARD_NO,USE_NO,AUTH_DATE,AUTH_AMT
FROM PV_TBCARDUSE
WHERE USE_NO = '00002037'
AND AUTH_DATE LIKE '199607%'
Rows Execution Plan
0 SELECT STATEMENT GOAL: CHOOSE
1 VIEW OF 'PV_TBCARDUSE'
1 UNION-ALL (PARTITION)
0 TABLE ACCESS OF 'TBCARDUSE_199507'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199508'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199509'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199510'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199511'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199511_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199512'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199512_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199601'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199601_IDX2'
1 TABLE ACCESS OF 'TBCARDUSE_199602'
2 INDEX (RANGE SCAN) OF 'TBCARDUSE_199602_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199603'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199603_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199604'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199604_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199605'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199605_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199606'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199606_IDX2'
1 TABLE ACCESS OF 'TBCARDUSE_199607'
2 INDEX (RANGE SCAN) OF 'TBCARDUSE_199607_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199608'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199608_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199609'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199609_IDX2'
( 설명 ) Partition Column이 LIKE로 비교 되었을 때는
FILTER가 동작하지 않음. (주의 요망)
(4) Partition Column이 " OR "로 비교 될 때
SELECT CARD_NO,USE_NO,AUTH_DATE,AUTH_AMT
FROM PV_TBCARDUSE
WHERE USE_NO = '00002037'
AND ( AUTH_DATE BETWEEN '19960601' AND '19960630'
OR AUTH_DATE BETWEEN '19960701' AND '19960730')
Rows Execution Plan
0 SELECT STATEMENT GOAL: CHOOSE
1 VIEW OF 'PV_TBCARDUSE'
1 UNION-ALL (PARTITION)
0 TABLE ACCESS OF 'TBCARDUSE_199507'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199508'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199509'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199510'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199510_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199511'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199511_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199512'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199512_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199601'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199601_IDX2'
1 TABLE ACCESS OF 'TBCARDUSE_199602'
2 INDEX (RANGE SCAN) OF 'TBCARDUSE_199602_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199603'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199603_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199604'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199604_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199605'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199605_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199606'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199606_IDX2'
1 TABLE ACCESS OF 'TBCARDUSE_199607'
2 INDEX (RANGE SCAN) OF 'TBCARDUSE_199607_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199608'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199608_IDX2'
0 TABLE ACCESS OF 'TBCARDUSE_199609'
1 INDEX (RANGE SCAN) OF 'TBCARDUSE_199609_IDX2'
( 설명 ) Partition Column이 OR로 비교 되었을 때는
FILTER가 동작하지 않음. ( BUG로 등록되어 있음 )
(5) Partition Column이 " BETWEEN "으로 비교되고 다른 비교
Column이 없을 때
SELECT CARD_NO,USE_NO,AUTH_DATE,AUTH_AMT
FROM PV_TBCARDUSE
WHERE AUTH_DATE BETWEEN '19960601' AND '19960630'
EXECUTION PLAN
SELECT STATEMENT
VIEW PV_TBCARDUSE
UNION-ALL (PARTITION)
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199507
INDEX (RANGE SCAN) TBCARDUSE_199510_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199508
INDEX (RANGE SCAN) TBCARDUSE_199510_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199509
INDEX (RANGE SCAN) TBCARDUSE_199510_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199510
INDEX (RANGE SCAN) TBCARDUSE_199510_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199511
INDEX (RANGE SCAN) TBCARDUSE_199511_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199512
INDEX (RANGE SCAN) TBCARDUSE_199512_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199601
INDEX (RANGE SCAN) TBCARDUSE_199601_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199602
INDEX (RANGE SCAN) TBCARDUSE_199602_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199603
INDEX (RANGE SCAN) TBCARDUSE_199603_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199604
INDEX (RANGE SCAN) TBCARDUSE_199604_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199605
INDEX (RANGE SCAN) TBCARDUSE_199605_IDX3
TABLE ACCESS FULL TBCARDUSE_199606
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199607
INDEX (RANGE SCAN) TBCARDUSE_199607_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199608
INDEX (RANGE SCAN) TBCARDUSE_199608_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199609
INDEX (RANGE SCAN) TBCARDUSE_199609_IDX3
(6) Partition Column이 " OR "로 비교되고 다른 비교 Column이
없을 때.
SELECT CARD_NO,USE_NO,AUTH_DATE,AUTH_AMT
FROM PV_TBCARDUSE
WHERE AUTH_DATE BETWEEN '19960501' AND '19960531'
OR AUTH_DATE BETWEEN '19960601' AND '19960630'
OR AUTH_DATE BETWEEN '19960701' AND '19960731'
EXECUTION PLAN
SELECT STATEMENT
VIEW PV_TBCARDUSE
UNION-ALL (PARTITION)
TABLE ACCESS FULL TBCARDUSE_199507
TABLE ACCESS FULL TBCARDUSE_199508
TABLE ACCESS FULL TBCARDUSE_199509
TABLE ACCESS FULL TBCARDUSE_199510
TABLE ACCESS FULL TBCARDUSE_199511
TABLE ACCESS FULL TBCARDUSE_199512
TABLE ACCESS FULL TBCARDUSE_199601
TABLE ACCESS FULL TBCARDUSE_199602
TABLE ACCESS FULL TBCARDUSE_199603
TABLE ACCESS FULL TBCARDUSE_199604
TABLE ACCESS FULL TBCARDUSE_199605
TABLE ACCESS FULL TBCARDUSE_199606
TABLE ACCESS FULL TBCARDUSE_199607
TABLE ACCESS FULL TBCARDUSE_199608
TABLE ACCESS FULL TBCARDUSE_199609
# 최악의 경우
(7) 위 (6)의 Query를 " BETWEEN "으로 변환 경우
SELECT /*+ FULL(PV_TBCARDUSE) */
CARD_NO,USE_NO,AUTH_DATE,AUTH_AMT
FROM PV_TBCARDUSE
WHERE AUTH_DATE BETWEEN '19960501' AND '19960731'
EXECUTION PLAN
SELECT STATEMENT
VIEW PV_TBCARDUSE
UNION-ALL (PARTITION)
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199507
INDEX (RANGE SCAN) TBCARDUSE_199510_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199508
INDEX (RANGE SCAN) TBCARDUSE_199510_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199509
INDEX (RANGE SCAN) TBCARDUSE_199510_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199510
INDEX (RANGE SCAN) TBCARDUSE_199510_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199511
INDEX (RANGE SCAN) TBCARDUSE_199511_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199512
INDEX (RANGE SCAN) TBCARDUSE_199512_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199601
INDEX (RANGE SCAN) TBCARDUSE_199601_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199602
INDEX (RANGE SCAN) TBCARDUSE_199602_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199603
INDEX (RANGE SCAN) TBCARDUSE_199603_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199604
INDEX (RANGE SCAN) TBCARDUSE_199604_IDX3
TABLE ACCESS FULL TBCARDUSE_199605
TABLE ACCESS FULL TBCARDUSE_199606
TABLE ACCESS FULL TBCARDUSE_199607
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199608
INDEX (RANGE SCAN) TBCARDUSE_199608_IDX3
FILTER
TABLE ACCESS (BY ROWID) OF TBCARDUSE_199609
INDEX (RANGE SCAN) TBCARDUSE_199609_IDX3
2) Insert, Delete, Update의 사용
현재까지는 Partition View에 직접적으로 Insert/Delete/Update를
할 수 없다.
(이는 8.0 Version에 가능] 따라서 현재는 2 가지 방법으로 가능.
(1) DYNAMIC SQL을 이용하는 방법
(2) LOGIC적으로 IF-ELSE 방법을사용하여 가능한 일어 날 수 있는 모든
경우를 기술하는 방법
(비교) (1)의 방법은 Application 작성이 간단하기는 하나 LOOP안에서
수행되거나 빈번히 수행되는 경우에는 Parsing Overhead가
심각해 질 정도로 증가 됨.
(2)의 방법은 (1)의 단점을 해소 할 수 있으나 Partition
Table이 추가, 변경됨 따라 주기적으로 APPLICATION이 같이
변경해 주어야 한다.
3) Partition View의 효율적인 사용 방법
(1) Parsing Time의 감소
Partition View는 많은 수의 Table을 UNION ALL View로 만든
것이므로 Query 수행 시 Parsing Time의 Overhead로 인해 성능
저하를 가져 올 수 있다.
이에 대해서 물리적인 방법(HOLD_CURSOR,
CURSOR_SPACE_FOR_TIME=true 등)으로 Re-Parsing Time을 줄일
수 있으나 Partion View를 효율적으로 생성하므로써 Overhead를
줄일 수 있다.
(가) 수직적 분할
(사례)에서는 약 100개 정도의 Column에 대해서 "Select * "의
형태로 되어 있어 Data Dictionary Call이 그만큼 많아 진다.
그러나 Table의 속성을 보면 필수 NOT NULL Column(10ro)을
제외한 90개의 Column이 실제적으로는 '신용판매','현금서비스',
'해외이용'의 3가지로 GROUPING 되는 것으로 PARTITION VIEW
자체를 3개 정도로 분할(수직적인 분할)하고 사용하여 Overhead
를 줄인다.
(나) 수평적 분할
가장 ACTIVE한 범위를 정하여 수평적으로 분할하여 Partition
View를 생성한다.
(사례)에서는 3개월,6개월,9개월 단위의 Partition View를
만들어 사용하고 있다.
(2) Partition Column이 비교절에 나오지 않을때
이 때는 어쩔 수 없이 Partition Column이 사용 될 수 없으므로
일반적인 UNION-ALL View형태로 Access 될 수 밖에 없다. 그러나
SELECT 결과가 1건일 경우에는 ROWNUM 제한을 시켜 될 수 있는 한
TABLE ACCESS를 제한시킨다.
( UNION ALL의 순서를 역순으로 하여 VIEW를 생성 )
CREATE OR REPLACE VIEW PV_TBCARDUSE1
AS
SELECT * FROM TBCARDUSE_199609
UNION ALL
SELECT * FROM TBCARDUSE_199608
UNION ALL
SELECT * FROM TBCARDUSE_199607
UNION ALL
SELECT * FROM TBCARDUSE_199606
UNION ALL
SELECT * FROM TBCARDUSE_199605
UNION ALL
SELECT * FROM TBCARDUSE_199604
UNION ALL
SELECT * FROM TBCARDUSE_199603
UNION ALL
SELECT * FROM TBCARDUSE_199602
UNION ALL
SELECT * FROM TBCARDUSE_199601
UNION ALL
SELECT * FROM TBCARDUSE_199512
UNION ALL
SELECT * FROM TBCARDUSE_199511
UNION ALL
SELECT * FROM TBCARDUSE_199510
UNION ALL
SELECT * FROM TBCARDUSE_199509
UNION ALL
SELECT * FROM TBCARDUSE_199508
UNION ALL
SELECT * FROM TBCARDUSE_199507
SELECT * FROM PV_TBCARDUSE1
WHERE USE_NO = '123456' ---+
AND CARD_NO = '45991276182212' ---+ (UNQUE)
AND ROWNUM = 1;
(사례)에서 시간적으로 최근의 TABLE을 먼저 UNION ALL하여
사용하였다. 이는 원하는 정보가 최근에 있을 확률이 높기때문에
먼저 찾게되면 더이상 TABLE의 ACCESS를 하지 않기때문이다.
(3) HINT의 사용
Partition View에 Hint 사용은 보통의 Query에 대해서와 같이
사용한다.
(1) PARALLEL HINT
SELECT /*+ PARALLEL(PV_TBCARDUSE,2) */
SUM(AUTH_AMT)
FROM PV_TBCARDUSE
WHERE AUTH_DATE BETWEEN '19960501' AND '19960731'
TBCARDUSE_199605,TBCARDUSE_199606,TBCARDUSE_199607
Table을 Parallel로 처리한다.
(2) INDEX_DESC HINT
이는 INDEX이름이 HINT내에 들어가야 하므로 원칙적으로는
불가능하지만 사용 될 Table이 명확하게 정의된다면 사용 할
수도 있다.
SELECT /*+ INDEX_DESC(a TBACRDUSE_199605_IDX1) */
FROM PV_TBCARDUSE a
WHERE CARD_NO = '4599243141847231'
AND AUTH_DATE BETWEEN '19960501' AND '19960531'
AND ROWNUM = 1

Hello,
Incorrect Display of Tables and Frames in Firefox when DESFORMAT=HTMLCSS (Doc ID 412272.1)
Regards

Problem Moving From the Standard Edition to the Enterprise Edition

Hi !
I am trying to move from Oracle 10g R2 10.2.0.1 Standard Edition to Oracle 10g R2 10.2.0.1 Enterprise Edition.
Platform is MS Windows XP PRO SP2
I follow all steps described in "Oracle® Database Upgrade Guide 10g Release 2 (10.2)" - section Moving From the Standard Edition to the Enterprise Edition.
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14238/intro.htm#sthref10
The problem is that after update from St. edition to Ent. edition when I run:
select * from v$version - I see :
Connected to:
Oracle Database 10g Release 10.2.0.1.0 - Production
while I expect to see something like .....
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining Scoring Engine options
Am I wrong ? Why information in view v$version does not update after this ?
Regards,
Phil
Message was edited by:
user585467

In your document you refer to the upgrade guide, this upgrade guide applies when you are upgrading from previous Oracle releases to 10g, not SE->EE.
If you want a procedure to upgrade the SE to EE, then follow this metalink note:
"How to Upgrade from Standard to Enterprise Edition ?
Doc ID: Note:117048.1"
If you performed this specific upgrade and you still see this error, then probably you are facing a bug, similar to the one described in "5844095", where the version is changed form SE->EE after 10.2.0.3 patchset application.
In your case it should be enough to apply 10.2.0.3 patchset to show it properly.
~ Madrid

Windows server 2008 R2 Standard Edition

Dear Team,
I am having server 2008 R2 standard edition. The Server is getting shut down and showing error in event viewer
"Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first"
Please reply on this asap to resolve the issue.

Hi,
unfortunately it is impossible to trace the cause if an improper shutdown from just the event (title).
Check this related kb article:
http://support.microsoft.com/kb/2028504
Please post back if you need further assistance in troubleshooting or consider opening a support case with Microsoft in case you want Microsoft to fix this for you.
MCP/MCSA/MCTS/MCITP

SQL Server Distributed Partitioning Views how to add a new node online

We are using distributed partitioning views in SQL Server 2012 Enterprise Edition for scaling out our data across more than one servers. Now we faced to question how to add a new node (server) into the scale outed db servers system without sending the servers
down, so our users will be able to use them during the process as well.
For example we have 4 servers with scaled out data. When we add the new empty server, the CHECKINGs for the partitioning columns should be reorganized. But during the process the partitioning views are not working.
The High Availability, Always On or Failover Cluster approaches seem are not resolve the problems.
So my question is how to add new node online?
KH

Thank you Erland for the reply.
Yes, it's sounds as possible solution but has some not resolvable nuance in it. Let's say we copied some data from Node5 to new added Node6. Let's assume in Node5 we had data in Table1 with partitioning column's values 100,101,102,103,104,105,106. Now
we want to copy part of the rows with partitioning column's values 103,104,105,106 from Node5.Table1 into Node6.Table1. With this Node5 will contain less data and will work more quickly (less IO, less CPU usage etc), and the rest data will be contained on
Node6. But because of Node5 is already in use, the Node5.Table1 contains CHECK CONSTRAINT = ParttionColumn should be from 100 up to 106. This is check for Node5. The Distributed Partitioning Views are already using the CHECKs to identify what server should
be used to get data from.
Now when we copied part of the Node5.Table1 rows to Node6.Table1 the views are still using the 103-106 rows from Node5.Table1 because the CHECK points there. Then we include the newest Node6.Table1 in the distributed partitioning views. OK, but we should
set some CHECK on new Node6.Table1 which will be used by views. We can't set intersecting checking like Node5 has CHECK 100-106 and Node6 has CHECK 103-106. We also can't edit Node5 check and set it 100-102 untill the data will be removed in it. But this means
that the data will not be available during the execution.
So, any ideas ?
KH

Standard edition unable to connect Discoverer 10g??

I am doing a proof of concept. I am using the Oracle 10g Standard edition DB and Discoverer. I downloaded th e Discoverer Admin and created an EUL over some sample tables. Now when I attempt to connect the error End User Layer Tables version 5.1.1.0.0.0 requires End User Layer Library of at least Version 10.1.2.45.20.0.
Is this telling me I can not do this proof of concept with Oracle DB standard edition?

You need to ensure that the version of Discoverer Admin is the same as the version of Discoverer Plus/Viewer/Desktop you're using. From what you're saying, I think you're using the version of Discoverer Admin that comes with either 9iDS or 10gDS, you then created your EUL and now you're trying to connect using Discoverer Plus/Viewer 10.1.2.
To sort this out, download the BI Tools that come with Business Intelligence 10g http://download.oracle.com/otn/nt/ias/1012/OracleBITools10gWin.exe then start the version of Discoverer Admin that comes with this download, connect to your EUL and you will be asked whether you want to upgrade the EUL tables. Go ahead and do this, and then you should be able to use Discoverer 10.1.2 against your EUL.
HTH
Mark

Standard Edition ONE and Advanced Installation

Hello,
I would like to perform an installation of the Oracle DB 11g Standard Edition ONE by using the Advanced installation. However, the Standard Edition ONE option is not available in the Advanced installation.
Can I use the Standard Edition option?
How can I proceed?
Thanks!
:)

Nathan Morgan wrote:
I have installed SE1 many times by clicking the SE option on the installer page. There is no SE1 option. From the point of view of the database installer SE1 and SE are identical. The software components are the same. The limitation in the licence agreement is that SE1 is restricted to a single machine with maximum capacity 2 sockets (2 n-core processors) -but- SE can be installed as a multple node RAC cluster with a maximum total capacity of 4 sockets (4 n-core processors). For example, see Oracle® Database Licensing Information 11g Release 1 (11.1) Part Number B28287-08
I AGAIN referenced that document. And again I do not see anything in the Licensing document that says you INSTALL SE1 by selecting SE. I see a lot of references to the fearture comparison. So I ASSUME that the installation is by selecting SE and using moral control over how it is deployed.
Could you please copy/paste the paragraph that turns it from assumption to fact ..

How to setup replication using Oracle 11gR2 standard edition one

Dear Guys,
I have two machines on which Oracle 11gR2 standard edition one is installed. I want to establish replication between them. How can I setup it? Please refer me to some step by step guide. I will be thankful to you guys.

Replicating Data Using Materialized Views
http://docs.oracle.com/cd/E14072_01/server.112/e10703/tdpii_reppit.htm#BEHHGGIB
Replicating Read/Write Data Using Materialized Views
http://docs.oracle.com/cd/E14072_01/server.112/e10703/tdpii_reppit.htm#BEHCEFGC

Partitioned views in Standard Edition

Similar Messages

Maybe you are looking for