To Configure boot.properties file for auto login while starting/stopping OBIEE 11g

A boot.properties file contains user credentials for starting and stopping an instance of WebLogic Server. An Administration  Server can refer to this file for user credentials instead of prompting you to provide them.

To configure the boot.properties file for the AdminServer (WebLogic), perform the following steps:

1. Go to $MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/AdminServers/security and create the boot.properties file.
vi boot.properties

2. add the below values in a file and save it.
username=admin_username
password=admin_password

eg:
username=weblogic
password=weblogic1

3. Now go to $MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/bin and run Admin server in nohup mode

nohup ./startWebLogic.sh >startWebLogic.log &

You can check in the log that it's using boot.properties file for login credentials.

eg:

/scratch/home/mw1/user_projects/domains/bifoundation_domain/servers/AdminServer/security/boot.properties>

Nov 28, 2012 11:40:25 PM oracle.ods.virtualization.engine.util.VDELogger info
INFO: Notification sent for Mapping config object reloaded




and also username and password will be encrypted automatically once admin server is started using boot.properties file. Samething with managed server
eg:
-bash-4.1$ cat boot.properties
#Wed Nov 28 23:39:59 PST 2012
password={AES}KzE36wWcZfXJriP/ctNLXyiJ7XhGliErrE3Hd9WJyj4\=
username={AES}L/OMSXhRReONiUV+ts45JE7uM5IZ+WAjSbhBNsG6xH8\=
-bash-4.1$ pwd
/scratch/home/mw1/user_projects/domains/bifoundation_domain/servers/AdminServer/security



To configure the boot.properties file for the Managed Server, perform the following steps:

1. Go to $MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/security and create the boot.properties file.
vi boot.properties

2. add the below values in a file and save it.
username=admin_username
password=admin_password

eg:
username=weblogic
password=weblogic1

3. Now go to $MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/bin and run managed server in nohup mode.

nohup ./startManagedWebLogic.sh bi_server1 >startManagedWebLogic.log &

Why Oracle Clusterware Needs Odd Number of Voting Disks

An odd number of voting disks is required for proper clusterware configuration. A node must be able to strictly access more than half of the voting disks at any time. So, in order to tolerate a failure of n voting disks, there must be at least 2n+1 configured.

When you have one voting disk and it goes bad, the cluster stops functioning and when you have two and one goes bad, the same happens because the nodes realize they can only write to half of the original disks , violating the rule that they must be able to write > half.When you have three and one goes bad, the cluster runs fine because the nodes know they can access more than half of the original voting disks (2/3 > half). That's why oracle recommend 3 voting disks for two node cluster.

Oracle Warehouse Builder patches for 10.2.0.2 and 10.2.0.3

Oracle warehouse builder software for 10.2.0.2 and 10.2.0.3 can be found in Oracle meta link with patch numbers 5696353 and 6264457 respectively.  Refer the document 340955.1 for further details.