Tools Downloads and Installations

From <http://docs.oracle.com/cd/B19306_01/server.102/b14211/technique.htm>

Thank you for your feedback |Recognition@hp

PERFORMANCE TUNING

==================

1. How would you approach database performance: By identifying bottlenecks and fixing them

2. How do you force the optimizer to use a new plan: By first enabling baseline capture using : alter session

set optimizer_capture_sql_plan_baselines = true;

3. Difference between local and global index: A global index is a one-to-many relationship, allowing one index partition to map to many table partitions while A local index is a one-to-one mapping between a index partition and a table partition.

4. What is the difference between DB file sequential read and DB File Scattered Read?: db file sequential read wait event has three parameters: file#, first block#, and block count while db file scattered Oracle metric event signifies that the user process is reading buffers into the SGA buffer cache and is waiting for a physical I/O call to return

5. Difference between nested loop joins and hash joins: Hash joins can not look up rows from the inner (probed) row source based on values retrieved from the outer (driving) row source, nested loops can

6. What factors do you consider when creating indexes on tables? How do you select the column for an index?:• Non-key columns are defined in the INCLUDE clause of the CREATE INDEX statement.

• Non-key columns can only be defined on non-clustered indexes on tables or indexed views.

7. If you were involved at the early stages of database development and coding, what are some of the measures you would suggest for optimal performance?

1. Get candid feedback from users. Determine the performance project's scope and subsequent performance goals, as well as performance goals for the future. This process is key in future capacity planning.

2. Get a full set of operating system, database, and application statistics from the system when the performance is both good and bad. If these are not available, then get whatever is available. Missing statistics are analogous to missing evidence at a crime scene: They make detectives work harder and it is more time-consuming.

3. Sanity-check the operating systems of all systems involved with user performance. By sanity-checking the operating system, you look for hardware or operating system resources that are fully utilized. List any over-used resources as symptoms for analysis later. In addition, check that all hardware shows no errors or diagnostics.

4. Check for the top ten most common mistakes with Oracle, and determine if any of these are likely to be the problem. List these as symptoms for later analysis. These are included because they represent the most likely problems. ADDM automatically detects and reports nine of these top ten issues. See Chapter 6, "Automatic Performance Diagnostics" and "Top Ten Mistakes Found in Oracle Systems".

5. Build a conceptual model of what is happening on the system using the symptoms as clues to understand what caused the performance problems. See "A Sample Decision Process for Performance Conceptual Modeling".

6. Propose a series of remedy actions and the anticipated behavior to the system, then apply them in the order that can benefit the application the most. ADDM produces recommendations each with an expected benefit. A golden rule in performance work is that you only change one thing at a time and then measure the differences. Unfortunately, system downtime requirements might prohibit such a rigorous investigation method. If multiple changes are applied at the same time, then try to ensure that they are isolated so that the effects of each change can be independently validated.

8. Is creating an index online possible?: YES

9. What is the difference between Redo, Rollback and Undo?:Redo log files record changes to the database as a result of transactions and internal Oracle server actions,undo and rollback segment terms are used interchangeably in db world. It is due to the compatibility issue of oracle.

Undo

What is Row Chaining and Row Migration?

10. How to find out background processes?: select sid, process, program

from v$session s join v$bgprocess using (paddr)

where s.status = 'ACTIVE'

and rownum < 5;

11. How to find background processes from OS:$ ps -ef|grep ora_|grep SID

12. How do you troubleshoot connectivity issues?: Verify path to TNS_ADMIN is set correctly and that all the connection identifier(SIDs) exists in the tnsnames.ora file

13. Why are bind variables important?:Bind variables have a huge impact on the stress in the shared pool Can you force literals to be converted into bind variables?: YES

14. What is adaptive cursor sharing? It allows the optimizer to generate a set of plans that are optimal for different sets of bind values

15. In Data Pump, if you restart a job in Data Pump, how it will know from where to resume?: By attaching the name of the job to be resumed. That is: expdp system/manager attach="Job_Name"

1. How would you approach database performance :http://docs.oracle.com/cd/B19306_01/server.102/b14211/technique.htm#i11146

Oracle performance methodology involves identifying bottlenecks and fixing them. It is recommended that changes be made to a system only after you have confirmed that there is a bottleneck. Performance problems generally result from either a lack of throughput, unacceptable user/jobresponse time, or both

Before looking at any database or operating system statistics, it is crucial to get feedback from the most important components of the system: the users of the system and the people ultimately paying for the application. Typical user feedback includes statements like the following:

· "The online performance is so bad that it prevents my staff from doing their jobs."

· "The billing run takes too long."

· "When I experience high amounts of Web traffic, the response time becomes unacceptable, and I am losing customers."

· "I am currently performing 5000 trades a day, and the system is maxed out. Next month, we roll out to all our users, and the number of trades is expected to quadruple."

From candid feedback, it is easy to set critical success factors for any performance work. Determining the performance targets and the performance engineer's exit criteria make managing the performance process much simpler and more successful at all levels. These critical success factors are better defined in terms of real business goals rather than system statistics.

Some real business goals for these typical user statements might be:

· "The billing run must process 1,000,000 accounts in a three-hour window."

· "At a peak period on a Web site, the response time will not exceed five seconds for a page refresh."

· "The system must be able to process 25,000 trades in an eight-hour window."

The ultimate measure of success is the user's perception of system performance. The performance engineer's role is to eliminate any bottlenecks that degrade performance. These bottlenecks could be caused by inefficient use of limited shared resources or by abuse of shared resources, causing serialization. Because all shared resources are limited, the goal of a performance engineer is to maximize the number of business operations with efficient use of shared resources. At a very high level, the entire database server can be seen as a shared resource. Conversely, at a low level, a single CPU or disk can be seen as shared resources.

The Oracle performance improvement method can be applied until performance goals are met or deemed impossible. This process is highly iterative, and it is inevitable that some investigations will be made that have little impact on the performance of the system. It takes time and experience to develop the necessary skills to accurately pinpoint critical bottlenecks in a timely manner. However, prior experience can sometimes work against the experienced engineer who neglects to use the data and statistics available to him. It is this type of behavior that encourages database tuning by myth and folklore. This is a very risky, expensive, and unlikely to succeed method of database tuning.

The Automatic Database Diagnostic Monitor (ADDM) implements parts of the performance improvement method and analyzes statistics to provide automatic diagnosis of major performance issues. Using ADDM can significantly shorten the time required to improve the performance of a system. See Chapter 6, "Automatic Performance Diagnostics" for a description of ADDM.

Steps in The Oracle Performance Improvement Method

Perform the following initial standard checks:

1. Get candid feedback from users. Determine the performance project's scope and subsequent performance goals, as well as performance goals for the future. This process is key in future capacity planning.

2. Get a full set of operating system, database, and application statistics from the system when the performance is both good and bad. If these are not available, then get whatever is available. Missing statistics are analogous to missing evidence at a crime scene: They make detectives work harder and it is more time-consuming.

3. Sanity-check the operating systems of all systems involved with user performance. By sanity-checking the operating system, you look for hardware or operating system resources that are fully utilized. List any over-used resources as symptoms for analysis later. In addition, check that all hardware shows no errors or diagnostics.

4. Check for the top ten most common mistakes with Oracle, and determine if any of these are likely to be the problem. List these as symptoms for later analysis. These are included because they represent the most likely problems. ADDM automatically detects and reports nine of these top ten issues. See Chapter 6, "Automatic Performance Diagnostics" and "Top Ten Mistakes Found in Oracle Systems".

5. Build a conceptual model of what is happening on the system using the symptoms as clues to understand what caused the performance problems. See "A Sample Decision Process for Performance Conceptual Modeling".

6. Propose a series of remedy actions and the anticipated behavior to the system, then apply them in the order that can benefit the application the most. ADDM produces recommendations each with an expected benefit. A golden rule in performance work is that you only change one thing at a time and then measure the differences. Unfortunately, system downtime requirements might prohibit such a rigorous investigation method. If multiple changes are applied at the same time, then try to ensure that they are isolated so that the effects of each change can be independently validated.

7. Validate that the changes made have had the desired effect, and see if the user's perception of performance has improved. Otherwise, look for more bottlenecks, and continue refining the conceptual model until your understanding of the application becomes more accurate.

8. Repeat the last three steps until performance goals are met or become impossible due to other constraints

ADDM

For a quick and easy approach to performance tuning, use the Automatic Database Diagnostic Monitor (ADDM). ADDM automatically monitors your Oracle system and provides recommendations for solving performance problems should problems occur. For example, suppose a DBA receives a call from a user complaining that the system is slow. The DBA simply examines the latest ADDM report to see which of the recommendations should be implemented to solve the problem. See Chapter 6, "Automatic Performance Diagnostics" for information on the features that help monitor and diagnose Oracle systems

MANUAL PERFORMANCE TUNING DIAGNOSIS

The following steps illustrate how a performance engineer might look for bottlenecks without using automatic diagnostic features. These steps are only intended as a guideline for the manual process. With experience, performance engineers add to the steps involved. This analysis assumes that statistics for both the operating system and the database have been gathered.

1. Is the response time/batch run time acceptable for a single user on an empty or lightly loaded system?
If it is not acceptable, then the application is probably not coded or designed optimally, and it will never be acceptable in a multiple user situation when system resources are shared. In this case, get application internal statistics, and get SQL Trace and SQL plan information. Work with developers to investigate problems in data, index, transaction SQL design, and potential deferral of work to batch/background processing.

2. Is all the CPU being utilized?
If the kernel utilization is over 40%, then investigate the operating system for network transfers, paging, swapping, or process thrashing. Otherwise, move onto CPU utilization in user space. Check to see if there are any non-database jobs consuming CPU on the system limiting the amount of shared CPU resources, such as backups, file transforms, print queues, and so on. After determining that the database is using most of the CPU, investigate the top SQL by CPU utilization. These statements form the basis of all future analysis. Check the SQL and the transactions submitting the SQL for optimal execution. Oracle provides CPU statistics in V$SQL and V$SQLSTATS.
See Also:
Oracle Database Reference for more information on V$SQL and V$SQLSTATS
If the application is optimal and there are no inefficiencies in the SQL execution, consider rescheduling some work to off-peak hours or using a bigger system.

3. At this point, the system performance is unsatisfactory, yet the CPU resources are not fully utilized.
In this case, you have serialization and unscalable behavior within the server. Get the WAIT_EVENTS statistics from the server, and determine the biggest serialization point. If there are no serialization points, then the problem is most likely outside the database, and this should be the focus of investigation. Elimination of WAIT_EVENTS involves modifying application SQL and tuning database parameters. This process is very iterative and requires the ability to drill down on the WAIT_EVENTS systematically to eliminate serialization points.

Top Ten Mistakes Found in Oracle Systems

This section lists the most common mistakes found in Oracle systems. By following the Oracle performance improvement methodology, you should be able to avoid these mistakes altogether. If you find these mistakes in your system, then re-engineer the application where the performance effort is worthwhile. See "Automatic Performance Tuning Features" for information on the features that help diagnose and tune Oracle systems. See Chapter 10, "Instance Tuning Using Performance Views" for a discussion on how wait event data reveals symptoms of problems that can be impacting performance.

1. Bad Connection Management
The application connects and disconnects for each database interaction. This problem is common with stateless middleware in application servers. It has over two orders of magnitude impact on performance, and is totally unscalable.

2. Bad Use of Cursors and the Shared Pool
Not using cursors results in repeated parses. If bind variables are not used, then there is hard parsing of all SQL statements. This has an order of magnitude impact in performance, and it is totally unscalable. Use cursors with bind variables that open the cursor and execute it many times. Be suspicious of applications generating dynamic SQL.

3. Bad SQL
Bad SQL is SQL that uses more resources than appropriate for the application requirement. This can be a decision support systems (DSS) query that runs for more than 24 hours or a query from an online application that takes more than a minute. SQL that consumes significant system resources should be investigated for potential improvement. ADDM identifies high load SQL and the SQL tuning advisor can be used to provide recommendations for improvement. See Chapter 6, "Automatic Performance Diagnostics" and Chapter 12, "Automatic SQL Tuning".

4. Use of Nonstandard Initialization Parameters
These might have been implemented based on poor advice or incorrect assumptions. Most systems will give acceptable performance using only the set of basic parameters. In particular, parameters associated with SPIN_COUNT on latches and undocumented optimizer features can cause a great deal of problems that can require considerable investigation.
Likewise, optimizer parameters set in the initialization parameter file can override proven optimal execution plans. For these reasons, schemas, schema statistics, and optimizer settings should be managed together as a group to ensure consistency of performance.
See Also:

· Oracle Database Administrator's Guide for information on initialization parameters and database creation

· Oracle Database Reference for details on initialization parameters

· "Performance Considerations for Initial Instance Configuration" for information on parameters and settings in an initial instance configuration

5. Getting Database I/O Wrong
Many sites lay out their databases poorly over the available disks. Other sites specify the number of disks incorrectly, because they configure disks by disk space and not I/O bandwidth. See Chapter 8, "I/O Configuration and Design".

6. Redo Log Setup Problems
Many sites run with too few redo logs that are too small. Small redo logs cause system checkpoints to continuously put a high load on the buffer cache and I/O system. If there are too few redo logs, then the archive cannot keep up, and the database will wait for the archive process to catch up. See Chapter 4, "Configuring a Database for Performance" for information on sizing redo logs for performance.

7. Serialization of data blocks in the buffer cache due to lack of free lists, free list groups, transaction slots (INITRANS), or shortage of rollback segments.
This is particularly common on INSERT-heavy applications, in applications that have raised the block size above 8K, or in applications with large numbers of active users and few rollback segments. Use automatic segment-space management (ASSM) to and automatic undo management solve this problem.

8. Long Full Table Scans
Long full table scans for high-volume or interactive online operations could indicate poor transaction design, missing indexes, or poor SQL optimization. Long table scans, by nature, are I/O intensive and unscalable.

9. High Amounts of Recursive (SYS) SQL
Large amounts of recursive SQL executed by SYS could indicate space management activities, such as extent allocations, taking place. This is unscalable and impacts user response time. Use locally managed tablespaces to reduce recursive SQL due to extent allocation. Recursive SQL executed under another user Id is probably SQL and PL/SQL, and this is not a problem.

10. Deployment and Migration Errors
In many cases, an application uses too many resources because the schema owning the tables has not been successfully migrated from the development environment or from an older implementation. Examples of this are missing indexes or incorrect statistics. These errors can lead to sub-optimal execution plans and poor interactive user performance. When migrating applications of known performance, export the schema statistics to maintain plan stability using the DBMS_STATS package.
Although these errors are not directly detected by ADDM, ADDM highlights the resulting high load SQL.

3.2 Emergency Performance Methods

This section provides techniques for dealing with performance emergencies. You have already had the opportunity to read about a detailed methodology for establishing and improving application performance. However, in an emergency situation, a component of the system has changed to transform it from a reliable, predictable system to one that is unpredictable and not satisfying user requests.

In this case, the role of the performance engineer is to rapidly determine what has changed and take appropriate actions to resume normal service as quickly as possible. In many cases, it is necessary to take immediate action, and a rigorous performance improvement project is unrealistic.

After addressing the immediate performance problem, the performance engineer must collect sufficient debugging information either to get better clarity on the performance problem or to at least ensure that it does not happen again.

The method for debugging emergency performance problems is the same as the method described in the performance improvement method earlier in this book. However, shortcuts are taken in various stages because of the timely nature of the problem. Keeping detailed notes and records of facts found as the debugging process progresses is essential for later analysis and justification of any remedial actions. This is analogous to a doctor keeping good patient notes for future reference.

3.2.1 Steps in the Emergency Performance Method

The Emergency Performance Method is as follows:

1. Survey the performance problem and collect the symptoms of the performance problem. This process should include the following:

· User feedback on how the system is underperforming. Is the problem throughput or response time?

· Ask the question, "What has changed since we last had good performance?" This answer can give clues to the problem. However, getting unbiased answers in an escalated situation can be difficult. Try to locate some reference points, such as collected statistics or log files, that were taken before and after the problem.

· Use automatic tuning features to diagnose and monitor the problem. See "Automatic Performance Tuning Features" for information on the features that help diagnose and tune Oracle systems. In addition, you can use Oracle Enterprise Manager performance features to identify top SQL and sessions.

2. Sanity-check the hardware utilization of all components of the application system. Check where the highest CPU utilization is, and check the disk, memory usage, and network performance on all the system components. This quick process identifies which tier is causing the problem. If the problem is in the application, then shift analysis to application debugging. Otherwise, move on to database server analysis.

3. Determine if the database server is constrained on CPU or if it is spending time waiting on wait events. If the database server is CPU-constrained, then investigate the following:

· Sessions that are consuming large amounts of CPU at the operating system level and database; check V$SESS_TIME_MODEL for database CPU usage

· Sessions or statements that perform many buffer gets at the database level; check V$SESSTAT and V$SQLSTATS

· Execution plan changes causing sub-optimal SQL execution; these can be difficult to locate

· Incorrect setting of initialization parameters

· Algorithmic issues as a result of code changes or upgrades of all components
If the database sessions are waiting on events, then follow the wait events listed in V$SESSION_WAIT to determine what is causing serialization. The V$ACTIVE_SESSION_HISTORY view contains a sampled history of session activity which can be used to perform diagnosis even after an incident has ended and the system has returned to normal operation. In cases of massive contention for the library cache, it might not be possible to logon or submit SQL to the database. In this case, use historical data to determine why there is suddenly contention on this latch. If most waits are for I/O, then examine V$ACTIVE_SESSION_HISTORY to determine the SQL being run by the sessions that are performing all of the inputs and outputs. See Chapter 10, "Instance Tuning Using Performance Views" for a discussion on wait events.

4. Apply emergency action to stabilize the system. This could involve actions that take parts of the application off-line or restrict the workload that can be applied to the system. It could also involve a system restart or the termination of job in process. These naturally have service level implications.

5. Validate that the system is stable. Having made changes and restrictions to the system, validate that the system is now stable, and collect a reference set of statistics for the database. Now follow the rigorous performance method described earlier in this book to bring back all functionality and users to the system. This process may require significant application re-engineering before it is complete.

2. How do you force the optimizer to use a new plan: http://www.oracle.com/technetwork/issue-archive/2009/09-mar/o29spm-092092.html

TECHNOLOGY: SQL

Baselines and Better Plans

By Arup Nanda

Use SQL plan management in Oracle Database 11g to optimize execution plans.

Have you ever been in a situation in which some database queries that used to behave well suddenly started performing poorly? More likely than not, you traced the cause back to a change in the execution plan. Further analysis may have revealed that the performance change was due to newly collected optimizer statistics on the tables and indexes referred to in those queries.

And thoroughly humbled by this situation, have you ever made a snap decision to stop statistics collection? This course of action keeps the execution plans pretty much the same for those queries, but it makes other things worse. Performance of some other queries, or even the same queries with different predicates (the WHERE clauses), deteriorates because of suboptimal execution plans generated from stale statistics.

Whatever action you take next carries some risk, so how can you mitigate that risk and ensure that the execution plans for the SQL statements generated are optimal while maintaining a healthy environment in which optimizer statistics are routinely collected and all SQL statements perform well without significant changes (such as adding hints)? You may resort to using stored outlines to freeze the plan, but that also means that you‘re preventing the optimizer from generating potentially beneficial execution plans.

In Oracle Database 11g, using the new SQL plan management feature, you can now examine how execution plans change over time, have the database verify new plans by executing them before using them, and gradually evolve better plans in a controlled manner.

SQL Plan Management

When SQL plan management is enabled, the optimizer stores generated execution plans in a special repository, the SQL management base. All stored plans for a specific SQL statement are said to be part of a plan history for that SQL statement.

Some of the plans in the history can be marked as “accepted.”When the SQL statement is reparsed, the optimizer considers only the accepted plans in the history. This set of accepted plans for that SQL statement is called a SQL plan baseline , or baseline for short.

The optimizer still tries to generate a better plan, however. If the optimizer does generate a new plan, it adds it to the plan history but does not consider it while reparsing the SQL, unless the new plan is better than all the accepted plans in the baseline. Therefore, with SQL plan management enabled, SQL statements will never suddenly have a less efficient plan that results in worse performance.

With SQL plan management, you can examine all the available plans in the plan history for a SQL statement, compare them to see their relative efficiency, promote a specific plan to accepted status, and even make a plan the permanent (fixed) one.

This article will show you how to manage SQL plan baselines—including capturing, selecting, and evolving baselines—by using Oracle Enterprise Manager and SQL from the command line to ensure the optimal performance of SQL statements.

Capture

The capture function of SQL plan management captures the various optimizer plans used by SQL statements. By default, capture is disabled—that is, SQL plan management does not capture the history for the SQL statements being parsed or reparsed.

Now let‘s capture the baselines for some SQL statement examples coming from one session. We will use a sample schema provided with Oracle Database 11g—SH—and the SALES table in particular.

First, we enable the baseline capture in the session:

alter session
set optimizer_capture_sql_plan_baselines = true;

Now all the SQL statements executed in this session will be captured, along with their optimization plans, in the SQL management base. Every time the plan changes for a SQL statement, it is stored in the plan history. To see this, run the script shown in Listing 1, which executes exactly the same SQL but under different circumstances. First, the SQL runs with all the defaults (including an implicit default optimizer_mode = all_rows). In the next execution, the optimizer_mode parameter value is set to first_rows. Before the third execution of the SQL, we collect fresh stats on the table and the indexes

Code Listing 1: Capturing SQL plan baselines

alter session set optimizer_capture_sql_plan_baselines = true;
-- First execution. Default Environment
select * /* ARUP */ from sales
where quantity_sold > 1 order by cust_id;
-- Change the optimizer mode
alter session set optimizer_mode = first_rows;
-- Second execution. Opt Mode changed
select * /* ARUP */ from sales
where quantity_sold > 1 order by cust_id;
-- Gather stats now
begin
   dbms_stats.gather_table_stats (
        ownname            => 'SH',
        tabname             => 'SALES',
        cascade              => TRUE,
        no_invalidate      => FALSE,
        method_opt        => 'FOR ALL INDEXED COLUMNS SIZE AUTO',
        granularity          => 'GLOBAL AND PARTITION',
        estimate_percent => 10,
        degree                => 4
    );
end;
/
-- Third execution. After stats
select * /* ARUP */ from sales
where quantity_sold > 1 order by cust_id;

If the plan changes in each of the executions of the SQL in Listing 1, the different plans will be captured in the plan history for that SQL statement. (The /* ARUP */ comment easily identifies the specific SQL statements in the shared pool.)

The easiest way to view the plan history is through Oracle Enterprise Manager. From the Database main page, choose the Server tab and then click SQL Plan Control . From that page, choose the SQL Plan Baseline tab. On that page, search for the SQL statements containing the name ARUP , as in Figure 1, which shows the plan history for the SQL statements on the lower part of the screen.

3. Difference between local and global index:

Oracle Global Index vs. Local Index

Question: What is the difference between a oracle global index and a local index?

Answer: When using Oracle partitioning, you can specify the “global” or “local” parameter in the create index syntax:

· Global Index: A global index is a one-to-many relationship, allowing one index partition to map to many table partitions. The docs says that a "global index can be partitioned by the range or hash method, and it can be defined on any type of partitioned, or non-partitioned, table".

· Local Index: A local index is a one-to-one mapping between a index partition and a table partition. In general, local indexes allow for a cleaner “divide and conquer” approach for generating fast SQL execution plans with partition pruning.

For complete details, see my tips for Oracle partitioning.

Global and Local Index partitioning with Oracle

The first partitioned index method is called a LOCAL partition. A local partitioned index creates a one-for-one match between the indexes and the partitions in the table. Of course, the key value for the table partition and the value for the local index must be identical. The second method is called GLOBAL and allows the index to have any number of partitions.

The partitioning of the indexes is transparent to all SQL queries. The great benefit is that the Oracle query engine will scan only the index partition that is required to service the query, thus speeding up the query significantly. In addition, the Oracle parallel query engine will sense that the index is partitioned and will fire simultaneous queries to scan the indexes.

Local partitioned indexes

Local partitioned indexes allow the DBA to take individual partitions of a table and indexes offline for maintenance (or reorganization) without affecting the other partitions and indexes in the table.

In a local partitioned index, the key values and number of index partitions will match the number of partitions in the base table.

CREATE INDEX year_idx

on all_fact (order_date)

LOCAL

(PARTITION name_idx1),

(PARTITION name_idx2),

(PARTITION name_idx3);

Oracle will automatically use equal partitioning of the index based upon the number of partitions in the indexed table. For example, in the above definition, if we created four indexes on all_fact, the CREATE INDEX would fail since the partitions do not match. This equal partition also makes index maintenance easier, since a single partition can be taken offline and the index rebuilt without affecting the other partitions in the table.

Global partitioned indexes

A global partitioned index is used for all other indexes except for the one that is used as the table partition key. Global indexes partition OLTP (online transaction processing) applications where fewer index probes are required than with local partitioned indexes. In the global index partition scheme, the index is harder to maintain since the index may span partitions in the base table.

For example, when a table partition is dropped as part of a reorganization, the entire global index will be affected. When defining a global partitioned index, the DBA has complete freedom to specify as many partitions for the index as desired.

Now that we understand the concept, let's examine the Oracle CREATE INDEX syntax for a globally partitioned index:

CREATE INDEX item_idx

on all_fact (item_nbr)

GLOBAL

(PARTITION city_idx1 VALUES LESS THAN (100)),

(PARTITION city_idx1 VALUES LESS THAN (200)),

(PARTITION city_idx1 VALUES LESS THAN (300)),

(PARTITION city_idx1 VALUES LESS THAN (400)),

(PARTITION city_idx1 VALUES LESS THAN (500));

Here, we see that the item index has been defined with five partitions, each containing a subset of the index range values. Note that it is irrelevant that the base table is in three partitions. In fact, it is acceptable to create a global partitioned index on a table that does not have any partitioning.

From <http://www.dba-oracle.com/t_global_local_partitioned_index.htm>

<https://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:5931711000346922149>

Thanks for the question, Aravindhan.

Submitted: January 16, 2013 - 12:53 am UTC | Last updated: August 08, 2013 - 4:56 pm UTC

Category: Database | Version: 11.1.0

QUESTION: Which Index is Better Global Or Local in Partitioned Table?

Latest Followup

You Asked

We have partitioned table based on date say startdate (Interval partition , For each day)

We will use query that will generate report based on days (like report for previous 5 days)

Also we use queries that will generate report based on hours (like report for previous 5 hours)

So there are queries will access data within partition and across partition as well

So please suggest whether we can for global or local index on start date

and we said...

well, if you are going to cross partitions - hitting 5 days worth of data - hopefully you would NOT be using an index at all. Hopefully you would be using a full scan of the five partitions since you are hitting every row.

If all of your queries include "startdate" in the predicate and you think you'll hit partitions at the most typically - it is likely you want to employ locally partitioned indexes for most all of your indexes.

And startdate doesn't need to be in all of these indexes (they do not need to be prefixed with startdate). Only when you are going after the previous N hours might you want an index that starts with startdate.

for example, suppose you have queries like:

select ....
from t
where startdate between sysdate and sysdate-5
and x > 100;

select ....
from t
where startdate between sysdate and sysdate-2
and x > 100;

it MIGHT make sense to have a locally partitioned index on X, just on X. If x > 100 returns a very small number of rows from those five partitions then an index on X and just on X would be appropriate. We will do five index range scans (which is acceptable) to find the rows.

For the second query we would just do two index range scans (again, acceptable).

You would want a globally partitioned index on X if you did queries like:

select ....
from t
where startdate between sysdate and sysdate-50
and x > 100;

select ....
from t
where x > 100;

From <https://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:5931711000346922149>

4. What is the difference between DB file sequential read and DB File Scattered Read? http://www.dba-oracle.com/m_cpu_time_execution.htm>

The db file sequential read wait event has three parameters: file#, first block#, and block count. In Oracle Database 10g, this wait event falls under the User I/O wait class. Keep the following key thoughts in mind when dealing with the db file sequential read wait event.

· The Oracle process wants a block that is currently not in the SGA, and it is waiting for the database block to be read into the SGA from disk.

· The two important numbers to look for are the TIME_WAITED and AVERAGE_WAIT by individual sessions.

· Significant db file sequential read wait time is most likely an application issue.

· From <http://logicalread.solarwinds.com/oracle-db-file-sequential-read-wait-event-part1-mc01/>

WHILE …

"The db file scattered Oracle metric event signifies that the user process is reading buffers into the SGAbuffer cache and is waiting for a physical I/Ocall to return. A db file scattered read issues a scatter-read to read the data into multiple discontinuous memory locations. A scattered read is usually a multiblock read. It can occur for a fast full scan (of an index) in addition to a full table scan.

The db file scattered read wait event identifies that a full table scan is occurring. When performing a full table scan into the buffer cache, the blocks read are read into memory locations that are not physically adjacent to each other. Such reads are called scattered read calls, because the blocks are scattered throughout memory. This is why the corresponding wait event is called 'db file scattered read'. Multiblock (up to DB_FILE_MULTIBLOCK_READ_COUNT blocks) reads due to full table scans into the buffer cache show up as waits for 'db file scattered read'."

Furthermore, Oracle FAQ's explains that "'db file scattered read' events signify time waited for I/O read requests to complete. Time is reported in 100's of a second for Oracle 8i releases and below, and 1000's of a second for Oracle 9i and above. Most people confuse these events with each other as they think of how data is read from disk. Instead they should think of how data is read into the SGA buffer cache or user PGA memory." Also, the difference between db file scattered read and db file sequential read is that file scattered reads, "is reading multiple data blocks and scatters them into different discontinuous buffers in the SGA."

The popular Ion tool is the easiest way to analyze Oracle cache and disk performance (db block parallel reads and writes), and Ion allows you to spot hidden disk I/O performance trends.

Ion is our favorite Oracle tuning tool, and the only 3rd party tool that we use.

5. Difference between nested loop joins and hash joins: http://blog.tanelpoder.com/2010/10/06/a-the-most-fundamental-difference-between-hash-and-nested-loop-joins/>

· Hash joins can not look up rows from the inner (probed) row source based on values retrieved from the outer (driving) row source, nested loops can.

Nested loops, Hash join and Sort Merge joins – difference?

Nested loop (loop over loop) : http://oracle-online-help.blogspot.com/2007/03/nested-loops-hash-join-and-sort-merge.html>

In this algorithm, an outer loop is formed which consists of few entries and then for each entry, and inner loop is processed.

Ex:

Select tab1.*, tab2.* from tabl, tab2 where tabl.col1=tab2.col2;

It is processed like:

For i in (select * from tab1) loop

For j in (select * from tab2 where col2=i.col1) loop

Display results;

End loop;

The Steps involved in doing nested loop are:

a) Identify outer (driving) table

Assign inner (driven) table to outer table.

For every row of outer table, access the rows of inner table.

In execution plan it is seen like this:

NESTED LOOPS

outer_loop

inner_loop

When optimizer uses nested loops?

Optimizer uses nested loop when we are joining tables containing small number of rows with an efficient driving condition. It is important to have an index on column of inner join table as this table is probed every time for a new value from outer table.

Optimizer may not use nested loop in case:

1. No of rows of both the table is quite high

2. Inner query always results in same set of records

3. The access path of inner table is independent of data coming from outer table.

Note: You will see more use of nested loop when using FIRST_ROWS optimizer mode as it works on model of showing instantaneous results to user as they are fetched. There is no need for selecting caching any data before it is returned to user. In case of hash join it is needed and is explained below.

Hash join

Hash joins are used when the joining large tables. The optimizer uses smaller of the 2 tables to build a hash table in memory and the scans the large tables and compares the hash value (of rows from large table) with this hash table to find the joined rows.

The algorithm of hash join is divided in two parts

1. Build a in-memory hash table on smaller of the two tables.

2. Probe this hash table with hash value for each row second table

In simpler terms it works like

Build phase

For each row RW1 in small (left/build) table loop

Calculate hash value on RW1 join key

Insert RW1 in appropriate hash bucket.

End loop;

Probe Phase

For each row RW2 in big (right/probe) table loop

Calculate the hash value on RW2 join key

For each row RW1 in hash table loop

If RW1 joins with RW2

Return RW1, RW2

End loop;

When optimizer uses hash join?

Optimizer uses has join while joining big tables or big fraction of small tables.

Unlike nested loop, the output of hash join result is not instantaneous as hash joining is blocked on building up hash table.

Note: You may see more hash joins used with ALL_ROWS optimizer mode, because it works on model of showing results after all the rows of at least one of the tables are hashed in hash table.

6. What factors do you consider when creating indexes on tables? How do you select the column for an index? = descDBA_IND_COLUMNS

·         SQL> desc dba_ind_columns
Name                            Null?    Type
----------------------------------------- -------- ----------------------------
INDEX_OWNER                       NOT NULL VARCHAR2(30)
INDEX_NAME                       NOT NULL VARCHAR2(30)
TABLE_OWNER                       NOT NULL VARCHAR2(30)
TABLE_NAME                       NOT NULL VARCHAR2(30)
COLUMN_NAME                             VARCHAR2(4000)
COLUMN_POSITION                  NOT NULL NUMBER
COLUMN_LENGTH                       NOT NULL NUMBER
CHAR_LENGTH                             NUMBER
DESCEND                             VARCHAR2(4)

From <https://community.oracle.com/thread/1099106>

When you are creating covering index you should keep in mind some guidelines:

· Non-key columns are defined in the INCLUDE clause of the CREATE INDEX statement.

· Non-key columns can only be defined on non-clustered indexes on tables or indexed views.

· All data types are allowed except text, ntext, and image.

· Computed columns that are deterministic and either precise or imprecise can be included columns.

· As with key columns, computed columns derived from image, ntext, and text data types can be non-key (included) columns as long as the computed column data type is allowed as a non-key index column.

· Column names cannot be specified in both the INCLUDE list and in the key column list.

· Column names cannot be repeated in the INCLUDE list.

· A maximum of 1023 additional columns can be used as non-key columns (a table can have a maximum of 1024 columns).

Performance benefit gained by using covering indexes is typically great for queries that return a large number of rows (by the way this queries are called a non-selective queries). For queries that return only a small number of rows performance is small. But here you can ask, what is the small number of rows? Small numer of rows could be 10 rows for table with hundreds of rows or 1000 rows for table with 1 000 000 rows.

Building Indexes in Ascending vs Descending Order

When you are creating indexes, often the default options are used. This options create index in ascending order. This is usually the most logical way if creating an index, but in some cases this approach wouldn’t be the best. For example when you create index on ColumnA of TableA using default options, the newest data are at the end. This works perfectly when you want to get data in ascending order from the last recent at the top to the most recent at the end. But what if you need to get the most recent data at the top?. In this case you can create index in descending order. In a few following examples I will show you hot to create indexes in different order and how they can affect performance of queries. For all following examples I will use PurchasingOrderHeader of AdventureWorks2008R2 database

From <http://www.codeproject.com/Articles/234399/Database-performance-optimization-part-Indexing>

7. If you were involved at the early stages of database development and coding, what are some of the measures you would suggest for optimal performance?

8. Is creating an index online possible?http://docs.oracle.com/cd/B28359_01/server.111/b28310/indexes003.htm>

You can create and rebuild indexes online. This enables you to update base tables at the same time you are building or rebuilding indexes on that table. You can perform DML operations while the index build is taking place, but DDL operations are not allowed. Parallel execution is not supported when creating or rebuilding an index online.

The following statements illustrate online index build operations:

CREATE INDEX emp_name ON emp (mgr, emp1, emp2, emp3) ONLINE;

Note:

Keep in mind that the time that it takes on online index build to complete is proportional to the size of the table and the number of concurrently executing DML statements. Therefore, it is best to start online index builds when DML activity is low.

See Also:

"Rebuilding an Existing Index"

9. What is the difference between Redo, Rollback and Undo?https://oraclenz.wordpress.com/2008/06/22/what-is-the-difference-between-rollback-and-undo-tablespace-otn-forum-by-user-user503050/>

REDO

Redo log files record changes to the database as a result of transactions and internal Oracle server actions. (A transaction is a logical unit of work, consisting of one or more SQL statements run by a user.)

Redo log files protect the database from the loss of integrity because of system failures caused by power outages, disk failures, and so on.

Redo log files must be multiplexed to ensure that the information stored in them is not lost in the event of a disk failure.

The redo log consists of groups of redo log files. A group consists of a redo log file and its multiplexed copies. Each identical copy is said to be a member of that group, and each group is identified by a number. The LogWriter (LGWR) process writes redo records from the redo log buffer to all members of a redo log group until the file is filled or a log switch operation is requested. Then, it switches and writes to the files in the next group. Redo log groups are used in a circular fashion.

<https://oraclenz.wordpress.com/2008/06/22/differences-between-undo-and-redo/>

There might be confusion while undo and rollback segment terms are used interchangeably in db world. It is due to the compatibility issue of oracle.

Undo

Oracle Database must have a method of maintaining information that is used to roll back, or undo, changes to the database. Such information consists of records of the actions of transactions, primarily before they are committed. These records are collectively referred to as undo.

Undo records are used to:

· Roll back transactions when a ROLLBACK statement is issued

· Recover the database

· Provide read consistency

· Analyze data as of an earlier point in time by using Flashback Query

When a ROLLBACK statement is issued, undo records are used to undo changes that were made to the database by the uncommitted transaction. During database recovery, undo records are used to undo any uncommitted changes applied from the redo log to the datafiles. Undo records provide read consistency by maintaining the before image of the data for users who are accessing the data at the same time that another user is changing it.

Undo vs Rollback

Earlier releases of Oracle Database used rollback segments to store undo. Oracle9i introduced automatic undo management, which simplifies undo space management by eliminating the complexities associated with rollback segment management. Oracle strongly recommends (Oracle 9i and on words) to use undo tablespace (automatic undo management) to manage undo rather than rollback segments.

To see the undo management mode and other undo related information of database-

SQL> show parameter undo

NAME TYPE VALUE

———————————— ———– ——————————

undo_management string AUTO

undo_retention integer 900

undo_tablespace string UNDOTBS1

Since the advent of Oracle9i, less time-consuming and suggested way is—using Automatic Undo Management—in which Oracle Database creates and manages rollback segments (now called “undo segments”) in a special-purpose undo tablespace. Unlike with rollback segments, we don’t need to create or manage individual undo segments—Oracle Database does that for you when you create the undo tablespace. All transactions in an instance share a single undo tablespace. Any executing transaction can consume free space in the undo tablespace, and when the transaction completes, its undo space is freed (depending on how it’s been sized and a few other factors, like undo retention). Thus, space for undo segments is dynamically allocated, consumed, freed, and reused—all under the control of Oracle Database, rather than manual management by someone.

Switching Rollback to Undo

1. We have to create an Undo tablespace. Oracle provides a function (10g and up) that provides information on how to size new undo tablespace based on the configuration and usage of the rollback segments in the system.

DECLARE

utbsiz_in_MB NUMBER;

BEGIN

utbsiz_in_MB ;= DBMS_UNDO_ADV.RBU_MIGRATION;

end;

CREATE UNDO TABLESPACE UNDOTBS

DATAFILE ‘/oradata/dbf/undotbs_1.dbf’

SIZE 100M AUTOEXTEND ON NEXT 10M

MAXSIZE UNLIMITED RETENTION NOGUARANTEE;

Note: In undo tablespace creation, “SEGMENT SPACE MANAGEMENT AUTO” can not be set

2.Change system parameters

SQL> alter system set undo_retention=900 scope=both;

SQL> alter system set undo_tablespace=UNDOTBS scope=both;

SQL> alter system set undo_management=AUTO scope=spfile;

SQL> shutdown immediate

SQL> startup

UNDO_MANAGEMENT is a static parameter. So database needs to be restarted.

Regards,

From <

What is Row Chaining and Row Migration? http://dba.stackexchange.com/questions/41142/how-to-check-which-background-process-are-running-in-my-oracle-database>

10. How to find out background processes?

1 select sid, process, program
2    from v$session s join v$bgprocess using (paddr)
3   where s.status = 'ACTIVE'
4*    and rownum <5
17:31:21   5 /

SID PROCESS                  PROGRAM
---------- ------------------------ ----------------------------------------------------------------
         21332                     ORACLE.EXE (PMON)
         3480                      ORACLE.EXE (PSP0)
         4976                      ORACLE.EXE (VKTM)
         5992                      ORACLE.EXE (GEN0)

Elapsed: 00:00:00.05

To maximize performance and accommodate many users, a multiprocess Oracle database system uses background processes. Background processes are the processes running behind the scene and are meant to perform certain maintenance activities or to deal with abnormal conditions arising in the instance. Each background process is meant for a specific purpose and its role is well defined.

Background processes consolidate functions that would otherwise be handled by multiple database programs running for each user process. Background processes asynchronously perform I/O and monitor other Oracle database processes to provide increased parallelism for better performance and reliability.

A background process is defined as any process that is listed in V$PROCESS and has a non-null value in the pname column.

Not all background processes are mandatory for an instance. Some are mandatory and some are optional. Mandatory background processes are DBWn, LGWR, CKPT, SMON, PMON, and RECO. All other processes are optional, will be invoked if that particular feature is activated.

Oracle background processes are visible as separate operating system processes in Unix/Linux. In Windows, these run as separate threads within the same service. Any issues related to background processes should be monitored and analyzed from the trace files generated and the alert log.

Background processes are started automatically when the instance is started.

To findout background processes from database:

SQL> select SID,PROGRAM from v$session where TYPE='BACKGROUND';

To findout background processes from OS:

$ ps -ef|grep ora_|grep SID

From <http://satya-dba.blogspot.com/2009/08/background-processes-in-oracle.html>

11. How to find background processes from OS: $ ps -ef|grep ora_|grep SID

12. How do you troubleshoot connectivity issues?

Oracle - Diagnosing Connection Problems

If you are having problems connecting to your Oracle database, then you should follow the following steps for diagnosing this:

· when you fail to connect, a file sqlnet.log is often created (see below). This can contain useful information about how the Oracle Client tried to connect, and the error it received.

· open a Windows command window and enter tnsping ORCL where ORCL is the name of the Oracle Service you are trying to connect to. If you are unsure of the Oracle Service name, from the AQT signon screen click on your Oracle database then click on Configure - the Oracle Service name is given in the field TNS Service Name.
tnsping will try to connect to the Oracle database, and will provide useful information about how it is doing this and the error it has received.

tnsnames.ora

The information about the Oracle service names, and how to connect to them, is given in the Oracle file tnsnames.ora. In many cases, connection problems have happened because the wrong tnsnames.ora file is being used.

Oracle looks at the following locations for tnsnames.ora:

· the directory referred to in environment variable TNS_ADMIN

· the directory ORACLE_HOME\network\admin. ORACLE_HOME is given in the ORACLE_HOME environment variable, or the Windows registry.

To complicate matters:

· a user may have multiple ORACLE_HOMEs

· Oracle products may have their own ORACLE_HOME (and thus tnsnames.ora). So SQL*PLUS may be using one tnsnames.ora file but (unknown to you), AQT is using another.

To clear up this uncertainty, it is recommended that the TNS_ADMIN environment variable is set to refer to directory where tnsnames.ora is located. All Oracle products and AQT will then use this tnsnames.ora file.

To view environment variables, open a Windows command window and enter SET. To permanently set an environment variable, go to the Windows Control Panel > System. Click on the Advanced tab and then the Environment Variables button (this is for Windows XP - other Windows versions may have these in a different location).

sqlnet.log

If you fail to connect, the Oracle client will generally write diagnostic information to sqlnet.log. Note that this does not include information on which tnsnames.ora file is being used, which is often the cause of many connection problems.

In earlier versions of Windows, sqlnet.log was written in the same directory as the AQT executable (eg. C:\Program Files\Advanced Query Tool v9). However for more recent versions of Windows (Windows Vista, Windows 7 and Window Server), access to the Program Files directories is restricted. As a result the file can often be created in a Virtual Store directory. You may wish to look for sqlnet.log in either:

· C:\Users\<username>\AppData\Local\VirtualStore\Program Files\Advanced Query Tool v9

· C:\Users\<username>\AppData\Local\VirtualStore\Windows\System32

Running AQT on a 64-bit version of Windows

If you are running AQT on a 64-bit version of Windows, you may fail to connect with message:

TNS could not resolve the connect identifier

This can happen due to a bug in the Oracle client in the 64-bit environment. This is described below.

By default, AQT will be installed into C:\Program Files (x86)\Advanced Query Tool v9. The Program Files (x86) directory structure is used for 32-bit applications. However there is a bug in the Oracle client - when you run a program which has a bracket in the path, the Oracle client will fail to parse tnsnames.ora correctly, resulting in the above message.

The resolution to this problem is to install AQT into a directory that doesn't have a bracket in the name.

Note that this problem has been fixed in recent versions of the Oracle Client.

From <http://www.querytool.com/help/1205.htm>

13. Why are bind variables important? Can you force literals to be converted into bind variables? YES

These simple examples clearly show how replacing literals with bind variables can save both memory and CPU, making OLTPapplications faster and more scalable. If you are using third-party applications that don't use bind variables you may want to consider setting the CURSOR_SHARING parameter, but this should not be considered a replacement for bind variables. The CURSOR_SHARING parameter is less efficient and can potentially reduce performance compared to proper use of bind variables.

From <https://oracle-base.com/articles/misc/literals-substitution-variables-and-bind-variables>

Oracle Bind Variable Tips

Oracle Tips by Michael R. Ault

The perils of Non-Use of Bind Variables in Oracle

The biggest problem in many applications is the non-use of bind variables. Oracle bind variables are a super important way to make Oracle SQL reentrant.

Why is the use of bind variables such an issue?

Oracle uses a signature generation algorithm to assign a hash value to each SQL statement based on the characters in the SQL statement. Any change in a statement (generally speaking) will result in a new hash and thus Oracle assumes it is a new statement. Each new statement must be verified, parsed and have an execution plan generated and stored, all high overhead procedures.

The high overhead procedures might be avoided by using bind variables. See these notes on Oracle cursor_sharing for details.

Ad-hoc query generators (Crystal Reports, Discoverer, Business Objects) do not use bind variables, a major reason for Oracle developing the cursor_sharing parameter to force SQL to use bind variables (when cursor_sharing=force).

Bind variables and shared pool usage

Use of bind variables can have a huge impact on the stress in the shared pool and it is important to know about locating similar SQL in Oracle. This script shows how to check your shared pool for SQL that is using bind variables. Below is an example output of a database that is utilizing bind variables and the SQL is fully reentrant:

Time: 03:15 PM Bind Variable Utilization PERFSTAT dbaville database

When SQL is placed within PL/SQL, the embedded SQL never changes and a single library cache entry will be maintained and searched, greatly improving the library cache hit ratio and reducing parsing overhead.

Here are some particularly noteworthy advantages of placing SQL within Oracle stored procedures and packages:

· High productivity: PL/SQL is a language common to all Oracle environments. Developer productivity is increased when applications are designed to use PL/SQL procedures and packages because it avoids the need to rewrite code. Also, the migration complexity to different programming environments and front-end tools will be greatly reduced because Oracle process logic code is maintained inside the database with the data, where it belongs. The application code becomes a simple “shell” consisting of calls to stored procedures and functions.

· Improved Security: Making use of the “grant execute” construct, it is possible to restrict access to Oracle, enabling the user to run only the commands that are inside the procedures. For example, it allows an end user to access one procedure that has a command delete in one particular table instead of granting the delete privilege directly to the end user. The security of the database is further improved since you can define which variables, procedures and cursors will be public and which will be private, thereby completely limiting access to those objects inside the PL/SQL package. With the “grant” security model, back doors like SQL*Plus can lead to problems; with “grant execute” you force the end-user to play by your rules.

· Application portability: Every application written in PL/SQL can be transferred to any other environment that has the Oracle Database installed regardless of the platform. Systems that consist without any embedded PL/SQL or SQL become “database agnostic” and can be moved to other platforms without changing a single line of code.

· Code Encapsulation: Placing all related stored procedures and functions into packages allows for the encapsulation of storage procedures, variables and datatypes in one single program unit in the database, making packages perfect for code organization in your applications.

· Global variables and cursors: Packages can have global variables and cursors that are available to all the procedures and functions inside the package.

From <http://www.dba-oracle.com/t_bind_variables.htm>

Writing Efficient PL/SQL

Oracle Tips by Burleson Consulting

The following Tip is from the outstanding book "Oracle PL/SQL Tuning: Expert Secrets for High Performance Programming" by Dr. Tim Hall, Oracle ACE of the year, 2006:

In this chapter we will cover a large range of techniques and concepts for improving the efficiency, memory consumption and speed of PL/SQL code. Where possible these techniques are accompanied by small working examples that will help you to understand the concepts and how they can be applied to your application code to boost performance. The first area we will focus on is the use of bind variables.

Using Bind Variables

For every statement issued against the server, Oracle searches the shared pool to see if the statement has already been parsed. If an exact text match of the statement is already present in the shared pool a soft parse is performed as the execution plan for the statement has already been created and can be reused. If the statement is not found in the shared pool a hard parse must be performed to determine the optimal execution path.

The important thing to remember from the previous paragraph is the term “exact text match”, as different numbers of spaces, literal values and case will result in a failure to find a text match, such that the following statements are considered different.

SELECT 1 FROM dual WHERE dummy = ‘X’;

SELECT 1 FROM dual WHERE dummy = ‘Y’;

SELECT 1 FROM DUAL WHERE dummy = ‘X’;

SELECT 1 FROM dual WHERE dummy = ‘X’;

The first two statements only differ by the value of the search criteria, specified using a literal. In these situations exact text matches can be achieved by replacing the literal values with bind variables that have the correct values bound to them. Using the previous example the statement passed to the server might look like this.

SELECT 1 FROM dual WHERE dummy = :B1;

For every execution the bind variable may have a different value, but the text sent to the server is the same allowing for an exact text, which results in a soft parse.

There are two main problems associated with applications that do not use bind variables:

· Parsing SQL statements is a CPU intensive process, so reparsing similar statements constantly represents a waste of CPU cycles.

· Parsed statements are stored in the shared pool until they are aged out. By not using bind variables the shared pool can rapidly become filled with similar statements, which waste memory and make the instance less efficient.

The bind_variable_usage.sql script illustrates the problems associated with not using bind variables by using dynamic SQL to simulate an application sending insert statements to the server.

bind_variable_usage.sql

CREATE TABLE bind_variables (

code VARCHAR2(10)

);

BEGIN

-- Perform insert without bind variables.

FOR i IN 1 .. 10 LOOP

BEGIN

EXECUTE IMMEDIATE

'INSERT INTO bind_variables (code) VALUES (''' || i || ''')';

EXCEPTION

WHEN NO_DATA_FOUND THEN

NULL;

END;

END LOOP;

-- Perform insert with bind variables.

FOR i IN 1 .. 10 LOOP

BEGIN

EXECUTE IMMEDIATE

'INSERT INTO bind_variables (code) VALUES (:B1)' USING TO_CHAR(i);

EXCEPTION

WHEN NO_DATA_FOUND THEN

NULL;

END;

END LOOP;

COMMIT;

END;

-- Display the associated SQL text.

COLUMN sql_text FORMAT A60

COLUMN executions FORMAT 9999

SELECT sql_text,

executions

FROM v$sql

WHERE INSTR(sql_text, 'INSERT INTO bind_variables') > 0

AND INSTR(sql_text, 'EXECUTE') = 0

ORDER BY sql_text;

DROP TABLE bind_variables;

The script starts by creating a test table and executing a simple insert statement 10 times, where the insert statement concatenates a value into the string rather than using a bind variable. Next it repeats this process but this time uses a bind variable rather than concatenating the value into the string. Finally it displays the SQL text parsed by the server and stored in the shared pool, which requires query access on the v$sql view. The results from the script are displayed below

* SQL> @bind_variable_usage.sql

Table created.

PL/SQL procedure successfully completed.

SQL_TEXT EXECUTIONS

--------------------------------------------------------- ----------

INSERT INTO bind_variables (code) VALUES ('1') 1

INSERT INTO bind_variables (code) VALUES ('10') 1

INSERT INTO bind_variables (code) VALUES ('2') 1

INSERT INTO bind_variables (code) VALUES ('3') 1

INSERT INTO bind_variables (code) VALUES ('4') 1

INSERT INTO bind_variables (code) VALUES ('5') 1

INSERT INTO bind_variables (code) VALUES ('6') 1

INSERT INTO bind_variables (code) VALUES ('7') 1

INSERT INTO bind_variables (code) VALUES ('8') 1

INSERT INTO bind_variables (code) VALUES ('9') 1

INSERT INTO bind_variables (code) VALUES (:B1) 10

11 rows selected.

Table dropped.

From this we can see that when bind variables were not used the server parsed and executed each query as a unique statement, whereas the bind variable statement was parsed once and executed 10 times. This clearly demonstrates how applications that do not use bind variables can result in wasted memory in the shared pool, along with increased CPU usage.

The cursor_sharing parameter

In some situations you are not in control of the application development process and may be forced to accept applications that do not use bind variables running against the database. In these situations you can still take advantage of bind variables by using the cursor_sharing parameter at instance or session level.

ALTER SYSTEM SET CURSOR_SHARING=FORCE;

ALTER SESSION SET CURSOR_SHARING=FORCE;

The parameter can be set to one of three values:

· EXACT – The default setting where only statements with an exact text match share the same cursor.

· SIMILAR – Statements that match except for some literal values share the same cursor, unless the literal values affect the meaning of the statement or the level of optimization.

· FORCE - Statements that match except for some literal values share the same cursor, unless the literal values affect the meaning of the statement.

If we flush the shared pool and repeat the previous test with cursor sharing set to force we see a different result.

SQL> conn sys/password as sysdba

Connected.

SQL> alter system set cursor_sharing=force;

System altered.

SQL> alter system flush shared_pool;

System altered.

SQL> conn test/test

Connected.

SQL> @bind_variable_usage.sql

Table created.

PL/SQL procedure successfully completed.

SQL_TEXT EXECUTIONS

------------------------------------------------------------ ----------

INSERT INTO bind_variables (code) VALUES (:"SYS_B_0") 10

INSERT INTO bind_variables (code) VALUES (:B1) 10

2 rows selected.

Table dropped.

Here we can see that the ten insert statements using literals have been converted to a single insert statement using a bind variable called ”SYS_B_0” which has executed ten times. The statement that already used bind variables was unaltered and also executed ten times.

The cursor_sharing feature should be considered and a last resort as the process of rewriting the queries requires extra resources. It’s far better to do the job properly in the first place rather than rely on this feature

In the next section we will see how we can gain the advantages of using bind variables within dynamic SQL.

From <http://www.dba-oracle.com/plsql/t_plsql_efficient.htm>

14. What is adaptive cursor sharing?

Adaptive cursor sharing(ACS) is another feature we've blogged about before, which allows the optimizer to generate a set of plans that are optimal for different sets of bind values. A common question is how the two interact, and whether users should consider changing the value of cursor_sharing when upgrading to 11g to take advantage of ACS. The simplest way to think about the interaction between the two features for a given query is to first consider whether literal replacement will take place for a query. Consider a query containing a literal:

select * from employees where job = 'Clerk'

From <https://blogs.oracle.com/optimizer/entry/explain_adaptive_cursor_sharing_behavior_with_cursor_sharing_similar_and_force>

15. In Data Pump, if you restart a job in Data Pump, how it will know from where to resume?

· edited: hate typing in here with an ipod. Too difficult to see the complete post.
I can say, you are missing actual point here.

My comments

If in case impdp job failed and terminated , Lets suppose process already imported 100 rows, Some how its terminated, Now your question is if you start job again it should start import after 100 >rows, i.e. from 101 rows. Of course this is not possible, You have to use options TABLE exists action as Replace/Append/Truncate.

Again, Pause & Continue Client is different, For example proactively you find some problem either from alert log file(Ex: Temp file) or at log file of Import, You can give pause Ctrl + C, again after >taking proper action you can use continue client, so that by using master table it can start import from that point.
Did you read what i mentioned here? May be understanding problem with my english.
I said, if job is paused by manually then if you resume it can continue that job from that point of time after giving continue client

If job is completely failed, i said it will start from scratch.
Maybe what I should have realized is that you think you can pause a job by typing ctl-c. This does not pause the job. All it does is pause the client. The Data Pump code that is doing the work is still happily plugging along. It is still exporting if you are running expdp, and still importing if you ran impdp. If you want to verify this, export a single table that has data and a couple of indexes. Then run an import job and remap the the schema to a schema that has nothing in it and type ctl-c after you see the table created. Make sure that you have indexes on the table. Let the job sit like this forever after typing ctl-c. In another window, run sqlplus and query the table. You will see rows in it. This is because the data pump processes are still running. Dont touch the the other window and soon enough you will see that the indexes ate created. If you want to do this with export, run a job and specify a log file. Type ctl-c after the estimate phase is complete. you will see nothing happening on the screen. In another window, tail -f the log file. You will see the log file is being written to. You will also see the dump file getting bigger.
Did you read what i mentioned here? May be understanding problem with my english.
I said, if job is paused by manually then if you resume it can continue that job from that point of time >after giving continue client

If job is completely failed, i said it will start from scratch.
This is not true. Again, you can't pause a job. If you are running export and someone does a shutdown of your database or computer then all of the data pump processes are gone and your dump file is 1/2 written. If you attach to that old job and issue a continue_client, the job will continue where it left off. If you were running import when this happened and If it was importing your payroll table data and imported everything but 1 row, when the system and database are back up, the payroll table will be empty. If you attach to the job and issue continue_client, all of the data will be loaded at that time.
Its a background job, Once you scheduled either by Crontab/Nohup, AFAIK you cant process pause in >impdp job. There would be no control with you.
ONCE AGAIN... THIS IS WRONG INFORMATION!!!!
Again - you can never pause a job. You can either stop it by

ctl-c
export> stop

or kill a job

ctl-c
export> kill

If you started the job using some script then:

expdp user/password attach=you_job_name_here
export> stop or kill
I know how to continue that job when i ran in foreground, What happens when i run by crontab or by >nohup ?
get the job name. Either by know what the script will do or by querying user_datapump_jobs or dba_datapump_jobs and then

expdp user/password attach=your_jobname_here
Can you please justify how its wrong information? I know that job can be paused and we have full >control when we run from our session(foreground).
Your job cant' be paused, and your job can be restarted even if you didn't use the client to start the job. That is why it is wrong. You have full control over a datapump job no matter how /where it was started
I'm saying when job is scheduled then you do not have control. If you have any other way please do >mention, Please note when it ran in background.
Again, if the data pump job is running, you have full control over it. You can have 20 different sessions attached to the job and all 20 dba can control it. You could change the parallel to be 20 while another dba connected to the job could add data files, while a 3rd dba attached to the job could bump the parallel value to 50.

Your understanding of what ctl-c does is what is confusing you and what makes your statements wrong. Like i said above, it does not pause the job. It just disconnects the client from the server processes. The server processes are running and exporting/importing just as they would be if there was a client attached. Typing continue will reattach it. So, that is why what you said is wrong.

If you want more tests to run, run your favorite expdp command ant type ctl-c after estimate is complete. Then at the Export> prompt, type exit. Your job will continue. If you specified a log file, it will be updated and you can tail -f it out.

Hope this clears it up for you.

Dean

Edited by: Dean Gagne on Jan 27, 2012 5:41 PM

EXAMPLES of SHELL SCRIPTING

#!/bin/bash

echo "This script does export the table COUNTRIES in C##DBA_TEST's schema"

echo `date`

sqlplus / as sysdba <<EOF

spool on

spool /u01/oracle/app/oracle/scripts/DBA_TEST.log

grant read,write on directory DBA_DATAPUMP_DIRECTORY to C##DBA_TEST;

alter user C##DBA_TEST identified by amag account unlock;

select username,table_name from dba_users,dba_tables where owner='C##DBA_TEST';

spool off

EXIT;

EOF

echo "The above are tables owned by C##DBA_TEST user.Don't forget to check logfile at /u01/oracle/app/oracle/scripts/DBA_TEST.log.We'll proceed to export the COUNTRIES table"

expdp C##DBA_TEST/amag tables=COUNTRIES directory=DATA_PUMP_DIRECTORY dumpfile=COUNTRIES.dmp logfile=COUNTRIES.log

echo "The logical backup of Table Export for C##DBA_TEST is successfully completed. Now, we shall go ahead and do a physical backup of the full database."

rman target=/ <<EOF

spool log to '/u01/oracle/app/oracle/scripts/rmanbackup.log';

list backup summary;

DELETE NOPROMPT BACKUPSET COMPLETED BEFORE 'sysdate-1';

CROSSCHECK BACKUP;

DELETE NOPROMPT EXPIRED BACKUP;

BACKUP DEVICE TYPE DISK FORMAT '/u01/oracle/app/oracle/backup/db_%d_%I_%s_%p.bkup' tag CDB FULL_DAILY_BACKUP of database;

BACKUP DEVICE TYPE DISK FORMAT '/u01/oracle/app/oracle/backup/log_%d_%I_%s_%p.bkup' tag CDB FULL_ARCHIVELOG all not _BACKED UP delete all input;

BACKUP DEVICE TYPE DISK FORMAT '/u01/oracle/app/oracle/backup/cf_%d_%U.bkup' tag CDB FULL_DAILY FULL CURRENT CONTROLFILE;

spool log off;

EXIT;

EOF

echo "Full Daily RMAN Physical backup completed successfully at `date`. Check logfile at /u01/oracle/app/oracle/scripts/rmanbackup.log"

:wq!

[oracle@localhost scripts]$ vi /u01/oracle/app/oracle/scripts/datapump.sh

[oracle@localhost scripts]$ chmod 775 /u01/oracle/app/oracle/scripts/datapump.sh

[oracle@localhost scripts]$ ll /u01/oracle/app/oracle/scripts/datapump.sh

-rwxrwxr-x. 1 oracle oracle 1462 Oct 12 08:46 /u01/oracle/app/oracle/scripts/datapump.sh

SCRIPT OUTPUT

[oracle@localhost scripts]$ /u01/oracle/app/oracle/scripts/datapump.sh

This script does export the table COUNTRIES in C##DBA_TEST's schema

Thu Oct 12 09:16:14 PDT 2017

SQL*Plus: Release 12.1.0.2.0 Production on Thu Oct 12 09:16:15 2017

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> SQL> SQL> grant read,write on directory DBA_DATAPUMP_DIRECTORY to C##DBA_TEST

ERROR at line 1:

ORA-22930: directory does not exist

SQL> alter user C##DBA_TEST identified by amag account unlock

ERROR at line 1:

ORA-28007: the password cannot be reused

SQL>

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

C##DBA_TEST

COUNTRIES

C##DUKEETOR_APP

COUNTRIES

C##DUKEETOR

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

C##TINZIM

COUNTRIES

SYSTEM

COUNTRIES

SYS

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

APEX_PUBLIC_USER

COUNTRIES

ANONYMOUS

COUNTRIES

DVF

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

APEX_040200

COUNTRIES

FLOWS_FILES

COUNTRIES

LBACSYS

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

SPATIAL_CSW_ADMIN_USR

COUNTRIES

SPATIAL_WFS_ADMIN_USR

COUNTRIES

MDDATA

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

OLAPSYS

COUNTRIES

DVSYS

COUNTRIES

SI_INFORMTN_SCHEMA

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

ORDPLUGINS

COUNTRIES

ORDDATA

COUNTRIES

ORDSYS

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

CTXSYS

COUNTRIES

OJVMSYS

COUNTRIES

WMSYS

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

GSMCATUSER

COUNTRIES

MDSYS

COUNTRIES

XDB

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

APPQOSSYS

COUNTRIES

DBSNMP

COUNTRIES

ORACLE_OCM

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

DIP

COUNTRIES

GSMUSER

COUNTRIES

GSMADMIN_INTERNAL

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

XS$NULL

COUNTRIES

OUTLN

COUNTRIES

SYSKM

COUNTRIES

USERNAME

--------------------------------------------------------------------------------

TABLE_NAME

--------------------------------------------------------------------------------

SYSDG

COUNTRIES

SYSBACKUP

COUNTRIES

AUDSYS

COUNTRIES

39 rows selected.

SQL> SQL> Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

The above are tables owned by C##DBA_TEST user.Don't forget to check logfile at /u01/oracle/app/oracle/scripts/DBA_TEST.log.We'll proceed to export the COUNTRIES table

Export: Release 12.1.0.2.0 - Production on Thu Oct 12 09:16:15 2017

Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

ORA-39001: invalid argument value

ORA-39000: bad dump file specification

ORA-31641: unable to create dump file "/u01/oracle/app/oracle/scripts/COUNTRIES.dmp"

ORA-27038: created file already exists

Additional information: 1

The logical backup of Table Export for C##DBA_TEST is successfully completed. Now, we shall go ahead and do a physical backup of the full database.

Recovery Manager: Release 12.1.0.2.0 - Production on Thu Oct 12 09:16:17 2017

connected to target database: CDB1 (DBID=828012650)

RMAN> RMAN> RMAN> RMAN> RMAN> RMAN> RMAN> RMAN> RMAN>

Spooling for log turned off

Recovery Manager12.1.0.2.0

RMAN>

Recovery Manager complete.

Full Daily RMAN Physical backup completed successfully at Thu Oct 12 09:16:19 PDT 2017. Check logfile at /u01/oracle/app/oracle/scripts/rmanbackup.log

[oracle@localhost scripts]$

==================================================================================

From <https://community.oracle.com/thread/2340182>

EXAMPLES of DATAPUMP =>expdp restart doubt

SQL> select table_name,username from dba_tables,dba_users where owner='C##DUKEETOR';

===

FIX:

===

SQL> create directory DATA_PUMP_DIRECTORY as '/u01/oracle/app/oracle/scripts';

SQL> grant read, write on directory DATA_PUMP_DIRECTORY to C##DUKEETOR;

Grant succeeded.

[oracle@localhost scripts]$ expdp C##DUKEETOR/amag tables=AMAZION directory=DATA_PUMP_DIRECTORY dumpfile=AMAZION.dmp logfile=AMAZION.log

Export: Release 12.1.0.2.0 - Production on Thu Oct 12 07:52:36 2017

Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

WARNING: Oracle Data Pump operations are not typically needed when connected to the root or seed of a container database.

Starting "C##DUKEETOR"."SYS_EXPORT_TABLE_01": C##DUKEETOR/******** tables=AMAZION directory=DATA_PUMP_DIRECTORY dumpfile=AMAZION.dmp logfile=AMAZION.log

Estimate in progress using BLOCKS method...

Processing object type TABLE_EXPORT/TABLE/TABLE_DATA

Total estimation using BLOCKS method: 64 KB

Processing object type TABLE_EXPORT/TABLE/TABLE

Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS

Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER

From <https://community.oracle.com/thread/2340182>

· Pleas Guide me how to attach job when it is running in background
I know well how to pause , its not cancel , and re attach job. If you process through background , i already mentioned >either shell script or Nohup when job processed there is no control with you.
This is documented. Le't say your initial command was:

expdp system/manager job_name=full_1_27_2012 directory=dpump_dir dumpfile=full_1_27_2012.dmp full=y

Then you can simply do this:

expdp system/manager attach=full_1_27_2012 =>resume from where JOB=full_1_27_2012 failed (e.g. after server got rebooted, etc)

This will bring you to the

EXPORT> help? (start, stop)

prompt. If the job is still running, you can then say

EXPORT> stop

IMPDP/EXPDP:

*Create directory BACKUP_DIR(oracle) as ' /u01/Test'>Grant read,write on directory BACKUP_DIR to scott/hr[ from SYS / as sysdba profile(not system user)]

-@/../Test$expdp scott/pw directory=BACKUP_DIR dumpfile=SCOTT_EXP.dmp Logfile=SCOTT_EXP.log

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

┌────────────────────────────────────────────────────────────────────┐

│ • MobaXterm Personal Edition v6.3 • │

│ (Unix utilities and X-server on Gnu/Cygwin) │

│ │

│→ Your computer drives are accessible through the /drives path │

│→ Your DISPLAY is set to 10.236.80.56:0.0 │

│→ When using SSH, your remote DISPLAY is automatically forwarded │

│→ Each command status is specified by a special symbol (v or x) │

│ │

│• Important: │

│This is MobaXterm Personal Edition. The Professional edition │

│allows you to customize MobaXterm for your company: you can add │

│your own logo, your parameters, your welcome message and generate │

│either an MSI installation package or a portable executable. │

│We can also modify MobaXterm or develop the plugins you need. │

│For more information: http://mobaxterm.mobatek.net/versions.php │

└────────────────────────────────────────────────────────────────────┘

Permanently added '10.236.28.242' (RSA) to the list of known hosts.

+---------------------------------------------------------------------+

| |

| Use of this network is restricted to authorized users only. User |

| activity may be monitored and/or recorded. Anyone using this |

| network expressly consents to such monitoring and/or recording. |

| |

| BE ADVISED: if possible criminal activity is detected, these |

| records, along with certain personal information, may be provided |

| to law enforcement officials. |

| |

+---------------------------------------------------------------------+

root@10.236.28.242's password:

Last login: Mon Sep 7 00:32:15 2015 from d2lseutsh036ag.dc2lab.local

+---------------------------------------------------------------------+

| |

| Use of this network is restricted to authorized users only. User |

| activity may be monitored and/or recorded. Anyone using this |

| network expressly consents to such monitoring and/or recording. |

| |

| BE ADVISED: if possible criminal activity is detected, these |

| records, along with certain personal information, may be provided |

| to law enforcement officials. |

| |

+---------------------------------------------------------------------+

-bash-3.2# sudo su - oracle

oracle@D2LSENPSH242[ORCLDR]# ll /u01/app/oracle/scripts

total 124

-rw-r--r-- 1 oracle oinstall 458 Oct 28 2013 sh_invalid_objects.sql

-rw-r--r-- 1 oracle oinstall 4996 Apr 22 2014 sh_tsdf.sql

-rw-r--r-- 1 oracle oinstall 452 Jul 29 2014 sh_fra.sql

-rw-r--r-- 1 oracle oinstall 175 Jul 31 2014 rman_delete_logs.txt

-rw-r--r-- 1 oracle oinstall 53 Jul 31 2014 sh_asmdisks.sql

-rw-r--r-- 1 oracle oinstall 53 Jul 31 2014 sh_asm_usage.sql

-rw-r--r-- 1 oracle oinstall 446 Jul 31 2014 sh_asm_files.sql

-rw-r--r-- 1 oracle oinstall 537 Oct 15 2014 sh_users.sql

-rw-r--r-- 1 oracle oinstall 137 Oct 15 2014 users_ORCL.txt

-rw-r--r-- 1 oracle oinstall 293 Oct 15 2014 sh_asmdisk_size.sql

-rw-r--r-- 1 oracle oinstall 465 Jan 27 2015 sh_restpnts.sql

-rw-r--r-- 1 oracle oinstall 538 Jan 27 2015 sh_reghist.sql

-rwxrwxrwx 1 oracle oinstall 1012 Feb 10 2015 delete_applied_logs_ORCLDR.sh

-rwxrwxrwx 1 oracle oinstall 17909 Feb 10 2015 rm_applied_logs.sh

-rwxrwxrwx 1 oracle oinstall 18000 Feb 10 2015 delete_applied_logs.sh

-rw-r--r-- 1 oracle oinstall 1950 Feb 10 2015 delete_applied_logs.log

-rw-r--r-- 1 oracle oinstall 630 Feb 13 2015 alogs2.sql

-rw-r--r-- 1 oracle oinstall 2726 Apr 23 16:24 tsdf_ORCL.txt

-rw-r--r-- 1 oracle oinstall 681 Apr 27 13:59 alogs.sql

-rw-r--r-- 1 oracle oinstall 713 May 4 15:57 alogs165.sql

-rw-r--r-- 1 oracle oinstall 713 May 4 15:58 alogs166.sql

-rw-r--r-- 1 oracle oinstall 395 Aug 6 12:53 asm_files.txt

oracle@D2LSENPSH242[ORCLDR]# cat sh_reghist.sql

cat: sh_reghist.sql: No such file or directory

oracle@D2LSENPSH242[ORCLDR]# cd /u01/app/oracle/scripts

oracle@D2LSENPSH242[ORCLDR]# cat sh_reghist.sql

REM ************************************************************************************************

REM sh_reghist.sql

REM list contents of registry$history

REM

REM ************************************************************************************************

SET echo off heading on

set pages 9999 lines 140

column action_time format a30

column action format a15

column namespace format a12

column version format a12

column comments format a30

column bundle_series format a14

select * from registry$history;

spool off

SET echo on

oracle@D2LSENPSH242[ORCLDR]# rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Fri Sep 18 15:57:28 2015

connected to target database (not started)

RMAN> crosscheck archivelog all;

using target database control file instead of recovery catalog

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of crosscheck command at 09/18/2015 15:57:48

RMAN-12010: automatic channel allocation initialization failed

RMAN-06403: could not obtain a fully authorized session

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

Linux-x86_64 Error: 2: No such file or directory

RMAN> show all;

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of show command at 09/18/2015 15:58:12

RMAN-06403: could not obtain a fully authorized session

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

Linux-x86_64 Error: 2: No such file or directory

RMAN> exit

Recovery Manager complete.

oracle@D2LSENPSH242[ORCLDR]# ls /u01/

app

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app

11.2.0.3 grid oracle oraInventory

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle

acfs acfsmounts admin backup cfgtoollogs checkpoints Clusterware D2LSENPSH242 diag media patches product scripts staging

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/backup

incr incr2

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/admin

+ASM LABDBDR orcl ORCLDR

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/admin/ORCLDR

adump

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/admin/orcl

adump

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/admin/LABDBDR

adump

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/admin/+ASM

pfile

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/11.2.0.3

ls: /u01/app/oracle/11.2.0.3: No such file or directory

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/11.2.0.3

grid

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oraInventory

backup ContentsXML install.platform logs oraInstaller.properties oui

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oraInventory/backup

2013-03-06_05-13-17PM 2013-03-06_12-03-21PM 2013-08-07_08-50-55PM 2013-08-14_06-34-59PM 2013-08-14_09-03-01PM 2013-08-14_09-03-30PM

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oraInventory/logs

installActions2013-03-06_04-58-02PM.log installActions2013-08-20_08-12-40PM.log OPatch2015-04-22_04-16-33-PM.log oraInstall2013-03-06_12-03-21PM.out

installActions2013-03-06_05-13-17PM.log installActions2013-08-20_08-15-30PM.log OPatch2015-07-23_05-08-13-PM.log oraInstall2013-08-07_08-50-55PM.err

installActions2013-03-06_11-33-57AM.log installActions2013-08-20_08-34-18PM.log OPatch2015-07-23_05-10-14-PM.log oraInstall2013-08-07_08-50-55PM.out

installActions2013-03-06_11-36-25AM.log installActions2013-08-20_08-41-09PM.log OPatch2015-07-23_05-13-35-PM.log oraInstall2013-08-14_06-34-59PM.err

installActions2013-03-06_11-42-00AM.log installActions2013-08-21_06-37-08PM.log OPatch2015-07-23_05-16-03-PM.log oraInstall2013-08-14_06-34-59PM.out

installActions2013-03-06_11-46-37AM.log installActions2013-08-21_06-37-22PM.log OPatch2015-07-23_05-26-44-PM.log oraInstall2013-08-14_09-03-01PM.err

installActions2013-03-06_11-48-33AM.log installActions2013-09-04_02-13-30PM.log OPatch2015-07-31_04-43-21-PM.log oraInstall2013-08-14_09-03-01PM.out

installActions2013-03-06_11-54-44AM.log OPatch2013-08-16_08-46-21-PM.log OPatch2015-08-06_03-42-12-PM.log oraInstall2013-08-14_09-03-30PM.err

installActions2013-08-07_08-50-55PM.log OPatch2013-08-16_08-59-58-PM.log OPatch2015-08-06_05-32-39-PM.log oraInstall2013-08-14_09-03-30PM.out

installActions2013-08-14_06-34-59PM.log OPatch2013-08-16_09-05-30-PM.log oraInstall2013-03-06_05-13-17PM.err oraInstall2013-08-20_08-41-09PM.err

installActions2013-08-20_06-52-37PM.log OPatch2013-10-29_08-26-14-PM.log oraInstall2013-03-06_05-13-17PM.out oraInstall2013-08-20_08-41-09PM.out

installActions2013-08-20_06-53-27PM.log OPatch2014-01-25_06-00-24-PM.log oraInstall2013-03-06_11-48-33AM.err oraInstall2013-09-04_02-13-30PM.err

installActions2013-08-20_07-19-41PM.log OPatch2014-07-30_09-39-40-PM.log oraInstall2013-03-06_11-48-33AM.out oraInstall2013-09-04_02-13-30PM.out

installActions2013-08-20_08-11-18PM.log OPatch2014-10-20_05-19-54-PM.log oraInstall2013-03-06_11-54-44AM.err UpdateNodeList2013-03-06_12-03-21PM.log

installActions2013-08-20_08-11-49PM.log OPatch2014-10-20_05-22-05-PM.log oraInstall2013-03-06_11-54-44AM.out UpdateNodeList2013-08-14_09-03-01PM.log

installActions2013-08-20_08-12-11PM.log OPatch2015-01-26_09-24-58-PM.log oraInstall2013-03-06_12-03-21PM.err UpdateNodeList2013-08-14_09-03-30PM.log

oracle@D2LSENPSH242[ORCLDR]# ls /

bin boot dev edsinfo.txt etc home lib lib64 lost+found media misc mnt opt proc root RPM sbin selinux srv sys tftpboot tmp u01 usr var

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app

11.2.0.3 grid oracle oraInventory

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle

acfs acfsmounts admin backup cfgtoollogs checkpoints Clusterware D2LSENPSH242 diag media patches product scripts staging

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/cfgtoologs

ls: /u01/app/oracle/cfgtoologs: No such file or directory

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/cfgtoollogs

asmca dbca emca netca postinstall

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/checkpoints

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/diag

asm clients crs diagtool lsnrctl netcman ofm rdbms tnslsnr

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/media

database grid OMS

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/media/database

doc install response rpm runInstaller sshsetup stage welcome.html

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/patches

oracle@D2LSENPSH242[ORCLDR]# ls /u01/app/oracle/staging

11.2.0.3

oracle@D2LSENPSH242[ORCLDR]#

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

FYI:

3123 rows selected.

=======================================

VIEWS BROKEN DOWN (alphabetically)

=====================================

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$A%';

TABLE_NAME

---------------------------------------------------------------------------

V$ACCESS

V$ACTIVE_INSTANCES

V$ACTIVE_SERVICES

V$ACTIVE_SESSION_HISTORY

V$ACTIVE_SESS_POOL_MTH

V$ADVISOR_CURRENT_SQLPLAN

V$ADVISOR_PROGRESS

V$ALERT_TYPES

V$AQ

V$AQ1

V$AQ_BACKGROUND_COORDINATOR

V$AQ_BMAP_NONDUR_SUBSCRIBERS

V$AQ_CROSS_INSTANCE_JOBS

V$AQ_JOB_COORDINATOR

V$AQ_MESSAGE_CACHE

V$AQ_MSGBM

V$AQ_NONDUR_REGISTRATIONS

V$AQ_NONDUR_SUBSCRIBER

V$AQ_NONDUR_SUBSCRIBER_LWM

V$AQ_NOTIFICATION_CLIENTS

V$AQ_SERVER_POOL

V$AQ_SUBSCRIBER_LOAD

V$ARCHIVE

V$ARCHIVED_LOG

V$ARCHIVE_DEST

V$ARCHIVE_DEST_STATUS

V$ARCHIVE_GAP

V$ARCHIVE_PROCESSES

V$ASH_INFO

V$ASM_ACFSREPL

V$ASM_ACFSREPLTAG

V$ASM_ACFSSNAPSHOTS

V$ASM_ACFSTAG

V$ASM_ACFSVOLUMES

V$ASM_ACFS_ENCRYPTION_INFO

V$ASM_ACFS_SECURITY_INFO

V$ASM_ACFS_SEC_ADMIN

V$ASM_ACFS_SEC_CMDRULE

V$ASM_ACFS_SEC_REALM

V$ASM_ACFS_SEC_REALM_FILTER

V$ASM_ACFS_SEC_REALM_GROUP

V$ASM_ACFS_SEC_REALM_USER

V$ASM_ACFS_SEC_RULE

V$ASM_ACFS_SEC_RULESET

V$ASM_ACFS_SEC_RULESET_RULE

V$ASM_ALIAS

V$ASM_ATTRIBUTE

V$ASM_AUDIT_CLEANUP_JOBS

V$ASM_AUDIT_CLEAN_EVENTS

V$ASM_AUDIT_CONFIG_PARAMS

V$ASM_AUDIT_LAST_ARCH_TS

V$ASM_CLIENT

V$ASM_DISK

V$ASM_DISKGROUP

V$ASM_DISKGROUP_STAT

V$ASM_DISK_IOSTAT

V$ASM_DISK_STAT

V$ASM_ESTIMATE

V$ASM_FILE

V$ASM_FILESYSTEM

V$ASM_OPERATION

V$ASM_TEMPLATE

V$ASM_USER

V$ASM_USERGROUP

V$ASM_USERGROUP_MEMBER

V$ASM_VOLUME

V$ASM_VOLUME_STAT

V$AW_AGGREGATE_OP

V$AW_ALLOCATE_OP

V$AW_CALC

V$AW_LONGOPS

V$AW_OLAP

V$AW_SESSION_INFO

73 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$B%';

TABLE_NAME

---------------------------------------------------------------------------

V$BACKUP

V$BACKUP_ARCHIVELOG_DETAILS

V$BACKUP_ARCHIVELOG_SUMMARY

V$BACKUP_ASYNC_IO

V$BACKUP_CONTROLFILE_DETAILS

V$BACKUP_CONTROLFILE_SUMMARY

V$BACKUP_COPY_DETAILS

V$BACKUP_COPY_SUMMARY

V$BACKUP_CORRUPTION

V$BACKUP_DATAFILE

V$BACKUP_DATAFILE_DETAILS

V$BACKUP_DATAFILE_SUMMARY

V$BACKUP_DEVICE

V$BACKUP_FILES

V$BACKUP_NONLOGGED

V$BACKUP_PIECE

V$BACKUP_PIECE_DETAILS

V$BACKUP_REDOLOG

V$BACKUP_SET

V$BACKUP_SET_DETAILS

V$BACKUP_SET_SUMMARY

V$BACKUP_SPFILE

V$BACKUP_SPFILE_DETAILS

V$BACKUP_SPFILE_SUMMARY

V$BACKUP_SYNC_IO

V$BGPROCESS

V$BH

V$BLOCKING_QUIESCE

V$BLOCK_CHANGE_TRACKING

V$BSP

V$BTS_STAT

V$BT_SCAN_CACHE

V$BT_SCAN_OBJ_TEMPS

V$BUFFERED_PUBLISHERS

V$BUFFERED_QUEUES

V$BUFFERED_SUBSCRIBERS

V$BUFFER_POOL

V$BUFFER_POOL_STATISTICS

38 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$C%';

TABLE_NAME

---------------------------------------------------------------------------

V$CACHE

V$CACHE_LOCK

V$CACHE_TRANSFER

V$CALLTAG

V$CELL

V$CELL_CONFIG

V$CELL_OFL_THREAD_HISTORY

V$CELL_REQUEST_TOTALS

V$CELL_STATE

V$CELL_THREAD_HISTORY

V$CHANNEL_WAITS

V$CIRCUIT

V$CLASS_CACHE_TRANSFER

V$CLASS_PING

V$CLIENT_SECRETS

V$CLIENT_STATS

V$CLONEDFILE

V$CLUSTER_INTERCONNECTS

V$CONFIGURED_INTERCONNECTS

V$CONTAINERS

V$CONTEXT

V$CONTROLFILE

V$CONTROLFILE_RECORD_SECTION

V$CON_SYSSTAT

V$CON_SYSTEM_EVENT

V$CON_SYSTEM_WAIT_CLASS

V$CON_SYS_TIME_MODEL

V$COPY_CORRUPTION

V$COPY_NONLOGGED

V$CORRUPT_XID_LIST

V$CPOOL_CC_INFO

V$CPOOL_CC_STATS

V$CPOOL_CONN_INFO

V$CPOOL_STATS

V$CR_BLOCK_SERVER

V$CURRENT_BLOCK_SERVER

36 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$D%';

TABLE_NAME

---------------------------------------------------------------------------

V$DLM_MISC

V$DLM_LATCH

V$DLM_CONVERT_LOCAL

V$DLM_CONVERT_REMOTE

V$DLM_ALL_LOCKS

V$DLM_LOCKS

V$DLM_RESS

V$DLM_TRAFFIC_CONTROLLER

V$DYNAMIC_REMASTER_STATS

V$DATAGUARD_STATUS

V$DBFILE

V$DATABASE

V$DISPATCHER

V$DISPATCHER_CONFIG

V$DISPATCHER_RATE

V$DB_PIPES

V$DB_OBJECT_CACHE

V$DBLINK

V$DATABASE_BLOCK_CORRUPTION

V$DELETED_OBJECT

V$DATAFILE_COPY

V$DATAFILE_HEADER

V$DATAFILE

V$DATAGUARD_CONFIG

V$DATAGUARD_STATS

V$DB_CACHE_ADVICE

V$DATABASE_INCARNATION

V$DETACHED_SESSION

V$DB_TRANSPORTABLE_PLATFORM

V$DNFS_STATS

V$DNFS_FILES

V$DNFS_SERVERS

V$DIAG_INFO

V$DNFS_CHANNELS

V$DIAG_CRITICAL_ERROR

V$DATAPUMP_JOB

V$DATAPUMP_SESSION

V$DIAG_ADR_CONTROL

V$DIAG_ADR_INVALIDATION

V$DIAG_INCIDENT

V$DIAG_PROBLEM

V$DIAG_INCCKEY

V$DIAG_INCIDENT_FILE

V$DIAG_SWEEPERR

V$DIAG_PICKLEERR

V$DIAG_VIEW

V$DIAG_VIEWCOL

V$DIAG_HM_RUN

V$DIAG_HM_FINDING

V$DIAG_HM_RECOMMENDATION

V$DIAG_HM_FDG_SET

V$DIAG_HM_INFO

V$DIAG_HM_MESSAGE

V$DIAG_DDE_USER_ACTION_DEF

V$DIAG_DDE_USR_ACT_PARAM_DEF

V$DIAG_DDE_USER_ACTION

V$DIAG_DDE_USR_ACT_PARAM

V$DIAG_DDE_USR_INC_TYPE

V$DIAG_DDE_USR_INC_ACT_MAP

V$DIAG_IPS_PACKAGE

V$DIAG_IPS_PACKAGE_INCIDENT

V$DIAG_IPS_PACKAGE_FILE

V$DIAG_IPS_FILE_METADATA

V$DIAG_IPS_FILE_COPY_LOG

V$DIAG_IPS_PACKAGE_HISTORY

V$DIAG_IPS_PKG_UNPACK_HIST

V$DIAG_IPS_REMOTE_PACKAGE

V$DIAG_IPS_CONFIGURATION

V$DIAG_INC_METER_SUMMARY

V$DIAG_INC_METER_INFO

V$DIAG_INC_METER_CONFIG

V$DIAG_INC_METER_IMPT_DEF

V$DIAG_INC_METER_PK_IMPTS

V$DIAG_DIR_EXT

V$DIAG_ALERT_EXT

V$DIAG_RELMD_EXT

V$DIAG_EM_USER_ACTIVITY

V$DIAG_EM_DIAG_JOB

V$DIAG_EM_TARGET_INFO

V$DIAG_AMS_XACTION

V$DIAG_VSHOWINCB

V$DIAG_VSHOWINCB_I

V$DIAG_V_INCFCOUNT

V$DIAG_V_NFCINC

V$DIAG_VSHOWCATVIEW

V$DIAG_VINCIDENT

V$DIAG_VINC_METER_INFO

V$DIAG_VIPS_FILE_METADATA

V$DIAG_VIPS_PKG_FILE

V$DIAG_VIPS_PACKAGE_FILE

V$DIAG_VIPS_PACKAGE_HISTORY

V$DIAG_VIPS_FILE_COPY_LOG

V$DIAG_VIPS_PACKAGE_SIZE

V$DIAG_VIPS_PKG_INC_DTL1

V$DIAG_VIPS_PKG_INC_DTL

V$DIAG_VINCIDENT_FILE

V$DIAG_V_INCCOUNT

V$DIAG_V_IPSPRBCNT1

V$DIAG_V_IPSPRBCNT

V$DIAG_VPROBLEM_LASTINC

V$DIAG_VPROBLEM_INT

V$DIAG_VEM_USER_ACTLOG

V$DIAG_VEM_USER_ACTLOG1

V$DIAG_VPROBLEM1

V$DIAG_VPROBLEM2

V$DIAG_V_INC_METER_INFO_PROB

V$DIAG_VPROBLEM

V$DIAG_VPROBLEM_BUCKET1

V$DIAG_VPROBLEM_BUCKET

V$DIAG_VPROBLEM_BUCKET_COUNT

V$DIAG_VHM_RUN

V$DIAG_DIAGV_INCIDENT

V$DIAG_VIPS_PACKAGE_MAIN_INT

V$DIAG_VIPS_PKG_MAIN_PROBLEM

V$DIAG_V_ACTINC

V$DIAG_V_ACTPROB

V$DIAG_V_SWPERRCOUNT

V$DIAG_VIPS_PKG_INC_CAND

V$DIAG_VNOT_EXIST_INCIDENT

V$DIAG_VTEST_EXISTS

V$DISK_RESTORE_RANGE

V$DATABASE_KEY_INFO

V$DIAG_IPS_PROGRESS_LOG

V$DIAG_DFW_CONFIG_CAPTURE

V$DIAG_DFW_CONFIG_ITEM

V$DEAD_CLEANUP

V$DG_BROKER_CONFIG

127 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$E%';

TABLE_NAME

---------------------------------------------------------------------------

V$EDITIONABLE_TYPES

V$EMON

V$ENABLEDPRIVS

V$ENCRYPTED_TABLESPACES

V$ENCRYPTION_KEYS

V$ENCRYPTION_WALLET

V$ENQUEUE_LOCK

V$ENQUEUE_STAT

V$ENQUEUE_STATISTICS

V$EVENTMETRIC

V$EVENT_HISTOGRAM

V$EVENT_NAME

V$EXECUTION

13 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$F%';

TABLE_NAME

---------------------------------------------------------------------------

V$FALSE_PING

V$FAST_START_SERVERS

V$FAST_START_TRANSACTIONS

V$FILEMETRIC

V$FILEMETRIC_HISTORY

V$FILESPACE_USAGE

V$FILESTAT

V$FILE_CACHE_TRANSFER

V$FILE_HISTOGRAM

V$FILE_OPTIMIZED_HISTOGRAM

V$FILE_PING

V$FIXED_TABLE

V$FIXED_VIEW_DEFINITION

V$FLASHBACK_DATABASE_LOG

V$FLASHBACK_DATABASE_LOGFILE

V$FLASHBACK_DATABASE_STAT

V$FLASHBACK_TXN_GRAPH

V$FLASHBACK_TXN_MODS

V$FLASHFILESTAT

V$FLASH_RECOVERY_AREA_USAGE

V$FOREIGN_ARCHIVED_LOG

V$FS_FAILOVER_HISTOGRAM

V$FS_FAILOVER_STATS

23 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$G%';

TABLE_NAME

---------------------------------------------------------------------------

V$GCSHVMASTER_INFO

V$GCSPFMASTER_INFO

V$GC_ELEMENT

V$GC_ELEMENTS_WITH_COLLISIONS

V$GES_BLOCKING_ENQUEUE

V$GES_DEADLOCKS

V$GES_DEADLOCK_SESSIONS

V$GES_ENQUEUE

V$GG_APPLY_COORDINATOR

V$GG_APPLY_READER

V$GG_APPLY_RECEIVER

V$GG_APPLY_SERVER

V$GLOBALCONTEXT

V$GLOBAL_BLOCKED_LOCKS

V$GLOBAL_TRANSACTION

V$GOLDENGATE_CAPABILITIES

V$GOLDENGATE_CAPTURE

V$GOLDENGATE_MESSAGE_TRACKING

V$GOLDENGATE_TABLE_STATS

V$GOLDENGATE_TRANSACTION

20 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$H%';

TABLE_NAME

---------------------------------------------------------------------------

V$HANG_INFO

V$HANG_SESSION_INFO

V$HANG_STATISTICS

V$HEAT_MAP_SEGMENT

V$HM_CHECK

V$HM_CHECK_PARAM

V$HM_FINDING

V$HM_INFO

V$HM_RECOMMENDATION

V$HM_RUN

V$HS_AGENT

V$HS_PARAMETER

V$HS_SESSION

V$HVMASTER_INFO

14 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$I%';

TABLE_NAME

---------------------------------------------------------------------------

V$INCMETER_CONFIG

V$INCMETER_INFO

V$INCMETER_SUMMARY

V$INDEXED_FIXED_COLUMN

V$INSTANCE

V$INSTANCE_CACHE_TRANSFER

V$INSTANCE_LOG_GROUP

V$INSTANCE_PING

V$INSTANCE_RECOVERY

V$IOFUNCMETRIC

V$IOFUNCMETRIC_HISTORY

V$IOSTAT_CONSUMER_GROUP

V$IOSTAT_FILE

V$IOSTAT_FUNCTION

V$IOSTAT_FUNCTION_DETAIL

V$IOSTAT_NETWORK

V$IOS_CLIENT

V$IO_CALIBRATION_STATUS

V$IO_OUTLIER

V$IR_FAILURE

V$IR_FAILURE_SET

V$IR_MANUAL_CHECKLIST

V$IR_REPAIR

23 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$J%';

TABLE_NAME

---------------------------------------------------------------------------

V$JAVAPOOL

V$JAVA_LIBRARY_CACHE_MEMORY

V$JAVA_POOL_ADVICE

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$K%';

TABLE_NAME

---------------------------------------------------------------------------

V$KERNEL_IO_OUTLIER

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$L%';

TABLE_NAME

---------------------------------------------------------------------------

V$LATCH

V$LATCHHOLDER

V$LATCHNAME

V$LATCH_CHILDREN

V$LATCH_MISSES

V$LATCH_PARENT

V$LGWRIO_OUTLIER

V$LIBCACHE_LOCKS

V$LIBRARYCACHE

V$LIBRARY_CACHE_MEMORY

V$LICENSE

V$LISTENER_NETWORK

V$LOADISTAT

V$LOADPSTAT

V$LOBSTAT

V$LOCK

V$LOCKED_OBJECT

V$LOCKS_WITH_COLLISIONS

V$LOCK_ACTIVITY

V$LOCK_ELEMENT

V$LOCK_TYPE

V$LOG

V$LOGFILE

V$LOGHIST

V$LOGMNR_CONTENTS

V$LOGMNR_DICTIONARY

V$LOGMNR_DICTIONARY_LOAD

V$LOGMNR_LATCH

V$LOGMNR_LOGFILE

V$LOGMNR_LOGS

V$LOGMNR_PARAMETERS

V$LOGMNR_PROCESS

V$LOGMNR_SESSION

V$LOGMNR_STATS

V$LOGMNR_TRANSACTION

V$LOGSTDBY

V$LOGSTDBY_PROCESS

V$LOGSTDBY_PROGRESS

V$LOGSTDBY_STATE

V$LOGSTDBY_STATS

V$LOGSTDBY_TRANSACTION

V$LOG_HISTORY

42 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$M%';

TABLE_NAME

---------------------------------------------------------------------------

V$MANAGED_STANDBY

V$MAPPED_SQL

V$MAP_COMP_LIST

V$MAP_ELEMENT

V$MAP_EXT_ELEMENT

V$MAP_FILE

V$MAP_FILE_EXTENT

V$MAP_FILE_IO_STACK

V$MAP_LIBRARY

V$MAP_SUBELEMENT

V$MAX_ACTIVE_SESS_TARGET_MTH

V$MEMORY_CURRENT_RESIZE_OPS

V$MEMORY_DYNAMIC_COMPONENTS

V$MEMORY_RESIZE_OPS

V$MEMORY_TARGET_ADVICE

V$METRIC

V$METRICGROUP

V$METRICNAME

V$METRIC_HISTORY

V$MTTR_TARGET_ADVICE

V$MUTEX_SLEEP

V$MUTEX_SLEEP_HISTORY

V$MVREFRESH

V$MYSTAT

24 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$N%';

TABLE_NAME

---------------------------------------------------------------------------

V$NFS_CLIENTS

V$NFS_LOCKS

V$NFS_OPEN_FILES

V$NLS_PARAMETERS

V$NLS_VALID_VALUES

V$NONLOGGED_BLOCK

6 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$O%';

TABLE_NAME

---------------------------------------------------------------------------

V$OBJECT_DEPENDENCY

V$OBJECT_DML_FREQUENCIES

V$OBJECT_PRIVILEGE

V$OBJECT_USAGE

V$OBSOLETE_PARAMETER

V$OFFLINE_RANGE

V$OFSMOUNT

V$OFS_STATS

V$OPEN_CURSOR

V$OPTIMIZER_PROCESSING_RATE

V$OPTION

V$OSSTAT

12 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$P%';

TABLE_NAME

---------------------------------------------------------------------------

V$PARALLEL_DEGREE_LIMIT_MTH

V$PARAMETER

V$PARAMETER2

V$PARAMETER_VALID_VALUES

V$PATCHES

V$PDBS

V$PDB_INCARNATION

V$PERSISTENT_PUBLISHERS

V$PERSISTENT_QMN_CACHE

V$PERSISTENT_QUEUES

V$PERSISTENT_SUBSCRIBERS

V$PGASTAT

V$PGA_TARGET_ADVICE

V$PGA_TARGET_ADVICE_HISTOGRAM

V$PING

V$POLICY_HISTORY

V$PQ_SESSTAT

V$PQ_SLAVE

V$PQ_SYSSTAT

V$PQ_TQSTAT

V$PROCESS

V$PROCESS_GROUP

V$PROCESS_MEMORY

V$PROCESS_MEMORY_DETAIL

V$PROCESS_MEMORY_DETAIL_PROG

V$PROPAGATION_RECEIVER

V$PROPAGATION_SENDER

V$PROXY_ARCHIVEDLOG

V$PROXY_ARCHIVELOG_DETAILS

V$PROXY_ARCHIVELOG_SUMMARY

V$PROXY_COPY_DETAILS

V$PROXY_COPY_SUMMARY

V$PROXY_DATAFILE

V$PWFILE_USERS

V$PX_BUFFER_ADVICE

V$PX_INSTANCE_GROUP

V$PX_PROCESS

V$PX_PROCESS_SYSSTAT

V$PX_PROCESS_TRACE

V$PX_SESSION

V$PX_SESSTAT

41 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$Q%';

TABLE_NAME

---------------------------------------------------------------------------

V$QMON_COORDINATOR_STATS

V$QMON_SERVER_STATS

V$QMON_TASKS

V$QMON_TASK_STATS

V$QUEUE

V$QUEUEING_MTH

6 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$R%';

TABLE_NAME

---------------------------------------------------------------------------

V$RECOVERY_AREA_USAGE

V$RECOVERY_FILE_DEST

V$RECOVERY_FILE_STATUS

V$RECOVERY_LOG

V$RECOVERY_PROGRESS

V$RECOVERY_STATUS

V$RECOVER_FILE

V$REDO_DEST_RESP_HISTOGRAM

V$REPLAY_CONTEXT

V$REPLAY_CONTEXT_LOB

V$REPLAY_CONTEXT_SEQUENCE

V$REPLAY_CONTEXT_SYSDATE

V$REPLAY_CONTEXT_SYSGUID

V$REPLAY_CONTEXT_SYSTIMESTAMP

V$REPLPROP

V$REPLQUEUE

V$REQDIST

V$RESERVED_WORDS

V$RESOURCE

V$RESOURCE_LIMIT

V$RESTORE_POINT

V$RESTORE_RANGE

V$RESULT_CACHE_DEPENDENCY

V$RESULT_CACHE_MEMORY

V$RESULT_CACHE_OBJECTS

V$RESULT_CACHE_STATISTICS

V$RESUMABLE

V$RFS_THREAD

V$RMAN_BACKUP_JOB_DETAILS

V$RMAN_BACKUP_SUBJOB_DETAILS

V$RMAN_BACKUP_TYPE

V$RMAN_COMPRESSION_ALGORITHM

V$RMAN_CONFIGURATION

V$RMAN_ENCRYPTION_ALGORITHMS

V$RMAN_OUTPUT

V$RMAN_STATUS

V$ROLLNAME

V$ROLLSTAT

V$ROWCACHE

V$ROWCACHE_PARENT

V$ROWCACHE_SUBORDINATE

V$RO_USER_ACCOUNT

V$RSRCMGRMETRIC

V$RSRCMGRMETRIC_HISTORY

V$RSRC_CONSUMER_GROUP

V$RSRC_CONSUMER_GROUP_CPU_MTH

V$RSRC_CONS_GROUP_HISTORY

V$RSRC_PLAN

V$RSRC_PLAN_CPU_MTH

V$RSRC_PLAN_HISTORY

V$RSRC_SESSION_INFO

V$RT_ADDM_CONTROL

V$RULE

V$RULE_SET

V$RULE_SET_AGGREGATE_STATS

55 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$S%';

TABLE_NAME

---------------------------------------------------------------------------

V$SQL_REDIRECTION

V$SQL_PLAN

V$SQL_PLAN_STATISTICS

V$SQL_PLAN_STATISTICS_ALL

V$SQL_WORKAREA

V$SQL_WORKAREA_ACTIVE

V$SQL_WORKAREA_HISTOGRAM

V$SYS_OPTIMIZER_ENV

V$SES_OPTIMIZER_ENV

V$SQL_OPTIMIZER_ENV

V$SQLFN_METADATA

V$SQLFN_ARG_METADATA

V$STANDBY_LOG

V$SESSION

V$SESSION_LONGOPS

V$SESSTAT

V$SUBCACHE

V$SYSSTAT

V$STATNAME

V$SGA

V$SYSTEM_PARAMETER

V$SYSTEM_PARAMETER2

V$SPPARAMETER

V$SQLAREA

V$SQLAREA_PLAN_HASH

V$SQLTEXT

V$SQLTEXT_WITH_NEWLINES

V$SQL

V$SQL_SHARED_CURSOR

V$SHARED_SERVER_MONITOR

V$SGASTAT

V$SGAINFO

V$SHARED_SERVER

V$STATISTICS_LEVEL

V$SESSION_CURSOR_CACHE

V$SESSION_WAIT_CLASS

V$SESSION_WAIT

V$SESSION_WAIT_HISTORY

V$SESSION_BLOCKERS

V$SESSION_EVENT

V$SESSION_CONNECT_INFO

V$SYSTEM_WAIT_CLASS

V$SYSTEM_EVENT

V$SYSTEM_CURSOR_CACHE

V$SESS_IO

V$SHARED_POOL_RESERVED

V$SORT_SEGMENT

V$SORT_USAGE

V$SQL_CURSOR

V$SQL_BIND_METADATA

V$SQL_BIND_DATA

V$SQL_SHARED_MEMORY

V$SESSION_OBJECT_CACHE

V$STANDBY_EVENT_HISTOGRAM

V$SGA_TARGET_ADVICE

V$SEGMENT_STATISTICS

V$SEGSTAT_NAME

V$SEGSTAT

V$SHARED_POOL_ADVICE

V$STREAMS_POOL_ADVICE

V$SGA_CURRENT_RESIZE_OPS

V$SGA_RESIZE_OPS

V$SGA_DYNAMIC_COMPONENTS

V$SGA_DYNAMIC_FREE_MEMORY

V$SYSMETRIC

V$SYSMETRIC_HISTORY

V$SERVICE_WAIT_CLASS

V$SERVICE_EVENT

V$SERVICES

V$SYSMETRIC_SUMMARY

V$SESSMETRIC

V$SERVICEMETRIC

V$SERVICEMETRIC_HISTORY

V$SQLPA_METRIC

V$SQL_JOIN_FILTER

V$SQLSTATS

V$SQLSTATS_PLAN_HASH

V$SYSAUX_OCCUPANTS

V$SCHEDULER_RUNNING_JOBS

V$SUBSCR_REGISTRATION_STATS

V$SYSTEM_FIX_CONTROL

V$SESSION_FIX_CONTROL

V$SQL_FEATURE

V$SQL_FEATURE_HIERARCHY

V$SQL_FEATURE_DEPENDENCY

V$SQL_HINT

V$SQL_CS_HISTOGRAM

V$SQL_CS_SELECTIVITY

V$SQL_CS_STATISTICS

V$SQL_MONITOR

V$SQL_PLAN_MONITOR

V$SSCR_SESSIONS

V$SECUREFILE_TIMER

V$SQLCOMMAND

V$SERV_MOD_ACT_STATS

V$SERVICE_STATS

V$SYS_TIME_MODEL

V$SESS_TIME_MODEL

V$STREAMS_CAPTURE

V$STREAMS_APPLY_COORDINATOR

V$STREAMS_APPLY_SERVER

V$STREAMS_APPLY_READER

V$STREAMS_TRANSACTION

V$STREAMS_MESSAGE_TRACKING

V$STREAMS_POOL_STATISTICS

V$SQL_BIND_CAPTURE

V$SBT_RESTORE_RANGE

V$SEGSPACE_USAGE

V$SQL_REOPTIMIZATION_HINTS

V$SYS_REPORT_STATS

V$SYS_REPORT_REQUESTS

V$SESSIONS_COUNT

V$SCHEDULER_INMEM_RTINFO

V$SCHEDULER_INMEM_MDINFO

V$SQL_DIAG_REPOSITORY

V$SQL_DIAG_REPOSITORY_REASON

V$SQL_MONITOR_STATNAME

V$SQL_MONITOR_SESSTAT

118 rows selected.

SQL>

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$T%';

TABLE_NAME

---------------------------------------------------------------------------

V$TABLESPACE

V$TEMPFILE

V$TEMPORARY_LOBS

V$TEMPSEG_USAGE

V$TEMPSTAT

V$TEMPUNDOSTAT

V$TEMP_CACHE_TRANSFER

V$TEMP_EXTENT_MAP

V$TEMP_EXTENT_POOL

V$TEMP_PING

V$TEMP_SPACE_HEADER

V$THREAD

V$THRESHOLD_TYPES

V$TIMER

V$TIMEZONE_FILE

V$TIMEZONE_NAMES

V$TOPLEVELCALL

V$TRANSACTION

V$TRANSACTION_ENQUEUE

V$TRANSPORTABLE_PLATFORM

V$TSDP_SUPPORTED_FEATURE

V$TSM_SESSIONS

V$TYPE_SIZE

23 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$U%';

TABLE_NAME

---------------------------------------------------------------------------

V$UNDOSTAT

V$UNIFIED_AUDIT_RECORD_FORMAT

V$UNIFIED_AUDIT_TRAIL

V$UNUSABLE_BACKUPFILE_DETAILS

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$V%';

TABLE_NAME

---------------------------------------------------------------------------

V$VERSION

V$VPD_POLICY

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$W%';

TABLE_NAME

---------------------------------------------------------------------------

V$WAITCLASSMETRIC

V$WAITCLASSMETRIC_HISTORY

V$WAITSTAT

V$WAIT_CHAINS

V$WALLET

V$WLM_PCMETRIC

V$WLM_PCMETRIC_HISTORY

V$WLM_PC_STATS

V$WORKLOAD_REPLAY_THREAD

9 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$X%';

TABLE_NAME

---------------------------------------------------------------------------

V$XML_AUDIT_TRAIL

V$XSTREAM_APPLY_COORDINATOR

V$XSTREAM_APPLY_READER

V$XSTREAM_APPLY_RECEIVER

V$XSTREAM_APPLY_SERVER

V$XSTREAM_CAPTURE

V$XSTREAM_MESSAGE_TRACKING

V$XSTREAM_OUTBOUND_SERVER

V$XSTREAM_TABLE_STATS

V$XSTREAM_TRANSACTION

V$XS_SESSIONS

V$XS_SESSION_NS_ATTRIBUTE

V$XS_SESSION_NS_ATTRIBUTES

V$XS_SESSION_ROLES

14 rows selected.

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$Y%';

no rows selected

SQL> select TABLE_NAME from DICTIONARY where TABLE_NAME like 'V$Z%';

no rows selected

======DBA Views============

* dba_all_tables

* dba_indexes

* dba_ind_partitions

* dba_ind_subpartitions

* dba_object_tables

* dba_part_col_statistics

* dba_subpart_col_statistics

* dba_tables

* dba_tab_cols

* dba_tab_columns

* dba_tab_col_statistics

* dba_tab_partitions

* dba_tab_subpartitions

· DBA_DB_LINKS - All DB links defined in the database

· ALL_DB_LINKS - All DB links the current user has access to

· USER_DB_LINKS - All DB links owned by current user

· e.g

SELECT DB_LINK, USERNAME, HOST FROM ALL_DB_LINKS

1. Know everything about any USER account in ORACLE database from dba_users/user_users/all_users

USERS

SQL> desc dba_users

Name Null? Type

------------------------------------------------------------------------------- ---------------------------------------------------------------- -------- ------ -------------------------------------------------------------------------------- ----------

USERNAME NOT NULL VARCHAR2(128)

USER_ID NOT NULL NUMBER

PASSWORD VARCHAR2(4000)

ACCOUNT_STATUS NOT NULL VARCHAR2(32)

LOCK_DATE DATE

EXPIRY_DATE DATE

DEFAULT_TABLESPACE NOT NULL VARCHAR2(30)

TEMPORARY_TABLESPACE NOT NULL VARCHAR2(30)

CREATED NOT NULL DATE

PROFILE NOT NULL VARCHAR2(128)

INITIAL_RSRC_CONSUMER_GROUP VARCHAR2(128)

EXTERNAL_NAME VARCHAR2(4000)

PASSWORD_VERSIONS VARCHAR2(12)

EDITIONS_ENABLED VARCHAR2(1)

AUTHENTICATION_TYPE VARCHAR2(8)

PROXY_ONLY_CONNECT VARCHAR2(1)

VARCHAR2(1)

COMMON VARCHAR2(3)

LAST_LOGIN TIMESTAMP(9) WITH TIME ZONE

ORACLE_MAINTAINED VARCHAR2(1)

2. Know everything about TABLES in your ORACLE database from dba_tables/user_tables/all_tables

SQL>desc dba_tables

Name Null? Type

----------------------------------------------------------------------------------------------------------------------------------------------- -------- ------------------------------------------------------------------------------------------------

OWNER NOT NULL VARCHAR2(128)

TABLE_NAME NOT NULL VARCHAR2(128)

TABLESPACE_NAME VARCHAR2(30)

CLUSTER_NAME VARCHAR2(128)

IOT_NAME VARCHAR2(128)

STATUS VARCHAR2(8)

PCT_FREE NUMBER

PCT_USED NUMBER

INI_TRANS NUMBER

MAX_TRANS NUMBER

INITIAL_EXTENT NUMBER

NEXT_EXTENT NUMBER

MIN_EXTENTS NUMBER

MAX_EXTENTS NUMBER

PCT_INCREASE NUMBER

FREELISTS NUMBER

FREELIST_GROUPS NUMBER

LOGGING VARCHAR2(3)

BACKED_UP VARCHAR2(1)

NUM_ROWS NUMBER

BLOCKS NUMBER

EMPTY_BLOCKS NUMBER

AVG_SPACE NUMBER

CHAIN_CNT NUMBER

AVG_ROW_LEN NUMBER

AVG_SPACE_FREELIST_BLOCKS NUMBER

NUM_FREELIST_BLOCKS NU

NUM_FREELIST_BLOCKS NUMBER

DEGREE VARCHAR2(10)

INSTANCES VARCHAR2(10)

CACHE VARCHAR2(5)

TABLE_LOCK VARCHAR2(8)

SAMPLE_SIZE NUMBER

LAST_ANALYZED DATE

PARTITIONED VARCHAR2(3)

IOT_TYPE VARCHAR2(12)

TEMPORARY VARCHAR2(1)

SECONDARY VARCHAR2(1)

NESTED VARCHAR2(3)

BUFFER_POOL VARCHAR2(7)

FLASH_CACHE VARCHAR2(7)

CELL_FLASH_CACHE VARCHAR2(7)

ROW_MOVEMENT VARCHAR2(8)

GLOBAL_STATS VARCHAR2(3)

USER_STATS VARCHAR2(3)

DURATION VARCHAR2(15)

SKIP_CORRUPT VARCHAR2(8)

MONITORING VARCHAR2(3)

CLUSTER_OWNER VARCHAR2(128)

DEPENDENCIES VARCHAR2(8)

COMPRESSION VARCHAR2(8)

COMPRESS_FOR VARCHAR2(30)

DROPPED VARCHAR2(3)

READ_ONLY VARCHAR2(3)

SEGMENT_CREATED VARCHAR2(3)

RESULT_CACHE VARCHAR2(7)

CLUSTERING VARCHAR2(3)

ACTIVITY_TRACKING VARCHAR2(23)

DML_TIMESTAMP VARCHAR2(25)

HAS_IDENTITY VARCHAR2(3)

CONTAINER_DATA VARCHAR2(3)

3. Know everything about any DATA FILES (Users data)in ORACLE database from dba_data_files/user_data_files/all_data_files

SQL>desc dba_data_files

Name Null? Type

----------------------------------------------------------------------------------------------------------------------------------------------- -------- ------------------------------------------------------------------------------------------------

FILE_NAME VARCHAR2(513)

FILE_ID NUMBER

TABLESPACE_NAME VARCHAR2(30)

BYTES NUMBER

BLOCKS NUMBER

STATUS VARCHAR2(9)

RELATIVE_FNO NUMBER

AUTOEXTENSIBLE VARCHAR2(3)

MAXBYTES NUMBER

MAXBLOCKS NUMBER

INCREMENT_BY NUMBER

USER_BYTES NUMBER

USER_BLOCKS NUMBER

ONLINE_STATUS VARCHAR2(7)

4. Know everything about any DIRECTORY(Oracle dir mapped to O/S(linux) dir)in ORACLE database from dba_directories/user_directories/all_directories

5. SQL> desc dba_directories

Name Null? Type

----------------------------------------------------------------------------------------------------------------------------------------------- -------- ------------------------------------------------------------------------------------------------

OWNER NOT NULL VARCHAR2(128)

DIRECTORY_NAME NOT NULL VARCHAR2(128)

DIRECTORY_PATH VARCHAR2(4000)

ORIGIN_CON_ID NUMBER

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

+mailto:kenneth.chando@associates.hq.dhs.gov

Thank you for your feedback |Recognition@hp

-rwxr-x--- 1 oracle oinstall 2134 Apr 23 14:13 dbup.sh

-rw-r--r-- 1 oracle oinstall 13788 Sep 30 01:01 delete_archlogs.log

-rw-r--r-- 1 oracle oinstall 25378 Jun 23 18:00 delete_archlogs.log.20150623180 0

-rw-r--r-- 1 oracle oinstall 99409 Jun 23 19:00 delete_archlogs.log.2015062319

-rwxr-x--- 1 oracle oinstall 272 Jun 25 18:46 delete_archlogs.sh

-rw-r--r-- 1 oracle oinstall 25730 Apr 13 2010 dfltpass.sql

-rw-r--r-- 1 oracle oinstall 1478 Apr 13 2010 df.sql

-rw-r--r-- 1 oracle oinstall 790 Apr 13 2010 endbackup.sql

-rw-r--r-- 1 oracle oinstall 1771 Apr 13 2010 g2b.sql

-rw-r--r-- 1 oracle oinstall 208 Apr 15 2010 gen_user_default.sql

-rwxr-x--- 1 oracle oinstall 878 Apr 23 14:13 grant_readonly.sh

-rw-r--r-- 1 oracle oinstall 110971 Sep 2 2010 grant_readonly.sql

-rw-r--r-- 1 oracle oinstall 15091 Apr 13 2010 hardening.sql

-rw-r--r-- 1 oracle oinstall 212 Apr 13 2010 invalid_objects.sql

-rwxr-x--- 1 oracle oinstall 1637 Apr 23 14:13 ldf.sh

-rw-r--r-- 1 oracle oinstall 468 May 1 17:16 metrics_database_resource.txt

-rwxr-x--- 1 oracle oinstall 5235 Apr 23 14:13 nb_arc_backup_BASSD.sh

-rw-rw-rw- 1 root root 3947 Apr 23 19:44 nb_arc_backup_BASSD.sh.out

-rwxr-x--- 1 oracle oinstall 5235 Apr 23 14:13 nb_arc_backup_DBSID.sh

-rwxr-x--- 1 oracle oinstall 11546 Apr 23 14:13 nb_hot_backup_BASSD.sh

-rwxr-x--- 1 oracle oinstall 11838 Apr 22 17:04 nb_hot_backup_BASSD.sh.old

-rw-rw-rw- 1 root root 3082 Apr 24 11:24 nb_hot_backup_BASSD.sh.out

-rwxr-x--- 1 oracle oinstall 11546 Apr 23 14:13 nb_hot_backup_DBSID.sh

-rw-r--r-- 1 oracle oinstall 52463 Apr 13 2010 Oracle_test_script_v4.sql

-rw-r--r-- 1 oracle oinstall 4550 Apr 15 2010 recompile_invalid_objects.sql

-rw-r--r-- 1 oracle oinstall 354 Apr 13 2010 redo_logs.sql

-rw-r--r-- 1 oracle oinstall 12374 Sep 3 22:52 rmanbackup_BASSD_disk_full_keep .log

-rwxr-x--- 1 oracle oinstall 478 May 21 15:00 rmanbackup_BASSD_disk_full_keep .sh

-rw-r--r-- 1 oracle oinstall 7722 Sep 27 00:48 rmanbackup_BASSD_disk_full.log

-rwxr-x--- 1 oracle oinstall 654 Jun 24 15:16 rmanbackup_BASSD_disk_full.sh

-rw-r--r-- 1 oracle oinstall 12102 Sep 30 01:18 rmanbackup_BASSD_disk_inc.log

-rwxr-x--- 1 oracle oinstall 556 Jun 24 15:15 rmanbackup_BASSD_disk_inc.sh

-rwxr-x--- 1 oracle oinstall 1258 Apr 23 15:56 rmanbackup_BASSD_sbt.sh

-rwxr-x--- 1 oracle oinstall 1250 Apr 23 14:13 rmanbackup_DBSID_sbt.sh

-rwxr-x--- 1 oracle oinstall 469 Apr 23 14:13 rmanbackup_log.sh

-rwxr-x--- 1 oracle oinstall 699 Apr 23 14:13 rmanbackup.sh

-rw-r--r-- 1 oracle oinstall 31228 Apr 13 2010 rpt_db_tuning.sql

-rw-r--r-- 1 oracle oinstall 22293 Apr 23 15:01 rpt_hardening_BASSD_150423.txt

-rw-r--r-- 1 oracle oinstall 10592 Aug 1 2011 rpt_hardening.sql

-rw-r--r-- 1 oracle oinstall 14884 Apr 13 2010 rpt_Oracle_Hardening.sql

-rw-r--r-- 1 oracle oinstall 70858 Apr 13 2010 rpt_scanner.sql

-rw-r--r-- 1 oracle oinstall 7304 Apr 13 2010 rpt_SLA_security.sql

-rw-r--r-- 1 oracle oinstall 2998 Apr 13 2010 rpt_user_audit.sql

-rw-r--r-- 1 oracle oinstall 3329 Apr 13 2010 rpt_user_privs.sql

-rw-r--r-- 1 oracle oinstall 270 Apr 13 2010 sh_active_locks.sql

-rw-r--r-- 1 oracle oinstall 465 Apr 13 2010 sh_active_sessions.sql

-rw-r--r-- 1 oracle oinstall 630 Apr 13 2010 sh_actwaits.sql

-rw-r--r-- 1 oracle oinstall 3499 Apr 13 2010 sh_all_sessions2.sql

-rw-r--r-- 1 oracle oinstall 665 Apr 13 2010 sh_all_sessions.sql

-rw-r--r-- 1 oracle oinstall 549 Apr 13 2010 sh_arch_hist.sql

-rw-r--r-- 1 oracle oinstall 721 Apr 13 2010 sh_db_links2.sql

-rw-r--r-- 1 oracle oinstall 300 Apr 13 2010 sh_db_links.sql

-rw-r--r-- 1 oracle oinstall 592 Apr 13 2010 sh_dependency.sql

-rw-r--r-- 1 oracle oinstall 1478 Apr 13 2010 sh_df.sql

-rw-r--r-- 1 oracle oinstall 612 Apr 13 2010 sh_disk.sql

-rw-r--r-- 1 oracle oinstall 462 Apr 13 2010 sh_free_mem.sql

-rw-r--r-- 1 oracle oinstall 503 Apr 13 2010 sh_hit_ratio.sql

-rw-r--r-- 1 oracle oinstall 487 Apr 13 2010 sh_invalid_index.sql

-rw-r--r-- 1 oracle oinstall 213 Apr 13 2010 sh_invalid_objects.sql

-rw-r--r-- 1 oracle oinstall 242 Apr 13 2010 sh_invalid.sql

-rw-r--r-- 1 oracle oinstall 823 Apr 13 2010 sh_iowaits.sql

-rw-r--r-- 1 oracle oinstall 1218 Apr 13 2010 sh_jobs.sql

-rw-r--r-- 1 oracle oinstall 478 Apr 13 2010 sh_part.sql

-rw-r--r-- 1 oracle oinstall 596 Apr 13 2010 sh_redo_logs.sql

-rw-r--r-- 1 oracle oinstall 774 Apr 13 2010 sh_resource_limits.sql

-rw-r--r-- 1 oracle oinstall 212 May 27 17:49 sh_rp.sql

-rw-r--r-- 1 oracle oinstall 897 Apr 13 2010 sh_sch_jobs.sql

-rw-r--r-- 1 oracle oinstall 1540 Apr 13 2010 sh_seg_extents.sql

-rw-r--r-- 1 oracle oinstall 373 Apr 13 2010 sh_sqlarea.sql

-rw-r--r-- 1 oracle oinstall 442 Apr 13 2010 sh_tab_analyzed.sql

-rw-r--r-- 1 oracle oinstall 450 Apr 13 2010 sh_temp_usage.sql

-rw-r--r-- 1 oracle oinstall 5348 Jun 16 21:01 sh_tsdf.sql

-rw-r--r-- 1 oracle oinstall 2658 Aug 1 2011 sh_ts.sql

-rw-r--r-- 1 oracle oinstall 1631 Apr 13 2010 sh_tss.sql

-rw-r--r-- 1 oracle oinstall 1568 Apr 13 2010 sh_tsss.sql

-rw-r--r-- 1 oracle oinstall 501 Apr 13 2010 sh_undo_usage.sql

-rw-r--r-- 1 oracle oinstall 1830 Apr 13 2010 sh_user_mem.sql

-rw-r--r-- 1 oracle oinstall 1293 Apr 13 2010 sh_user_privs.sql

-rw-r--r-- 1 oracle oinstall 151 Apr 13 2010 sh_user_sql.sql

-rw-r--r-- 1 oracle oinstall 1237 Apr 13 2010 sh_users_roles.sql

-rw-r--r-- 1 oracle oinstall 556 May 20 14:41 sh_users.sql

-rw-r--r-- 1 oracle oinstall 1326 Apr 13 2010 sh_waits.sql

-rw-r--r-- 1 oracle oinstall 596 Apr 13 2010 sys_event.sql

-rw-r--r-- 1 oracle oinstall 7510 Jul 9 12:52 tsdf_BASSD.txt

-rw-r--r-- 1 oracle oinstall 5245 Apr 13 2010 tsdf.sql

-rw-r--r-- 1 oracle oinstall 681 Jun 16 20:21 tsdf_.txt

-rw-r--r-- 1 oracle oinstall 1631 Apr 13 2010 tss.sql

-rw-r--r-- 1 oracle oinstall 9667 Sep 16 14:37 users_BASSD.txt

-rw-r--r-- 1 oracle oinstall 5099 Apr 13 2010 utlpwdmg.sql

[kenneth.chando@d2asedvic004 ~]$ crontab -l

You (kenneth.chando) are not allowed to use this program (crontab)

See crontab(1) for more information

[kenneth.chando@d2asedvic004 ~]$ sudo su - oracle

oracle@d2asedvic004[BASSD]# crontab -l

#30 22 03 9 * /u01/app/oracle/scripts/rmanbackup_BASSD_disk_full_keep.sh > /u01/app/oracle/scripts/rmanbackup_BASSD_disk_full_keep.log 2>&1

#30 22 08 9 * /u01/app/oracle/scripts/rmanbackup_BASSD_disk_full.sh > /u01/app/oracle/scripts/rmanbackup_BASSD_disk_full.log 2>&1

59 23 * * 6 /u01/app/oracle/scripts/rmanbackup_BASSD_disk_full.sh > /u01/app/oracle/scripts/rmanbackup_BASSD_disk_full.log 2>&1

59 23 * * 1-5 /u01/app/oracle/scripts/rmanbackup_BASSD_disk_inc.sh > /u01/app/oracle/scripts/rmanbackup_BASSD_disk_inc.log 2>&1

01 1,5,9,13,17,21 * * * /u01/app/oracle/scripts/delete_archlogs.sh > /u01/app/oracle/scripts/delete_archlogs.log 2>&1

oracle@d2asedvic004[BASSD]# cat /u01/app/oracle/scripts/rmanbackup_BASSD_disk_full.log

Backup Starting at Sat Sep 26 23:59:01 UTC 2015

stty: standard input: Invalid argument

Recovery Manager: Release 12.1.0.2.0 - Production on Sat Sep 26 23:59:01 2015

connected to target database: BASSD (DBID=3461595491)

RMAN>

Starting backup at 26-SEP-15

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=1021 device type=DISK

channel ORA_DISK_1: starting incremental level 0 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00002 name=/u01/app/oradata/BASSD/BASS_DATA_TBLSPC.DAT

input datafile file number=00008 name=/u01/app/oradata/BASSD/BASS_STG_TBLSPC.DAT

input datafile file number=00004 name=/u01/app/oradata/BASSD/undotbs01.dbf

input datafile file number=00007 name=/u01/app/oradata/BASSD/BASS_INDEX_TBLSPC.DAT

input datafile file number=00009 name=/u01/app/oradata/BASSD/EPM_TBSP_DATA.dat

input datafile file number=00010 name=/u01/app/oradata/BASSD/OBIEE_REP.dat

input datafile file number=00011 name=/u01/app/oradata/BASSD/OBI_REP.dat

input datafile file number=00012 name=/u01/app/oradata/BASSD/ODI_TBSP.dat

input datafile file number=00013 name=/u01/app/oradata/BASSD/FDM_TBSP.dat

input datafile file number=00014 name=/u01/app/oradata/BASSD/CBM_EPM_TBSP_DATA.dat

input datafile file number=00003 name=/u01/app/oradata/BASSD/sysaux01.dbf

input datafile file number=00001 name=/u01/app/oradata/BASSD/system01.dbf

input datafile file number=00005 name=/u01/app/oradata/BASSD/INFA_TBLSPC.DAT

input datafile file number=00006 name=/u01/app/oradata/BASSD/users01.dbf

channel ORA_DISK_1: starting piece 1 at 26-SEP-15

channel ORA_DISK_1: finished piece 1 at 27-SEP-15

piece handle=/u01/app/FRA/backup/db_BASSD_3461595491_1131_1.bkup tag=BASSD_WEEKLY_FULL comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:48:05

Finished backup at 27-SEP-15

Starting Control File and SPFILE Autobackup at 27-SEP-15

piece handle=/u01/app/FRA/BASSD/autobackup/2015_09_27/o1_mf_s_891478046_c0gh4zf8_.bkp comment=NONE

Finished Control File and SPFILE Autobackup at 27-SEP-15

RMAN>

Starting backup at 27-SEP-15

current log archived

using channel ORA_DISK_1

channel ORA_DISK_1: starting archived log backup set

channel ORA_DISK_1: specifying archived log(s) in backup set

input archived log thread=1 sequence=88534 RECID=88756 STAMP=891454117

input archived log thread=1 sequence=88535 RECID=88757 STAMP=891454270

input archived log thread=1 sequence=88536 RECID=88758 STAMP=891468712

input archived log thread=1 sequence=88537 RECID=88759 STAMP=891468721

input archived log thread=1 sequence=88538 RECID=88760 STAMP=891468727

input archived log thread=1 sequence=88539 RECID=88761 STAMP=891476058

input archived log thread=1 sequence=88540 RECID=88762 STAMP=891476062

input archived log thread=1 sequence=88541 RECID=88763 STAMP=891478051

channel ORA_DISK_1: starting piece 1 at 27-SEP-15

channel ORA_DISK_1: finished piece 1 at 27-SEP-15

piece handle=/u01/app/FRA/backup/log_BASSD_3461595491_1133_1.bkup tag=BASSD_WEEKLY_FULL comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07

channel ORA_DISK_1: deleting archived log(s)

archived log file name=/u01/app/FRA/BASSD/archivelog/2015_09_26/o1_mf_1_88534_c0fqs4wf_.arc RECID=88756 STAMP=891454117

archived log file name=/u01/app/FRA/BASSD/archivelog/2015_09_26/o1_mf_1_88535_c0fqxy1z_.arc RECID=88757 STAMP=891454270

archived log file name=/u01/app/FRA/BASSD/archivelog/2015_09_26/o1_mf_1_88536_c0g61831_.arc RECID=88758 STAMP=891468712

archived log file name=/u01/app/FRA/BASSD/archivelog/2015_09_26/o1_mf_1_88537_c0g61jqz_.arc RECID=88759 STAMP=891468721

archived log file name=/u01/app/FRA/BASSD/archivelog/2015_09_26/o1_mf_1_88538_c0g61q4p_.arc RECID=88760 STAMP=891468727

archived log file name=/u01/app/FRA/BASSD/archivelog/2015_09_27/o1_mf_1_88539_c0gf6syb_.arc RECID=88761 STAMP=891476058

archived log file name=/u01/app/FRA/BASSD/archivelog/2015_09_27/o1_mf_1_88540_c0gf6y00_.arc RECID=88762 STAMP=891476062

archived log file name=/u01/app/FRA/BASSD/archivelog/2015_09_27/o1_mf_1_88541_c0gh52wx_.arc RECID=88763 STAMP=891478051

Finished backup at 27-SEP-15

Starting Control File and SPFILE Autobackup at 27-SEP-15

piece handle=/u01/app/FRA/BASSD/autobackup/2015_09_27/o1_mf_s_891478058_c0gh5ccz_.bkp comment=NONE

Finished Control File and SPFILE Autobackup at 27-SEP-15

RMAN>

Starting backup at 27-SEP-15

using channel ORA_DISK_1

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

channel ORA_DISK_1: starting piece 1 at 27-SEP-15

channel ORA_DISK_1: finished piece 1 at 27-SEP-15

piece handle=/u01/app/FRA/backup/cf_BASSD_3fqi5o1f_1_1.bkup tag=BASSD_WEEKLY_FULL comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 27-SEP-15

Starting Control File and SPFILE Autobackup at 27-SEP-15

piece handle=/u01/app/FRA/BASSD/autobackup/2015_09_27/o1_mf_s_891478065_c0gh5kv9_.bkp comment=NONE

Finished Control File and SPFILE Autobackup at 27-SEP-15

RMAN>

released channel: ORA_DISK_1

allocated channel: ORA_MAINT_DISK_1

channel ORA_MAINT_DISK_1: SID=1021 device type=DISK

RMAN>

RMAN retention policy will be applied to the command

RMAN retention policy is set to recovery window of 1 days

Deleting the following obsolete backups and copies:

Type Key Completion Time Filename/Handle

-------------------- ------ ------------------ --------------------

Backup Set 1092 26-SEP-15

Backup Piece 1092 26-SEP-15 /u01/app/FRA/BASSD/autobackup/2015_09_26/o1_mf_s_891391266_c0ctf465_.bkp

Backup Set 1094 26-SEP-15

Backup Piece 1094 26-SEP-15 /u01/app/FRA/BASSD/autobackup/2015_09_26/o1_mf_s_891391298_c0ctg47z_.bkp

Backup Set 1095 26-SEP-15

Backup Piece 1095 26-SEP-15 /u01/app/FRA/backup/cf_BASSD_39qi33a7_1_1.bkup

deleted backup piece

backup piece handle=/u01/app/FRA/BASSD/autobackup/2015_09_26/o1_mf_s_891391266_c0ctf465_.bkp RECID=1092 STAMP=891391268

deleted backup piece

backup piece handle=/u01/app/FRA/BASSD/autobackup/2015_09_26/o1_mf_s_891391298_c0ctg47z_.bkp RECID=1094 STAMP=891391300

deleted backup piece

backup piece handle=/u01/app/FRA/backup/cf_BASSD_39qi33a7_1_1.bkup RECID=1095 STAMP=891391304

Deleted 3 objects

RMAN>

List of Backup Pieces

BP Key BS Key Pc# Cp# Status Device Type Piece Name

------- ------- --- --- ----------- ----------- ----------

1090 1090 1 1 AVAILABLE DISK /u01/app/FRA/backup/db_BASSD_3461595491_1124_1.bkup

1091 1091 1 1 AVAILABLE DISK /u01/app/FRA/backup/db_BASSD_3461595491_1125_1.bkup

1093 1093 1 1 AVAILABLE DISK /u01/app/FRA/backup/log_BASSD_3461595491_1127_1.bkup

1096 1096 1 1 AVAILABLE DISK /u01/app/FRA/BASSD/autobackup/2015_09_26/o1_mf_s_891391305_c0ctgbnx_.bkp

deleted backup piece

backup piece handle=/u01/app/FRA/backup/db_BASSD_3461595491_1124_1.bkup RECID=1090 STAMP=891388751

deleted backup piece

backup piece handle=/u01/app/FRA/backup/db_BASSD_3461595491_1125_1.bkup RECID=1091 STAMP=891391191

deleted backup piece

backup piece handle=/u01/app/FRA/backup/log_BASSD_3461595491_1127_1.bkup RECID=1093 STAMP=891391272

deleted backup piece

backup piece handle=/u01/app/FRA/BASSD/autobackup/2015_09_26/o1_mf_s_891391305_c0ctgbnx_.bkp RECID=1096 STAMP=891391306

Deleted 4 objects

RMAN>

released channel: ORA_MAINT_DISK_1

RMAN>

Recovery Manager complete.

Backup Completed at Sun Sep 27 00:48:05 UTC 2015

oracle@d2asedvic004[BASSD]#

Cronjob Script for BASST(Omer’s)

/u01/app/oracle/scripts/rmanbackup_BASST_disk_full_keep.sh >/u01/app/oracle/scripts/rmanbackup_BASST_disk_full_keep.log 2>&1

oracle@d2asetsic002[BASST]# cat /u01/app/oracle/scripts/rmanbackup_BASST_disk_full_keep.sh

SCRIPT

#!/bin/ksh

echo "Backup Starting at `date`"

. $HOME/.profile

rman target=/ << EOF

BACKUP device type disk format '/u01/app/FRA/backup/keep/db_%d_%I_%s_%p.bkup' tag BASST_keep_full database;

backup device type disk format '/u01/app/FRA/backup/keep/log_%d_%I_%s_%p.bkup' tag BASST_keep_full archivelog all not backed up;

backup device type disk format '/u01/app/FRA/backup/keep/cf_%d_%U.bkup' tag BASST_keep_full current controlfile;

EXIT;

EOF

echo "Backup Completed at `date`"

oracle@d2asetsic002[BASST]#

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

+mailto:kenneth.chando@hp.com

SET PAGESIZE 2000 LINESIZE 150

TTITLE CENTER 'DISK SPACE USAGE' SKIP 1

col TOTAL format 999999999.99 heading "Allocated Space|(GB)"

col USED format 999999999.99 heading "Used Space|(GB)"

col FREE format 999999999.99 heading "Free Space|(GB)"

col PERCENT_USED format 99999.99 heading "Space Usage|(%)"

BREAK ON REPORT

COMPUTE SUM LABEL "TOTAL DB SIZE:" OF USED ON REPORT;

SELECT a.tablespace_name,

ROUND(a.bytes/1024/1024/1024,2) TOTAL,

ROUND(NVL( b.bytes,0)/1024/1024/1024,2) USED,

ROUND(NVL(c.bytes, 0)/1024/1024/1024,2) FREE,

ROUND(NVL(b.bytes,0)*100/NVL(a.bytes,0),2) AS PERCENT_USED

FROM SYS.SM$TS_AVAIL a, SYS.SM$TS_USED b, SYS.SM$TS_FREE c

WHERE a.tablespace_name= b.tablespace_name(+)

AND b.tablespace_name = c.tablespace_name(+)

ORDER BY 5 DESC;

SIZE(%)

SET LINESIZE 200 PAGESIZE 2000

COL DATABASE_SIZE FOR A25

COL FREE_SPACE FOR A15

COL USED_SPACE FOR A15

SELECT ROUND (SUM (used.bytes) / 1024 / 1024 / 1024) || ' GB' "DATABASE_SIZE",

ROUND (SUM (used.bytes) / 1024 / 1024 / 1024) -

ROUND (free.p / 1024 / 1024 / 1024) || ' GB' "USED_SPACE",

ROUND (free.p / 1024 / 1024 / 1024) || ' GB' "FREE_SPACE"

FROM (

SELECT SUM (bytes) AS bytes

FROM v$datafile

UNION ALL

SELECT SUM (bytes) AS bytes

FROM v$tempfile

UNION ALL

SELECT SUM (bytes) AS bytes

FROM v$log

) used,

(SELECT SUM (bytes) AS p FROM dba_free_space ) free

GROUP BY free.p;

Db file_rename

set timing off

set feedback off

set echo off

set linesize 200

set pagesize 0

spool c:TXSTST3_db_file_rename

select 'mv ' || name || ' ' || replace(name,'/txstin1','/txstst3') ksh_cmd

from v$datafile order by name;

select 'mv ' || member || ' ' || replace(member,'/txstin1','/txstst3') as ksh_cmd

from v$logfile order by member;

select 'mv ' || name || ' ' || replace(name,'/temp/temp','/temp/txstst3temp') as ksh_cmd

from v$tempfile order by name;

select 'alter database rename file ''' || name || ''' to ''' || replace(name,'/txstin1','/txstst3') || ''';' as sql_cmd

from v$datafile order by name;

select 'alter database rename file ''' || member || ''' to ''' || replace(member,'/txstin1','/txstst3') || ''';' as sql_cmd

from v$logfile order by member;

select 'alter database rename file ''' || name || ''' to ''' || replace(name,'/temp/temp','/temp/txstst3temp') || ''';' as sql_cmd

from v$tempfile order by name;

spool off

db_cache_ratios

VAR val1 NUMBER;

COL val1 FOR 999999999.99

EXEC SELECT 100*(1-(SUM(Reloads)/SUM(Pins))) val1 INTO :val1 FROM V$LIBRARYCACHE;

VAR val2 NUMBER;

COL val2 FOR 999999999.99

EXEC SELECT 100*(1-(SUM(Getmisses)/SUM(Gets))) val2 INTO :val2 FROM V$ROWCACHE;

VAR val3 NUMBER;

COL val3 FOR 999999999.99

EXEC SELECT value val3 INTO :val3 FROM V$SYSSTAT WHERE Name = 'physical reads';

VAR val4 NUMBER;

COL val4 FOR 999999999.99

EXEC SELECT value val4 INTO :val4 FROM V$SYSSTAT WHERE Name = 'db block gets';

VAR val5 NUMBER;

COL val5 FOR 999999999.99

EXEC SELECT value val5 INTO :val5 FROM V$SYSSTAT WHERE Name = 'consistent gets';

VAR val6 NUMBER;

COL val6 FOR 999999999.99

EXEC SELECT ((1-(:val3/(:val4 + :val5)))*100) val6 INTO :val6 FROM DUAL;

VAR val7 NUMBER;

COL val7 FOR 999999999.99

VAR val8 NUMBER;

COL val8 FOR 999999999.99

EXEC SELECT SUM(Users_Opening)/COUNT(*) val7 , SUM(Executions)/COUNT(*) val8 INTO :val7, :val8 FROM V$SQLAREA;

SELECT 'Data Block Buffer Hit Ratio : '|| :val6,

' Shared SQL Pool ',

' Dictionary Hit Ratio : '|| :val2,

' Shared SQL Buffers (Library Cache) ',

' Cache Hit Ratio : '|| :val1,

' Avg. Users/Stmt : '|| :val7,

' Avg. Executes/Stmt : '|| :val8

FROM DUAL;

ENABLE/DISABLE DATAGUARD

*********************

* DISABLE Dataguard

*********************

On Standby DB:

------------------

i) SQL> alter database recover managed standby database cancel;

ii) SQL> alter system set log_archive_dest_state_2=DEFER SCOPE=BOTH;

On Primary DB:

---------------------

i) SQL> alter system set log_archive_dest_state_2=DEFER SCOPE=BOTH SID='*';

*********************

* EABLE Dataguard

*********************

On Primary DB:

---------------------

ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH SID='*';

On Standby DB:

---------------------

ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

FIND CONTENTION in Database:

Finding the contention

When a session is waiting on this event, an entry will be seen in the v$session_wait system view giving more information on the blocks being waited for:

SELECT p1 "file#", p2 "block#", p3 "class#"

FROM v$session_wait

WHERE event = 'read by other session';

If information collected from the above query repeatedly shows that the same block, (or range of blocks), is experiencing waits, this indicates a "hot" block or object. The following query will give the name and type of the object:

SELECT relative_fno, owner, segment_name, segment_type

FROM dba_extents

WHERE file_id = &file

AND &block BETWEEN block_id AND block_id + blocks - 1;

Eliminating contention

Depending on the database environment and specific performance situation the following variety of methods can be used to eliminate contention:

Tune inefficient queries - This is one of those events you need to "catch in the act" through the v$session_wait view as prescribed above. Then, since this is a disk operating system issue, take the associated system process identifier (c.spid) and see what information we can obtain from the operating system.

Redistribute data from the hot blocks –deleting and reinserting the hot rows will often move them to a new data block. This will help decrease contention for the hot block and increase performance. More information about the data residing within the hot blocks can be retrieved with queries similar to the following:

SELECT data_object_id

FROM dba_objects

WHERE owner='&owner' AND object_name='&object';

SELECT dbms_rowid.rowid_create(1,<data_object_id>,<relative_fno>,<block>,0) start_rowid

FROM dual;

--rowid for the first row in the block

SELECT dbms_rowid.rowid_create(1,<data_object_id>,<relative_fno>,<block>,500) end_rowid

FROM dual;

--rowid for the 500th row in the block

SELECT <column_list>

FROM <owner>.<segment_name>

WHERE rowid BETWEEN <start_rowid> AND <end_rowid>

CHECK SYS_PRIVS:

SET LINESIZE 180 PAGESIZE 2000

COL TABLE_NAME FOR A30

COL GRANTEE FOR A20

COL PRIVILEGE FOR A25

COL OWNER FOR A20

SELECT GRANTEE, TABLE_NAME, OWNER, PRIVILEGE

FROM DBA_TAB_PRIVS

WHERE substr(privilege,1,20) LIKE '%EXECUTE%'

AND substr(table_name,1,35) LIKE 'UTL_%'

AND GRANTEE NOT IN ( 'EXECUTE_CATALOG_ROLE', 'SYS', 'SYSTEM', 'GATHER_SYSTEM_STATISTICS','DBA', 'SELECT_CATALOG_ROLE', 'EXP_FULL_DATABASE', 'IMP_FULL_DATABASE')

ORDER BY TABLE_NAME, GRANTEE

CHECK STATISTICS:

SELECT DTM.TABLE_OWNER,

DTM.TABLE_NAME,

DTM.PARTITION_NAME,

ROUND ( (DTM.INSERTS + DTM.UPDATES + DTM.DELETES) / DT.NUM_ROWS,2) * 100 "CHANGE_FACTOR",

DT.PARTITIONED,

DT.NUM_ROWS

FROM SYS.DBA_TAB_MODIFICATIONS DTM,

DBA_TABLES DT

WHERE DTM.TABLE_OWNER = DT.OWNER

AND DTM.TABLE_NAME = DT.TABLE_NAME

AND NOT DTM.TABLE_OWNER IN ('SYS','SYSTEM', 'DBSNMP', 'OUTLN')

AND NOT DT.NUM_ROWS IS NULL

AND IOT_TYPE IS NULL

AND ( (DT.PARTITIONED = 'YES' AND NOT DTM.PARTITION_NAME IS NULL)

OR (DT.PARTITIONED = 'NO' AND DTM.PARTITION_NAME IS NULL))

AND NOT (DTM.TABLE_OWNER, DTM.TABLE_NAME) IN (SELECT DTS.OWNER, DTS.TABLE_NAME FROM DBA_TAB_STATISTICS DTS WHERE DTS.STATTYPE_LOCKED ='ALL')

AND NOT (DTM.TABLE_OWNER, DTM.TABLE_NAME) IN (SELECT DET.OWNER, DET.TABLE_NAME FROM DBA_EXTERNAL_TABLES DET)

AND DTM.TABLE_OWNER='DWADM'

ORDER BY 2;

SELECT * FROM DBA_TAB_STATISTICS

WHERE STALE_STATS='YES'

AND NOT OWNER IN ('SYSTEM', 'DBSNMP','SYS');

CHECK ROLE_PRIVS

As for the second question: the thing you're looking for, are the system privileges CREATE USER, DROP USER and possibly ALTER USER might be useful. These privileges might have been granted directly to a user or via a role.

This query checks and shows both:

select grantee, 'DIRECTLY' type, privilege priv_or_role

from dba_sys_privs

where privilege in ('CREATE USER', 'DROP USER', 'ALTER USER')

and grantee in (select username from dba_users)

UNION

select grantee, 'VIA ROLE' type, granted_role priv_or_role

from dba_role_privs

where granted_role in (

select grantee

from dba_sys_privs

where privilege in ('CREATE USER', 'DROP USER', 'ALTER USER')

and grantee in (select role from dba_roles)

);

CHECK MEMORY_USAGE:

set serveroutput on

DECLARE

libcac NUMBER(10,2);

rowcac NUMBER(10,2);

bufcac NUMBER(10,2);

redlog NUMBER(10,2);

spsize NUMBER;

blkbuf NUMBER;

logbuf NUMBER;

BEGIN

SELECT VALUE INTO redlog FROM v$sysstat

WHERE name = 'redo log space requests';

SELECT 100*(SUM(pins)-SUM(reloads))/SUM(pins) INTO libcac FROM v$librarycache;

SELECT 100*(SUM(gets)-SUM(getmisses))/SUM(gets) INTO rowcac FROM v$rowcache;

SELECT 100*(cur.VALUE + con.VALUE - phys.VALUE)/(cur.VALUE + con.VALUE) INTO bufcac

FROM v$sysstat cur,v$sysstat con,v$sysstat phys,v$statname ncu,v$statname nco,v$statname nph

WHERE cur.statistic# = ncu.statistic#

AND ncu.name = 'db block gets'

AND con.statistic# = nco.statistic#

AND nco.name = 'consistent gets'

AND phys.statistic# = nph.statistic#

AND nph.name = 'physical reads';

SELECT VALUE INTO spsize FROM v$parameter WHERE name = 'shared_pool_size';

SELECT VALUE INTO blkbuf FROM v$parameter WHERE name = 'db_block_buffers';

SELECT VALUE INTO logbuf FROM v$parameter WHERE name = 'log_buffer';

DBMS_OUTPUT.put_line('> SGA CACHE STATISTICS');

DBMS_OUTPUT.put_line('> ********************');

DBMS_OUTPUT.put_line('> SQL Cache Hit rate = '||libcac);

DBMS_OUTPUT.put_line('> Dict Cache Hit rate = '||rowcac);

DBMS_OUTPUT.put_line('> Buffer Cache Hit rate = '||bufcac);

DBMS_OUTPUT.put_line('> Redo Log space requests = '||redlog);

DBMS_OUTPUT.put_line('> ');

DBMS_OUTPUT.put_line('> INIT.ORA SETTING');

DBMS_OUTPUT.put_line('> ****************');

DBMS_OUTPUT.put_line('> Shared Pool Size = '||spsize||' Bytes');

DBMS_OUTPUT.put_line('> DB Block Buffer = '||blkbuf||' Blocks');

DBMS_OUTPUT.put_line('> Log Buffer = '||logbuf||' Bytes');

DBMS_OUTPUT.put_line('> ');

libcac < 99 THEN DBMS_OUTPUT.put_line('*** HINT: Library Cache too low! Increase the Shared Pool Size.');

END IF;

rowcac < 85 THEN DBMS_OUTPUT.put_line('*** HINT: Row Cache too low! Increase the Shared Pool Size.');

END IF;

bufcac < 90 THEN DBMS_OUTPUT.put_line('*** HINT: Buffer Cache too low! Increase the DB Block Buffer value.');

END IF;

redlog > 100 THEN DBMS_OUTPUT.put_line('*** HINT: Log Buffer value is rather low!');

END IF;

END;

BLOCKING_SESSIONS:

Prompt ============ Display the BLOCKING SESSION =============

SELECT B.SID,

B.SQL_ID,

B.USERNAME,

B.MACHINE

FROM V$SESSION B

WHERE B.SID = (SELECT DISTINCT blocker FROM (select a.sid blocker, 'is blocking the session ', b.sid blockee

FROM v$lock a, v$lock b

WHERE a.block =1

AND b.request > 0

AND a.id1=b.id1

AND a.id2=b.id2)

);

Prompt ============ Display the BLOCKED SESSION =============

SELECT

S.SID,

S.SQL_ID,

S.USERNAME,

S.MACHINE

FROM V$SESSION S

WHERE S.SID = (SELECT DISTINCT blockee FROM (select a.sid blocker, 'is blocking the session ', b.sid blockee

FROM v$lock a, v$lock b

WHERE a.block =1

AND b.request > 0

AND a.id1=b.id1

AND a.id2=b.id2)

);

BLOCKING SESSIONS:

set pagesize 14000 linesize 170

select s1.username || '@' || s1.machine

|| ' ( SID=' || s1.sid || ' ) is blocking '

|| s2.username || '@' || s2.machine || ' ( SID=' || s2.sid || ' ) ' AS blocking_status

from v$lock l1, v$session s1, v$lock l2, v$session s2

where s1.sid=l1.sid and s2.sid=l2.sid

and l1.BLOCK=1 and l2.request > 0

and l1.id1 = l2.id1

and l2.id2 = l2.id2

order by s1.machine, s2.machine;

ACTIVE USERS:

A script such as follows works well. It shows you who's logged in and active -- and if

active, the statement they are executing (and the last et text shows you how long that

statement has been executing). Currently, it shows only SQL that is executing right now,

just change the predicate from "where status = 'ACTIVE'" to "where status = status" if

you want to see the currently executing as well as LAST executed (in which case the last

et column text shows you how long they've been idle -- not how long that statement took

to execute):

column status format a10

set feedback off

set serveroutput on

select username, sid, serial#, process, status

from v$session

where username is not null

column username format a20

column sql_text format a55 word_wrapped

set serveroutput on size 1000000

declare

x number;

begin

for x in

( select username||'('||sid||','||serial#||

') ospid = ' || process ||

' program = ' || program username,

to_char(LOGON_TIME,' Day HH24:MI') logon_time,

to_char(sysdate,' Day HH24:MI') current_time,

sql_address, LAST_CALL_ET

from v$session

where status = 'ACTIVE'

and rawtohex(sql_address) <> '00'

and username is not null order by last_call_et )

loop

for y in ( select max(decode(piece,0,sql_text,null)) ||

max(decode(piece,1,sql_text,null)) ||

max(decode(piece,2,sql_text,null)) ||

max(decode(piece,3,sql_text,null))

sql_text

from v$sqltext_with_newlines

where address = x.sql_address

and piece < 4)

loop

if ( y.sql_text not like '%listener.get_cmd%' and

y.sql_text not like '%RAWTOHEX(SQL_ADDRESS)%')

then

dbms_output.put_line( '--------------------' );

dbms_output.put_line( x.username );

dbms_output.put_line( x.logon_time || ' ' ||

x.current_time||

' last et = ' ||

x.LAST_CALL_ET);

dbms_output.put_line(

substr( y.sql_text, 1, 250 ) );

end if;

end loop;

end;

column username format a25 word_wrapped

column module format a35 word_wrapped

column action format a25 word_wrapped

column client_info format a30 word_wrapped

SELECT username||'('||sid||','||serial#||')' username,

module,

action,

client_info

FROM V$SESSION

where module || action || client_info IS NOT NULL

ORDER BY 1;

ACTIVE SESSIONS:

set linesize 350 pagesize 14000

ALTER SESSION SET NLS_DATE_FORMAT='MM/DD/YYYY HH24:MI:SS';

col username for a15

col spid for 99999999

col sid for 999999

col serial# for 99999999

col LOGON_TIME for a20

col sql_text for a80

col PID for 99999

col process for a20

SELECT DISTINCT

a.username,

---b.spid,

a.osuser,

a.status,

a.logon_time,

a.sid,

a.machine,

a.serial#,

---c.sql_text,

b.PID,

a.Process

FROM V$SESSION a, V$PROCESS b, V$SQLTEXT c

WHERE a.PADDR=b.ADDR

AND c.hash_value=a.sql_hash_value

----and a.STATUS='ACTIVE'

order by a.sid;

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

SELECT 'GRANT SELECT ON ' || OWNER || '.' || TABLE_NAME || ' TO system;'

FROM DBA_TABLES

WHERE OWNER='asevilla'

ORDER BY TABLE_NAME;

SELECT 'GRANT SELECT ON ' || OWNER || '.' || TABLE_NAME || ' TO sysman;'

FROM DBA_TABLES

WHERE OWNER='asevilla'

ORDER BY TABLE_NAME;

SELECT 'GRANT SELECT ON ' || OWNER || '.' || OBJECT_NAME || ' TO system;'

FROM DBA_OBJECTS

WHERE OWNER='asevilla'

AND OBJECT_TYPE='VIEW'

ORDER BY OBJECT_NAME;

SELECT 'GRANT SELECT ON ' || OWNER || '.' || OBJECT_NAME || ' TO sysman;'

FROM DBA_OBJECTS

WHERE OWNER='asevilla'

AND OBJECT_TYPE='VIEW'

ORDER BY OBJECT_NAME;

SELECT 'GRANT SELECT, INSERT, UPDATE, DELETE ON ' || OWNER || '.' || TABLE_NAME || ' TO sys;'

FROM DBA_TABLES

WHERE OWNER='asevilla'

ORDER BY TABLE_NAME;

SELECT 'GRANT SELECT, INSERT, UPDATE, DELETE ON ' || OWNER || '.' || TABLE_NAME || ' TO asevilla;'

FROM DBA_TABLES

WHERE OWNER='asevilla'

ORDER BY TABLE_NAME;

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

XCLOCK: X11->forwarding:

MobaXterm requires you to do SSH –X user@DestionationiP before GUI will work.

DATABASE INSTALL:

After successful install of your database, you need to set your environment variables CORRECTLY:

1. ~/.bash_profile (modify to reflect the new $ORACLE_HOME)

2. $PATH

RECOVER system tablespace from RMAN:

RMAN>

run

{

set newname for datafile 1 to '/u01/oradata/LABDB/datafile/non_default_location/system01.dbfq60k_.dbf';

restore tablespace system;

switch datafile all;

recover tablespace system;

alter database open;

};

Or:

SQL>create tablespace SYSTEM datafile '/u01/oradata/LABDB/datafile/non_default_location/system01.dbfq60k_.dbf' size 50M autoextend on;

(security monitoring)

Desc DBA_audit_session

Desc DB_audit_object

================================================================================================================================

restore controlfile from '/u01/oradata/LABDB/controlfile/o1_mf_8nkgs300_.ctl' to '/u01/oradata/LABDB/datafile/non_default_location';

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

(phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

From: Chando, Kenneth
Sent: Tuesday, October 06, 2015 8:45 PM
To:kenneth.chando@associates.hq.dhs.gov
Cc: Chando, Kenneth
Subject: VIEWING a USER's Privilege to an Object

SELECT 'GRANT SELECT ON ' || OWNER || '.' || TABLE_NAME || ' TO system;'

FROM DBA_TABLES

WHERE OWNER='asevilla'

ORDER BY TABLE_NAME;

SELECT 'GRANT SELECT ON ' || OWNER || '.' || TABLE_NAME || ' TO sysman;'

FROM DBA_TABLES

WHERE OWNER='asevilla'

ORDER BY TABLE_NAME;

SELECT 'GRANT SELECT ON ' || OWNER || '.' || OBJECT_NAME || ' TO system;'

FROM DBA_OBJECTS

WHERE OWNER='asevilla'

AND OBJECT_TYPE='VIEW'

ORDER BY OBJECT_NAME;

SELECT 'GRANT SELECT ON ' || OWNER || '.' || OBJECT_NAME || ' TO sysman;'

FROM DBA_OBJECTS

WHERE OWNER='asevilla'

AND OBJECT_TYPE='VIEW'

ORDER BY OBJECT_NAME;

SELECT 'GRANT SELECT, INSERT, UPDATE, DELETE ON ' || OWNER || '.' || TABLE_NAME || ' TO sys;'

FROM DBA_TABLES

WHERE OWNER='asevilla'

ORDER BY TABLE_NAME;

SELECT 'GRANT SELECT, INSERT, UPDATE, DELETE ON ' || OWNER || '.' || TABLE_NAME || ' TO asevilla;'

FROM DBA_TABLES

WHERE OWNER='asevilla'

ORDER BY TABLE_NAME;

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

Hi Bruce,

Find below my draft playbook for the HP DC2LAB 12c install

**NOTE: Please as you’re currently performing the task in the LAB, kindly modify/amend to suit our purpose. Include screenshot where possible.

=====================================================================================================================================

I. ORACLE CONFIGURATION

The following two installation files were downloaded from Oracle Support’s website (www.support.oracle.com).

i. linuxamd64_12102_database_1of2.zip

ii. linuxamd64_12102_database_2of2.zip

======================================================================================================================================

II. Create directory on the server that host the two zipped files above

#cd /u01/app/oracle

#mkdir staging

=======================================================================================================================================

III. Create directory structure that will be used as the base ($ORACLE_BASE) and home ($ORACLE_HOME) location for the oracle 12c software binaries as shown below:

#cd /

#mkdir -p /u01/app/oracle/product/12.1.0.1

=========================================

IV. Change the ownership of the directory you just created as shown:

#chown oracle:oinstall -R /u01/app/oracle

====================================================

V. Go to the home directory of oracle user as shown:

====================================================

#cd /home/oracle

#ls -ltra

============================================================================================

VI. Add/Modify entries in the ~/.bash_profile for the oracle user to fit currently install version of oracle rdbms software (e.g. 12.1.0.1):

============================================================================================================================

ORACLE_HOME=/u01/app/oracle/product/12.1.0.1

ORACLE_BASE=/u01/app/oracle

ORACLE_SID=labdb

ORACLE_UNQNAME=labdb

ORACLE_DB=labdb

ORACLE_GRID=/u01/app/12.1.0.1/grid; export ORACLE_GRID

DIAG=$ORACLE_BASE/diag/rdbms/labdb/labdb/trace

TNS_ADMIN=$ORACLE_HOME/network/admin

# PATH=$HOME/bin:/u01/app/oracle/product/11.2.0.3/bin:$PATH

# PATH=$HOME/bin:/u01/app/oracle/product/11.2.0.3/bin:/usr/local/bin:/bin:/usr/bin

PATH=$HOME:/usr/sbin:/usr/proc/bin:/usr/local/sbin:$ORACLE_HOME/bin:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:/usr/local/bin:/usr/bin:$PATH

PATH=$ORACLE_BASE/scripts:$PATH

export ORACLE_HOME ORACLE_BASE ORACLE_SID ORACLE_UNQNAME TNS_ADMIN DIAG

alias ll='ls -al'

alias scripts='cd /u01/app/oracle/scripts'

alias sql='$ORACLE_HOME/bin/sqlplus "/ as sysdba"'

ora_db=$( echo "$ORACLE_DB" | tr -s '[:upper:]' '[:lower:]' )

alias alog='tail -200 /u01/app/oracle/diag/rdbms/${ora_db}/${ORACLE_SID}/trace/alert_${ORACLE_SID}.log'

alias bdump='cd /u01/app/oracle/diag/rdbms/${ora_db}/${ORACLE_SID}/trace/'

alias udump='cd /u01/app/oracle/diag/rdbms/${ora_db}/${ORACLE_SID}/trace/'

alias cdump='cd /u01/app/oracle/diag/rdbms/${ora_db}/${ORACLE_SID}/cdump'

alias adump='cd /u01/app/oracle/admin/${ORACLE_DB}/adump'

#alias goasm='. $HOME/.goasm'

#alias godb='. $HOME/.godb'

export TMOUT=0

PS1="$USER@"`hostname`"[$ORACLE_SID]# "

#export ORACLE_BASE=/u01/app/oracle

#export ORACLE_HOME=/u01/app/oracle/product/12.1.0.1

#export ORACLE_SID=labdb

export TNS_ADMIN=/u01/app/oracle/product/12.1.0.1/network/admin

# export PATH=/usr/sbin:/usr/proc/bin:/usr/local/bin:/usr/local/sbin:/usr/ccs/bin:/usr/local/bin:/bin:/usr/bin

-- INSERT --

=====================================================================================================

VII. INSTALL ORACLE DATABASE SOFTWARE

=====================================

1.Winscp - transfer the 2 oracle zipped files to the /u01/app/oracle/staging directory in your server directory on your Linux server

2. On server where oracle 12c is to be installed do:

#export ORACLE_HOME=/u01/app/oracle/12.1.0.1

#cd /u01/app/oracle/staging

3. Unzip the 2 oracle 12c zipped files:

#unzip linuxamd64_12102_database_1of2.zip

#unzip linuxamd64_12102_database_2of2.zip

4. Once extraction is completed, view contents by doing:

# ls -ltra on /u01/app/oracle/staging

5. Go to the database directory

#cd /u01/app/oracle/staging/database

6. Kick off the installation script (runInstaller) as follows:

/u01/app/oracle/staging/database#./runInstaller

==================================================================================================

7. Run the commands below to check DISPLAY settings:

#echo $DISPLAY

#If no DISPLAY setting configured, do:

8. root# ssh server IP Address (i.e. when connected via MobaXterm)

9. echo $DISPLAY (x11 DISPLAY settings will be forwarded to your server when you ssh to server ip)

==============================================================================================

10. Kick off the installation script (runInstaller) as follows:

/u01/app/oracle/staging/database#./runInstaller

11. Uncheck the "I wish to receive security updates via My Oracle Support" option

12. Click "YES"

13. Select "Skip software updates"

14. Click "NEXT"

15. Select "Create and configure a database"/"Install database software only" (for very new install)

16. Click "NEXT"

17. Select "Server Class"

18. Click "NEXT"

19. Select "Single instance database installation"

20. Click "NEXT"

21. Select "Typical Install"

22. Click "NEXT"

23. Most of the information will be pre-populated for: Oracle_base,Software location,Database file location, etc

24. Enter Global database name (e.g. labdb)

25. Enter/Confirm Password

26. Click "NEXT" (leave defaults)

27. Click "NEXT"

28. Click "Install"

29. Execute required Configuration scripts as root user in another session (e.g see below)

root#/../../root.sh

30. Click "OK" once scripts are executed as root user.

31. Click "Close"

=================================================

TESTING

==========

$echo $ORACLE_HOME

$echo $ORACLE_SID

32. Connect to your database and test by doing:

#sql

sql>select name from v$database;

sql>select status from v$instance;

==============================================================================================================

Thank you!

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

That was perfectly fine.

Then you would have to go back and create the database, or create it manually with the script I sent you.

Thanks

Lionel

From: Chando, Kenneth
Sent: Wednesday, October 14, 2015 3:43 PM
To: Charles, Lionel
Cc: Franklin, Bruce
Subject: RE: 4th day with no database

I was just talking to Bruce about the possibility that I might have used the selection of “Install Database Software Only” rather than “Create and Configure a Database” option…

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

From: Charles, Lionel
Sent: Wednesday, October 14, 2015 3:31 PM
To: Chando, Kenneth
Cc: Franklin, Bruce
Subject: RE: 4th day with no database

Ken,

I know you shadowed Bruce to get this completed and thanks to both of you. Did you see where something might have been missed causing the issue you encountered?

Thanks

Lionel

From: Chando, Kenneth
Sent: Wednesday, October 14, 2015 2:59 PM
To: Matthews, Gregory (Scott); Bailey, Denise Nikcevich; Dorgan, Dennis P.; Franklin, Bruce; Charles, Lionel
Cc: Ignatz, Bryan; Batheja, Rajeev
Subject: RE: 4th day with no database

Hi Dennis,

Thanks for your patience.

You can now connect to the database.

Let us know if you face any issues.

Thank you!

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

(Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

https://docs.oracle.com/cd/E23104_01/sysreqs1213/sysrs.htm

Thank you for your feedback |Recognition@hp

From: Matthews, Gregory (Scott)
Sent: Tuesday, October 13, 2015 2:41 PM
To: Bailey, Denise Nikcevich; Chando, Kenneth; Dorgan, Dennis P.; Franklin, Bruce; Charles, Lionel
Cc: Ignatz, Bryan; Batheja, Rajeev
Subject: RE: 4th day with no database

Ken,

Do these changes mean the database should be back up and running now?

Thanks

-Scott

Gregory Scott Matthews
DC2 Tools Engineer - DHS
DC2 Program, An ISO 20000:2011 Organization
HP Enterprise Services

gregory.matthews@hp.com
T +1 434 374 0621
Hewlett-Packard Company
Data Center 2
Clarksville, VA 23927

From: Bailey, Denise Nikcevich
Sent: Monday, October 12, 2015 5:35 PM
To: Chando, Kenneth; Dorgan, Dennis P.; Franklin, Bruce; Charles, Lionel
Cc: Matthews, Gregory (Scott); Ignatz, Bryan; Batheja, Rajeev
Subject: RE: 4th day with no database

It is my understanding that we should not be using memory_target, based off another admin who talked to Martin Fesmire, the Database Capability Lead for HPES. We should use the memory percentage parameter.

I have adjusted the /etc/sysctl.conf file with the correct parameters for 4 GB of memory and also added some RHEL tuning parameters that are supposed to provide.

Please let me know if you got it working.

Denise

Denise Nikcevich Bailey

UNIX/Linux Engineer
Global Engineering and Technical Consulting (GE&TC)

HP Enterprise Services

denise.bailey@hp.com
T +1 248 639 6067
M +1 248 497 1384
Hewlett-Packard Company
585 South Boulevard
Pontiac, MI 48341 (Eastern Time)
USA

Scheduled Time Off: October 19, November 30, December 1, (HPE Shutdown) 28,29,30,31

From: Chando, Kenneth
Sent: Monday, October 12, 2015 11:38 AM
To: Bailey, Denise Nikcevich; Dorgan, Dennis P.; Franklin, Bruce; Charles, Lionel
Cc: Matthews, Gregory (Scott); Ignatz, Bryan
Subject: RE: 4th day with no database

Hi Denise,

Here is what I just got from Oracle’s site concerning minimum requirements for a 12c database:

Please, let us know if anything else is needed.

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

From: Bailey, Denise Nikcevich
Sent: Monday, October 12, 2015 11:37 AM
To: Chando, Kenneth; Dorgan, Dennis P.; Franklin, Bruce; Charles, Lionel
Cc: Matthews, Gregory (Scott); Ignatz, Bryan
Subject: RE: 4th day with no database

If /dev/shm is low, please send the Oracle Note with the OS tuning requirements for RHEL version you are on in the Lab.

Thanks.

Denise

Denise Nikcevich Bailey

UNIX/Linux Engineer
Global Engineering and Technical Consulting (GE&TC)

HP Enterprise Services

denise.bailey@hp.com
T +1 248 639 6067
M +1 248 497 1384
Hewlett-Packard Company
585 South Boulevard
Pontiac, MI 48341 (Eastern Time)
USA

Scheduled Time Off: October 19, November 30, December 1, (HPE Shutdown) 28,29,30,31

From: Chando, Kenneth
Sent: Monday, October 12, 2015 8:10 AM
To: Dorgan, Dennis P.; Franklin, Bruce; Charles, Lionel
Cc: Matthews, Gregory (Scott); Ignatz, Bryan; Bailey, Denise Nikcevich
Subject: RE: 4th day with no database

Hi Brian/Denise,

After installing 12c on node D2LSENPSH164 in the DC2LAB, there is need for more memory.

Kindly address.

See below:

Thank you!

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

From: Chando, Kenneth
Sent: Friday, October 09, 2015 8:48 AM
To: Dorgan, Dennis P.; Franklin, Bruce; Charles, Lionel
Cc: Matthews, Gregory (Scott); Ignatz, Bryan
Subject: RE: 4th day with no database

Hi Dennis,

Good morning. After consulting with Oracle Support, they recommend us to rebuild the database.

I’m currently rebuilding it completely.

Will update you when it’s all done.

Thank you!

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( phone: (919) 424-5394

C phone (919) 349-5439

Thank you for your feedback |Recognition@hp

From: Dorgan, Dennis P.
Sent: Friday, October 09, 2015 8:46 AM
To: Chando, Kenneth; Franklin, Bruce; Charles, Lionel
Cc: Matthews, Gregory (Scott); Ignatz, Bryan
Subject: RE: 4th day with no database

Hi Ken:

Has there been any progress towards getting the CCC database operational again? Today is the 5^th day it has been down.

Thanks,

Dennis

From: Chando, Kenneth
Sent: Thursday, October 08, 2015 9:49 AM
To: Dorgan, Dennis P.; Franklin, Bruce; Charles, Lionel
Cc: Matthews, Gregory (Scott); Ignatz, Bryan
Subject: RE: 4th day with no database

Hi Dennis,

I have been in contact with Oracle support this morning and they’re looking into this.

I’m pushing them to get this issue taken care of as soon as possible.

The sad situation here is that as it stands currently, DC2LAB doesn’t have a media backup option for now. That would have made things easier for us to recover the file locally here at HP.

Sorry for the inconveniences caused.

Thank you!

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

(phone: (919) 424-5394

C phone (919) 349-5439

http://oracleinstance.blogspot.com/2009/12/enable-archivelog-and-flashback-in-rac.html

Thank you for your feedback |Recognition@hp

From: Dorgan, Dennis P.
Sent: Thursday, October 08, 2015 8:27 AM
To: Franklin, Bruce; Charles, Lionel; Chando, Kenneth
Cc: Matthews, Gregory (Scott); Ignatz, Bryan
Subject: 4th day with no database

Hello all:

What is happening with the Oracle database for CCC? This begins the 4^th day it has been down, and I can do nothing without it!

Please get this thing fixed!

Thanks,

Dennis

Manual Database Creation

Friday, October 16, 2015

8:16 AM

**** Set new database environment *****

. oraenv

**** Create password file ***

orapwd file=orapwCSGDB password=Password1 entries=30

sqlplus /nolog

connect sys/password as sysdba

startup nomount

CREATE DATABASE CSGDB

USER SYS IDENTIFIED BY Password1

USER SYSTEM IDENTIFIED BY Password1

LOGFILE GROUP 1 ('/u01/oradata/CSGDB/redo01a.log', '/u01/oradata/CSGDB/redo

01b.log') SIZE 10M,

GROUP 2 ('/u01/oradata/CSGDB/redo02a.log', '/u01/oradata/CSGDB/redo

02b.log') SIZE 10M,

GROUP 3 ('/u01/oradata/CSGDB/redo03a.log', '/u01/oradata/CSGDB/redo

03b.log') SIZE 10M

MAXLOGFILES 16

MAXLOGMEMBERS 3

MAXLOGHISTORY 200

MAXDATAFILES 100

MAXINSTANCES 8

CHARACTER SET WE8MSWIN1252

NATIONAL CHARACTER SET AL16UTF16

DATAFILE '/u01/oradata/CSGDB/system01.dbf' SIZE 325M REUSE

EXTENT MANAGEMENT LOCAL

DEFAULT TEMPORARY TABLESPACE temp

TEMPFILE '/u01/oradata/CSGDB/temp01.dbf'

SIZE 50M REUSE AUTOEXTEND on

sysaux

datafile '/u01/oradata/CSGDB/sysaux01.dbf'

SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED

UNDO TABLESPACE undotbs1

DATAFILE '/u01/oradata/CSGDB/undotbs01.dbf'

SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED;

SQL> !uname -a

SQL> @cr_CSGDB_DB.sql

Database created.

****** create additional tablespaces ******

spool cr_userapp_tbs.log

create tablespace users datafile '/u01/oradata/CSGDB/users01.dbf' size 10M extent management local autoallocate segment space management

auto;

create tablespace csg datafile '/u01/oradata/CSGDB/CSGDB.dbf' size 4000M extent management local autoallocate segment space management

auto;

create temporary tablespace temp tempfile '/u01/oradata/CSGDB/temp1.dbf' size 2000M reuse autoextend on;

spool off

******* Run catalog.sql ****

******* Run catproc.sql ****

******* create role and user ****

spool cr_csgADMINROLE.log

create role aradminrole;

grant alter session to csgadminrole;

grant CREATE CLUSTER to csgadminrole;

grant CREATE DATABASE LINK to csgadminrole;

grant CREATE PROCEDURE to csgadminrole;

grant CREATE SEQUENCE to csgadminrole;

grant CREATE SESSION to csgadminrole;

grant CREATE SYNONYM to aradminrole;

grant CREATE TABLE to csgadminrole;

grant CREATE TRIGGER to csgadminrole;

grant CREATE VIEW to csgadminrole;

grant QUERY REWRITE to csgadminrole;

create user csgadmin identified by c8es013gr# default tablespace csg temporary tablespace temp;

grant csgadminrole to csgadmin;

******* Create spfile from pfile ****

Script Database Creation

Friday, October 16, 2015

8:14 AM

/u01/app/oracle/product/11.2.0.3/bin/orapwd file=orapwCSGDB password=s3cur1ty entries=30

sqlplus /nolog

connect sys/s3cur1ty as sysdba

startup nomount

oracle@D2LSENPSH228[CSGDB]# sqlplus /nolog

SQL*Plus: Release 11.2.0.3.0 Production on Tue Aug 5 01:59:26 2014

SQL> sys/s3cur1ty as sysdba

SP2-0734: unknown command beginning "sys/s3cur1..." - rest of line ignored.

SQL> connect sys/s3cur1ty as sysdba

Connected.

SQL> shutdown

ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup nomount

ORACLE instance started.

Total System Global Area 1653518336 bytes

Fixed Size 2228904 bytes

Variable Size 1325403480 bytes

Database Buffers 318767104 bytes

Redo Buffers 7118848 bytes

SQL> @cr_CSGDB_DB.sql

Database created.

SQL> @cr_userapp_tbs.sql

Tablespace created.

PL/SQL procedure successfully completed.

TIMESTAMP

--------------------------------------------------------------------------------

COMP_TIMESTAMP CATALOG 2014-08-05 02:11:42

PL/SQL procedure successfully completed.

SQL>

SQL> SELECT dbms_registry_sys.time_stamp('CATPROC') AS timestamp FROM DUAL;

TIMESTAMP

--------------------------------------------------------------------------------

COMP_TIMESTAMP CATPROC 2014-08-05 02:21:27

1 row selected.

SQL>

SQL> SET SERVEROUTPUT OFF

SQL>

SQL> @cr_csgADMINROLE.sql

SQL> spool cr_csgADMINROLE.log

SQL>

SQL> create role csgadminrole;

Role created.

SQL>

SQL> grant alter session to csgadminrole;

Grant succeeded.

SQL> grant CREATE CLUSTER to csgadminrole;

Grant succeeded.

SQL> grant CREATE DATABASE LINK to csgadminrole;

Grant succeeded.

SQL> grant CREATE PROCEDURE to csgadminrole;

Grant succeeded.

SQL> grant CREATE SEQUENCE to csgadminrole;

Grant succeeded.

SQL> grant CREATE SESSION to csgadminrole;

Grant succeeded.

SQL> grant CREATE SYNONYM to aradminrole;

grant CREATE SYNONYM to aradminrole

ERROR at line 1:

ORA-01917: user or role 'ARADMINROLE' does not exist

SQL> grant CREATE TABLE to csgadminrole;

Grant succeeded.

SQL> grant CREATE TRIGGER to csgadminrole;

Grant succeeded.

SQL> grant CREATE VIEW to csgadminrole;

Grant succeeded.

SQL> grant QUERY REWRITE to csgadminrole;

Grant succeeded.

SQL>

SQL> create user csgadmin identified by c8es013gr# default tablespace csg temporary tablespace temp;

User created.

SQL>

SQL> grant csgadminrole to csgadmin;

Grant succeeded.

SQL>

SQL> spool off

SQL> grant CREATE SYNONYM to csgadminrole;

Grant succeeded.

SQL> grant csgadminrole to csgadmin;

Grant succeeded.

SQL> grant CREATE SYNONYM to csgadminrole;

Grant succeeded.

SQL> grant csgadminrole to csgadmin;

Grant succeeded.

SQL>

SQL> create spfile from pfile;

File created.

********

******* Apply Jul2014 patch

Patching component oracle.rdbms, 11.2.0.3.0...

Copying file to "/u01/app/oracle/product/11.2.0.3/cpu/CPUJul2014/catcpu.sql"

Copying file to "/u01/app/oracle/product/11.2.0.3/cpu/CPUJul2014/catcpu_rollback.sql"

Applying interim patch '18740215' to OH '/u01/app/oracle/product/11.2.0.3'

Patching component oracle.rdbms, 11.2.0.3.0...

Patching component oracle.rdbms.rsf, 11.2.0.3.0...

Patches 13742433,13742434,13742435,13742436,13742438,14062795,14062797,14480675,14480676,15862016,15862017,15862018,15862019,15862020,15862021,15862022,15862023,15862024,16314467,16794241,16794242,16794244,17333197,17333198,17333199,17333203,17748830,17748831,17748832,17748833,18173592,18173593,18173595,18681866,18740215 successfully applied.

Log file location: /u01/app/oracle/product/11.2.0.3/cfgtoollogs/opatch/opatch2014-08-05_13-50-38PM.log

OPatch succeeded.

SQL> PROMPT Updating registry...

Updating registry...

SQL> INSERT INTO registry$history

2 (action_time, action,

3 namespace, version, id,

4 bundle_series, comments)

5 VALUES

6 (SYSTIMESTAMP, 'APPLY',

7 SYS_CONTEXT('REGISTRY$CTX','NAMESPACE'),

8 '11.2.0.3',

9 11,

10 'CPU',

11 'CPUJul2014');

1 row created.

SQL> COMMIT;

Commit complete.

SQL> SPOOL off

SQL> SET echo off

Check the following log file for errors:

/u01/app/oracle/cfgtoollogs/catbundle/catbundle_CPU_CSGDB_APPLY_2014Aug05_14_04_09.

DC2 DATABASE SUPPORT_TECHNICAL DOCUMENTS

Wednesday, May 20, 2015

10:37 AM

============ORACLE TROUBLESHOOTING - OMER 2012============

Team,

Here are a few notes on troubleshooting common Oracle issues while you are on-call.

All Oracle and SQL servers we support are listed in spreadsheet. They are also listed in the two public groups I have created in HPSA: “Oracle Servers” and “SQL Servers” we will try to keep them up to date. HPSA will be the fastest way to get to these servers otherwise you may have to go through some jump servers to get to some of them when working from home.

Once you login with your own account to an oracle server issue “sudo su – oracle” to become the oracle user. We have setup the environment for the oracle user in all servers via the .profile. We created alias that will make you move around and access the databases easily. Here are some of the alias names you could use (just enter the alias and hit <Enter>)

alias scripts='cd /u01/app/oracle/scripts'

alias ll='ls -ltr'

alias nomon='sudoedit /opt/CA/SharedComponents/ccs/atech/agents/config/caiLogA2/*OraNegativeList.txt'

alias alog='tail -100 /u01/app/oracle/diag/rdbms/${ora_sid}/${ORACLE_SID}/trace/alert_${ORACLE_SID}.log'

alias bdump='cd /u01/app/oracle/diag/rdbms/${ora_sid}/${ORACLE_SID}/trace'

alias udump='cd /u01/app/oracle/diag/rdbms/${ora_sid}/${ORACLE_SID}/trace'

alias adump='cd /u01/app/oracle/admin/${ORACLE_SID}/adump'

alias cdump='cd /u01/app/oracle/admin/${ORACLE_SID}/cdump'

alias admin='cd /u01/app/oracle/admin/${ORACLE_SID}'

alias data='cd /u01/oradata/${ORACLE_SID}'

alias bkup='cd /u01/app/oracle/backup'

alias media='cd /u01/app/media'

alias pfile='cd $ORACLE_HOME/dbs'

alias dbs='cd $ORACLE_HOME/dbs'

alias arch='cd /u01/oradata/${ORACLE_SID}/arch'

alias sql='sqlplus "/ as sysdba"'

For example to look at the last 100 lines of the database alert log, which is helpful in troubleshooting issues, you would type alog and hit <Enter>

If you need to look up more lines you can go to the trace directory where the alert log is located by typing bdump and hitting <Enter> and then tail to any number of lines.

We have also created a collection of scripts and placed them in the /u01/app/oracle/scripts in all database servers. Just use the “scripts” alias to go there and look them out. Here are a sample helpful ones:

sh_active_locks.sql

sh_user_sql.sql -- display source code run by specific user session

sh_active_sessions.sql

sh_all_sessions.sql

sh_df.sql -- list datafiles and their auto extend storage

sh_temp_usage.sql -- who is currently using TEMP tablespace

sh_users.sql -- list database users and their default tablespaces and account status (whether open or locked)

sh_tsdf.sql -- list tablespace information. To get a good picture of auto extendible datafiles run sh_df.sql

sh_free_mem.sql

sh_waits.sql

sh_arch_hist.sql -- list archivelog sizing information by dates

sh_invalid_objects.sql

sh_sqlarea.sql -- what is currently running

In Servers that are configured as DataGuard (whether primary or standby) we can also run the alogs.sql script to list logs and show whether they have been applied to the standby or not. If there is a gap (logs not shipped or not applied) then there could be a communication issue between the servers. There are procedures for fixing the issue when standby is falling behind.

In that directory you will also see the netbackup RMAN scripts (start with nb_hot_backup_*.sh). The output of these scripts when executed by netbackup policies are saved in the scripts directory a nb_hot_backup_*.sh.out which you can check to diagnose backup issues.

Adjusting space if needed is straight forward using ALTER DATABASE or ALTER TABLESPACE commands.

You can use a few UNIX commands to check filesystem space utilization i.e. df –h | grep u01

You can also run the “top” command to check memory and cpu utilization.

To check the listener you can use lsnrctl commands to check status stop and start the service if/when needed.

For Oracle RAC we use a set of commands to check, start and stop database services and another set of commands to check, start, and stop cluster ready services (crs). These can be executed from either node of the cluster:

Server Control (srvctl commands) are used to check, start, or stop database instances and other services such as listener (instead of using sqlplus or lsnrctl as the case of standalone servers).. Here are some examples:

===== Check Status ================

Confirm that the Oracle ASM instance is running:

# srvctl status asm

ASM is running on d2aclprhq003,d2aclprhq004

# srvctl status instance -d ESDOP -n d2aclprhq003

Instance ESDOP1 is running on node d2aclprhq003

# srvctl status instance -d ESDOP -n d2aclprhq004

Instance ESDOP2 is running on node d2aclprhq004

# srvctl status instance -d ESDOP -i ESDOP1,ESDOP2

Instance ESDOP1 is running on node d2aclprhq003

Instance ESDOP2 is running on node d2aclprhq004

# srvctl status listener

Listener LISTENER is enabled

Listener LISTENER is running on node(s): d2aclprhq003,d2aclprhq004

# srvctl status scan_listener

SCAN Listener LISTENER_SCAN1 is enabled

SCAN listener LISTENER_SCAN1 is running on node d2aclprhq004

SCAN Listener LISTENER_SCAN2 is enabled

SCAN listener LISTENER_SCAN2 is running on node d2aclprhq003

SCAN Listener LISTENER_SCAN3 is enabled

SCAN listener LISTENER_SCAN3 is running on node d2aclprhq003

# srvctl status nodeapps

VIP d2aclprhq003-vip is enabled

VIP d2aclprhq003-vip is running on node: d2aclprhq003

VIP d2aclprhq004-vip is enabled

VIP d2aclprhq004-vip is running on node: d2aclprhq004

Network is enabled

Network is running on node: d2aclprhq003

Network is running on node: d2aclprhq004

GSD is disabled

GSD is not running on node: d2aclprhq003

GSD is not running on node: d2aclprhq004

ONS is enabled

ONS daemon is running on node: d2aclprhq003

ONS daemon is running on node: d2aclprhq004

eONS is enabled

eONS daemon is running on node: d2aclprhq003

eONS daemon is running on node: d2aclprhq004

====== STOP =====================

srvctl stop database -d IWMST

-- this stops database and shutdown all instances

srvctl stop instance -d IWMST -i IWMST1,IWMST2

srvctl stop instance -d IWMST -n d2acltscb010

srvctl stop instance -d IWMST -n d2acltscb011

srvctl stop instance -d ESDOP -n d2aclprhq004

-- To stop all services

srvctl stop nodeapps -n d2aclprhq003 -f -v

srvctl stop nodeapps -n d2aclprhq004 -f -v

srvctl stop listener

srvctl stop asm

====== START =====================

srvctl start asm

srvctl start database -d IWMST

-- this starts database and all instances

OR start each instance seprately

srvctl start instance -d IWMST -n d2acltscb010

srvctl start instance -d IWMST -n d2acltscb011

srvctl start listener

srvctl start nodeapps -n d2acltscb010

srvctl start nodeapps -n d2acltscb011

Usually all services start automatically when a server is rebooted unless there is an underlying issues such as asm disk.

Cluster Ready Service Control (crsctl) commands can be used to check, stop and start cluster services. You need to sudo from oracle to root to execute these commands:

export PATH=/u01/app/grid/bin:$PATH

export CRID_HOME=/u01/app/grid

====== STATUS CHECKS ================================================

[root@d2acltscb011 ~]# crs_stat -t

Name Type Target State Host

------------------------------------------------------------

ora.CRSDG.dg ora....up.type ONLINE ONLINE d2ac...b010

ora.DATADG.dg ora....up.type ONLINE ONLINE d2ac...b010

ora.FRADG.dg ora....up.type ONLINE ONLINE d2ac...b010

ora....ER.lsnr ora....er.type ONLINE ONLINE d2ac...b010

ora....N1.lsnr ora....er.type ONLINE ONLINE d2ac...b011

ora....N2.lsnr ora....er.type ONLINE ONLINE d2ac...b010

ora....N3.lsnr ora....er.type ONLINE ONLINE d2ac...b010

ora.asm ora.asm.type ONLINE ONLINE d2ac...b010

ora....SM1.asm application ONLINE ONLINE d2ac...b010

ora....10.lsnr application ONLINE ONLINE d2ac...b010

ora....010.gsd application OFFLINE OFFLINE

ora....010.ons application ONLINE ONLINE d2ac...b010

ora....010.vip ora....t1.type ONLINE ONLINE d2ac...b010

ora....SM2.asm application ONLINE ONLINE d2ac...b011

ora....11.lsnr application ONLINE ONLINE d2ac...b011

ora....011.gsd application OFFLINE OFFLINE

ora....011.ons application ONLINE ONLINE d2ac...b011

ora....011.vip ora....t1.type ONLINE ONLINE d2ac...b011

ora.eons ora.eons.type ONLINE ONLINE d2ac...b010

ora.gsd ora.gsd.type OFFLINE OFFLINE

ora.iwmst.db ora....se.type ONLINE ONLINE d2ac...b010

ora....network ora....rk.type ONLINE ONLINE d2ac...b010

ora.oc4j ora.oc4j.type OFFLINE OFFLINE

ora.ons ora.ons.type ONLINE ONLINE d2ac...b010

ora.scan1.vip ora....ip.type ONLINE ONLINE d2ac...b011

ora.scan2.vip ora....ip.type ONLINE ONLINE d2ac...b010

ora.scan3.vip ora....ip.type ONLINE ONLINE d2ac...b010

[root@d2acltscb011 ~]#

Use the crsctl check cluster command on any node in the cluster to check the

status of the Oracle Clusterware stack.

crsctl check cluster [-all | [-n server_name [...]]

# crsctl check cluster -all

**************************************************************

d2acltscb010:

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

**************************************************************

d2acltscb011:

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

**************************************************************

Use the crsctl check crs command to check the status of Oracle High Availability

Services and the Oracle Clusterware stack on the local server.

# crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

Use the crsctl check ctss command to check the status of the Cluster Time

Synchronization services

# crsctl check ctss

CRS-4700: The Cluster Time Synchronization Service is in Observer mode.

Use the crsctl query css votedisk command to display the voting disks used

by Cluster Synchronization Services, the status of the voting disks, and the location of

the disks, whether they are stored on Oracle ASM or elsewhere

# crsctl query css votedisk

## STATE File Universal Id File Name Disk group

-- ----- ----------------- --------- ---------

1. ONLINE 53c6bef2eb8e4fe2bfc807fdd7a080b0 (ORCL:CRS) [CRSDG]

Located 1 voting disk(s).

# crsctl status server

NAME=d2aclprhq003

STATE=ONLINE

NAME=d2aclprhq004

STATE=ONLINE

# crsctl status serverpool

NAME=Free

ACTIVE_SERVERS=

NAME=Generic

ACTIVE_SERVERS=d2aclprhq003 d2aclprhq004

NAME=ora.ESDOP

ACTIVE_SERVERS=d2aclprhq003 d2aclprhq004

====== START =====================================================

crsctl start crs

crsctl start cluster -all

crsctl start cluster [-all | -n server_name [...]]

crsctl start cluster -n d2aclprhq004

crsctl start cluster [-all | -n server_name [...]]

crsctl start cluster -n d2aclprhq004

Use the crsctl start cluster command on any node in the cluster to start the

Oracle Clusterware stack.

# cd /u01/app/grid/bin

# ./crsctl start cluster -n d2aclprhq004

CRS-2672: Attempting to start 'ora.cssd' on 'd2aclprhq004'

CRS-2672: Attempting to start 'ora.diskmon' on 'd2aclprhq004'

CRS-2676: Start of 'ora.diskmon' on 'd2aclprhq004' succeeded

CRS-2676: Start of 'ora.cssd' on 'd2aclprhq004' succeeded

CRS-2672: Attempting to start 'ora.ctssd' on 'd2aclprhq004'

CRS-2676: Start of 'ora.ctssd' on 'd2aclprhq004' succeeded

CRS-2679: Attempting to clean 'ora.asm' on 'd2aclprhq004'

CRS-5011: Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/u01/app/grid/log/d2aclprhq004/agent

/ohasd/oraagent_oracle/oraagent_oracle.log"

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

Linux-x86_64 Error: 2: No such file or directory

Process ID: 0

Session ID: 0 Serial number: 0

CRS-5011: Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/u01/app/grid/log/d2aclprhq004/agent

/ohasd/oraagent_oracle/oraagent_oracle.log"

CRS-2681: Clean of 'ora.asm' on 'd2aclprhq004' succeeded

CRS-2672: Attempting to start 'ora.asm' on 'd2aclprhq004'

CRS-2676: Start of 'ora.asm' on 'd2aclprhq004' succeeded

CRS-2672: Attempting to start 'ora.crsd' on 'd2aclprhq004'

CRS-2676: Start of 'ora.crsd' on 'd2aclprhq004' succeeded

-bash-3.2#

====== STOP =====================================================

crsctl stop cluster [-all | -n server_name [...]] [-f]

crsctl stop cluster

crsctl stop crs

crsctl stop crs -f

crsctl stop cluster

crsctl stop crs

Use the crsctl stop cluster command on any node in the cluster to stop the

Oracle Clusterware stack on all servers in the cluster or specific servers.

Syntax

crsctl stop cluster [-all | -n server_name [...]] [-f]

crsctl stop crs

Use the crsctl stop crs command to stop Oracle High Availability Services on

the local server.

Syntax

crsctl stop crs [-f]

=================ASM DISK MIGRATE=====================================

1.List storage devices and make sure that new disks are visible to both cluster nodes.

Migrate

Migrate ASM to new disks

fdisk -l

Disk /dev/sdg: 8589 MB, 8589934592 bytes

255 heads, 63 sectors/track, 1044 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdg doesn't contain a valid partition table

Disk /dev/sdh: 64.4 GB, 64424509440 bytes

255 heads, 63 sectors/track, 7832 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdh doesn't contain a valid partition table

Disk /dev/sdi: 32.2 GB, 32212254720 bytes

255 heads, 63 sectors/track, 3916 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdi doesn't contain a valid partition table

2. Partition the new disks

-bash-3.2# fdisk /dev/sdg

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

The number of cylinders for this disk is set to 1044.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n

Command action

e extended

p primary partition (1-4)

Partition number (1-4): 1

First cylinder (1-1044, default 1):

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-1044, default 1044):

Using default value 1044

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.

The kernel still uses the old table.

The new table will be used at the next reboot.

Syncing disks.

-bash-3.2#

-bash-3.2# fdisk /dev/sdh

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

The number of cylinders for this disk is set to 7832.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n

Command action

e extended

p primary partition (1-4)

Partition number (1-4): 1

First cylinder (1-7832, default 1):

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-7832, default 7832):

Using default value 7832

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.

The kernel still uses the old table.

The new table will be used at the next reboot.

Syncing disks.

-bash-3.2# fdisk /dev/sdi

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

The number of cylinders for this disk is set to 3916.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n

Command action

e extended

p primary partition (1-4)

Partition number (1-4): 1

First cylinder (1-3916, default 1):

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-3916, default 3916):

Using default value 3916

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.

The kernel still uses the old table.

The new table will be used at the next reboot.

Syncing disks.

3.List the disks again to verify new partitions are listed on both nodes

-bash-3.2# fdisk -l

Disk /dev/sda: 85.8 GB, 85899345920 bytes

255 heads, 63 sectors/track, 10443 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 33 265041 83 Linux

/dev/sda2 34 5238 41809162+ 8e Linux LVM

/dev/sda3 5239 10443 41809162+ 8e Linux LVM

Disk /dev/sdb: 5368 MB, 5368709120 bytes

255 heads, 63 sectors/track, 652 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 47.2 GB, 47244640256 bytes

255 heads, 63 sectors/track, 5743 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/sdd: 21.4 GB, 21474836480 bytes

255 heads, 63 sectors/track, 2610 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/sde: 26.8 GB, 26843545600 bytes

255 heads, 63 sectors/track, 3263 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sde doesn't contain a valid partition table

Disk /dev/sdf: 1073 MB, 1073741824 bytes

255 heads, 63 sectors/track, 130 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdf doesn't contain a valid partition table

Disk /dev/sdg: 8589 MB, 8589934592 bytes

255 heads, 63 sectors/track, 1044 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdg1 1 1044 8385898+ 83 Linux

Disk /dev/sdh: 64.4 GB, 64424509440 bytes

255 heads, 63 sectors/track, 7832 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdh1 1 7832 62910508+ 83 Linux

Disk /dev/sdi: 32.2 GB, 32212254720 bytes

255 heads, 63 sectors/track, 3916 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdi1 1 3916 31455238+ 83 Linux

4.List current asm disks

-bash-3.2# /etc/init.d/oracleasm listdisks

CRS

DATA

FRA

5.Label new asm disks

-bash-3.2# /etc/init.d/oracleasm createdisk OCRDISK /dev/sdg1

Marking disk "OCRDISK" as an ASM disk: [ OK ]

-bash-3.2# /etc/init.d/oracleasm createdisk DATADISK /dev/sdh1

Marking disk "DATADISK" as an ASM disk: [ OK ]

-bash-3.2# /etc/init.d/oracleasm createdisk FRADISK /dev/sdi1

Marking disk "FRADISK" as an ASM disk: [ OK ]

-bash-3.2# /etc/init.d/oracleasm scandisks

Scanning the system for Oracle ASMLib disks:

[ OK ]

6.Verify ASM disks again

-bash-3.2# /etc/init.d/oracleasm listdisks

CRS

DATA

DATADISK

FRA

FRADISK

OCRDISK

7.Add new ASM Disks to ASM

-bash-3.2# sudo su - oracle

oracle@D2LSENPSH165[orcl1]# goasm

oracle@D2LSENPSH165[+ASM1]# sql

SQL*Plus: Release 11.2.0.3.0 Production on Wed Feb 18 19:57:08 2015

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Real Application Clusters and Automatic Storage Management options

SQL>

set pages 999 lines 120

col name format a20

col path format a20

SELECT name, path, header_status, total_mb, free_mb FROM V$ASM_DISK;

NAME PATH HEADER_STATU TOTAL_MB FREE_MB

-------------------- -------------------- ------------ ---------- ----------

ORCL:DATADISK PROVISIONED 0 0

ORCL:FRADISK PROVISIONED 0 0

ORCL:OCRDISK PROVISIONED 0 0

CRS ORCL:CRS MEMBER 5120 4725

DATA ORCL:DATA MEMBER 45056 16108

FRA ORCL:FRA MEMBER 20480 18710

6 rows selected.

SQL>select name, state, total_mb, free_mb from V$ASM_DISKGROUP;

NAME STATE TOTAL_MB FREE_MB

------------------------------ ----------- ---------- ----------

CRSDG MOUNTED 5120 4725

DATADG MOUNTED 45056 16108

FRADG MOUNTED 21504 19598

SQL>Alter diskgroup CRSDG ADD DISK 'ORCL:OCRDISK' REBALANCE POWER 9;

Diskgroup altered.

SQL>Alter diskgroup FRADG ADD DISK 'ORCL:FRADISK' REBALANCE POWER 9;

Diskgroup altered.

SQL>Alter diskgroup DATADG ADD DISK 'ORCL:DATADISK' REBALANCE POWER 9;

Diskgroup altered.

SQL>select group_number, name, state, total_mb, free_mb from V$ASM_DISKGROUP;

GROUP_NUMBER NAME STATE TOTAL_MB FREE_MB

------------ ------------------------------ ----------- ---------- ----------

1 CRSDG MOUNTED 13309 12912

2 DATADG MOUNTED 106492 77542

3 FRADG MOUNTED 52222 50314

SQL>SELECT GROUP_NUMBER, OPERATION, STATE, POWER, EST_MINUTES FROM V$ASM_OPERATION;

GROUP_NUMBER OPERA STAT POWER EST_MINUTES

------------ ----- ---- ---------- -----------

2 REBAL WAIT 9

3 REBAL RUN 9 0

SQL> /

GROUP_NUMBER OPERA STAT POWER EST_MINUTES

------------ ----- ---- ---------- -----------

2 REBAL WAIT 9

SQL> /

no rows selected

SQL>

set pages 999 lines 120

col name format a20

col path format a20

SELECT name, path, header_status, total_mb, free_mb FROM V$ASM_DISK;

NAME PATH HEADER_STATU TOTAL_MB FREE_MB

-------------------- -------------------- ------------ ---------- ----------

CRS ORCL:CRS MEMBER 5120 4945

DATA ORCL:DATA MEMBER 45056 32778

FRA ORCL:FRA MEMBER 20480 19663

DATADISK ORCL:DATADISK MEMBER 61436 44764

FRADISK ORCL:FRADISK MEMBER 30718 29670

OCRDISK ORCL:OCRDISK MEMBER 8189 7967

6 rows selected.

8.Drop old ASM Disks from ASM

SQL>Alter diskgroup CRSDG DROP DISK CRS rebalance power 9;

Diskgroup altered.

SQL>Alter diskgroup FRADG DROP DISK FRA rebalance power 9;

Diskgroup altered.

SQL>Alter diskgroup DATADG DROP DISK DATA rebalance power 9;

Diskgroup altered.

SQL>

SQL>SELECT GROUP_NUMBER, OPERATION, STATE, POWER, EST_MINUTES FROM V$ASM_OPERATION;

GROUP_NUMBER OPERA STAT POWER EST_MINUTES

------------ ----- ---- ---------- -----------

2 REBAL RUN 9 4

SQL> /

no rows selected

SQL>

set pages 999 lines 120

col name format a20

col path format a20

SELECT name, path, header_status, total_mb, free_mb FROM V$ASM_DISK;

NAME PATH HEADER_STATU TOTAL_MB FREE_MB

-------------------- -------------------- ------------ ---------- ----------

ORCL:CRS FORMER 0 0

ORCL:DATA MEMBER 0 0

ORCL:DATADISK MEMBER 0 0

ORCL:FRA FORMER 0 0

FRADISK ORCL:FRADISK MEMBER 30718 28807

OCRDISK ORCL:OCRDISK MEMBER 8189 7794

6 rows selected.

SQL>ALTER DISKGROUP DATADG MOUNT;

Diskgroup altered.

SQL>

set pages 999 lines 120

col name format a20

col path format a20

SELECT name, path, header_status, total_mb, free_mb FROM V$ASM_DISK;

NAME PATH HEADER_STATU TOTAL_MB FREE_MB

-------------------- -------------------- ------------ ---------- ----------

ORCL:CRS FORMER 0 0

ORCL:DATA FORMER 0 0

ORCL:FRA FORMER 0 0

DATADISK ORCL:DATADISK MEMBER 61436 32488

FRADISK ORCL:FRADISK MEMBER 30718 28807

OCRDISK ORCL:OCRDISK MEMBER 8189 7794

6 rows selected.

9.Delete ASM disk labels of old disks

As root:

In node 1

-bash-3.2# /etc/init.d/oracleasm listdisks

CRS

DATA

DATADISK

FRA

FRADISK

OCRDISK

-bash-3.2#

-bash-3.2# /etc/init.d/oracleasm deletedisk CRS

Removing ASM disk "CRS": [ OK ]

-bash-3.2#

-bash-3.2# /etc/init.d/oracleasm deletedisk DATA

Removing ASM disk "DATA": [ OK ]

-bash-3.2#

-bash-3.2# /etc/init.d/oracleasm deletedisk FRA

Removing ASM disk "FRA": [ OK ]

If a disk label cannot be removed (because of BUG that even after the drop claims that the disk is busy), clean Header by issuing the following command and then try the deletedisk command again :

# dd if=/dev/zero of=/dev/sdf bs=1024 count=100

10. Make sure old ASM disk labels are removed from both Nodes

In Node 1

-bash-3.2# /etc/init.d/oracleasm listdisks

DATADISK

FRADISK

OCRDISK

In Node 2

-bash-3.2# /etc/init.d/oracleasm listdisks

CRS

DATA

DATADISK

FRA

FRADISK

OCRDISK

-bash-3.2# /etc/init.d/oracleasm scandisks

Scanning the system for Oracle ASMLib disks:

[ OK ]

-bash-3.2# /etc/init.d/oracleasm listdisks

DATADISK

FRADISK

OCRDISK

11. Have UNIX SA and Storage Admin remove old storage devices

=============HOW TO ENABLE FLASHBACK DATABASE=============

How to Enable Flashback Database

To enable flashback database the following operations is needed.

1)Configure the Database in archivelog mode.

Changing the Database Archiving Mode

1)See the current archiving mode of the database.

select log_mode from v$database;

2)Perform clean shutdown of the database.

shutdown immediate or,

shutdown transactional or,

shutdown normal

You cannot change the mode from ARCHIVELOG to NOARCHIVELOG if any datafiles need media recovery.

3)Backup the Database.

4)If you use pfile as initialization file then edit the archive destination parameter (like LOG_ARCHIVE_DEST) as your archival destination. If you use spfile ignore this step.

5)Mount the database but don't open.

STARTUP MOUNT

6)Change the archival mode and open the database.

ALTER DATABASE ARCHIVELOG

If you use spfile then you can use ALTER SYSTEM SET LOG_ARCHIVE_DEST='your location'

ALTER DATABASE OPEN;

7)Check the archival Location

archive log list

8)Shutdown and Backup the database.

SHUTDOWN IMMEDIATE

2)Configure Flash Recovery Area.

To configure flash recovery area,

Set Up a Flash Recovery Area for RMAN

Flash recovery area simplifies the ongoing administration of your database by automatically naming recovery-related files, retaining them as long as they are needed for restore and recovery activities, and deleting them when they are no longer needed to restore your database and space is needed for some other backup and recovery-related purpose.

To see up flash recovery follow below steps.

1)Set up DB_RECOVERY_FILE_DEST_SIZE:

SQL> alter system set db_recovery_file_dest_size=2G;

2)Decide the area from OS where you will place Flash recovery area.

SQL>host mkdir /oradata1/flash_recovery_area

3)Set up DB_RECOVERY_FILE_DEST:

SQL> alter system set db_recovery_file_dest='/oradata1/flash_recovery_area';

The V$RECOVERY_FILE_DEST and V$FLASH_RECOVERY_AREA_USAGE views can help to find out the current location, disk quota, space in use, space reclaimable by deleting files,total number of files, the percentage of the total disk quota used by different types of files, and how much space for each type of file can be reclaimed by deleting files that are obsolete, redundant, or already backed up to tape.

In order to disable flash recovery area issue,

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST='' SCOPE=BOTH SID='*';

3)Clean Shutdown and mount the database.

SQL> SHUT IMMEDIATE;

SQL> STARTUP MOUNT;

SQL> Alter Database Flashback ON;

Before running command you can check whether flashback was actually On or not.

select flashback_on from v$database;

Steps:

------

SQL> alter database flashback ON;

Database altered.

SQL> select flashback_on from v$database;

FLASHBACK_ON

------------------

YES

4)Open the database and optionally you can set DB_FLASHBACK_RETENTION_TARGET to the length of the desired flashback window in minutes. By default it is 1 day(1440 minutes).

SQL> ALTER DATABASE OPEN;

To make it 3 days

SQL> ALTER SYSTEM SET DB_FLASHBACK_RETENTION_TARGET=4320;

SQL> show parameter DB_FLASHBACK_RETENTION_TARGET

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

db_flashback_retention_target integer 4320

However you can disable Flashback Database for a tablespace.Then you must take its datafiles offline before running FLASHBACK DATABASE.

Like,

SQL> select file_name,file_id from dba_data_files where tablespace_name='TEST';

FILE_NAME FILE_ID

------------------------------ ----------

/oradata2/1.dbf 5

SQL> alter database datafile 5 offline;

Database altered.

SQL> ALTER TABLESPACE test flashback off;

Tablespace altered.

SQL> recover datafile 5;

Media recovery complete.

SQL> alter database datafile 5 online;

Database altered.

To disable flashback feature simply issue,

SQL>ALTER DATABASE FLASHBACK OFF;

Database altered.

===ENABLE ARCHIVELOG AND FLASHBACK IN RAC DATABASE===

Step by step process of putting a RAC database in archive log mode and then enabling the flashback Database option.

Enabling archive log in RAC Database:

A database must be in archivelog mode before enabling flashback.

In this example database name is test and instances name are test1 and test2.

step 1:

creating recovery_file_dest in asm disk

SQL> alter system set db_recovery_file_dest_size=200m sid='*';

System altered.

SQL> alter system set db_recovery_file_dest='+DATA' sid='*';

System altered.

SQL> archive log list;

Database log mode No Archive Mode

Automatic archival Disabled

Archive destination USE_DB_RECOVERY_FILE_DEST

Oldest online log sequence 12

Current log sequence 14

SQL>

step 2:

set the LOG_ARCHIVE_DEST_1 parameter. since these parameters will be identical for all nodes, we will use sid='*'. However, you may need to modify this for your situation if the directories are different on each node.

SQL> alter system set log_archive_dest_1='LOCATION=USE-DB_RECOVERY_FILE_DEST';

System altered.

step 3:

set LOG_ARCHIVE_START to TRUE for all instances to enable automatic archiving.

SQL> alter system set log_archive_start=true scope=spfile sid='*';

System altered.

Note that we illustrate the command for backward compatibility purposes, but in oracle database 10g onwards, the parameter is actually deprecated. Automatic archiving will be enabled by default whenever an oracle database is placed in archivelog mode.

step 4:

Set CLUSTER_DATABASE to FALSE for the local instance, which you will then mount to put the database into archivelog mode. By having CLUSTER_DATABASE=FALSE, the subsequent shutdown and startup mount will actually do a Mount Exclusive by default, which is necessary to put the database in archivelog mode, and also to enable the flashback database feature:

SQL> alter system set cluster_database=false scope=spfile sid='test1';

System altered.

step 5;

Shut down all instances. Ensure that all instances are shut down cleanly:

SQL> shutdown immediate

step 6:

Mount the database from instance test1 (where CLUSTER_DATABASE was set to FALSE) and then put the database into archivelog mode.

SQL> startup mount

ORA-32004: obsolete and/or deprecated parameter(s) specified

ORACLE instance started.

Database mounted.

SQL> alter database archivelog;

Database altered.

NOTE:

If you did not shut down all instances cleanly in step 5,

putting the database in archivelog mode will fail

with an ORA-265 Error.

SQL> alter database archivelog;

ERROR at line 1:

ORA-00265: instance recovery required, cannot set ARCHIVELOG mode

step 7:

Confirm that the database is in archivelog mode, with the appropriate parameters, by issuing the ARCHIVE LOG LIST command:

SQL> archive log list;

Database log mode Archive Mode

Automatic archival Enabled

Archive destination USE-DB_RECOVERY_FILE_DEST

Oldest online log sequence 13

Next log sequence to archive 15

Current log sequence 15

step 8

Confirm the location of the RECOVERY_FILE_DEST via a SHOW PARAMETER.

SQL> show parameter recovery_file

NAME TYPEVALUE

------------------------------------ ----------- ------------------------------

db_recovery_file_dest string +DATA

db_recovery_file_dest_size big integer 200M

Step 9:

Once the database is in archivelog mode, you can enable flashback while the database is still mounted in Exclusive mode (CLUSTER_DATABASE=FALSE).

SQL> alter database flashback on;

Database altered.

Step 10:

Confirm that Flashback is enabled and verify the retention target:

SQL> select flashback_on,current_scn from v$database;

FLASHBACK_ONCURRENT_SCN

------------------ -----------

YES0

SQL> show parameter flash

NAMETYPE VALUE

------------------------------------ ----------- ------------------------------

db_flashback_retention_target integer1440

step 11:

Reset the CLUSTER_DATABASE parameter back to TRUE for all instances:

SQL> alter system set cluster_database=true scope=spfile sid=' * ';

System altered.

step 12:

shutdown the instance and then restart all cluster database instances.

All instances will now be archiving their redo threads.

SQL> shu immediate

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

start the database, using srvctl command or normal startup

[root@rac1 bin]# ./srvctl status database -d test

Instance test1 is not running on node rac1

Instance test2 is not running on node rac2

[root@rac1 bin]# ./srvctl start database -d test

[root@rac1 bin]# ./srvctl status database -d test

Instance test1 is running on node rac1

Instance test2 is running on node rac2

[root@rac1 bin]#

on test1 instance:

SQL> archive log list;

Database log mode Archive Mode

Automatic archival Enabled

Archive destination USE-DB_RECOVERY_FILE_DEST

Oldest online log sequence 14

Next log sequence to archive 16

Current log sequence 16

SQL>

on test2 instance:

SQL> archive log list;

Database log mode Archive Mode

Automatic archival Enabled

Archive destination USE-DB_RECOVERY_FILE_DEST

Oldest online log sequence 3

Next log sequence to archive 5

Current log sequence 5

SQL>

wow, both are in archive log mode

hope, this document will help you .

regards,

rajeshkumar g

UPGRADE GUIDE

Wednesday, June 17, 2015

8:01 AM

How to Upgrade to Oracle Grid Infrastructure 12c Release 1 (LINUX - LAB)

http://docs.oracle.com/database/121/CWLIN/procstop.htm#CWLIN10001

This appendix describes how to perform Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM) upgrades.

Oracle Clusterware upgrades can be rolling upgrades, in which a subset of nodes are brought down and upgraded while other nodes remain active. Oracle ASM 12c Release 1 (12.1) upgrades can be rolling upgrades. If you upgrade a subset of nodes, then a software-only installation is performed on the existing cluster nodes that you do not select for upgrade.

This appendix contains the following topics:

· Back Up the Oracle Software Before Upgrades

· About Oracle Grid Infrastructure and Oracle ASM Upgrade and Downgrade

· Options for Oracle Grid Infrastructure Upgrades and Downgrades

· Restrictions and Guidelines for Oracle Grid Infrastructure Upgrades

· Preparing to Upgrade an Existing Oracle Clusterware Installation

· Using CVU to Validate Readiness for Oracle Clusterware Upgrades

· Understanding Rolling Upgrades Using Batches

· Performing Rolling Upgrade of Oracle Grid Infrastructure

· Performing Rolling Upgrade of Oracle ASM

· Applying Patches to Oracle ASM

· Updating Oracle Enterprise Manager Cloud Control Target Parameters

· Unlocking the Existing Oracle Clusterware Installation

· Checking Cluster Health Monitor Repository Size After Upgrading

· Downgrading Oracle Clusterware After an Upgrade

B.0 Downloading Oracle 12c GI and DB Software

Grid Infrastructure:

http://download.oracle.com/otn/linux/oracle12c/121010/linuxamd64_12c_grid_1of2.zip

http://download.oracle.com/otn/linux/oracle12c/121010/linuxamd64_12c_grid_2of2.zip

RDBMS:

http://download.oracle.com/otn/linux/oracle12c/121020/linuxamd64_12102_database_1of2.zip

http://download.oracle.com/otn/linux/oracle12c/121020/linuxamd64_12102_database_2of2.zip

B.1 Back Up the Oracle Software Before Upgrades

Before you make any changes to the Oracle software, Oracle recommends that you create a backup of the Oracle software and databases.

GRID_HOME=/u01/app/11.2.0.3/grid

RDBMS_HOME=/u01/app/oracle/product/11.2.0.3

ORACLE_DB=LABDB

ORACLE_SIDs=LABDB1, LABDB2

cd /u01/app/backup

tar -cvf oracle_home_11203.tar /u01/app/oracle/product/11.2.0.3

gzip oracle_home_11203.tar

tar -cvf oracle_inventory.tar /u01/app/oracle/oraInventory

gzip oracle_inventory.tar

B.3 Options for Oracle Grid Infrastructure Upgrades and Downgrades

Upgrade options from Oracle Grid Infrastructure 11g to Oracle Grid Infrastructure 12c include the following:

· Oracle Grid Infrastructure rolling upgrade which involves upgrading individual nodes without stopping Oracle Grid Infrastructure on other nodes in the cluster

· Oracle Grid Infrastructure non-rolling upgrade by bringing the cluster down and upgrading the complete cluster

Upgrade options from Oracle Grid Infrastructure 11g Release 2 (11.2) to Oracle Grid Infrastructure 12c include the following:

· Oracle Grid Infrastructure rolling upgrade, with OCR and voting disks on Oracle ASM

· Oracle Grid Infrastructure complete cluster upgrade (downtime, non-rolling), with OCR and voting disks on Oracle ASM

Downgrade options from Oracle Grid Infrastructure 12c to earlier releases include the following:

· Oracle Grid Infrastructure downgrade to Oracle Grid Infrastructure 11g Release 2 (11.2)

· Oracle Grid Infrastructure downgrades to releases before Oracle Grid Infrastructure 11g Release 2 (11.2), Oracle Grid Infrastructure 11gRelease 1 (11.1), Oracle Clusterware and Oracle ASM 10g, if storage for OCR and voting files is on storage other than Oracle ASM

B.4 Restrictions and Guidelines for Oracle Grid Infrastructure Upgrades

Oracle recommends that you use the Cluster Verification Utility tool (CVU) to check if there are any patches required for upgrading your existing Oracle Grid Infrastructure 11g Release 2 (11.2) or Oracle RAC database 11g Release 2 (11.2) installations.

Be aware of the following restrictions and changes for upgrades to Oracle Grid Infrastructure installations, which consists of Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM):

· Do not delete directories in the Grid home. For example, do not delete the directory Grid_home/Opatch. If you delete the directory, then the Grid infrastructure installation owner cannot use OPatch to patch the grid home, and OPatch displays the error message "'checkdir' error: cannot create Grid_home/OPatch".

· To upgrade existing Oracle Grid Infrastructure installations to Oracle Grid Infrastructure 12c Release 1 (12.1), you must first verify if you need to apply any mandatory patches for upgrade to succeed. See Section B.6 for steps to check readiness.

See Also:

Oracle 12c Upgrade Companion (My Oracle Support Note 1462240.1

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1462240.1

· Oracle Clusterware and Oracle ASM upgrades are always out-of-place upgrades. You cannot perform an in-place upgrade of Oracle Clusterware and Oracle ASM to existing homes.

· The same user that owned the earlier release Oracle Grid Infrastructure software must perform the Oracle Grid Infrastructure 12c Release 1 (12.1) upgrade. Before Oracle Database 11g, either all Oracle software installations were owned by the Oracle user, typically oracle, or Oracle Database software was owned by oracle, and Oracle Clusterware software was owned by a separate user, typically crs.

· Oracle ASM and Oracle Clusterware both run in the Oracle Grid Infrastructure home.

· During a major release upgrade to Oracle Grid Infrastructure 12c Release 1 (12.1), the software in the 12c Release 1 (12.1) Oracle Grid Infrastructure home is not fully functional until the upgrade is completed. Running srvctl, crsctl, and other commands from the new Grid homes are not supported until the final rootupgrade.sh script is run and the upgrade is complete across all nodes.

To manage databases in existing earlier release database homes during the Oracle Grid Infrastructure upgrade, use the srvctl from the existing database homes.

B.5 Preparing to Upgrade an Existing Oracle Clusterware Installation

If you have an existing Oracle Clusterware installation, then you upgrade your existing cluster by performing an out-of-place upgrade. You cannot perform an in-place upgrade.

The following sections list the steps you can perform before you upgrade Oracle Grid Infrastructure:

B.5.1 Checks to Complete Before Upgrading Oracle Clusterware

Complete the following tasks before starting an upgrade:

1. For each node, use Cluster Verification Utility to ensure that you have completed preinstallation steps. It can generate Fixup scripts to help you to prepare servers. In addition, the installer will help you to ensure all required prerequisites are met.

Ensure that you have information you will need during installation, including the following:

· An Oracle base location for Oracle Clusterware.

GRID_HOME=/u01/app/11.2.0.3/grid

ORACLE_BASE=/u01/app/oracle

ORACLE_HOME=/u01/app/oracle/product/11.2.0.3

ORACLE_DB=LABDB

ORACLE_SIDs=LABDB1, LABDB2

· An Oracle Grid Infrastructure home location that is different from your existing Oracle Clusterware location.

GRID_HOME=/u01/app/12.2.0.3/grid

· SCAN name and addresses, and other network addresses, as described in Chapter 5.

· Privileged user operating system groups, as described in Chapter 6.

· root user access, to run scripts as root during installation, using one of the options described in Section 8.1.1.

2. For the installation owner running the installation, if you have environment variables set for the existing installation, then unset the environment variables $ORACLE_HOME and $ORACLE_SID, as these environment variables are used during upgrade. For example:

3. If the cluster was previously forcibly upgraded, then ensure that all inaccessible nodes have been deleted from the cluster or joined to the cluster before starting another upgrade. For example, if the cluster was forcibly upgraded from 11.2.0.3 to 12.1.0.1, then ensure that all inaccessible nodes have been deleted from the cluster or joined to the cluster before upgrading to another release, for example, 12.1.0.2.

B.5.2 Unset Oracle Environment Variables

Unset Oracle environment variables.

If you have set ORA_CRS_HOME as an environment variable, following instructions from Oracle Support, then unset it before starting an installation or upgrade. You should never use ORA_CRS_HOME as an environment variable except under explicit direction from Oracle Support.

Check to ensure that installation owner login shell profiles (for example, .profile or .cshrc) do not have ORA_CRS_HOME set.

If you have had an existing installation on your system, and you are using the same user account to install this installation, then unset the following environment variables: ORA_CRS_HOME; ORACLE_HOME; ORA_NLS10; TNS_ADMIN; and any other environment variable set for the Oracle installation user that is connected with Oracle software homes.

Also, ensure that the $ORACLE_HOME/bin path is removed from your PATH environment variable.

unset ORACLE_BASE

unset ORACLE_HOME

unset ORACLE_SID

unset TNS_ADMIN

export PATH=/usr/sbin:/usr/proc/bin:/usr/local/bin:/usr/local/sbin:/usr/ccs/bin:/usr/local/bin:/bin:/usr/bin

B.5.3 Running the Oracle ORAchk Upgrade Readiness Assessment

ORAchk (Oracle RAC Configuration Audit Tool) Upgrade Readiness Assessment can be used to obtain an automated upgrade-specific health check for upgrades to Oracle Grid Infrastructure 11.2.0.3, 11.2.0.4, 12.1.0.1, and 12.1.0.2. You can run the ORAchk Upgrade Readiness Assessment tool and automate many of the manual pre-upgrade and post upgrade checks.

Oracle recommends that you download and run the latest version of ORAchk from My Oracle Support. For information about downloading, configuring, and running ORAchk configuration audit tool, refer to My Oracle Support note 1457357.1

, which is available at the following URL:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1457357.1

Execution Instructions

Note: It is highly recommend that you review Document 1268927.2 as well as the ORAchk Users Guide for a full understanding of ORAchk prior to executing the steps below.

1. Download ORAchk from Document 1268927.2.

2. Log in to the system as the Oracle RDBMS software installation owner.

3. Stage the orachk.zip kit (downloaded in step 1) in its own directory the node on which the tool will be executed.

4. Unzip orachk.zip kit, leaving the script and driver files together in the same directory.

5. Validate the permissions for orachk are 755 (-rwxr-xr-x). If the permissions are not currently set to 755, set the permissions on orachk as follows:

$ chmod 755 orachk

6. During the 11.2.0.3 upgrade planning phase of your pending RAC upgrade, execute ORAchk in pre-upgrade mode and follow the on-screen prompts:
Note: It is HIGHLY recommended that the pre-upgrade checks are executed in the planning phase of the upgrade. This will allow planning and implementation of findings highlighted by ORAchk.

$ ./orachk -u -o pre

7. Review the HTML report generated by the ORAchk pre-upgrade execution and implement the recommended changes as necessary.

8. Once you have successfully upgraded (GI and/or RDBMS), execute ORAchk in post-upgrade mode and follow the on-screen prompts:

$ ./orachk -u -o post

9. Review the HTML report generated by the ORAchk post-upgrade execution and implement the recommended changes as necessary.

What to expect

· The target clusterware and database versions are 11.2.0.3, 11.2.0.4 and 12.1.0.1

· In pre-upgrade mode the tool will detect all databases registered in the clusterware automatically and present a list of databases on which to perform pre-upgrade checks. If any databases that were already upgraded are selected, the pre-upgrade checks will be skipped for them.

· In post-upgrade mode the tool will detect all databases registered in the clusterware automatically and present a list of databases on which to perform post-upgrade checks. If any databases that were not upgraded are selected, the post-upgrade checks will be skipped for them.

· In both modes the tool will check the clusterware and OS appropriately.

· When the tool completes the user will be referred to an HTML formated report which will contain the findings and links to additional details and information.

oracle@D2LSENPSH160[LABDB1]# ./orachk -u -o pre

Enter upgrade target version (valid versions are 11.2.0.3.0, 11.2.0.4.0, 12.1.0.1.0, 12.1.0.2.0):- 12.1.0.2.0

CRS stack is running and CRS_HOME is not set. Do you want to set CRS_HOME to /u01/app/11.2.0.3/grid?[y/n][y]y

Checking ssh user equivalency settings on all nodes in cluster

Node d2lsenpsh161 is configured for ssh user equivalency for oracle user

Searching for running databases . . . . .

. .

List of running databases registered in OCR

1. LABDB

2. None of above

Select databases from list for checking best practices. For multiple databases, select 1 for All or comma separated number like 1,2 etc [1-2][1].1

. .

Checking Status of Oracle Software Stack - Clusterware, ASM, RDBMS

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

-------------------------------------------------------------------------------------------------------

Oracle Stack Status

-------------------------------------------------------------------------------------------------------

Host Name CRS Installed RDBMS Installed CRS UP ASM UP RDBMS UP DB Instance Name

-------------------------------------------------------------------------------------------------------

d2lsenpsh160 Yes Yes Yes Yes Yes LABDB1

d2lsenpsh161 Yes Yes Yes Yes Yes LABDB2

-------------------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------------------------------------------

Installed components summary

---------------------------------------------------------------------------------------------------------------------------------

GI_HOME ORACLE_HOME Database Names

---------------------------------------------------------------------------------------------------------------------------------

/u01/app/11.2.0.3/grid - 11.2.0.3.0 /u01/app/oracle/product/11.2.0.3 - 11.2.0.3.0 LABDB

---------------------------------------------------------------------------------------------------------------------------------

…

Results:

WARNING => Shell limit soft nproc for DB is NOT configured according to recommendation

FAIL => Opatch version is lower than recommended in RDBMS_HOME for /u01/app/oracle/product/11.2.0.3

FAIL => Opatch version is lower than recommended in GRID_HOME

INFO => Information about ASM process parameter when its not set to default value

FAIL => ASM_DISKSTRING parameter is either null or set to /dev/*

WARNING => Berkeley Database location does not point to correct GI_HOME

Download and unpacked: p6880880_112000_LINUX.zip - OPatch 11.2.0.3.6

to $ORACLE_HOME and $GRID_HOME

Changed diskstring in ASM database:

Alter system set diskstring=’ORCL:*’;

Exeute orachk again:

./orachk -u -o pre

Data collections completed. Checking best practices on d2lsenpsh160.

--------------------------------------------------------------------------------------

WARNING => Shell limit soft nproc for DB is NOT configured according to recommendation

WARNING => TNS_ADMIN environment variable is set

WARNING => One or More Object Names in ALL_OBJECTS table are Reserved Words for LABDB

WARNING => One or More Column Names in ALL_TAB_COLUMNS table are Reserved Words for LABDB

WARNING => Review the PRE-UPGRADE details for the databases checked below for more information for LABDB

WARNING => OS parameter vm.swappiness is NOT set to the recommended value

WARNING => Berkeley Database location does not point to correct GI_HOME

WARNING => Some Users Needing Network ACLs for Oracle Utility Packages Found for LABDB

Data collections completed. Checking best practices on d2lsenpsh161.

--------------------------------------------------------------------------------------

WARNING => Shell limit soft nproc for DB is NOT configured according to recommendation

WARNING => TNS_ADMIN environment variable is set

INFO => Information about ASM process parameter when its not set to default value

WARNING => Berkeley Database location does not point to correct GI_HOME

B.6 Using CVU to Validate Readiness for Oracle Clusterware Upgrades

You can use Cluster Verification Utility (CVU) to assist you with system checks in preparation for starting an upgrade. CVU runs the appropriate system checks automatically, and either prompts you to fix problems, or provides a fixup script to be run on all nodes in the cluster before proceeding with the upgrade.

This section contains the following topics:

· About the CVU Grid Upgrade Validation Command Options

· Example of Verifying System Upgrade Readiness for Grid Infrastructure

B.6.1 About the CVU Grid Upgrade Validation Command Options

You can run upgrade validations in one of two ways:

· Run OUI, and allow the CVU validation built into OUI to perform system checks and generate fixup scripts

· Run the CVU manual script cluvfy.sh script to perform system checks and generate fixup scripts

To use OUI to perform pre-install checks and generate fixup scripts, run the installation as you normally would. OUI starts CVU, and performs system checks as part of the installation process. Selecting OUI to perform these checks is particularly appropriate if you think you have completed preinstallation checks, and you want to confirm that your system configuration meets minimum requirements for installation.

To use the cluvfy.sh command-line script for CVU, navigate to the staging area for the upgrade, where the runcluvfy.sh command is located, and run the command runcluvfy.sh stage -pre crsinst -upgrade to check the readiness of your Oracle Clusterware installation for upgrades. Running runcluvfy.sh with the -pre crsinst -upgrade options performs system checks to confirm if the cluster is in a correct state for upgrading from an existing clusterware installation.

The command uses the following syntax, where variable content is indicated by italics:

runcluvfy.sh stage -pre crsinst -upgrade [-rolling] -src_crshome src_Gridhome

-dest_crshome dest_Gridhome -dest_version dest_release

[-fixup][-method {sudo|root} [-location dir_path] [-user user_name]] [-verbose]

The options are:

· -n nodelist

The -n flag indicates cluster member nodes, and nodelist is the comma-delimited list of non-domain qualified node names on which you want to run a preupgrade verification. If you do not add the -n flag to the verification command, then all the nodes in the cluster are verified. You must add the -n flag if the clusterware is down on the node where runcluvfy.sh is run.

· -rolling

Use this flag to verify readiness for rolling upgrades.

· -src_crshome src_Gridhome

Use this flag to indicate the location of the source Oracle Clusterware or Grid home that you are upgrading, where src_Gridhome is the path to the home that you want to upgrade.

· -dest_crshome dest_Gridhome

Use this flag to indicate the location of the upgrade Grid home, where dest_ Gridhome is the path to the Grid home.

· -dest_version dest_release

Use the -dest_version flag to indicate the release number of the upgrade, including any patchset. The release number must include the five digits designating the release to the level of the platform-specific patch. For example: 12.1.0.1.0.

· -fixup [-method {sudo|root} [-location dir_path] [-user user_name]

Use the -fixup flag to indicate that you want to generate instructions for any required steps you need to complete to ensure that your cluster is ready for an upgrade. The default location is the CVU work directory.

The -fixup -method flag defines the method by which root scripts are run. The -method flag requires one of the following options:

· sudo: Run as a user on the sudoers list.

· root: Run as the root user.

If you select sudo, then enter the -location flag to provide the path to Sudo on the server, and enter the -user flag to provide the user account with Sudo privileges.

· -verbose

Use the -verbose flag to produce detailed output of individual checks.

B.6.2 Example of Verifying System Upgrade Readiness for Grid Infrastructure

You can verify that the permissions required for installing Oracle Clusterware have been configured by running a command similar to the following:

As root create the new GRID home and change ownership to installer on both nodes:

# mkdir -p /u01/app/12.1.0.1/grid

# chown oracle:oinstall /u01/app/12.1.0.1/grid

# chown oracle:oinstall /u01/app/12.1.0.1

As “oracle”

# cd /u01/app/oracle/media/12c/grid

unset ORACLE_BASE

unset ORACLE_HOME

unset ORACLE_SID

unset TNS_ADMIN

export PATH=/usr/sbin:/usr/proc/bin:/usr/local/bin:/usr/local/sbin:/usr/ccs/bin:/usr/local/bin:/bin:/us/bin

./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /u01/app/11.2.0.3/grid -dest_crshome /u01/app/12.1.0.1/grid -dest_version 12.1.0.1.0 -fixup –verbose

oracle@D2LSENPSH160[LABDB1]# ./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /u01/app/11.2.0.3/grid -dest_crshome /u01/app/12.1.0.1/grid -dest_version 12.1.0.1.0 -fixup -verbose

Performing pre-checks for cluster services setup

Checking node reachability...

Check: Node reachability from node "D2LSENPSH160"

Destination Node Reachable?

------------------------------------ ------------------------

d2lsenpsh160 yes

d2lsenpsh161 yes

Result: Node reachability check passed from node "D2LSENPSH160"

Checking user equivalence...

Check: User equivalence for user "oracle"

Node Name Status

------------------------------------ ------------------------

d2lsenpsh161 passed

d2lsenpsh160 passed

Result: User equivalence check passed for user "oracle"

Checking CRS user consistency

Result: CRS user consistency check successful

Checking ASM disk size consistency

ERROR:

PRCT-1207 : Failed to set the ORACLE_SID for running asmcmd from CRS home location /u01/app/11.2.0.3/grid

Checking node connectivity...

Checking hosts config file...

Node Name Status

------------------------------------ ------------------------

d2lsenpsh161 passed

d2lsenpsh160 passed

Verification of the hosts config file successful

Interface information for node "d2lsenpsh161"

Name IP Address Subnet Gateway Def. Gateway HW Address MTU

------ --------------- --------------- --------------- --------------- ----------------- ------

eth0 10.236.28.161 10.236.28.0 0.0.0.0 UNKNOWN 00:50:56:91:21:B4 1500

eth0 10.236.28.163 10.236.28.0 0.0.0.0 UNKNOWN 00:50:56:91:21:B4 1500

eth1 10.239.74.161 10.239.74.0 0.0.0.0 UNKNOWN 00:50:56:91:21:B5 1500

eth1 169.254.184.42 169.254.0.0 0.0.0.0 UNKNOWN 00:50:56:91:21:B5 1500

eth2 10.236.27.161 10.236.27.0 0.0.0.0 UNKNOWN 00:50:56:91:21:B6 1500

eth3 192.168.0.161 192.168.0.0 0.0.0.0 UNKNOWN 00:50:56:91:21:BE 1500

Interface information for node "d2lsenpsh160"

Name IP Address Subnet Gateway Def. Gateway HW Address MTU

------ --------------- --------------- --------------- --------------- ----------------- ------

eth0 10.236.28.160 10.236.28.0 0.0.0.0 10.236.28.1 00:50:56:91:21:B1 1500

eth0 10.236.28.162 10.236.28.0 0.0.0.0 10.236.28.1 00:50:56:91:21:B1 1500

eth0 10.236.28.176 10.236.28.0 0.0.0.0 10.236.28.1 00:50:56:91:21:B1 1500

eth1 10.239.74.160 10.239.74.0 0.0.0.0 10.236.28.1 00:50:56:91:21:B2 1500

eth1 169.254.136.37 169.254.0.0 0.0.0.0 10.236.28.1 00:50:56:91:21:B2 1500

eth2 10.236.27.160 10.236.27.0 0.0.0.0 10.236.28.1 00:50:56:91:21:B3 1500

eth3 192.168.0.160 192.168.0.0 0.0.0.0 10.236.28.1 00:50:56:91:21:BD 1500

Check: Node connectivity using interfaces on subnet "10.236.28.0"

Check: Node connectivity of subnet "10.236.28.0"

Source Destination Connected?

------------------------------ ------------------------------ ----------------

d2lsenpsh161[10.236.28.161] d2lsenpsh161[10.236.28.163] yes

d2lsenpsh161[10.236.28.161] d2lsenpsh160[10.236.28.176] yes

d2lsenpsh161[10.236.28.161] d2lsenpsh160[10.236.28.160] yes

d2lsenpsh161[10.236.28.161] d2lsenpsh160[10.236.28.162] yes

d2lsenpsh161[10.236.28.163] d2lsenpsh160[10.236.28.176] yes

d2lsenpsh161[10.236.28.163] d2lsenpsh160[10.236.28.160] yes

d2lsenpsh161[10.236.28.163] d2lsenpsh160[10.236.28.162] yes

d2lsenpsh160[10.236.28.176] d2lsenpsh160[10.236.28.160] yes

d2lsenpsh160[10.236.28.176] d2lsenpsh160[10.236.28.162] yes

d2lsenpsh160[10.236.28.160] d2lsenpsh160[10.236.28.162] yes

Result: Node connectivity passed for subnet "10.236.28.0" with node(s) d2lsenpsh161,d2lsenpsh160

Check: TCP connectivity of subnet "10.236.28.0"

Source Destination Connected?

------------------------------ ------------------------------ ----------------

d2lsenpsh161:10.236.28.161 d2lsenpsh161:10.236.28.163 passed

d2lsenpsh161:10.236.28.161 d2lsenpsh160:10.236.28.176 passed

d2lsenpsh161:10.236.28.161 d2lsenpsh160:10.236.28.160 passed

d2lsenpsh161:10.236.28.161 d2lsenpsh160:10.236.28.162 passed

Result: TCP connectivity check passed for subnet "10.236.28.0"

Check: Node connectivity using interfaces on subnet "10.239.74.0"

Check: Node connectivity of subnet "10.239.74.0"

Source Destination Connected?

------------------------------ ------------------------------ ----------------

d2lsenpsh160[10.239.74.160] d2lsenpsh161[10.239.74.161] yes

Result: Node connectivity passed for subnet "10.239.74.0" with node(s) d2lsenpsh160,d2lsenpsh161

Check: TCP connectivity of subnet "10.239.74.0"

Source Destination Connected?

------------------------------ ------------------------------ ----------------

d2lsenpsh160:10.239.74.160 d2lsenpsh161:10.239.74.161 passed

Result: TCP connectivity check passed for subnet "10.239.74.0"

Checking subnet mask consistency...

Subnet mask consistency check passed for subnet "10.236.28.0".

Subnet mask consistency check passed for subnet "10.239.74.0".

Subnet mask consistency check passed.

Result: Node connectivity check passed

Checking multicast communication...

Checking subnet "10.239.74.0" for multicast communication with multicast group "224.0.0.251"...

Check of subnet "10.239.74.0" for multicast communication with multicast group "224.0.0.251" passed.

Check of multicast communication passed.

Task ASM Integrity check started...

Starting check to see if ASM is running on all cluster nodes...

ASM Running check passed. ASM is running on all specified nodes

Starting Disk Groups check to see if at least one Disk Group configured...

Disk Group Check passed. At least one Disk Group configured

Task ASM Integrity check failed...

Checking OCR integrity...

OCR integrity check passed

Checking ASMLib configuration.

Node Name Status

------------------------------------ ------------------------

d2lsenpsh161 passed

d2lsenpsh160 passed

Result: Check for ASMLib configuration passed.

Check: Total memory

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 3.8565GB (4043840.0KB) 4GB (4194304.0KB) failed

d2lsenpsh160 3.8565GB (4043840.0KB) 4GB (4194304.0KB) failed

Result: Total memory check failed

Check: Available memory

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 2.3413GB (2454984.0KB) 50MB (51200.0KB) passed

d2lsenpsh160 1.975GB (2070932.0KB) 50MB (51200.0KB) passed

Result: Available memory check passed

Check: Swap space

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 6GB (6291448.0KB) 3.8565GB (4043840.0KB) passed

d2lsenpsh160 6GB (6291448.0KB) 3.8565GB (4043840.0KB) passed

Result: Swap space check passed

Check: Free disk space for "d2lsenpsh161:/usr,d2lsenpsh161:/etc,d2lsenpsh161:/u01/app/11.2.0.3/grid,d2lsenpsh161:/sbin"

Path Node Name Mount point Available Required Status

---------------- ------------ ------------ ------------ ------------ ------------

/usr d2lsenpsh161 / 21.5986GB 6.9586GB passed

/etc d2lsenpsh161 / 21.5986GB 6.9586GB passed

/u01/app/11.2.0.3/grid d2lsenpsh161 / 21.5986GB 6.9586GB passed

/sbin d2lsenpsh161 / 21.5986GB 6.9586GB passed

Result: Free disk space check passed for "d2lsenpsh161:/usr,d2lsenpsh161:/etc,d2lsenpsh161:/u01/app/11.2.0.3/grid,d2lsenpsh161:/sbin"

Check: Free disk space for "d2lsenpsh160:/usr,d2lsenpsh160:/etc,d2lsenpsh160:/u01/app/11.2.0.3/grid,d2lsenpsh160:/sbin"

Path Node Name Mount point Available Required Status

---------------- ------------ ------------ ------------ ------------ ------------

/usr d2lsenpsh160 / 12.582GB 6.9586GB passed

/etc d2lsenpsh160 / 12.582GB 6.9586GB passed

/u01/app/11.2.0.3/grid d2lsenpsh160 / 12.582GB 6.9586GB passed

/sbin d2lsenpsh160 / 12.582GB 6.9586GB passed

Result: Free disk space check passed for "d2lsenpsh160:/usr,d2lsenpsh160:/etc,d2lsenpsh160:/u01/app/11.2.0.3/grid,d2lsenpsh160:/sbin"

Check: Free disk space for "d2lsenpsh161:/var"

Path Node Name Mount point Available Required Status

---------------- ------------ ------------ ------------ ------------ ------------

/var d2lsenpsh161 /var 808MB 5MB passed

Result: Free disk space check passed for "d2lsenpsh161:/var"

Check: Free disk space for "d2lsenpsh160:/var"

Path Node Name Mount point Available Required Status

---------------- ------------ ------------ ------------ ------------ ------------

/var d2lsenpsh160 /var 749MB 5MB passed

Result: Free disk space check passed for "d2lsenpsh160:/var"

Check: Free disk space for "d2lsenpsh161:/tmp"

Path Node Name Mount point Available Required Status

---------------- ------------ ------------ ------------ ------------ ------------

/tmp d2lsenpsh161 /tmp 3.8213GB 1GB passed

Result: Free disk space check passed for "d2lsenpsh161:/tmp"

Check: Free disk space for "d2lsenpsh160:/tmp"

Path Node Name Mount point Available Required Status

---------------- ------------ ------------ ------------ ------------ ------------

/tmp d2lsenpsh160 /tmp 3.0622GB 1GB passed

Result: Free disk space check passed for "d2lsenpsh160:/tmp"

Check: User existence for "oracle"

Node Name Status Comment

------------ ------------------------ ------------------------

d2lsenpsh161 passed exists(1100)

d2lsenpsh160 passed exists(1100)

Checking for multiple users with UID value 1100

Result: Check for multiple users with UID value 1100 passed

Result: User existence check passed for "oracle"

Check: Group existence for "oinstall"

Node Name Status Comment

------------ ------------------------ ------------------------

d2lsenpsh161 passed exists

d2lsenpsh160 passed exists

Result: Group existence check passed for "oinstall"

Check: Group existence for "dba"

Node Name Status Comment

------------ ------------------------ ------------------------

d2lsenpsh161 passed exists

d2lsenpsh160 passed exists

Result: Group existence check passed for "dba"

Check: Membership of user "oracle" in group "oinstall" [as Primary]

Node Name User Exists Group Exists User in Group Primary Status

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 yes yes yes yes passed

d2lsenpsh160 yes yes yes yes passed

Result: Membership check for user "oracle" in group "oinstall" [as Primary] passed

Check: Membership of user "oracle" in group "dba"

Node Name User Exists Group Exists User in Group Status

---------------- ------------ ------------ ------------ ----------------

d2lsenpsh161 yes yes yes passed

d2lsenpsh160 yes yes yes passed

Result: Membership check for user "oracle" in group "dba" passed

Check: Run level

Node Name run level Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 3 3,5 passed

d2lsenpsh160 3 3,5 passed

Result: Run level check passed

Check: Hard limits for "maximum open file descriptors"

Node Name Type Available Required Status

---------------- ------------ ------------ ------------ ----------------

d2lsenpsh161 hard 65536 65536 passed

d2lsenpsh160 hard 65536 65536 passed

Result: Hard limits check passed for "maximum open file descriptors"

Check: Soft limits for "maximum open file descriptors"

Node Name Type Available Required Status

---------------- ------------ ------------ ------------ ----------------

d2lsenpsh161 soft 4096 1024 passed

d2lsenpsh160 soft 4096 1024 passed

Result: Soft limits check passed for "maximum open file descriptors"

Check: Hard limits for "maximum user processes"

Node Name Type Available Required Status

---------------- ------------ ------------ ------------ ----------------

d2lsenpsh161 hard 16384 16384 passed

d2lsenpsh160 hard 16384 16384 passed

Result: Hard limits check passed for "maximum user processes"

Check: Soft limits for "maximum user processes"

Node Name Type Available Required Status

---------------- ------------ ------------ ------------ ----------------

d2lsenpsh161 soft 2047 2047 passed

d2lsenpsh160 soft 2047 2047 passed

Result: Soft limits check passed for "maximum user processes"

There are no oracle patches required for home "/u01/app/11.2.0.3/grid".

Checking for suitability of source home "/u01/app/11.2.0.3/grid" for upgrading to version "12.1.0.1.0".

Result: Source home "/u01/app/11.2.0.3/grid" is suitable for upgrading to version "12.1.0.1.0".

Check: System architecture

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 x86_64 x86_64 passed

d2lsenpsh160 x86_64 x86_64 passed

Result: System architecture check passed

Check: Kernel version

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 2.6.18-274.el5 2.6.18 passed

d2lsenpsh160 2.6.18-274.el5 2.6.18 passed

Result: Kernel version check passed

Check: Kernel parameter for "semmsl"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 250 250 250 passed

d2lsenpsh160 250 250 250 passed

Result: Kernel parameter check passed for "semmsl"

Check: Kernel parameter for "semmns"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 32000 32000 32000 passed

d2lsenpsh160 32000 32000 32000 passed

Result: Kernel parameter check passed for "semmns"

Check: Kernel parameter for "semopm"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 100 100 100 passed

d2lsenpsh160 100 100 100 passed

Result: Kernel parameter check passed for "semopm"

Check: Kernel parameter for "semmni"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 128 128 128 passed

d2lsenpsh160 128 128 128 passed

Result: Kernel parameter check passed for "semmni"

Check: Kernel parameter for "shmmax"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 2070446080 2070446080 2070446080 passed

d2lsenpsh160 2070446080 2070446080 2070446080 passed

Result: Kernel parameter check passed for "shmmax"

Check: Kernel parameter for "shmmni"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 4096 4096 4096 passed

d2lsenpsh160 4096 4096 4096 passed

Result: Kernel parameter check passed for "shmmni"

Check: Kernel parameter for "shmall"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 2097152 2097152 404384 passed

d2lsenpsh160 2097152 2097152 404384 passed

Result: Kernel parameter check passed for "shmall"

Check: Kernel parameter for "file-max"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 6815744 6815744 6815744 passed

d2lsenpsh160 6815744 6815744 6815744 passed

Result: Kernel parameter check passed for "file-max"

Check: Kernel parameter for "ip_local_port_range"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 between 9000 & 65500 between 9000 & 65500 between 9000 & 65535 passed

d2lsenpsh160 between 9000 & 65500 between 9000 & 65500 between 9000 & 65535 passed

Result: Kernel parameter check passed for "ip_local_port_range"

Check: Kernel parameter for "rmem_default"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 4194304 4194304 262144 passed

d2lsenpsh160 4194304 4194304 262144 passed

Result: Kernel parameter check passed for "rmem_default"

Check: Kernel parameter for "rmem_max"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 4194304 4194304 4194304 passed

d2lsenpsh160 4194304 4194304 4194304 passed

Result: Kernel parameter check passed for "rmem_max"

Check: Kernel parameter for "wmem_default"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 262144 262144 262144 passed

d2lsenpsh160 262144 262144 262144 passed

Result: Kernel parameter check passed for "wmem_default"

Check: Kernel parameter for "wmem_max"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 1048586 1048586 1048576 passed

d2lsenpsh160 1048586 1048586 1048576 passed

Result: Kernel parameter check passed for "wmem_max"

Check: Kernel parameter for "aio-max-nr"

Node Name Current Configured Required Status Comment

---------------- ------------ ------------ ------------ ------------ ------------

d2lsenpsh161 1048576 1048576 1048576 passed

d2lsenpsh160 1048576 1048576 1048576 passed

Result: Kernel parameter check passed for "aio-max-nr"

Check: Package existence for "make"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 make-3.81-3.el5 make-3.81 passed

d2lsenpsh160 make-3.81-3.el5 make-3.81 passed

Result: Package existence check passed for "make"

Check: Package existence for "binutils"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 binutils-2.17.50.0.6-14.el5 binutils-2.17.50.0.6 passed

d2lsenpsh160 binutils-2.17.50.0.6-26.el5 binutils-2.17.50.0.6 passed

Result: Package existence check passed for "binutils"

Check: Package existence for "gcc(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 gcc(x86_64)-4.1.2-51.el5 gcc(x86_64)-4.1.2 passed

d2lsenpsh160 gcc(x86_64)-4.1.2-54.el5 gcc(x86_64)-4.1.2 passed

Result: Package existence check passed for "gcc(x86_64)"

Check: Package existence for "libaio(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 libaio(x86_64)-0.3.106-5 libaio(x86_64)-0.3.106 passed

d2lsenpsh160 libaio(x86_64)-0.3.106-5 libaio(x86_64)-0.3.106 passed

Result: Package existence check passed for "libaio(x86_64)"

Check: Package existence for "glibc(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 glibc(x86_64)-2.5-65 glibc(x86_64)-2.5-58 passed

d2lsenpsh160 glibc(x86_64)-2.5-118.el5_10.2 glibc(x86_64)-2.5-58 passed

Result: Package existence check passed for "glibc(x86_64)"

Check: Package existence for "compat-libstdc++-33(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 compat-libstdc++-33(x86_64)-3.2.3-61 compat-libstdc++-33(x86_64)-3.2.3 passed

d2lsenpsh160 compat-libstdc++-33(x86_64)-3.2.3-61 compat-libstdc++-33(x86_64)-3.2.3 passed

Result: Package existence check passed for "compat-libstdc++-33(x86_64)"

Check: Package existence for "glibc-devel(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 glibc-devel(x86_64)-2.5-65 glibc-devel(x86_64)-2.5 passed

d2lsenpsh160 glibc-devel(x86_64)-2.5-118.el5_10.2 glibc-devel(x86_64)-2.5 passed

Result: Package existence check passed for "glibc-devel(x86_64)"

Check: Package existence for "gcc-c++(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 gcc-c++(x86_64)-4.1.2-51.el5 gcc-c++(x86_64)-4.1.2 passed

d2lsenpsh160 gcc-c++(x86_64)-4.1.2-54.el5 gcc-c++(x86_64)-4.1.2 passed

Result: Package existence check passed for "gcc-c++(x86_64)"

Check: Package existence for "libaio-devel(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 libaio-devel(x86_64)-0.3.106-5 libaio-devel(x86_64)-0.3.106 passed

d2lsenpsh160 libaio-devel(x86_64)-0.3.106-5 libaio-devel(x86_64)-0.3.106 passed

Result: Package existence check passed for "libaio-devel(x86_64)"

Check: Package existence for "libgcc(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 libgcc(x86_64)-4.1.2-51.el5 libgcc(x86_64)-4.1.2 passed

d2lsenpsh160 libgcc(x86_64)-4.1.2-54.el5 libgcc(x86_64)-4.1.2 passed

Result: Package existence check passed for "libgcc(x86_64)"

Check: Package existence for "libstdc++(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 libstdc++(x86_64)-4.1.2-51.el5 libstdc++(x86_64)-4.1.2 passed

d2lsenpsh160 libstdc++(x86_64)-4.1.2-54.el5 libstdc++(x86_64)-4.1.2 passed

Result: Package existence check passed for "libstdc++(x86_64)"

Check: Package existence for "libstdc++-devel(x86_64)"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 libstdc++-devel(x86_64)-4.1.2-51.el5 libstdc++-devel(x86_64)-4.1.2 passed

d2lsenpsh160 libstdc++-devel(x86_64)-4.1.2-54.el5 libstdc++-devel(x86_64)-4.1.2 passed

Result: Package existence check passed for "libstdc++-devel(x86_64)"

Check: Package existence for "sysstat"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 sysstat-7.0.2-11.el5 sysstat-7.0.2 passed

d2lsenpsh160 sysstat-7.0.2-12.el5 sysstat-7.0.2 passed

Result: Package existence check passed for "sysstat"

Check: Package existence for "ksh"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 ksh-20100202-1.el5_6.6 ksh-... passed

d2lsenpsh160 ksh-20100621-18.el5_10.1 ksh-... passed

Result: Package existence check passed for "ksh"

Check: Package existence for "nfs-utils"

Node Name Available Required Status

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 nfs-utils-1.0.9-54.el5 nfs-utils-1.0.9-60 failed

d2lsenpsh160 nfs-utils-1.0.9-70.el5 nfs-utils-1.0.9-60 passed

Result: Package existence check failed for "nfs-utils"

Checking for multiple users with UID value 0

Result: Check for multiple users with UID value 0 passed

Check: Current group ID

Result: Current group ID check passed

Starting check for consistency of primary group of root user

Node Name Status

------------------------------------ ------------------------

d2lsenpsh161 passed

d2lsenpsh160 passed

Check for consistency of root user's primary group passed

Starting Clock synchronization checks using Network Time Protocol(NTP)...

NTP Configuration file check started...

The NTP configuration file "/etc/ntp.conf" is available on all nodes

NTP Configuration file check passed

Checking daemon liveness...

Check: Liveness for "ntpd"

Node Name Running?

------------------------------------ ------------------------

d2lsenpsh161 yes

d2lsenpsh160 yes

Result: Liveness check passed for "ntpd"

Check for NTP daemon or service alive passed on all nodes

Checking whether NTP daemon or service is using UDP port 123 on all nodes

Check for NTP daemon or service using UDP port 123

Node Name Port Open?

------------------------------------ ------------------------

d2lsenpsh161 yes

d2lsenpsh160 yes

NTP common Time Server Check started...

NTP Time Server ".INIT." is common to all nodes on which the NTP daemon is running

Check of common NTP Time Server passed

Clock time offset check from NTP Time Server started...

Checking on nodes "[d2lsenpsh161, d2lsenpsh160]"...

Check: Clock time offset from NTP Time Server

Time Server: .INIT.

Time Offset Limit: 1000.0 msecs

Node Name Time Offset Status

------------ ------------------------ ------------------------

d2lsenpsh161 0.0 passed

d2lsenpsh160 0.0 passed

Time Server ".INIT." has time offsets that are within permissible limits for nodes "[d2lsenpsh161, d2lsenpsh160]".

Clock time offset check passed

Result: Clock synchronization check using Network Time Protocol(NTP) passed

Checking Core file name pattern consistency...

Core file name pattern consistency check passed.

Checking to make sure user "oracle" is not in "root" group

Node Name Status Comment

------------ ------------------------ ------------------------

d2lsenpsh161 passed does not exist

d2lsenpsh160 passed does not exist

Result: User "oracle" is not part of "root" group. Check passed

Check default user file creation mask

Node Name Available Required Comment

------------ ------------------------ ------------------------ ----------

d2lsenpsh161 0022 0022 passed

d2lsenpsh160 0022 0022 passed

Result: Default user file creation mask check passed

Checking integrity of file "/etc/resolv.conf" across nodes

Checking the file "/etc/resolv.conf" to make sure only one of domain and search entries is defined

"domain" and "search" entries do not coexist in any "/etc/resolv.conf" file

Checking if domain entry in file "/etc/resolv.conf" is consistent across the nodes...

"domain" entry does not exist in any "/etc/resolv.conf" file

Checking if search entry in file "/etc/resolv.conf" is consistent across the nodes...

Checking file "/etc/resolv.conf" to make sure that only one search entry is defined

More than one "search" entry does not exist in any "/etc/resolv.conf" file

All nodes have same "search" order defined in file "/etc/resolv.conf"

Checking DNS response time for an unreachable node

Node Name Status

------------------------------------ ------------------------

d2lsenpsh161 passed

d2lsenpsh160 passed

The DNS response time for an unreachable node is within acceptable limit on all nodes

Check for integrity of file "/etc/resolv.conf" passed

UDev attributes check for OCR locations started...

Result: UDev attributes check passed for OCR locations

UDev attributes check for Voting Disk locations started...

Result: UDev attributes check passed for Voting Disk locations

Check: Time zone consistency

Result: Time zone consistency check passed

Checking VIP configuration.

Checking VIP Subnet configuration.

Check for VIP Subnet configuration passed.

Checking VIP reachability

Check for VIP reachability passed.

Checking Oracle Cluster Voting Disk configuration...

Oracle Cluster Voting Disk configuration check passed

Clusterware version consistency passed.

Checking integrity of name service switch configuration file "/etc/nsswitch.conf" ...

Checking if "hosts" entry in file "/etc/nsswitch.conf" is consistent across nodes...

Checking file "/etc/nsswitch.conf" to make sure that only one "hosts" entry is defined

More than one "hosts" entry does not exist in any "/etc/nsswitch.conf" file

All nodes have same "hosts" entry defined in file "/etc/nsswitch.conf"

Check for integrity of name service switch configuration file "/etc/nsswitch.conf" passed

Checking daemon "avahi-daemon" is not configured and running

Check: Daemon "avahi-daemon" not configured

Node Name Configured Status

------------ ------------------------ ------------------------

d2lsenpsh161 yes failed

d2lsenpsh160 yes failed

Daemon not configured check failed for process "avahi-daemon"

Check: Daemon "avahi-daemon" not running

Node Name Running? Status

------------ ------------------------ ------------------------

d2lsenpsh161 yes failed

d2lsenpsh160 yes failed

Daemon not running check failed for process "avahi-daemon"

Starting check for /dev/shm mounted as temporary file system ...

Check for /dev/shm mounted as temporary file system passed

Starting check for /boot mount ...

Check for /boot mount passed

Starting check for zeroconf check ...

Check for zeroconf check passed

******************************************************************************************

Following is the list of fixable prerequisites selected to fix in this session

******************************************************************************************

-------------- --------------- ----------------

Check failed. Failed on nodes Reboot required?

-------------- --------------- ----------------

Daemon "avahi-daemon" not d2lsenpsh161 no

configured and running ,d2lsenpsh160

Execute "/tmp/CVU_12.1.0.1.0_oracle/runfixup.sh" as root user on nodes "d2lsenpsh161,d2lsenpsh160" to perform the fix up operations manually

Press ENTER key to continue after execution of "/tmp/CVU_12.1.0.1.0_oracle/runfixup.sh" has completed on nodes "d2lsenpsh161,d2lsenpsh160"

Fix: Daemon "avahi-daemon" not configured and running

Node Name Status

------------------------------------ ------------------------

d2lsenpsh161 failed

d2lsenpsh160 failed

ERROR:

PRVG-9023 : Manual fix up command "/tmp/CVU_12.1.0.1.0_oracle/runfixup.sh" was not issued by root user on node "d2lsenpsh161"

PRVG-9023 : Manual fix up command "/tmp/CVU_12.1.0.1.0_oracle/runfixup.sh" was not issued by root user on node "d2lsenpsh160"

Result: "Daemon "avahi-daemon" not configured and running" could not be fixed on nodes "d2lsenpsh161,d2lsenpsh160"

Fix up operations for selected fixable prerequisites were unsuccessful on nodes "d2lsenpsh161,d2lsenpsh160"

Pre-check for cluster services setup was unsuccessful on all the nodes.

B.7 Understanding Rolling Upgrades Using Batches

Upgrades from earlier releases require that you upgrade the entire cluster. You cannot select or de-select individual nodes for upgrade. Oracle does not support attempting to add additional nodes to a cluster during a rolling upgrade.

Oracle recommends that you leave Oracle RAC instances running when upgrading Oracle Clusterware. When you start the root script on each node, the database instances on that node are shut down and then the rootupgrade.sh script starts the instances again. If you upgrade from Oracle Grid Infrastructure 11g Release 11.2.0.2 and later to any later release of Oracle Grid Infrastructure, then all nodes are selected for upgrade by default.

You can use root user automation to automate running the rootupgrade.sh script during the upgrade. When you use root automation, you can divide the nodes into groups, or batches, and start upgrades of these batches. Between batches, you can move services from nodes running the previous release to the upgraded nodes, so that services are not affected by the upgrade. Oracle recommends that you use rootautomation, and allow the rootupgrade.sh script to stop and start instances automatically. You can also continue to run root scripts manually.

B.8 Performing Rolling Upgrade of Oracle Grid Infrastructure

This section contains the following topics:

· Performing a Standard Upgrade from an Earlier Release

· Completing an Oracle Clusterware Upgrade when Nodes Become Unreachable

· Upgrading Inaccessible Nodes After Forcing an Upgrade

B.8.1 Performing a Standard Upgrade from an Earlier Release

Use the following procedure to upgrade the cluster from an earlier release:

1. Start the installer, and select the option to upgrade an existing Oracle Clusterware and Oracle ASM installation.

2. On the node selection page, select all nodes.

3. Select installation options as prompted. Oracle recommends that you configure root script automation, so that the rootupgrade.sh script can be run automatically during the upgrade.

4. Run root scripts, using either automatically or manually:

· Running root scripts automatically

If you have configured root script automation, then use the pause between batches to relocate services from the nodes running the previous release to the new release.

· Running root scripts manually

If you have not cohe script on the local node first. The script shuts down the earlier release installation, replaces it with the new Oracle Clusterware release, and starts the new Oracle Clusterware installation.

After the script completes successfully, you can run the script in parallel on all nodes except for one, which you select as the last node. When the script is run successfully on all the nodes except the last node, run the script on the last node.

When upgrading from 12.1.0.1 Oracle Flex Cluster, Oracle recommends that you run the rootupgrade.sh script on all Hub Nodes before running it on Leaf Nodes.

5. After running the rootupgrade.sh script on the last node in the cluster, if you are upgrading from a release earlier than Oracle Grid Infrastructure 11g Release 2 (11.2.0.2), and left the check box labeled ASMCA checked, as is the default, then Oracle Automatic Storage Management Configuration Assistant ASMCA runs automatically, and the Oracle Grid Infrastructure upgrade is complete. If you unchecked the box during the interview stage of the upgrade, then ASMCA is not run automatically.

If an earlier release of Oracle Automatic Storage Management (Oracle ASM) is installed, then the installer starts ASMCA to upgrade Oracle ASM to 12c Release 1 (12.1). You can choose to upgrade Oracle ASM at this time, or upgrade it later.

Oracle recommends that you upgrade Oracle ASM at the same time that you upgrade Oracle Clusterware. Until Oracle ASM is upgraded, Oracle Databases that use Oracle ASM cannot be created and the Oracle ASM management tools in the Oracle Grid Infrastructure 12cRelease 1 (12.1) home (for example, srvctl) do not work.

6. Because the Oracle Grid Infrastructure home is in a different location than the former Oracle Clusterware and Oracle ASM homes, update any scripts or applications that use utilities, libraries, or other files that reside in the Oracle Clusterware and Oracle ASM homes.

Note:

At the end of the upgrade, if you set the Oracle Cluster Registry (OCR) backup location manually to the earlier release Oracle Clusterware home (CRS home), then you must change the OCR backup location to the new Oracle Grid Infrastructure home (Grid home). If you did not set the OCR backup location manually, then the backup location is changed for you during the upgrade.

Because upgrades of Oracle Clusterware are out-of-place upgrades, the previous release Oracle Clusterware home cannot be the location of the current release OCR backups. Backups in the old Oracle Clusterware home can be deleted.

See Also:

Section A.12, "Failed or Incomplete Installations and Upgrades" for information about completing failed or incomplete upgrades

ASMLib installation and configuration verification. - This task checks the ASMLib installation and configuration across the systems.

Check Failed on Nodes: [D2LSENPSH161, D2LSENPSH160]

Verification result of failed node: D2LSENPSH161 Details:

PRVG-10122 : ASMLib configuration value set to configuration parameter "ORACLEASM_UID" on the node "D2LSENPSH161" does not match with cluster nodes - Cause: The ASMLib configuration check found inconsistent settings across cluster nodes. - Action: Ensure that the ASMLib is correctly installed and configured on all the nodes with same configuration settings and that the user has the necessary access privileges for the configuration file.

PRVG-10122 : ASMLib configuration value set to configuration parameter "ORACLEASM_GID" on the node "D2LSENPSH161" does not match with cluster nodes - Cause: The ASMLib configuration check found inconsistent settings across cluster nodes. - Action: Ensure that the ASMLib is correctly installed and configured on all the nodes with same configuration settings and that the user has the necessary access privileges for the configuration file.

PRVG-10122 : ASMLib configuration value set to configuration parameter "ORACLEASM_ENABLED" on the node "D2LSENPSH161" does not match with cluster nodes - Cause: The ASMLib configuration check found inconsistent settings across cluster nodes. - Action: Ensure that the ASMLib is correctly installed and configured on all the nodes with same configuration settings and that the user has the necessary access privileges for the configuration file.

Verification result of failed node: D2LSENPSH160 Details:

PRVG-10122 : ASMLib configuration value set to configuration parameter "ORACLEASM_UID" on the node "D2LSENPSH160" does not match with cluster nodes - Cause: The ASMLib configuration check found inconsistent settings across cluster nodes. - Action: Ensure that the ASMLib is correctly installed and configured on all the nodes with same configuration settings and that the user has the necessary access privileges for the configuration file.

PRVG-10122 : ASMLib configuration value set to configuration parameter "ORACLEASM_GID" on the node "D2LSENPSH160" does not match with cluster nodes - Cause: The ASMLib configuration check found inconsistent settings across cluster nodes. - Action: Ensure that the ASMLib is correctly installed and configured on all the nodes with same configuration settings and that the user has the necessary access privileges for the configuration file.

PRVG-10122 : ASMLib configuration value set to configuration parameter "ORACLEASM_ENABLED" on the node "D2LSENPSH160" does not match with cluster nodes - Cause: The ASMLib configuration check found inconsistent settings across cluster nodes. - Action: Ensure that the ASMLib is correctly installed and configured on all the nodes with same configuration settings and that the user has the necessary access privileges for the configuration file.

-bash-3.2# uname -a

Linux D2LSENPSH160 2.6.18-400.1.1.el5 #1 SMP Sun Dec 14 06:01:17 EST 2014 x86_64 x86_64 x86_64 GNU/Linux

-bash-3.2#

-bash-3.2# /u01/app/12.1.0.1/grid/rootupgrade.sh

Performing root user operation for Oracle 12c

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /u01/app/12.1.0.1/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]:

The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying dbhome to /usr/local/bin ...

The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying oraenv to /usr/local/bin ...

The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying coraenv to /usr/local/bin ...

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root script.

Now product-specific root actions will be performed.

Using configuration parameter file: /u01/app/12.1.0.1/grid/crs/install/crsconfig_params

2015/01/13 17:15:06 CLSRSC-363: User ignored prerequisites during installation

ASM upgrade has started on first node.

OLR initialization - successful

2015/01/13 17:17:58 CLSRSC-329: Replacing Clusterware entries in file '/etc/inittab'

CRS-4133: Oracle High Availability Services has been stopped.

CRS-4123: Oracle High Availability Services has been started.

2015/01/13 17:21:38 CLSRSC-343: Successfully started Oracle clusterware stack

clscfg: EXISTING configuration version 5 detected.

clscfg: version 5 is 11g Release 2.

Successfully accumulated necessary OCR keys.

Creating OCR keys for user 'root', privgrp 'root'..

Operation successful.

2015/01/13 17:22:43 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded

-bash-3.2#

-bash-3.2# uname -a

Linux D2LSENPSH161 2.6.18-400.1.1.el5 #1 SMP Sun Dec 14 06:01:17 EST 2014 x86_64 x86_64 x86_64 GNU/Linux

-bash-3.2# /u01/app/12.1.0.1/grid/rootupgrade.sh

Performing root user operation for Oracle 12c

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /u01/app/12.1.0.1/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]:

The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying dbhome to /usr/local/bin ...

The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying oraenv to /usr/local/bin ...

The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying coraenv to /usr/local/bin ...

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root script.

Now product-specific root actions will be performed.

Using configuration parameter file: /u01/app/12.1.0.1/grid/crs/install/crsconfig_params

2015/01/13 17:24:21 CLSRSC-363: User ignored prerequisites during installation

OLR initialization - successful

2015/01/13 17:26:56 CLSRSC-329: Replacing Clusterware entries in file '/etc/inittab'

CRS-4133: Oracle High Availability Services has been stopped.

CRS-4123: Oracle High Availability Services has been started.

2015/01/13 17:30:47 CLSRSC-343: Successfully started Oracle clusterware stack

clscfg: EXISTING configuration version 5 detected.

clscfg: version 5 is 12c Release 1.

Successfully accumulated necessary OCR keys.

Creating OCR keys for user 'root', privgrp 'root'..

Operation successful.

Start upgrade invoked..

Started to upgrade the Oracle Clusterware. This operation may take a few minutes.

Started to upgrade the OCR.

Started to upgrade the CSS.

The CSS was successfully upgraded.

Started to upgrade Oracle ASM.

Started to upgrade the CRS.

The CRS was successfully upgraded.

Oracle Clusterware operating version was successfully set to 12.1.0.1.0

2015/01/13 17:33:36 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded

-bash-3.2#

Cause - The plug-in failed in its perform method Action - Refer to the logs or contact Oracle Support Services. Log File Location

/u01/app/oraInventory/logs/installActions2015-01-13_04-47-36PM.log

>>> Ignoring required pre-requisite failures. Continuing...

Preparing to launch Oracle Universal Installer from /tmp/OraInstall2015-01-13_04-47-36PM. Please wait ...oracle@D2LSENPSH160[LABDB1]# You can find the log of this install session at:

/u01/app/oraInventory/logs/installActions2015-01-13_04-47-36PM.log

B.8.2 Completing an Oracle Clusterware Upgrade when Nodes Become Unreachable

If some nodes become unreachable in the middle of an upgrade, then you cannot complete the upgrade, because the upgrade script (rootupgrade.sh) did not run on the unreachable nodes. Because the upgrade is incomplete, Oracle Clusterware remains in the previous release. You can confirm that the upgrade is incomplete by entering the command crsctl query crs activeversion.

To resolve this problem, run the rootupgrade command with the -force flag on any of the nodes where the rootupgrade.sh script has already completed as follows:

Grid_home/rootupgrade.sh -force

For example:

# /u01/app/12.1.0/grid/rootupgrade.sh-force

This command forces the upgrade to complete. Verify that the upgrade has completed by using the commandcrsctl query crs activeversion. The active release should be the upgrade release.

The force cluster upgrade has the following limitations:

· All active nodes must be upgraded to the newer release.

· All inactive nodes (accessible or inaccessible) may be either upgraded or not upgraded.

· For inaccessible nodes, after patch set upgrades, you can delete the node from the cluster. If the node becomes accessible later, and the patch version upgrade path is supported, then you can upgrade it to the new patch version.

· If the cluster was previously forcibly upgraded, then ensure that all inaccessible nodes have been deleted from the cluster or joined to the cluster before starting the upgrade.

B.8.3 Upgrading Inaccessible Nodes After Forcing an Upgrade

Starting with Oracle Grid Infrastructure 12c, after you complete a force cluster upgrade, you can join inaccessible nodes to the cluster as an alternative to deleting the nodes, which was required in earlier releases. To use this option, Oracle Grid Infrastructure 12c Release 1 (12.1) software must already be installed on the nodes.

To complete the upgrade of nodes that were inaccessible or unreachable:

1. Log in as the Grid user on the node that is to be joined to the cluster.

2. Change directory to the /crs/install directory in the Oracle Grid Infrastructure 12c Release 1 (12.1) Grid home. For example:

3. $ cd /u01/12.1.0/grid/crs/install

4. Run the following PERL command, where existingnode is the name of the option and upgraded_node is any node that was successfully upgraded and is currently part of the cluster:

5. $ rootupgrade.sh -join -existingnode upgraded_node

Note:

The -join operation is not supported for Oracle Clusterware releases earlier than 11.2.0.1.0. In such cases, delete the node and add it to the clusterware using the addNode command.

B.8.4 Changing the First Node for Install and Upgrade

If the first node becomes inaccessible, you can force another node to be the first node for installation or upgrade. During installation, ifroot.sh fails to complete on the first node, run the following command on another node using the -force option:

root.sh -force -first

For upgrade, run the following command:

rootupgrade.sh -force -first

B.9 Performing Rolling Upgrade of Oracle ASM

After you have completed the Oracle Clusterware portion of Oracle Grid Infrastructure 12c Release 1 (12.1) upgrade, you may need to upgrade Oracle ASM separately under the following conditions:

· If you are upgrading from a release in which Oracle ASM was in a separate Oracle home, such as Oracle ASM 10g Release 2 (10.2) or Oracle ASM 11g Release 1 (11.1)

· If the Oracle ASM portion of the Oracle Grid Infrastructure upgrade failed, or for some other reason Automatic Storage Management Configuration assistant (asmca) did not run.

You can use asmca to complete the upgrade separately, but you should do it soon after you upgrade Oracle Clusterware, as Oracle ASM management tools such as srvctl do not work until Oracle ASM is upgraded.

Note:

ASMCA performs a rolling upgrade only if the earlier release of Oracle ASM is either 11.1.0.6 or 11.1.0.7. Otherwise, ASMCA performs a non-rolling upgrade, in which ASMCA shuts down all Oracle ASM instances on all nodes of the cluster, and then starts an Oracle ASM instance on each node from the new Oracle Grid Infrastructure home.

After you have upgraded Oracle ASM with Oracle Grid Infrastructure 12c Release 1, you can install individual patches for Oracle ASM by downloading them from the Oracle Automated Release Update site. See Section B.9.1, "About Upgrading Oracle ASM Separately" for more information about upgrading Oracle ASM separately using ASMCA.

B.9.1 About Upgrading Oracle ASM Separately

Note the following if you intend to perform either full release or software patch level rolling upgrades of Oracle ASM:

· The active release of Oracle Clusterware must be 12c Release 1 (12.1). To determine the active release, enter the following command:

· $ crsctl query crs activeversion

· You can upgrade a single instance Oracle ASM installation to a clustered Oracle ASM installation. However, you can only upgrade an existing single instance Oracle ASM installation if you run the installation from the node on which the Oracle ASM installation is installed. You cannot upgrade a single instance Oracle ASM installation on a remote node.

· You must ensure that any rebalance operations on your existing Oracle ASM installation are completed before starting the upgrade process.

· During the upgrade process, you alter the Oracle ASM instances to an upgrade state. You do not need to shut down database clients unless they are on Oracle ACFS. However, because this upgrade state limits Oracle ASM operations, you should complete the upgrade process soon after you begin. The following are the operations allowed when an Oracle ASM instance is in the upgrade state:

· Diskgroup mounts and dismounts

· Opening, closing, resizing, or deleting database files

· Recovering instances

· Queries of fixed views and packages: Users are allowed to query fixed views and run anonymous PL/SQL blocks using fixed packages, such as dbms_diskgroup)

· You do not need to shut down database clients unless they are on Oracle ACFS.

See Also:

See Section B.9.2, "Upgrading Oracle ASM Using ASMCA" for steps to upgrade Oracle ASM separately using ASMCA

B.9.2 Upgrading Oracle ASM Using ASMCA

Complete the following tasks if you must upgrade from an Oracle ASM release where Oracle ASM was installed in a separate Oracle home, or if the Oracle ASM portion of Oracle Grid Infrastructure upgrade failed to complete:

1. On the node you plan to start the upgrade, set the environment variable ASMCA_ROLLING_UPGRADE as true. For example:

2. $ export ASMCA_ROLLING_UPGRADE=true

3. From the Oracle Grid Infrastructure 12c Release 1 (12.1) home, start ASMCA. For example:

4. $ cd /u01/12.1/grid/bin

5. $ ./asmca

6. Select Upgrade.

ASM Configuration Assistant upgrades Oracle ASM in succession for all nodes in the cluster.

7. After you complete the upgrade, run the command to unset the ASMCA_ROLLING_UPGRADE environment variable.

See Also:

Oracle Database Upgrade Guide and Oracle Automatic Storage Management Administrator's Guide for additional information about preparing an upgrade plan for Oracle ASM, and for starting, completing, and stopping Oracle ASM upgrades

B.10 Applying Patches to Oracle ASM

After you have upgraded Oracle ASM with Oracle Grid Infrastructure 12c Release 1, you can install individual patches for Oracle ASM by downloading them from My Oracle Support.

This section explains about Oracle ASM patches as follows:

· About Individual (One-Off) Oracle ASM Patches

· About Oracle ASM Software Patch Levels

· Patching Oracle ASM to a Software Patch Level

B.10.1 About Individual (One-Off) Oracle ASM Patches

Individual patches are called one-off patches. An Oracle ASM one-off patch is available for a specific released release of Oracle ASM. If a patch you want is available, then you can download the patch and apply it to Oracle ASM using the OPatch Utility. The OPatch inventory keeps track of the patches you have installed for your release of Oracle ASM. If there is a conflict between the patches you have installed and patches you want to apply, then the OPatch Utility advises you of these conflicts. See Section B.10.3, "Patching Oracle ASM to a Software Patch Level"for information about applying patches to Oracle ASM using the OPatch Utility.

B.10.2 About Oracle ASM Software Patch Levels

The software patch level for Oracle Grid Infrastructure represents the set of all one-off patches applied to the Oracle Grid Infrastructure software release, including Oracle ASM. The release is the release number, in the format of major, minor, and patch set release number. For example, with the release number 12.1.0.1, the major release is 12, the minor release is 1, and 0.0 is the patch set number. With one-off patches, the major and minor release remains the same, though the patch levels change each time you apply or roll back an interim patch.

As with standard upgrades to Oracle Grid Infrastructure, at any given point in time for normal operation of the cluster, all the nodes in the cluster must have the same software release and patch level. Because one-off patches can be applied as rolling upgrades, all possible patch levels on a particular software release are compatible with each other.

See Also:

· Section B.8.1, "Performing a Standard Upgrade from an Earlier Release" for information about upgrading Oracle Grid Infrastructure

· Section B.10.3, "Patching Oracle ASM to a Software Patch Level" for information about applying patches to Oracle ASM using the OPatch Utility

B.10.3 Patching Oracle ASM to a Software Patch Level

Starting with Oracle Grid Infrastructure 12c Release 1 (12.1), a new cluster state called "Rolling Patch" is available. This mode is similar to the existing "Rolling Upgrade" mode in terms of the Oracle ASM operations allowed in this quiesce state.

1. Download patches you want to apply from My Oracle Support:

https://support.oracle.com

Select the Patches and Updates tab to locate the patch.

Oracle recommends that you select Recommended Patch Advisor, and enter the product group, release, and platform for your software. My Oracle Support provides you with a list of the most recent patch set updates (PSUs) and critical patch updates (CPUs).

Place the patches in an accessible directory, such as /tmp.

2. Change directory to the /opatch directory in the Grid home. For example:

3. $ cd /u01/app/12.1.0/grid/opatch

4. Review the patch documentation for the patch you want to apply, and complete all required steps before starting the patch upgrade.

5. Follow the instructions in the patch documentation to apply the patch.

B.11 Updating Oracle Enterprise Manager Cloud Control Target Parameters

Because Oracle Grid Infrastructure 12c Release 1 (12.1) is an out-of-place upgrade of the Oracle Clusterware home in a new location (the Oracle Grid Infrastructure for a cluster home, or Grid home), the path for the CRS_HOME parameter in some parameter files must be changed. If you do not change the parameter, then you encounter errors such as "cluster target broken" on Oracle Enterprise Manager Cloud Control.

To resolve the issue, upgrade the Enterprise Manager Cloud Control target, and then update the Enterprise Manager Agent Base Directory on each cluster member node running an agent, as described in the following sections:

· Updating the Enterprise Manager Cloud Control Target After Upgrades

· Updating the Enterprise Manager Agent Base Directory After Upgrades

B.11.1 Updating the Enterprise Manager Cloud Control Target After Upgrades

1. Log in to Enterprise Manager Cloud Control.

2. Navigate to the Targets menu, and then to the Cluster page.

3. Click a cluster target that was upgraded.

4. Click Cluster, then Target Setup, and then Monitoring Configuration from the menu.

5. Update the value for Oracle Home with the new Grid home path.

6. Save the updates.

B.11.2 Updating the Enterprise Manager Agent Base Directory After Upgrades

1. Navigate to the bin directory in the Management Agent home.

The Agent Base directory is a directory where the Management Agent home is created. The Management Agent home is in the pathAgent_Base_Directory/core/EMAgent_Version. For example, if the Agent Base directory is /u01/app/emagent, then the Management Agent home is created as /u01/app/emagent/core/12.1.0.1.0.

2. In the /u01/app/emagent/core/12.1.0.1.0/bin directory, open the file emctl with a text editor.

3. Locate the parameter CRS_HOME, and update the parameter to the new Grid home path.

4. Repeat steps 1-3 on each node of the cluster with an Enterprise Manager agent.

B.12 Unlocking the Existing Oracle Clusterware Installation

After upgrade from previous releases, if you want to deinstall the previous release Oracle Grid Infrastructure Grid home, then you must first change the permission and ownership of the previous release Grid home. Complete this task using the following procedure:

Log in as root, and change the permission and ownership of the previous release Grid home using the following command syntax, whereoldGH is the previous release Grid home, swowner is the Oracle Grid Infrastructure installation owner, and oldGHParent is the parent directory of the previous release Grid home:

#chmod -R 755 oldGH

#chown -R swowner oldGH

#chown swowner oldGHParent

For example:

#chmod -R 755 /u01/app/11.2.0.3/grid

#chown -R oracle /u01/app/11.2.0.3/grid

#chown oracle /u01/app/11.2.0.3

After you change the permissions and ownership of the previous release Grid home, log in as the Oracle Grid Infrastructure Installation owner (grid, in the preceding example), and use the Oracle Grid Infrastructure 12c deinstallation tool to remove the previous release Grid home (oldGH).

B.13 Checking Cluster Health Monitor Repository Size After Upgrading

If you are upgrading from a prior release using IPD/OS to Oracle Grid Infrastructure then review the Cluster Health Monitor repository size (the CHM repository). Oracle recommends that you review your CHM repository needs, and enlarge the repository size if you want to maintain a larger CHM repository.

Note:

Your previous IPD/OS repository is deleted when you install Oracle Grid Infrastructure, and you run the root.sh script on each node.

Cluster Health Monitor is not available with IBM: Linux on System z configurations.

By default, the CHM repository size is a minimum of either 1GB or 3600 seconds (1 hour). The CHM repository is one gigabyte (1 GB), regardless of the size of the cluster.

To enlarge the CHM repository, use the following command syntax, where retention_time is the size of CHM repository in number of seconds:

oclumon manage -repos changeretentiontime retention_time

The value for retention_time must be more than 3600 (one hour) and less than 259200 (three days). If you enlarge the CHM repository size, then you must ensure that there is local space available for the repository size you select on each node of the cluster. If there is not sufficient space available, then you can move the repository to shared storage.

For example, to set the repository size to four hours:

$ oclumon manage -repos changeretentiontime 14400

B.14 Downgrading Oracle Clusterware After an Upgrade

After a successful or a failed upgrade to Oracle Clusterware 12c Release 1 (12.1), you can restore Oracle Clusterware to the previous release. This section contains the following topics:

· About Downgrading Oracle Clusterware After an Upgrade

· Downgrading to Releases Before 11g Release 2 (11.2.0.2)

· Downgrading to 11g Release 1 (11.2.0.2) or Later Release

B.14.1 About Downgrading Oracle Clusterware After an Upgrade

Downgrading Oracle Clusterware restores the Oracle Clusterware configuration to the state it was in before the Oracle Clusterware 12cRelease 1 (12.1) upgrade. Any configuration changes you performed during or after the Oracle Grid Infrastructure 12c Release 1 (12.1) upgrade are removed and cannot be recovered.

In the downgrade procedures, the following variables are used:

· first node is the first node on which the rootupgrade script completed successfully.

· non-first nodes are all other nodes where the rootupgrade script completed successfully.

To restore Oracle Clusterware to the previous release, use the downgrade procedure for the release to which you want to downgrade.

Note:

When downgrading after a failed upgrade, if rootcrs.sh does not exist on a node, then use perl rootcrs.pl instead ofrootcrs.sh.

B.14.2 Downgrading to Releases Before 11g Release 2 (11.2.0.2)

To downgrade Oracle Clusterware:

1. If the rootupgrade script failed on a node, then downgrade the node where the upgrade failed:

2. rootcrs.sh -downgrade

3. On all other nodes where the rootupgrade script ran successfully, use the command syntaxGrid_home/crs/install/rootcrs.sh -downgrade [-force] to stop the 12c Release 1 (12.1) resources, and shut down the Oracle Grid Infrastructure 12c Release 1 (12.1) stack.

4. rootcrs.sh -downgrade

5. After the rootcrs.sh -downgrade script has completed on all non-first nodes, on the first node use the command syntaxGrid_home/crs/install/rootcrs.sh -downgrade [-force] -lastnode.

For example:

# /u01/app/12.1.0/grid/crs/install/rootcrs.sh -downgrade -lastnode

Note:

With Oracle Grid Infrastructure 12c, you no longer need to provide the location of the previous release Grid home or release number.

This script downgrades the OCR. If you want to stop a partial or failed Oracle Grid Infrastructure 12c Release 1 (12.1) installation and restore the previous release Oracle Clusterware, then use the -force flag with this command. Run this command from a directory that has write permissions for the Oracle Grid Infrastructure installation user.

6. On any of the cluster member nodes where the rootcrs script has run successfully:

a. Log in as the Oracle Grid Infrastructure installation owner.

b. Use the following command to start the installer, where /u01/app/12.1.0/grid is the location of the new (upgraded) Grid home:

7. ./runInstaller -nowait -waitforcompletion -ignoreSysPrereqs -updateNodeList -silent

8. CRS=false ORACLE_HOME=/u01/app/12.1.0/grid

Add the flag -cfs if the Grid home is a shared home.

9. On any of the cluster member nodes where the rootupgrade.sh script has run successfully:

a. Log in as the Oracle Grid Infrastructure installation owner (grid).

b. Use the following command to start the installer, where the path you provide for the flag ORACLE_HOME is the location of the home directory from the earlier Oracle Clusterware installation

For example:

$ cd /u01/app/12.1.0/grid/oui/bin

$ ./runInstaller -nowait -waitforcompletion -ignoreSysPrereqs -updateNodeList -silent

CRS=true ORACLE_HOME=/u01/app/crs

c. For downgrades to 11.1 and earlier releases

If you are downgrading to Oracle Clusterware 11g Release 1 (11.1) or an earlier release, then you must run root.sh manually from the earlier release Oracle Clusterware home to complete the downgrade after you complete step b.

OUI prompts you to run root.sh manually from the earlier release Oracle Clusterware installation home in sequence on each member node of the cluster to complete the downgrade. After you complete this task, downgrade is completed.

Running root.sh from the earlier release Oracle Clusterware installation home restarts the Oracle Clusterware stack, starts up all the resources previously registered with Oracle Clusterware in the earlier release, and configures the old initialization scripts to run the earlier release Oracle Clusterware stack.

After completing the downgrade, update the entry for Oracle ASM instance in the oratab file (/etc/oratab or/var/opt/oracle/oratab) on every node in the cluster as follows:

+ASM<instance#>:<RAC-ASM home>:N

B.14.3 Downgrading to 11g Release 1 (11.2.0.2) or Later Release

Follow these steps to downgrade Oracle Grid Infrastructure:

1. On all remote nodes, use the command syntax Grid_home/crs/install/rootcrs.sh -downgrade [-force] to stop the 12c Release 1 (12.1) resources, and shut down the Oracle Grid Infrastructure 12c Release 1 (12.1) stack.

2. # /u01/app/12.1.0/grid/crs/install/rootcrs.sh -downgrade

If you want to stop a partial or failed Oracle Grid Infrastructure 12c Release 1 (12.1) installation and restore the previous release Oracle Clusterware, then use the -force flag with this command.

3. After the rootcrs.sh -downgrade script has completed on all remote nodes, on the local node use the command syntaxGrid_home/crs/install/rootcrs.sh -downgrade [-force] -lastnode

For example:

# /u01/app/12.1.0/grid/crs/install/rootcrs.sh -downgrade -lastnode

Note:

Starting with Oracle Grid Infrastructure 12c Release 1 (12.1), you no longer need to provide the location of the earlier release Grid home or earlier release number.

4. On any of the cluster member nodes where the rootupgrade.sh script has run successfully:

a. Log in as the Oracle Grid Infrastructure installation owner.

b. Use the following command to start the installer, where /u01/app/12.1.0/grid is the location of the new (upgraded) Grid home:

5. $ cd /u01/app/12.1.0/grid/oui/bin

6. ./runInstaller -nowait -waitforcompletion -ignoreSysPrereqs -updateNodeList

7. -silent CRS=false ORACLE_HOME=/u01/app/12.1.0/grid

Add the flag -cfs if the Grid home is a shared home.

8. On any of the cluster member nodes where the rootupgrade script has run successfully:

a. Log in as the Oracle Grid Infrastructure installation owner.

b. Use the following command to start the installer, where the path you provide for the flag ORACLE_HOME is the location of the home directory from the earlier Oracle Clusterware installation

For example:

$ cd /u01/app/12.1.0/grid/oui/bin

$ ./runInstaller -nowait -waitforcompletion -ignoreSysPrereqs -updateNodeList -silent CRS=true ORACLE_HOME=/u01/app/crs

c. For downgrades to 11.2.0.2

If you are downgrading to Oracle Clusterware 11g Release 1 (11.2.0.2), then you must start the Oracle Clusterware stack manually after you complete step b.

On each node, start Oracle Clusterware from the earlier release Oracle Clusterware home using the command crsctl start crs. For example, where the earlier release home is /u01/app/11.2.0/grid, use the following command on each node:

/u01/app/11.2.0/grid/bin/crsctl start crs

9. For downgrades to 12.1.0.1

If you are downgrading to Oracle Grid Infrastructure 12c Release 1 (12.1.0.1), then run the following commands to configure the Grid Management Database:

a. Start the 12.1.0.1 Oracle Clusterware stack on all nodes.

b. On any node, remove the MGMTDB resource as follows:

c. 12101_Grid_home/bin/srvctl remove mgmtdb

d. Run DBCA in the silent mode from the 12.1.0.1 Oracle home and create the Management Database as follows:

e.12101_Grid_home/bin/dbca -silent -createDatabase -templateName

f. MGMTSeed_Database.dbc -sid -MGMTDB -gdbName _mgmtdb -storageType ASM

g. -diskGroupName ASM_DG_NAME

h.-datafileJarLocation 12101_grid_home/assistants/dbca/templates -characterset AL32UTF8 -autoGeneratePasswords

i. Configure the Management Database by running the Configuration Assistant from the location 12101_Grid_home/bin/mgmtca.

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

Hi Ken

The referenced document is a good starting point, however please notice the following:

1. We cannot clone the ORACLE_HOME mainly because we will be replacing the host operation system (Solaris) with a different operating system (RHEL 6). Therefore the RDBMS Home as well as the OMS binaries will all be installed and not cloned.

2. Even the database cannot be cloned for the same reason because the platforms we are cloning from and two are different thus the database will need to be converted first and then imported.

As for your questions:

Questions I do have is:

1. Do we currently use Load Balancer in this environment? No

2. Any BI Publisher? No

3. Do we have a multi-OMS setup in the current environment? Currently No but the new system will be multi-OMS. Please review the DPS.

Thanks,

Omer

From: Chando, Kenneth
Sent: Thursday, October 22, 2015 10:16 AM
To: Abdalla, Omer
Subject: RE: Enterprise Manager 1-System Upgrade (different host) from 10.2.0.5 or from 11.1.0.1 to 12c (Doc ID 329.1)

Hi Omer,

I found the above piece of guidelines interesting. I believe it may be a good pointer towards attaining our goal of the cross-platform migration of OEM 12c.

As of now, Oracle doesn’t seem to have put a comprehensive guide on this. However, I have included at the bottom of the page(see attached) some Oracle Helpful link, should we want to upgrade our current OEM 12c after we successfully migrate it over from Solaris server to our new RHEL server.

**NOTE:

Moving OEM 12c from Solaris to RHEL, we might have to clone the current Existing $ORACLE_HOME (in old platform: Solaris) and then move it to the new RHEL server so as to save time on patching. We might have to include just recent patches that’s not been applied to the $ORACLE_HOME that was existing in Old Solaris Server.

In a high-level, we would have to:

1. Backup & Recover Enterprise Manager,

2. Install New OS platform (In this case RHEL)

3. Create accounts

4. Assign Storage volume

5. Relocate the Management Repository to the new host (RHEL)

**NOTE:

Questions I do have is:

1. Do we currently use Load Balancer in this environment?

2. Any BI Publisher?

3. Do we have a multi-OMS setup in the current environment?

Let me know your thoughts.

Thank you!

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

http://docs.oracle.com/cd/E24628_01/upgrade.121/e22625/toc.htm

Thank you for your feedback |Recognition@hp

From: Abdalla, Omer
Sent: Monday, October 19, 2015 1:55 PM
To: Chando, Kenneth
Subject: RE: Enterprise Manager 1-System Upgrade (different host) from 10.2.0.5 or from 11.1.0.1 to 12c (Doc ID 329.1)

Ken,

I expected you to go through available documentation and find out what is relevant to our situation and to write a concise a step-by-step guide to get it migrated based on the vendor documents you reviewed.

source environment: Oracle 12c OEM and Oracle 11g RDMBS running on Solaris 10

Target environment: Oracle 12c OEM and Oracle 12c RDBMS running on RHEL 6.

Thanks,

Omer

From: Chando, Kenneth
Sent: Monday, October 19, 2015 1:43 PM
To: Abdalla, Omer
Subject: Enterprise Manager 1-System Upgrade (different host) from 10.2.0.5 or from 11.1.0.1 to 12c (Doc ID 329.1)

Hi Omer,

Here is the cross-platform that I researched. Please go through and let me know your thoughts. After you go through, we can see how to customize it in our environment.

Here is the OEM Cross-platform Migration link:

Thank you!

Best,

Ken Chando

HP Enterprise Services

2610 Wycliff Rd Suite 220

Raleigh, NC 27607

(Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

“A lot of people, when a guy scores a lot of goals, think, 'He's a great player', because a goal is very important, but a great player is a player who can do everything on the field. He can do assists, encourage his colleagues, give them confidence to go forward. It is someone who, when a team does not do well, becomes one of the leaders.“

Thank you for your feedback |Recognition@hp

Hi Lionel,

Pele(The Brazilian soccer player) once said:

You’re INDEED a great TEAM player! You know how to lead people when they’re down and disappointed. You’re full of great inspiration.

My short experience working with you has been a wonderful treasure. You embody the skillset to be a great and wonderful leader.

Thank you very much!!!

I wish you well and look forward to be privileged to work with you again some day.

**If you don’t mind, I would like to have your contact to keep in touch**

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

From: Charles, Lionel
Sent: Tuesday, November 10, 2015 1:02 PM
To: DC2 DATABASE SUPPORT
Subject: Final days

Team,

I plan to be on vacation beginning Monday November 16^th through Friday November 27^th 2015. I will return on Monday November 30^th 2015 to say goodbye to a great team I will be leaving behind.

Lionel Charles

(240) 419-0146 – (cell)

(703) 713-7390 – (Lync)

Email Lionel.Charles@hpe.com

Thank you for your feedback |Recognition@hpe.com

Ken,

I am humbled by your comparison and praise and I thank you. The team is a great one of talented individuals and I am happy to be a part of it. Be a good listener, respect others, let all have a fair chance, be patient and ask if you don’t know. Don’t remember to do your homework.

I will share my contact information when I return in November 30^th .

Here is my email address:

lashleyslg@gmail.com

Hope your family is doing well.

Regards

Lionel

Hi Rajeev,

The group distribution list for our team is DC2 Database Support.

Kindly grant SQL Server access to everyone in this list in the DC2LAB.

Below is some of helpful information we got from Bryan.

	Physical Node		IP	Port
DC2	D2LSENPSH138	MGMT3 (Public)	10.236.28.138	717
		PROD3	10.239.74.138
		BUR3	10.236.27.138
		Heartbeat Network	10.10.10.10
		Replica Endpoint		5022

DC2	D2LSENPSH139	MGMT3 (Public)	10.236.28.139	717
		PROD3	10.239.74.139
		BUR3	10.236.27.139
		Heartbeat Network	10.10.10.11
		Replica Endpoint		5022

DC1	D2LSENPSH338	MGMT3 (Public)	10.78.28.138	717
		PROD3	10.78.74.138
		BUR3	10.78.27.138
		Heartbeat Network	192.168.0.138
		Replica Endpoint

DC1	D2LSENPSH339	MGMT3 (Public)	10.78.28.139	717
		PROD3	10.78.74.139
		BUR3	10.78.27.139
		Heartbeat Network	192.168.0.139
		Replica Endpoint		5022

Cluster IP for DC2			10.236.28.140
Cluster IP for DC1			10.78.28.140

Cluster Name		WINSQLCLSTR

Node and File Share Majority		\\Server\Fileshare	\\10.236.28.22\database

SQL AG Name		SQLAG1

Sorry for the long delay, give it another shot with the new vcenter (SAME IP, 10.236.28.130 for vCenter Manager).

Bryan

Thanks!

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

http://ent192.sharepoint.hp.com/teams/hpopncollab/Wiki%20Pages/Set-up.aspx

Thank you for your feedback |Recognition@hp

Bruce, Ken, Omer, Cyrus, Johnnie, Abdel and Hank,

Being a part of your special team meant so much to me. You guys truly exhibit what team work is all about. You never said no when I asked. You did not abandon me when I did not know. I never felt alone among you. You were always ready to share and care. Even when you were away from work I could always count on you. You are all special in your individual roles and as a team.

Please know that I will treasure the experiences I shared with you and know I wish you continued success in your work life and family life. Don’t stray from the values you hold dear. Keep supporting each other and make Hank look good. He thinks the world of your team and he brags about it.

Thank you Hank, Omer, Ken, Johnnie, Cyrus, Abdel and Bruce.

Lionel Charles

(New contact info below)

lashleyslg@gmail.com

(301) 377-3944

echo >> $RMAN_LOG_FILE

chmod 666 $RMAN_LOG_FILE

# ---------------------------------------------------------------------------

# Log the start of this script.

# ---------------------------------------------------------------------------

echo Script $0 >> $RMAN_LOG_FILE

echo ==== started on `date` ==== >> $RMAN_LOG_FILE

echo >> $RMAN_LOG_FILE

# ---------------------------------------------------------------------------

# Replace /u01/app/oracle/product/11.2.0, below, with the Oracle home path.

# ---------------------------------------------------------------------------

ORACLE_HOME=/u01/app/oracle/product/11.2.0.3

export ORACLE_HOME

# ---------------------------------------------------------------------------

# Replace ora81, below, with the Oracle SID of the target database.

# ---------------------------------------------------------------------------

ORACLE_SID=EAIRP

export ORACLE_SID

# ---------------------------------------------------------------------------

# Replace ora81, below, with the Oracle DBA user id (account).

# ---------------------------------------------------------------------------

ORACLE_USER=oracle

# ---------------------------------------------------------------------------

# Set the target connect string.

# Replace "sys/manager", below, with the target connect string.

# ---------------------------------------------------------------------------

TARGET_CONNECT_STR=/

# ---------------------------------------------------------------------------

# Set the Oracle Recovery Manager name.

# ---------------------------------------------------------------------------

RMAN=$ORACLE_HOME/bin/rman

# ---------------------------------------------------------------------------

# Print out the value of the variables set by this script.

# ---------------------------------------------------------------------------

echo >> $RMAN_LOG_FILE

echo "RMAN: $RMAN" >> $RMAN_LOG_FILE

echo "ORACLE_SID: $ORACLE_SID" >> $RMAN_LOG_FILE

echo "ORACLE_USER: $ORACLE_USER" >> $RMAN_LOG_FILE

echo "ORACLE_HOME: $ORACLE_HOME" >> $RMAN_LOG_FILE

# ---------------------------------------------------------------------------

# Print out the value of the variables set by bphdb.

# ---------------------------------------------------------------------------

echo >> $RMAN_LOG_FILE

echo "NB_ORA_FULL: $NB_ORA_FULL" >> $RMAN_LOG_FILE

echo "NB_ORA_INCR: $NB_ORA_INCR" >> $RMAN_LOG_FILE

echo "NB_ORA_CINC: $NB_ORA_CINC" >> $RMAN_LOG_FILE

echo "NB_ORA_SERV: $NB_ORA_SERV" >> $RMAN_LOG_FILE

echo "NB_ORA_POLICY: $NB_ORA_POLICY" >> $RMAN_LOG_FILE

# ---------------------------------------------------------------------------

# NOTE: This script assumes that the database is properly opened. If desired,

# this would be the place to verify that.

# ---------------------------------------------------------------------------

echo >> $RMAN_LOG_FILE

# ---------------------------------------------------------------------------

# If this script is executed from a NetBackup schedule, NetBackup

# sets an NB_ORA environment variable based on the schedule type.

# The NB_ORA variable is then used to dynamically set BACKUP_TYPE

# For example, when:

# schedule type is BACKUP_TYPE is

# ---------------- --------------

# Automatic Full INCREMENTAL LEVEL=0

# Automatic Differential Incremental INCREMENTAL LEVEL=1

# Automatic Cumulative Incremental INCREMENTAL LEVEL=1 CUMULATIVE

# For user initiated backups, BACKUP_TYPE defaults to incremental

# level 0 (full). To change the default for a user initiated

# backup to incremental or incremental cumulative, uncomment

# one of the following two lines.

# BACKUP_TYPE="INCREMENTAL LEVEL=1"

# BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"

# Note that we use incremental level 0 to specify full backups.

# That is because, although they are identical in content, only

# the incremental level 0 backup can have incremental backups of

# level > 0 applied to it.

# ---------------------------------------------------------------------------

if [ "$NB_ORA_FULL" = "1" ]

then

echo "Full backup requested" >> $RMAN_LOG_FILE

BACKUP_TYPE="INCREMENTAL LEVEL=0"

elif [ "$NB_ORA_INCR" = "1" ]

then

echo "Differential incremental backup requested" >> $RMAN_LOG_FILE

BACKUP_TYPE="INCREMENTAL LEVEL=1"

elif [ "$NB_ORA_CINC" = "1" ]

then

echo "Cumulative incremental backup requested" >> $RMAN_LOG_FILE

BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"

elif [ "$BACKUP_TYPE" = "" ]

then

echo "Default - Full backup requested" >> $RMAN_LOG_FILE

BACKUP_TYPE="INCREMENTAL LEVEL=0"

# ---------------------------------------------------------------------------

# Call Recovery Manager to initiate the backup. This example does not use a

# Recovery Catalog. If you choose to use one, replace the option 'nocatalog'

# from the rman command line below with the

# 'rcvcat <userid>/<passwd>@<tns alias>' statement.

# Note: Any environment variables needed at run time by RMAN

# must be set and exported within the switch user (su) command.

# ---------------------------------------------------------------------------

# Backs up the whole database. This backup is part of the incremental

# strategy (this means it can have incremental backups of levels > 0

# applied to it).

# We do not need to explicitly request the control file to be included

# in this backup, as it is automatically included each time file 1 of

# the system tablespace is backed up (the inference: as it is a whole

# database backup, file 1 of the system tablespace will be backed up,

# hence the controlfile will also be included automatically).

# Typically, a level 0 backup would be done at least once a week.

# The scenario assumes:

# o you are backing your database up to two tape drives

# o you want each backup set to include a maximum of 5 files

# o you wish to include offline datafiles, and read-only tablespaces,

# in the backup

# o you want the backup to continue if any files are inaccessible.

# o you are not using a Recovery Catalog

# o you are explicitly backing up the control file. Since you are

# specifying nocatalog, the controlfile backup that occurs

# automatically as the result of backing up the system file is

# not sufficient; it will not contain records for the backup that

# is currently in progress.

# o you want to archive the current log, back up all the

# archive logs using two channels, putting a maximum of 20 logs

# in a backup set, and deleting them once the backup is complete.

# Note that the format string is constructed to guarantee uniqueness and

# to enhance NetBackup for Oracle backup and restore performance.

# NOTE WHEN USING TNS ALIAS: When connecting to a database

# using a TNS alias, you must use a send command or a parms operand to

# specify environment variables. In other words, when accessing a database

# through a listener, the environment variables set at the system level are not

# visible when RMAN is running. For more information on the environment

# variables, please refer to the NetBackup for Oracle Admin. Guide.

# ---------------------------------------------------------------------------

CMD_STR="

ORACLE_HOME=$ORACLE_HOME

export ORACLE_HOME

ORACLE_SID=$ORACLE_SID

export ORACLE_SID

$RMAN target $TARGET_CONNECT_STR nocatalog msglog $RMAN_LOG_FILE append << EOF

RUN {

ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';

ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';

SEND 'NB_ORA_POLICY=COMP_PROJ_Linux_ORA_EAIRP_Inc';

BACKUP

$BACKUP_TYPE

SKIP INACCESSIBLE

TAG db_inc_backup

FILESPERSET 5

# recommended format

FORMAT 'bk_%s_%p_%t'

DATABASE;

sql 'alter system archive log current';

RELEASE CHANNEL ch00;

RELEASE CHANNEL ch01;

# backup all archive logs

ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';

ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';

BACKUP

TAG db_arch_backup

filesperset 20

FORMAT 'al_%s_%p_%t'

ARCHIVELOG ALL DELETE INPUT;

RELEASE CHANNEL ch00;

RELEASE CHANNEL ch01;

# Note: During the process of backing up the database, RMAN also backs up the

# control file. This version of the control file does not contain the

# information about the current backup because "nocatalog" has been specified.

# To include the information about the current backup, the control file should

# be backed up as the last step of the RMAN section. This step would not be

# necessary if we were using a recovery catalog.

ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';

BACKUP

# recommended format

FORMAT 'cntrl_%s_%p_%t'

CURRENT CONTROLFILE;

RELEASE CHANNEL ch00;

}

EOF

# Initiate the command string

if [ "$CUSER" = "root" ]

then

su - $ORACLE_USER -c "$CMD_STR" >> $RMAN_LOG_FILE

RSTAT=$?

else

/usr/bin/sh -c "$CMD_STR" >> $RMAN_LOG_FILE

RSTAT=$?

# ---------------------------------------------------------------------------

# Log the completion of this script.

# ---------------------------------------------------------------------------

if [ "$RSTAT" = "0" ]

then

LOGMSG="ended successfully"

else

LOGMSG="ended in error"

echo >> $RMAN_LOG_FILE

echo Script $0 >> $RMAN_LOG_FILE

echo ==== $LOGMSG on `date` ==== >> $RMAN_LOG_FILE

echo >> $RMAN_LOG_FILE

exit $RSTAT

oracle@D2CSEVPHQ004[EAIRP]# vi nb_inc_backup_EAIRP.sh

#!/bin/sh

# $Header: hot_database_backup.sh,v 1.2 2002/08/06 23:51:42 $

#bcpyrght

#***************************************************************************

#ecpyrght

# ---------------------------------------------------------------------------

# hot_database_backup.sh

# ---------------------------------------------------------------------------

# This script uses Recovery Manager to take a hot (inconsistent) database

# backup. A hot backup is inconsistent because portions of the database are

# being modified and written to the disk while the backup is progressing.

# You must run your database in ARCHIVELOG mode to make hot backups. It is

# assumed that this script will be executed by user root. In order for RMAN

# to work properly we switch user (su -) to the oracle dba account before

# execution. If this script runs under a user account that has Oracle dba

# privilege, it will be executed using this user's account.

# ---------------------------------------------------------------------------

# Determine the user which is executing this script.

# ---------------------------------------------------------------------------

CUSER=`id |cut -d"(" -f2 | cut -d ")" -f1`

# ---------------------------------------------------------------------------

# Put output in <this file name>.out. Change as desired.

# Note: output directory requires write permission.

# ---------------------------------------------------------------------------

RMAN_LOG_FILE=${0}.out

# ---------------------------------------------------------------------------

# You may want to delete the output file so that backup information does

# not accumulate. If not, delete the following lines.

# ---------------------------------------------------------------------------

if [ -f "$RMAN_LOG_FILE" ]

then

rm -f "$RMAN_LOG_FILE"

# -----------------------------------------------------------------

# Initialize the log file.

"nb_inc_backup_EAIRP.sh" 295L, 11626C

I am not sure if you are all aware that HPE is a Diamond Partner of Oracle (there are only a handful of companies who have that kind of partnership with Oracle). This partnership entitle us to access a lot of internal vendor training and certification materials that are not available to the general public and HPE provides vouchers for taking some of the certification exams that are deemed necessary to maintain the partnership status.

Our Company Id is 6057. Please review he following SharePoint site for more information on registering for OPN:

The HPE OPN team also has a presence in Yammer (I am sure you are all aware of what Yammer is):

https://www.yammer.com/hpe.com/#/threads/inGroup?type=in_group&feedId=5364881

Thanks,

OMER ABDALLA
DC2 Database Support

DC2 Program, An ISO 20000:2011 Organization
omer.abdalla@hpe.com

omer.abdalla@associates.hq.dhs.gov

T +1 919 424 5448
M +1 202 870 3162
Hewlett-Packard Enterprise
2610 Wycliff Rd Suite 220
Raleigh, NC 27607
USA

HARDENING SCRIPT:

select OWNER, TABLE_NAME, PRIVILEGE from DBA_TAB_PRIVS

where GRANTEE='PUBLIC' and TABLE_NAME in ('UTL_FILE','UTL_TCP','UTL_SMTP','UTL_HTTP','DBMS_RANDOM','DBMS_LDAP','DBMS_LDAP_UTIL','DBMS_BACKUP_RESTORE','DBMS_JAVA');

PROMPT

PROMPT Please revoke these privileges from PUBLIC by executing the following statements:

set head off feed off

select 'revoke '||PRIVILEGE||' on '||trim(OWNER)||'.'||TABLE_NAME||' from PUBLIC;'

from DBA_TAB_PRIVS

where GRANTEE='PUBLIC' and TABLE_NAME in ('UTL_FILE','UTL_TCP','UTL_SMTP','UTL_HTTP','DBMS_RANDOM','DBMS_LDAP','DBMS_LDAP_UTIL','DBMS_BACKUP_RESTORE','DBMS_JAVA');

set head on feed on

PROMPT

PROMPT All system privileges except for CREATE SESSION must be restricted to DBAs,

PROMPT application object owner accounts/schemas (locked accounts), and default Oracle accounts.

PROMPT List of system privileges assigned to Roles

break on grantee skip 1;

col privilege format a35

select grantee, privilege , admin_option

from dba_sys_privs

where grantee in (select role from dba_roles)

and grantee not in ('SELECT_CATALOG_ROLE', 'DBA'

,'IMP_FULL_DATABASE'

,'EXP_FULL_DATABASE','RECOVERY_CATALOG_OWNER'

,'SCHEDULER_ADMIN', 'AQ_ADMINISTRATOR_ROLE')

and privilege not in ('CREATE SESSION')

and (admin_option = 'YES' or privilege like '%ANY%')

order by grantee, privilege

clear breaks;

clear columns;

PROMPT

PROMPT List of Roles assigned to Users

break on granted_role skip 1 ;

select granted_role, grantee, admin_option

from dba_role_privs

where grantee not in ('SYS','SYSTEM', 'DBA',

'DMSYS','CTXSYS','OUTLN','ORDSYS','MDSYS',

'OLAPSYS','SYSMAN','PERFSTAT')

order by granted_role, grantee

clear breaks;

PROMPT

PROMPT List of system privs assigned directly to users

PROMPT These should be reassigned using roles.

break on grantee skip 1;

select grantee, privilege

from dba_sys_privs

where grantee not in (select role from dba_roles)

and grantee not in ('SYS','SYSTEM',

'DMSYS','CTXSYS','OUTLN','ORDSYS','MDSYS','ORDPLUGINS',

'XDB','WMSYS','DBSNMP','OLAPSYS','SYSMAN','PERFSTAT')

order by grantee, privilege

clear breaks;

clear columns;

PROMPT

PROMPT List of object privs assigned directly to users

PROMPT Privileges should be controlled using roles.

col privilege format a10;

col grantee format a15;

col owner_object format a40;

break on grantee on privilege skip 1;

select grantee, privilege,

owner||'.'||table_name owner_object

from dba_tab_privs

where grantee not in (select role from dba_roles)

and grantee not in ('SYS','SYSTEM','PUBLIC',

'DMSYS','CTXSYS','OUTLN','ORDSYS','MDSYS',

'SDB','WMSYS','XDB','DBSNMP',

'OLAPSYS','SYSMAN','PERFSTAT')

order by grantee, privilege

clear breaks;

clear columns;

PROMPT

PROMPT List of users that can pass on system privs and the objects they control

PROMPT Users should not be able to pass system privs to others

break on grantee;

select grantee, privilege

from dba_sys_privs

where admin_option='YES'

and grantee not in ('DBA','SYSTEM','SYS', 'SCHEDULER_ADMIN'

,'XDB','AQ_ADMINISTRATOR_ROLE')

order by grantee, privilege

clear breaks;

PROMPT

PROMPT List of system privileges that should be reviewed and possibly revoked

break on grantee skip 1;

select grantee, privilege

from dba_sys_privs

where( privilege like 'ADMINISTER %'

or privilege like '%ANY%'

or (privilege like 'ALTER%' and privilege not like '%SESSION')

privilege like 'DROP %'

privilege like 'AUDIT%'

or privilege in ('BECOME USER', 'CREATE DATABASE LINK', 'CREATE PROFILE',

'CREATE ROLE', 'CREATE USER', 'CREATE ROLLBACK SEGMENT',

'EXPORT FULL DATABASE', 'IMPORT FULL DATABASE', 'MANAGE TABLESPACE')

)

and grantee not in ('DBA','SYSTEM','SYS','IMP_FULL_DATABASE'

,'EXP_FULL_DATABASE','DMSYS', 'SCHEDULER_ADMIN','ORDSYS', 'XDB'

,'MDSYS','RECOVERY_CATALOG_OWNER','WMSYS','CTXSYS','DMSYS','DBSNMP',

'PERFSTAT','ORDPLUGINS', 'AQ_ADMINISTRATOR_ROLE','OUTLN' )

order by grantee, privilege

clear breaks;

clear columns;

PROMPT

PROMPT List of object privs that should be reviewed and possibly revoked.

col owner_object format a40;

col grantee format a15;

col privilege format a10;

break on grantee skip 1;

select grantee, privilege,

owner||'.'||table_name owner_object

from dba_tab_privs

where owner in ('SYS','SYSTEM')

and table_name like 'DBA%'

and grantee not in ('SELECT_CATALOG_ROLE','SYSTEM','DBA'

,'MDSYS','ORDSYS','WMSYS','DMSYS','AQ_ADMINISTRATOR_ROLE','CTXSYS')

clear breaks;

clear columns;

PROMPT

PROMPT List of objects created using sys or system

PROMPT excluding those created on installation

break on object_type skip 1;

col object_name format a40;

select distinct object_type, object_name

from dba_objects

where owner in ('SYS','SYSTEM')

and trunc(created) > (select trunc(created) from v$database)

and object_type not like 'INDEX%'

order by object_type, object_name

clear breaks;

column owner format a10;

column segment_name format a25;

column segment_type format a25;

set feedback off heading off

select 'The Following is a list of all objects that are owned by users other than SYS and SYSTEM '||chr(13)||chr(10),

'but are stored in the SYSTEM tablespace....'

from dual

where 0 < ( select count(*)

from sys.dba_segments

where owner not in ('SYS', 'SYSTEM','OUTLN')

and tablespace_name = 'SYSTEM' )

set heading on

break on owner skip 1;

select owner, segment_name, segment_type

from sys.dba_segments

where owner not in ('SYS', 'SYSTEM','OUTLN')

and tablespace_name = 'SYSTEM'

order by owner, segment_name

prompt

set feedback off heading off

select 'The Following Users have the SYSTEM tablespace as their Default or '||chr(13)||chr(10),

'Temporary Tablespace. Please change that for all non-system accounts'

from dual

where 0 <

( select count(*)

from sys.dba_users

where username not in ('SYS', 'SYSTEM','OUTLN')

and ( default_tablespace = 'SYSTEM' or temporary_tablespace = 'SYSTEM') )

set heading on

column username format a10;

column default_tablespace format a15 heading 'Default';

column temporary_tablespace format a15 heading 'Temporary';

column account_status format a16 heading 'Account Status';

select username, default_tablespace, temporary_tablespace, account_status

from sys.dba_users

where username not in ('SYS', 'SYSTEM','OUTLN')

and ( default_tablespace = 'SYSTEM' or temporary_tablespace = 'SYSTEM')

order by username

set feedback on

prompt

set feedback on

column username format a20;

PROMPT Opened Accounts

select username , account_status

from dba_users where account_status = 'OPEN'

PROMPT Accounts NOT open

select username , account_status

from dba_users where account_status != 'OPEN'

spool off;

oracle@d2asedvic004[BASSD]#

Thank you!

Derek E. Doolittle

Special Agent

Federal Investigative Services

P.O. Box 71159

Soldier Support Center

4-2843 Normandy Drive, Room B-H-2

Confidentiality Notice: The documents accompanying this email transmittal and/or the content of the email may contain confidential information belonging to the sender. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party without prior authorization. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of these documents is strictly prohibited. If you have received this email transmittal in error, please notify the sender immediately by reply email and destroy all copies of the original message.

From: Chando, Kenneth [mailto:kenneth.chando@hpe.com]
Sent: Wednesday, January 27, 2016 10:46 AM
To: Doolittle, Derek E
Subject: HR Details

Hi Derek,

My HR details are:

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

Hi Derek,

See requested address for my siblings below:

NAME	Address
Susan	19243 Lancer Circle, Purcellville, VA 20132
Josephine	109 Houndschase Run, Cary, NC 27513
Janvier	6163 Bushmill Rd, Raleigh NC 27613
Mathias	2825 Schubert Dr., SilverSpring, MD 20904
John	2632 Weddington Ave, Charlotte, NC 28204
Florence	Douala, Cameroon (Cameroon has no organized street address)

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

From: Doolittle, Derek E [mailto:Derek.Doolittle@opm.gov]
Sent: Thursday, January 28, 2016 7:55 AM
To: Chando, Kenneth
Subject: RE: HR Details

I also need to know the current home addresses for all the individuals you provided. Are Janvier and Florence US citizens or registered aliens?

Derek E. Doolittle

Special Agent

Federal Investigative Services

P.O. Box 71159

Soldier Support Center

4-2843 Normandy Drive, Room B-H-2

From: Chando, Kenneth [mailto:kenneth.chando@hpe.com]
Sent: Wednesday, January 27, 2016 10:46 AM
To: Doolittle, Derek E
Subject: HR Details

Hi Derek,

My HR details are:

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

Ken,

I need one last piece of information. What does Janvier do for a living (employment) and how often do you have contact with him? Weekly, monthly, etc. and the type (phone, email, etc.).

Thanks,

Derek E. Doolittle

Special Agent

Federal Investigative Services

P.O. Box 71159

Soldier Support Center

4-2843 Normandy Drive, Room B-H-2

Ken,

One last thing, I need the phone number for Mathias.

Thanks,

Derek E. Doolittle

Special Agent

Federal Investigative Services

P.O. Box 71159

Soldier Support Center

4-2843 Normandy Drive, Room B-H-2

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

From: Chando, Kenneth
Sent: Thursday, April 14, 2016 2:18 PM
To: Chando, Kenneth <kenneth.chando@hpe.com>
Subject: Testing Results

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

83%

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

From: Chando, Kenneth
Sent: Thursday, April 14, 2016 2:34 PM
To: Chando, Kenneth <kenneth.chando@hpe.com>
Subject: RE: Testing Results-ANSWERS

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

From: Chando, Kenneth
Sent: Thursday, April 14, 2016 2:18 PM
To: Chando, Kenneth <kenneth.chando@hpe.com>
Subject: Testing Results

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

DBASE TUNING REPORT

oracle@d2aseutsh018.ndc.local[openview]# vi rpt_db_tuning.sql

substr(to_char(a.extents,'9999'),2)||'/'||

substr(to_char(b.max_extents,'9999'),2) "Extents",

100*(a.extents/b.max_extents) "% to Max"

from sys.dba_segments a, sys.dba_indexes b

where a.owner not in ('SYS','SYSTEM')

and b.index_name = a.segment_name

and b.owner = a.owner

and a.segment_type = 'INDEX'

and 100*(a.extents/b.max_extents) >= 75

union

select substr(a.tablespace_name,1,19) "Tablespace",

a.segment_type "Type",

substr(a.owner||'.'||a.segment_name,1,37) "Segment",

bytes "Bytes",

substr(to_char(a.extents,'9999'),2)||'/'||

substr(to_char(b.max_extents,'9999'),2) "Extents",

100*(a.extents/b.max_extents) "% to Max"

from sys.dba_segments a, sys.dba_tables b

where a.owner not in ('SYS','SYSTEM')

and b.table_name = a.segment_name

and b.owner = a.owner

and a.segment_type = 'TABLE'

and 100*(a.extents/b.max_extents) >= 75

order by 2, 1, 3

clear computes

ttitle off

prompt

rem ******************************* USER STATS ********************************

set newpage 0

rem Shows number of accounts , DBA accounts and then analyzes breakdown

rem by tablespaces

ttitle center 'Number of Users per Tablespace' skip 2

column df format a20 heading 'Default Tablespace'

column tmp format a20 heading 'Temporary Tablespace'

column cnt_df format 9,999 heading '# of|Users'

column cnt_tmp format 9,999 heading '# of|Users'

select

Default_tablespace df,

count(*) cnt_df,

temporary_tablespace tmp,

count(*) cnt_tmp

from sys.dba_users

group by default_tablespace, temporary_tablespace

clear computes

clear breaks

ttitle off

rem ********************** DATABASE OBJECTS ****************************

rem This counts the number of DB objects defined in the catalog

rem - it can provide additional information when sizing the

rem DC_ Dictionary cache parameters and reducing recursive calls

set newpage 0

column object_type format a20 heading 'Object Type'

column cnt format 9,999,999 heading 'Count'

compute sum of cnt on report

break on report

ttitle center 'Count of Objects' skip 2

select owner, object_type, count(*)

from dba_objects

group by owner, object_type;

select object_type , count(object_type) cnt

from sys.dba_objects

group by object_type

union

select 'COLUMN' , count(*) kount

from sys.col$

union

select 'DB LINKS' , count(*) kount

from sys.link$

union

select 'CONSTRAINT' , count(*) kount

from sys.con$

prompt

clear computes

clear breaks

ttitle off

rem *********** THIS PRINTS OUT THE CURRENT SGA PARAMETERS ********

set newpage 0 termout on

prompt

prompt Reporting Database Parameters

prompt

set termout off

column name format a45 heading 'Parameter Name'

column value format a60 heading 'Parameter Value'

ttitle center 'Database Parameter Values' skip 2

select name , value

from v$parameter

order by name

clear computes

clear breaks

ttitle off

rem ******************************* Initialization Parameters - Recommendation ******************************

rem checks various key INIT.ORA parameters and advises on their appropriateness.

set newpage 0

set heading off

set feedback off

set verify off

set echo off

ttitle '* * * * *' center skip 2

select 'Archiving is not turned on for the '||

' database! This means that recovery is only ' nl,

'possible up to the last cold backup or export. This is not good practice for a ' nl,

'production database. Check if this is acceptable.' nl

from v$parameter

where name = 'log_archive_start'

and value = 'FALSE'

select 'The Buffer cache (DB_BLOCK_BUFFERS * DB_BLOCK_SIZE ) is set too low for a Production ' nl,

'database. It is set to '||to_char(max(bytes)) ||'. It should be at least 16 Megabytes for a serious' nl,

'production system. If you have sufficient free memory, consider increasing it '

from v$sgastat

where name = 'db_block_buffers'

having max(bytes) < 16000000

select 'Your SORT_AREA_RETAINED_SIZE and SORT_AREA_SIZE are set to the same value('||a.value||'). ' nl,

'Unless you are running a database which is totally dedicated to large batch jobs, it is best ' nl,

'to allocate the extra memory only to the people that need it. Typical settings are 64K for' nl,

'SORT_AREA_RETAINED_SIZE and 2Meg for SORT_AREA_SIZE '

from v$parameter a , v$parameter b

where a.name = 'sort_area_size'

and b.name = 'sort_area_retained_size'

and b.value = a.value

select 'The SEQUENCE_CACHE_ENTRIES is undersized. It should ideally be sized to fit all of the ' nl,

'cached entries required for all sequences. The parameter is set to '||b.value||'.' nl,

'It should be set to '||sum (a.cache_size) ||'.'

from sys.dba_sequences a, v$parameter b

where b.name='sequence_cache_entries'

group by b.value

having sum (a.cache_size) < b.value

select 'Your LOG_BUFFER could be enlarged to improve performance. It is currently set ' nl,

'to '||b.value||'. There have been a number of redo log space request ('||a.value||') waits.' nl,

'Consider enlarging the LOG_BUFFER to a value such as '||b.value * 1.5||'.'

from v$parameter b, v$sysstat a

where b.name = 'log_buffer'

and a.name = 'redo log space requests'

and a.value > 50

and b.value < (select 1000000 from dual)

select 'Warning: Enqueue Timeouts are '||value||'. They should be zero if the INIT.ora parameter is ' line1,

'high enough. Try increasing INIT.ora parameter ENQUEUE_RESOURCES and see if the Timeouts reduces.'

from v$sysstat

where name = 'enqueue timeouts'

and value > 0

rem ******************************* System Tablespace - Recommendation **************************************

rem Make sure that SYSTEM tablespace is used only to store Oracle objects.

ttitle off

column owner format a10;

column segment_name format a25;

column segment_type format a25;

column nl newline;

select 'The Following is a list of all objects that are owned by users other than SYS and SYSTEM ' nl,

'but are stored in the SYSTEM tablespace....' nl

from dual

where 0 < ( select count(*)

from sys.dba_segments

where owner not in ('SYS', 'SYSTEM')

and tablespace_name = 'SYSTEM' )

break on owner skip 1;

select ' ', owner, segment_name, segment_type

from sys.dba_segments

where owner not in ('SYS', 'SYSTEM')

and tablespace_name = 'SYSTEM'

order by owner, segment_name

prompt

select 'You have modified your SYSTEM Tablespace PCTINCREASE to '||pct_increase nl,

'This is different to Oracles recommended setting of 50.' nl,

'Make sure that you will not have any problems as a result of this. ' nl

from sys.dba_tablespaces

where pct_increase != 50

and tablespace_name = 'SYSTEM'

prompt

select 'The Following Users have the SYSTEM tablespace as their Default Tablespace.' nl,

'This is bad practice because it can often cause the SYSTEM tablespace to ' nl,

'fill and Oracle to grind to a halt. ' nl

' nl

from dual

where 0 <

( select count(*)

from sys.dba_users

where username not in ('SYS', 'SYSTEM')

and default_tablespace = 'SYSTEM' )

select ' ', username

from sys.dba_users

where username not in ('SYS', 'SYSTEM')

and default_tablespace = 'SYSTEM'

order by username

prompt

select 'The Following Users have the SYSTEM tablespace as their Temporary Tablespace.' nl,

'This is bad practice because it can often cause the SYSTEM tabelspace to ' nl,

'fill and Oracle to grind to a halt. ' nl

from dual

where 0 <

( select count(*)

from sys.dba_users

where username not in ('SYS', 'SYSTEM')

and temporary_tablespace = 'SYSTEM' )

select ' ', username

from sys.dba_users

where username not in ('SYS', 'SYSTEM')

and temporary_tablespace = 'SYSTEM'

order by username

prompt

prompt End of Report.

ttitle '************ END OF REPORT ************' center skip 2

select ' ' from dual;

clear computes

clear breaks

ttitle off

spool off

set heading on feedback on termout on

======2====================================================================================================================

oracle@d2aseutsh018.ndc.local[openview]# vi rpt_hardening.sql

-- Oracle Hardening Report

-- This script will generate a file named rpt_hardening_<SID>_<DATE>.txt

-- Written by: Omer Abdalla - 10/29/2008 - Last updated 05/12/2011

col dbname new_value n_dbname noprint

col rptnme new_value n_rptnme noprint

select name||'_'||to_char(sysdate,'YYMMDD') rptnme, name dbname

from v$database;

spool rpt_hardening_&n_rptnme..txt

set pagesize 6000;

set linesize 120;

set feedback off;

set echo off;

btitle off;

ttitle off;

set head off;

select

'Oracle Hardening Report for '||instance_name||' as of '||

to_char(sysdate,'DL')||' '||to_char(sysdate,'HH24:MI')

from v$instance

select

'Oracle Version: '||version from v$instance

col name format a60

col status format a20

PROMPT

PROMPT There should be at least two copies of the controlfile, each in a separate filesystem/disk.

PROMPT Here are the current control files for this instance:

select name, status from v$controlfile

PROMPT

PROMPT There should be at least 3 redo logs with 2 members in each group (in separate disks).

PROMPT Here are the current groups and logfiles:

break on groupno;

column groupno format a10

col member format a60

select 'GROUP '||group# groupno, member from v$logfile

order by group#

PROMPT

PROMPT The following are file destinations as set in the spfile:

col name format a30;

col value format a50;

select name, value from v$spparameter

where name like '%_dest'

set feedback on;

PROMPT

PROMPT Now checking Security Compliance items

PROMPT

PROMPT 1.1 Oracle Default Users

PROMPT With the exception of SYS, SYSTEM, DBSNMP, and SYSMAN

PROMPT All default accounts should be locked and expired.

PROMPT Please lock the following accounts (if any listed):

col username format a37

col profile format a20

select username, profile, account_status

from dba_users

where username in (

'DIP',

'DMSYS',

'EXFSYS',

'MDDATA',

'SCOTT',

'SI_INFORMTN_SCHEMA',

'OUTLN',

'WKPROXY',

'WMSYS',

'ORDSYS',

'ORDPLUGINS',

'MDSYS',

'CTXSYS',

'XDB',

'ANONYMOUS',

'OWNER',

'WKSYS',

'ODM_MTR',

'ODM',

'OLAPSYS',

'HR',

'OE',

'PM',

'SH',

'QS_ADM',

'QS',

'QS_WS',

'QS_ES',

'QS_OS',

'QS_CBADM',

'QS_CB',

'QS_CS') and rtrim(account_status) not in ('LOCKED','EXPIRED '||Chr(38)||' LOCKED')

PROMPT

PROMPT 1.1 Database Demonstration Objects

PROMPT The following demo/sample schema accounts should not exist

PROMPT in production databases. Please remove them:

select username, account_status

from dba_users

where username in (

'SH',

'HR',

'OE',

'PM',

'QS_ADM',

'QS',

'SCOTT',

'QS_WS',

'QS_ES',

'QS_OS',

'QS_CBADM',

'QS_CB',

'QS_CS')

PROMPT

PROMPT 1.2 Default Database Accounts With Default Passwords

PROMPT The following accounts (if any listed) are using default passwords

PROMPT Either remove the accounts or change the passwords,

PROMPT lock and expire the accounts, and audit them:

PROMPT Running Oracle Default Password Scanner from patch 4926128

@dfltpass

btitle off;

ttitle off;

REM 1.2 To identify accounts with default passwords in 11g we run the following query

PROMPT 1.2 Identifying Default Database Accounts With Default Passwords in 11g

SELECT d.username, u.account_status from DBA_USERS_WITH_DEFPWD d, DBA_USERS u

WHERE d.username = u.username and u.username not in ('XS$NULL')

ORDER by 2,1;

PROMPT Execute the following statements to change default passwords on all default oracle accounts

PROMPT

select 'ALTER USER '||username||' identified by &New_Password;'

from DBA_USERS_WITH_DEFPWD

WHERE username not in ('XS$NULL');

PROMPT

PROMPT 1.3 The following accounts are assigned the default profile

PROMPT Please configure and assign user profile definitions to

PROMPT each database user that adheres to password policy guidelines.

PROMPT

col username format a30

select username, profile from dba_users

where profile = 'DEFAULT' and username not in ('XS$NULL');

PROMPT Execute the following statements to apply the DHS_H_APPL to all default oracle accounts

PROMPT

select 'ALTER USER '||username||' PROFILE DHS_H_APPL;'

from dba_users where profile = 'DEFAULT' and username not in ('XS$NULL');

PROMPT

PROMPT List of Profiles and and resources assigned to profiles

col limit format a20;

break on profile skip 1;

select profile, resource_name, limit

from dba_profiles

group by profile, resource_name, limit

order by profile, resource_name, limit

clear breaks;

clear columns;

set heading off

set feedback off

-- select ''||chr(13)||chr(10)||''||chr(13)||chr(10),

-- 'remote_login_passwordfile should be set to ''NONE'' . It is currently set to '||value||chr(13)||chr(10),

-- 'You need to set it by running the following command:'||chr(13)||chr(10)||chr(13)||chr(10),

-- 'ALTER SYSTEM SET remote_login_passwordfile=NONE SCOPE=SPFILE; '

-- from v$spparameter

-- where rtrim(lower(name))='remote_login_passwordfile' and (value is null or value not in ('None','NONE','none'));

select ''||chr(13)||chr(10)||''||chr(13)||chr(10),

'audit_sys_operations should be set to ''True'' . It is currently set to '||value||chr(13)||chr(10),

'You need to set it by running the following command:'||chr(13)||chr(10)||chr(13)||chr(10),

'ALTER SYSTEM SET audit_sys_operations=TRUE SCOPE=SPFILE; '

from v$spparameter

where rtrim(lower(name))='audit_sys_operations' and (value is null or value not in ('True','TRUE','true'));

select ''||chr(13)||chr(10)||''||chr(13)||chr(10),

'********************************************************************************',

''||chr(13)||chr(10)||''||chr(13)||chr(10),

'audit_trail should be set to ''db_extended'' . It is currently set to '||value||chr(13)||chr(10),

'You need to set it by running the following command:'||chr(13)||chr(10)||chr(13)||chr(10),

'ALTER SYSTEM SET audit_trail=''db_extended'' SCOPE=spfile; '

from v$spparameter

where rtrim(lower(name))='audit_trail' and (value is null or rtrim(lower(value)) not in ('db_extended'));

select ''||chr(13)||chr(10)||''||chr(13)||chr(10),

'The AUD$ should be owned by SYS user.'||chr(13)||chr(10),

'It is currently owned by '||owner

from dba_tables where table_name='AUD$' and owner!='SYS';

select ''||chr(13)||chr(10)||''||chr(13)||chr(10),

'o7_dictionary_accessibility should be set to ''FALSE'' . '||chr(13)||chr(10)||

'It is currently set to '||value||chr(13)||chr(10),

'You need to set it by running the following command:'||chr(13)||chr(10)||chr(13)||chr(10),

'ALTER SYSTEM SET o7_dictionary_accessibility=FALSE SCOPE=SPFILE; '

from v$spparameter

where rtrim(lower(name))='o7_dictionary_accessibility' and rtrim(lower(value))='true';

select ''||chr(13)||chr(10)||''||chr(13)||chr(10),

'utl_file_dir is currently set to '||value||chr(13)||chr(10),

'This parameter should not be set. Use CREATE DIRECTORY options'||chr(13)||chr(10)||

'to setup file I/O for PL/SQL.'

from v$spparameter

where rtrim(lower(name))='utl_file_dir' and value is not null;

set feedback off

select '_trace_files_public is not set to FALSE. '||chr(13)||chr(10)||

' Add the following undocumented parameter setting to init.ora:'||chr(13)||chr(10)||

'_trace_files_public=false' AS "init.ora setting"

from sys.x$ksppi x,sys.x$ksppcv y

where x.inst_id=userenv('Instance')

and y.inst_id=userenv('Instance')

and x.indx=y.indx

and x.ksppinm='_trace_files_public' and y.ksppstvl!='FALSE';

set heading on

set feedback on

PROMPT Following priviliges are assigned to PUBLIC

PROMPT Revoke all unnecessary privileges and roles from PUBLIC.

PROMPT

PROMPT List of system privs assigned to PUBLIC

PROMPT These should be revoked.

col privilege format a15;

col grantee format a15;

select grantee, privilege

from dba_sys_privs

where grantee in ('PUBLIC')

col OWNER format a10

col TABLE_NAME format a20

col PRIVILEGE format a15

PROMPT

PROMPT Revoke unnecessary execute privileges on Oracle-supplied PL/SQL packages

PROMPT from the PUBLIC role. These Privileges should be controlled using roles.

PROMPT

select OWNER, TABLE_NAME, PRIVILEGE from DBA_TAB_PRIVS

where GRANTEE='PUBLIC' and TABLE_NAME in ('UTL_FILE','UTL_TCP','UTL_SMTP','UTL_HTTP','DBMS_RANDOM','DBMS_LDAP','DBMS_LDAP_UTIL','DBMS_BACKUP_RESTORE','DBMS_JAVA');

PROMPT

PROMPT Please revoke these privileges from PUBLIC by executing the following statements:

set head off feed off

select distinct 'grant EXECUTE on SYS.UTL_FILE to MDSYS, OLAPSYS, WMSYS, ORACLE_OCM, ORDPLUGINS, XDB, ORDSYS;'||chr(13)||chr(10)||

'grant EXECUTE on SYS.DBMS_LDAP to WMSYS, APEX_030200;'||chr(13)||chr(10)||

'grant EXECUTE on SYS.UTL_HTTP to ORDPLUGINS, MDSYS;'||chr(13)||chr(10)||

'grant EXECUTE on SYS.DBMS_RANDOM to MDSYS, DBSNMP;'||chr(13)||chr(10)||

'grant EXECUTE on SYS.DBMS_JAVA to MDSYS;'

from DBA_TAB_PRIVS

where GRANTEE='PUBLIC' and TABLE_NAME in ('UTL_FILE','UTL_TCP','UTL_SMTP','UTL_HTTP','DBMS_RANDOM','DBMS_LDAP','DBMS_LDAP_UTIL','DBMS_BACKUP_RESTORE','DBMS_JAVA');

select distinct 'revoke '||PRIVILEGE||' on '||trim(OWNER)||'.'||TABLE_NAME||' from PUBLIC;'

from DBA_TAB_PRIVS

where GRANTEE='PUBLIC' and TABLE_NAME in ('UTL_FILE','UTL_TCP','UTL_SMTP','UTL_HTTP','DBMS_RANDOM','DBMS_LDAP','DBMS_LDAP_UTIL','DBMS_BACKUP_RESTORE','DBMS_JAVA');

select distinct '@?/rdbms/admin/utlrp.sql'

from DBA_TAB_PRIVS

where GRANTEE='PUBLIC' and TABLE_NAME in ('UTL_FILE','UTL_TCP','UTL_SMTP','UTL_HTTP','DBMS_RANDOM','DBMS_LDAP','DBMS_LDAP_UTIL','DBMS_BACKUP_RESTORE','DBMS_JAVA');

set feedback on

prompt

set feedback on

column username format a40;

column profile format a15;

column account_status format a18;

PROMPT Opened Accounts

select username, profile , account_status

from dba_users where account_status = 'OPEN'

PROMPT Accounts NOT open

select username, profile , account_status

from dba_users where account_status != 'OPEN'

spool off;

============3====================================================================================================

oracle@d2aseutsh018.ndc.local[openview]# vi rpt_scanner.sql

-- ----------------------------------------------------------------------------

-- --

-- PENTEST LIMITED --

-- --------------- --

-- --

-- File Name : %M%.%R% --

-- Author : Pentest Limited --

-- Date : November 2001 --

-- --

-- Description --

-- ----------- --

-- --

-- Simple Oracle scanner to review some basic aspects of an Oracle --

-- installation. --

-- --

-- Version History --

-- =============== --

-- --

-- Who Ver Date Description --

-- ------- ----- -------- ------------------------------ --

-- PF 1.0 Dec 2001 First Issue --

-- ----------------------------------------------------------------------------

-- set up SQL*PLUS

-- ----------------------------------------------------------------------------

whenever sqlerror exit rollback

set head on

set feed on

set linesize 80

set termout on

set serveroutput on size 1000000

-- ----------------------------------------------------------------------------

-- capture the output

-- ----------------------------------------------------------------------------

spool scanner.lis

-- ----------------------------------------------------------------------------

-- create an anonymouse block to scan with

-- ----------------------------------------------------------------------------

declare

type user_tab is table of varchar2(30) index by binary_integer;

type pwd_tab is table of varchar2(30) index by binary_integer;

type hash_tab is table of varchar2(16) index by binary_integer;

username user_tab;

password pwd_tab;

hash hash_tab;

tab_key binary_integer:=1;

i binary_integer:=1;

cursor c_user is

select username,

password

from dba_users;

cursor c_utl_cur is

select rtrim(name) name,

rtrim(value) value

from v$parameter

where name='utl_file_dir';

cursor c_trace is

select rtrim(name) name,

decode(rtrim(value),NULL,'NULL',rtrim(value)) value

from v$parameter

where name like '%dest%';

cursor c_utl_trace is

select rtrim(a.name) name

from v$parameter a,

v$parameter b

where a.name='utl_file_dir'

and b.name like '%dest%'

and a.value=b.value;

cursor c_sys_priv (cp_priv in dba_sys_privs.privilege%type) is

select grantee,

privilege

from dba_sys_privs

where privilege like cp_priv;

cursor c_admin is

select grantee,

privilege priv

from dba_sys_privs

where admin_option='YES'

union

select grantee,

granted_role priv

from dba_role_privs

where admin_option='YES';

cursor c_grant is

select grantee,

privilege,

table_name

from dba_tab_privs

where grantable='YES'

union

select grantee,

privilege,

table_name

from dba_col_privs

where grantable='YES';

cursor c_ext is

select username

from dba_users

where password='EXTERNAL';

cursor c_dba is

select grantee

from dba_role_privs

where granted_role='DBA';

cursor c_links is

select name,

host,

userid,

password,

authusr,

authpwd

from sys.link$

where password is not null;

lv_sys_priv c_sys_priv%rowtype;

lv_utl_cur c_utl_cur%rowtype;

lv_trace c_trace%rowtype;

lv_utl_trace c_utl_trace%rowtype;

found number:=0;

begin

-- --------------------------------------------------------------------

-- manually load the user list into the tables

-- --------------------------------------------------------------------

tab_key:=1;

username(tab_key):='ADAMS';

password(tab_key):='WOOD';

hash(tab_key):='72CDEF4A3483F60D';

tab_key:=2;

username(tab_key):='ADLDEMO';

password(tab_key):='ADLDEMO';

hash(tab_key):='147215F51929A6E8';

tab_key:=3;

username(tab_key):='APPLSYS';

password(tab_key):='FND';

hash(tab_key):='0F886772980B8C79';

tab_key:=4;

username(tab_key):='APPLYSYSPUB';

password(tab_key):='PUB';

hash(tab_key):='A5E09E84EC486FC9';

tab_key:=5;

username(tab_key):='APPS';

password(tab_key):='APPS';

hash(tab_key):='D728438E8A5925E0';

tab_key:=6;

username(tab_key):='AQDEMO';

password(tab_key):='AQDEMO';

hash(tab_key):='5140E342712061DD';

tab_key:=7;

username(tab_key):='AQJAVA';

password(tab_key):='AQJAVA';

hash(tab_key):='8765D2543274B42E';

tab_key:=8;

username(tab_key):='AQUSER';

password(tab_key):='AQUSER';

hash(tab_key):='4CF13BDAC1D7511C';

tab_key:=9;

username(tab_key):='AUDIOUSER';

password(tab_key):='AUDIOUSER';

hash(tab_key):='CB4F2CEC5A352488';

tab_key:=10;

username(tab_key):='AURORA$ORB$UNAUTHENTICATED';

password(tab_key):='INVALID';

hash(tab_key):='80C099F0EADF877E';

tab_key:=11;

username(tab_key):='BLAKE';

password(tab_key):='PAPER';

hash(tab_key):='9435F2E60569158E';

tab_key:=12;

username(tab_key):='CATALOG';

password(tab_key):='CATALOG';

hash(tab_key):='397129246919E8DA';

tab_key:=13;

username(tab_key):='CDEMO82';

password(tab_key):='CDEMO83';

hash(tab_key):='7299A5E2A5A05820';

tab_key:=14;

username(tab_key):='CDEMOCOR';

password(tab_key):='CDEMOCOR';

hash(tab_key):='3A34F0B26B951F3F';

tab_key:=15;

username(tab_key):='CDEMOUCB';

password(tab_key):='CDEMOUCB';

hash(tab_key):='CEAE780F25D556F8';

tab_key:=16;

username(tab_key):='CDEMORID';

password(tab_key):='CDEMORID';

hash(tab_key):='E39CEFE64B73B308';

tab_key:=17;

username(tab_key):='CENTRA';

password(tab_key):='CENTRA';

hash(tab_key):='63BF5FFE5E3EA16D';

tab_key:=18;

username(tab_key):='CLARK';

password(tab_key):='CLOTH';

hash(tab_key):='7AAFE7D01511D73F';

tab_key:=19;

username(tab_key):='COMPANY';

password(tab_key):='COMPANY';

hash(tab_key):='402B659C15EAF6CB';

tab_key:=20;

username(tab_key):='CSMIG';

password(tab_key):='CSMIG';

hash(tab_key):='09B4BB013FBD0D65';

tab_key:=21;

username(tab_key):='CTXDEMO';

password(tab_key):='CTXDEMO';

hash(tab_key):='CB6B5E9D9672FE89';

tab_key:=22;

username(tab_key):='CTXSYS';

password(tab_key):='CTXSYS';

hash(tab_key):='24ABAB8B06281B4C';

tab_key:=23;

username(tab_key):='DBSNMP';

password(tab_key):='DBSNMP';

hash(tab_key):='E066D214D5421CCC';

tab_key:=24;

username(tab_key):='DEMO';

password(tab_key):='DEMO';

hash(tab_key):='4646116A123897CF';

tab_key:=25;

username(tab_key):='DEMO8';

password(tab_key):='DEMO9';

hash(tab_key):='0E7260738FDFD678';

tab_key:=26;

username(tab_key):='EMP';

password(tab_key):='EMP';

hash(tab_key):='B40C23C6E2B4EA3D';

tab_key:=27;

username(tab_key):='EVENT';

password(tab_key):='EVENT';

hash(tab_key):='7CA0A42DA768F96D';

tab_key:=28;

username(tab_key):='FINANCE';

password(tab_key):='FINANCE';

hash(tab_key):='6CBBF17292A1B9AA';

tab_key:=29;

username(tab_key):='FND';

password(tab_key):='FND';

hash(tab_key):='0C0832F8B6897321';

tab_key:=30;

username(tab_key):='GPFD';

password(tab_key):='GPFD';

hash(tab_key):='BA787E988F8BC424';

tab_key:=31;

username(tab_key):='GPLD';

password(tab_key):='GPLD';

hash(tab_key):='9D561E4D6585824B';

tab_key:=32;

username(tab_key):='HR';

password(tab_key):='HR';

hash(tab_key):='4C6D73C3E8B0F0DA';

tab_key:=33;

username(tab_key):='HLW';

password(tab_key):='HLW';

hash(tab_key):='855296220C095810';

tab_key:=34;

username(tab_key):='IMAGEUSER';

password(tab_key):='IMAGEUSER';

hash(tab_key):='E079BF5E433F0B89';

tab_key:=35;

username(tab_key):='IMEDIA';

password(tab_key):='IMEDIA';

hash(tab_key):='8FB1DC9A6F8CE827';

tab_key:=36;

username(tab_key):='JONES';

password(tab_key):='STEEL';

hash(tab_key):='B9E99443032F059D';

tab_key:=37;

username(tab_key):='JMUSER';

password(tab_key):='JMUSER';

hash(tab_key):='063BA85BF749DF8E';

tab_key:=38;

username(tab_key):='LBACSYS';

password(tab_key):='LBACSYS';

hash(tab_key):='AC9700FD3F1410EB';

tab_key:=39;

username(tab_key):='MDSYS';

password(tab_key):='MDSYS';

hash(tab_key):='9AAEB2214DCC9A31';

tab_key:=40;

username(tab_key):='MFG';

password(tab_key):='MFG';

hash(tab_key):='FC1B0DD35E790847';

tab_key:=41;

username(tab_key):='MIGRATE';

password(tab_key):='MIGRATE';

hash(tab_key):='5A88CE52084E9700';

tab_key:=42;

username(tab_key):='MILLER';

password(tab_key):='MILLER';

hash(tab_key):='D0EFCD03C95DF106';

tab_key:=43;

username(tab_key):='MMO2';

password(tab_key):='MMO3';

hash(tab_key):='AE128772645F6709';

tab_key:=44;

username(tab_key):='MODTEST';

password(tab_key):='YES';

hash(tab_key):='BBFF58334CDEF86D';

tab_key:=45;

username(tab_key):='MOREAU';

password(tab_key):='MOREAU';

hash(tab_key):='CF5A081E7585936B';

tab_key:=46;

username(tab_key):='NAMES';

password(tab_key):='NAMES';

hash(tab_key):='9B95D28A979CC5C4';

tab_key:=47;

username(tab_key):='MTSSYS';

password(tab_key):='MTSSYS';

hash(tab_key):='6465913FF5FF1831';

tab_key:=48;

username(tab_key):='MXAGENT';

password(tab_key):='MXAGENT';

hash(tab_key):='C5F0512A64EB0E7F';

tab_key:=49;

username(tab_key):='OCITEST';

password(tab_key):='OCITEST';

hash(tab_key):='C09011CB0205B347';

tab_key:=50;

username(tab_key):='ODS';

password(tab_key):='ODS';

hash(tab_key):='89804494ADFC71BC';

tab_key:=51;

username(tab_key):='ODSCOMMON';

password(tab_key):='ODSCOMMON';

hash(tab_key):='59BBED977430C1A8';

tab_key:=52;

username(tab_key):='OE';

password(tab_key):='OE';

hash(tab_key):='D1A2DFC623FDA40A';

tab_key:=53;

username(tab_key):='OEMADM';

password(tab_key):='OEMADM';

hash(tab_key):='9DCE98CCF541AAE6';

tab_key:=54;

username(tab_key):='OLAPDBA';

password(tab_key):='OLAPDBA';

hash(tab_key):='1AF71599EDACFB00';

tab_key:=55;

username(tab_key):='OLAPSVR';

password(tab_key):='INSTANCE';

hash(tab_key):='AF52CFD036E8F425';

tab_key:=56;

username(tab_key):='OLAPSYS';

password(tab_key):='MANAGER';

hash(tab_key):='3FB8EF9DB538647C';

tab_key:=57;

username(tab_key):='ORAREGSYS';

password(tab_key):='ORAREGSYS';

hash(tab_key):='28D778112C63CB15';

tab_key:=58;

username(tab_key):='ORDPLUGINS';

password(tab_key):='ORDPLUGINS';

hash(tab_key):='88A2B2C183431F00';

tab_key:=59;

username(tab_key):='ORDSYS';

password(tab_key):='ORDSYS';

hash(tab_key):='7EFA02EC7EA6B86F';

tab_key:=60;

username(tab_key):='OUTLN';

password(tab_key):='OUTLN';

hash(tab_key):='4A3BA55E08595C81';

tab_key:=61;

username(tab_key):='PERFSTAT';

password(tab_key):='PERFSTAT';

hash(tab_key):='AC98877DE1297365';

tab_key:=62;

username(tab_key):='PM';

password(tab_key):='PM';

hash(tab_key):='C7A235E6D2AF6018';

tab_key:=63;

username(tab_key):='PO';

password(tab_key):='PO';

hash(tab_key):='355CBEC355C10FEF';

tab_key:=64;

username(tab_key):='PO8';

password(tab_key):='PO8';

hash(tab_key):='7E15FBACA7CDEBEC';

tab_key:=65;

username(tab_key):='PO7';

password(tab_key):='PO7';

hash(tab_key):='6B870AF28F711204';

tab_key:=66;

username(tab_key):='PORTAL30';

password(tab_key):='PORTAL31';

hash(tab_key):='D373ABE86992BE68';

tab_key:=67;

username(tab_key):='PORTAL30_DEMO';

password(tab_key):='PORTAL30_DEMO';

hash(tab_key):='CFD1302A7F832068';

tab_key:=68;

username(tab_key):='PORTAL30_PUBLIC';

password(tab_key):='PORTAL30_PUBLIC';

hash(tab_key):='42068201613CA6E2';

tab_key:=69;

username(tab_key):='PORTAL30_SSO';

password(tab_key):='PORTAL30_SSO';

hash(tab_key):='882B80B587FCDBC8';

tab_key:=70;

username(tab_key):='PORTAL30_SSO_PS';

password(tab_key):='PORTAL30_SSO_PS';

hash(tab_key):='F2C3DC8003BC90F8';

tab_key:=71;

username(tab_key):='PORTAL30_SSO_PUBLIC';

password(tab_key):='PORTAL30_SSO_PUBLIC';

hash(tab_key):='98741BDA2AC7FFB2';

tab_key:=72;

username(tab_key):='POWERCARTUSER';

password(tab_key):='POWERCARTUSER';

hash(tab_key):='2C5ECE3BEC35CE69';

tab_key:=73;

username(tab_key):='PRIMARY';

password(tab_key):='PRIMARY';

hash(tab_key):='70C3248DFFB90152';

tab_key:=74;

username(tab_key):='PUBSUB';

password(tab_key):='PUBSUB';

hash(tab_key):='80294AE45A46E77B';

tab_key:=75;

username(tab_key):='QS';

password(tab_key):='QS';

hash(tab_key):='4603BCD2744BDE4F';

tab_key:=76;

username(tab_key):='QS_ADM';

password(tab_key):='QS_ADM';

hash(tab_key):='3990FB418162F2A0';

tab_key:=77;

username(tab_key):='QS_CB';

password(tab_key):='QS_CB';

hash(tab_key):='870C36D8E6CD7CF5';

tab_key:=78;

username(tab_key):='QS_CBADM';

password(tab_key):='QS_CBADM';

hash(tab_key):='20E788F9D4F1D92C';

tab_key:=79;

username(tab_key):='QS_CS';

password(tab_key):='QS_CS';

hash(tab_key):='2CA6D0FC25128CF3';

tab_key:=80;

username(tab_key):='QS_ES';

password(tab_key):='QS_ES';

hash(tab_key):='9A5F2D9F5D1A9EF4';

tab_key:=81;

username(tab_key):='QS_OS';

password(tab_key):='QS_OS';

hash(tab_key):='0EF5997DC2638A61';

tab_key:=82;

username(tab_key):='QS_WS';

password(tab_key):='QS_WS';

hash(tab_key):='0447F2F756B4F460';

tab_key:=83;

username(tab_key):='RE';

password(tab_key):='RE';

hash(tab_key):='933B9A9475E882A6';

tab_key:=84;

username(tab_key):='REPADMIN';

password(tab_key):='REPADMIN';

hash(tab_key):='915C93F34954F5F8';

tab_key:=85;

username(tab_key):='RMAIL';

password(tab_key):='RMAIL';

hash(tab_key):='DA4435BBF8CAE54C';

tab_key:=86;

username(tab_key):='RMAN';

password(tab_key):='RMAN';

hash(tab_key):='E7B5D92911C831E1';

tab_key:=87;

username(tab_key):='SAMPLE';

password(tab_key):='SAMPLE';

hash(tab_key):='E74B15A3F7A19CA8';

tab_key:=88;

username(tab_key):='SCOTT';

password(tab_key):='TIGER';

hash(tab_key):='F894844C34402B67';

tab_key:=89;

username(tab_key):='SDOS_ICSAP';

password(tab_key):='SDOS_ICSAP';

hash(tab_key):='C789210ACC24DA16';

tab_key:=90;

username(tab_key):='SECDEMO';

password(tab_key):='SECDEMO';

hash(tab_key):='009BBE8142502E10';

tab_key:=91;

username(tab_key):='SH';

password(tab_key):='SH';

hash(tab_key):='54B253CBBAAA8C48';

tab_key:=92;

username(tab_key):='SYS';

password(tab_key):='CHANGE_ON_INSTALL';

hash(tab_key):='D4C5016086B2DC6A';

tab_key:=93;

username(tab_key):='SYSADM';

password(tab_key):='SYSADM';

hash(tab_key):='BA3E855E93B5B9B0';

tab_key:=94;

username(tab_key):='SYSTEM';

password(tab_key):='MANAGER';

hash(tab_key):='D4DF7931AB130E37';

tab_key:=95;

username(tab_key):='TAHITI';

password(tab_key):='TAHITI';

hash(tab_key):='F339612C73D27861';

tab_key:=96;

username(tab_key):='TDOS_ICSAP';

password(tab_key):='TDOS_ICSAP';

hash(tab_key):='7C0900F751723768';

tab_key:=97;

username(tab_key):='TRACESVR';

password(tab_key):='TRACE';

hash(tab_key):='F9DA8977092B7B81';

tab_key:=98;

username(tab_key):='TSDEV';

password(tab_key):='TSDEV';

hash(tab_key):='29268859446F5A8C';

tab_key:=99;

username(tab_key):='TSUSER';

password(tab_key):='TSUSER';

hash(tab_key):='90C4F894E2972F08';

tab_key:=100;

username(tab_key):='USER0';

password(tab_key):='USER0';

hash(tab_key):='8A0760E2710AB0B4';

tab_key:=101;

username(tab_key):='USER1';

password(tab_key):='USER1';

hash(tab_key):='BBE7786A584F9103';

tab_key:=102;

username(tab_key):='USER2';

password(tab_key):='USER2';

hash(tab_key):='1718E5DBB8F89784';

tab_key:=103;

username(tab_key):='USER3';

password(tab_key):='USER3';

hash(tab_key):='94152F9F5B35B103';

tab_key:=104;

username(tab_key):='USER4';

password(tab_key):='USER4';

hash(tab_key):='2907B1BFA9DA5091';

tab_key:=105;

username(tab_key):='USER5';

password(tab_key):='USER5';

hash(tab_key):='6E97FCEA92BAA4CB';

tab_key:=106;

username(tab_key):='USER6';

password(tab_key):='USER6';

hash(tab_key):='F73E1A76B1E57F3D';

tab_key:=107;

username(tab_key):='USER7';

password(tab_key):='USER7';

hash(tab_key):='3E9C94488C1A3908';

tab_key:=108;

username(tab_key):='USER8';

password(tab_key):='USER8';

hash(tab_key):='D148049C2780B869';

tab_key:=109;

username(tab_key):='USER9';

password(tab_key):='USER9';

hash(tab_key):='0487AFEE55ECEE66';

tab_key:=110;

username(tab_key):='UTLBSTATU';

password(tab_key):='UTLESTAT';

hash(tab_key):='C42D1FA3231AB025';

tab_key:=111;

username(tab_key):='VIDEOUSER';

password(tab_key):='VIDEOUSER';

hash(tab_key):='29ECA1F239B0F7DF';

tab_key:=112;

username(tab_key):='VIF_DEVELOPER';

password(tab_key):='VIF_DEV_PWD';

hash(tab_key):='9A7DCB0C1D84C488';

tab_key:=113;

username(tab_key):='VIRUSER';

password(tab_key):='VIRUSER';

hash(tab_key):='404B03707BF5CEA3';

tab_key:=114;

username(tab_key):='VRR1';

password(tab_key):='VRR2';

hash(tab_key):='811C49394C921D66';

tab_key:=115;

username(tab_key):='WEBDB';

password(tab_key):='WEBDB';

hash(tab_key):='D4C4DCDD41B05A5D';

tab_key:=116;

username(tab_key):='WKSYS';

password(tab_key):='WKSYS';

hash(tab_key):='545E13456B7DDEA0';

-- --------------------------------------------------------------------

-- check all users in the database and see if defaults are set still

-- --------------------------------------------------------------------

dbms_output.put_line('Check default user passwords');

dbms_output.put_line('============================');

for lv_user in c_user loop

for i in 1..tab_key loop

if lv_user.username=username(i) then

if lv_user.password=hash(i) then

dbms_output.put_line('Default : '

||username(i)||' passwd is :'

||password(i));

exit;

end if;

end loop;

-- --------------------------------------------------------------------

-- check for some of the dangerous privileges

-- ALTER SYSTEM

-- --------------------------------------------------------------------

found:=0;

dbms_output.put_line('.');

dbms_output.put_line('Display Users that have the "ALTER SYSTEM" privilege');

dbms_output.put_line('====================================================');

for lv_sys_priv in c_sys_priv('ALTER SYSTEM') loop

dbms_output.put_line(lv_sys_priv.privilege||' :'||lv_sys_priv.grantee);

end loop;

-- --------------------------------------------------------------------

-- check for CREATE LIBRARY

-- --------------------------------------------------------------------

dbms_output.put_line('.');

dbms_output.put_line('Display Users that have the "CREATE LIBRARY" privilege');

dbms_output.put_line('======================================================'); for lv_sys_priv in c_sys_priv('CREATE%LIBRARY') loop

dbms_output.put_line(lv_sys_priv.privilege||' :'||lv_sys_priv.grantee);

end loop;

-- --------------------------------------------------------------------

-- check the location of utl_file_dir and ensure its not the same as

-- the trace directories

-- --------------------------------------------------------------------

found:=0;

dbms_output.put_line('.');

dbms_output.put_line('Dislay utl_file_dir');

dbms_output.put_line('===================');

open c_utl_cur;

loop

fetch c_utl_cur into lv_utl_cur;

if c_utl_cur%notfound then

if found=0 then

dbms_output.put_line('utl_file_dir is not set');

end if;

exit;

else

found:=1;

dbms_output.put_line('utl_file_dir is '||rtrim(lv_utl_cur.value));

end if;

end loop;

close c_utl_cur;

dbms_output.put_line('.');

dbms_output.put_line('Dislay destinations');

dbms_output.put_line('===================');

found:=0;

open c_trace;

loop

fetch c_trace into lv_trace;

if c_trace%notfound then

if found=0 then

dbms_output.put_line('no trace directories set');

end if;

exit;

else

found:=1;

dbms_output.put_line(rtrim(lv_trace.name)

||' is '||rtrim(lv_trace.value));

end if;

end loop;

close c_trace;

-- --------------------------------------------------------------------

-- check if the utl_file_dir clashes with any of the dest directions

-- --------------------------------------------------------------------

dbms_output.put_line('.');

dbms_output.put_line('Display any clash between utl_file_dir and destination direcories');

dbms_output.put_line('=================================================================');

found:=0;

open c_utl_trace;

loop

fetch c_utl_trace into lv_utl_trace;

if c_utl_trace%notfound then

if found=0 then

dbms_output.put_line('No apparent match between utl_file_dir and dest directories');

end if;

exit;

else

dbms_output.put_line(lv_utl_trace.name||' matches utl_file_dir');

end if;

end loop;

close c_utl_trace;

-- --------------------------------------------------------------------

-- check for users with the DBA privilege

-- --------------------------------------------------------------------

dbms_output.put_line('.');

dbms_output.put_line('Check for users with "DBA" privilege');

dbms_output.put_line('====================================');

for lv_dba in c_dba loop

dbms_output.put_line(lv_dba.grantee);

end loop;

-- --------------------------------------------------------------------

-- check out which users have ANY

-- --------------------------------------------------------------------

dbms_output.put_line('.');

dbms_output.put_line('Check for users with "ANY" privilege');

dbms_output.put_line('====================================');

for lv_sys_priv in c_sys_priv('%ANY%') loop

dbms_output.put_line(lv_sys_priv.privilege||' :'||lv_sys_priv.grantee);

end loop;

-- --------------------------------------------------------------------

-- check out users or roles that have "with admin"

-- --------------------------------------------------------------------

dbms_output.put_line('.');

dbms_output.put_line('Check for users or roles the have "with admin"');

dbms_output.put_line('==============================================');

for lv_admin in c_admin loop

dbms_output.put_line(lv_admin.priv||' :'||lv_admin.grantee);

end loop;

-- --------------------------------------------------------------------

-- check out which privileges have with with grant

-- --------------------------------------------------------------------

dbms_output.put_line('.');

dbms_output.put_line('Check for users and roles that have "grantable"');

dbms_output.put_line('===============================================');

for lv_grant in c_grant loop

dbms_output.put_line(lv_grant.privilege||' :'

||lv_grant.table_name||' :'||lv_grant.grantee);

end loop;

-- --------------------------------------------------------------------

-- check out external users

-- --------------------------------------------------------------------

dbms_output.put_line('.');

dbms_output.put_line('Display External Users');

dbms_output.put_line('======================');

for lv_ext in c_ext loop

dbms_output.put_line(lv_ext.username);

end loop;

-- --------------------------------------------------------------------

-- check out database links where there is a password set.

-- --------------------------------------------------------------------

dbms_output.put_line('.');

dbms_output.put_line('Display Database links where there is a password set');

dbms_output.put_line('====================================================');

for lv_links in c_links loop

dbms_output.put_line(lv_links.name||' :'||lv_links.host||' :'

||lv_links.userid||' :'||lv_links.password

||' :'||lv_links.authusr||' :'||lv_links.authpwd);

end loop;

end;

=======4=======================================================================================================

oracle@d2aseutsh018.ndc.local[openview]# vi rpt_user_audit.sql

rem Set up environment

set termout off

set pause off

set pages 5400 lines 80

set feedback off

set time off

rem ***************************************************************************

rem send output to a file

col dbname new_value n_dbname noprint

col rptnme new_value n_rptnme noprint

select name||'_'||to_char(sysdate,'YYMMDD') rptnme, name dbname

from v$database;

spool useraudit_&n_rptnme..txt

rem ***************************************************************************

rem Print overall heading for report

set heading off

prompt ########################################################################

prompt # Oracle Database Security Report #

prompt ########################################################################

prompt

prompt Instance Name:

select value from v$parameter where name='db_name'

prompt

prompt Date Of This Report:

Column today format a30

select to_char(sysdate,'dd Month YYYY HH24:MI') today from sys.dual;

set heading on

rem ***************************************************************************

rem System Privileges

prompt ########################################################################

prompt

prompt System Privileges

prompt

Column grantee format a25

Column privilege format a30

select * from sys.dba_sys_privs

order by grantee,privilege

prompt

rem ***************************************************************************

rem List of Users

column username format a15

column default_tablespace format a30

column temporary_tablespace format a30

prompt ########################################################################

prompt

prompt List of Users

prompt

select username,default_tablespace,temporary_tablespace

from sys.dba_users

order by username

prompt ########################################################################

prompt

prompt Recent database logon sessions

prompt

column osuser format a15

select distinct username, osuser, logon_time

from v$session

where username is not null

prompt

rem ***************************************************************************

rem Roles

prompt ########################################################################

prompt

prompt Roles

prompt

select * from sys.dba_roles

order by role

prompt

rem ***************************************************************************

rem Role Privileges

prompt ########################################################################

prompt

prompt Role Privileges

prompt

select * from sys.dba_role_privs

order by grantee,granted_role

prompt

rem Close out SQL*Plus script

spool off

rem exit

rem ***************************************************************************

=====5====================================================================================================================

oracle@d2aseutsh018.ndc.local[openview]# vi rpt_user_privs.sql

rem Set up environment

set termout off

set pause off

set pages 5400 lines 80

set feedback off

set time off

rem ***************************************************************************

rem send output to a file

col dbname new_value n_dbname noprint

col rptnme new_value n_rptnme noprint

select name||'_'||to_char(sysdate,'YYMMDD') rptnme, name dbname

from v$database;

spool userprivs_&n_rptnme..txt

rem ***************************************************************************

rem Print overall heading for report

set heading off

prompt ########################################################################

prompt # Oracle Database Security Report #

prompt ########################################################################

prompt

prompt Instance Name:

select value from v$parameter where name='db_name'

prompt

prompt Date Of This Report:

Column today format a30

select to_char(sysdate,'dd Month YYYY HH24:MI') today from sys.dual;

set heading on

rem ***************************************************************************

rem System Privileges

prompt ########################################################################

prompt

prompt System Privileges

prompt

Column grantee format a25

Column privilege format a30

select * from sys.dba_sys_privs

order by grantee,privilege

prompt

rem ***************************************************************************

rem Users

column username format a15

column default_tablespace format a30

column temporary_tablespace format a30

prompt ########################################################################

prompt

prompt Users

prompt

select username,default_tablespace,temporary_tablespace

from sys.dba_users

order by username

prompt

rem ***************************************************************************

rem Roles

prompt ########################################################################

prompt

prompt Roles

prompt

select * from sys.dba_roles

order by role

prompt

rem ***************************************************************************

rem Role Privileges

prompt ########################################################################

prompt

prompt Role Privileges

prompt

select * from sys.dba_role_privs

order by grantee,granted_role

prompt

rem ***************************************************************************

rem Table Privileges

set lines 85

column grantee format a25

column table_name format a30

column owner format a12

column privilege format a15

prompt ########################################################################

prompt

prompt Table Privileges

prompt

select grantee,table_name,owner,privilege

from sys.dba_tab_privs

where grantee not in ('SYS','SYSTEM','EXP_FULL_DATABASE')

order by grantee,table_name

prompt

rem ***************************************************************************

rem Close out SQL*Plus script

spool off

rem exit

rem ***************************************************************************

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

http://www.businessinsider.com/hpe-employees-shocked-and-relieved-about-enterprise-services-spinoff-2016-5

Thank you for your feedback |Recognition@hp

From: Gonzalez, Christopher D.
Sent: Friday, April 29, 2016 10:04 AM
To: Chando, Kenneth <kenneth.chando@hpe.com>
Cc: Kegley, Hank <hank.kegley@hpe.com>
Subject: RE: Final Clearance Notification

You have TOP SECRET eligibility and TOP SECRET access. The previous email listed SECRET.

From: Gonzalez, Christopher D.
Sent: Friday, April 29, 2016 9:54 AM
To: Chando, Kenneth <kenneth.chando@hpe.com>
Cc: Kegley, Hank <hank.kegley@hpe.com>
Subject: Final Clearance Notification

The HP Enterprise Services Industrial Security Office received notification from the Defense Security Service that you have been granted SECRET eligibility. Per the contract you are currently working on your access level is SECRET. All documentation in your record is up-to-date and no action is required at this time.

Please note that your _SSBI_investigation closed on 2016 04 22 , and your eligibility was granted on 2016 04 28 by DOD CAF. It is important that you keep this information for future clearance applications.

T3 level investigations should be submitted for a periodic re-investigation (PR) at the 9-3/4 year mark. SSBI level investigations should be submitted for a PR at the 4-3/4 year mark. Use the date the investigation closed to determine the time period for beginning the re-investigation process. It is your responsibility to notify the industrial security office of any changes in your status. This includes, contract change or any job related change, marital status, address/phone number, etc. so that we may report the most up to date information to the government.

Please contact the Industrial Security Office at industrialsecurity@hp.com if you have any questions.

Attached is a copy of an SF 312. Please give me a call at your earliest convenience so we can perform a Verbal Attestation. It should only take roughly 2 minutes to complete a Verbal Attestation.

*** Reminder if you are leaving the company, going on LOA (for more than 30 days), or no longer supporting a classified contract contact the industrialsecurity@hp.com mailbox for the required SECURITY DEBRIEFING DOCUMENTS. ***

V/R,
Christopher Gonzalez, AFSO
Industrial Security Office
HP Enterprise Services
13600 EDS Drive
A3S-C53
Herndon, VA 20171
Phone: 703-713-7212
Fax: 703-742-1757

__________________________________________________________________________
Visit HPES Industrial Security Office (on the HP network) for help with your
security needs. HPES Industrial Security Office
New Email for HPES Industrial Security: industrialsecurity@hpe.com

The information transmitted in this message is intended only for the person(s)
or entity to which it is addressed and may contain sensitive and/or privileged
material. Any review, retransmission, dissemination or other use of, or taking
of any action in reliance upon, this information by persons or entities other
than the intended recipient(s) is prohibited. If you received this in error,
please contact the sender and destroy any copies of this document.

Consulting is an employee-heavy kind of business and the division nearly doubled HP's headcount, from 172,000 to more than 311,000 in 2008.

From the get go, the unit had layoffs but as Enterprise Services revenues tanked, by 2012, HP began cutting deeper.

The company got rid of more than 55,000 people, and had plans to cut another 25,000 - 30,000 people.

On top of that, Whitman also said she was offshoring up to 60% of the unit's remaining jobs in order to lower costs and bring profit margins up to 9%.

HP Enterprise did other things to reduce headcount. Last year, it told thousands that they were to go for a contract labor company, doing their same jobs, typically for less pay and benefits. If they refused and quit they might not be entitled to severance. (Some HP employees staged a revolt and, surprisingly, won.)

All told, HP had been spending about $1 billion a year for the last seven years cutting jobs.

Employees shifting to the new company probably won't be spared layoffs.

Whitman warned that there will "cost synergies" of $1.5 billion to be had after the transaction closes in 2017 and that word almost always includes cutting jobs.

But the savings won't just come from layoffs. For instance, between the two companies they have 95 data centers. "Okay, we definitely do not need 95 data centers," Whitman says.

Good Day,

Following our conversation just earlier, I am writing to formally declare my resignation from HPE, effective today, 2-Jun-2016.

I came to HPE with the hope of making a great difference by leveraging knowledge, creativity, and innovation.

Unfortunately, the constraints of this position too severely put limits to those qualities that give me intrinsic job satisfaction and a sense of accomplishment.

I regret that I am letting down Ken Chando, Hassan Abdel, Bruce Franklin, and Abdalla Omer, in that I was never able to truly contribute.

I wish you all the very best success in your endeavors, both within HPE and in your personal lives.

I hope that you will be able to bring in someone with clearance to begin more immediately assisting the DBA Team with their work load.

Best,

Johnny R. Grimes

From: Grimes, Johnny Ralph
Sent: Tuesday, 17 May 2016 11:36 AM
To: Kegley, Hank <hank.kegley@hpe.com>
Cc: Hackney, Terry <terry.hackney@hpe.com>
Subject: HPE follow-up

Good Day,

I hope this message finds you in improving health. I’ve also included Terry herein while you are in recovery as I am not sure who will need to follow-up.

Please find attached letter regarding concerns/questions I have regarding current role and responsibilities. Of note, I have run this letter by Omer Abdalla on 4-May to gather his thoughts and incorporated slight revision following his feedback.

I have most enjoyed our conversations and meeting you. I wish you the very best, if you are ever in the need of work or looking for another opportunity, please contact me.

Wherever I may be, I will try to bring you in. My company contact: grimesj@broadsidesoftware.com

Best to you and your family,

Johnny

From: Grimes, Johnny Ralph
Sent: Thursday, 2 June 2016 3:46 PM
To: Hackney, Terry <terry.hackney@hpe.com>
Cc: Kegley, Hank <hank.kegley@hpe.com>; Abdel Hassan (abdel.e.hassan@hpe.com) <abdel.e.hassan@hpe.com>; 'Chando, Kenneth' <kenneth.chando@hpe.com>; Omer Abdalla (omer.abdalla@hpe.com) <omer.abdalla@hpe.com>; 'Franklin, Bruce' <bruce.franklin@hpe.com>; Omer Abdalla (omer.abdalla@hpe.com) <omer.abdalla@hpe.com>; Green, Jennifer (US Public Sector) <jenniferg@hpe.com>; Brown, Heather Bryant (ISO) <heather.b.brown@hpe.com>
Subject: RE: HPE follow-up

Good Day,

Following our conversation just earlier, I am writing to formally declare my resignation from HPE, effective today, 2-Jun-2016.

I came to HPE with the hope of making a great difference by leveraging knowledge, creativity, and innovation.

Unfortunately, the constraints of this position too severely put limits to those qualities that give me intrinsic job satisfaction and a sense of accomplishment.

I regret that I am letting down Ken Chando, Hassan Abdel, Bruce Franklin, and Abdalla Omer, in that I was never able to truly contribute.

I wish you all the very best success in your endeavors, both within HPE and in your personal lives.

I hope that you will be able to bring in someone with clearance to begin more immediately assisting the DBA Team with their work load.

Best,

Johnny R. Grimes

From: Grimes, Johnny Ralph
Sent: Tuesday, 17 May 2016 11:36 AM
To: Kegley, Hank <hank.kegley@hpe.com>
Cc: Hackney, Terry <terry.hackney@hpe.com>
Subject: HPE follow-up

Good Day,

I hope this message finds you in improving health. I’ve also included Terry herein while you are in recovery as I am not sure who will need to follow-up.

MSSQL SERVER

Questions from training

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

http://www.timezoneconverter.com/cgi-bin/tzc.tzc

Thank you for your feedback |Recognition@hp

From: VC-HRGS-AMS
Sent: Tuesday, April 12, 2016 11:52 AM
To: Haynes, Annmarie (TDLS) <annmarie.haynes@hpe.com>
Cc: Chando, Kenneth <kenneth.chando@hpe.com>
Subject: FW: Introduction to Microsoft Windows Containers connecting issues via MYROOM and Sab Cloud

Hi Annmarie,

Please assist the below learner.

Regards

Saumia

Hewlett Packard Enterprise

Event Management Team

VC-HRGS-AMS@hpe.com

From: Chando, Kenneth
Sent: Tuesday, April 12, 2016 9:04 PM
To: VC-HRGS-AMS <vc-hrgs-ams@hpe.com>
Subject: Introduction to Microsoft Windows Containers connecting issues via MYROOM and Sab Cloud

Hi VC team,

I’m trying to connect to this ongoing training “Introduction to Microsoft Windows Containers”

I’m currently connected in my both myRoom and Saba. Also, following the guide that was sent, I’m having issues connecting to the training via MyRoom or Saba cloud.

Please assist/direct me on how to connect.

This event will be held in MyRoom. Prior to the beginning of the event, ensure you or Install or Update to the latest version of MyRoom 10.4.0.0174: https://www.myroom.hpe.com/ . If you experience any difficulty with HP MyRoom, please call Technical Support at 1-888-351-4732 or 1-919-595-4243, http://www.myroom.hpe.com/Support .

If you need to cancel your enrollment, please see the Cancel Enrollment section below.

Declining the calendar appointment does not cancel your enrollment in Accelerating U.

Offering ID:

02008666

Course Title:

Introduction to Microsoft Windows Containers

Delivery Time Zones:

Pacific Time Zone

Sessions Details:

(Date, Start & End Time)

Date	Time and Time Zone
April 12, 2016	08:00 AM - 09:30 AM Pacific Time Zone

Time Zone Conversion:

Use the following URL to make the conversion from (USA PST / Europe CET / APJ Singapore Time) to your time zone.

Expectations

Expectations for successful class completion:

· Be on time and attend all class lecture

· Participate in face-to-face and/or phone-based virtual classes

· If you know that you are unable to fulfill class expectations please consider cancelling ahead of time to allow attendance by other learners

Participant MyRoom Keys and Dial-In Numbers:

To Install MyRoom, please follow the steps from the “Set up information” provided after this column. If you experience any difficulty installing MyRoom, please call Technical Support at 1-888-351-4732 or 1-919-595-4243, www.myroom.hpe.com/Support.

To attend your My Room event USE the following KEY:

MEPIIIMHEEV

Directions to use the MyRoom Key:

Either:

· Launch HP MyRoom client from your computer

o Sign in with your e-mail address and password

o Enter the HP MyRoom participant key provided above into the Key field at the bottom of your tray

o Press Enter on your keyboard

Or:

· Launch HP MyRoom client from your computer

o Click the Enter with key link

o Enter your first and last name in the User Name field

o Enter the participant key provided above into the Key field

o Click the Enter Room button

Note:

It is recommended to use the MyRoom audio functionality. A headset is a must to attend the trainings in MyRoom.

Attempting to connect and experiencing issues:

Close all applications not related to HP MyRoom, especially Outlook.

Note that certain applications are network-resource-heavy. Closing these will help to ensure a stable connection.

Close out of MyRoom completely and then re-open MyRoom.
Clear the IE cache and history.
Reboot, at minimum, one hour prior to connecting.

Your collaboration is critical to the success of your event. For more information please see your confirmation email from Accelerating U or your Outlook Calendar Appointment.

Setup Information:

HPE Employees:

SETUP INFORMATION:

Download your free account and read more about MyRoom (copy and paste URL below into browser):

https://myitsupport.ext.hpe.com/myITsupport/ITSArticle?ArticleNumber=000001564

Note: A headset is mandatory to attend the trainings in MyRoom

Test your set up: Go to https://www.myroom.hpe.com/helpfiles/MyRoom/mergedProjects/MyRoomPremium/new_hp_myroom/settings/audio.htmto select and test your audio settings

Help & Support is also available with valuable quick reference guides & much more

https://www.myroom.hpe.com/Support

TRAINING and DOCUMENTATION:

Virtual instructor-led sessions and WBT on HPU:

HP MyRoom Overview (Course Code 00940828): One hour; includes features and functions used for training and meetings; delivered in a lecture mode with questions submitted via the question manager.

HP MyRoom Features and Functions (Course Code: 00947560): two hours; includes demos of features and functions used for training and meetings.

Delivery Language:

English

VC Logistical Support (Same day of the offering):

Support for the same day of the offering:

For phone line problems or logistical issues such as invalid VC keys, insufficient number of seats booked, or missing scheduling information on the same day of the offering, please use the contact information below.

All countries other than the US, Canada and Puerto Rico should call the U.S. using AT&T access codes.

For problems on the day of the offering, contact our support lines provided below:

Location / Region	Support Lines
For US, Canada and Puerto Rico (AMS):	1-866-460-1090
EMEA & APJ:	1-800-582-8612 (accessed via the AT&T in-country access codes)
World-wide Toll Access (to be used as a backup number only if toll-free number is not available):	+1-770-343-0241 In order to use this world-wide toll free, an AT&T access code needs to be dialed first. The following link has all the countries with their respective access codes listed: http://www.business.att.com/bt/dial_guide.jsp

Hours of Operation: 23hours a day, 5 days a week - Global support

(No support during 5.30 AM – 6.30 AM IST)

Use the following URL to make the conversion from (USA PST / Europe CET / APJ Singapore Time) to your time zone. http://www.timezoneconverter.com/cgi-bin/tzc.tzc

Cancel Enrollment:

HPE Learner

Cancellation Policy –
If you cannot attend, please cancel your enrollment immediately but no later than 2 weeks before the class start date to make your seat available to another employee.

How to cancel your enrollment-

· Sign in to Accelerating U

· Click ME on the top navigation bar

· Click the course title and then click Drop

Region Generic Mailbox:

For queries on this training, please send email to VC-HRGS-AMS@hpe.com

Remarks:

Please login using your full name

Hello All,

Thank you all for your patience during these 4 days. I hope there was some beneficial information for each one in this workshop.

Few important articles for the topics discussed today are as follows:

Distributed Replay

· Installing and Configuring SQL Server 2012 Distributed Replay

· Performing a Distributed Replay with Multiple Clients using SQL Server 2012 Distributed Replay *****

· Introducing the SQL Server 2012 Distributed Replay Utility (en-US)

· Replay a Trace File (SQL Server Profiler)

· Configure Distributed Replay

· Ebook on Distributed Replay available for download from Microsoft website

PowerShell

· Hey, Scripting Guy! How Can I Use Profiles with Windows PowerShell?

· Signing PowerShell Scripts

· Convert URNs to SQL Server Provider Paths

Contained Databases

· Contained Databases

· Security Best Practices with Contained Databases

· Migrate to a Partially Contained Database

· SQL Server 2012: Sometimes Partial Is Preferable

The following is the link to the virtual labs for SQL 2014 Alwayson Failover cluster instance as well as availability group. All you would need is a MSDN subscription:

https://vlabs.holsystems.com/vlabs/technet?eng=VLabs&auth=none&src=vlabs&altadd=true&labid=12694

http://www.microsoft.com/en-us/server-cloud/support/learning-center/virtual-labs.aspx

Please shoot me an email if you have any questions or concerns related to the new features of SQL 2012. I will try to respond as soon as possible.

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Thursday, March 10, 2016 7:15 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Following are the important articles on topics that we discussed today:

AlwaysOn

· Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server) *****Important

· Interoperability and Coexistence with Other Database Engine Features

· Restrictions and limitations for using other features with AlwaysOn Availability Groups

· Active Secondaries: Backup on Secondary Replicas (AlwaysOn Availability Groups)

· Active Secondaries: Readable Secondary Replicas (AlwaysOn Availability Groups) *****Important

· Configure Read-Only Routing for an Availability Group (SQL Server)

· AlwaysOn: Making latest statistics available on Readable Secondary, Read-Only database and Database Snapshot

· Configure Backup on Availability Replicas (SQL Server)

· Transaction_log_Backup_details*****Important

SQL Server Failover Clusters

·Failover Cluster Cmdlets in Windows PowerShell Listed by Task Focus

·Understanding MS DTC Resources in Windows Server 2008 Failover Clusters

·How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008

·What does Cluster-Aware mean?

·SQL Server Multi-Subnet Clustering (SQL Server)

·View Cluster Quorum NodeWeight Settings

·Whitepaper on SQL Server 2012 AlwaysOn: Multisite Failover Cluster Instance *****

·View and Read Failover Cluster Instance Diagnostics Log

·AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using Failover Cluster Instances and Availability Groups

In addition to the above articles, here's a query to check the role of the Availability Replica on the current instance for a particular database, this could be used to schedule all jobs on a SQL Server environment and have them only run if they are in fact, the replica owner.

select role, role_desc

from sys.dm_hadr_availability_replica_states ars

join sys.dm_hadr_database_replica_states drs

on ars.group_id = drs.group_id

where ars.is_local = 1

and drs.is_local = 1

and drs.database_id = db_id('AdventureWorks')

Tomorrow we will start at the same time 10 am Central time and the topics for tomorrow are:

011_SQL_Server_2012_Features_for_Admins_Module_3_Lesson 11_PowerShell_and_WMI_Scripting

012_SQL_Server_2012_Features_for_Admins_Module_3_Lesson_12_Utilizing_Distributed_Replay

015_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 15_Contained_Databases

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Wednesday, March 9, 2016 7:52 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Following are the important articles on topics that we discussed today (these links are not there in the PowerPoint slides/notes):

· SQL Server Policy-Based Management Team Blog

· Part 1: Anatomy of SQL Server 2008 Resource Governor CPU Demo

· Part 2: Resource Governor CPU Demo on multiple CPUs

· Get Started with Microsoft SQL Server Data Tools

· FAQ: Microsoft SQL Server Data Tools

· Learn More About Microsoft SQL Server Data Tools

and here is the 31-days blog series on Extended Event from Jonathan Kehayias in which he talks about some interesting scenarios to use extended events (some of them listed below) – An XEvent A Day: 31 days of Extended Events. If you read one blog post from this series every day, you will become a master in Extended Events in just 31 days J. Some interesting post in this series

· Tracking Ghost Cleanup

· An XEvent a Day (15 of 31) – Tracking Ghost CleanupHow Many Checkpoints are Issued During a Full Backup?

Tomorrow we will start at the same time 10 am Central time and the topics for tomorrow are:

013_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 13_Failover_Clustering

014_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 14_AlwaysOn_Availability_Groups

015_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 15_Contained_Databases

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Tuesday, March 8, 2016 7:13 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Tomorrow we will start at 10 am Central time.

Following are the links that might be beneficial for the topics discussed during the session today –

· Breakthrough performance with in-memory technologies

· How Fast is Project Codenamed “Hekaton” – It’s ‘Wicked Fast’!

· How to reduce paging of buffer pool memory in the 64-bit version of SQL Server

· http://mssqlwiki.com/2013/04/22/max-server-memory-do-i-need-to-configure/******

SQL Server 2012 Licensing

· Features Supported by the Editions of SQL Server 2012

· SQL Server 2012 Licensing Value vs. Oracle Database ******

And some more that I usually share with my customers J

· Upgrade to a Different Edition of SQL Server 2012 (Setup)

· How to reduce paging of buffer pool memory in the 64-bit version of SQL Server

· Do I have to assign the Lock Pages in Memory privilege for Local System?

· Find Non-Buffer Pool Memory (MemToLeave) in "Private Bytes"

· Virtual Accounts and Managed Service Accounts in SQL Server 2012

· Managed Service Accounts Frequently Asked Questions (FAQ)

· PerfMon Objects, Counters, Thresholds, & Utilities for SQL Server

· Disk Partition Alignment Best Practices for SQL Server

· Microsoft® SQL Server 2012 Best Practices Analyzer

· Interoperability and Coexistence with Other Database Engine Features

The plan for tomorrow is to cover the following lessons:

Lesson 05_Installation_Techniques_Using_the_Command_Prompt

Lesson 06_Upgrade_and_Migration_Overview

Lesson_09_SQL_Server_Management_Studio_and_Developer_Tools

& Maybe Lesson 10_Extended_Events_Enhancements

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Monday, March 7, 2016 5:36 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Just a reminder, we start tomorrow at 10 am Central time. Below is the information to connect to the workshop.

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Monday, February 29, 2016 7:40 PM
Subject: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello Premier Customers,

You are registered for a Microsoft Remote Delivery starting Tuesday morning and this e-mail will explain the details. Please read this entire email as there are some action items for you to complete before Tuesday’s start to ensure a smooth delivery and positive educational experience.

This workshop is being delivered “remotely,” which means the instructors will be located at a different location than you; the content of the workshop will be hosted in the cloud and downloaded the first day of the workshop.

Americas Education Services Presents

Premier Remote Delivery – WorkshopPLUS - SQL Server 2012: Features for Administrators

March 8-11, 2016

10:00 AM Central Time

Presenter: Ankita Matai

How the Offering Works:The Premier Remote Delivery workshops are delivered via a web platform. The instructor provides a combination of PowerPoint, live demos, and Q&A to deliver a rich and effective learning experience.

Cloud Hosted Lab Environment

The lab environment for the workshop will be hosted on the internet at the following location:

· Lab Access: https://www.premier-education-services.com/EntryPoint

· Lab Code*: MDaXqpqW

*Please Test Connectivity as soon as possible, using the Connectivity Code highlighted above. To test your connection, please log-into the Premier Education Services website (www.Premier-Education-Services.com) and click Test Your Connection link in the Hosted Labs area of your Premier Entry Point (You’ll need a Microsoft account, formerly known as Windows Live). You can use any Microsoft account. Sign up for one at: http://signup.live.com

Meeting Information

Attendee Access:https://educationservices.eventbuilder.com/SQLSer2012FAMarch8

· This link contains the meeting access points for each day of the delivery.

· Attendees require the following in order to view the stream, which is covered in detail in the EventBuilder Streaming Preparation document attached. Attendees may also wish to provide their IT department with the EventBuilder Minimum Requirements document attached.

1. Supported browsers: Internet Explorer (10 or higher), Chrome, Firefox or Safari

2. Flash Player, which can be installed here

3. Working computer speakers

4. Broadband internet connection of 1 mbps per attendee

5. Access to video streaming via their network. Ports 80, 443 and 1935 must be open. This can be evaluated via the test page.

6. Webcast support: support@eventbuilder.com

1. Once you click the link ‘Attendee Access’ URL you will be directed to a landing page that lists all of the days of your workshop. Please find the correct day and click the “Join” button.

2. Click on the “Join” button and you will be asked to fill in a few fields with basic information (first name, last name, email, company).

If you need assistance, we are available to help via email. We will also be available 30 minutesbefore class starts on Tuesday to help troubleshoot any connectivity issues.

Understand the Logistics – It can be challenging to keep the class on-schedule in a remote setting. We will be adhering to start/end times pretty strictly for that reason. We plan to break for about 1 hour for lunch, which typically occurs at noon central time. We will also be including other 15 minutes breaks as we do with our in person workshops. It may be a good idea to bring lunch for the next three days. Please plan accordingly as there will not be a recording of this available after the workshop.

If you have difficulty testing your connectivity to the hosted lab, please contact me directly.

You will receive an email survey after the workshop – please take the time to fill that out so that we may know if we’ve satisfied your expectations. Enjoy the workshop!

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

Hello All,

Following are the important articles on topics that we discussed today:

AlwaysOn

· Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server) *****Important

· Restrictions and limitations for using other features with AlwaysOn Availability Groups

· Active Secondaries: Backup on Secondary Replicas (AlwaysOn Availability Groups)

· Active Secondaries: Readable Secondary Replicas (AlwaysOn Availability Groups) *****Important

· Configure Read-Only Routing for an Availability Group (SQL Server)

· AlwaysOn: Making latest statistics available on Readable Secondary, Read-Only database and Database Snapshot

· Configure Backup on Availability Replicas (SQL Server)

· Transaction_log_Backup_details*****Important

SQL Server Failover Clusters

·Failover Cluster Cmdlets in Windows PowerShell Listed by Task Focus

·Understanding MS DTC Resources in Windows Server 2008 Failover Clusters

·How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008

·What does Cluster-Aware mean?

·SQL Server Multi-Subnet Clustering (SQL Server)

·View Cluster Quorum NodeWeight Settings

·Whitepaper on SQL Server 2012 AlwaysOn: Multisite Failover Cluster Instance *****

·View and Read Failover Cluster Instance Diagnostics Log

·AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using Failover Cluster Instances and Availability Groups

select role, role_desc

from sys.dm_hadr_availability_replica_states ars

join sys.dm_hadr_database_replica_states drs

on ars.group_id = drs.group_id

where ars.is_local = 1

and drs.is_local = 1

and drs.database_id = db_id('AdventureWorks')

Tomorrow we will start at the same time 10 am Central time and the topics for tomorrow are:

011_SQL_Server_2012_Features_for_Admins_Module_3_Lesson 11_PowerShell_and_WMI_Scripting

012_SQL_Server_2012_Features_for_Admins_Module_3_Lesson_12_Utilizing_Distributed_Replay

015_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 15_Contained_Databases

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Wednesday, March 9, 2016 7:52 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Following are the important articles on topics that we discussed today (these links are not there in the PowerPoint slides/notes):

· SQL Server Policy-Based Management Team Blog

· Part 1: Anatomy of SQL Server 2008 Resource Governor CPU Demo

· Part 2: Resource Governor CPU Demo on multiple CPUs

· Get Started with Microsoft SQL Server Data Tools

· FAQ: Microsoft SQL Server Data Tools

· Learn More About Microsoft SQL Server Data Tools

· Tracking Ghost Cleanup

· An XEvent a Day (15 of 31) – Tracking Ghost CleanupHow Many Checkpoints are Issued During a Full Backup?

Tomorrow we will start at the same time 10 am Central time and the topics for tomorrow are:

013_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 13_Failover_Clustering

014_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 14_AlwaysOn_Availability_Groups

015_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 15_Contained_Databases

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Tuesday, March 8, 2016 7:13 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Tomorrow we will start at 10 am Central time.

Following are the links that might be beneficial for the topics discussed during the session today –

· Breakthrough performance with in-memory technologies

· How Fast is Project Codenamed “Hekaton” – It’s ‘Wicked Fast’!

· How to reduce paging of buffer pool memory in the 64-bit version of SQL Server

· http://mssqlwiki.com/2013/04/22/max-server-memory-do-i-need-to-configure/******

SQL Server 2012 Licensing

· Features Supported by the Editions of SQL Server 2012

· SQL Server 2012 Licensing Value vs. Oracle Database ******

And some more that I usually share with my customers J

· Upgrade to a Different Edition of SQL Server 2012 (Setup)

· How to reduce paging of buffer pool memory in the 64-bit version of SQL Server

· Do I have to assign the Lock Pages in Memory privilege for Local System?

· Find Non-Buffer Pool Memory (MemToLeave) in "Private Bytes"

· Virtual Accounts and Managed Service Accounts in SQL Server 2012

· Managed Service Accounts Frequently Asked Questions (FAQ)

· PerfMon Objects, Counters, Thresholds, & Utilities for SQL Server

· Disk Partition Alignment Best Practices for SQL Server

· Microsoft® SQL Server 2012 Best Practices Analyzer

· SQL Server Policy-Based Management Team Blog

The plan for tomorrow is to cover the following lessons:

Lesson 05_Installation_Techniques_Using_the_Command_Prompt

Lesson 06_Upgrade_and_Migration_Overview

Lesson_09_SQL_Server_Management_Studio_and_Developer_Tools

& Maybe Lesson 10_Extended_Events_Enhancements

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Monday, March 7, 2016 5:36 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Just a reminder, we start tomorrow at 10 am Central time. Below is the information to connect to the workshop.

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Monday, February 29, 2016 7:40 PM
Subject: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello Premier Customers,

Americas Education Services Presents

Premier Remote Delivery – WorkshopPLUS - SQL Server 2012: Features for Administrators

March 8-11, 2016

10:00 AM Central Time

Presenter: Ankita Matai

Cloud Hosted Lab Environment

The lab environment for the workshop will be hosted on the internet at the following location:

· Lab Access: https://www.premier-education-services.com/EntryPoint

· Lab Code*: MDaXqpqW

Meeting Information

Attendee Access:https://educationservices.eventbuilder.com/SQLSer2012FAMarch8

· This link contains the meeting access points for each day of the delivery.

7. Supported browsers: Internet Explorer (10 or higher), Chrome, Firefox or Safari

8. Flash Player, which can be installed here

9. Working computer speakers

10. Broadband internet connection of 1 mbps per attendee

11. Access to video streaming via their network. Ports 80, 443 and 1935 must be open. This can be evaluated via the test page.

12. Webcast support: support@eventbuilder.com

1. Once you click the link ‘Attendee Access’ URL you will be directed to a landing page that lists all of the days of your workshop. Please find the correct day and click the “Join” button.

2. Click on the “Join” button and you will be asked to fill in a few fields with basic information (first name, last name, email, company).

If you need assistance, we are available to help via email. We will also be available 30 minutesbefore class starts on Tuesday to help troubleshoot any connectivity issues.

If you have difficulty testing your connectivity to the hosted lab, please contact me directly.

You will receive an email survey after the workshop – please take the time to fill that out so that we may know if we’ve satisfied your expectations. Enjoy the workshop!

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

Hello All,

Following are the important articles on topics that we discussed today (these links are not there in the PowerPoint slides/notes):

· Part 1: Anatomy of SQL Server 2008 Resource Governor CPU Demo

· Part 2: Resource Governor CPU Demo on multiple CPUs

· Get Started with Microsoft SQL Server Data Tools

· FAQ: Microsoft SQL Server Data Tools

· Learn More About Microsoft SQL Server Data Tools

· Tracking Ghost Cleanup

· An XEvent a Day (15 of 31) – Tracking Ghost CleanupHow Many Checkpoints are Issued During a Full Backup?

Tomorrow we will start at the same time 10 am Central time and the topics for tomorrow are:

013_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 13_Failover_Clustering

014_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 14_AlwaysOn_Availability_Groups

015_SQL_Server_2012_Features_for_Admins_Module_4_Lesson 15_Contained_Databases

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Tuesday, March 8, 2016 7:13 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Tomorrow we will start at 10 am Central time.

Following are the links that might be beneficial for the topics discussed during the session today –

· Breakthrough performance with in-memory technologies

· How Fast is Project Codenamed “Hekaton” – It’s ‘Wicked Fast’!

· How to reduce paging of buffer pool memory in the 64-bit version of SQL Server

· http://mssqlwiki.com/2013/04/22/max-server-memory-do-i-need-to-configure/******

SQL Server 2012 Licensing

· Features Supported by the Editions of SQL Server 2012

· SQL Server 2012 Licensing Value vs. Oracle Database ******

And some more that I usually share with my customers J

· Upgrade to a Different Edition of SQL Server 2012 (Setup)

· How to reduce paging of buffer pool memory in the 64-bit version of SQL Server

· Do I have to assign the Lock Pages in Memory privilege for Local System?

· Find Non-Buffer Pool Memory (MemToLeave) in "Private Bytes"

· Virtual Accounts and Managed Service Accounts in SQL Server 2012

· Managed Service Accounts Frequently Asked Questions (FAQ)

· PerfMon Objects, Counters, Thresholds, & Utilities for SQL Server

· Disk Partition Alignment Best Practices for SQL Server

· Microsoft® SQL Server 2012 Best Practices Analyzer

· Breakthrough performance with in-memory technologies

The plan for tomorrow is to cover the following lessons:

Lesson 05_Installation_Techniques_Using_the_Command_Prompt

Lesson 06_Upgrade_and_Migration_Overview

Lesson_09_SQL_Server_Management_Studio_and_Developer_Tools

& Maybe Lesson 10_Extended_Events_Enhancements

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Monday, March 7, 2016 5:36 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Just a reminder, we start tomorrow at 10 am Central time. Below is the information to connect to the workshop.

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Monday, February 29, 2016 7:40 PM
Subject: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello Premier Customers,

Americas Education Services Presents

Premier Remote Delivery – WorkshopPLUS - SQL Server 2012: Features for Administrators

March 8-11, 2016

10:00 AM Central Time

Presenter: Ankita Matai

Cloud Hosted Lab Environment

The lab environment for the workshop will be hosted on the internet at the following location:

· Lab Access: https://www.premier-education-services.com/EntryPoint

· Lab Code*: MDaXqpqW

Meeting Information

Attendee Access:https://educationservices.eventbuilder.com/SQLSer2012FAMarch8

· This link contains the meeting access points for each day of the delivery.

13. Supported browsers: Internet Explorer (10 or higher), Chrome, Firefox or Safari

14. Flash Player, which can be installed here

15. Working computer speakers

16. Broadband internet connection of 1 mbps per attendee

17. Access to video streaming via their network. Ports 80, 443 and 1935 must be open. This can be evaluated via the test page.

18. Webcast support: support@eventbuilder.com

1. Once you click the link ‘Attendee Access’ URL you will be directed to a landing page that lists all of the days of your workshop. Please find the correct day and click the “Join” button.

2. Click on the “Join” button and you will be asked to fill in a few fields with basic information (first name, last name, email, company).

If you need assistance, we are available to help via email. We will also be available 30 minutesbefore class starts on Tuesday to help troubleshoot any connectivity issues.

If you have difficulty testing your connectivity to the hosted lab, please contact me directly.

You will receive an email survey after the workshop – please take the time to fill that out so that we may know if we’ve satisfied your expectations. Enjoy the workshop!

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

Hello All,

Tomorrow we will start at 10 am Central time.

Following are the links that might be beneficial for the topics discussed during the session today –

· How Fast is Project Codenamed “Hekaton” – It’s ‘Wicked Fast’!

· How to reduce paging of buffer pool memory in the 64-bit version of SQL Server

· http://mssqlwiki.com/2013/04/22/max-server-memory-do-i-need-to-configure/******

SQL Server 2012 Licensing

· Features Supported by the Editions of SQL Server 2012

· SQL Server 2012 Licensing Value vs. Oracle Database ******

And some more that I usually share with my customers J

· Upgrade to a Different Edition of SQL Server 2012 (Setup)

· How to reduce paging of buffer pool memory in the 64-bit version of SQL Server

· Do I have to assign the Lock Pages in Memory privilege for Local System?

· Find Non-Buffer Pool Memory (MemToLeave) in "Private Bytes"

· Virtual Accounts and Managed Service Accounts in SQL Server 2012

· Managed Service Accounts Frequently Asked Questions (FAQ)

· PerfMon Objects, Counters, Thresholds, & Utilities for SQL Server

· Disk Partition Alignment Best Practices for SQL Server

· Microsoft® SQL Server 2012 Best Practices Analyzer

The plan for tomorrow is to cover the following lessons:

Lesson 05_Installation_Techniques_Using_the_Command_Prompt

Lesson 06_Upgrade_and_Migration_Overview

Lesson_09_SQL_Server_Management_Studio_and_Developer_Tools

& Maybe Lesson 10_Extended_Events_Enhancements

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Monday, March 7, 2016 5:36 PM
Subject: RE: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello All,

Just a reminder, we start tomorrow at 10 am Central time. Below is the information to connect to the workshop.

Regards,

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

From: Ankita Matai
Sent: Monday, February 29, 2016 7:40 PM
Subject: WorkshopPlus - SQL 2012 Features for Administrator - March 8th-11th

Hello Premier Customers,

Americas Education Services Presents

Premier Remote Delivery – WorkshopPLUS - SQL Server 2012: Features for Administrators

March 8-11, 2016

10:00 AM Central Time

Presenter: Ankita Matai

Cloud Hosted Lab Environment

The lab environment for the workshop will be hosted on the internet at the following location:

· Lab Access: https://www.premier-education-services.com/EntryPoint

· Lab Code*: MDaXqpqW

Meeting Information

Attendee Access:https://educationservices.eventbuilder.com/SQLSer2012FAMarch8

· This link contains the meeting access points for each day of the delivery.

19. Supported browsers: Internet Explorer (10 or higher), Chrome, Firefox or Safari

20. Flash Player, which can be installed here

21. Working computer speakers

22. Broadband internet connection of 1 mbps per attendee

23. Access to video streaming via their network. Ports 80, 443 and 1935 must be open. This can be evaluated via the test page.

24. Webcast support: support@eventbuilder.com

1. Once you click the link ‘Attendee Access’ URL you will be directed to a landing page that lists all of the days of your workshop. Please find the correct day and click the “Join” button.

2. Click on the “Join” button and you will be asked to fill in a few fields with basic information (first name, last name, email, company).

If you need assistance, we are available to help via email. We will also be available 30 minutesbefore class starts on Tuesday to help troubleshoot any connectivity issues.

If you have difficulty testing your connectivity to the hosted lab, please contact me directly.

You will receive an email survey after the workshop – please take the time to fill that out so that we may know if we’ve satisfied your expectations. Enjoy the workshop!

Ankita Matai | Premier Field Engineer| SQL Server | Mobile (: 302-766-3268 | Iselin, NJ, USA

Please see the below guidance from the MDC Hardware Services Team.

ALCON,

RE: Data floor equipment

Another friendly reminder, when you have finished using crash carts, trash cans, work benches or tables and other portable work surfaces they are to be moved to the front of the data hall, (west wall). In B2 they should be on the south wall, but at the west end near the single door.

Crash carts are to be stowed neatly!

DO NOT LOCK THE WHEELS ON ANYTHING ON THE DATA FLOOR WHEN YOU ARE NOT USING IT, YOURSELF. Even then the necessity is questionable.

DO NOT remove the dongles from the monitor/USB cable bundle or remove any securing tie-wraps.

The crash carts are not configured exactly the same though we are working on relative standardization.

Report problems encountered to or request additional cables, etc. from the Hardware Services team if needed.

Be careful that documentation or media isn’t left in the data halls. Data security needs to be taken very seriously, so please take all documents and media with you when you leave the data hall.”

Your participation in helping keep these units neat, clean and maintained will not only help the next person, but will in turn help you out as well.

Regards,

@Michael W. Bradish - ITIL v3 Foundation Certified

Technology Consultant III/Hardware technician/U.S. Public Sector – ITO Delivery

Data Center Strategy and Services / Facilities Management / Hardware Services

DC2 Program, an ISO 20000:2011 Organization

Email michael.bradish@hpe.com hardwareguy@hpe.com

Cell 434 568-7164 | Office 434 374-3541

KJ4NSN

Thanks David!

Greatly appreciated.

The baby and mom are doing well. Will extend your regards.

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

From: Willette, David
Sent: Monday, November 09, 2015 9:57 AM
To: Kegley, Hank; Chando, Kenneth
Cc: Green, Jennifer (US Public Sector); DC2 DATABASE SUPPORT
Subject: Re: Congratulations On your new addition

Please accept my congratulations as well Kenneth!

David Willette

Data Center Delivery Manager / Deputy Program Manager
DHS-DC2 Program, An ISO 20000:2011 Organization
Hewlett Packard Enterprise

david.a.willette@hp.com
T +1 434 374 3564
M +1 434 265 0918
Hewlett Packard Enterprise
Mid-Atlantic Datacenter

------ Original message------

From: Kegley, Hank

Date: Mon, Nov 9, 2015 9:52 AM

To: Chando, Kenneth;

Cc: Willette, David;Green, Jennifer (US Public Sector);DC2 DATABASE SUPPORT;

Subject:Congratulations On your new addition

Kenneth Congratulations on the arrival of your daughter

HANK KEGLEY

SERVICE DELIVERY MANAGER

System Support (L2 UNIX/WINTEL/DATABASE)

US Public Sector (HOMELAND SECURITY)

DC2 Program, An ISO 20000:2011 Organization

Telephone + 1 919.424.5644

Lync +1 919.745.4151

Mobile +1 704 506 3281

FAX: 919.424.9858

Email Hank.kegley@hpe.com

2610 Wycliff Road, Raleigh, North Carolina 27607

Thank you for your feedback |Recognition@hp

Thank you, Ken for taking care of the lab databases

Omer

From: Chando, Kenneth
Sent: Wednesday, January 20, 2016 8:57 AM
To: DC2 DATABASE SUPPORT
Subject: Standalone 12c database can now be accessed successfully

Hi Team,

Standalone 12c database can now be accessed successfully. Did clean up used space on /u01 mount point from %100 down to 70%.See below:

See current status below. Database can now be accessed successfully.

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

ALEX DAVIS

I did the SQL commands below myself. Hopefully that’s it.

From: Davis, Alexander
Sent: Thursday, June 09, 2016 9:11 AM
To: DC2 DATABASE SUPPORT <dc2db@hpe.com>
Subject: RE: requesting help cleaning up the db on d2lseutsh049

Omer/Ken:

Support recommends running the following from the standalone db setup guide to make sure all the users and permissions are in place:

5. Create the Database User opsware_admin

Create the database user 'opsware_admin' with the following privileges.

SQL> create user opsware_admin identified by opsware_admin

default tablespace truth_data temporary tablespace temp

SA Oracle Setup for the Model Repository — Standalone Version 17

quota unlimited on truth_data;

SQL> grant alter session to opsware_admin with admin option;

SQL> grant create procedure to opsware_admin with admin option;

SQL> grant create public synonym to opsware_admin with admin option;

SQL> grant create sequence to opsware_admin with admin option;

SQL> grant create session to opsware_admin with admin option;

SQL> grant create table to opsware_admin with admin option;

SQL> grant create trigger to opsware_admin with admin option;

SQL> grant create type to opsware_admin with admin option;

SQL> grant create view to opsware_admin with admin option;

SQL> grant delete any table to opsware_admin with admin option;

SQL> grant drop public synonym to opsware_admin with admin option;

SQL> grant select any table to opsware_admin with admin option;

SQL> grant select_catalog_role to opsware_admin with admin option;

SQL> grant query rewrite to opsware_admin with admin option;

SQL> grant restricted session to opsware_admin with admin option;

SQL> grant execute on dbms_utility to opsware_admin with grant option;

SQL> grant analyze any to opsware_admin;

SQL> grant insert, update, delete, select on sys.aux_stats$ to opsware_admin;

SQL> grant gather_system_statistics to opsware_admin;

SQL> grant create job to opsware_admin with admin option;

SQL> grant create any directory to opsware_admin;

SQL> grant drop any directory to opsware_admin;

SQL> grant alter system to opsware_admin;

SQL> grant create role to opsware_admin;

SQL> grant create user to opsware_admin;

SQL> grant alter user to opsware_admin;

SQL> grant drop user to opsware_admin;

SQL> grant create profile to opsware_admin;

SQL> grant alter profile to opsware_admin;

Once we do this please re-run rerun.sql. Then I will try the model repository setup script again for the secondary core.

I think if we find we just need to start from scratch the db setup scripts are still in /u01/app/oracle/admin/truth/scripts/

From: Abdalla, Omer
Sent: Wednesday, June 08, 2016 4:37 PM
To: Davis, Alexander <alexander.davis@hpe.com>
Subject: RE: requesting help cleaning up the db on d2lseutsh049

From: Davis, Alexander
Sent: Wednesday, June 08, 2016 2:44 PM
To: DC2 DATABASE SUPPORT <dc2db@hpe.com>
Subject: requesting help cleaning up the db on d2lseutsh049
Importance: High

Could someone from the oracle side (preferably in Raleigh today) execute the following as oracle on d2lseutsh049:

(This is from a support case excerpt where they discussed how to fix the sort of situation I’m in on d2lseutsh049 – the software install is OK but the data in the tables is invalid)

Now we are assuming that there are some residue of the old installation and you just want to clean up the objects in step 3 and reinstall a different version of SA. This step just requires that you cleanup all the objects that were created in step 3.

-- Drop All the users

DROP USER AAA CASCADE;

DROP USER TRUTH CASCADE;

DROP USER LCREP CASCADE;

DROP USER GCADMIN CASCADE;

DROP USER AAA_USER CASCADE;

DROP USER SPIN CASCADE;

DROP USER TWIST CASCADE;

DROP USER OPSWARE_PUBLIC_VIEWS CASCADE;

DROP USER VAULT CASCADE;

-- Drop all the Roles

DROP ROLE DATA_OWNER;

DROP ROLE DATA_USER;

DROP ROLE TRUTH_MOD;

DROP ROLE TRUTH_RO;

DROP ROLE TRUTH_API;

DROP ROLE LCREP_RO;

DROP ROLE LCREP_MOD;

DROP ROLE AAA_ADMIN;

DROP ROLE AAA_READER;

DROP ROLE AAA_WRITER;

DROP ROLE AAA_API;

DROP ROLE GCADMIN_ROLE;

-- Drop the Profile

DROP PROFILE OPSWARE_PUBLIC_VIEWS_PRF;

-- Drop all the public Synonyms

Run the following query to generate the list of synonyms to drop. This will give a bunch of delete statements ( if there are any synonyms left undeleted).

Run all the individual deletes that the select creates.

SELECT 'DROP PUBLIC SYNONYM "' || synonym_name || '";'

FROM SYS.dba_synonyms

WHERE owner = 'PUBLIC'

AND table_owner IN ('AAA', 'TRUTH', 'LCREP', 'GCADMIN', 'AAA_USER', 'SPIN', 'TWIST', 'OPSWARE_PUBLIC_VIEWS', 'VAULT');

Hi Omer,

The 049 server rmanbackup script was point to the IWMSD ORACLE_SID instead of truth and it’s OH was still 11.2.0

I had to modify script (rmanbackup_truth.sh) so that ORACLE_SID=truth and $ORACLE_HOME=12.1.0

Also, the database was in NOARCHIVELOG mode. Had to put it in Archivelog mode and tested backup and it was successful on 049.

Here is the dbora file for 049 server. It’s pointing to 12.1.0 OH: vi /etc/init.d/dbora

Old rmanbackup script

032 server =>no oradata, backup nor truth directory exist. The backup script has oradata and truth directories as part of its backup path

For rman_disk_backup.sh

For rmanbackup.sh =>Has IWMSD as its SID

On 032 server, there seems to have been deleted the oradata/backup/truth directory and the backup script is pointing this this location.

Did try to recreate these directories but got prompted to login with my oracle password. Did try our regular oracle password and it didn’t take it. I also tried Password1 to no avail. See:

Also, I couldn’t view the dbora script in /etc/init.d since couldn’t sudo to root for password reasons. See new modified rmanbackup script:

032 is in archvielog mode. Once the oradata, backup and truth directories are recreated, rmanbackup_truth.sh should run successfully.

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134

Thank you for your feedback |Recognition@hp

Hi Alex,

From the database perspective, there seems to be no issue of concern. I can login to it and it’s open.

Also checking on the size of the tablespaces and data files, there isn’t any discrepancy. See below:

SQL> @sh_tsdf.sql

June 6, 2016 Datafiles used by TRUTH database

===================================

Size Used Aut

File Name Tablespace (Mb) (in Mb) Used % Xtn Status

------------------------------------------------------- --------------- ---------- ---------- ------- --- ----------

/u02/oradata/truth/aaa_data02.dbf AAA_DATA 32.00 9.50 29.69 YES ONLINE

/u03/oradata/truth/aaa_data01.dbf AAA_DATA 32.00 4.00 12.50 YES ONLINE

/u04/oradata/truth/aaa_indx01.dbf AAA_INDX 32.00 6.13 19.14 YES ONLINE

/u03/oradata/truth/aaa_indx02.dbf AAA_INDX 32.00 16.00 50.00 YES ONLINE

/u03/oradata/truth/audit_data01.dbf AUDIT_DATA 32.00 2.94 9.18 YES ONLINE

/u02/oradata/truth/audit_indx01.dbf AUDIT_INDX 32.00 3.50 10.94 YES ONLINE

/u04/oradata/truth/lcrep_data01.dbf LCREP_DATA 261.00 178.31 68.32 YES ONLINE

/u03/oradata/truth/lcrep_data02.dbf LCREP_DATA 5.00 5.00 100.00 YES ONLINE

/u02/oradata/truth/lcrep_indx01.dbf LCREP_INDX 133.00 49.00 36.84 YES ONLINE

/u04/oradata/truth/lcrep_indx02.dbf LCREP_INDX 133.00 132.44 99.58 YES ONLINE

/u04/oradata/truth/strg_data01.dbf STRG_DATA 32.00 7.13 22.27 YES ONLINE

/u02/oradata/truth/strg_data02.dbf STRG_DATA 5.00 5.00 100.00 YES ONLINE

/u03/oradata/truth/strg_indx02.dbf STRG_INDX 5.00 5.00 100.00 YES ONLINE

/u02/oradata/truth/strg_indx01.dbf STRG_INDX 32.00 14.13 44.14 YES ONLINE

/u04/oradata/truth/sysaux01.dbf SYSAUX 1,060.00 935.81 88.28 YES ONLINE

/u04/oradata/truth/system01.dbf SYSTEM 726.00 663.94 91.45 YES SYSTEM

/u04/oradata/truth/temp01.dbf TEMP 128.00 128.00 100.00 YES ONLINE

/u03/oradata/truth/temp02.dbf TEMP 160.00 74.00 46.25 YES ONLINE

/u04/oradata/truth/truth_data02.dbf TRUTH_DATA 4,000.00 3,999.94 100.00 YES ONLINE

/u02/oradata/truth/truth_data01.dbf TRUTH_DATA 4,000.00 4,000.00 100.00 YES ONLINE

/u02/oradata/truth/truth_data03.dbf TRUTH_DATA 20,480.00 1,220.00 5.96 YES ONLINE

/u02/oradata/truth/truth_indx02.dbf TRUTH_INDX 645.00 636.00 98.60 YES ONLINE

/u03/oradata/truth/truth_indx01.dbf TRUTH_INDX 517.00 442.31 85.55 YES ONLINE

/u02/oradata/truth/undo02.dbf UNDO 389.00 23.69 6.09 YES ONLINE

/u04/oradata/truth/undo01.dbf UNDO 153.00 26.63 17.40 YES ONLINE

June 6, 2016 Tablespace used by db_name database

===================================

Initial Next

Extent Extent Total Size Used Free Extent

Name in (KB) in (KB) (in Mb) (in Mb) (in Mb) Used % Type Management Status

--------------- ------- ------- ---------- ---------- ---------- ------- --------- ---------- --------

AAA_INDX 64 64.00 22.13 41.88 34.57 PERMANENT LOCAL ONLINE

AUDIT_DATA 64 32.00 2.94 29.06 9.18 PERMANENT LOCAL ONLINE

STRG_DATA 64 37.00 12.13 24.88 32.77 PERMANENT LOCAL ONLINE

SYSAUX 64 1,060.00 935.81 124.19 88.28 PERMANENT LOCAL ONLINE

LCREP_DATA 64 266.00 183.31 82.69 68.91 PERMANENT LOCAL ONLINE

AUDIT_INDX 64 32.00 3.50 28.50 10.94 PERMANENT LOCAL ONLINE

STRG_INDX 64 37.00 19.13 17.88 51.69 PERMANENT LOCAL ONLINE

SYSTEM 64 726.00 663.94 62.06 91.45 PERMANENT LOCAL ONLINE

AAA_DATA 64 64.00 13.50 50.50 21.09 PERMANENT LOCAL ONLINE

TRUTH_DATA 64 28,480.00 9,219.94 19,260.06 32.37 PERMANENT LOCAL ONLINE

TRUTH_INDX 64 1,162.00 1,078.31 83.69 92.80 PERMANENT LOCAL ONLINE

UNDO 64 542.00 50.31 491.69 9.28 UNDO LOCAL ONLINE

LCREP_INDX 64 266.00 181.44 84.56 68.21 PERMANENT LOCAL ONLINE

TEMP 1,024 1,024 288.00 202.00 86.00 70.14 TEMPORARY LOCAL ONLINE

Redo Log Files

GROUP# Status MEMBER Megabytes

------- ---------- ------------------------------------------------------- ---------

1 CURRENT /u02/oradata/truth/redo1a.log 100

2 INACTIVE /u02/oradata/truth/redo2a.log 100

3 INACTIVE /u02/oradata/truth/redo3a.log 100

Control Files

Status NAME IS_ BLOCK_SIZE FILE_SIZE_BLKS CON_ID

---------- ------------------------------------------------------------ --- ---------- -------------- ----------

/u04/oradata/truth/control01.ctl NO 16384 1236 0

/u02/oradata/truth/control02.ctl NO 16384 1236 0

/u03/oradata/truth/control03.ctl NO 16384 1236 0

SQL>

Best,

Ken Chando

( Office Phone: (919) 424-5394

( Cell Phone: (434) 265-4134