|Oracle9i OLAP User's Guide
Release 2 (220.127.116.11)
Part Number A95295-02
When using the OLAP Catalog write API, you should be aware of logic and conventions that are common to all the
CWM2 procedure first checks the calling user's security privileges. The calling user must be the entity owner and must have the
OLAP_DBA role. If the calling user does not meet the security requirements, the procedure fails with an exception. For example, if your identity is
jsmith, you cannot successfully execute
CWM2_OLAP_HIERARCHY.DROP_HIERARCHY for a hierarchy owned by
After verifying the security requirements, each procedure checks for the existence of the entity and of its parent entities. All procedures, except
CREATE procedures, return an error if the entity does not already exist. For example, if you call
CWM2_OLAP_LEVEL.SET_DESCRIPTION, and the level does not already exist, the procedure will fail. Similarly, if you call
CWM2_OLAP_MEASURE.SET_DESCRIPTION and the measure exists but the parent cube does not exist, then the procedure will fail.
You can specify arguments to
CWM2 procedures in lower case, upper case, or mixed case.
If the argument is a metadata entity name (for example,
dimension_name) or a value that will be used in further processing by other procedures (for example, the
solved_code of a hierarchy), the procedure converts the argument to upper case. For all other arguments, the case that you specify is retained.
None of the procedures that create, map, and validate OLAP metadata include a COMMIT. Your script should execute all the statements that create and map new metadata, then validate the metadata by calling procedures in
CWM2_OLAP_VALIDATE, and finally do a COMMIT to commit the new metadata to the database.
However, if the metadata is specifically for the OLAPI API, you must refresh the OLAP API Metadata Reader tables after validating the metadata. This procedure,
CWM2_OLAP_METADATA_REFRESH.MR_REFRESH, does include a COMMIT.