Troubleshooting the BladeLogic RDS

See the following sections for resolving issues you may encounter when deploying the BMC BladeLogic RDS:

The SSLPort is set to 0 by default

By default, the SSLPort for the BladeLogic Rapid Deployment Stack is set to 0. Port 9831 is required for PXE provisioning.

Workaround:

From the RDS, connect to the console.
In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
Expand the hierarchy of the Application Servers node.
Right-click the Application Server you want to edit and select Edit. The Edit Application Server Profile dialog box opens.
Edit the SSL Port to configure it to a value 9831 instead of 0. The SSL Port field is shown below.

Error message when deploying the RDS OVF on Virtual Center 5.0

While deploying the RDS OVF on Virtual Center 5.0, you may see the warning shown below:

Workaround: Select Yes and continue with the deployment.

Error when trying to deploy the RDS from vSphere Client connected to the host

If the ESX host is being managed by Virtual Center, you may get the following error when trying to deploy the RDS from vSphere Client connected to the host:

Access to resource settings on the host is restricted to the server that is managing it.

Workaround: Connect the vSphere Client to the Virtual Center Server instead of the host and proceed with the deployment.

A compilation error is returned when I import the Oracle database dump

The following table presents strategies to resolve a compilation error that is returned when you attempt to import the Oracle database dump during the BladeLogic RDS installation.

Action	Strategy
Importing Oracle database dump	When you import the Oracle database dumps, a compilation error is returned if the relevant schema name is specified incorrectly in the db dump import command. Ensure that the schema name is XE.
Importing Oracle database dump	To import the Oracle database dump, use the following command example: impdp system/xxxxxxx@BLADE REMAP_SCHEMA=XE:bladelogic directory=PUMP_DIR transform=oid:n dumpfile=bladelogic.dmp logfile=bladelogic.log
Importing BladeLogic Database Dump User	When you import the BladeLogic Database Dump User, ensure that: The BLADELOGIC tablespace is available in the Oracle server The schema name is XE
Importing BladeLogic Portal Database User	When you import the BladeLogic Portal Database User, ensure that: The portal_database tablespace is available in the Oracle server The schema name is portal_database
Importing Oracle database dump for Portal	To import the Oracle database dump, use the following command example: impdp system/xxxxxxx@BLADE REMAP_SCHEMA=portal_database:PORTALDB directory=PUMP_DIR transform=oid:n dumpfile=portal_database.dmp logfile=portal_database.log
Creating the portal_database tablespace	To create the portal_database tablespace, use the following command example: CREATE BIGFILE TABLESPACE portal_database DATAFILE '/usr/oracle/databases/ora112db/portal_database.dbf' SIZE 512M AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE BIGFILE TABLESPACE portal_database_INDEX DATAFILE '/usr/oracle/databases/ora112db/portal_database_index.dbf' SIZE 512M AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE USER portal_database PROFILE DEFAULT IDENTIFIED BY sa DEFAULT TABLESPACE portal_database TEMPORARY TABLESPACE TEMP ACCOUNT UNLOCK; GRANT CONNECT TO portal_database; GRANT DBA TO portal_database; commit;

I want to connect the BladeLogic Portal to a different database

To reconfigure the Portal database bundled with the BladeLogic RDS, consult the"I want to connect the portal to a different database" section Troubleshooting the installation topic in the BMC BladeLogic Portal documentation.