- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Write Authorization for directory /oracle /oracle...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2002 02:24 AM
тАО02-14-2002 02:24 AM
We are trying to upgrade oracle 8.05 64-bit to 8.1.7 64-bit on HP-UX 11.00 64-bit.
In the preparation procedure we must check write authorization for directory /oracle with command "touch /oracle/write_test", but the user ora
The user/group of the directory /oracle and /oracle/stage is root, it is correct?
Arlindo Ferreira.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2002 02:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2002 02:48 AM
тАО02-14-2002 02:48 AM
Re: Write Authorization for directory /oracle /oracle/stage
The user/group of oracle installation directories should be oracle/dba.
(oracle beeing software owner and dba the osdba group)
and the chmod 775 is OK for this dir.
The Oracle8i installation introduces a new oracle install-group (oinstall) that is causing some confusion. If you use it, just make oracle member of both oinstall and dba groups.
Andreas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2002 02:50 AM
тАО02-14-2002 02:50 AM
Re: Write Authorization for directory /oracle /oracle/stage
See the installation manual from your oracle product. The installation havat to execute from oracle dba. Then all installed files owned by oracle dba (group dba). Some additional right are to be set with postinstall script root.sh from root.
You have to change all the files with chown.
chown -R
Notify your main program named oracle has s-bit like this: -rwsr-sr-x
Ruediger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2002 01:21 AM
тАО02-15-2002 01:21 AM
Re: Write Authorization for directory /oracle /oracle/stage
I always tend to be extremly carefull with
chmod -R
chown -R
chgrp -R
I have seen so many systems, where lost+found had been set to wrong settings with one of these.
You need write permissions on /oracle only for the installation/upgrade and can remove it afterwards. If you have more than one database or database versions, keep in mind, that with 8.1.7 you will get a diffrent ORACLE_HOME, another fact to be very carefull with the commands mentioned above.
The installation process is quite tolerant on this. If you get an error (root has dropped a script somwhere, where the install likes to remove it *typical*), you get a clear message what is wrong, can correct it in a second shell and reprocess. No need for global "chXXX -R" commands.
Volker