Troubleshooting UPI Upgrade issues

The RSCD agent bundle is not found at the required location. The rscd directory is missing from the UPI Disk1/files/installers/ directory.

1. Verify that the RSCDAgent.zip" file is extracted and the "rscd" directory is placed in the "files\installers" directory.
2. Follow the steps in the referenced Knowledge Article.

Pre-upgrade environment discovery

Failed to perform infrastructure discovery. Unable to launch the NSH or BLCLI commands required to discover the Application Servers in the environment.

1. Verify that all the upgrade prerequisites are met before upgrading the environment.
2. Follow the steps in the referenced Knowledge Article.

Pre-upgrade prerequisite validation 

Follow the steps in the referenced Knowledge Article.

The following prerequisite has failed for server (server01.bmc.com):

The RSCD agent is configured in a way that prevents the remote communication with the server. The RSCD agent on the specified server is either down or the ACLs are restricted.

Possible reasons could be:

• The user is not part of root/Administrators group.
• The user does not have sufficient permissions for read and write operations.
• The RSCD agent is not licensed.
• The RSCD agent is configured to request client side certificates for authentication/authorization.
• The Network Shell is configured to run in the proxy mode and always communicate with the Network Shell Proxy Server.

1. Verify that the RSCD agent is up and running and that the RSCD ACLs allow the OS user running the UPI access and provide a mapping to the root or a local administrator.
2. From the server where the UPI is being run, test access by launching NSH as the same OS user running the UPI and then type "agentinfo serverX" to confirm access and mapping.
3. Follow the steps in the referenced Knowledge Article.

1. Verify that the RSCD agent is up and running and that the RSCD ACLs allow the OS user running the UPI access and provide a mapping to the root or a local administrator.
2. From the server where the UPI is being run, test access by launching NSH as the same OS user running the UPI and then type "agentinfo serverX" to confirm access and mapping.
3. Follow the steps in the referenced Knowledge Article.

The following prerequisites failed for server (server01.bmc.com):

User {0} does not have privileges to perform the upgrade.

1. Configure the read and write privileges to access the computer using the RSCD agent. 
2. On a Linux Application Server, run the UPI as a root user.
3. Follow the steps in the referenced Knowledge Article.

Unable to retrieve the database version after querying the system_property.

The database is unable to connect using the DB connection information stored in the _template deployment. 

Follow the steps in the referenced Knowledge Article.

Specified directory has one or more directories which do not have a short name 8dot3.

1. Ensure that the directory path you specify has a short name (8dot3) generated for all the directories in the path.
2. Follow the steps in the referenced Knowledge Article.

Network Shell Client is configured in a way that prevents remote communication with other hosts.

This error indicates that the server where the UPI is being run is configured to run either in the Network Shell client mode or to use client side certificates with authentication/authorization.

Follow the steps in the referenced Knowledge Article.

Database upgrade

1. Review the blmigration.log file located in the NSH/br directory.
   The detailed database error is usually found directly under this heading:
   DISPLAYING ALL THE ERRORS
2. Review the bsainstallupgrade.log file located in the host computer's temporary directory to understand the cause for the database migration failure.
   

3. If you are not able to determine the problem from the installation log file, please contact BMC support.

   
   

   
   

I

In this case, the missing privileges were not detected during the UPI prerequisite validation step, and the UPI proceeded to the database upgrade/migration.

The insufficient privileges were then detected during the SB Migration and logged to blmigration.log.

Do the following:

1. Make sure the required privileges are assigned directly to the bladelogic DB user and not via a role.
2. Follow the steps in the referenced Knowledge Article.

1. Identify the problematic tablespace and provide this error message to the site Oracle DBA.
   

   Some Oracle tablespaces cannot be extended.

   In this example, it is the UNDO tablespace but that could vary. For example, TEMP, DATA, INDEX, and so on.

2. Once the tablespace is extended, rerun the upgrade and it should continue from the point of failure.

If a different error is encountered after resolving the tablespace issue, contact BMC Support as manual intervention or a DB restore may be required to get the database back to a state where the upgrade can be re-run.

The MS SQL Server transaction log is full.

Note the exact error message and provide this to the site MS SQL Server DBA.

Once the problem has been corrected, rerun the upgrade and it should continue from the point of failure.

If a different error is encountered after resolving the transaction log issue, contact BMC Support as manual intervention or a DB restore may be required to get the database back to a state where the upgrade can be re-run.

This error is the Oracle database-side memory error.

Contact the site Oracle DBA to resolve this issue by increasing the memory settings, such as SGA.

The method that is used to resolve the error varies for different Oracle environments and depends on best practices and the Oracle Memory Management method that is in use, such as AMM or ASMM.

The stored procedure is not complied or failed to compile due to dependencies or shared memory.
This issue is usually an intermittent DB side issue and simply rerunning the UPI may resolve the issue.

• If the following error is encountered during the 8.9.04.003 upgrade, check the referenced KA:
  "ORA-01418: specified index does not exist"
• If the following error is encountered during any other upgrade step, contact BMC Customer Support and provide the information specified in step 4.
  "ORA-01418: specified index does not exist"

The online rebuilding of Oracle indexes is a feature for Oracle Enterprise Edition databases. It cannot be used for Oracle Standard Edition databases.

The database upgrade in the 8.9.03 patch 1 release had a defect (DRBLG-116418), which relied on this feature.

Follow the steps in the referenced Knowledge Article.

The RSCD Agent upgrade failed on blfs. Refer to the log file located at /tmp/BladeLogic_Install on the server where the upgrade failed.

Some possible causes and steps for remediation:

Check if Version.new file is present in TrueSight Server Automation installation directory.

Application Server(s) upgrade

Review the appropriate log on the specified Server:

• (Linux) /tmp/BladeLogic_Install
• (Windows) %TEMP%/OM-install.log

Post-upgrade 

environment discovery

This issue occurs because the Application Server upgrade was not successful and the service is down.

Specified Application Server(s) may not be restarting after upgrade.

Review the appserver.log and/or console.log on the specified Application Servers(s) to determine if they are currently down and, if so, why.

Once Application Server(s) have been restarted, rerun the UPI to resume.

Post-upgrade content installation

Manually importing out-of-box content