Download Oracle.1z0-531.ExamLabs.2019-03-07.69q.tqb
| Vendor: | Oracle |
| Exam Code: | 1z0-531 |
| Exam Name: | Oracle Essbase 11 Essentials |
| Date: | Mar 07, 2019 |
| File Size: | 2 MB |
Demo Questions
Question 1
Which six files are involved in database recovery for block storage option after a database crash?
- Essn.pag – data
- Essn.ind – index
- Essn.dat
- Temp.dat
- Dbname.esm - kernel file that contains control information for db recovery
- Dbname.tct - transaction control table
- Dbname.ind - free fragment file for data and index free fragments
- DBname.otl
- Metadata folder
Correct answer: ABEFGH
Explanation:
If there is a problem with any one of these essential database files, the entire database becomes corrupted and Essbase Server cannot start the database:essn.pag (A) essn.ind (B) dbname.esm (E) dbname.tct (F) dbname.ind (G) dbname.otl (for block storage databases) (H): Outline file, which stores all metadata for a database and defines how data is stored, but does not store data itselfTo restore the database, delete these file, restart the database, and reload from data files or from export files backed up before the corruption. Reference: Hyperion, Backup and Recovery GuideUsing Backup and Restore for Block Storage Databases If there is a problem with any one of these essential database files, the entire database becomes
corrupted and Essbase Server cannot start the database:
- essn.pag (A)
- essn.ind (B)
- dbname.esm (E)
- dbname.tct (F)
- dbname.ind (G)
- dbname.otl (for block storage databases) (H): Outline file, which stores all metadata for a database and defines how data is stored, but does not store data itself
To restore the database, delete these file, restart the database, and reload from data files or from export files backed up before the corruption.
Reference: Hyperion, Backup and Recovery Guide
Using Backup and Restore for Block Storage Databases
Question 2
Which two options would provide a better design for the following accounts and metrics?
- If there are a small number of accounts that require FTE and Expense dollars, split Accounts and Metrics into 2 dimensions
- If there are a large number of accounts that require FTE and Expense dollars, split Accounts and Metrics into 2 dimensions
- If reporting dictates FTE and dollars in the columns and accounts in the rows, split Accounts and Metrics into 2 dimensions
- If block size is large, then keep Accounts and Metrics as one dimension with a dense dimension
Correct answer: BD
Explanation:
Use Application Design Best Practices, Minimize the number of dimensions, Avoid Repetition in dimensions, Avoid inter dimensional irrelevance. http://www.scribd.com/doc/40391863/10-Hardcore-Essbase-Tuning-Tips-You-Ve-Never-Heard-Before Use Application Design Best Practices, Minimize the number of dimensions, Avoid Repetition in dimensions, Avoid inter dimensional irrelevance.
http://www.scribd.com/doc/40391863/10-Hardcore-Essbase-Tuning-Tips-You-Ve-Never-Heard-Before
Question 3
Identify the two true statements about incremental loading.
- Allows for real time data access for end users.
- Creates *subscribes* along the main slice in the database.
- Materialization of slices is required to provide users the correct query results.
- Different materialized views may exist within a slice as compared to the main slice of the database.
Correct answer: AC
Explanation:
A: Incremental loading and fast aggregation can provide near real-time analysis of transactional data.C: Incremental loading creates subcubes or slices alongside the primary slice of the database.Note: Following a data load, Essbase ASO does not store any aggregate values, but instead calculates them on demand. For large databases, where the time required to generate these values may become inconvenient, the database can materialize one or more aggregate "views", made up of one aggregate level from each dimension (for example, the database may calculate all combinations of the fifth generation of Product with the third generation of Customer), and these views are then used to generate other aggregate values where possible. This process can be partially automated, where the administrator specifies the amount of disk space that may be used, and the database generates views according to actual usage.This approach has a major drawback in that the cube cannot be treated for calculation purposes as a single large hypercube, because aggregate values cannot be directly controlled, so write-back from front-end tools is limited, and complex calculations that cannot be expressed as MDX expressions are not possible. Hyperion Essbase - System 9 Database Administrator's Guide A: Incremental loading and fast aggregation can provide near real-time analysis of transactional data.
C: Incremental loading creates subcubes or slices alongside the primary slice of the database.
Note: Following a data load, Essbase ASO does not store any aggregate values, but instead calculates them on demand. For large databases, where the time required to generate these values may become inconvenient, the database can materialize one or more aggregate "views", made up of one aggregate level from each dimension (for example, the database may calculate all combinations of the fifth generation of Product with the third generation of Customer), and these views are then used to generate other aggregate values where possible. This process can be partially automated, where the administrator specifies the amount of disk space that may be used, and the database generates views according to actual usage.
This approach has a major drawback in that the cube cannot be treated for calculation purposes as a single large hypercube, because aggregate values cannot be directly controlled, so write-back from front-end tools is limited, and complex calculations that cannot be expressed as MDX expressions are not possible.
Hyperion Essbase - System 9 Database Administrator's Guide
