The BroadSoft BroadWorks DBS is a different animal than other BroadWorks servers, and it requires a special set of commands to keep it alive and well. The level of care and feeding required for the database reminds of BroadWorks App Server release R12 and R13; those were not happy days.
Check status of the FRA Disk Group
- dbsctl diskinfo
- /etc/init.d/oracleasm listdisks
- On a healthy, normal system, this should list two entries: DATA and FRA
- srvctl status diskgroup -g FRA
- As root: /sbin/blkid | grep asm
These show a lot of what happen when installing the Oracle parts of the DBS:
- /u01/app/oraInventory/logs/installActions* show
Convert a standalone DBS to be a secondary DBS
- Clear ASM DATA and FRA disk groups
- Install DBS on DBS2 as a standalone primary
- On the primary/active DBS: use config-ssh to mesh both bwadmin and oracle accounts
- On the other DBS which will become the standby: sitectl convert bwCentralizedDbX
- On the primary/active DBS: peerctl add dbs2
Fix the kernel 2.6.18-400.1.1.el5 name mismatch for OracleASM
Upgrading to the BroadWorks DBS R20sp1 requires a kernel update. As of 2014 December 19, updating the RHEL 5 kernel installs version 2.6.18-400.1.1.el5.
However, only oracleasm-2.6.18-400.el5-2.0.5-1.el5 is available from Oracle.
However, the kernel module appears to be cross-compatible. Here’s how I moved it:
mkdir -p /lib/modules/2.6.18-400.1.1.el5/kernel/drivers/addon/oracleasm
cp /lib/modules/2.6.18-400.el5/kernel/drivers/addon/oracleasm/oracleasm.ko /lib/modules/2.6.18-400.1.1.el5/kernel/drivers/addon/oracleasm
cat /lib/modules/2.6.18-400.el5/modules.dep >> /lib/modules/2.6.18-400.1.1.el5/modules.dep