Here is a suggested plan of action.

1. Backup your SPA DB to a different place (this is not a mandatory, but

recommended).
2. Un-register the Symmetrix arrays from SPA GUI
3. Close spa
4. Stop stpd service - stordaemon shutdown storstpd -immediate
5. Stop smas service - /etc/init.d/smas stop
6. Stop the Smas_db service - ./smas_mysql_unix_helper.sh -k
7. Delete/move the spa_registratons file under \EMC\SYMAPI\stp\spa
8. Delete/move all the policy files under EMC\SMAS\JBoss\server\default-
em\data\persistency\SPA_POLICIES
9. Restart Smas_db service - ./smas_mysql_unix_helper.sh -s
10.Restart smas - /etc/init.d/smas start
11.Restart stpd - stordaemon start storstpd
12.Start SPA
13.Redo the registration in the GUI and monitor for an hour or 2 to see if
performance data starts showing back up.

./smas_mysql_unix_helper.sh -s to start the db

cd /opt/emc/SMAS/jboss/server/default-em/data/msq/
./smas_mysql_unix_helper.sh -k

Service Request #56264222

You might also want to check to see if the service is running (STORDAEMON LIST -V),
and then restart it. (storstpd)

Goal

What logs do I need to gather to troubleshoot a Unix / Linux Symmetrix Management

Application Server (SMAS) issue?
What logs do I need to troubleshoot a Linux Unisphere for VMAX issue?

Environment

EMC SW: Symmetrix Management Application Server SMC/SPA

EMC SW: Unisphere for VMAX

EMC SW: Symmetrix Management Console (SMC) 7.2.X and above.

EMC SW: Symmetrix Performance Analyzer (SPA) 2.1.X and above.

Resolution

A request has been made for this information to be included in EMCGrab for UNIX
operating systems.

1. Installation Log:
/opt/emc/SMAS/installerlogs
EMC_SMAS_INSTALL_xx_xx_xx_xx_xx.log
2. Runtime Logs:
/opt/emc/SMAS/jboss/bin
Run, Run_b1 and Shutdown logs
3. Default Server Logs:
/opt/emc/SMAS/jboss/server/default-em/log
boot and smas log
4. SMC litewave logs:
/opt/emc/SMAS/jboss/server/default-em/deploy/smc.ear/smc.war/WEB-INF/log
litewave.trc
5. SPA Litewave logs:
/opt/emc/SMAS/jboss/server/default-em/deploy/spa.ear/spa.war/WEB-INF/logs
litewave.trc
SPAPerformance.log

6. SPA DB error logs:

/opt/emc/SMAS/jboss/server/default-em/data/msq/data
HostName.err

7. MySQL Server Configuration File

/opt/emc/SMAS/jboss/server/default-em/data/msq
my.ini
8. SMC ini file
/opt/emc/SMAS/jboss/server/default-em/deploy/smc.ear/smc.war/WEB-INF
eccweb.ini
9. SPA ini file
/opt/emc/SMAS/jboss/server/default-em/deploy/spa.ear/spa.war/WEB-INF
eccweb.ini
10. Audit Logs:
/opt/emc/SMAS/jboss/server/default-em/data/auditlog
11. hs_*.err files /opt/emc/SMAS/jboss/bin

12. jboss.xml /opt/emc/SMAS/jboss/server/default-em/deploy/domina-symm.ear/domain-

symm-ejb.jar/META-INF

13. spa-ds.xml /opt/emc/SMAS/jboss/server/default-em/deploy

14. The most recent symapi log file and storspd log located in /var/symapi/log

Starting with the 4.4.5 version of the emcgrab utility you can run:
./emcgrab.sh -smas

NOTE: This flag is ineffective if the installation is not in the "default" SMAS
locations

Notes Update 5/22/2012

This log collection is compatible for the Unisphere for Vmax and SMAS. The
directory structure has not changed in Unisphere for VMAX. The directory structure
has remained the same.
Currently SMAS runs on Solaris and Linux based systems. This solution relates to
those Operating systems.

Refer to KB article 14418 for Unix based SMAS logs

Refer to KB article 14192 for WINDOWS based SMAS logs.

Refer to KB article 9172 for Solutions Enabler Installation log files on Unix and
Windows.

What are the procedures for Opening a Solutions Enabler OPT? - 13083

___________________________________________________________________________________
______________________--

Goal How to move SPA database to a different location when the disk is completely
full and SPA has stopped opening.
How to install SPA to a different location keeping the historical data intact.

Issue SPA does not open as the disk is full so can not backup/restore database.

Environment EMC SW: Symmetrix Performance Analyzer (SPA)

EMC SW: Symmetrix Management Appication Server (SMAS)

Resolution PLEASE READ THIS ENTIRE PROCESS BEFORE PROCEEDING. Take special note of
the warnings below.

Perform the below steps:

1. Unregister all Symmetrix for SPA data collection.

2. Stop the SMAS Service (EMC Symmetrix Management Application Server Service)

3. Please wait a few minutes and then stop the SMAS DB Service (EMC_smasdb Service)

4. Warning: It is important to check that the database shutdown correctly

- Please ensure there are no critical errors in ...\SMAS\jboss\server\default-

em\data\msq\data\<hostname>.err while shutting down the database

- Please ensure that the following file does not exist

...\SMAS\jboss\server\default-em\data\msq\data\<hostname>.pid

If the <hostname>.pid file exists then the database was not shut down cleanly.

Warning: Do not proceed with relocating the database if you suspect that the
database has errors or was not shut down cleanly.

5. Copy the entire "\Program Files\EMC\SMAS\jboss\server\default-em\data\msq\data"

folder to another disk.

6. Reinstall SMAS with SPA to a new location with sufficient disk space.

7. Warning: Do not register any Symmetrix for SPA data collection.

8. Stop the SMAS Server Service (EMC Symmetrix Management Application Server
Service)
9. Please wait a few minutes and then stop the SMAS DB Service (EMC_smasdb Service)

10. Overwrite the data folder in the new ..\SMAS\jboss\server\default-em\data\msq

directory with the entire "data" directory that was previously copied during step
5.

11. Restart the SMAS DB Service (EMC_smasdb Service)

12. Restart the SMAS Server Service. (EMC Symmetrix Management Application Server
Service)

13. Register Symmetrix for SPA data collection.

Warning : Failing to stop the service before copying and pasting can cause the
database corruption.
The backup/restore on the same O.S. but different bits would work with Version 2.1
and up.

Warning :

Copies of SPA Databases can only be moved to equivalent SMAS install versions and
on equivalent Operating systems from which the original copy was taken.
Examples : The database backup/restore taken from a 32bit O.S. can be moved to a 64
bit O.S of the SAME TYPE, Win to Win, Linux to Linux is ok.
Currently the database backup/restore cannot be moved from
one type of O.S to another type of O.S. For example, Linux to Windows. The O.S.
types MUST MATCH !
The SMAS install kits must be exactly the same. Same version,
and same 32/64 bit kit type.

Failure to follow these instructions will result in the database being lost or
damaged.

Please note, Before attempting this procedure if you have any questions or doubts
please open an OPT with SPA Engineering and mention this primus case.