Common pitfalls during repository install

        It is recommended that we use the oracle user account on your OS (the same user account used to install other Oracle software such as the RDBMS) to install OWB. If you decide to use other user accounts besides the “oracle” user account, there might be some permission problems such that installation of the repository might fail or the Control Center Service cannot be started up properly.

        A common permission issue is shown below: a java IOException is thrown with the ORA-6512 error. Detailed information can be found in the latest installation log file under <owb-home>/owb/UnifiedRepos where <owb-home> is the OWB product installation directory.

clip_image002

 

clip_image004[5]

        The IOException is an indication that a file cannot be accessed. In this case, the error is thrown out when OWB is trying to access the rtrepos.properties file. This file is located under <owb-home>/owb/bin/admin. During the installation of OWB repository, the oracle user account should be able to access this directory and have write access there (This is because the java program that writes to this file is loaded into the database and runs from there).

        To fix this permission issue, you can go to the directory, check if the file exists there. If it is not there (that is, first-time installation), then grant write access on that directory to the oracle user account with Admin privilege; if it already exists, grant the write permission on that file to the oracle user account. Then you can restart the repository installation. Moreover, this file should only be modifiable by the oracle user account, in order to avoid wrong manipulation by other users.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

ETL, CDC, Real-Time DI and Data Quality for the Oracle Database from the inside.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today