ORA-33273: Analytic workspace FPA.FPAPJP has open cursors ... error?

Question

Gurus,
When we try to detach analytic workspace, I get the following error
## Detail 0 ## java.sql.SQLException: ORA-33273: Analytic workspace FPA.FPAPJP has open cursors and cannot be detached.
ORA-06512: at "APPS.FPA_UTILITIES_PVT", line 129 ORA-06512: at "APPS.FPA_PROCESS_PVT", line 4685
ORA-34684: All of your attached analytic workspaces are read-only. Therefore, the UPDATE command will not save changes. ORA-06512: at line 1
The workspace " FPA.FPAPJP" has been opened in read-write mode and no explicit cursors are present in the code.
Any inputs are truly appreciate.
Thanks - Srujan

Answer 1

This is a new error to me. For what it is worth, here is a dba query to list open cursors by session.
select
vses.username||':'||vsst.sid username,
vstt.name,
max(vsst.value) value
from
v$sesstat vsst,
v$statname vstt, 
v$session vses
where
vstt.statistic# = vsst.statistic# and
vsst.sid = vses.sid and
vstt.name in
  ('opened cursors current',
   'opened cursors cumulative') and
  vses.username is not null
group by
vsst.sid,
vses.username,
vstt.name
order by
vsst.sid,
vses.username,
vstt.name
/Here is a query to list all attach aws.
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_nameWas this a one off event or is it happening repeatedly? If it is a one-off, then closing the session or stopping and starting the database instance should resolve the problem.