Enterprise Technology Assessment: Oracle, Cognos & IT Service Management

SLA measurement for tickets uses dual criteria: 'Problem Resolved' means the technical fix is implemented, while 'Service Restored' confirms the service is fully operational for end users. Both conditions must be met - the fix must be complete AND the service must actually work for the customer.

HLE in SERV stands for High Level Estimates, which are preliminary rough estimates of effort required for a service request. These are initial ballpark figures prepared before detailed analysis, used for early planning and resource assessment.

P1 (Priority 1) tickets represent critical incidents requiring immediate action. Best practices include regular status updates, timely customer communication, persistent follow-up, and notification when service is restored. All options reflect professional incident management protocols.

The question asks to select SR types from the list. Application Support, Program Change, and Emergency Change are standard service request categories. Fixed Variable and Variable are not SR types. The 'All of the Above' option is logically incorrect because D and E should not be selected.

Service restoration time is a critical metric for incident management. Being able to update this timestamp even after ticket closure allows for accurate record-keeping and reporting. This flexibility ensures data accuracy when final resolution details become available after initial closure.

In the SERV system, SRs qualify for production launch after passing Quality Gate 2 (QG2). QG1 appears to be an earlier milestone (possibly requirements or design approval), while QG2 represents the final quality checkpoint before production deployment.

THB (Technical Handbook/Base) updates in ADMS (Advanced Data Management System) typically follow a quarterly cycle. A 3-month update frequency is standard for technical documentation that requires regular synchronization with system changes. Monthly updates would be too frequent for stable documentation, while 6-month or 15-day cycles are either too slow or unnecessarily rapid.

Testing reports in Cognos requires validation to verify data accuracy, filter logic, and formatting. The 'Validate Report' function checks the report definition, verifies calculations, and ensures the report will execute correctly before actual execution.

In Cognos, a macro is a set of instructions or commands that can run applications or automate tasks, while a prompt specifies the manner in which data is displayed in reports (such as filters, sorting, or formatting options). Macros execute actions; prompts control presentation.

Cognos models are tested through the 'Check Model' option in the Tools menu. This validates the model's structure, verifies relationships between query items, checks for inconsistencies, and ensures the model is ready for report generation before it's published.

Cognos Visualizer presents data cubes in a visual dashboard format for interactive analysis, while Cognos Scripting provides a scripting environment to write Cognos macros and programs that automate tasks, extend functionality, and integrate with other systems.

Cognos project security is implemented through packages (which control what data users can access) combined with users, groups, and roles managed through Access Manager. This layered approach grants or restricts access to specific reports, models, and data based on organizational roles.

A single table can have a maximum of 12 triggers: 3 triggers (INSERT, UPDATE, DELETE) × 2 timing options (BEFORE, AFTER) × 2 levels (statement-level, row-level). This provides comprehensive automation for data integrity and business rule enforcement at different execution stages.

The months_between date function returns a numeric value representing the number of months between two dates. This is useful for calculating durations, age, or time periods in month units. Other date functions like days_between return counts, while add_days/add_months return modified dates, not numeric values.

Oracle uses different types of segments to store data efficiently. Data segments store table data, index segments store index structures, temporary segments hold intermediate results during sort operations, and rollback segments store before-images for transaction rollback and recovery. Option C correctly lists all four fundamental segment types used in Oracle database storage management.

Oracle database is primarily developed in C programming language. The core database engine, memory management, and low-level system interfaces are written in C for portability and performance. While components may use other languages, C remains the foundational language for Oracle's development.

In Hibernate and similar ORM frameworks, mapping-level instructions (defined on specific properties or relationships) do override session-level instructions. This allows fine-grained control where specific mappings behave differently from the session default configuration.