Workspace could not be attached

Question

Hi All ,
I executed below:
exec DBMS_CUBE.BUILD('NN_OLAP_POC.MARKET_SALES_CUBE, NN_OLAP_POC.BRAND_SALES_CUBE', parallelism=>2) ;
and it fails with :
ERROR at line 1:
ORA-37162: OLAP error
XOQ-01707: Oracle job "JOB$_196" failed while executing slave build
"NN_OLAP_POC.MARKET_SALES_CUBE USING (LOAD NO SYNCH, SOLVE) AS OF SCN 31840126"
with error "37162: ORA-37162: OLAP error
XOQ-01600: OLAP DML error "ORA-4030: out of process memory when trying to
allocate 14083672 bytes (xsCCube,xsCCube_1)" while executing DML
"SYS.AWXML!R11_AGGREGATE_CONSISTENT('MARKET_SALES_CUBE.CUBE'
'MARKET_SALES_CUBE.SOLVE.AGGREGATIONDEFINITION'
SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'P59')"
ORA-06512: at "SYS.DBMS_CUBE", line 236
ORA-06512: at "SYS.DBMS_CUBE", line 305
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_CUBE", line 236
ORA-06512: at "SYS.DBMS_CUBE", line 280
ORA-06512: at line 1
Now I am not being able to attach the AW in REad Write mode and I believe that has been locked by the AWM itself and I need to bounce the database to remove the lock .
Can you please point out the reason of the failure and even if failed AW should release the lock which is not the case now .
Thanks in advance ,
DxP

Answer 1

The session that had attached the AW in RW mode is probably still alive, which means the AW cannot be attached RW by any other session. This may have sorted itself out by the time you read this, but if not, then run the following as DBA.
set pages 500 lines 110
col usn format a23 heading "USER (SID,SERIAL#,SVR)"
col aw format a22 heading "OLAP AW (ATTACHED)"
col generation format 99999 heading "Genrtn"
select
  username || ' ('||sid||','||serial#||','||
  decode(server,
    'DEDICATED','D',
    'SHARED', 'S', 'U')||')' usn,
    gvawo.inst_id,
    owner||'.'||daws.aw_name||' ('||
     decode(attach_mode,
     'READ WRITE', 'RW',
     'READ ONLY', 'RO',
     'MULTIWRITE', 'MW',
     'EXCLUSIVE', 'XW', attach_mode)||')' aw,
  generation
from
  dba_aws daws,
  gv$aw_olap gvawo,
  gv$aw_calc gvawc,
  gv$session gvses
where
  daws.aw_number = gvawo.aw_number
  and sid = gvawo.session_id
  and gvawc.session_id = sid
  and gvawo.inst_id = gvawc.inst_id
  and gvses.inst_id = gvawc.inst_id
order by
  username,
  sid,
  daws.aw_name
/This will list all the attached AWs and the sessions that own them. Similar information can be obtained from AWM using the node 'Reports->OLAP DBA Reports->AWs Attached'.
Here is a sample output.
USER (SID,SERIAL#,SVR)        INST_ID OLAP AW (ATTACHED)       Genrtn
GLOBAL (16,357,D)           1 SYS.AWXML (RO)            2
GLOBAL (16,357,D)           1 SYS.EXPRESS (RO)            2
GLOBAL (101,4017,D)           1 SYS.EXPRESS (RO)            2
SCOTT (18,599,D)           1 SYS.EXPRESS (RO)            2
SCOTT (18,599,D)           1 GLOBAL.GLOBAL (RW)            0As you can see, user SCOTT has the AW named 'GLOBAL' attached in RW mode. I can kill the session using
alter system kill session '18,599';