JMS Messages lost after server restart

Hi All,
We have an environment where Oracle SOA 11g is configured to use Weblogic JMS (Database persistence). The JDBC stores have been created to hold the persistent JMS messages. However we have observed that after server restart the messages are getting lost from the queue (non consumed messages as well).
Is there any configuration which we are missing?
Regards
Subhankar

Hello Subhankar,
Which Weblogic version are you using? What are the configuration parameters of the JMS queue you defined? During server shutdown/restart, do you see any errors in the server log?
I would suggest you to raise a case with support as it may require an inspection of your environment and settings to find out the root cause.
Regards,
Anuj

Similar Messages

Nokia 5233 messages lost after phone restart

Hi,
I'm having a weird problem with my nokia 5233. It happened to me twice now that after restarting the device, I would lose all of my messages including messages in my folders and drafts and even sent messages. I have opted to save all my messages in my memory card, which is Kingston 4GB. What might be causing the problem and if I can recover my messages, as I have very important messages in there..........And if there is any solution on preventing this catastrophe again................
Thanks
Iftikhar

This seems to be a common issue with the S60 mobile operating system. No comment from Nokia regarding a resolution so far.
My E75 phone has also experienced the disappearing-messages-act saved in my SD card when my phone restarted from a low battery shut down. Inbox/Draft/Sent Items were completely wiped out.
I tried to change the SMS location from SD Card to Phone Memory then back to SD Card again.
I also tried to (safely & properly) remove the SD Card then reinserted it back. Still no go.
The worst part is that I spent 3 days searching the Internet and found that it's not rare for this problem to occur on an S60 platform yet no resolution from the web nor does Nokia offer any solution to it's customers.
They're about to lose a 12 year loyal and solid Nokia Fan (along with his friends and relatives to migrate to the Blackberry & iPhone Bandwagon) soon if they can't help us retrieve the important messages that was wiped out from our inbox. <sigh>..
Pictures and all other files stored in the SD Card are still intact. It's just my 3,000++ important SMS that's wiped out.

Messages are getting lost during server restart

Hi,
we have a clustered environment.
soa_server1, soa_server2, soa_server3 and osb_server1, osb_server2, osb_server3
Queues are configured on each server.
Overall process flow is (JMS Queue (configrued in soa_server1) --> BPEL --> mediator -->JMS (configrued in osb_server1) --> proxyService --> Target System.
When there is a need to bounce the server (start / stop) ; and to make sure messages are not lost during server bounce.
we are following the below procedure for server start
1) pause soa_server1 queues then bounce soa_server1
2) pause soa_server2 queues then bounce soa_server2
3) pause soa_server3 queues then bounce soa_server3
We are observing there is a message lost after server bounce...
thanks in advance
anvv sharma

Are you using XA connection factory? If no then this may cause message loss. It is also considered a best practice to configure error queue for JMS queues to avoid message loss (as a precautionary measure).
How did you find that messages are getting lost?
Regards,
Anuj

Canceling timers after server restart

hi,
i create a couple of timers. while the application server is up i can cancel them by getting the TimerService object of the bean it's associated with, calling getTimers() and cancelling the Timer objects returned from it.
if i restart the server (let's say it crashed), the timers created in the previous session are back to run - they are persistent by definition. but now i can't cancel them anymore: same getTimers() returns an empty Collection. i think this happens because the old timers from the previous session were not rebound to the new ejbcontext, or something like this.
my question is: how can i cancel timers, that were re-invoked after server restart.
thank you.
Message was edited by:
cyclid

Below are my tests that show canceling of timers working as expected:
Session bean methods:
public void createTimers()
{      System.out.println("### CREATE - a single-action timer that expires in 4s");
ctx.getTimerService().createTimer(4000, "single-action timer that expires in 4s");
System.out.println("### CREATE - an interval timer that expires in every 2s");
ctx.getTimerService().createTimer(2000, 2000, "interval timer that expires in every 2s");
public void cancelAllTimers() {
     System.out.println("### CANCEL - timers:");
     for (java.util.Iterator iter = ctx.getTimerService().getTimers().iterator(); iter.hasNext();) {
          Timer timer = (Timer) iter.next();
          System.out.println(" canceling ... " + timer.getInfo());
          timer.cancel();
public void logCurrentTime() {
     System.out.println("### CURRENT TIME - " + java.util.Calendar.getInstance().getTime());
public void ejbTimeout(Timer timer)
{     System.out.println("### EJB TIMEOUT - " + timer.getInfo());
Java Client test:
ejb.cancelAllTimers();
Thread.sleep(4000);
ejb.logCurrentTime();
ejb.createTimers();
Thread.sleep(8000);
ejb.cancelAllTimers();
ejb.logCurrentTime();
Thread.sleep(8000);
ejb.logCurrentTime();
Logs:
1. Shutdown servers while there is an interval timer
The log shows the interval timer came back and then was cancel after server restart
07/02/06 13:46:23 ### CANCEL - timers:
07/02/06 13:46:27 ### CURRENT TIME - Tue Feb 06 13:46:27 EST 2007
07/02/06 13:46:27 ### CREATE - a single-action timer that expires in 4s
07/02/06 13:46:27 ### CREATE - an interval timer that expires in every 2s
07/02/06 13:46:29 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:46:31 ### EJB TIMEOUT - single-action timer that expires in 4s
07/02/06 13:46:31 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:46:32 Shutting down OC4J...
C:\oc4j\10131_061009\j2ee\home>java -jar oc4j.jar
07/02/06 13:48:12 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
07/02/06 13:48:13 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:15 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:17 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:18 ### CANCEL - timers:
07/02/06 13:48:18 canceling ... interval timer that expires in every 2s
07/02/06 13:48:22 ### CURRENT TIME - Tue Feb 06 13:48:22 EST 2007
2. Cancel timers right after they were created
07/02/06 13:50:11 ### CANCEL - timers:
07/02/06 13:50:15 ### CURRENT TIME - Tue Feb 06 13:50:15 EST 2007
07/02/06 13:50:15 ### CREATE - a single-action timer that expires in 4s
07/02/06 13:50:15 ### CREATE - an interval timer that expires in every 2s
07/02/06 13:50:17 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:19 ### EJB TIMEOUT - single-action timer that expires in 4s
07/02/06 13:50:19 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:21 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:23 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:23 ### CANCEL - timers:
07/02/06 13:50:23 canceling ... interval timer that expires in every 2s
07/02/06 13:50:23 ### CURRENT TIME - Tue Feb 06 13:50:23 EST 2007
07/02/06 13:50:31 ### CURRENT TIME - Tue Feb 06 13:50:31 EST 2007

Sending a jms message from one server to another in a cluster fails..

Hi,
          My platform is wl6.1 sp7 two servers in a cluster...
          I have problems sending jms messages from one server to the other. When sending to a destination on the same server it works fine, but sending to the other server do not work. I get no exceptions when I send the message. The "Monitor all Active JMS Destinations..."->"Messages Received" column increase number of received messages for the remote server. But the onMessage method in the bean is not called(I am logging all calls to a file...)
          Any suggestions?
          And..
          My understanding is that the JNDINameReplicated default value is set to true? But when I don't set this value to true the jndi name is not replicated too the other server.
          (The state for both servers are Running in the admin console and listed servers in the cluster is 2....
          Server names:
          * bluej, biztalk-lab
          JMS connection factory:
          * xlink.jms.factory.commerceFactory, deplyed on both servers and for the cluster
          Destinations:
          * xlink.jms.service.report.biztalk-lab.Report for the biztalk-lab server active on 'biztalk-labJMSServer' JMS-server
          * xlink.jms.service.report.bluej.Report for the bluej server active on 'bluejJMSServer' JMS-server)
          ~b

Deployed to the bluej server:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>xlink.jms.service.report.bluej.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.bluej.Report</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <message-driven-descriptor>
          <destination-jndi-name>xlink.jms.service.report.bluej.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.bluej.Report</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <ejb-class>no.xlink.server.service.report.engine.jms.ReportBean</ejb-class>
          <transaction-type>Bean</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          </message-driven>
          </enterprise-beans>
          </ejb-jar>
          Deployed to the biztalk-lab server:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <message-driven-descriptor>
          <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <ejb-class>no.xlink.server.service.report.engine.jms.ReportBean</ejb-class>
          <transaction-type>Bean</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          </message-driven>
          </enterprise-beans>
          </ejb-jar>

Retaining listening channel password after server restart

Hi,
I have configured b2b email listening channel & everytime i restart the soa server, the password is blank.
Is there a way to retain/store the password after server restart?
Thanks
Ganesh

Hi Anuj,
I faced the problem with PS2 and now with PS3 also.
For me in listening channel, it does not store the password & during server startup, it tries to connect to email server & fails with invalid password or some error like that.
I am going to raise a SR today & will see how that goes.
Thanks
Ganesh

EJB projects failed after server restart

Hi Experts,
I had deployed some Web Dynpro projects and EJB projects. But everytime after server restarts or SDM restarts, the EJB projects will gone. I have to redeploy the EJB projects to make the WDP projects works, or else the WDP projects will hit nullpointer which saying not able to find the specific EJB.
Any idea?
Thanks & Regards,
Sarah

Thanks
wawoodwa , this command solved my problem!!!
On other sites I found command:
"Update-MailboxDatabaseCopy –Identity ‘DB2’ –CatalogOnly" it was not working, I got the same error as OldSchoola.

Message lost after rollback

I have three queues setup. A Base queue, Backout queue and a Hold queue.
A test application reads from Base queue and rollback() the session. After attempting to deliver the message two times, the JMS application sends the message to Backout queue after the third rollback().
My application (MsgRequeueApp) reads the message from Backout queue and waits for some time, adds some headers for its own use, sends the message again to Base Queue. The test application reads the re-queued message and rollback() three times. At the end of the third rollback(), the message is lost. I was expecting the message to go back to Backout Queue.
1. MsgRequeueApp does not log any new messages. So, it is not reading any new message.
2. I am monitoring the queues from weblogic's Admin console. The message is not present in Base Queue / Backout queue / Hold queue.
Note: There is a different logic that would send messages to Hold queue. But I am not testing that right now.
Here is the log after I enabled logging (Headers, Body)
####<Feb 4, 2013 10:56:31 AM CST> <> <> <1359996991531> <116727> <> <> <SystemModule-0!TESTBOQ> <ConsumerCreate> <<anonymous>> <MC:CA(local):OAMI(DefaultServer.jms.connection19.session20.consumer22)> <> <>
####<Feb 4, 2013 10:56:31 AM CST> <> <> <1359996991552> <840437> <> <> <SystemModule-0!TESTBASEQ> <ConsumerCreate> <<anonymous>> <MC:CA(local):OAMI(DefaultServer.jms.connection23.session24.consumer26)> <> <>
####<Feb 4, 2013 11:05:11 AM CST> <BEA1-00037A05C5399E472B1E-574C53746F72655F44656661756C74446F6D61696E5F46696C6553746F72652D30> <> <1359997511266> <249265> <ID:<237345.1359997510782.0>> <> <SystemModule-0!TESTBASEQ> <Produced> <<anonymous>> <> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode><mes:JMSExpiration>0</mes:JMSExpiration><mes:JMSPriority>4</mes:JMSPriority><mes:JMSRedelivered>false</mes:JMSRedelivered><mes:JMSTimestamp>1359997510782</mes:JMSTimestamp><mes:Properties/></mes:Header><mes:Body><mes:Text>TestCase1</mes:Text></mes:Body></mes:WLJMSMessage>> <>
####<Feb 4, 2013 11:05:22 AM CST> <> <> <1359997522152> <866698> <ID:<237345.1359997510782.0>> <> <SystemModule-0!TESTBASEQ> <Retry exceeded> <<WLS Kernel>> <> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode><mes:JMSExpiration>0</mes:JMSExpiration><mes:JMSPriority>4</mes:JMSPriority><mes:JMSRedelivered>true</mes:JMSRedelivered><mes:JMSTimestamp>1359997510782</mes:JMSTimestamp><mes:Properties/></mes:Header><mes:Body><mes:Text>TestCase1</mes:Text></mes:Body></mes:WLJMSMessage>> <>
####<Feb 4, 2013 11:05:22 AM CST> <> <> <1359997522152> <885695> <ID:<237345.1359997510782.0>> <> <SystemModule-0!TESTBOQ> <Produced> <<WLS Kernel>> <> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode><mes:JMSExpiration>0</mes:JMSExpiration><mes:JMSPriority>4</mes:JMSPriority><mes:JMSRedelivered>false</mes:JMSRedelivered><mes:JMSTimestamp>1359997510782</mes:JMSTimestamp><mes:Properties/></mes:Header><mes:Body><mes:Text>TestCase1</mes:Text></mes:Body></mes:WLJMSMessage>> <>
####<Feb 4, 2013 11:05:31 AM CST> <BEA1-00077A05C5399E472B1E-574C53746F72655F44656661756C74446F6D61696E5F46696C6553746F72652D30> <> <1359997531207> <716965> <ID:<237345.1359997530728.0>> <> <SystemModule-0!TESTBASEQ> <Produced> <<anonymous>> <> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode><mes:JMSExpiration>0</mes:JMSExpiration><mes:JMSPriority>4</mes:JMSPriority><mes:JMSRedelivered>false</mes:JMSRedelivered><mes:JMSTimestamp>1359997530728</mes:JMSTimestamp><mes:Properties/></mes:Header><mes:Body><mes:Text>TestCase1</mes:Text></mes:Body></mes:WLJMSMessage>> <>
####<Feb 4, 2013 11:05:31 AM CST> <BEA1-00027A05C5399E472B1E-574C53746F72655F44656661756C74446F6D61696E5F46696C6553746F72652D30> <> <1359997531209> <972000> <ID:<237345.1359997510782.0>> <> <SystemModule-0!TESTBOQ> <Consumed> <<anonymous>> <MC:CA(local):OAMI(DefaultServer.jms.connection19.session20.consumer22)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode><mes:JMSExpiration>0</mes:JMSExpiration><mes:JMSPriority>4</mes:JMSPriority><mes:JMSRedelivered>false</mes:JMSRedelivered><mes:JMSTimestamp>1359997510782</mes:JMSTimestamp><mes:Properties/></mes:Header><mes:Body><mes:Text>TestCase1</mes:Text></mes:Body></mes:WLJMSMessage>> <>
####<Feb 4, 2013 11:05:41 AM CST> <> <> <1359997541259> <230216> <ID:<237345.1359997530728.0>> <> <SystemModule-0!TESTBASEQ> <Retry exceeded> <<WLS Kernel>> <> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode><mes:JMSExpiration>0</mes:JMSExpiration><mes:JMSPriority>4</mes:JMSPriority><mes:JMSRedelivered>true</mes:JMSRedelivered><mes:JMSTimestamp>1359997530728</mes:JMSTimestamp><mes:Properties/></mes:Header><mes:Body><mes:Text>TestCase1</mes:Text></mes:Body></mes:WLJMSMessage>> <>
####<Feb 4, 2013 11:05:41 AM CST> <> <> <1359997541259> <250889> <ID:<237345.1359997530728.0>> <> <SystemModule-0!TESTBOQ> <Produced> <<WLS Kernel>> <> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode><mes:JMSExpiration>0</mes:JMSExpiration><mes:JMSPriority>4</mes:JMSPriority><mes:JMSRedelivered>false</mes:JMSRedelivered><mes:JMSTimestamp>1359997530728</mes:JMSTimestamp><mes:Properties/></mes:Header><mes:Body><mes:Text>TestCase1</mes:Text></mes:Body></mes:WLJMSMessage>> <>
####<Feb 4, 2013 11:05:41 AM CST> <BEA1-000A7A05C5399E472B1E-574C53746F72655F44656661756C74446F6D61696E5F46696C6553746F72652D30> <> <1359997541304> <943009> <ID:<237345.1359997530728.0>> <> <SystemModule-0!TESTBOQ> <Consumed> <<anonymous>> <MC:CA(local):OAMI(DefaultServer.jms.connection19.session20.consumer22)> <<?xml version="1.0" encoding="UTF-8"?>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message"><mes:Header><mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode><mes:JMSExpiration>0</mes:JMSExpiration><mes:JMSPriority>4</mes:JMSPriority><mes:JMSRedelivered>false</mes:JMSRedelivered><mes:JMSTimestamp>1359997530728</mes:JMSTimestamp><mes:Properties/></mes:Header><mes:Body><mes:Text>TestCase1</mes:Text></mes:Body></mes:WLJMSMessage>> <>
Can someone help me figure out how I can debug what is going wrong here?

Do you have a redelivery limit set on the producer or the destination? If you do, a message may be discarded once the limit is reached depends on your delivery-failure-params on the destination. You can configure to have the messages put into an error destination once they reach their redelivery limit.

How to avoid BPEL process deployment after server restart

Hi,
Message flow in my application is as below
BPEL1 --> ESB --> BPEL2
After every server restart the ESB is failing to invoke a perticular operation of BPEL2 service. All other operations of BPEL2 are working fine.
We are redeploying the BPEL2 proccess everytime the server restart happens to fix this issue. As a temporary fix, we are trying to bypass the ESB and directly invoke BPEL2 from BPEL1, but not sure if this solution works.
Can someone please suggest me as to how to avoid redeployment of the BPEL2 process?
Please let me know incase any additional information is required.
Thanks in advance.
Regards,
Manoj
Edited by: user11290555 on Jun 20, 2010 3:18 PM

Hi,
try the SOA forum. This here is for JDeveloper and ADF related questions
Frank

JNDI - rebind required after server restart

We are using a third party JMS Provider (we have to use this provider implementation as opposed to WLS Provider), which requires a JNDI implementation. We can use the Sun File JNDI implementation, but seeing as WLS is in the environment, binding the JNDI names into WLS seemed the natural thing to do. This works great, except that we have to bind after each server start up (as the WLS JNDI naming is not persistent across server restart).
I was wondering if anyone had any 'neat' tricks or ideas around this, aside from startup class.

JMS has a ForeignJMSProvider config option to do this I believe. 9.0 will also support this more generally.

How to send a JMS message to a server ....

Hi
I want to know how to send a jms message to a Queue and that is in a different server...
How to send A message using a application client to a Message queue That is in another Machine(Server is in another machine )
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.cosnaming.CNCtxFactory");
env.put(Context.PROVIDER_URL, "iiop://127.0.0.1:3700/");
InitialContext initialContext = new InitialContext(env);
connectionFactory = (ConnectionFactory) initialContext.lookup("jms/ConnectionFactory");
queue = (Queue) initialContext.lookup("jms/Queue");
get a NameNotFoundException
Anyone have an Idea
thanks
Ishkmi
Message was edited by:
ishkmi

ok..try this..insert the ip address of the server where ur app server is
running . i understand ur client and server is running on diff machines.
ip address 127.0.0.1 is for local host. it tries to look for the server in
same system as the client.
substitue ip address of server in below line instead of 127.0..0.1
env.put(Context.PROVIDER_URL, "iiop://127.0.0.1:3700/");
best of luck ..lemme know..

Web Service from stateful Session Bean deleted after server restart

Hi,
i created a stateful session bean and from this a web service.
I am able to deploy it and it works really fine.
My problem is: after a server restart the web service is gone and i
have to deploy it again.
I have some other web services (but these are web services from stateless session beans)
but they "survive" the server restart.
I don't want to deploy the web service after every server restart, did I forget something or
is it a general problem of stateful session beans or web services?
Thanks in advance
Jens

Hello Björn,
I am not quite sure what your problem is but did you have a look at these articles:
http://help.sap.com/saphelp_nw04/helpdata/en/4d/993441c73cef23e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/be/2e2c4142aef623e10000000a155106/frameset.htm
I hope they can give you some idea.
Regads
Vyara

Missing data after server restart

Hi,
We restarted our MDM server at the OS level last night. Everything seemed okay after the restart. However, when our users came in this morning, they found that some data was missing from a table. We have a Material repository with 3 main tables. Some data which have previously been populated was not appearing in our Products Detail table, the largest of the three. A large number of rows in the table had columns that failed to load with data on the repository auto-start that occured after the server restart. The auto start value in the mds.ini file was set at 300 (5 minutes) as we had seen this iisue happen once before, and thought that may help.
A stop and restart of the repository corrected the issue. Is there anything we could have done to prevent this? Is it worthwhile to try increasing the auto start delay again? Validating detail data after every server restart is not an effective option.
MDM version: 7.1 SP08
OS: AIX DB: Oracle 11g
Thanks!
Dave

Hi Dave,
I meant that when you load repository using Immediate data is loaded from .acl files (accelerator files) in a async manner.
Whereas when you load by Update Indices new acl files are generated.
Below men6tioned is a comparision between the 2 ways of laoding repository:
Load Repository Immediate
o Loads indexes from accelerator files instead of being regenerated by reading the data them from the DB and creating the index.
o Automatically builds indexes stored in out-of-date accelerator files.
o Is usually fast.
 Load Repository with Update Indices
o Rebuilds all MDM indexes files by reading and indexing data stored in the DB. The results are flushed on disk as accelerator files.
o Necessary by repository schema changes or if any error occurs.
o Might take significant amount of time to complete.
So when you observe some visual data impact in your repository it is good idea to rebuild indexes.
I guess we cannot schedule this as default behavior is to load by immediate even through the inin parameter.
as a best practice one can do this by fixing a time frame eg monthly depending on data/schema changes.
Thanks,
Ravi

Can't connect to EM after server restart

Hope somebody can help me with this problem.
I have a 10g RAC installation and after a restart of one of the DB_servers i wasn't able to reach the EM console. I'm running on Linux OS.
This is what i have done:
- emctl start dbconsole (its started without problems)
I have checked the portlist.ini file to ensure that im using correct port. It says:
E.M http port : 1158 - E.M agent port :3938
I use Mozilla with url: http://servername:1158/em/console/ with no luck.
It doesnt understand the url and it routed to googel search.
This actually worked before my restart.
Could someone give me some hints please.
Rob

This is what i found in the emoms.trc
Is this saying you somethin ?
java.sql.SQLException: ORA-01089: immediate shutdown in progress - no operations are permitted
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:111)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:330)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:287)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:742)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:214)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:953)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1260)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3290)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3334)
at oracle.sysman.util.jdbc.ConnectionWrapper._applySessionParams(ConnectionWrapper.java:2971)
at oracle.sysman.util.jdbc.ConnectionWrapper.<init>(ConnectionWrapper.java:181)
at oracle.sysman.emSDK.svc.conn.FGAConnection.<init>(FGAConnection.java:115)
at oracle.sysman.emSDK.svc.conn.FGAConnectionCache.getFGAConnection(FGAConnectionCache.java:192)
at oracle.sysman.emSDK.svc.conn.ConnectionService.getSystemConnection(ConnectionService.java:683)
at oracle.sysman.emdrep.notification.NotificationMgr.getConnection(NotificationMgr.java:252)
at oracle.sysman.emdrep.notification.NotificationMgr.resetConnection(NotificationMgr.java:298)
at oracle.sysman.emdrep.notification.NotificationMgr.run(NotificationMgr.java:1190)
2006-09-11 15:28:52,360 [NotificationMgrThread] ERROR jdbc.ConnectionWrapper _applySessionParams.2980 - SQLException message: ORA-01089: immediate shutdown in progress - no operations are permitted
Rob

SnapDrive transport protocol settings lost after service restart.

Hi everyone,
On one of our SQL Servers we have SnapDrive v.6.4.2, OS is Windows Server 2008 SP2, the server is in a workgroup, not in a AD Domain.
In SnapDrive transport protocol settings we have a storage system defined and everything works fine, but after restarting the SnapDrive service (mostly because of a server restart) the storage settings disappear (the storage system is no longer defined) and SnapDrive cannot see the VMDK LUNs, therefore SnapManager cannot take SQL Server backups.
Any help or suggestions regarding a solution to this problem will be greatly appreciated.
Regards,
Sezgin

I am experiencing the same issue and the OS is Windows server 2003 SP2. Even after adding the transport protocol settings I dont see LUNs getting displayed.

JMS Messages lost after server restart

Similar Messages

Maybe you are looking for