Thursday, May 23, 2013

OBIEE 11g RPD password Change via command mode

Change the OBI Repository Password from the Command mode

In OBIEE there is new BI Server utility called obieerpdpwdchg to change the RPD password from command mode. Please follow the steps to change the repository password using the obieerpdpwdchg utility, and then deploy the modified repository in Fusion Middle ware Control.

Step 1:

  •  Run bi-init to launch a command prompt. 
  • You can find the bi-init command from 

      Client installations: ORACLE_HOME/bifoundation/server/bin

Simple/Software/Enterprise other installations: ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup

Execute bi-init.cmd  to display a command prompt that is initialized to your Oracle instance like below

Once done above step.

Step 2:

  •  At the command prompt, type obieerpdpwdchg with the following arguments: 
  •  -I name_and_path_of_existing_repository 
  •  -O name_and_path_of_new_repository 

Then, enter the current (old) password and the new password when prompted. The repository password must be longer than five characters and cannot be empty. For example:

obieerpdpwdchg -I C:\SampleAppLite_BI0001.rpd -O C:\New_SampleAppLite_BI0001.rpd
Give password for repository: Admin123
Give password for repository: satya123

  • 3. Open a Web browser and log in to Fusion Middleware Control from the computer where the updated repository is located. 
  • 4. In the navigation tree, expand Business Intelligence and then click coreapplication to display the Business Intelligence Overview page. 
  • 5. Display the Repository tab of the Deployment page. 
  • 6. Click Lock and Edit Configuration. 
  • 7. Click Browse next to Repository File. Then, select the updated repository file and click Open. 
  • 8. Enter the new (updated) repository password in the Repository Password and the Confirm Password fields. 
  • Make sure to specify the password that has been set in the repository. If the passwords do not match, the Oracle BI Server fails to start, and an error is logged in nqserver.log.

Hope this help's


No comments:

Post a Comment