Refresh Analytic Workspace increase tablespace size ?

Hello, I'm using CWM2 OLAP objects with 9.2.0.6 database version. I have analytic workspaces, too.
I execute refresh of my analytic workspace, using the script generated by Analytic Workspace Manager 9.2.0.4.1. I have noticed that, strangely, whenever I execute the script, it increases the used space of the tablespace containing analytic workspace.
Is this usual ? The script doesn't include new objects, and the effect is the same. What is failing ? I think that this should not happen.
Any idea ? Thanks a lot by your help

vbarres wrote:
if my datawarehouse
grows dinamically (I'm adding new objects every day),
what size has to have my aw tablespace ? It's
difficult to reserve space on disk for this...I'm confused here. Are you really adding new objects every day, or just adding more data to the existing ones. In general, if you are adding more data, the growth should be reasonably predictable, assuming a reasonable AW design. The usual growth confusion has to do with reloading the same data over again, where the growth is unexpected.
rhaug wrote:
I had a similar problem in my AW. The temp and the aw tablespace got ridiculously big. >The temp tablespace exceeded 20gb before the disk got full and everything crashed.
In my case I had made several cubes to perform different tests. When I deleted all but >one cube things behaved more normal and the aggregation time was stable.Again, I'm not sure what is going on here from the descriptions. As far as I know, there should not be a problem with multiple cubes in the same AW. You don't say what version you are in, but is it possibly version 10? I could see some interaction in a parallel build, where the various cubes are built simultaneously, and thus the pages on the free list are necessarily available for reuse when you might want them. More details would be interesting here. You might also try a serial build (I'm not sure where the switch is in AWM, but I'm sure it's there somewhere).

Similar Messages

ORA-01653 unable to increase tablespace size

We have Oracle 11gR2 RAC with ASM installed on Redhat Linux
I am not able to extend tablespace it gives error ORA-01653
I checked ASM views
GROUP_NUMBER     NAME     SECTOR_SIZE     BLOCK_SIZE     ALLOCATION_UNIT_SIZE     STATE     TYPE     TOTAL_MB     FREE_MB
1     DWH_OCR     512     4096     1048576     MOUNTED     NORMAL     3057     2131
2     DATABASE     512     4096     1048576     CONNECTED     NORMAL     204798     1536
Above view shows we have 1536 Mb free in our Database ASM disk group. And when i checked tablespaces used space so i found its not exceeding 70 GB.
Please suggest/advice what can be ocuppying space in ASM? and how to free it?
Also note archiving is also disabled. I tried to empty recycle bin also. Still same issue.
Thanks in advance
Zeeshan Sheikh

select * from DBA_TABLESPACE_USAGE_METRICS;
TABLESPACE_NAME     USED_SPACE     TABLESPACE_SIZE     USED_PERCENT
ESECTOR_DATA     552     4194302     0.013160712
NCC_DATA     1281408     4194302     30.55116203
ODI_DATA     2358040     4194302     56.22008143
QUEST_DATA     184     4194302     0.004386904
SHOAIBA_DATA     50048     4194302     1.193237874
SYSAUX     225720     4194302     5.381586734
SYSTEM     521560     4194302     12.43496534
TEMP     3200     4194302     0.076293982
UNDOTBS1     160     4194302     0.003814699
UNDOTBS2     16552     4194302     0.39463062
USERS     3337400     4194302     79.56985453
WSECTOR_DATA     192     4194302     0.004577639
select * from v$asm_diskgroup;
GROUP_NUMBER     NAME     SECTOR_SIZE     BLOCK_SIZE     ALLOCATION_UNIT_SIZE     STATE     TYPE     TOTAL_MB     FREE_MB     HOT_USED_MB     COLD_USED_MB     REQUIRED_MIRROR_FREE_MB     USABLE_FILE_MB     OFFLINE_DISKS     COMPATIBILITY     DATABASE_COMPATIBILITY     VOTING_FILES
0     FLASH     512     4096     0     DISMOUNTED          0     0     0     0     0     0     0     0.0.0.0.0     0.0.0.0.0     N
1     DWH_OCR     512     4096     1048576     MOUNTED     NORMAL     3057     2131     0     926     310     910     0     11.2.0.0.0     10.1.0.0.0     N
2     DATABASE     512     4096     1048576     CONNECTED     NORMAL     204798     1536     0     203262     0     768     0     11.2.0.0.0     10.1.0.0.0     N

Increasing tablespace quota

Hi
i have a requirement in which i need to increase tablespace size for my schema. actually the tablespace that is given to me is shared by many other 'owners' too but i want the datasize just for me to be increased.
SELECT OWNER,TABLESPACE_NAME,SUM(BYTES/1024/1024) "Allocated Size in MB"
FROM DBA_SEGMENTS WHERE TABLESPACE_NAME = 'DATA_TS1'
GROUP BY OWNER,TABLESPACE_NAME ORDER BY OWNER;
will give this result
OWNER | TABLESPACE_NAME| Allocated Size in MB
30026882 | DATA_TS1 | 170.9375
30042534 | DATA_TS1 | 0.1875
myself | DATA_TS1 | 106951.875
now how can i just increase quota for 'myself'?
Can this be done? and if so can you plz provide me with syntax?

Hi,
974647 wrote:
SELECT OWNER,TABLESPACE_NAME,SUM(BYTES/1024/1024) "Allocated Size in MB"
FROM DBA_SEGMENTS WHERE TABLESPACE_NAME = 'DATA_TS1'
GROUP BY OWNER,TABLESPACE_NAME ORDER BY OWNER;
will give this result
OWNER | TABLESPACE_NAME| Allocated Size in MB
30026882 | DATA_TS1 | 170.9375
30042534 | DATA_TS1 | 0.1875
myself | DATA_TS1 | 106951.875That's showing you the space already being used. The quotas for each user are obviously at least that large, but the query above doesn't say anything more about quotas. Query dba_ts_quotas to see the quota information.
now how can i just increase quota for 'myself'?
Can this be done? and if so can you plz provide me with syntax?
ALTER USER myself QUOTA x M ON data_ts1;where x is the new number of megabytes.
There is no way to guarantee that other users won't use the newly created space if they have sufficiently large quotas. If you want to make some space available only to a given user, then you need a tablespace where nobody except that user has a quota.

SYSAUX tablespace increasing in size

Hi,
I have noticed that SYSAUX tablespace increasing in size. This tablespace is being used by the below components. However, none of those components are used by my applications. They are installed by default with Oracle 10g Realese1. what makes this tablespace increase?? and what should be done to stop increasing in this tablespace?
Oracle Ultra Search 10.1.0.3.0 VALID WKSYS
Oracle Enterprise Manager 10.1.0.3.0 VALID SYSMAN
Oracle XML Database 10.1.0.3.0 VALID XDB
OLAP Catalog 10.1.0.3.0 VALID OLAPSYS
Oracle Text 10.1.0.3.0 VALID CTXSYS
Spatial 10.1.0.3.0 VALID MDSYS
Oracle interMedia 10.1.0.3.0 VALID ORDSYS
Oracle Expression Filter 10.1.0.3.0 VALID EXFSYS
Oracle Workspace Manager 10.1.0.2.0 VALID WMSYS
Oracle Data Mining 10.1.0.3.0 VALID DMSYS

The following is from a metalink post of mine on the same subject>>
The sysaux tablespace is used to hold AWR data among other uses. Reduce the retention and interval setting for the AWR snapshots to reduce the space necessary to hold the data. See dbms_workload_repository package procedure modify_snapshot_settings.
Your statistics collection level will also feed into the above.
Take a look at other features/products you have assigned to sysaux if any and examine the data collection and retention rules you have specified for them.
<<
HTH -- Mark D Powell --

How to increase page size for balance file upload in Workspace.

Hi All,
Please suggest how to increase page size for balance file upload in shared Workspace pages.
Thanks,

A word of caution is in order regarding changing from facing to non-facing and back again. If you have overridden master page items, you'll get a second, non-overridden copy on all the even-number pages when that half of the master page is re-applied. This applies to master text frames which override automatically when text flows into them as well as to objects you manually override. I think you'll find this particular technique also only works for master text frames, whereas the Layout Adjustment should work in all situations where frames snap to guides.

Analytic Workspaces and Database Tablespace

Hi,
I am trying to understand the intricacies in the setup of Analytic Workspaces and their corresponding tablespaces in the database, and here is the background:
I created an Analytic Workspace, say AW1 in a database that had a tablespace, say TS1. After sometime, I created another Tablespace, TS2 in the same database and using the same schema as before, created an Analytic Workspace, AW2 in TS2.
However, AW2 seems to get created in TS1 even though I select TS2 explicitly at the time of creating AW2. Also, if I drop an AW created using TS2 and then import it again (in the same schema) from the template, it gets created in TS1 and not TS2 as I would expect.
In essence, it seems to me that all AWs get created in the TS that was the first TS of my database (TS1 in this case), irrespective of the fact that I created them in different Tablespaces. Also, for all these experiments, the database and the environment is the same.
Can anyone please explain this behavior?
For reference, the database in use is Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production With the Partitioning, Oracle Label Security, OLAP and Data Mining Scoring Engine options
and the AWs have been created using Oracle Analytic Workspace Manager (AWM) v10.2.0.3.0A.
Any help is much appreciated.
Thanks and Regards,
Piyush

Hi Piyush,
AWM lets you specify the tablespace for your AW which allows you to override the default tablespace for the user. However, this information is not recorded in the XML template. Therefore, if you create an AW in a non-default tablespace, save the definition to an XML template, drop the AW and use the XML template to rebuild the AW then the AW will get created in the default tablespace.
There are two workarounds to this (that I can think of)
1) Use a script to rebuild the AW from the XML template and alter the users default tablespace as part of the script and then set it back after the AW has been built.
2) Use the AW Create packages that do allow you to specify the tablespace for the AW, run the DML command to create the standard form metadata and then script the loading of the XML definitions for each dimension and all your cubes.
Hope this helps
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Increase the size of tablespace

