About patch 2529822,is it necessory for BI sample?

Question

Hi folds!
I want to use the sample of olap,and i must install BI Beans from OTN.My database is Oracle9.2.0.2,and i know i need patch sets :263293,2529822 .
But i am a student and have no Support Identifier.How can i get patch sets? what is patch 2529822? is it necessory?
Best Regards.
Thanks
Jiaowei Zhao

Answer 1

Oracle9i OLAP
Best Practices for Tabular Cube Aggregation and Query Operations
Release 2 for Windows and UNIX
March 2003
Part No. A92122-04
This document provides techniques and practices designed to optimize the performance of typical OLAP operations and manageability of the environment. This information is divided into four distinct categories:
Schema Design Considerations
Oracle Configuration Parameters and Session Settings for Access Structure Builds
Access Structure Scripting Package
Query Operation Optimizations
Schema Design Considerations
Assign surrogate keys, which are unique across all hierarchical levels, to dimensional data. The surrogate keys are defined as type NUMBER with length defined by the magnitude of distinct dimension members. (If there is expected growth in this list, factor that in accordingly.) These surrogate keys are to be used as the primary keys of the dimension tables. A routine to supplement the character keys in the fact tables with the newly defined surrogates must be run prior to defining OLAP objects. An example script for this type of routine is provided below.
Create separate tablespaces for planned Materialized Views and View Indices. This will not significantly affect any aspect of performance, but it is good practice for file management.
Compute statistics on base tables prior to executing build scripts for access structures (materialized views and indices).
Surrogate Key Assignment (Example)
This example generates surrogate keys for the channel members and recreates the channel table with the surrogate keys. It then recreates the sales table with the surrogate keys included.
PROMPT Generate surrogate keys for CHANNELS
DROP TABLE chan_skey;
CREATE TABLE chan_skey AS
SELECT
lvlid AS lvlid,
dimval AS dimval,
dense_rank () OVER
(ORDER BY lvlid, dimval) AS dimkey
FROM
(SELECT DISTINCT TO_CHAR(channel_total) AS dimval, 0 lvlid FROM
channels UNION ALL
SELECT DISTINCT TO_CHAR(channel_class) AS dimval, 1 lvlid FROM
channels UNION ALL
SELECT DISTINCT TO_CHAR(channel_id) AS dimval, 2 lvlid FROM
channels);
COMMIT;
DROP INDEX chan_skey_index;
CREATE INDEX chan_skey_index ON chan_skey(lvlid);
COMMIT;
PROMPT Create CHANNELS_NEW table with surrogate keys
DROP TABLE channels_new;
CREATE TABLE channels_new
( channel_id CHAR(1),
channel_id_key NUMBER,
channel_desc VARCHAR2(20),
channel_class VARCHAR2(20),
channel_class_key NUMBER,
channel_total VARCHAR2(13),
channel_total_key NUMBER) ;
INSERT /*+ APPEND*/ INTO channels_new
SELECT c.channel_id,
(SELECT DISTINCT sk2.dimkey
FROM chan_skey sk2
WHERE sk2.dimval = TO_CHAR(c.channel_id)
AND sk2.lvlid = 2),
c.channel_desc,
c.channel_class,
(SELECT DISTINCT sk1.dimkey
FROM chan_skey sk1
WHERE sk1.dimval = TO_CHAR(c.channel_class)
AND sk1.lvlid = 1),
c.channel_total,
(SELECT DISTINCT sk0.dimkey
FROM chan_skey sk0
WHERE sk0.dimval = TO_CHAR(c.channel_total)
AND sk0.lvlid = 0)
FROM channels c;
COMMIT;
DROP table chan_skey;
prompt Create SALES with references to the surrogate keys
DROP TABLE sales_new;
CREATE TABLE sales_new
PARTITION BY RANGE (time_id_key)
(PARTITION sales_q1_1998 VALUES LESS THAN (91),
PARTITION sales_q2_1998 VALUES LESS THAN (182),
PARTITION sales_q3_1998 VALUES LESS THAN (274),
PARTITION sales_q4_1998 VALUES LESS THAN (366),
PARTITION sales_q1_1999 VALUES LESS THAN (456),
PARTITION sales_q2_1999 VALUES LESS THAN (547),
PARTITION sales_q3_1999 VALUES LESS THAN (639),
PARTITION sales_q4_1999 VALUES LESS THAN (731),
PARTITION sales_q1_2000 VALUES LESS THAN (822),
PARTITION sales_q2_2000 VALUES LESS THAN (913),
PARTITION sales_q3_2000 VALUES LESS THAN (1005),
PARTITION sales_q4_2000 VALUES LESS THAN (MAXVALUE))
AS
SELECT products_new.prod_id_key,
customers_new.cust_id_key,
times_new.time_id_key,
channels_new.channel_id_key,
promotions_new.promo_id_key,
sales.quantity_sold,
sales.amount_sold
FROM products_new,
customers_new,
times_new,
channels_new,
promotions_new,
sales
WHERE sales.prod_id = products_new.prod_id AND
sales.cust_id = customers_new.cust_id AND
sales.time_id = times_new.time_id AND
sales.channel_id = channels_new.channel_id AND
sales.promo_id = promotions_new.promo_id;
REM DROP TABLE sales;
REM RENAME table sales_new sales;
Oracle Configuration Parameters and Session Settings for Access Structure Builds
Cube Aggregation Optimizations
init.ora Parameters
Modify the standard init.ora file (named initsid.ora, located oracle_home/admin/sid/pfile) by setting or adding the parameters described below. When starting the database for an initial build or major data update operation, use this specifically modified parameters file with a command such as this:
startup pfile = filepath
Make the following changes to the parameters file:
db_cache_size=n
Where: n is 25% of real memory
Example: 128M for 512M of RAM
db_file_multiblock_read_count=n
Where: n is a number based on hardware. The ideal would be multiplier of 8k blocks to equal the disk stripe width.
shared_pool_size = n
Where: n is 10% or less of real memory.
Example: Approximately 10M for 512M of RAM
pga_aggregate_target=n
Where: n is 50% of real memory
Example: 256M for 512M of RAM
parallel_automatic_tuning=true
#parallel_max_servers
Comment out this setting with the # symbol.
#parallel_min_servers
Comment out this setting with the # symbol.
workarea_size_policy=AUTO
disk_asynch_io=true
Session Parameters
In the SQL*Plus® session in which the access structure build scripts will be executed, set the following parameters:
alter session enable parallel query;
alter session enable parallel dml;
alter session set "query_rewrite_enabled"=FALSE;
Access Structure Scripting Package
Refer to the Oracle9i OLAP User's Guide, Part V, for creating and managing tabular summary data structures.
Query Operation Optimizations
init.ora Parameters
For the RDBMS 9.2.0.3 patch set, make the following change to the init.ora parameter file. For additional information on changing the database initialization settings, refer to "init.ora Parameters".
multijoin_key_table_lookup=false
ALTER_SESSION Parameters
Insure that the SYS.OLAP$ALTER_SESSION table is populated with the following settings:
pga_aggregate_target=n
Where: n is 25% of real memory. Increase as needed for larger concurrent user loads.
Example: 128M for 512M RAM
db_file_multiblock_read_count=2
star_transformation_enabled=true
query_rewrite_enabled=true
query_rewrite_integrity=stale_tolerated
optimizer_index_cost_adj=25
#optimizer_mode=all_rows
Uncomment this setting for the RDBMS 9.2.0.2.x patch set
subquerypruning_enabled=true
noor_expansion=true
querycost_rewrite=false
prerewrite_push_pred=true
generalizedpruning_enabled=true
unionrewrite_for_gs=force
The SYS.OLAP_ALTER_SESSION table contents are invoked automatically when an OLAP API client connects to the database. Other clients connecting for querying purposes should set these parameters via the ALTER SESSION command.