AW ATTACH

The AW ATTACH command attaches a workspace to your session. Oracle OLAP makes the specified workspace the current one. Previously attached workspaces move down in the list of attached workspaces to make room for the new current one at the top of the list.

When you attach more than one workspace, the code and data in all the attached workspaces are available during your session. The current workspace is first on the workspace list, which Oracle OLAP keeps for your session.

Statement	Description
ACQUIRE	When attached in multiwriter mode, acquires and (optionally) resynchronizes the specified objects so that their changes can be updated and committed.
RELEASE	When attached in multiwriter mode, changes the access mode of the specified variables, relations, valuesets, or dimensions from read/write (acquired) access to read-only access.
RESYNC	When an analytic workspace is attached in multiwriter mode, drops private changes for the specified read-only objects and retrieves the data from the latest visible generations.
REVERT	When attached in multiwriter mode, drops all changes made to the specified objects since they were last updated, resynchronized, or acquired, or since the analytic workspace was attached.

Statement

Description

ACQUIRE

When attached in multiwriter mode, acquires and (optionally) resynchronizes the specified objects so that their changes can be updated and committed.

RELEASE

When attached in multiwriter mode, changes the access mode of the specified variables, relations, valuesets, or dimensions from read/write (acquired) access to read-only access.

RESYNC

When an analytic workspace is attached in multiwriter mode, drops private changes for the specified read-only objects and retrieves the data from the latest visible generations.

REVERT

When attached in multiwriter mode, drops all changes made to the specified objects since they were last updated, resynchronized, or acquired, or since the analytic workspace was attached.

When you attach a workspace, Oracle OLAP looks for and executes the following programs in the order indicated:

Reattaching an attached workspace with a AW ATTACH workspace statement does not cause Oracle OLAP to bring a new copy of the workspace into working memory. Instead, Oracle OLAP takes the following actions:

However, when you have made any changes to data during the session, they are not discarded when you reattach an active workspace. Furthermore, current aliases for the workspace are not changed.

You cannot attach a workspace that is in your schema and whose name is the same as an assigned alias. Similarly, you cannot assign an alias that duplicates the name of an attached workspace that is in your schema. Furthermore, you cannot assign the same alias to two attached workspaces.

In an AW DELETE statement, when you specify a workspace name (for a workspace that is not attached) and the name is the same as an assigned alias, Oracle OLAP interprets the name as an alias and reports an error.

Startup Programs

Assume that you have created an analytic workspace named awtest that contains five programs named PERMIT_READ, PERMIT_WRITE, ONATTACH, MYATTACH, and AUTOGO that have the following definitions.

DEFINE PERMIT_READ PROGRAM BOOLEAN
PROGRAM
SHOW 'permit_read program executing'
AW LIST
RETURN YES
END
 
DEFINE PERMIT_WRITE PROGRAM BOOLEAN
PROGRAM
SHOW 'permit_write program executing'
AW LIST
RETURN YES
END
 
DEFINE ONATTACH PROGRAM BOOLEAN
PROGRAM
SHOW 'onattach program executing'
AW LIST
RETURN YES
END
 
DEFINE MYATTACH PROGRAM BOOLEAN
PROGRAM
SHOW 'myattach program executing'
AW LIST
RETURN YES
END
 
DEFINE AUTOGO PROGRAM 
PROGRAM
SHOW 'autogo program executing'
AW LIST
END

The programs that execute when you attach awtest vary depending on the attachment mode and keywords in the AW ATTACH statement:

When you attach awtest in read/write mode using the following statements.
```
AW DETACH awtest
AW ATTACH awtest RW
```
First the PERMIT_WRITE program executes, and then the ONATTACH program executes.
When you attach awtest in read-only mode using the following statements.
```
AW DETACH axuserwtest
AW ATTACH awtest NOONATTACH RO
```
Only the PERMIT_READ program executes.
When you attach awtest in read-only mode using the following statements.
```
AW DETACH awtest
AW ATTACH awtest RO
```
First the PERMIT_READ program executes, and then the ONATTACH program executes.
When you attach awtest in read-only mode using the following statements.
```
AW DETACH awtest
AW ATTACH awtest ONATTACH myattach RO
```
First the PERMIT_READ program executes, and then the MYATTACH program executes.
When you attach awtest in multi mode using the following statements.
```
AW DETACH awtest
AW ATTACH awtest MULTI
```
First the PERMIT_WRITE program executes, and then the ONATTACH program executes.
When you attach awtest in read-only mode using the following statements.l
```
AW DETACH awtest
AW ATTACH awtest AUTOGO
```
First the PERMIT_WRITE program executes. Secondly, the ONATTACH program executes. Finally, the AUTOGO program executes.

Attaching an Analytic Workspace Using an ONATTACH Program

Suppose you have two workspaces of sales data, one for expenses and one for revenue. You have a third workspace called analysis contains programs to analyze the data. Your analysis workspace has the following ONATTACH program to attach the other two.

DEFINE onattach PROGRAM
PROGRAM
AW ATTACH expenses RW AFTER analysis 
AW ATTACH revenues RW AFTER analysis 
END

To run the ONATTACH program, attach the analysis workspace with the following statement.

AW ATTACH analysis

When you issue an AW LIST statement, you can see from the following output, that all three of your analytic workspaces are attached.

ANALYSIS  R/W CHANGED   XUSER.ANALYSIS
REVENUE   R/W UNCHANGED XUSER.REVENUES
EXPENSES  R/W UNCHANGED XUSER.EXPENSES
EXPRESS   R/O UNCHANGED SYS.EXPRESS