what is the sqlplus command to change the size of existing tablespace?
Tablespace is USERS, I need to increase the size of table space.

Hi,
>>Do I need to increase the size of both tablespace & datafile?
Remember: Oracle stores data logically in tablespaces and physically in datafiles associated with the corresponding tablespace. In resume, you can alter the size of a datafile.
ALTER DATABASE DATAFILE '/u03/oradata/users01.dbf' RESIZE 5000M
>>/u03/oradata/users01.dbf not a USERS01.ORA
The name of the datafiles depends of notation that a DBA are using.
Cheers

Increase the size to tablespace

Can any one forward me the SQL/PLSQL command to increase the size of tablespace.

Hi,
TEST>SELECT FILE_NAME, BYTES/1024/1024 "MiB" FROM DBA_DATA_FILES
2 /
FILE_NAME                                 MiB
/path/redo/dbs.dbf                       1500
/path/data/datbig04.dbf                 15360
/path/data/datbig05.dbf                 15360
/path/data/datbig06.dbf                 15360
/path/index/idxbig01.dbf                24576
/path/index/idxbig02.dbf                24576
/path/index/idxbig03.dbf                24576
36 rows selected.Try to describe DBA_DATA_FILES in order to know what info you can get in it.
Regards,
Yoann.

How to get last time when tablespace size increase

