Which Business Monitor migration steps can be carried out without a database connection?
Yan Fang 1200008V6D Visits (6348)
Here is a scenario: Customer plans to migrate their environment from Business Monitor 126.96.36.199 to 8.5.6 but only have a 2 day window(Saturday and Sunday). This is a too small window(48 hours). This customer has a large amount of data in their current 188.8.131.52 Monitor environment. Keep in mind the source database is updated everyday and they cannot stop the application for more than a day before migration. They would like to do all database related migration tasks in one day. They also want no additional database migration tasks completed ahead of schedule. I'll explain if its possible to cut down the migration tasks below.
According to the High
The migration to the new IBM Business Monitor (v8.5.6) is scheduled to be installed on a NEW MACHINE however they will use the same database as the current. As noted above, they do not have enough time to migrate because they have to complete all tasks in 2 days. The goal is to do as many of the migration steps as possible, ahead of the scheduled outage.
Firstly, we can recommend that steps 1 to 3 can be done ahead of schedule if they have no new monitor model version / updating to the current Monitor 184.108.40.206 environment. Unfortunately Steps 4, 6, 7. 8, and 9 depend on the source Monitor database so these steps cannot be moved ahead.
The Configuring IBM Business Monitor Step 5 contains five additional sub-steps. Lets determine if any of these sub-steps can be completed ahead of schedule.
5-1. Create profiles. When you are creating the deployment manager, use the information from your source environment in the database configuration page of the administrative console.
5-2. Start the deployment manager and the custom nodes.
5-3. Configure the target deployment environment using the monConfig script.
5-4. Check the port number where IBM Cognos Business Intelligence is running, and add the port number to the virtual hosts list.
5-5. Stop the target deployment environment.
Since the database is currently running, when Step 5-1 and 5-2 are performed without a connection to the database in the target BPM 8.5.6 environment, the below error appears in the SystemOut.log.
LifecycleStop E com.
For the database ConnectException message with ERRORCODE=-4499, SQLSTATE=08001, look in the DB2
Table 6. Class Code 08: Connection Exception 08001 The connection was unable to be established to the application server or other server.
As you see the Monitor server can't establish the connection with the database server. However if carefully read Step 17 in Creating deployment manager profiles, note the details in step 17j.
j. Click Next. If the MONITOR database has not yet been created, you will see a Database validation failure warning message. Click Yes to continue. You can create the database at a later time.
So if you "Create a deployment manager profile of BM8.5.6" and "Create a custom profile of BM8.5.6" of step 5-1 and can not connect to database, you can IGNORE the database connection error according to the above information. Please note before you can perform step 5-2, Starting Profile, this needs configuration information from the monitor database. You will need to create the database, configure the database using the database scripts, and then connect to database prior to attempting step 5-2.
In summary, the customer can run the below migration steps ahead of schedule without a database connection: