Posts Tagged ‘Oracle’

Sun Advanced Lights Out Manager system controller (ALOM SC) – ALOM Logs Commands

June 16th, 2014, posted in Oracle, Solaris, TEChNoLoGY
Share

ALOM Logs Commands,ALOM Logs, Sun System,Sun Fire T2000,Sun Fire V445,Sun Fire, Sun Fire System,ALMO,ALOM Logs,ALOM Log,ALOM command,Log Command,V445_Console,ALOM V445_Console,Sun Fire V445 Console


Sun Advanced Lights Out Manager system controller (ALOM SC)

ALOM System Controller enables you to remotely manage and administer a server.
It comes preinstalled on the machine, so as soon you plug in power cable, it works.
Yes, it uses server’s standby power, which enables you to remotely power off and on server (very useful when someone schedule power outage in remote office and you want gracefully to bring server down and after outage power it on). ALOM monitors hardware in the server, like CPU, RAM, Power supply, etc, and much more like Voltage and status of alarms. Of course, all this exercise assumes you configured ALOM’s network parameters.

Try to have dedicated management subnet for this. If you access ALOM and stay idle for 1 minute, it will switch to serial console. Or you can type console and reach serial console of remote system from your cube or home living room.

ALOM Logs Commands,ALOM Logs, Sun System,Sun Fire T2000,Sun Fire V445,Sun Fire, Sun Fire System,ALMO,ALOM Logs,ALOM Log,ALOM command,Log Command,ALOM Logs Commands,ALOM Logs, Sun System,Sun Fire T2000,Sun Fire V445,Sun Fire, Sun Fire System,ALMO,ALOM Logs,ALOM Log,ALOM command,Log Command,V445_Console,ALOM V445_Console,Sun Fire V445 Console,Hardware consoles Oracle,Hardware consoles ,Oracle,Hardware ,consoles Oracle,Sun Advanced Lights Out Manager system controller

sc> console

To go back to ALOM type #. (pound and dot)

ALOM  Commands :

showplatform [-v]

showfru

showdate

consolehistory [-v] [boot | run]

showenvironment

showusers [-g]

showsc [-v]

userpassword

showlogs [-v]

ALOM Logs Commands,ALOM Logs, Sun System,Sun Fire T2000,Sun Fire V445,Sun Fire, Sun Fire System,ALMO,ALOM Logs,ALOM Log,ALOM command,Log Command,ALOM Logs Commands,ALOM Logs, Sun System,Sun Fire T2000,Sun Fire V445,Sun Fire, Sun Fire System,ALMO,ALOM Logs,ALOM Log,ALOM command,Log Command,V445_Console,ALOM V445_Console,Sun Fire V445 Console,Hardware consoles Oracle,Hardware consoles ,Oracle,Hardware ,consoles Oracle,Sun Advanced Lights Out Manager system controller

Link : http://docs.oracle.com/cd/E19102-01/n440.srvr/817-5481-11/command_shell.html
Link : http://www.googlux.com/alom.html
Link : http://docs.oracle.com/cd/E19076-01/t2k.srvr/819-2548-14/3_Diags.html
Share

Oracle : Seven Deadly Habits Of A DBA And How To Cure Them

June 20th, 2013, posted in Oracle
Share

Seven Deadly Habits Of A DBA And How To Cure Them,oracle,dba,cure,sin,mistake,issues,Seven Deadly Habits of a DBA and how to cure them

Calling widespread bad habits in database administration “deadly” may seem extreme. However, when you consider the critical nature of most data, and just how damaging data loss or corruption can be to a corporation, “deadly” seems pretty dead-on.
Although these habits are distressingly common among DBAs, they are curable with some shrewd management intervention. What follows is a list of the seven habits we consider the deadliest, along with some ideas on how to eliminate them.

Habit #1. THE LEAP OF FAITH: “We have faith in our backup.”
Blind faith can be endearing, but not when it comes backing up a database. Backups should be trusted only as far as they have been tested and verified.
Cures:

  • Have your DBAs verify that the backup is succeeding regularly, preferably using a script that notifies them if there’s an issue.
  • Maintain a backup to your backup. DBAs should always use at least two backup methods. A common technique is to use those old-fashioned exports as a backup to the online backups.
  • Resource test recoveries as often as is practical. An early sign that your DBA team is either overworked or not prioritizing correctly is having a quarter go by without a test recovery. Test recoveries confirm that your backup strategy is on track, while allowing your team to practice recovery activities so they can handle them effectively when the time comes.

Habit #2. GREAT EXPECTATIONS: “It will work the way we expect it to. Let’s go ahead.”
Although not user friendly in the traditional sense, Oracle is very power-user friendly— once you’ve been working with it for a while, you develop an instinct for the way things “should” work. Although that instinct is often right, one of the most dangerous habits any DBA can possess is an assumption that Oracle will “just work” the way it should.
Cures:

  • Inculcate a “practice, practice, practice” mentality throughout the organization. DBAs need to rehearse activities in the safe sandbox of a test environment that’s designed to closely mimic the behaviour of the production system. The organization needs to allow the time and money for them to do so.
  • Pair inexperienced DBAs with senior ones whenever possible—or take them under your own wing. New DBAs tend to be fearless, but learning from someone else’s experience can help instill some much needed paranoia.
  • Review the plans for everything. It’s amazing how often DBAs say, “I’ve done that a hundred times, I don’t need a plan.” If they’re heading into execution mode, they absolutely need a plan.

Habit #3. LAISSEZ-FAIRE ADMINISTRATION: “We don’t need to monitor the system. The users always let us know when something’s wrong.”
If you depend on the users to inform the DBA team that there’s a problem, it may already be too late.
Cures:

  • Install availability and performance monitoring systems so that issues are identified and resolved before they cause service-affecting failures.
  • Avoid post-release software issues by working with developers and testers to ensure that all production-ready software is stable and high-performance.

Habit #4. THE MEMORY TEST: “We’ll remember how this happened, and what we did to get things going again.”

It may seem impossible that a DBA team would forget a massive procedure that took them weeks to get right, and yet it happens all the time. In order to prevent recurring mistakes and take advantage of gained experience, documentation is essential.

Cures:

  • Require that your DBAs maintain a comprehensive documentation library and activity diary, including a significant level of rationale, syntax, and workflow detail.
  • Provide your team with groupware on your intranet so that these documents become searchable in an emergency.
  • Enforce the discipline of documentation and check it periodically. Ask your DBAs: When was this tablespace created, by whom, and with what SQL? What tasks were performed on a particular day? If they can’t answer quickly, you’ll know they’ve gone back to relying on memory.

Habit #5. THE BLAME GAME: “Don’t look at me, it’s the developer’s fault that SQL is in production”

Some DBAs have a real “us versus them” mentality when it comes to developers in their organization. They see themselves not as facilitators helping the developers develop quality code from a database standpoint, but rather as guardians who prevent poor-quality code from making it into production. This might seem like semantics, but a confrontational relationship between developers and DBAs results in a lack of developer initiative and significant slowdowns in release cycles.

Cures:

  • Select DBAs who understand it’s their responsibility to work as an integrated team with the developers they support.
  • Cultivate a team attitude by structuring continuous DBA involvement in every project rather than at review milestones.
  • Consider assigning an individual DBA in a developer support role. If it’s clearly in the job description, there’s more motivation to do it well.

Habit #6. THE SOLO ACT: “I know what I’m doing and don’t need any help.”

Database administration is increasingly complex and even the most senior DBAs can’t possibly know every last detail. DBAs have different specialties, which need to be culled and utilized. When DBAs feel like they know, or should know, everything, they don’t ask questions and miss out on valuable knowledge they could be gaining from others.
Cures:

  • Foster a teamwork culture where it’s acceptable for DBAs to admit they don’t know the answer and to ask for help.
  • Encourage your DBAs to seek out an outside peer group as a forum for brainstorming and testing their assumptions. No single person can match the expertise and experience of even a relatively small group.
  • Provide a safety net of tech resources such as reference materials, courses, and outside experts or consultants on call.

Habit #7. TECHNO-LUST: “Things would work so much better if only we had…”
DBAs are often on top of the latest technology, which can help them do a superlative job. But when the desire for new technology causes DBAs to recommend unnecessary hardware purchases or software add-ons, costs tend to skyrocket quickly—as do problems.

Cures:

  • Never upgrade your hardware infrastructure without first exhausting all tuning opportunities. Remember, ten years ago enormous enterprises were run on servers one-tenth the capacity—all thanks to necessity and skill.
  • Never consent to using advanced or new features until you’re well aware of the ongoing maintenance commitment and resulting costs.
  • Watch out for DBA support software that presents friendly GUI interfaces for difficult tasks. This type of interface allows a beginner DBA to act as an intermediate DBA under certain circumstances, but simultaneously prevents that beginner from learning the actual skills behind the tasks. Moreover, these tools tend to hide real risks from the DBA, making potentially damaging activities as easy as point-and-click.Whether it takes a twelve-step program or one tiny adjustment, all of these deadly DBA habits can be kicked. Of course, the first step is recognizing the problem. By starting with this list and doing a careful inventory of the successes and failures in your team’s database administration, you’ll be well on your way to finding a cure
Main url: http://appsdbaclass.blogspot.com/2011/10/seven-deadly-habits-of-dbaand-how-to.html?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+OracleAppsDbaoracleEbsR12+%28Oracle+Apps+DBA+%28Oracle+EBS+R12%29%29
Share

Compiling PL/SQL and using TOAD to write stored procedures

June 12th, 2013, posted in Oracle
Share