Hi all,
I need last date and time when tablespace size was extended. Kindly tell me is there any query which can help me.
Thanks

possible if you've 10g database and holding license to use AWR.
table name is dba_hist_tbspc_space_usage
SELECT TO_CHAR (sp.begin_interval_time,'DD-MM-YYYY') days
, ts.tsname
, max(round((tsu.tablespace_size* dt.block_size )/(1024*1024),2) ) cur_size_MB
, max(round((tsu.tablespace_usedsize* dt.block_size )/(1024*1024),2)) usedsize_MB
FROM DBA_HIST_TBSPC_SPACE_USAGE tsu
, DBA_HIST_TABLESPACE_STAT ts
, DBA_HIST_SNAPSHOT sp
, DBA_TABLESPACES dt
WHERE tsu.tablespace_id= ts.ts#
AND tsu.snap_id = sp.snap_id
AND ts.tsname = dt.tablespace_name
AND ts.tsname NOT IN ('SYSAUX','SYSTEM')
GROUP BY TO_CHAR (sp.begin_interval_time,'DD-MM-YYYY'), ts.tsname
ORDER BY ts.tsname, days;http://maxwellmiranda.wordpress.com/2011/03/22/segmenttablespace-growth-details-script/

Are Analytic Workspaces suitable for very large data sets?

