root.sh
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: root.sh

Hybrid View

  1. #1
    Join Date
    Sep 2002
    Posts
    376

    root.sh

    hi,

    When we run root.sh, it prompts for local bin directory, and it creates 3 files dbhome,oraenv,coraenv.

    since i am doing 2nd installation on the same machine, should i Overwrite this ? Or let the old one be there ?


    Bascially, when are these 3 scripts used ??

    thx
    ------------------------------------------------------------------------
    The most enjoyable things in the world are either Immoral or too Expensive or otherwise Inaccessible anyway

  2. #2
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    it really makes no difference

  3. #3
    Join Date
    Dec 2002
    Location
    Bangalore ( India )
    Posts
    2,434
    dont over wirte..
    funky...

    "I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."

    "Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"

  4. #4
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    340
    Hi
    root.sh script is written in the orainst directory.
    root.sh, which is a shell script, updates/creates an oratab file. The oratab file is the file where the user will place references to all databases to be discovered by the agent and controlled by the Oracle Enterprise Manager. For each database created, the entry is of the form: :<$ORACLE_HOME>:[Y/N]

    The agent is normally configured by root.sh as a setuid program. If root.sh was successful, the agent will have been installed as setuid root so that the agent can run jobs as the users whose name and password are given in the Preferred Credentials for that host.

    If the agent is not a setuid program, all Enterprise Manager jobs are run with the permissions of the user who started the agent.

    The user who submits node jobs to the UNIX agent should have read/write access to the Agent's ORACLE_HOME. If the root.sh does not have setuid set, then any job submitted to the agent will run with the privileges of the user who owns the Agent executable (dbsnmp.exe). root.sh will force the user to set the preferred credentials at the Oracle Enterprise Manager Console for any job on the Agent.

    For getting more details about oracle utilities like oraenve,..etc
    go through this link http://www.remote-dba.net/teas_rem_util2.htm

    Gopu

  5. #5
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    what the hell as that got to do with the question asked?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width