Upgrade UNIX 6.1 to 6.2 Master bizarre behavior

Reginald Hill · ‎03-01-2015

We are experiencing a bizarre behavior after our install upgrade from 6.1 to 6.2 Master.

1. Clone the UNIX 6.1 master machine (Unix0161) and import/export the 6.1 database onto another database server, then removed the entire Tidal/Master directory from the now clone UNIX 6.2 master machine (Unix026-2).

2. Installed the UNIX 6.2 master on to (Unix026-2).

3. From the bin directory execute the ./tesm status command and the service was stopped

4. Applied hotfixes, performance parameters

5. From the bin directory execute the ./tesm start command

The log says Master initialized but the server status is still down. Somehow the replicate server (UNIX026-2) is still attached to (UNIX0161) when startup the new TES 6.2 master service (UNIX026-2) the TES 6.1 master service (UNIX0161) stop.

Where can I start with troubleshooting the issue?. Your feedback is appreciated

UNIX OS (SunOS 5.10 Generic_150400-11 sun4v sparc SUNW,SPARC-Enterprise-T5220)

Derrick Au · ‎03-02-2015

Hi Reginald,

I am not familiar with the Unix version, but based on your problem description I believe the error lies between steps 1 and 2.

In Step 1, when cloning the Master (Unix0161), what state was it in (running/stopped)?

When importing/exporting 6.1 database onto another database server. Are you working off a backup of the database? Can you verify db connection for Unix026-2 (which database server is it connecting to)?

In Step 2, have you verified that Master was removed completely on Unix026-2?

HTH,

Derrick Au

Reginald Hill · ‎03-02-2015

Q: In Step 1, when cloning the Master (Unix0161), what state was it in (running/stopped)?

A: The master service was running

Q: When importing/exporting 6.1 database onto another database server. Are you working off a backup of the database?

A: Yes- And also a number of queries we executed on the database (Blank out License - Update the nodmst_alias to new hostname- Disable agents/adapters- Set system Queue to zero)

Q: Can you verify db connection for Unix026-2 (which database server is it connecting to)?

A: Yes

6.1 master.props file

JdbcDriver=oracle.jdbc.driver.OracleDriver

JdbcURL=jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = odm3dev-scan.kbm1.com)(PORT = 1521))(LOAD_BALANCE = YES)(CONNECT_DATA =(SERVICE_NAME = tdl6dev)))

Classpath=${TIDAL_HOME}/lib/Scheduler.jar:${TIDAL_HOME}/lib/ojdbc6.jar:${CLASSPATH}

CMDMasterPort=6600

JAVA_HOME=/apps/tidal/java/jre1.6.0_35/bin/sparcv9

JVMARGS=-Xms4096m -Xmx8192m

6.2 master.props file

Classpath=${TIDAL_HOME}/lib/Scheduler.jar:${TIDAL_HOME}/lib/ojdbc6.jar:${TIDAL_HOME}/lib/jetty-all-9.1.1.v20140108.jar:${CLASSPATH}

JdbcDriver=oracle.jdbc.driver.OracleDriver

JdbcURL=jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=yes)(ADDRESS=(PROTOCOL=TCP)(HOST=odm4dev-scan)(PORT=1521))(CONNECT_DATA=(SERVER=dedicated)(SERVICE_NAME=tdl62dev.kbm1.com)))

CMDMasterPort=6600

JAVA_HOME=/apps/tidal/java/jre1.7.0_75/bin/sparcv9

JVMARGS=-Xms4096m -Xmx8192m

Q: In Step 2, have you verified that Master was removed completely on Unix026-2?

A: Yes

Derrick Au · ‎03-02-2015

Hi Reginald,

Perhaps someone with more Oracle knowledge/Unix-based Tidal can jump in. As far as I can see, the Master props look okay in that the host and service name are explicitly defined differently.

Have you opened a ticket with Cisco Tech Support?

Are you stopping/starting Tidal service from Java/Web client? Could it be that your client manager props is pointing to Unix0161?

Also, have you tried installing 6.2 on a new VM instance rather from a cloned VM?

HTH,

Derrick Au

millennium

derrick.au@mlp.com