Hi all,
I have made many different tests with analytic workspaces and i have used the different features (compression,composites...). The results especially for maintenance are disappointing.
I have a star schema with 6 dimensions. The fact table has 730 million rows, the first dimension has 2,9 million rows and the other 5 dimensions have between 25 and 300 rows each.
My conclusion is that Analytic Workspaces don't help in situations like mine. The time for maintenance is very very bad not to mention the time for aggregations. I even tried to populate the cube in parts( 90 million rows for the first population) but nothing change. And there are some other problems with storage and tablespaces ( I always get the message unable to extent TEMP tablespace. The size of it is 54Gb).
Is there something i missing? Has anyone similar problem or different opinion?
Thank you,
Ilias

A few other tips to add to Keith's excellent advice:
- How many CPU's does your server have? The answer to this may help you decide the optimal level to partition at (in my experience DAY is too low and can cause different problems). What other levels does your time dimension have? Are you loading your cubes in parallel?
- To speed up your load, partition your underlying fact table with the same granularity as your cubes and place an index on the field mapped to the partition dimension
- Are you using 10.2.0.3? If so, be very careful with the storage data type you choose when creating your cubes. The default in 10.2.0.3 is NUMBER which has the capability of storing data to 38 significant figures. This usually exceeds what is required for most datasets. If your dataset allows you to use storage of 15 significant figures then you should create your cubes using the DECIMAL data type instead. This will use about one third of the storage space and significantly increase your build speeds (in my experience, more than 3 times faster)
- Make sure you have preallocated enough permanent and temporary tablespaces for your build. Autoextending can be very time consuming.
- Consider reducing the amount of aggregation you do in batch. It should not be necessary to pre-aggregate everything in order to get good query performance.
Generally, I would say that the volume should not be a problem. A single dimension with 2.9 million values is fairly big and can be slow (in OLAP terms) to query but that should not be an obstacle to building it in the first place.
Good luck!
Stuart

ORA-34492: Analytic workspace object cubename _STORED does not exist.

I am having issues accessing cube data from a user other than where the AW was built.
Following is what I have done in User-1:
1. Create two AW's in User-1 : AW-1 and AW-2.
2. Create all objects in these two AW's
3. AW-2 is dynamically attached on attaching AW-1 by using PERMIT startup programs. Please refer Attaching multiple AW's
4. Refreshed both AW's to load data
5. ALLCOMPILE - no errors.
6. Created some SQL views on User-1 which basically query the underlying cube views. I also have some queries using the olap_table option.
7. All my querries work fine in User-1. I can access data from AW-1 and AW-2.
However, we give access to the above SQL views through an abstract user: User-abs. In 10g, all we did was grant select privs to all the User-1.AW$ tables and also on all the sql views. This would let User-abs get data from the cubes in User-1.
I am not able to get User-abs to do the same in 11g. We encounter an error mentioning that the workspace object <cubename>_STORED does not exist. The cubename it is referring to exists in AW-2.
I granted select privs on all AW$ tables, dimension views, cube views and the abstracted sql views but the error persists.
I tried searching this forum but could not find any helpful leads. Any help will be greatly appreciated.
Thanks!
Database - 11.2.0.1
AWM - 11.2.0.2.0A

