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

Similar Messages

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

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

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.

Users missing after server restart

Hello,
I have had 2 servers in the past week loose all the user accounts after a server restart. In both cases I had to restore from backup. Anyone else have this happen to them?
Thanks!

Hi Henrique,
How are you restarting your server?
The roles and users are present in the data\ldap folder on your server folder, by any chance are they getting deleted?
-Faisal
http://www.weblogic-wonders.com

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

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.

OC4J 9.0.4 standalone : webapp not bound after server restart

Hello,
A strange thing happened to an OC4J 9.0.4 instance on AIX 5.2:
- I started the instance.
- I deployed an application using:
java -jar ${OC4J_HOME}/admin.jar ormi://localhost admin <pwd> -deploy -file cfj.ear -deploymentName cfj
java -jar ${OC4J_HOME}/admin.jar ormi://localhost admin <pwd> -bindWebApp cfj webcfj http-web-site /cfj
- I tested the application: no problem.
- Then I stopped the instance.
- The day after, I restarted my instance.
The problem is that the application was no more bound to /cfj, although everything was fine in http-web-site.xml.
I ran the "-bindWebApp" admin.jar stuff, and the application was ok again.
Did anyone have such a problem ? It is the first time for me, and it happend on a production system ! Any idea on how to fix it ?
Thanks in advance for any advice/information,
Pierre Laroche

Hello Glin,
It happened again with another application named but, which is now the last application listed in http-web-site.xml instead of cfj. Here are some excerpt from the xml files:
server.xml
<application name="bep" path="../applications/bep.ear" auto-start="true" />
<application name="ccl" path="../applications/ccl.ear" auto-start="true" />
<application name="cmt" path="../applications/cmt.ear" auto-start="true" />
<application name="eau" path="../applications/eau.ear" auto-start="true" />
<application name="eee" path="../applications/eee.ear" auto-start="true" />
<application name="erp" path="../applications/erp.ear" auto-start="true" />
<application name="tsc" path="../applications/tsc.ear" auto-start="true" />
<application name="zou" path="../applications/zou.ear" auto-start="true" />
<application name="sms" path="../applications/sms.ear" auto-start="true" />
<application name="eir" path="../applications/eir.ear" auto-start="true" />
<application name="cfj" path="../applications/cfj.ear" auto-start="true" />
<application name="but" path="../applications/but.ear" auto-start="true" />
http-web-site.xml
<default-web-app application="default" name="defaultWebApp" />
<web-app application="default" name="dms0" root="/dms0" />
<web-app application="default" name="dms" root="/dmsoc4j" />
<web-app application="default" name="init" load-on-startup="true" root="/init" />
<web-app application="bep" name="webbep" load-on-startup="true" root="/bep" />
<web-app application="ccl" name="webccl" load-on-startup="true" root="/ccl" />
<web-app application="cmt" name="webcmt" load-on-startup="true" root="/cmt" />
<web-app application="eau" name="webeau" load-on-startup="true" root="/eau" />
<web-app application="eee" name="webeee" load-on-startup="true" root="/eee" />
<web-app application="erp" name="weberp" load-on-startup="true" root="/erp" />
<web-app application="tsc" name="webtsc" load-on-startup="true" root="/tsc" />
<web-app application="zou" name="webzou" load-on-startup="true" root="/zou" />
<web-app application="sms" name="websms" load-on-startup="true" root="/sms" />
<web-app application="eir" name="webeir" load-on-startup="true" root="/eir" />
<web-app application="cfj" name="webcfj" load-on-startup="true" root="/cfj" />
<web-app application="but" name="webbut" load-on-startup="true" root="/but" />
<access-log path="../log/http-web-access.log" />
It seems correct to me. Any idea ?
Thanks,
Pierre

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

EAR project not starting after server restart.

Hello all,
I have made a plain EAR project that contains a WAR file which again contains some servelets and static stuff like images and JavaScript files. The project does not use any SAP specific functionality and is hence a regular J2EE EAR project that in theory could run on all compliant J2EE servers.
The problem is that when the server restarts the project does not start (not even lazily, that is upon a request being made to it). In other words I have to start it manually by using Visual Administrator or redeploying. Naturally this approach is not a long term solution.
In the application-j2ee-engine.xml file of the EAR project I have tried to set the parameter start-up to always with no luck as documented here:
[http://help.sap.com/saphelp_nw04s/helpdata/en/25/0c08f3981343609d4045f8acaa0a76/frameset.htm]
The server is a 7.0 sp 14.
I have succesfully deployed the project on older servers with no problems.
Any ideas?

Hi,
Undeploy your application from SAP AS Java, e.g. via Visual Admin, and then redeploy it. If it does not start automatically, start it manually from VA. Check if you restart the server, the application is also started up correctly.
Besides that, does your application depends on another application, library, or service? (i.e. uses another appllication, library or service)
If so, did you explicitly declared this relation via the reference tag in application-j2ee-engine.xml ?
Kind regards,
Tsvetomir

Transactional replication triggers disabled after server restart

Hello Everyone,
I have been facing this issue since couple of days. I have configured transactional replication with updatable subscriber in sql server 2008 R2. It was working fine till date. Recently we are facing an issue where subscriber whenever restarts, one
of the table's replication triggers(insert, update and delete) are disabled automatically. We have to manually enable all the triggers for that table. Other tables are working fine. Please help. Thanks in advance.
Regards,
Sai

Have you checked information from replication monitor?
You should disable all triggers because you don't want SQL Server to fire the trigger on the Subscriber database when the database receives an insert, update, or delete operation. Because the trigger has already fired on the Publisher database, firing the trigger
on the Subscriber database might repeat the transaction.
http://technet.microsoft.com/en-us/library/ms151718(v=sql.110).aspx
http://msdn.microsoft.com/en-us/library/ms152529.aspx

Human Task expiration after server restart

I am having serious problems related to BPEL human task expiration in SOA 11g. If my server is down or if I restart my server and any human task has its expiration during this server downtime, then this human task never exprires. What I want is that any human task should get expired at its expiration date-time irrespective of server state. Please help.

I am having serious problems related to BPEL human task expiration in SOA 11g. If my server is down or if I restart my server and any human task has its expiration during this server downtime, then this human task never exprires. What I want is that any human task should get expired at its expiration date-time irrespective of server state. Please help.

Client lookup after Server restart

Hi,
I'm experiencing problems on client side when reconnecting to a remote object that has been unbound and rebound again.
Scenario:
1. The server performs a rebind of the remote object (Naming.rebind(name,obj)
2. Client gets a reference to the remote object with Naming.lookup(name)
3. The server unbind the remote object:
- Naming.unbind(obj)
- UnicastRemoteObject.unexportObject(obj,true);
4. The server rebind again a new instance of the remote object on the same name.
5. On client side, any call to the remote object throws a java.rmi.NoSuchObjectException, even after a new Naming.lookup(name).
6. Re-start the client and all is OK !
Any help ?
Thank you.
Christophe

After rebinding the same server instance it will (most probably) use a different port number.
This is why the original reference you have at the client does not work because it is sending messages to a port that is no longer in use. After restarting the client, it no doubt does another lookup, gets a new reference (with the correct port number) and communication is restored.

Missing data after server restart

Similar Messages

Maybe you are looking for