learn unix and linux commands

Article: Oracle Enterprise Manager Grid Control

 
Thread Tools Search this Thread
# 1  
Old 07-22-2010
Article: Oracle Enterprise Manager Grid Control

Arvind Maheshwari and Debu Panda describe Oracle Enterprise Manager Grid control architecture, terminology, basic concepts, and entities, and walk through the lifecycle of a managed target in Grid Control.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

Running RMAN backups from grid control but using oracle account with rsa keys vs a password ?

I'm a sysadmin trying to help out one of our DBA's setup the RMAN backups (Oracle 11g on rhel5 ) so they can schedule and control them from the OEM grid control. But we want the oracle user to use ssh keys instead of a password. I have the working rsa keys in place for the user but the GUI seems to... (0 Replies)
Discussion started by: samael00
0 Replies
Login or Register to Ask a Question
USER(5) 						   Sun Grid Engine File Formats 						   USER(5)

NAME
user - Sun Grid Engine user entry file format DESCRIPTION
A user entry is used to store ticket and usage information on a per user basis. Maintaining user entries for all users participating in a Sun Grid Engine system is required if Sun Grid Engine is operated under a user share tree policy. If the enforce_user cluster configuration parameter is set to auto, a user object for the submitting user will be created automatically during job submission, if one does not already exist. The auto_user_oticket, auto_user_fshare, auto_user_default_project, and auto_user_delete_time cluster configuration parameters will be used as default attributes of the new user object. A list of currently configured user entries can be displayed via the qconf(1) -suserl option. The contents of each enlisted user entry can be shown via the -suser switch. The output follows the user format description. New user entries can be created and existing can be modi- fied via the -auser, -muser and -duser options to qconf(1). Note, Sun Grid Engine allows backslashes () be used to escape newline ( ewline) characters. The backslash and the newline are replaced with a space (" ") character before any interpretation. FORMAT
A user entry contains four parameters: name The user name as defined for user_name in sge_types(1). oticket The amount of override tickets currently assigned to the user. fshare The current functional share of the user. default_project The default project of the user. delete_time Note: Deprecated, may be removed in future release. The wall-clock time when this user will be deleted, expressed as the number of seconds elapsed since January 1, 1970. If set to zero, the affected user is a permanent user. If set to one, the user currently has active jobs. For additional information about automatically cre- ated users, see the enforce_user and auto_user_delete_time parameters in sge_conf(5). SEE ALSO
sge_intro(1), sge_types(1), qconf(1). sge_conf(5). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ USER(5)