Wiley Enterprise manager offline issue

[Former Member]

Hello All,

The Wiley Enterprise Manager which was running smoothly went offline.

It is not getting started when i try to start. Am pasting the contents from log file 'IntroscopeEnterpriseManager.log' below,

************************************

************************************

Introscope Enterprise Manager failed to start because:

An error occurred while trying to start Isengard.

Press 'Enter' to acknowledge....

nager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"

12/07/11 05:42:15 PM GMT+05:30 [INFO] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private

12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Started hot config polling. Polling interval set to 60 seconds

12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager.ServerSocketFactory] Created Server Socket Factory: com.wily.jip.server.ext.DefaultServerSocketFactory

12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Using data directory: /usr/sap/ccms/wilyintroscope_sd2/data

12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] The system will store non-counter zero values.

12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] The system will shut down if there are Disk I/O errors in 5 continuous timeslices.

12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Using archive directory /usr/sap/ccms/wilyintroscope_sd2/data/archive

12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Reading Smartstor Metadata

12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Loading metadata file: data/metrics.metadata

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Finished reading Smartstor Metadata

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Thread priority set at 1

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Data tier 1 configured at collection frequency 15 seconds for 1 day

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Data tier 2 configured at collection frequency 60 seconds for 7 days

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Data tier 3 configured at collection frequency 300 seconds for 23 days

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] SmartStor Tiering time offset configured to 0:00

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] SmartStor conversion of Spool to Data time offset configured to 0 minute

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.Agent] Configured EM Global Live Metric count limit at 500000

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.Agent] Configured per-agent metric count limit at 50000

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.Agent] Configured EM Global Historical Metric count limit at 1200000

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Available processors is 8

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.ConnectionTicket] Agent connection tickets = 8

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.Agent] Agent automatic unmount delay configured to 60 minute(s).

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.TransactionTracer] Storage directory configured to /usr/sap/ccms/wilyintroscope_sd2/traces

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.TransactionTracer] Configured introscope.enterprisemanager.transactionevents.storage.queue.limit to 1000

12/07/11 05:42:17 PM GMT+05:30 [ERROR] [Manager] The EM failed to start. Unable to open the Perst backing store: /usr/sap/ccms/wilyintroscope_sd2/traces/traces_20111119.db

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Shutting down data persistence subsystem

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Shutting down the Isengard server

12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Orderly shutdown complete.

Kindly advice,

Thank You,

Regards,

Hasan

[guilherme_balbinot · Accepted solution]

Hello,

The new problem is that sometimes this historical trace and data might got corrupted due to abnormal termination of EM.

In this case please take following steps:

1. check if there is enough space in the directories /traces and /data.

2. use the script IndexRebuilder.sh in EM installation folder to try to rebuild the data corrupted.

3. If there is any error appearing during executing the script, that means the historical data got corrupted and cannot be rebuilt. Proceed to next item (4).

4. As mentioned in the section 2.17 "Enterprise Manager Corrupted Data Files" in the IntroscopeFAQ.pdf attached in the NOTE 797147, the solution is to delete the directories /traces and /data and restart your EM to re-generate these directories. The side effect is that you will lose all historical data that is stored in the Enterprise Manager.

Best regards,

Guilherme

[Former Member · Accepted solution]

Hello Guilherme,

The Issue is solved:)

Rebuild was not successful so deleted the traces and data folders and started the EM, it is online now.

Can you suggest what is the space to be allocated to both these folders(traces & data)?

Thanks for your detailed reponse

Regards,

Hasan

[Former Member · Accepted solution]

Hasan there is no rule for the space allocation..No SAP recommendation also..

I can tell you my space for these 2 directories..I have never faced a space issue till now..You can use this.

sm2adm> cd data

sm2adm> df -k .

Filesystem 1024-blocks Free %Used Iused %Iused Mounted on

/dev/hd2 4915200 1784948 64% 54067 12% /usr

sm2adm> cd traces

sm2adm> df -k .

Filesystem 1024-blocks Free %Used Iused %Iused Mounted on

/dev/hd2 4915200 1783588 64% 54067 12% /usr

[Former Member]

Thanks for your suggestions