jods

Getting the following message when trying to run distributions from Super to Super or Super to Sub

*** SYSTEM ERROR RSALOC02 ***

Have tried to up the memory for Compostites and Text Variables from 1GB to 2GB but no good.

Have run Composite Maintenance to reduce size.

We do have text variables without sizes defined - Could this be a potential cause?

Pleeeeassse Heeeelp Meeeeeeeee !!!!!!!!!!

T4molie

Jods,

Can't answer your question but have you thought about trying posting on OTN?

Andy

jods

Yeap and Experts-Exchange for 250 points.

Got the answer in the end...

J4CKO

iTrader: (1)

Was it this ?

Applies to:
Oracle OLAP - Version: 10.1.0.2 to 10.2.0.3
Oracle Warehouse Builder - Version: 10.2.0.1 to 10.2.0.3
This problem can occur on any platform.
Symptoms
When attempting to maintain an OLAP cube that has built in AWM or while loading data in a cube
from OWB, then the following errors occur in the alert.log file:

** OLAP Option logged the following system error
** SYSTEM ERROR RSALOC02 **
** along with process call stack, to tracefile
** e:\oracle\product\10.2.0\admin\dwh\udump\dwh_ora_1 864.trc
Errors in file e:\oracle\product\10.2.0\admin\dwh\udump\dwh_ora_1 864.trc:
ORA-00600: internal error code, arguments: [XSOOPS], [RSALOC02]
Errors in file e:\oracle\product\10.2.0\admin\dwh\udump\dwh_ora_1 864.trc:
ORA-00600: internal error code, arguments: [xsCBTInit00], [0x025A7CC00]
ORA-00600: internal error code, arguments: [XSOOPS], [RSALOC02].
Cause
The xsCBTInit00 means that there is an out of ranspace.
Moreover, the RSALOC02 generally implies that the composite BTREE
(metadata which is kept around for each composite) has grown too large
for its ranspace, a special part of the database. This is a fixed limit
and depends on the density of the data in your composite.
Solution
1) Compress the composites using BTREE64.

For example:

1.1) log in AWM through the olap user owner
1.2) open the Olap Worksheet
1.3) type the following commands:

CONSIDER <composite Name>
CHGDFN <composite Name> BTREE64;

(CONSIDER to make that object definition the current definition)
(CHGDFN command enables you to change certain aspects of the definitions
of analytic workspace objects).

2) Use less dimensions in the composites (meaning that one or more dimensions
of the composite is dense with respect to the others).

3) Reduce the complexity of the dimensions.

Using export and import commands,
then removing the density of the data
(density of the data means that the data are kept space not properly
due they are keeping cells sporadically).

For example:

considering "AWNAME" your AW and "myuser" your user.

3.1) Create a directory object, and grant the privileges with your user
that you are working (i.e.: myuser)

SQL> connect as sysdba
SQL> create directory my_dir as 'D:\temp_aw';
SQL> grant read, write on directory my_dir to myuser;

3.2) Export AW object: AWNAME

login as myuser in sqlplus
set serveroutput on
exec dbms_aw.execute('aw attach AWNAME ro');
exec dbms_aw.execute('limit name to all');
exec dbms_aw.execute('allstat');
exec dbms_aw.execute('export all to eif file ''my_dir/export_file_name.eif'' ');
exec dbms_aw.execute('aw detach AWNAME');

3.4) Drop AW object: AWNAME

exec dbms_aw.execute('aw delete AWNAME');

3.5) Create empty AW object

exec dbms_aw.execute('aw create AWNAME');

3.6) Import data

exec dbms_aw.execute('aw attach AWNAME');
exec dbms_aw.execute('import all from eif file ''my_dir/export_file_name.eif'' ');
exec dbms_aw.execute('update');
commit;
exec dbms_aw.execute('aw detach AWNAME');

jods

We had 7 years of Task Processor history - It just got too much in the end.
Cleared out prior to Jan 07 - sorted.