Wednesday, December 3, 2008
Monday, November 3, 2008
Sunday, October 26, 2008
The HP Oracle Database Machine is primitive, slow, expensive, closed, power-hungry, cannot handle advanced analytics and requires significant management overhead.
But other than that, it’s not a bad start for Oracle!
There are some others making similar noise such as Chuck Hollis, VP -- Global Marketing CTO @ EMC Corporation. In a recent post he highlights a disagreement with Kevin Closson, Oracle storage guru and one, if not THE one, behind the HP Oracle Database Machine. See:
Saturday, October 25, 2008
In my businesses, I have always tried to pay in the dead center of the curve. Fifty percent of the companies pay better, and the others pay worse. I then try to provide a work environment that is respectful, challenging and fun.
In this market I think retention of good DBAs with that philosophy would still be difficult. Good DBAs can easily move further up the curve and still find a work environment that is respectful, challenging and fun. As he says, we all have families to feed, super to put away and over valued property to pay off or rent.
I couldn't agree more with this bit though - Lesson 5:
Stress is your biggest enemy. The world of the DBA is an incredibly stressful one and it is even worse in smaller organizations. If you have only one DBA, he or she knows that they alone have to keep the database up and running, or the business will stop running. This causes the Atlas Syndrome, named after the Greek myth of the Titan condemned by Zeus to hold up the heavens on his shoulders.
Providing adequate staffing and opportunities for mentoring can help your DBAs reduce the stress and burden. Companies can also augment their in-house DBA staff by contracting with a remote DBA firm, a new breed of vendor offering database expertise and support. The remote DBA firms, staffed with seasoned database experts, can even offer your in-house DBA mentoring, on-the-job training, and critical support.
Ahem, cough, self endorsement here. I work for Mark Gurry & Associates, an excellent remote DBA and on-site DBA services firm. The company only hires top DBAs (another self endorsement) SO if you are reading this and thinking you would like to take some peak stress off your DBA, or you are a DBA but would like some help now and then, give us a call.
MGA's site: http://www.mga.com
Monday, October 20, 2008
Looks like a cool tool. I'm going to give it a try. It's free, what harm can it do!
Address : http://tiny.cc/iXvMO
Wikipedia - What is Data Profiling?
Friday, September 5, 2008
Thursday, September 4, 2008
Friday, May 9, 2008
MOF version 3 described itself as being based on ITIL foundations and ITIL complaint. MOF version 3 I thought was very practical and I am hoping version 4 builds on that. MOF version 4 at first look seemes to be more generic. I still have to have a good read of all of the docs so I can't make an assesment yet.
MOF 4.0 is available at http://www.microsoft.com/mof and the MOF Community is at http://forums.technet.microsoft.com/en/MOF4/threads.
Pinching a bit from the MOF 4 FAQ:
How is MOF different from ITIL?
There are many similarities between MOF and ITIL. Both help IT organizations achieve reliable and cost-effective IT services; each uses the entire IT service lifecycle as the context for work activities. ITIL v3 is a vast compendium of information that addresses the breadth of IT activities by providing considerable detail in a number of areas. ITIL content consists of more than 1300 pages of concepts and models that address how IT organizations can provide valued services.
Similarly, MOF 4.0 contains core IT service management guidance, but takes a more streamlined approach to meet the needs of the overburdened IT professional. MOF 4.0 presents fundamental IT processes and their associated activities in an easy-to-grasp table format. And because busy IT professionals still have to implement, execute, follow or report IT policies and navigate risks every day, MOF 4.0 includes policy creation in the Plan Phase as well as support for IT governance, risk management, and compliance throughout the entire IT service lifecycle. Risk management and internal controls provide a coherent focus throughout the lifecycle and demonstrate the interconnectedness of all IT activities.
Microsoft Operations Framework (MOF) 4.0 is contained in a set of 23 documents.
Don Lemmex, MOF Program Manager describes in the MOF forums the differences between 3.0 and 4.0. as:
- The biggest difference is that 4.0 is that we have established a complete lifecycle for IT services. Now the IT organization and the business have a map for making decisions, the kinds of activities involved in providing IT services, and when the activities should happen.
- MSF is now integrated into the overall IT lifecycle to make a deeper relationship between development and operations.
- The material is much more streamlined and focuses on essential concepts. We wanted to give the IT professional enough context to understand what is involved right away, and not force them to immerse themselves in an entire body of knowledge before applying it to their situation.
- Governance, risk management, policy and compliance are new in 4.0 in recognition of their critical importance to successful IT services.
- The Team Model in MOF 3.0 is now a Team SMF in MOF 4.0 and provides a much improved way to consider roles and accountabilities throughout the lifecycle.
- The community for MOF is even more important for 4.0 than it was in 3.0, since much of the “making it real in my situation” will take place here on these forums. This is the place to look for and contribute adaptable, pragmatic examples that show “this is what I did, and it worked really well for us.”
So the goal of MOF 4.0 is practical guidance that provides the right concepts and a community that constantly develops and extends the application of these concepts through discussion, examples, and job aids.
Monday, April 28, 2008
- Windows Server for Oracle Database Administrators (DBAs)
- Real Application Clusters (RAC)Real Application Clusters (RAC)
- Performance and MonitoringPerformance and Monitoring
- Storage and BackupStorage and Backup
Technorati Tags: oracle, windows, rac, microsoft, bestpractice
Friday, March 28, 2008
I have had the joy of working with SQL Server recently, and I must admit it is very intuitive to manage, and SQL Server patches are just like any other Windows Microsoft patch.
Computerworld - Database expert: Oracle behind Microsoft on patch management
Oracle needs to improve patch management, an area where it's currently lagging five years behind Microsoft, according to database expert Karel Miko at Czech consultancy DCIT.
Thursday, March 20, 2008
I especially like MOF because you don't have to pay thousands of British Pounds for the documentation - Microsoft puts it online for free. Rock on Microsoft! Vista is a dog, but you are making up for it.
Much is applicable to the implementation of ITIL in a database support environment.
Version 3 is now in Beta - you can download and look at the docs here:
This Beta includes, amongst others, these documents:
· Business/IT Alignment SMF
· Change and Configuration SMF
· Customer Service SMF
· Financial Management SMF
· Problem Management SMF
· Design and Deliver Phase Overview
· Operate and Support Phase Overview
· Plan and Optimize Phase Overview
· Build SMF
· Deploy SMF
· Envision SMF
· Governance, Risk, and Compliance SMF
· Operations Management SMF
· Policy Management SMF
· Project Plan SMF
· Reliability Management SMF
· Service Monitoring and Control SMF
· Stabilize SMFCurrent (Version 2) MOF:
Tuesday, January 29, 2008
This is not an all-inclusive installation guide – Oracle already has written that
Oracle® Database Installation Guide 10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit) HTML
Oracle® Database Installation Guide 10g Release 2 (10.2) for Solaris Operating System (x86) HTML
Oracle® Database Installation Guide 10g Release 2 (10.2) for Solaris Operating System (x86-64) HTML
Rather this is to supplement Chapter 2, Preinstallation Tasks. Sections 2.54 – 2.6 inclusive. Oracle forgot to add, and continues to forget, the details on creating a project for Oracle and configuring resource controls for that project.
So, picking up from where you create the Oracle Inventory group, oinstall, and the database administrator group, dba. ( # groupadd oinstall # groupadd dba):
1. Configure Kernel Parameters and Resource Controls
From the Oracle installation guide it is not clear which kernel parameters are supposed to use the new Solaris 10 resource control facility, and those which are to use the the /etc/system file.
The following table is ripped from the 10.2 installation guide and as it says in the doco, the kernel parameter and shell limit values shown in the following section are recommended values only.
For production database systems, Oracle recommends that you tune these values to optimize the performance of the system.
Refer to your operating system documentation for more information about tuning kernel parameters blah blah blah.
The table contains the four resource controls that replace the old entries in the /etc/system file for a specific kernel parameter. Note that the /etc/system file is still used for the parameters listed with an ‘NA’ in the Resource Control Column.
| || |
| || |
| || |
| || |
I’ll ignore the kernel parameters in /etc/system – that’s documented already. Let’s take a look at the resource control settings instead. Much more interesting.
Before we start setting resource values, we first need to create a project for the Oracle installation:
1.1. Create the group.dba project for Oracle
# projadd group.dba<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
You should now see the project listed by the projects command and in /etc/project
bash-3.00# projects -l group.dba
projid : 100
users : (none)
groups : (none)
bash-3.00# cat /etc/project
Assuming all looks good, then proceed…
1.2. Configure group.dba project Resource Controls
projmod -sK "project.max-shm-memory=(privileged,2G,deny)" group.dba
projmod -sK "project.max-sem-ids=(privileged,100,deny)" group.dba
projmod -sK "project.max-shm-ids=(privileged,100,deny)" group.dba
projmod -sK "project.max-sem-nsems=(privileged,256,deny)" group.dba
Just to check (for fun):
bash-3.00# projects -l group.dba
projid : 100
users : (none)
groups : (none)
BTW, don’t use the prctl command to change the values (as shown in part of the installation guide) as the changed parameters do not persist after a system restart (as it says later in the installation guide after you have already followed their example and used prctl). Use projmod
1.3. Create, or update oracle user with default project group.dba
1.3.1. Create the Oracle user account, oracle, group.dba as default project
# useradd -g oinstall -G dba -m -d /export/home0/oracle -s /bin/bash -K project=group.dba oracle
# passwd -r files oracle
What’s with this –K value? From the sun man page doco:
Replace existing or add to a user's key=value pair attributes. Multiple -K options can be used to replace or add multiple key=value pairs. The generic -K option with the appropriate key can be used instead of the specific implied key options (-A, -P, -R, -p). See user_attr(4) for a list of valid key=value pairs. Values for these keys are usually found in man pages or other sources related to those keys. For example, see project(4) for guidance on values for the project key. Use the command ppriv(1) with the -v and -l options for a list of values for the keys defaultpriv and limitpriv.
Keys must not be repeated. Specifying a key= without a value removes an existing key=value pair.
The type key must be specified only without a value or with the role value. Specifying the type key without a value leaves the account as a normal user, with the role value changing from a normal user to a role user. As a role account, no roles (-R or roles=value) can be present.
See user_attr(4) for a list of valid key=value pairs
1.3.2. Update an existing oracle user default project to group.dba
There is an algorithm Solaris uses to determine the default project:
Determining a User's Default Project
To log in to the system, a user must be assigned a default project. A user is automatically a member of that default project, even if the user is not in the user or group list specified in that project.
Because each process on the system possesses project membership, an algorithm to assign a default project to the login or other initial process is necessary.
The algorithm is documented in the man page getprojent(3C).
The system follows ordered steps to determine the default project. If no default project is found, the user's login, or request to start a process, is denied.
The system sequentially follows these steps to determine a user's default project:
1. If the user has an entry with a project attribute defined in the /etc/user_attr extended user attributes database, then the value of the project attribute is the default project. See the user_attr(4) man page.
2. If a project with the name user.user-id is present in the project database, then that project is the default project. See the project(4) man page for more information.
3. If a project with the name group.group-name is present in the project database, where group-name is the name of the default group for the user, as specified in the passwd file, then that project is the default project. For information on the passwd file, see the passwd(4) man page.
4. If the special project default is present in the project database, then that project is the default project.
If you have already created the Oracle user you may find that while oracle is a member of the project, it’s default project is not group.dba.
You can use the usermod command to assign Oracle to the project.
# usermod -K project=group.dba oracle
You should now see in the /etc/user_attr file an entry for Oracle.
bash-3.00# cat /etc/user_attr
# Copyright 2007 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# execution attributes for profiles. see user_attr(4)
#ident "@(#)user_attr 1.1 07/01/31 SMI"
root::::auths=solaris.*,solaris.grant;profiles=Web Console Management,All;lock_after_retries=no
oracle::::type=normal;project=group.dba<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Oracle’s default project according to the default project algorithm should now be group.dba
bash-3.00# su - oracle
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
-bash-3.00$ id -p
uid=101(oracle) gid=102(oinstall) projid=100(group.dba)
2. Final Note and References
That should be enough to get you going – you can continue on with the Oracle installation guide 2.7 Identifying Required Software Directories.
For further details see Solaris 10 Reference Manual Collection,
man pages section 5: Standards, Environments, and Macros, resource_controls(5)
For other values that can be assigned to a project, see:
project(4) and man pages section 5: Standards, Environments, and Macros: resource_controls(5)
Solaris Containers-Resource Management and Solaris Zones: "Setting Resource Controls"
Solaris Containers-Resource Management and Solaris Zones, "Projects and Tasks (Overview)"
Details on the /etc/project file:
man pages section 4: File Formats: project(4)
The commands that are shown in the following table provide the primary administrative interface to the project and task facilities.
Man Page Reference
Displays project memberships for users. Lists projects from project database. Prints information on given projects. If no project names are supplied, information is displayed for all projects. Use the projects command with the -l option to print verbose output.
Executes the user's default shell or specified command, placing the execution command in a new task that is owned by the specified project. newtask can also be used to change the task and the project binding for a running process. Use with the -F option to create a finalized task.
Updates information in the password files. Use with the -K key=value option to add to user attributes or replace user attributes in local files.
Adds a new project entry to the /etc/project file. The projadd command creates a project entry only on the local system. projadd cannot change information that is supplied by the network naming service. Can be used to edit project files other than the default file, /etc/project. Provides syntax checking for project file. Validates and edits project attributes. Supports scaled values.
Modifies information for a project on the local system. projmod cannot change information that is supplied by the network naming service. However, the command does verify the uniqueness of the project name and project ID against the external naming service. Can be used to edit project files other than the default file, /etc/project. Provides syntax checking for project file. Validates and edits project attributes. Can be used to add a new attribute, add values to an attribute, or remove an attribute. Supports scaled values.
Deletes a project from the local system. projdel cannot change information that is supplied by the network naming service.
Adds default project definitions to the local files. Use with the -K key=value option to add or replace user attributes.
Deletes a user's account from the local file.
Modifies a user's login information on the system. Use with the -K key=value option to add or replace user attributes.
Friday, January 18, 2008
With the DBMS_UTILITY.DB_VERSION procedure, which returns database version information.
This question caused me a bit of grief.
I had been writing a procedure to drop a users objects, so that developers could just clean out everything owned by a user without doing DROP USER and CREATE USER. After all, who wants to give developers the DROP USER privilege? Anyway, after spending a while sidetracked with SYS_CONTEXT function and the USERENV context, which would seem to be the logical place to find the database version detail, I eventually stumbled on to DBMS_UTILITY.DB_VERSION.
The following simple example program in PL/SQL demonstrates how to get the database version using PL/SQL.
using DBMS_UTILITY.DB_VERSION shows how the version and compatibility can be found.
SET SERVEROUTPUT ONDECLARE
DBMS_UTILITY.db_version (version => l_version,
compatibility => l_compatibility);
DBMS_OUTPUT.put_line('Version: ' || l_version || ' Compatibility: ' || l_compatibility);
anonymous block completed
Version: 126.96.36.199.0 Compatibility: 8.1.7
Wednesday, January 9, 2008
By default Oracle installs all windows products using a local administrator account. Any Oracle services are setup to run as LOCAL SYSTEM, and all path entries are added to the SYSTEM PATH. This means that the last Oracle product that gets installed is first in the system PATH.
You can change the order the homes appear in the path, and if some homes are even in the path by manually running the Oracle Installer after the last installation, and using the path options in the Installed Products section.
This is fine for a single Oracle home, but completely HOPELESS in a multi-home environment.
The Oracle binaries in different homes, and services, should run as different windows users – each home should have its own user, each with local Administrator privilege.
Each user then has the PATH (and possibly other environment variables like JRE_HOME or PERL5LIB) crafted specifically for the product in that home.
Services that are based in that home should run as that Oracle Home user.
Basically, treat the products as if they are running in a UNIX environment J
There are numerous benefits such as
1. Products using the correct support libraries, java, perl
2. LOCAL SYSTEM does not have certain network privileges, which prevents Oracle from using UNC path names. Running as an OS user allows RMAN and other processes to use UNC path names to connect to file systems on other servers
So, after installing a product, remove the oracle entries from the SYSTEM PATH, and add them to the USER PATH for the OS user that has been created to run the products in that Oracle Home.
The only variable that may make sense to leave in the system path is invPtr which point to the Oracle Installer inventory location.
With a shared inventory, you should use the latest version of the installer installed on the server. Of course you could go one step further and run multiple product inventories, and add invPtr as user-level environment variable, with invPtr pointing to the appropriate inventory.
When running services with local user accounts, grant the following local security policies, to the user. Use the Local Security Policy Manager in the Control Panel, administrative tools, or run: %SystemRoot%\system32\secpol.msc /s
In "User Rights Assignment" add the OS users to the following rights groups:
"logon as batch job"
"Run as a service"
"Replace a Process Level Token"
Follow up: There is a good discussion about this here: dizwells "NFS for Windows" post.