Interface's parent

how can an interface has a parent? the parent i want is an abstract class. thanks

all those interfaces are actually DAOs. I want my DAOs to have the same parent. In the parent I want to define Connection as an instance variable with setter/getter. That connection will be passed from the DAO Factory. DAO methods will use that Connection to complete their work. This way I can make sure that in a use-case all DAOs use the same connection.
So instead of
public interface EmployeeDAO {
  public Employee getEmployeeById( int employeeId) throws EmployeeNotFoundException;
public class MSSqlServerEmployeeDAO implements EmployeeDAO {
  public Employee getEmployeeById( int employeeId) throws EmployeeNotFoundException {...}
}I would have
public abstract class ParentDAO {
private Connection connection = null;
public void setConnection(connection) {this.connection = connection;}
public Connection getConnection() {return this.connection;}
public abstract class EmployeeDAO extends ParentDAO {
  public abstract Employee getEmployeeById( int employeeId) throws EmployeeNotFoundException;
public class MSSqlServerEmployeeDAO extends EmployeeDAO {
  public Employee getEmployeeById( int employeeId) throws EmployeeNotFoundException {...}
}What do you think?

Similar Messages

  • Event Log: Interface Dot11Radio0, parent lost: Had to lower data rate

    Hi,
    AIR-AP1242
    Firmware: 12.3(8)JEB
    AP -> WGB mobil station
    The event log from WGB have often this warning:
    %DOT!!-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Had to lower data rate
    Way?...
    It is the first installation with this description.

    Is the client able to associate to the AP and transfer data. This error message genrally indicate a weak signal strength or a bad link. Move the client to a different location and check if that works.

  • Interface Dot11Radio0, cannot associate: No matching SSID

    Hi all, I have a problem with a P2P Bridge with a couple of Aironet 1242AG.
    Sometimes this Bridge goes down, and if I change Channel, it goes up.
    When Bridge is down I can see this log in NoRoot:
    *Apr 23 04:12:20.002: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP XXXX-Root 0014.1b60.9230 [None WPA PSK]
    *Apr 23 04:12:20.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Apr 23 04:12:20.008: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: authenticate response status (12) denied
    *Apr 23 04:12:20.069: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP XXXX-Root 0014.1b60.9230 [None WPA PSK]
    *Apr 23 04:12:20.079: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Received deauthenticate (2) not valid
    *Apr 23 04:12:20.081: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Apr 23 04:12:31.049: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: No matching SSID
    *Apr 23 04:13:32.392: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: Rcvd response from 0014.1b60.9230 channel 6 3669
    *Apr 23 04:18:46.404: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: Authenticating
    *Apr 23 04:30:18.666: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP XXXX-Root 0014.1b60.9230 [None WPA PSK]
    *Apr 23 04:30:18.666: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    I can see this log in Root:
    7w4d: %DOT11-7-AUTH_FAILED: Station 001c.f663.1110 Authentication failed
    7w4d: %DOT11-4-MAXRETRIES: Packet to client 001c.f663.1110 reached max retries, removing the client
    7w4d: Client 001c.f663.1110 failed: reached maximum retries
    7w4d: %DOT11-7-AUTH_FAILED: Station 001c.f663.1110 Authentication failed
    I don't understand "No matching SSID" and authentication error, the Wpa-psk and Ssid are the same.
    Do you have idea? I suppose a RF problem.
    Regards

    Hi,
    The "no matching SSID" appears when your non-root bridge tries to associate to a given SSID and does not detect any parent offering that SSID...
    This seems to indicate (IMHO) a RF problem... you may want to try to monitor the link quality between your root and non root. If the signal is lots, then you would typically get this no matching SSID message while the non-root tries to reconnect without success.
    Which code are you running on these APs?
    Jerome

  • Aironet 1300 radio keeps on shutting down

    Hi,
    I have a problem with the wireless bridge connection using aironet 1300. It work fine before.no changes were done. The problem is that the radio keeps on shutting down.in the web interface radio is enabled but down. i have to manually diable it then enable it back to resolve the issue. Problem is random and this is happening on both aironet. Below is the log.
    on the first aironet:
    1 Mar 31 02:20:59.444 Error Interface Dot11Radio0, changed state to up
    2 Mar 31 02:20:59.443 Warning Interface Dot11Radio0, Associated To AP UPAdminBridge 001e.4a05.b820 [None]
    3 Mar 31 02:20:59.389 Error Interface Dot11Radio0, changed state to down
    4 Mar 31 02:20:59.339 Warning Interface Dot11Radio0, parent lost: Received deauthenticate (2) not valid
    5 Mar 31 01:24:51.062 Error Interface Dot11Radio0, changed state to up
    6 Mar 31 01:24:51.061 Warning Interface Dot11Radio0, Associated To AP UPAdminBridge 001e.4a05.b820 [None]
    on the second aironet:
    1 Mar 17 09:30:42.107 Information Interface Dot11Radio0, Station UP-ASBridge 001e.f7f1.abc0 Reassociated KEY_MGMT[NONE]
    2 Mar 17 09:30:41.971 Information Interface Dot11Radio0, Deauthenticating Station 001e.f7f1.abc0 Reason: Previous authentication no longer valid
    3 Mar 17 09:30:41.971 Warning Packet to client 001e.f7f1.abc0 reached max retries, removing the client
    regards,
    Christian

    Verify that when the radio interface is shutdown, the workstations can connect to the server immediately. Also ping from the AP to server and workstations to verify if there is any difference seen to the results seen prior to the radio interface being shut down.

  • Problems with external context mapping

    Hi ,
    I am having the following problems with external context mapping from one WD component to another.
    Problem description:
    In the <i>Component Interfaces</i> I have defined a WD interface "InfA".
    In the <i>interface controller</i> of this compoenent,I have ContextA and attributeA(cardinality 1..1).The contextA is marked as an "Input Element".
    Now my webdynpro componentB adds InfA as used component.In componentB I decalre a contextB with attributeB and map it to contextA to set up the external context mapping.
    Now I expect that if any webdynpro component implements this WD interface InfA ,he has access to contextA with the data getting filled from contextB.
    After i have created the component for the used component I try to fill values in the source node contextB thru this code:
    wdContext.currentContextB.setB(value);
    But in the runtime I keep getting error nullPointerException for nodeContextB,suggesting that the mapping has not been completed.
    Can anyone suggest due to what the error can come ,and, if its a webdynpro bug ,is there a workaround??
    Thanks in advance for your help.
    Best regards
    Sourav