Compiling PL/SQL and using TOAD to write stored procedures :


  • PL/SQL compiler (version?) is quite stupid: ” Missing a semi-colon flags a line several lines below where the actual semi-colon is missing.”  Likewise for a missing single quote character
  • To escape the single quote character, double it.”  Therefore four consecutive single quotes is a string consisting of a single quote
  • When the compiler reports a compiler error at a certain line, that line # is relative to the start of the Body of stored procedure (assuming you are editing the Body and not the Spec)
  • To compile and “save” your stored procedure to the Oracle server in TOAD, be sure to use the “Execute As Script” button () in the Editor.  Do NOT use the “Execute/compile statement at caret” button.

    link : http://buildingaircastles.blogspot.com/2010/11/compiling-plsql-and-using-toad-to-write.html

  • Share

    Oracle : Activate Oracle on XAMPP for Windows : OCI8 : XAMPP ORACLE CONFIGURATION

    March 1st, 2013, posted in Oracle, PHP
    Share

    If you want to connect with Oracle database using PHP script you will have to do some effort. Because with the default installation of XAMPP for Windows, we don’t get PHP Oracle connectivity enabled. This can be enabled easily when you need to connect to a Oracle Database from your PHP application/script. PHP has got the OCI8 extension, which provides Oracle connectivity to PHP application, and OCI8 uses Oracle Instant Client Package to get Oracle specific functions.

    I had the need to connect to a Oracle Database from a PHP script in one of my recent projects, the following is what I did to enable Oracle connectivity in XAMPP for Windows.

    1. In your XAMPP Start Page, go to phpinfo, look for string oci8. If string found it indicate that connection to oracle is available, otherwise to activate connection do the following steps:
    2. Open the currently used php.ini file by looking at the phpinfo, from the XAMPP folder.
    3. Find string ;extension=php_oci8.dll. Remove the semicolon (;) ahead of the string to activate the oracle extension.
    4. Save the php.ini file.
    5. Download the “Instant Client Package – Basic” for Windows from the OTN Instant Client page. Unzip it to c:instantclient_11_1
    6. Edit the PATH environment setting and add c:instantclient_11_1 before any other Oracle directories. For example, on Windows XP, follow Start -> Control Panel -> System -> Advanced -> Environment Variables and edit PATH in the System variables list.
    7. Set desired Oracle globalization language environment variables such as NLS_LANG. If nothing is set, a default local environment will be assumed. See An Overview on Globalizing Oracle PHP Applications for more details.
    8. Unset Oracle variables such as ORACLE_HOME and ORACLE_SID, which are unnecessary with Instant Client (if they are set previously).
    9. Restart XAMPP (or Start if its not already started).
    10. To make sure that connection to oracle database has successfully activated, go to phpinfo. Find string: oci8. If found, then XAMPP can now communicate with Oracle Database.

    The steps to do the same on Linux are almost similar, except there you will use the Linux versions of the packages and setting PATH variables would be different.

    To test the connection you can use this script

    <?php
    $conn = oci_connect('username', 'password', 'host:port/servicename');
    $query = 'select table_name from user_tables';
    $stid = oci_parse($conn, $query);
    oci_execute($stid, OCI_DEFAULT);
    while ($row = oci_fetch_array($stid, OCI_ASSOC)) {
    foreach ($row as $item) {
    echo $item." | ";
    }
    echo "
    n";
    }
    oci_free_statement($stid);
    oci_close($conn);
    ?>

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

    If you need to configure your xampp installation (on winXP) to connect to the oracle

    – first you need to download oracle basic instant client for windows

    – After unzipping the instant client on a selected directory (i.e. c:/instantclient_11_1) you need to copy all dlls from this directory to “xampp/apache/bin/”

    – Add instant client directory to windows system variable’s path : follow Start -> Control Panel -> System -> Advanced -> Environment Variables and edit PATH in the System variables list

    – now open up php.ini from “xampp/php” and remove semicolon from this line “;extension=php_oci8.dll”

    all you have to do is restarting apache and you’re all set

    Another wonderful link for this topic is : http://me2learn.wordpress.com/2008/10/18/connect-php-with-oracle-database/

    Share

    ORACLE : How to Calculate Average of Date Values ?

    February 25th, 2013, posted in Oracle Queries
    Share

    Are you getting trouble of calculating average time of a filed, where data type is date time ?
    Don’t worry. You are at right place to get right solution.

    I’m going to calculate average time of a filed.
    If there is two time value in a day, i will calculate the first one means minimum one.

    SELECT TO_CHAR(TRUNC(SYSDATE)+AVG(VDATE-TRUNC(VDATE)),’HH24:MI:SS’)
    FROM (SELECT MIN(DDATE) VDATE
    FROM DEPT
    GROUP BY TRUNC(DDATE))

    ****************************************************************************************************************
    Note : Please not do make backups before using these queries and also confirm them yourself or by aother means as
    well.
    *****************************************************************************************************************
    Share