I can think of two possible problems. First, you may not be properly qualifying the owner name when you refer to the object. This can be important when refering to objects owned by other schemas. For example instead of 'my_cube_stored' you would say 'user-1.aw-2!my_cube_stored'. You should also be careful about the order in which you attach the AWs. Do you want AW-2 attached first or last? Use the LAST keyword on AW ATTACH to control this.
Another possibility is that you have added additional logic to PERMIT_READ over and above the 'aw attach' comand. I was able to recreate the error with the following code in a new AW called TEST_AW in the GLOBAL schema.
DEFINE PERMIT_READ PROGRAM BOOLEAN
PROGRAM
aw attach global.global
show global.global!units_cube_stored
return true
ENDAttaching TEST_AW in RO mode as any user gives me the following error.
ORA-34492: Analytic workspace object GLOBAL.GLOBAL!UNITS_CUBE_STORED does not
exist.
ORA-06512: at "SYS.DBMS_AW", line 93
ORA-06512: at "SYS.DBMS_AW", line 122
ORA-06512: at line 1Here is the documentation for PERMIT_READ
>
PERMIT_READ
A PERMIT_READ program is a program that you can create and that Oracle OLAP checks for by name when an AW ATTACH read-only command executes. Depending on the value returned by the program, Oracle OLAP executes the code within the program after attaching the analytic workspace. Depending on the statements in the permit_read program the user is granted or denied access to specific objects or sets of object values. Within permit_read program, you can specify PERMIT commands that grant or restrict access to individual workspace objects. All of the objects referred to in a given permit_read must exist in the same analytic workspace.
>
Note, especially, the restriction in the last sentence. This means that a PERMIT_READ program in AW1, for example, cannot refer to objects in AW2. So this is why my PERMIT_READ doesn't work. The AUTOGO does not have these restrictions, but as we know from the forum post you cited, AUTOGO is broken in 11.2.0.1. You can move forward to 11.2.0.2 where AUTOGO is fixed, but there is workaround, which is to add a PERMIT_READ program to the second AW to do the work. For example, if I add this PERMIT_READ to GLOBAL and remove the 'show' command from the PERMIT_READ in TEST_AW, then everything works as expected.
DEFINE PERMIT_READ PROGRAM BOOLEAN
PROGRAM
if aw(attached 'test_aw')
then do
show global.global!units_cube_stored
doend
return true
END

How to increase the size of sort_area_size

How to increase the size of sort_area_size and what size should be according to the PROD database
Thanks

user10869960 wrote:
Hi,
Many Thanks Charles
Oracle does not recommend using the SORT_AREA_SIZE parameter unless the instance is configured with the shared server option. Oracle recommends that you enable automatic sizing of SQL working areas by setting PGA_AGGREGATE_TARGET instead. SORT_AREA_SIZE is retained for backward compatibility."
--How can i know the instance is configured with the shared server option or not?This might be a tough question to answer. A shared server configuration may be enabled, but the clients may still connect using dedicated sessions, in which case PGA_AGGREGATE_TARGET would still apply.
From
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_2088.htm
V$SESSION includes a column named SERVER which will contain one of the following for each of the sessions: DEDICATED, SHARED, PSEUDO, or NONE. As a quick check, you could query V$SESSION to see if any sessions are connected using a shared server connection.
From:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm
There are several parameters which are used to configure shared server support, as well as several views to monitor shared server.
As Robert mentioned, when the WORKAREA_SIZE_POLICY is set to AUTO, the SORT_AREA_SIZE setting is not used, unless a shared server configuration is in use.
--What default value is WORKAREA_SIZE_POLICY and SORT_AREA_SIZE ?From:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams157.htm
"Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO. This means that SQL working areas used by memory-intensive SQL operators (such as sort, group-by, hash-join, bitmap merge, and bitmap create) will be automatically sized. A nonzero value for this parameter is the default since, unless you specify otherwise, Oracle sets it to 20% of the SGA or 10 MB, whichever is greater."
Actually I am facing performence issue since long time till now i did not get the solution even i have raised SRs but i could not.When the issue occur system seems hang.what i monitored whenever hdisk0 and hdisk1 use 100% the issue occur.
Regards,
SajidWhen you say that you have had a performance issue for a long time, is it a performance problem faced by a single SQL statement, a single user, a single application, or everything on the server? If you are able to identify a single user, or SQL statement that is experiencing poor performance, I suggest starting with a 10046 trace at level 8 (wait events) or level 12 (wait events and bind variables) to determine why the execution appears to be slow. If you have not yet determined a specific user or SQL statement that is experiencing performance problems, you might start with either a Statspack Report or an AWR Report (AWR requires a separate license).
If you believe that temp tablespace usage may be a contributing factor to the performance problem, you may want to periodically run this query, which will indicate currently in use temp tablespace usage:
{code}
SELECT /*+ ORDERED */
TU.USERNAME,
S.SID,
S.SERIAL#,
S.SQL_ID,
S.SQL_ADDRESS,
TU.SEGTYPE,
TU.EXTENTS,
TU.BLOCKS,
SQL.SQL_TEXT
FROM
V$TEMPSEG_USAGE TU,
V$SESSION S,
V$SQL SQL
WHERE
TU.SESSION_ADDR=S.SADDR
AND TU.SESSION_NUM=S.SERIAL#
AND S.SQL_ID=SQL.SQL_ID
AND S.SQL_ADDRESS=SQL.ADDRESS;
{code}
The SID and SERIAL# returned by the above could then be used to enable a 10046 trace for a session. The SQL_ID (and CHILD_NUMBER from V$SESSION in recent releases) could be used with DBMS_XPLAN.DISPLAY_CURSOR to return the execution plan for the SQL statement.
You could also take a look in V$SQL_WORKAREA_ACTIVE to determine which, if any, SQL statement are resulting in single-pass, or multi-pass executions, which both access the temp tablespace.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

