BizTech Blog

Oracle database’s ORACLE_SID can be renamed using a couple of methods. The first method, which is a tradition method, is to create a new control file using the reuse database flag and give it a new incarnation. Once this is done we can change the values in the external files (sqlnet.ora, tnsnames.ora, init.ora (spfile)) and open the database. From Oracle 9i and beyond Oracle database can be renamed using the dbnewid (or) nid utility. In this post, we will go through the steps to rename the database using the nid utility.

• Backup the database (Always a good practice before any changes are made).
• Start the database in mount state (do not open it).
• Invoke the dbnewid utility

nid TARGET=sys/password@<CURRENT_ORACLE_SID> DBNAME=<NEW_ORACLE_SID>

Oracle has de-supported Hyperion Business Rules (HBR) in the 11.1.2.2 release. Customers with HBR in the previous releases need to migrate them to Calc Manager in 11.1.2.2. Support Doc (MetaLink Doc) ID 1448421.1 - Hyperion Business Rules Statement of Direction - has an attachment that provides an overview of the changes in availability of Hyperion Business Rules. This document would help you assess any impact to your current implementation, and to plan future decisions related to integration with the Oracle's Hyperion suite of products. The steps for migrating from Business Rules to Calc Manager depends on your specific installation type and can be found in - http://docs.oracle.com/cd/E17236_01/epm.1112/epm_install_1112200.pdf ( Page 22,23)

When Fusion Middleware Applications are installed there is a default user (weblogic or a specific name that you provide) that is created during the domain creation which acts as a super user for all Middleware Applications. This post walks through the process of resetting the weblogic password in an event that it’s lost.

1. Shutdown Weblogic Server and all associated applications.
2. Set the Weblogic Server environment variables –
   $DOAMIN_HOME/bin/setDomainEnv.sh
3. Navigate to $DOMAIN_HOME/security and rename the DefaultAuthenticatorInit.ldift file.
4. Create an initialization file in the same directory using the below command –
   java weblogic.security.utils.AdminAccount <weblogic_user_name> <weblogic_password> .
5. This will create a new DefaultAuthenticatorInit.ldift file.
6. Navigate to $DOMAIN_HOME/servers/AdminServer and rename the data directory.
7. Repeat step 6 for all the managed servers which are part of the domain.
8. If boot.properties is used, recreate them with the username and password that was provided in Step 4.
9. Start Admin Server and make sure you can login using the new credentials.
10. Start the rest of the services

Note: This process will remove all the user accounts in the weblogic domain and only the new user that is created will be present and act as a super user.