![]() Previous |
![]() Next |
The AW DETACH command removes an analytic workspace from the workspace list. When you remove the first workspace, the second workspace becomes the current workspace (unless it is the EXPRESS
workspace). When you detach an analytic workspace, changes that were made before an UPDATE was issued remain in the Database and become permanent with the next COMMIT. When changes were made after the UPDATE was issued, they are discarded.
Note: When a program named TRIGGER_AW exists in the analytic workspace, the execution of an AW DETACH statement automatically executes that program. |
Syntax
AW DETACH [CACHE|NOCACHE] workspace
Parameters
Specifies that the analytic workspace is cached if there have been no changes to it since it was attached. (Default)
Specifies that the analytic workspace is not cached even if there have been no changes to it since it was attached.
Note: You must specify NOCACHE when you detach an analytic workspace if you want Oracle OLAP to execute any Permission, OnAttach, or Autogo programs the next time you attach the workspace in the same session. |
The name of the analytic workspace. You can specify either an analytic workspace name or an analytic workspace alias, depending on the keywords you are using.
Usage Notes
Determining if an Analytic Workspace Has Changed
The following statements indicate if an analytic workspace has been changed while it was attached:
AW function with the CHANGED keyword
AW LIST shows the analytic workspace as unattached.
Cache Size
By default the list of cached analytic workspaces is two. In other words, by default only two analytic workspaces can be on the cached at one time and as new workspaces are added to the cache list, earlier workspaces are removed. For example, assume that you have detached two analytic workspaces in the following order: 1) mywk1
, 2) mywk2
. Now you issue an AW DETACH CACHE command for mywk3
. Oracle OLAP removes mywk1
from the cache and the cache list and caches mywk3
adding it to the cache list after mywk2
.
Note: Under severe memory contention, Oracle OLAP may release memory by emptying the cache. |
You can change the size of the cache by using the event number 37372 where level is the number of analytic workspaces to retain. Specify a level of 1024 to disable the cache entirely. Not determined for beta: Is this information valid to regular developers?
Programs Executed When an Analytic Workspace is Detached
When an analytic workspace is detached, the following programs may execute:
If that analytic workspace being detached contains a program named ONDETACH, the ONDETACH program executes.
If the current analytic workspace is detaching a different analytic workspace and the current workspace contains a program named TRIGGER_AW, then the TRIGGER_AW program executes.
Examples