    HI,
    Valery : I personally checked  by doing the example, if the names of value attribute are different in the child's interface and parents component controller then it throws the exception.
    Sourav: NullPointer Exception is thrown when something is not properly initialised, if in the main component the cardinality of mapped origin is 1.1 then you need to access it element directly like:
    wdContext.currentParentNodeElement().setFname("Abhijeet");
        wdContext.currentParentNodeElement().setLname("M");
    i will suggest just check out if you are declaring some element of value node and without initialising taking its use or what?
    if this doesnt solve your problem, please post the expanded exception.
    hope it helps
    let me know if you face nay problem
    regards

  • Lower than expected 1310 bridge performance

    Hi All,
    We have recently installed an wireless WAN link over 7 km (aproximate 4.5 milles) distance. The towers are sufficent for fresnel and earth bulge and obstacles requirements.
    We have used Cisco Aironet 1310 bridges (one configured as root bridge, the other as non-root bridge). The antennas are 24 dBi from Hyperlink, connected by RP-TNC to N pigtails, also provided by Hyperlink. According the Cisco utilities, the antennas has more than enough gain for the distance, climatic and topographic conditions.
    The alignement of the antennas was made visually (using binoculars) on one side, on the other with precision instruments.
    To select the frequency (the automatic selection works awfuly bad, it establish connection one of three times) we use the Carrier Busy Test on the network interface / Radio 802.11G menu, where we are able to pick the frequency with zero percent (0%) utilization most of the time.
    The problems we experiment are the following:
    - The latency times are very variable. From 1 ms, to 207 ms, to other values. We have used other wireless equipment with more stable performance.
    - There are lost packets frequently, even with the slightest network traffic (2 PC's with terminal service sessions). Supousedly, the link is of 54 Mbps speed, but the quality is very low.
    - At the moment, we are losing connection every couple of minutes. After that the non-root configured bridge stays down and the only way to reestablish connection is by reseting the 1310.
    - I see that the speed changes every time I refresh the IE utility.
    I still havent configured any security, because the awful way the link works.
    What could be the reason for such bad performance?
    Best Regards,
    Igor Sotelo.

    Hi All,
    I have noticed that when the switches have VLAN configured, the latency is very variable. In this particular case, the switches does not have this configuration. I haven't configured VLAN's on the wireless bridges either.
    I will test the link without any switches, it's an good idea. Perhaps there is "something" with the wired network.
    Other than that the specifics are:
    - I have used Belden RG-6 1530A cable that has even higher grade than the Belden 9077 recommended by the manuals.
    - The extension of the cables is around 40 meters (120 foot).
    - We have installed another wireless link in the place, that uses the same frequency, but different polarity. Also we try to separate the channels at least 7 frequencies.
    - The other system is omnidireccional in nature, and it doesn't have excessive gain.
    - On the place where the equipment of both systems coexist, the physical separation between the antennas of the two systems is around 9 foots (3 meters).
    The error messages we get are:
    - On the root bridge:
    Mar 1 00:00:57.238 Information Interface Dot11Radio0, Deauthenticating Station 0017.0ec6.a590 Reason: Previous authentication no longer valid
    Mar 1 00:00:57.237 Warning Packet to client 0017.0ec6.a590 reached max retries, removing the client
    - On the non-root bridge:
    Mar 1 16:19:52.072 Notification Line protocol on Interface Dot11Radio0, changed state to up
    Mar 1 16:19:51.072 Error Interface Dot11Radio0, changed state to up
    Mar 1 16:19:51.071 Warning Interface Dot11Radio0, Associated To AP Central-2 0017.0ec6.a580 [None]
    Mar 1 16:16:00.255 Warning Interface Dot11Radio0, cannot associate: No Response
    Mar 1 16:15:50.397 Notification Line protocol on Interface Dot11Radio0, changed state to down
    Mar 1 16:15:49.398 Error Interface Dot11Radio0, changed state to down
    Mar 1 16:15:49.397 Warning Interface Dot11Radio0, parent lost: Too many retries
    Mar 1 16:14:56.788 Notification Line protocol on Interface Dot11Radio0, changed state to up
    Mar 1 16:14:55.788 Error Interface Dot11Radio0, changed state to up
    Mar 1 16:14:55.788 Warning Interface Dot11Radio0, Associated To AP Central-2 0017.0ec6.a580 [None]
    When we make a reload on any of the bridges the link reestablishes for some time. With this message on the root bridge:
    Mar 1 00:00:44.194 Information Interface Dot11Radio0, Station NONROOTNAME 0017.0ec6.a590 Reassociated KEY_MGMT[NONE]
    Mar 1 00:00:35.456 Notification Line protocol on Interface Dot11Radio0, changed state to up
    I will appreciate any additional help.
    Best Regards,
    Igor Sotelo.

  • Aironet 1300 dropping every 36-48 hours, help please

    Within the past month our 1300's have begun going down around every 36 hours. They are setup with a root bridge and 4 non-root bridges and are set to use the least congested frequency. I am interested in solving this problem as well as setting up the non-root bridges to act as APs as well as connecting some offices to our main network. Please help if you can! A

    This is the error patern from an associated bridge:
    Interface Dot11Radio0, changed state to up
    2 Mar 10 15:27:15.265 Warning Interface Dot11Radio0, Associated To AP ClarendonHealth 0018.b92b.4190 [None WPA PSK]
    3 Mar 10 15:27:15.060 Error Interface Dot11Radio0, changed state to down
    4 Mar 10 15:27:15.059 Warning Interface Dot11Radio0, parent lost: Received deauthenticate (2) not valid
    5 Mar 10 15:16:57.191 Notification Line protocol on Interface Dot11Radio0, changed state to up
    6 Mar 10 15:16:56.191 Error Interface Dot11Radio0, changed state to up
    7 Mar 10 15:16:56.190 Warning Interface Dot11Radio0, Associated To AP ClarendonHealth 0018.b92b.4190 [None WPA PSK]
    8 Mar 10 15:16:56.003 Warning Interface Dot11Radio0, cannot associate: Associating
    9 Mar 10 15:15:48.999 Warning Interface Dot11Radio0, cannot associate: No Response
    10 Mar 10 15:15:39.446 Notification Line protocol on Interface Dot11Radio0, changed state to down
    11 Mar 10 15:15:38.446 Error Interface Dot11Radio0, changed state to down
    12 Mar 10 15:15:38.445 Warning Interface Dot11Radio0, parent lost: Too many retries
    13 Mar 8 15:20:26.778 Notification Line protocol on Interface Dot11Radio0, changed state to up
    14 Mar 8 15:20:25.778 Error Interface Dot11Radio0, changed state to up
    15 Mar 8 15:20:25.777 Warning Interface Dot11Radio0, Associated To AP ClarendonHealth 0018.b92b.4190 [None WPA PSK]
    16 Mar 8 15:20:25.193 Warning Interface Dot11Radio0, cannot associate: Rcvd response from 0018.b92b.4190 channel 9 3367
    17 Mar 8 15:19:14.188 Warning Interface Dot11Radio0, cannot associate: No Response
    18 Mar 8 15:19:04.550 Notification Line protocol on Interface Dot11Radio0, changed state to down

  • Aironet 1310 Bridges keep losing connection

    There was a similar thread about this last year and I tried what was listed in there to no avail.  I have 2 Aironet 1310 bridges, one as a route bridge and the second as a non-route with clients.  These worked great for nearly a year, we had no problems keeping the connection up.  They were not connected for the last few months but nothing was changed on the configuration, when I put them back up they reconnected just fine and worked for about an hour, not they randomly disconnect with the same message in the log entries below.  Is there something wrong with them now?  The are using the same antennas as before and are in the same exact locations.
    logs from root bridge
    Nov 29 13:52:53.311: %DOT11-4-MAXRETRIES: Packet to client XXXX.XXXX.XXXX reached max retries, removing the client
    Nov 29 13:52:53.311: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station XXXX.XXXX.XXXX Reason: Previous authentication no longer valid
    Nov 29 13:52:53.568: %DOT11-6-ASSOC: Interface Dot11Radio0, Station Test XXX.XXXX.XXXX Reassociated KEY_MGMT[WPAv2 PSK]
    Nov 29 13:55:16.260: %DOT11-4-MAXRETRIES: Packet to client XXXX.XXXX.XXXX reached max retries, removing the client
    Nov 29 13:55:16.260: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station XXXX.XXXX.XXXX Reason: Previous authentication no longer valid
    Nov 29 13:55:16.550: %DOT11-4-MAXRETRIES: Packet to client XXXX.XXXX.XXXX reached max retries, removing the client
    Nov 29 13:55:16.550: Client XXXX.XXXX.XXXX failed: reached maximum retries
    logs from non-root
    Nov 29 2010 13:52:55: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Received deauthenticate (2) not valid
    Nov 29 2010 13:52:55: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

    I am not at the remote location any more, but the route bridge had a signal of -78 dB and a SNR of -22 dB.  The non-route has -77dB for signal and a SNR of -22 dB.  The location has line of sight, over water with nothing in the way. 
    Since I last posted I changed the fragmentation and RTS thresholds back to default from 4000 and it has been up for 24 hours now.  I am hoping that it has made the difference.

  • Introspector finds wrong PropertyDescriptors on overriden methods

    Hello all, I've noticed some odd behaviour from Introspector.getBeanInfo(Class).
    public interface TestB {
    public class TestBImpl implements TestB {
    public interface TestA {
         public TestB getTestB();
    public class TestAImpl implements TestA {
         private TestBImpl testB;
         public TestBImpl getTestB() {
              return testB;
         public void setTestB(TestBImpl testB) {
              this.testB = testB;
    }Notice TestAImpl overrides "public TestB getTestB(); " with the more specific "public TestBImpl getTestB()". TestAImpl also includes a setter for testB.
    Now let's try and get the PropertyDescriptors of TestAImpl
    BeanInfo bi = Introspector.getBeanInfo(TestAImpl.class);
    for (PropertyDescriptor pd: bi.getPropertyDescriptors()) {
         if (pd.getName().equals("testB")) {
              System.out.println("Read Method: " + pd.getReadMethod().toGenericString());
              if (pd.getWriteMethod() == null) {
                   System.out.println("Test Failed");
              } else {
                   System.out.println("Write Method: " + pd.getWriteMethod().toGenericString());
                   System.out.println("Test Passed");
              break;
    }The test fails with the following output
    Read Method: public volatile TestB TestAImpl.getTestB()
    Test FailedThe getter found is from the TestA interface, not from TestAImpl. It's no surprise then that it's unable to locate the setter which is not defined in the interface.
    This this a bug or am I missing something? To me it should work similar to Class.getMethod(String, Class[]) which starts at the bottom and recurses up the super chain.
    Thanks
    Mark

    I submitted a bug about this issue. The problem is not only with interfaces but with basic subclassing too.
    See this code and output:
    import java.beans.BeanInfo;
    import java.beans.IntrospectionException;
    import java.beans.Introspector;
    import java.beans.PropertyDescriptor;
    import java.lang.reflect.Method;
    import java.lang.reflect.InvocationTargetException;
    * Shows odd behavior when using an instrospector from the java.beans api
    public class InstrospectorPossibleBugTest {
            * super class for people
           public class Person {
                   public Object getName() {
                           return null;
            * A worker is a Person
           public class Worker extends Person {
                   private String name;
                   public String getName() {
                           return name;
                   public void setName(String name) {
                           this.name = name;
            * This small test cases shows the odd behavior.
            * Even though Worker conforms with the getters and setters for the javabean spec the
            * Instrospector seems to not be able to find any setter for the property name.
            * Seems like instead of following a bottom up lookup for property accessors it starts and stops once it
            * finds a compatible property in one of the implemented interfaces or parent classes.
           public static void main(String... args) throws IntrospectionException, InvocationTargetException, IllegalAccessException {
                   BeanInfo info = Introspector.getBeanInfo(Worker.class);
                   PropertyDescriptor[] descriptors = info.getPropertyDescriptors();
                   for (PropertyDescriptor descriptor : descriptors) {
                           if (!descriptor.getName().equals("class")) {
                                   System.out.println("property: \t\t\t\t\t\t" + descriptor.getName());
                                   System.out.println("getter: \t\t\t\t\t\t" + descriptor.getReadMethod());
                                   System.out.println("getter returns: \t\t\t\t" + descriptor.getReadMethod().getReturnType());
                                   System.out.println("setter: \t\t\t\t\t\t" + descriptor.getWriteMethod());
                                   String propertyName = descriptor.getName();
                                   String setterName = "set" + propertyName.substring(0, 1).toUpperCase() + propertyName.substring(1);
                                   Method setter = findMethodImplFirst(Worker.class, setterName, String.class);
                                   System.out.println("setter with reflection: \t\t" + setter);
    }Output:
    property: name
    getter: public java.lang.Object Worker.getName()
    getter returns: class java.lang.Object
    setter: null

  • Duet server installation error

    My  dear  duets ,
    please request you all from the bottom of the Duet heart  : seggestion
    below is th java logs .
    pelase reply if your nto busy  it`s urgent ......
    Please wait...
    Client log:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    <!NAME[F:\usr\sap\J2E\JC00\SDM\program\log\sdmcl20070430092257.log]/>
    <!PATTERN[sdmcl20070430092257.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    Apr 30, 2007 2:52:57 PM  Info: -
    Starting deployment -
    Apr 30, 2007 2:52:57 PM  Info: Error handling strategy: OnErrorStop
    Apr 30, 2007 2:52:57 PM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Apr 30, 2007 2:52:57 PM  Info: Update strategy: UpdateAllVersions
    Apr 30, 2007 2:52:57 PM  Info: Starting deployment prerequisites:
    Apr 30, 2007 2:52:58 PM  Info: Loading selected archives...
    Apr 30, 2007 2:52:58 PM  Info: Loading archive 'F:\usr\sap\J2E\JC00\SDM\program\temp\OSPCOMMON02_0.sca'
    Apr 30, 2007 2:52:59 PM  Info: Loading archive 'F:\usr\sap\J2E\JC00\SDM\program\temp\OSPCOMMON02_0.sca'
    Apr 30, 2007 2:53:00 PM  Info: Selected archives successfully loaded.
    Apr 30, 2007 2:53:00 PM  Info: Actions per selected component:
    Apr 30, 2007 2:53:00 PM  Info: Update: Selected development component 'xapps/osp/fw/appinst/ui/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069200'/'9' updates currently deployed development component 'xapps/osp/fw/appinst/ui/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069200'/'7'.
    Apr 30, 2007 2:53:00 PM  Info: Initial deployment: Selected development component 'xapps/osp/fw/restartapp/ui/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069124'/'9' will be deployed.
    Apr 30, 2007 2:53:00 PM  Info: Initial deployment: Selected development component 'xapps/osp/fw/common/rmagent/deployer'/'sap.com'/'MAIN_OSP10VAL_C'/'1069161'/'9' will be deployed.
    Apr 30, 2007 2:53:00 PM  Info: Update: Selected development component 'xapps/osp/common/enterpriseapp'/'sap.com'/'MAIN_OSP10VAL_C'/'1075176'/'9' updates currently deployed development component 'xapps/osp/common/enterpriseapp'/'sap.com'/'MAIN_OSP10VAL_C'/'1075176'/'7'.
    Apr 30, 2007 2:53:00 PM  Info: Initial deployment: Selected development component 'xapps/osp/rolemanagement/azman/wsproxy'/'sap.com'/'MAIN_OSP10VAL_C'/'1069120'/'9' will be deployed.
    Apr 30, 2007 2:53:00 PM  Info: Update: Selected development component 'xapps/osp/common/data'/'sap.com'/'MAIN_OSP10VAL_C'/'1069119'/'9' updates currently deployed development component 'xapps/osp/common/data'/'sap.com'/'MAIN_OSP10VAL_C'/'1069119'/'7'.
    Apr 30, 2007 2:53:00 PM  Info: Initial deployment: Selected software component 'OSP_COMMON'/'sap.com'/'MAIN_OSP10VAL_C'/'1000.100.0.2.0.20070116144642''/'9' will be deployed.
    Apr 30, 2007 2:53:00 PM  Info: Update: Selected development component 'xapps/osp/fw/admin/launchpad/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069153'/'9' updates currently deployed development component 'xapps/osp/fw/admin/launchpad/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069153'/'7'.
    Apr 30, 2007 2:53:00 PM  Info: Ending deployment prerequisites. All items are correct.
    Apr 30, 2007 2:53:00 PM  Info: Saved current Engine state.
    Apr 30, 2007 2:53:00 PM  Info: Starting: Update: Selected development component 'xapps/osp/common/data'/'sap.com'/'MAIN_OSP10VAL_C'/'1069119'/'9' updates currently deployed development component 'xapps/osp/common/data'/'sap.com'/'MAIN_OSP10VAL_C'/'1069119'/'7'.
    Apr 30, 2007 2:53:01 PM  Info: <!LOGHEADER[START]/>
    Apr 30, 2007 2:53:01 PM  Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
    Apr 30, 2007 2:53:01 PM  Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    Apr 30, 2007 2:53:01 PM  Info: <!NAME[F:\usr\sap\J2E\JC00\SDM\program\log\jddilog20070430145300.log]/>
    Apr 30, 2007 2:53:01 PM  Info: <!PATTERN[jddilog20070430145300.log]/>
    Apr 30, 2007 2:53:01 PM  Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
    Apr 30, 2007 2:53:01 PM  Info: <!ENCODING[Cp1252]/>
    Apr 30, 2007 2:53:01 PM  Info: <!LOGHEADER[END]/>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<<<<<<<<<<<<< Table Deployment >>>>>>>>>>>>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<<<<<<<<<<<<< Table Deployment >>>>>>>>>>>>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info: 
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info: 
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table BC_DDDBRTH >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table BC_DDDBRTH >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table BC_DDDBTABLERT >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table BC_DDDBTABLERT >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table BC_DDDBRTH >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table BC_DDDBRTH >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table BC_DDDBRTX >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table BC_DDDBRTX >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  >>> Analyze tables from archive in database ORACLE
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  >>> Analyze tables from archive in database ORACLE
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_KEYSEQ.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_KEYSEQ.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_KEYSEQ >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_KEYSEQ >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_KEYSEQ successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_KEYSEQ successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_KEYSEQ successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_KEYSEQ successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_LS_BACKEND.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_LS_BACKEND.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_LS_BACKEND >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_LS_BACKEND >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_BACKEND successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_BACKEND successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_BACKEND successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_BACKEND successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_LS_JAS.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_LS_JAS.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_LS_JAS >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_LS_JAS >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_JAS successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_JAS successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_JAS successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_JAS successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_LS_JASTOBE.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_LS_JASTOBE.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_LS_JASTOBE >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_LS_JASTOBE >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_JASTOBE successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_JASTOBE successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_JASTOBE successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_LS_JASTOBE successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_RM_RSC.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_RM_RSC.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_RM_RSC >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_RM_RSC >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_RM_RSC successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_RM_RSC successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_RM_RSC successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_RM_RSC successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ADDON.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ADDON.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ADDON >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ADDON >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ADDON successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ADDON successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ADDON successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ADDON successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ERP.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ERP.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ERP >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ERP >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERP successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERP successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERP successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERP successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ERPTOAO.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ERPTOAO.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ERPTOAO >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ERPTOAO >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTOAO successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTOAO successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTOAO successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTOAO successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ERPTORO.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ERPTORO.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ERPTORO >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ERPTORO >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTORO successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTORO successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTORO successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTORO successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ERPTYPE.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ERPTYPE.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ERPTYPE >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ERPTYPE >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Table XAP_OSP_SM_ERPTYPE not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Table XAP_OSP_SM_ERPTYPE not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_ERPTYPE"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_ERPTYPE"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:00 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTYPE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTYPE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTYPE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ERPTYPE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_MENERP.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_MENERP.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_MENERP >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_MENERP >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_MENERP successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_MENERP successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_MENERP successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_MENERP successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_MENROLE.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_MENROLE.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_MENROLE >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_MENROLE >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Table XAP_OSP_SM_MENROLE not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Table XAP_OSP_SM_MENROLE not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_MENROLE"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_MENROLE"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_MENROLE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_MENROLE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_MENROLE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_MENROLE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_PORROLE.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_PORROLE.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_PORROLE >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_PORROLE >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Table XAP_OSP_SM_PORROLE not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Table XAP_OSP_SM_PORROLE not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_PORROLE"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_PORROLE"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_PORROLE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_PORROLE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_PORROLE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_PORROLE deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ROLES.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_ROLES.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ROLES >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_ROLES >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Table XAP_OSP_SM_ROLES not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Table XAP_OSP_SM_ROLES not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_ROLES"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_ROLES"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ROLES deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ROLES deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ROLES deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_ROLES deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_USERS.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_SM_USERS.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_USERS >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_SM_USERS >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>DROP<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Table XAP_OSP_SM_USERS not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Table XAP_OSP_SM_USERS not found on DB
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Action: DROP
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_USERS"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:    DROP TABLE "XAP_OSP_SM_USERS"
    Apr 30, 2007 2:53:01 PM  Info:
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Error 4004 will be ignored
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_USERS deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_USERS deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_USERS deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_SM_USERS deleted
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_TASKS.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Next archive object : dbtables/XAP_OSP_TASKS.gdbtable
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_TASKS >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  <<< Analyze table XAP_OSP_TASKS >>>
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  predefined action is: >>>null<<<
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  No action required for table     
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_TASKS successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_TASKS successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_TASKS successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Runtime XML of XAP_OSP_TASKS successfully written
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Analysis and adjustment of tables successfully executed
    Apr 30, 2007 2:53:01 PM  Info: 14:53:01 2007-04-30 dbs-Info:  Analysis and adjustment of tables successfully executed
    Apr 30, 2007 2:53:01 PM  Info: Finished successfully: development component 'xapps/osp/common/data'/'sap.com'/'MAIN_OSP10VAL_C'/'1069119'/'9', grouped by
    Apr 30, 2007 2:53:01 PM  Info: Starting to save the repository
    Apr 30, 2007 2:53:01 PM  Info: Finished saving the repository
    Apr 30, 2007 2:53:01 PM  Info: Starting: Update: Selected development component 'xapps/osp/common/enterpriseapp'/'sap.com'/'MAIN_OSP10VAL_C'/'1075176'/'9' updates currently deployed development component 'xapps/osp/common/enterpriseapp'/'sap.com'/'MAIN_OSP10VAL_C'/'1075176'/'7'.
    Apr 30, 2007 2:53:01 PM  Info: SDA to be deployed: F:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\xapps\osp\common\enterpriseapp\MAIN_OSP10VAL_C\9\1075176\sap.com_xappsospcommon~enterpriseapp.sda
    Apr 30, 2007 2:53:01 PM  Info: Software type of SDA: J2EE
    Apr 30, 2007 2:53:01 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 30, 2007 2:53:43 PM  Info: Begin of log messages of the target system:
    07/04/30 14:53:01 -  ***********************************************************
    07/04/30 14:53:02 -  Start updating EAR file...
    07/04/30 14:53:02 -  start-up mode is lazy
    07/04/30 14:53:03 -  EAR file updated successfully for 953ms.
    07/04/30 14:53:03 -  Start updating...
    07/04/30 14:53:04 -  EAR file uploaded to server for 828ms.
    07/04/30 14:53:42 -  Successfully updated. Update took 37890ms.
    07/04/30 14:53:42 -  Deploy Service status:
    07/04/30 14:53:42 -    Application : sap.com/xappsospcommon~enterpriseapp
    07/04/30 14:53:42 -   
    07/04/30 14:53:42 -    com.sap.xapps.osp  - LOGGING CONFIGURATION
    07/04/30 14:53:42 -    SAP/XAP_OSP  - JDBCCONNECTOR
    07/04/30 14:53:42 -    CommonDistributionBusConnFactory  - JMSCONNECTOR
    07/04/30 14:53:42 -    SchedulerTopicFactory  - JMSCONNECTOR
    07/04/30 14:53:42 -    ResourceManagerConnFactory  - JMSCONNECTOR
    07/04/30 14:53:42 -    DistributionBusTopic  - JMSCONNECTOR
    07/04/30 14:53:42 -    SchedulerTopic  - JMSCONNECTOR
    07/04/30 14:53:42 -    ResourceManagerStartupTopic  - JMSCONNECTOR
    07/04/30 14:53:42 -    ResourceManagerComponentsTopic  - JMSCONNECTOR
    07/04/30 14:53:42 -    TextReplacementServicesBean  - EJB
    07/04/30 14:53:42 -    TextReplacementStartupMDBBean  - EJB
    07/04/30 14:53:42 -    TextReplacementMDBBean  - EJB
    07/04/30 14:53:42 -    TextReplacementResourcesMDBBean  - EJB
    07/04/30 14:53:42 -    InstConfiguratorBean  - EJB
    07/04/30 14:53:42 -    ResourceManagerStartupMDBBean  - EJB
    07/04/30 14:53:42 -    LoggerMDBBean  - EJB
    07/04/30 14:53:42 -    SchedulerBean  - EJB
    07/04/30 14:53:42 -    KeyGeneratorEJBBean  - EJB
    07/04/30 14:53:42 -    ServiceLocaltorMDBBean  - EJB
    07/04/30 14:53:42 -    ScenarioTypeMDBBean  - EJB
    07/04/30 14:53:42 -    ServerInfoMDBBean  - EJB
    07/04/30 14:53:42 -    ResourceManagerNotifierBean  - EJB
    07/04/30 14:53:42 -    LocaleHandlerBean  - EJB
    07/04/30 14:53:42 -    LocaleHandlerMDBBean  - EJB
    07/04/30 14:53:42 -    FileTransferAgentBean  - EJB
    07/04/30 14:53:42 -    FileTransferManagerBean  - EJB
    07/04/30 14:53:42 -    AgentBean  - EJB
    07/04/30 14:53:42 -    TaksEngineBean  - EJB
    07/04/30 14:53:42 -    InstEndBean  - EJB
    07/04/30 14:53:42 -    XmlFinderBean  - EJB
    07/04/30 14:53:42 -    DeployTaskBean  - EJB
    07/04/30 14:53:42 -    CreateSdmVariablesTaskBean  - EJB
    07/04/30 14:53:42 -    ImportAdminXmlTaskBean  - EJB
    07/04/30 14:53:42 -    ConfigureEsaDestinationsBean  - EJB
    07/04/30 14:53:42 -    KeyStorageConnectorBean  - EJB
    07/04/30 14:53:42 -    DestinationConnectorBean  - EJB
    07/04/30 14:53:42 -    UserStoreConnectorBean  - EJB
    07/04/30 14:53:42 -    PolicyConfigurationConnectorBean  - EJB
    07/04/30 14:53:42 -    DeployConnectorBean  - EJB
    07/04/30 14:53:42 -    SdmConnectorBean  - EJB
    07/04/30 14:53:42 -    J2eeSystemConnectorBean  - EJB
    07/04/30 14:53:42 -    ConfigManagerConnectorBean  - EJB
    07/04/30 14:53:42 -    CacheMDBBean  - EJB
    07/04/30 14:53:42 -    CacheInvalidateTaskBean  - EJB
    07/04/30 14:53:42 -    WEB SERVICE PORTS:
                         /ResourceManagerNotifierWS/Config1
                           - WEBSERVICES
    07/04/30 14:53:42 -    MAIN_OSPDEV_Dxappsospschedulerwebmodule~sap.com  - WEB
    07/04/30 14:53:42 -    ResourceManagerNotifierWS/Config1  - WEB
    07/04/30 14:53:42 -    MAIN_D10PSPD_Dxappsospmonitoringwebmodule~sap.com  - WEB
    07/04/30 14:53:42 -  ***********************************************************
    Apr 30, 2007 2:53:43 PM  Info: End of log messages of the target system.
    Apr 30, 2007 2:53:43 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 30, 2007 2:53:43 PM  Warning: Finished with warnings: development component 'xapps/osp/common/enterpriseapp'/'sap.com'/'MAIN_OSP10VAL_C'/'1075176'/'9', grouped by software component 'OSP_COMMON'/'sap.com'/'MAIN_OSP10VAL_C'/'1000.100.0.2.0.20070116144642''/'9':
    Caught exception during application startup from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while starting application sap.com/xapps/osp/common/enterpriseapp and wait.
    Reason: Clusterwide exception: server ID 7459750:com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Naming error.
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.loadFactory(ContainerImpl.java:1900)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.prepareStart(ContainerImpl.java:698)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4666)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4639)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.ClassNotFoundException: com.sap.engine.services.rmi_p4.LoadBalancerImpl
    Found in negative cache
    Loader Info -
    ClassLoader name: [interface:cross]
    Parent loader name: [Frame ClassLoader]
    No references !
    Resources:
       F:\usr\sap\J2E\JC00\j2ee\cluster\server0\bin\interfaces\cross\cross_api.jar
    Loading model: {parent,local,references}
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455)
         at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
         at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
         at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.loadFactory(ContainerImpl.java:1897)
         ... 20 more
    Caused by: java.lang.ClassNotFoundException: com.sap.engine.services.rmi_p4.LoadBalancerImpl
    Found in negative cache
    Loader Info -
    ClassLoader name: [interface:cross]
    Parent loader name: [Frame ClassLoader]
    No references !
    Resources:
       F:\usr\sap\J2E\JC00\j2ee\cluster\server0\bin\interfaces\cross\cross_api.jar
    Loading model: {parent,local,references}
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:141)
         at com.sap.engine.interfaces.cross.CrossObjectBroker.getLoadBalancer(CrossObjectBroker.java:145)
         at com.sap.engine.interfaces.cross.CrossObjectBroker.getDestination(CrossObjectBroker.java:88)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:339)
         ... 28 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Apr 30, 2007 2:53:43 PM  Info: Starting to save the repository
    Apr 30, 2007 2:53:43 PM  Info: Finished saving the repository
    Apr 30, 2007 2:53:44 PM  Info: Starting: Update: Selected development component 'xapps/osp/fw/admin/launchpad/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069153'/'9' updates currently deployed development component 'xapps/osp/fw/admin/launchpad/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069153'/'7'.
    Apr 30, 2007 2:53:44 PM  Info: SDA to be deployed: F:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\xapps\osp\fw\admin\launchpad\webdynpro\MAIN_OSP10VAL_C\9\1069153\sap.com_xappsospfwadminlaunchpad~webdynpro.sda
    Apr 30, 2007 2:53:44 PM  Info: Software type of SDA: J2EE
    Apr 30, 2007 2:53:44 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 30, 2007 2:53:49 PM  Info: Begin of log messages of the target system:
    07/04/30 14:53:44 -  ***********************************************************
    07/04/30 14:53:44 -  Start updating EAR file...
    07/04/30 14:53:44 -  start-up mode is lazy
    07/04/30 14:53:44 -  EAR file updated successfully for 31ms.
    07/04/30 14:53:44 -  Start updating...
    07/04/30 14:53:44 -  EAR file uploaded to server for 47ms.
    07/04/30 14:53:44 -  Successfully updated. Update took 250ms.
    07/04/30 14:53:44 -  Deploy Service status:
    07/04/30 14:53:44 -    Application : sap.com/xappsospfwadminlaunchpad~webdynpro
    07/04/30 14:53:44 -   
    07/04/30 14:53:44 -    sap.com/xappsospfwadminlaunchpad~webdynpro  - WEBDYNPRO
    07/04/30 14:53:44 -  ***********************************************************
    Apr 30, 2007 2:53:49 PM  Info: End of log messages of the target system.
    Apr 30, 2007 2:53:49 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 30, 2007 2:53:49 PM  Warning: Finished with warnings: development component 'xapps/osp/fw/admin/launchpad/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069153'/'9', grouped by :
    Caught exception during application startup from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while starting application sap.com/xapps/osp/fw/admin/launchpad/webdynpro and wait.
    Reason: Clusterwide exception: server ID 7459750:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/xappsospfwadminlaunchpad~webdynpro'' for startup. Reason=
    Clusterwide exception: Failed to start application ''sap.com/xappsospfwadminlaunchpadwebdynpro'': The referenced application ''sap.com/xappsospcommonenterpriseapp'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
         at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1421)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4666)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4639)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Apr 30, 2007 2:53:49 PM  Info: Starting to save the repository
    Apr 30, 2007 2:53:50 PM  Info: Finished saving the repository
    Apr 30, 2007 2:53:50 PM  Info: Starting: Update: Selected development component 'xapps/osp/fw/appinst/ui/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069200'/'9' updates currently deployed development component 'xapps/osp/fw/appinst/ui/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069200'/'7'.
    Apr 30, 2007 2:53:50 PM  Info: SDA to be deployed: F:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\xapps\osp\fw\appinst\ui\webdynpro\MAIN_OSP10VAL_C\9\1069200\sap.com_xappsospfwappinstui~webdynpro.sda
    Apr 30, 2007 2:53:50 PM  Info: Software type of SDA: J2EE
    Apr 30, 2007 2:53:50 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 30, 2007 2:53:56 PM  Info: Begin of log messages of the target system:
    07/04/30 14:53:50 -  ***********************************************************
    07/04/30 14:53:50 -  Start updating EAR file...
    07/04/30 14:53:50 -  start-up mode is lazy
    07/04/30 14:53:50 -  EAR file updated successfully for 31ms.
    07/04/30 14:53:50 -  Start updating...
    07/04/30 14:53:50 -  EAR file uploaded to server for 31ms.
    07/04/30 14:53:50 -  Successfully updated. Update took 187ms.
    07/04/30 14:53:50 -  Deploy Service status:
    07/04/30 14:53:50 -    Application : sap.com/xappsospfwappinstui~webdynpro
    07/04/30 14:53:50 -   
    07/04/30 14:53:50 -    sap.com/xappsospfwappinstui~webdynpro  - WEBDYNPRO
    07/04/30 14:53:50 -  ***********************************************************
    Apr 30, 2007 2:53:56 PM  Info: End of log messages of the target system.
    Apr 30, 2007 2:53:56 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 30, 2007 2:53:56 PM  Warning: Finished with warnings: development component 'xapps/osp/fw/appinst/ui/webdynpro'/'sap.com'/'MAIN_OSP10VAL_C'/'1069200'/'9', grouped by :
    Caught exception during application startup from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while starting application sap.com/xapps/osp/fw/appinst/ui/webdynpro and wait.
    Reason: Clusterwide exception: server ID 7459750:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/xappsospfwappinstui~webdynpro'' for startup. Reason=
    Clusterwide exception: Failed to start application ''sap.com/xappsospfwappinstuiwebdynpro'': The referenced application ''sap.com/xappsospcommonenterpriseapp'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
         at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1421)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4666)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4639)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Apr 30, 2007 2:53:56 PM  Info: Starting to save the repository
    Apr 30, 2007 2:53:56 PM  Info: Finished saving the repository
    Apr 30, 2007 2:53:56 PM  Info: Starting: Initial deployment: Selected development component 'xapps/osp/fw/common/rmagent/deployer'/'sap.com'/'MAIN_OSP10VAL_C'/'1069161'/'9' will be deployed.
    Apr 30, 2007 2:53:56 PM  Info: SDA to be deployed: F:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\xapps\osp\fw\common\rmagent\deployer\MAIN_OSP10VAL_C\9\1069161\sap.com_xappsospfwcommonrmagent~deployer.sda
    Apr 30, 2007 2:53:56 PM  Info: Software type of SDA: J2EE
    Apr 30, 2007 2:53:56 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 30, 2007 2:53:57 PM  Info: Begin of log messages of the target system:
    07/04/30 14:53:56 -  ***********************************************************
    07/04/30 14:53:56 -  Start updating EAR file...
    07/04/30 14:53:56 -  start-up mode is lazy
    07/04/30 14:53:56 -  EAR file updated successfully for 47ms.
    07/04/30 14:53:56 -  Start deploying ...
    07/04/30 14:53:56 -  EAR file uploaded to server for 16ms.
    07/04/30 14:53:57 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/xappsospfwcommonrmagent~deployer..
                         Reason: Exception during generation of components of application sap.com/xappsospfwcommonrmagent~deployer in container EJBContainer.; nested exception is:
                              com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/xappsospfwcommonrmagent~deployer in container EJBContainer.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:568)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/xappsospfwcommonrmagent~deployer in container EJBContainer.
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:553)
                              ... 10 more
                         Caused by: java.lang.NoClassDefFoundError: com/sap/xapps/osp/infrastructure/resourcemanager/exceptions/ResourceManagerException
                              at java.lang.Class.getDeclaredMethods0(Native Method)
                              at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
                              at java.lang.Class.getMethod0(Class.java:1901)
                              at java.lang.Class.getMethod(Class.java:984)
                              at com.sap.engine.services.ejb.util.ClassUtils.hasMethod(ClassUtils.java:45)
                              at com.sap.engine.services.ejb.deploy.verifier.BeanClassCheck.check(BeanClassCheck.java:56)
                              at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:51)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate

    HIIIIIIIIIIIIIIIIIIIII ,
    I FIX THE ERROR BY Installing the sp19 pack......

  • Aironet 1310 errors...

    Hi,
    we have got two ofices in different area. We decided to connect them with two AP's Aironet 1310 with mode point-to-point bridge. We have voice traffic over this wi-fi channel. If we use IOS 12.3(4)-JA we have noticed many errors in the logs 1310 such as "DOT11-4-MAXRETRIES: Packet to client [mac] reached max retries, remove
    the client" or "DOT11-4-UPLINK_LINK_DOWN: Interface Dot11Radio0, parent lost: To many retries". The connection betwen AP's is down at regular intervals and not established again. The connection has upped only after disconnect and reconnect the power injector power jack. Time to response is less than 100 ms for ping. We have changed IOS ver 12.3(8)-JA2 and unfortunately it doesn't help, though the errors has noticed less, but Time to response is between 70 ms and 5000 ms. It is too bad for normal work in our ofices, we wanted to have Time to response about 50 ms. Could you advise something?
    Thanks.

    Packet to client MAC reached max retries, remove the client" is happened when your client try to associate AP which doesn't support client function correctly (usually authentication type doesn'tmatch).

  • 1242G Bridge problems

    I have two bridges setup using 4 x 1242ag.
    On both links one ap is set as root bridge and the other as a non root bridge. On link is fine but the other is showing "Interface Dot11radio0, parent deauthenticate (2) Not Valid" in the logs every 5 mins or so. Is this a noise problem?

    Looks like this is two problems.  If Bridge open before, and not now I would reset the preferences.  Hold down the Ctrl key and start Bridge.  You should get a reset window with 3 options.

  • Bridge to bridge and bridge to access-point is it possible

    here;s my topology i am trying to configure. i have a router whose ethernet is connected to a bridge.this bridge 1 is connected to a bridge 2 via wireless. now i am trying to connect a access-point via wireless to this bridge2. is it possible for bridge 2 to support connectivity to the bridge1 and the access-point both of them via wireless.
    can someone pls help me on this.
    waiting for someone to reply.
    regards

    Take a look at my suggested config below. The first accesspoint will broadcast a SSID for clients and use a different SSID for the bridge. This setup has no 802.1x mechanism yet, but you can add that later. For the topology see PtoPLinkExample.gif posted earlier.
    ----- Accesspoint 1 --------------
    dot11 ssid bridge
    authentication open
    dot11 ssid WiFiNet
    authentication open
    guest-mode
    interface Dot11Radio0
    ssid bridge
    ssid WiFiNet
    ----- Accesspoint 2 --------------
    dot11 ssid bridge
    authentication open
    interface Dot11Radio0
    parent 1
    ssid bridge
    station-role workgroup-bridge
    ----- Accesspoint 3 --------------
    dot11 ssid WiFiNet
    authentication open
    guest-mode
    interface Dot11Radio0
    ssid WiFiNet

  • 871 with 2 1100 Aironet Repeaters

    I am having quite a bit of trouble with setting up a very simple network.
    My objective is to cover a small warehouse with wireless coverage to allow for data collection from remote scales in fixed location.
    To reach to the far corner of the warehouse I needed to repeaters as discovered by trial and error. The problem is that the second repeater disconnects somewhat randomly. The disconnect period can be from as little as 30 minutes to has long as 8 hours. When the second repeater disconnects it take roughyl two minutes for it to reconnect. I am attaching the event log in hopes that it means something to some one. Also I am having a somewhat annoying problem that when ever I power down any of the equipment certain parameters are not saved such as the time and on the 871 the DHCP address range resets. I am not sure if this problem is related but it is quite bother some.
    1 Jun 15 14:25:30.583 R Information Interface Dot11Radio0, Station 0020.4a89.1d0a Associated KEY_MGMT[NONE]
    2 Jun 15 14:25:28.551 R Warning Interface Dot11Radio0, Associated To AP Repeater1 0017.59e1.2334 [None]
    3 Jun 15 14:25:28.549 R Error Interface Dot11Radio0, changed state to up
    4 Jun 15 14:25:28.492 R Error Interface Dot11Radio0, changed state to down
    5 Jun 15 14:25:28.491 R Information Interface Dot11Radio0, Deauthenticating Station 0020.4a89.1d0a Reason: Previous authentication no longer valid
    6 Jun 15 14:25:28.490 R Warning Interface Dot11Radio0, parent lost: Received deauthenticate (2) not valid
    7 Jun 15 14:24:45.796 R Information Interface Dot11Radio0, Station 0020.4a89.1d0a Associated KEY_MGMT[NONE]
    8 Jun 15 14:24:00.769 R Warning Interface Dot11Radio0, Associated To AP Repeater1 0017.59e1.2334 [None]
    9 Jun 15 14:24:00.767 R Error Interface Dot11Radio0, changed state to up
    10 Jun 15 14:24:00.711 R Error Interface Dot11Radio0, changed state to down
    11 Jun 15 14:24:00.710 R Information Interface Dot11Radio0, Deauthenticating Station 0020.4a89.1d0a Reason: Previous authentication no longer valid
    12 Jun 15 14:24:00.675 R Warning Interface Dot11Radio0, parent lost: Received deauthenticate (2) not valid
    13 Jun 15 14:24:00.598 R Information Interface Dot11Radio0, Station 0020.4a89.1d0a Associated KEY_MGMT[NONE]
    14 Jun 15 14:23:51.606 R Warning Interface Dot11Radio0, Associated To AP Repeater1 0017.59e1.2334 [None]
    15 Jun 15 14:23:51.604 R Error Interface Dot11Radio0, changed state to up
    16 Jun 15 14:23:51.542 R Error Interface Dot11Radio0, changed state to down
    17 Jun 15 14:23:51.541 R Information Interface Dot11Radio0, Deauthenticating Station 0020.4a89.1d0a Reason: Previous authentication no longer valid
    18 Jun 15 14:23:51.539 R Warning Interface Dot11Radio0, parent lost: Received deauthenticate (2) not valid
    19 Jun 15 14:23:15.811 R Information Interface Dot11Radio0, Station 0020.4a89.1d0a Associated KEY_MGMT[NONE]
    20 Jun 15 14:22:48.593 R Warning Interface Dot11Radio0, Associated To AP Repeater1 0017.59e1.2334 [None]

    Hi Roberto,
    Hopefully the attached docs will answer your question:
    Cisco Aironet 1100 Series
    Using VLANs with Cisco Aironet Wireless Equipment
    Deprecated versions of Cisco Aironet software permit binding multiple SSIDs to one VLAN. Current versions do not.
    http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801d0815.shtml#
    Cisco IOS Software Configuration Guide for Cisco Aironet Access Points, 12.2(15)JA
    Configuring Multiple SSIDs
    vlan vlan-id
    (Optional) Assign the SSID to a VLAN on your network. Client devices that associate using the SSID are grouped into this VLAN. You can assign only one SSID to a VLAN.
    http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_guide_chapter09186a00802085c4.html
    Hope this helps!
    Rob
    Please remember to rate helpful posts.......

  • Workgroup Bridge

    I'm getting an the following error on my workgroup bridge. And I'm not able to pass traffic across it.
    *Mar 1 00:03:29.665: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
    0, changed state to up
    *Mar 1 00:05:48.860: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost:
    Received deauthenticate (1) failure
    *Mar 1 00:05:48.861: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to do
    wn

    Turns out my Bridge date and time was off. I set the date and time, and all is good.

Maybe you are looking for