|Oracle® OLAP Application Developer's Guide
10g Release 1 (10.1)
Part Number B10333-02
This appendix provides upgrade instructions and identifies some of the major differences between Oracle Express Server 6.3 and Oracle OLAP. It is intended to provide a frame of reference to help you understand the material presented in this guide.
This appendix includes the following topics:
Oracle OLAP is installed as an option in Oracle Enterprise Edition, and it is now integrated with Oracle Database. While Express Server runs in a service environment, Oracle OLAP runs within the Oracle kernel.
In Oracle, the term database refers only to the relational database. An Express database is now called an analytic workspace. In Oracle OLAP, an analytic workspace can be used either as a transient data cache or as a persistent data repository. A persistent analytic workspace is stored as a LOB in a relational table, which in turn is stored in a tablespace. There are no "
The administrative tasks for Oracle OLAP are merged with the database tool set.
Oracle Enterprise Manager encompasses the tools for administering Oracle databases, providing a common user interface across all platforms. Performance data for OLAP can be collected in system tables the same as any other Oracle database performance statistics. Oracle Enterprise Manager provides a graphical interface to SQL. Because OLAP now runs within the Oracle Database kernel, many of the basic administrative tasks (such as starting, stopping, and configuring the process) are subsumed into database management.
Analytic Workspace Manager is the tool for creating and managing analytic workspaces.
Oracle OLAP does not use operating system identities, except for the installation user under whose identity Oracle Database is installed. You can delete other operating system identities created for use by Express Server (such as the DBA user, the Initialize user, the Default user, and individual user names) if they have no other purpose.
All authentication is performed by Oracle Database. Applications must always present credentials before opening a session, and those credentials must match a user name and password stored in the relational database. Before users can access Oracle OLAP, you must define user names and passwords in the database.
For users to access operating system files, they must have access rights to a directory object that is mapped to the physical directory path. This access is granted either to an individual user ID or to a database role.
See Also:Chapter 12 for more information about OLAP administration tasks
An Oracle OLAP session is always connected to the database. You do not open a connection with the database as a separate or optional step.
You can copy data between an analytic workspace objects (such as variables and dimensions) and relational tables in the following ways:
A PL/SQL package named
DBMS_AWM provides procedures for creating an analytic workspace from relational tables. Analytic Workspace Manager provides a graphical interface to this package.
The OLAP DML
SQL command fetches data into dimensions and variables for further manipulation. A new SQL
IMPORT command facilitates bulk data transfer from relational tables into the analytic workspace, and a new SQL
INSERT DIRECT command facilitates data transfer from the analytic workspace into relational tables.
Using SQL table functions, it is now possible for a SQL-based application to manipulate and extract data from an analytic workspace. Express Server did not permit a data transfer to be initiated externally. Analytic Workspace Manager provides a graphical interface to the
The Express Server language support has been replaced by Oracle Globalization Technology, which provides more extensive localization support and is much easier to administer than the localization features of Express Server. Oracle Database and Oracle OLAP use the same character set, which is selected during installation.
If you are upgrading Express databases that use translation tables, then you can delete those tables because they are not needed by Oracle OLAP. Likewise, you should check your Express programs for use of obsolete commands and keywords that supported translation tables. Support for Globalization Technology has been added to the OLAP DML. These options enable an application to query the current localization settings and override the behaviors controlled by the default language and territory.
Table B-1 identifies the Unicode character sets available in Oracle that are equivalent to the Express Server character sets. If you plan to import Express databases or to use Oracle OLAP to access multibyte data in external files, then you might find this information helpful in identifying an appropriate database character set. Note that the Express
CHARSET option is now obsolete.
Oracle OLAP enables applications to access its multidimensional data directly through either a Java API or SQL. Express SPL programs can be executed using either programming method. Be sure to review all SPL programs to remove commands that are no longer available and to take advantage of new functionality.
Analytic Workspace Manager provides wizards for creating a database standard form analytic workspace from relational tables, aggregating the data, and enabling the workspace for access by the BI Beans or Oracle Discoverer. Enablement involves generating relational views of data stored in an analytic workspace, and creating metadata for those views that is in the appropriate type for the application.
You cannot run Windows C++, HTML, or Java applications that were developed for use with Express Server.
See Also:Chapter 6 for methods of creating standard form analytic workspaces from data in relational tables
OLAP Worksheet provides an interactive environment for developing stored procedures in either the OLAP DML or SQL. The PL/SQL
DBMS_AW procedure executes OLAP DML commands from a SQL environment.
Oracle OLAP provides communications through Oracle Call Interface (OCI) and Java Database Connectivity (JDBC).
The BI Beans can query data that is stored either in an analytic workspace or in relational tables. The database administrator defines OLAP Catalog metadata for both types of data source. The metadata is stored in tables and views.
Database standard form is a type of metadata stored in analytic workspaces for use by the server tools provided in Analytic Workspace Manager. This metadata is stored in properties on workspace objects and in catalogs, which are implemented as special dimensions, variables, and valuesets.
Oracle Express Administrator is not available in Oracle OLAP, and the Oracle Express Objects metadata that it generated is not used by the BI Beans.
Support in the following areas has been added to the OLAP DML:
ROLLUPcommand are still available, but composite dimensions and aggmaps are strongly recommended instead, because they are easier to manage and perform better.
See Also:OLAP DML Reference for comprehensive lists of new, obsolete, and significantly revised commands
UPDATE command moves analytic workspace changes from a temporary tablespace to a permanent tablespace. Your changes are not saved permanently until you execute a
COMMIT command, either from your Oracle OLAP session or from SQL. A
COMMIT writes the permanent tablespace to disk.
Changes that have not been moved to the permanent tablespace are not committed. If you issue a
COMMIT without first updating your analytic workspace, then no changes to the analytic workspace that you made after your last
UPDATE are committed to disk.
COMMIT command executes a SQL
COMMIT command. All changes made during your session are committed, whether they were made through Oracle OLAP or through another form of access (such as SQL) to the database.
EIF files are used to transfer the contents of an analytic workspace from one database to another and to upgrade from an Express database. You can create an analytic workspace from an Express database simply by using EIF files to transfer the objects.
The more complex task is to create an analytic workspace in database standard form, so that you can use the current generation of Oracle OLAP tools. You may be able to leverage your investment in Express metadata to create standard form metadata. Otherwise, you must define a new logical metadata model.
If your Express database contains Oracle Express Objects metadata (that is, it was created by Oracle Express Administrator), then you can use a conversion program named
CREATE_DB_STDFORM. Without Oracle Express Objects metadata,
CREATE_DB_STDFORM cannot generate sufficient standard form metadata for the OLAP tools to work.
Especially if your source data is in flat files, then use
CREATE_DB_STDFORM if possible. There are no tools currently available for creating a standard form analytic workspace directly from flat files.
If your source data is in tables or views, then you have a choice of using
CREATE_DB_STDFORM to convert an Express database, or using other tools to create an analytic workspace directly from the source data.
CREATE_DB_STDFORM enables you to use your Oracle Express Objects metadata instead of redefining the logical model in the OLAP Catalog. However, you must perform other steps manually, as described in "What CREATE_DB_STDFORM Does Not Do For You". You can choose which method best suits your needs.
Table B-2 identifies the upgrade options.
Table B-2 Choosing an Upgrade Path for Express Databases
|If you have Oracle Express Objects metadata...||And your source data is located in...||THEN create a standard form analytic workspace using...|
|Yes||Tables or views|
|No||Tables or views||One of the methods described in Chapter 6.|
|No||Flat files||Oracle Warehouse Builder as described in Chapter 6, or the method described in Chapter 11.|
CREATE_DB_STDFORM enables you to start using the BI Beans against your data in a matter of minutes. The conversion step from Oracle Express Objects metadata to database standard form metadata involves running a single program. You can then enable the analytic workspace for the BI Beans using a dialog in Analytic Workspace Manager. The entire process, from importing the EIF file to querying views of the analytic workspace using a BI Beans application, is very quick and fully automated.
If you load data only at the base level, then you can use the Aggregation wizards in Analytic Workspace Manager to create and deploy an aggregation plan. This method of aggregation is faster and more flexible than the
The conversion process circumvents the usual first step in creating an analytic workspace: developing a logical data model in the OLAP Catalog and mapping the logical objects to the data source. In this usual scenario, if you want to modify the logical model, you modify the OLAP Catalog; the tools make the appropriate changes to the standard form catalogs by refreshing them from the OLAP Catalog. This maintenance process is not available to analytic workspaces converted by
CREATE_DB_STDFORM. Thus, you must do the following tasks manually:
If you want to perform time-based analysis on your data, you must identify all time dimensions and populate end date and time span attributes before using
CREATE_DB_STDFORM. A sample program is provided in this appendix.
Your analytic workspace may contain programs with references to obsolete commands. You must revise them. You may also want to use some of the new features. For example, you can handle sparse data with composites (instead of conjoints) if you are not doing so already. You must define new variables and copy the data from the old variables (or reload it from the data source) to make this change.
You cannot use the Refresh Wizard in Analytic Workspace Manager to copy new data into a converted analytic workspace. Instead, you must modify the load programs or create new ones, and run them manually.
You must make any changes to the standard form metadata manually using the
MAINTAIN command and qualified data references.
The Oracle Express Objects conversion tool operates on an analytic workspace. It uses the Oracle Express Objects metadata to identify the roles of various objects, and then does the following:
Populates existing objects with the appropriate standard form properties. For example, the Oracle Express Objects language dimension is given the
AW$ROLE value of
Creates new standard form objects with the dimensions and properties required by standard form, and copies the data from existing objects into it. For example, standard form attributes are dimensioned by the hierdim dimension and Oracle Express Objects attributes are not. In an
XADEMO analytic workspace, the conversion tool creates a variable named
CHANNEL_LONG_DESCRIPTION dimensioned by
_XA_LANGDIM, and populates it with values from
Creates and populates standard form metadata objects, such as the standard form catalogs, member_gid and member_inhier variables, and member_familyrel and member_levelrel relations. For descriptions of these standard form objects, refer to Appendix A.
The conversion tool adds standard form objects and properties; it does not delete any Oracle Express Objects objects or properties. You can delete them manually if you wish.
The BI Beans requires a level-sorted Time dimension with period end dates and time span attributes in order to support time-based analysis.
CREATE_DB_STDFORM program runs the Oracle Express Objects conversion tool. It has this syntax:
CREATE_DB_STDFORM(aw, [mode], [debug], [directory], [filename], [metacheck])
aw is the name of the analytic workspace (TEXT)
mode is the attachment mode (RO | RW | RWX)
debug controls whether the debugger runs (YES | NO)
directory is a database directory where the debug file is written (TEXT)
filename is the name of the debug file (TEXT)
metacheck controls whether a metadata check precedes the conversion (YES | NO)
For example, the following command attaches
XADEMO in read/write mode, verifies that the Oracle Express Objects metadata is complete, converts the analytic workspace to standard form, and sends status messages to the screen:
The next command attaches
XADEMO in read/write exclusive mode and redirects the status messages to a file named
xademo.log in a database directory named
xademo_dir. It also performs the metadata check.
CALL CREATE_DB_STDFORM('xademo', 'rwx', yes, 'xademo_dir', 'xademo.log')
Most of the steps for converting to standard form (such as creating a new analytic workspace and importing the EIF file) can be done using the Object View in Analytic Workspace Manager. However, this procedure uses the command-line interface provided by OLAP Worksheet, on the basis that users making this conversion are already familiar with OLAP DML commands.
Follow these steps to use the Oracle Express Objects metadata conversion tool to create a standard form analytic workspace.
Create an EIF file from your Oracle Express Objects database, and copy the file to a physical directory that is mapped to a database directory.
For information about database directories, refer to Permitting Access to External Files.
Open Analytic Workspace Manager and attach to Oracle Database, as described in "Introduction to Analytic Workspace Manager".
From the Tools menu, choose OLAP Worksheet.
OLAP Worksheet opens in a separate window. For information about using OLAP Worksheet, refer to "Using OLAP Worksheet to Execute OLAP DML".
Create a new analytic workspace from the EIF file using commands like these:
AW CREATE aw IMPORT ALL FROM EIF FILE 'directory/filename.eif' DATA DFNS UPDATE COMMIT
Identify the time dimensions:
LIMIT name TO OBJ(PROPERTY 'DIMTYPE') EQ 1 REPORT name
Identify the hierarchy dimension for each time dimension:
SHOW OBJ(PROPERTY 'HIERDIM' timedim)
Note: The Oracle Express Objects metadata identifies all of the objects that support hierarchies and levels for a dimension. You can use the
FULLDSC command to see all of the properties of a dimension, or use the
OBJ function as shown here to obtain the value of particular properties, such as
Create date and time span attributes for each dimension.
DEFINE TIME_TIME_SPAN VARIABLE INTEGER <timedim hierdim> PROPERTY 'USERDATA' FALSE DEFINE TIME_END_DATE VARIABLE DATE <timedim hierdim> PROPERTY 'USERDATA' FALSE
Populate the end date and time span attributes, as described in "Populating Time Attributes".
Set properties on the Time dimension:
CONSIDER timedim PROPERTY 'END_DATE' attribute_name PROPERTY 'TIME_SPAN' attribute_name
TIME_SPAN values (attribute_name) identify the names of the variables that you just created.
Run the conversion tool with a command like this:
Refer to the syntax description in "CREATE_DB_STDFORM Syntax".
After the conversion tool completes successfully, save the changes:
You now have a standard form analytic workspace.
Enable the workspace for the BI Beans. Refer to "Enabling an Analytic Workspace for an Application".
You can do this step now or after you have completed the other steps in this procedure.
To refresh the analytic workspace with new data, revise and run the data loader programs, as described in "Revising the Load Programs".
Dimension members are sorted chronologically within level.
AW$TYPE property has a value of
Period end date and time span attributes are defined and populated.
The conversion process sets the
AW$TYPE property, defines standard form attributes for period end dates and time span, and registers this information in the standard form catalogs. It does not change the order of the Time dimension members nor populate the attributes.
If the Time members are not already sorted in chronological order within levels, then use a program like the one shown in "Sorting Dimension Members" to sort them correctly. This topic assumes that your analytic workspace contains an embedded total dimension for time periods.
The end date and time span attributes are variables dimensioned by Time and Time's hierdim dimension. The end date variable must be defined with a
DATE data type.
The method that you use to populate the end date and time span attributes depends on your data source and the format of your Time dimension members. If the information is available from your original data source (that is, the source from which you populated the Express database), then you can load the information using a file reader program like those discussed in "Reading Flat Files". Otherwise, you must derive the information from the dimension members or their descriptions. An example of this method is shown in "Populating the XADEMO Time Attributes".
You must define and set the following properties before running
On the Time dimension, set the
TIME_SPAN properties to the object names for these attributes. The
DIMTYPE property should be set to
On the end-date and time-span attributes, set the
USERDATA property to
The Refresh wizard in Analytic Workspace Manager only operates on analytic workspaces created using
DBMS_AWM procedures, as described in Chapter 6. When you create an analytic workspace using
CREATE_DB_STDFORM, you circumvent the mechanisms that provide the Refresh wizard with the information it needs to acquire new data. You must refresh your analytic workspace manually using OLAP DML programs.
Your analytic workspace probably contains programs generated by Express Administrator for refreshing your Express database. You can begin by modifying these programs for use in your analytic workspace; they are unusable in their current state.
Delete the following code from your load programs:
EDDE.HIERMNT. This program managed the metadata associated with dimension hierarchies. It is not available for use in analytic workspaces, nor is any of the information about your data that was stored in an
XPDDDATA database. You must manage any changes to the standard form metadata manually.
Code to establish a connection with Oracle. Since the analytic workspace is part of Oracle Database, a connection is always open.
The load programs only refresh the dimensions and measures. They do not refresh the dimension attributes, the hierarchy and level objects, or the standard form catalogs. Refer to Chapter 11 for information about writing load programs for standard form objects associated with dimensions. Refer to Appendix A for information about the standard form catalogs.
This example uses an EIF file that contains objects and Oracle Express Objects metadata from an Express database named
XADEMO. If you are converting an Express database, you are probably already familiar with
Suppose that an EIF file named
xademo.eif is located in a system directory named
\users\oracle\xademo_files. Take these steps to create a standard form analytic workspace from this file.
Log in to your Oracle database as the
SYSTEM user and create the
XADEMO user, permanent and temporary tablespaces, and a database directory for access to the EIF file.
CREATE TABLESPACE olapdata DATAFILE '$ORACLE_HOME/oradata/olapdata.dbf' SIZE 5M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TEMPORARY TABLESPACE olaptmp TEMPFILE '$ORACLE_HOME/oradata/olaptmp.tmp' SIZE 5M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K; CREATE USER xademo IDENTIFIED BY 'xademo' DEFAULT TABLESPACE olapdata TEMPORARY TABLESPACE olaptmp QUOTA UNLIMITED ON olapdata QUOTA UNLIMITED ON olaptmp ACCOUNT UNLOCK; CREATE DIRECTORY xademo_dir as '/users/oracle/OraHome1/xademo_files'; GRANT READ ON DIRECTORY xademo_dir TO xademo;
Refer to Chapter 12 for information about performing these tasks.
Open Analytic Workspace Manager and connect to your Oracle Database as the
Open OLAP Worksheet.
Create an analytic workspace from the EIF file:
AW CREATE xademo IMPORT ALL FROM EIF FILE 'olapdata/xademo.eif' DATA DFNS UPDATE COMMIT
Identify the time dimensions:
LIMIT name TO OBJ(PROPERTY 'DIMTYPE') EQ 1 REPORT name NAME -------------- TIME QUARTER YEAR MONTH
This example shows how to provide support to the
HIERDIM dimension for
SHOW OBJ(PROPERTY 'HIERDIM' 'TIME') T0.HIERDIM
DEFINE TIME_END_DATE VARIABLE DATE <TIME T0.HIERDIM> PROPERTY 'USERDATA' FALSE DEFINE TIME_TIME_SPAN VARIABLE INTEGER <TIME T0.HIERDIM> PROPERTY 'USERDATA' FALSE
TIME_TIME_SPAN variables, as described in the following sections.
Set the properties on
CONSIDER time PROPERTY 'END_DATE' 'TIME_END_DATE' PROPERTY 'TIME_SPAN' 'TIME_TIME_SPAN'
Convert the analytic workspace to database standard form:
CALL CREATE_DB_STDFORM('xademo') UPDATE COMMIT
XADEMO database does not have a data loader program, so no example is provided here. However, Chapter 11 includes examples of file load and SQL fetch programs.
Oracle Express Objects metadata stores the names of supporting objects in properties on the
TIME dimension, as shown in Table B-3.
Table B-3 Oracle Express Objects Properties for Hierarchy and Level Support
||List of hierarchies (dimension)|
||List of levels (dimension)|
||Level associated with each dimension member (relation)|
||Description of each level (formula)|
By using the
OBJ function, you can discover the names of objects that support the
SHOW OBJ(PROPERTY 'LEVELDIM' 'TIME') T0.LEVELDIM SHOW OBJ(PROPERTY 'LEVELLABELFRM' 'TIME') T0.LVLLABFRM
TIME dimension has two hierarchies, which are listed in the
T0.LEVELDIM dimension. They are named
YTD. The following report shows sample
TIME members at each level.
REPORT DOWN time t0.levelrel W 20 t0.lvllabfrm ----------------------------T0.HIERDIM----------------------------- ------------STANDARD------------- ---------------YTD--------------- TIME T0.LEVELREL T0.LVLLABFRM T0.LEVELREL T0.LVLLABFRM ---------- ------------ -------------------- ------------ -------------------- JAN96 L3 Month(s) L5 YTD Month(s) Detail FEB96 L3 Month(s) L5 YTD Month(s) Detail Q1.96 L2 Quarter(s) NA NA LAST.YTD NA NA L4 YTD Summaries 1996 L1 Year(s) NA NA
POP_TIME_ATTRS program shown in Example B-1 populates the
TIME_END_DATE, the program uses the
ENDDATE function to identify the last day of each time period. The
ENDDATE function only operates on dimensions with a time data type (such as
YEAR). However, the
TIME dimension has a
TEXT data type. Several transformations are needed before the
ENDDATE function can be used. The program takes these steps:
For each level, defines a dimension with the appropriate data type (
YEAR). In the example, the dimensions are named
Stores the names of the dimension members for particular level in a valueset. In the example, the valueset is named
Uses the current status of the
T_LIST valueset to add members to the new dimensions (
TIME_TIME_SPAN, the program extracts the first two characters from
TIME_END_DATE at the month level, which has values like
30APR96, to get the number of days in each month.
The program then uses the
ROLLUP command to calculate the number of days in each quarter and year.
T0.PARENT is a self-relation that identifies the parent-child relationships among dimension members. However,
TIME_TIME_SPAN are both dimensioned by
ROLLUP cannot use
T0.PARENT. Instead, the program creates a relation named
TIME_PARENTREL dimensioned only by
TIME, populates it from
T0.PARENT, and uses the new relation in the
Note that aggmaps are more efficient than
ROLLUP, but since this case involves just a single dimension in which all aggregate values are stored,
ROLLUP is slightly more convenient and the performance differences are negligible.
Example B-1 OLAP DML Program for Populating TIME Attributes
DEFINE POP_TIME_ATTRS PROGRAM PROGRAM VARIABLE _ytd TEXT " Stores YTD time members TRAP ON cleanup " Divert processing on error to CLEANUP label " Define dimensions for each level with date data types IF NOT EXISTS('m_temp') THEN DEFINE m_temp DIMENSION MONTH ELSE MAINTAIN m_temp DELETE ALL IF NOT EXISTS('q_temp') THEN DEFINE q_temp DIMENSION QUARTER ELSE MAINTAIN q_temp DELETE ALL " Format years like TIME year members (1997 instead of YR97) IF NOT EXISTS('y_temp') THEN DO DEFINE y_temp DIMENSION YEAR CONSIDER y_temp VNF <YYYY> DOEND ELSE MAINTAIN y_temp DELETE ALL " Define a valueset to store time members IF NOT EXISTS('t_list') THEN DEFINE t_list VALUESET TIME ELSE LIMIT t_list TO NA " Define a one-dimensional time self-relation for rollup IF NOT EXISTS('time_parentrel') THEN DEFINE time_parentrel RELATION time <time> ELSE time_parentrel = NA " Initialize target variables ALLSTAT time_time_span = NA time_end_date = NA " ******************************************* " Set values for the STANDARD hierarchy " ******************************************* LIMIT t0.hierdim TO 'STANDARD' " Select all time members at the month level LIMIT time TO t0.levelrel 'L3' " Store months in the valueset LIMIT t_list TO time " Populate M_TEMP so all months have a MONTH data type MAINTAIN m_temp MERGE values(t_list) " Calculate the end date FOR m_temp time_end_date(time, m_temp) = ENDDATE(m_temp) " Extract the number of days in each month time_time_span = CONVERT(EXTCHARS(time_end_date, 1, 2), DECIMAL) " Store quarters in q_temp LIMIT time TO t0.levelrel 'L2' LIMIT t_list TO time MAINTAIN q_temp MERGE VALUES(t_list) FOR q_temp time_end_date(time, q_temp) = ENDDATE(q_temp) " Store years in y_temp LIMIT time TO t0.levelrel 'L1' LIMIT t_list TO time MAINTAIN y_temp MERGE VALUES(t_list) FOR y_temp time_end_date(time, y_temp) = ENDDATE(y_temp) " ******************************************* " Set values for the YTD hierarchy " ******************************************* LIMIT t0.hierdim TO 'YTD' " Limit status of months to YTD LIMIT time TO t0.levelrel 'L5' LIMIT t_list TO time LIMIT m_temp TO t_list " Calculate end date and time span for months FOR m_temp time_end_date(time, m_temp) = ENDDATE(m_temp) time_time_span = CONVERT(EXTCHARS(time_end_date, 1, 2), DECIMAL) " Get current and previous YTD LIMIT time TO t0.parent EQ 'LAST.YTD' LIMIT time KEEP LAST 1 _ytd = time time_end_date(time, 'LAST.YTD') = time_end_date(time, _ytd) LIMIT time TO t0.parent EQ 'CURRENT.YTD' LIMIT time KEEP LAST 1 _ytd = time time_end_date(time, 'CURRENT.YTD') = time_end_date(time, _ytd) " Rollup time span for quarters and years LIMIT t0.hierdim TO ALL LIMIT time TO ALL FOR t0.hierdim DO time_parentrel = t0.parent ROLLUP time_time_span OVER time USING time_parentrel DOEND CLEANUP: " Delete temporary objects DELETE m_temp q_temp y_temp t_list time_parentrel END