Sponsored Content
Full Discussion: Oracle on Solaris
Operating Systems Solaris Oracle on Solaris Post 69663 by sveera on Monday 18th of April 2005 02:56:54 PM
Old 04-18-2005
Power oracle

Hi ,
Thanks for the quick reply. when i typed the command that you gave i got a long listing . when i try to check for the ORACLE_HOME PATH variable it says that it is not set ..then what do i do to use oracle from my login ....i know what variables to set but it says that variables are not set ...then how come other users are using it ? is it because it is not set in my login it is giving that the variable is not set ?
thanks
sveera
 

6 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Oracle on solaris.

Good afternoon Unix folks, I have been asked to find out if there is an ideal way to setup oracle on sun solaris. Right now, I have 2 36gig drives mirrored for my root volume. I have 4 more raid 5 for my datavolume. For io purposes, I need to break up these drives to prove that io is the... (2 Replies)
Discussion started by: niasdad
2 Replies

2. UNIX for Advanced & Expert Users

oracle on solaris

Hi Friends , I need to connect to Oracle using sqlplus and it says that sqlplus is not found . I need to check if Oracle is running or not .is there any command to check if oracle is running ? Please help Thanks in advance Veera (2 Replies)
Discussion started by: sveera
2 Replies

3. Shell Programming and Scripting

Oracle on Solaris

Please is there a way and how can I check is my oracle database OK on my solaris I did not istall that database but on processes I can see there are lot of oracle processes running ..also I would like to use that database.. That was my first q and second: I can telnet that machine from my local... (1 Reply)
Discussion started by: amon
1 Replies

4. Solaris

solaris-oracle

Hi, what are all best performance practices we can set in solaris box for oracle database 10.2.0.2 Thanks. (3 Replies)
Discussion started by: rags_s11
3 Replies

5. Solaris

Oracle Db on Solaris OS

What is the minimum amount of RAM a db could be made to run on solaris OS .. i just need to test high availability failover of oracle db on a VM so want to make the db as thin as possible and to make it run on least amount on memory. (1 Reply)
Discussion started by: fugitive
1 Replies

6. Solaris

Oracle Solaris 11

Hello Friends I was running Solaris 10 on SunFire X2200 M2, with 40 Sunray 270 units, and would like to advance to a higher version of Solaris, Can anybody with experience on this help how to go about it, or if there is any other open source os to go with the hardware advice Thanks in... (1 Reply)
Discussion started by: daviey.daviey
1 Replies
SU(1)								   User Commands							     SU(1)

NAME
su - change user ID or become superuser SYNOPSIS
su [options] [username] DESCRIPTION
The su command is used to become another user during a login session. Invoked without a username, su defaults to becoming the superuser. The optional argument - may be used to provide an environment similar to what the user would expect had the user logged in directly. Additional arguments may be provided after the username, in which case they are supplied to the user's login shell. In particular, an argument of -c will cause the next argument to be treated as a command by most command interpreters. The command will be executed by the shell specified in /etc/passwd for the target user. You can use the -- argument to separate su options from the arguments supplied to the shell. The user will be prompted for a password, if appropriate. Invalid passwords will produce an error message. All attempts, both valid and invalid, are logged to detect abuse of the system. The current environment is passed to the new shell. The value of $PATH is reset to /bin:/usr/bin for normal users, or /sbin:/bin:/usr/sbin:/usr/bin for the superuser. This may be changed with the ENV_PATH and ENV_SUPATH definitions in /etc/login.defs. A subsystem login is indicated by the presence of a "*" as the first character of the login shell. The given home directory will be used as the root of a new file system which the user is actually logged into. OPTIONS
The options which apply to the su command are: -c, --command COMMAND Specify a command that will be invoked by the shell using its -c. The executed command will have no controlling terminal. This option cannot be used to execute interactive programs which need a controlling TTY. -, -l, --login Provide an environment similar to what the user would expect had the user logged in directly. When - is used, it must be specified before any username. For portability it is recommended to use it as last option, before any username. The other forms (-l and --login) do not have this restriction. -s, --shell SHELL The shell that will be invoked. The invoked shell is chosen from (highest priority first): The shell specified with --shell. If --preserve-environment is used, the shell specified by the $SHELL environment variable. The shell indicated in the /etc/passwd entry for the target user. /bin/sh if a shell could not be found by any above method. If the target user has a restricted shell (i.e. the shell field of this user's entry in /etc/passwd is not listed in /etc/shells), then the --shell option or the $SHELL environment variable won't be taken into account, unless su is called by root. -m, -p, --preserve-environment Preserve the current environment, except for: $PATH reset according to the /etc/login.defs options ENV_PATH or ENV_SUPATH (see below); $IFS reset to "<space><tab><newline>", if it was set. If the target user has a restricted shell, this option has no effect (unless su is called by root). Note that the default behavior for the environment is the following: The $HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS environment variables are reset. If --login is not used, the environment is copied, except for the variables above. If --login is used, the $TERM, $COLORTERM, $DISPLAY, and $XAUTHORITY environment variables are copied if they were set. Other environments might be set by PAM modules. CAVEATS
This version of su has many compilation options, only some of which may be in use at any particular site. CONFIGURATION
The following configuration variables in /etc/login.defs change the behavior of this tool: CONSOLE_GROUPS (string) List of groups to add to the user's supplementary groups set when logging in on the console (as determined by the CONSOLE setting). Default is none. Use with caution - it is possible for users to gain permanent access to these groups, even when not logged in on the console. DEFAULT_HOME (boolean) Indicate if login is allowed if we can't cd to the home directory. Default is no. If set to yes, the user will login in the root (/) directory if it is not possible to cd to her home directory. ENV_PATH (string) If set, it will be used to define the PATH environment variable when a regular user login. The value is a colon separated list of paths (for example /bin:/usr/bin) and can be preceded by PATH=. The default value is PATH=/bin:/usr/bin. ENV_SUPATH (string) If set, it will be used to define the PATH environment variable when the superuser login. The value is a colon separated list of paths (for example /sbin:/bin:/usr/sbin:/usr/bin) and can be preceded by PATH=. The default value is PATH=/sbin:/bin:/usr/sbin:/usr/bin. SULOG_FILE (string) If defined, all su activity is logged to this file. SU_NAME (string) If defined, the command name to display when running "su -". For example, if this is defined as "su" then a "ps" will display the command is "-su". If not defined, then "ps" would display the name of the shell actually being run, e.g. something like "-sh". SYSLOG_SU_ENAB (boolean) Enable "syslog" logging of su activity - in addition to sulog file logging. FILES
/etc/passwd User account information. /etc/shadow Secure user account information. /etc/login.defs Shadow password suite configuration. EXIT VALUES
On success, su returns the exit value of the command it executed. If this command was terminated by a signal, su returns the number of this signal plus 128. If su has to kill the command (because it was asked to terminate, and the command did not terminate in time), su returns 255. Some exit values from su are independent from the executed command: 0 success (--help only) 1 System or authentication failure 126 The requested command was not found 127 The requested command could not be executed SEE ALSO
login(1), login.defs(5), sg(1), sh(1). shadow-utils 4.5 01/25/2018 SU(1)
All times are GMT -4. The time now is 04:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy