This video will show you how to install any software without knowing admin password. If you want to run another program, just copy the name of that program and replace it with the.
I have shared computer, where admin install Oracle XE. But I cannot e.g. create new user, because I have not rights in OS, afaik.In Oracle documentation written that DBA should be member of administrator group.Does exists way that I can manage local instance XE without admin rights?I need start/stop database, connect/disconnect, kill session etc. It is need for test my Java application.
Thanks.
user710818user710818
4 Answers
You don't need an OS user with admin right (once Oracle is installed and running).
Just connect as SYSDBA then you can create new Oracle users and manage the complete database..
(I do that on XP as well - working with regular user, but connecting as SYSTEM or SYS with the SYSDBA role if I need to configure something in Oracle)
a_horse_with_no_namea_horse_with_no_name
Does exists way that I can manage local instance XE without admin rights?
Probably not ... if that's what the Oracle documentation says.
A sensible strategy would be to discuss your problem with the admins. Point out that it makes it difficult for you to do your job if you don't have access rights. If they won't grant you system Admin rights, ask them to suggest alternatives that will allow you to do your job.
It may be simply that they need to grant you additional rights in Oracle.
Stephen CStephen C
How about getting admin rights in a Virtual Machine? See virtualbox.org.
GowthamGowtham
From XE manual here :
' On each platform, if the OS authentication user group does not already exist, it is automatically created when you install Oracle Database XE. In addition, upon installation on the Linux platform, the user account oracle is automatically created and placed in the dba group. Upon installation on the Windows platform, the user performing the installation is automatically added to the ORA_DBA group. On both platforms, you can add other host users to the OS authentication user group to enable them to connect to the database with the SYSDBA privilege. '
Since installation on windows needs admin user which I assume you are not, so it renders the automatic addition of that admin user to ORA_DBA group useless for you.
So what your admin can do immediately after XE installation on this shared machine is just add your non-admin OS user (local or domain level, whatever) to the newly created OS local group 'ORA_DBA'. Once this is done, you can simply open the sqlplus prompt and connect with SYSDBA privilege using your own non-admin user in future:
However, you will still not be able to restart the Oracle service or the TNS listener, even if you are in the ORA_DBA group.
Community♦
AbidAbid
Not the answer you're looking for? Browse other questions tagged windowsoraclewindows-xpadmin or ask your own question.
I'd like to be able to allow the development team to install services on a Win2003 server. They can already connect via RDP/FTP with limited accounts but I'd like to be able to grant installation privileges.
How do I do that without granting admin rights?
(The services are created using the .NET framework so we're installing with C:WindowsMicrosoft.NETFrameworkv2.0.50727installutil.exe)
Robin MRobin M
3 Answers
Delegated permission to install services is going to be a little bit tough. There is a 'SC_MANAGER_CREATE_SERVICE' right that can be granted to users on the service control manager (SCM) object in the global object manager.
In Windows versions up to Windows Server 2003, the rights could not be changed on the SCM. Starting in W2K3 SP1, you could change the rights on the SCM.
The API to change the security is SetServiceObjectSecurity, and more information is available here: http://msdn.microsoft.com/en-us/library/aa379589(VS.85).aspx
Some more reference re: the rights that can be granted to the SCM and the default DACL set on the SCM is available here: http://msdn.microsoft.com/en-us/library/ms685981(VS.85).aspx
In short, there's no way to do this w/o writing code. There's no magic registry setting, etc. If you can get somebody to write the code for you, though, it's totally feasible.
Evan AndersonEvan Anderson
I think the bigger problem is letting the dev team access a server they don't administer. Rather than trying to grant the rights to the users (SC_MANAGER_CREATE_SERVICE) think really hard about giving them their own box- even just a VM to test on, once they say it's ready an actual admin should install the services into the production system.
Jim BJim B
http://support.microsoft.com/?kbid=288129 has some info on managing services, but I don't think this can be extended to include creating arbitrary services without some major security changes on your server.
If you create a service or services then grant access as described in the knowledge base, your developers can stop the service and copy in new binaries, so they can develop/debug services even if you have to create them in the first place.
Personally I restrict our developers to a test server and grant them administrator access. The little darlings don't get access to my live servers without first convincing me their stuff is working!
JR
John RennieJohn Rennie