How to increase the size of attachments?

When I try to upload a file over 2mb, the following error occurs:
Task failed.
Caused by: Task '0' in activity '/PlanejamentoDeVenda#Default-1.0/Interactive[DefinicaoDoMetodoDeEntrada]' for instance '/PlanejamentoDeVenda#Default-1.0/3/0' could not be successfully executed. The task failed while executing method 'JSP_Router'.
Caused by: The method 'JSP_Router' from class 'xobject.Fuego__AutoGen__Screenflows__.__ImportacaoDaPlanilha' could not be successfully executed.
Caused by: Process execution engine execution error.
Caused by: The task could not be successfully executed.
*Reason: 'fuego.server.exception.AttachmentMaxSizeExceededRuntimeException: Attachment max size is exceeded. Max size = '2097152'. Current file size = '5654528'.'.*
*Caused by: Attachment max size is exceeded. Max size = '2097152'. Current file size = '5654528'.*I have added to workspace.properties a new value for entry fuego.workspace.servlet.Attachment.MAX_ATTACHMENT_SIZE such as: 11309056, but the error continues.
Have also tried to put in the BPM Object that represents the file as separated but the problem also remains.
Someone would tell me how can I increase this size?

duplicated.
Edited by: krock on Jan 15, 2009 12:33 PM

How can i increase the size of MBUF in SAP

how can i increase the size of MBUF. anyone plz help me

HI Zahid,
What do you mean increase size of MBUF
Is this a table ?
if yes then you need to extend the tablesapce of table MBUF, no the table.
using brtools you can extend the tablespace.
Regards,
Fendi

Cannot drop cube or analytic workspace due to ORA-37409

The error is ORA-37409: cannot delete or truncate AW used by CUBE ORGANIZED table.
This seems very closely related to the bug discussed in this thread: Drop cube organized table
We need to drop and rebuild a cube due to a design change. It looks like there are some CR$ tables related to the cube preventing the drop.
We cannot drop the CR$ table, nor can we drop the cube, nor can we drop the analytic workspace. We have tried disabling materialized view refresh on the cubes (which works but leaves the CR$ tables out there). We have tried the drop using dbms_aw.aw_delete and with dbms_cube.import_xml (to remove everything). No such luck.
Is there a workaround you can give me that will allow us to drop the CR$ tables? Or a workaround that will allow us to drop the workspace?

Update:
Our last attempt to drop the analytic workspace did remove almost all OLAP metadata. However, there were still rows in sys.olap_tab$ with object IDs relating the problem CR$ tables. In a test database, we confirmed that deleting these rows does allow us to drop the CR$ tables that cannot otherwise be dropped. However, running DML against a sys-owned table like this is unwise at best, and certainly an unsupported workaround (unless we can get Oracle's blessing to do it).
We may go through MOS and see if Oracle can provide a one-off patch for the bug listed above, to correct this situation. Or perhaps they may be able to provide some other direction.
This puts us in a situation where our only immediate option may be to uninstall the OLAP option and reinstall it.

Refresh Analytic Workspace increase tablespace size ?

Similar Messages

Maybe you are looking for