Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 212 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OBIEE - Change permissions to file system folders created on BI catalog
We observed that each time we create a folder on the OBIEE Catalog, this is created on the file system (catalog folder) with following permissions
drwx------
However our customer has developed some scripts that need to have the “read” permissions to folders for groups too.
Do you know any way to change this behavior to provide the permissions
drwxr----- ??
Note that files created from OBIEE Catalog are created on the File System with -rw-r-----
If we ssh login on the Exalytics server with the “oracle” user and create a folder directly on the catalog folder, then the OS uses the umask assigned to the “oracle” user and provides the correct permissions (umask 022) (drwxr-xr-x)
So it seems that the BI Presentation server (sawserver) or some internal script changes at some point the umask for creating the folders on the web catalog’s folder.
(All OBIEE processes are executed with the “oracle” user)
Any idea where or how can we change this behavior?
Answers
-
PraveenKumar R-Oracle wrote:...create a folder on the OBIEE Catalog, this is created on the file system...
...our customer has developed some scripts that need to have the “read” permissions...
...ssh login on the Exalytics server with the “oracle” user and create a folder directly on the catalog folder...You know that you must not do these things, right?
Yes, the OBIEE web catalog is saved on the filesystem in a nicely readable way (and I really thanks Oracle for that), but it isn't a file system, it isn't something which need to be access via the file system in any way! It's an application owned data storage. Oracle could have developed a weird storage for that and put everything into a single .dat file (or any other random binary things) and we would be very limited when having to recover things because of PEBCAKs.
If you or your client need to do something on that part of the file system, you need to use the web interface, the Catalog Manager tool or runcat.sh/.bat, these are the only supported ways to interact with the catalog.
Don't consider it part of your file system, it's an application owned thing and need to be considered as a blackbox you don't touch in any other way than with the provided application tools.
0 -
Hi,
Thanks for your quick response.
0
