|Oracle® OLAP DML Reference
10g Release 1 (10.1)
Part Number B10339-02
The COMMIT command executes a SQL
COMMIT command. All changes made in your database session are committed, whether they were made through Oracle OLAP or through another form of access (such as SQL) to the database.
When you want changes that you have made in a workspace to be committed when you execute the COMMIT command, then you must first update the workspace using the UPDATE command. UPDATE moves changes from a temporary work area to the database table in which the workspace is stored. Changes that have not been moved to the table are not committed.
The COMMIT command only affects changes in workspaces that you have attached in read/write access mode. After the command returns, all committed changes are visible to other users who subsequently attach the workspace.
When you do not use the UPDATE and COMMIT commands, changes made to an analytic workspace during your session are discarded when you end your Oracle session.
Note:You can detach and reattach a workspace without losing updated changes, even though they are not committed. This is because the detaching and reattaching occur within a single database session.
When you execute a SQL
COMMIT statement in your session outside Oracle OLAP, this statement commits all updated changes in workspaces that you have attached with read/write access.
Many users execute DML statements using SQL*Plus® or OLAP Worksheet. Both of these tools automatically execute a COMMIT statement when you end your session.
When you have attached a shared workspace and another user has read/write access, that user's UPDATE and COMMIT commands do not affect your view of the workspace. Your view of the data remains the same as when you attached the workspace. When you want access to the changes, you can detach the workspace and reattach it.