Managing Request without Monitor Log: APO Request or Terminated Request Gen

Hello Everyone,
Need some help of managing a system created DTP named Request without Monitor Log: APO Request or Terminated Request Generation. This is like a staging DTP provided by SAP to support data loads to DSO or Cube and, it's good if the process goes smoothly.
However when we encountered unnecessary error such as tables space or memory problem, this particular job will get stuck and there's no way to move forward or backwards from this point. There were some answers to delete the request from RSICCONT, but I don't see the direct relations here, or maybe I'm wrong.
My only question - Have anyone any idea on how to work around this.
The last thing I've in hand is to delete the whole thing (requests) and re-do from start (extraction). Not a pleasant thing as this DSO feeds to 2 Cube & 1 DSO and then to another Cube. 
Thanking everyone in advance.
Regards,
Azmadi

Hi,
sad to knw you had to delete the whole data and reload. I faced the same issue today and here is what i did,
when you go to the reconstruction tab, you will find 2 ticks present
1st one that tells if request is available in data target and
2nd which gives the transfer structure status.
Now, if the first check is crossed it could mean 2 things....data no longer exists in data target or data was not updated to data target these are 2 different things.
So, in your case it wud have sed data was not updated to the target.
Solution, just reconstruct that request and then in the request tab mark it red and delete again since you dont need it.... then the activation through process chain will not fail.

Similar Messages

  • Requests without Monitor Log: APO Request or Terminated Request Generation

    Hello all,
    Can you please help me in the following issue:
    I had in an ODS, a full request of type:
    Requests without Monitor Log: APO Request or Terminated Request Generation.
    I deleted the request from table: RSICCONT in debugging mode. The request was on green.
    Now I have problems on activating the next requests in automatically. Manually it is working.
    Request REQU_6DFXRA2VWJL3KYU44JPCWKXL2 no longer exists in DSO SVO_PPAB; system is inconsistent
    Activation of M records from DataStore object SVO_PPAB terminated
    Please help
    Thank you
    Ramona

    Hi,
    Refer the below links,
    Re: Managing Request without Monitor Log: APO Request or Terminated Request Gen
    http://ar.delhigovt.nic.in/ar1/Mission%20Conv%20RFP%20-%20Vol%20I-%20V4.0.pdf
    http://help.sap.com/bp_bblibrary/600/documentation/R61_BPP_EN_DE.doc
    Hope it helps you,
    Regards,
    Ravindra.

  • Request without Monitor Log: APO Request or Terminated Request Generation

    Hi,
    While loading data to ODS from the sources system there is new error request appearing in the ODS with following description:
    “Request without Monitor Log: APO Request or Terminated Request Generation”
    Unable to see the error details as this request is not appearing in the monitor, unable to delete the request from the ODS and the error message is below.
    Deletion of request REQU_435CYSN3FS0USQJXVKQOLAZ65 from data target ZRORDITM failed      RSMPC          060
    Deletion of request REQU_435CYSN3FS0USQJXVKQOLAZ65 from data target ZRORDITM failed      RSMPC          060
    Any thoughts on above issue are helpful.
    Thanks
    Kumar

    My thoughts on this...
    This problem might be caused by a program error.
    DataStore objects allow you to check or generate master data ID (SID) values during the activation. If you choose to do this, the parallel processes may terminate.
    <b>The following prerequisites must apply:-</b>
    You activate the DataStore object data in parallel (see transaction RSODSO_SETTINGS).
    During the activation, SID values are checked or generated (option "Generation of SID Values" is set).
    The generated programs of the InfoObjects of the DataStore objects are not current at the start of the activation (in particular, after metadata changes).
    Note 978772 - P10: Parallel SID generation terminates with deadlock
    Hope it Helps
    Chetan
    @CP..

  • Request without Monitor Log:

    HI Frds,
    When i am deleteing a req. from ODS, i am not able delete the Req. I Req. status is in Red and tech. status also in Red. Its showing DTP/Infopackage as "Request without Monitor Log: APO Request or Terminated Request Generation" and not able to see the Moniter(RSMO).
    Kindly can one give me some solution to delete these type req. ?
    Thanks
    Pari

    Hi,
    Apply the recommendation of the above note:
    1138410-->execute the report RSSM_ZOMBIE_REQUEST_DELETE before checking  if you do not have entries in the table RSSELDONE or the table RSMONMESS but which may be displayed in the administration of a
    data target with the descriptive text "Request without monitor log:  APO request or terminated request creation".
    I hope it helps.
    Best regards,
    Fran.

  • DBIF_DSQL2_DEFAULT_CR_ERROR": APO Interface without monitor log

    Hi
    V3.x
    'Manage' in ODS - IP displays following message: " Request loaded using the APO interface without monitor log". The request is red in ODS and other requests after this request do not activate. Zero records were loaded from flat file.
    The request is green in Monitor.
    SM37 displays the following message: "ABAP/4 processor: DBIF_DSQL2_DEFAULT_CR_ERROR"
    What do I do to rectify this?
    Thanks
    Cj

    Hi
    please ignore my previous statement. I've noticed that the IP in the monitor is already green but that te following message is displayed: "Request REQU_49UKKF2TZEX4Z7WRU6BW28IM6 in ODS ZABAND must have QM status green before it ......"
    Now I sit with inactive requests before and after this request that is red.
    What do I do to rectify this please?
    Cj

  • TT14000: TimesTen daemon internal error: Could not send 'manage' request

    Hi
    I have got error like TimesTen daemon internal error: Could not send 'manage' request .Can any one help, why this error is came and what is solution for this.
    I have restarted the Timesten Daemon now its working fine.But why i got that error?
    Below is the tterror log :
    12:50:27.53 Err : : 31518: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc 400 err1 703 err2 836
    12:50:28.52 Warn: : 31518: 31522 ------------------: subdaemon process exited
    14:04:21.95 Warn: : 31518: 31619/0xcce7500: Recovery started
    14:04:23.01 Warn: : 31619: subd: Warning identified in [sub.c: line 2152]
    14:04:23.01 Warn: : 31619: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    14:04:23.01 Warn: : 31619: -- file "db.c", lineno 12011, procedure "sbDbConnect"
    14:04:23.01 Warn: : 31619: subd: connect trouble, rc 2, reason 20100
    14:04:23.01 Warn: : 31619: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    20:23:57.74 Warn: : 31518: 9216 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
    21:15:17.79 Warn: : 31518: 22608 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
    09:22:11.63 Warn: : 31518: 32431 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=21
    09:28:03.52 Warn: : 31518: 32417 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
    20:26:56.30 Warn: : 31518: 1165 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
    20:40:31.73 Warn: : 31518: 21549 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=3
    23:17:52.64 Warn: : 31518: 29899 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=20 '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=215
    09:42:29.96 Warn: : 31518: 22044 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
    13:12:19.91 Warn: : 31518: 16923 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
    19:42:46.21 Warn: : 31518: 10794 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
    00:00:06.83 Warn: : 6786: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 34 users
    00:00:06.83 Warn: : 6786: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
    00:00:06.83 Warn: : 6786: WARNING: data store no longer considered in use
    00:00:06.84 Warn: : 6786: WARNING: PL/SQL shared segment existed at time of daemon termination
    00:00:06.84 Err : : 6786: TT14000: TimesTen daemon internal error: Could not destroy PL/SQL shared memory, error
    00:00:06.84 Warn: : 6786: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    00:00:15.32 Warn: : 6786: 6792/0x1edfc500: Recovery started
    00:00:16.39 Warn: : 6792: subd: Warning identified in [sub.c: line 2152]
    00:00:16.39 Warn: : 6792: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    00:00:16.39 Warn: : 6792: -- file "db.c", lineno 12011, procedure "sbDbConnect"
    00:00:16.39 Warn: : 6792: subd: connect trouble, rc 2, reason 20100
    00:00:16.39 Warn: : 6792: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    17:51:04.03 Warn: : 6786: 17730 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=10
    10:03:44.61 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
    10:03:52.28 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
    10:04:02.73 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
    17:58:15.58 Warn: : 6786: 15156 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=7
    18:02:14.24 Warn: REP: 7064: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
    18:02:25.07 Warn: REP: 7064: got termination signal, stopping
    18:02:25.81 Warn: : 6790: got termination signal, stopping
    18:02:25.86 Warn: : 6792: got termination signal, stopping
    18:02:25.87 Err : : 6786: TT14006: TimesTen daemon disconnect failed: 6792/0x2aaab80008c0: disconnect complete: Disconnect not started. Info: 0 7064 0x1f758520 (/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32)
    18:02:25.87 Err : : 6792: TT14000: TimesTen daemon internal error: subd: Monitor thread failed to disconnect, tt error 798 (TT0798: Daemon reports error 0 -- file "db.c", lineno 16124, procedure "sbDbDisconnect").
    18:02:25.87 Warn: : 6786: got termination signal, stopping
    18:02:25.91 Warn: : 6789: got termination signal, stopping
    18:02:25.95 Warn: : 6791: got termination signal, stopping
    18:02:26.05 Err : : 6786: TT14000: TimesTen daemon internal error: Could not connect to subdaemon port 43791
    18:02:26.05 Err : : 6786: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
    18:02:26.05 Err : REP: 7064: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPHOLD' thread
    18:02:26.05 Err : REP: 7064: TT_TT70_32:repagent.c(3338): TT791: TT0791: Cannot communicate with subdaemon -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
    18:02:26.05 Warn: : 6786: 6792 ------------------: subdaemon process exited
    18:02:26.05 Warn: : 6786: 6792 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=10
    18:02:26.05 Warn: : 6786: daRecovery: subdaemon 6792, managing data store, failed: invalidate (failcode=202)
    18:02:26.05 Warn: : 6786: Invalidating the data store (failcode 202, recovery for 6792)
    18:02:26.11 Err : : 6786: Could not connect to subdaemon 6794, port 56784
    18:02:26.28 Warn: : 6786: 6789 ------------------: subdaemon process exited
    18:02:26.53 Warn: : 6786: 6791 ------------------: subdaemon process exited
    18:02:26.59 Warn: : 6786: 6790 ------------------: subdaemon process exited
    18:02:26.71 Err : : 6786: Could not connect to subdaemon 7064, port 45797
    13:42:14.95 Warn: : 10502: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    13:42:32.63 Err : : 10502: TT14000: TimesTen daemon internal error: Error 22 creating shared segment, KEY 0x4e048006
    13:42:32.63 Err : : 10502: -- OS reports invalid shared segment size
    13:42:32.63 Err : : 10502: -- Confirm that SHMMAX kernel parameter is set > datastore size
    13:42:32.63 Err : : 10508: subd: Error identified in [sub.c: line 2152]
    13:42:32.63 Err : : 10508: subd: (Error 836): TT0836: Cannot create data store shared-memory segment, error 22 -- file "db.c", lineno 9572, procedure "sbDbConnect"
    13:42:32.63 Err : : 10508: -- file "db.c", lineno 9572, procedure "sbDbConnect"
    13:42:32.63 Warn: : 10508: subd: connect trouble, rc 1, reason 836
    13:42:32.63 Err : : 10508: Err 836: TT0836: Cannot create data store shared-memory segment, error 22 -- file "db.c", lineno 9572, procedure "sbDbConnect"
    13:42:32.63 Err : : 10502: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc 400 err1 703 err2 836
    13:42:33.63 Warn: : 10502: 10508 ------------------: subdaemon process exited
    13:46:59.96 Warn: : 10502: 10605/0x819500: Recovery started
    13:47:01.02 Warn: : 10605: subd: Warning identified in [sub.c: line 2152]
    13:47:01.02 Warn: : 10605: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    13:47:01.02 Warn: : 10605: -- file "db.c", lineno 12011, procedure "sbDbConnect"
    13:47:01.02 Warn: : 10605: subd: connect trouble, rc 2, reason 20100
    13:47:01.02 Warn: : 10605: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    15:37:47.14 Warn: : 10502: 28930 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1392803846 count=1
    19:41:05.92 Warn: : 10502: 28950 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=1
    12:18:40.18 Warn: : 10502: 19264 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=16
    19:09:15.13 Warn: : 10502: 29472 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=24
    20:29:21.07 Warn: : 10502: 6896 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=27
    11:11:30.98 Warn: REP: 18767: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
    14:26:06.81 Warn: : 10502: 25502 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=3
    10:52:42.36 Warn: : 10502: 6487 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=12
    11:06:20.50 Warn: : 10502: 15322 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=1
    13:19:36.58 Warn: REP: 18767: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
    16:48:45.24 Warn: : 10506: got termination signal, stopping
    16:48:45.48 Warn: : 10505: got termination signal, stopping
    16:48:45.95 Warn: : 10502: 10505 ------------------: subdaemon process exited
    16:48:45.95 Warn: : 10502: 10506 ------------------: subdaemon process exited
    16:48:45.99 Warn: REP: 18767: got termination signal, stopping
    16:48:46.20 Warn: : 10507: got termination signal, stopping
    16:48:46.26 Warn: : 10502: got termination signal, stopping
    16:48:46.86 Warn: : 10605: got termination signal, stopping
    16:48:46.95 Warn: : 10502: 10507 ------------------: subdaemon process exited
    16:48:46.99 Err : : 10502: TT14000: TimesTen daemon internal error: Could not connect to subdaemon port 36872
    16:48:46.99 Err : : 10502: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
    16:48:46.99 Err : REP: 18767: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPLISTENER' thread
    16:48:46.99 Err : REP: 18767: TT_TT70_32:repagent.c(3338): TT791: TT0791: Cannot communicate with subdaemon -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
    16:48:46.99 Warn: : 10502: 10605 ------------------: subdaemon process exited
    16:48:46.99 Warn: : 10502: 10605 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=10
    16:48:46.99 Warn: : 10502: daRecovery: subdaemon 10605, managing data store, failed: invalidate (failcode=202)
    16:48:46.99 Warn: : 10502: Invalidating the data store (failcode 202, recovery for 10605)
    16:48:47.09 Err : : 10502: Could not connect to subdaemon 10510, port 58206
    16:48:47.16 Err : : 10502: Could not connect to subdaemon 18767, port 49611
    13:17:45.67 Warn: : 8602: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    13:17:52.84 Warn: : 8602: 8605/0x12207500: Recovery started
    13:18:41.73 Err : : 8602: 8789/(nil): /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/snmp.ini: bad -trap_dest value SMARTS4: Host not found (authoritative answer)
    13:31:31.49 Warn: : 8602: 5706 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=1
    01:25:41.22 Warn: : 8602: 18419 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=158
    10:29:11.03 Warn: : 8602: 30002 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=43
    12:47:07.86 Warn: : 8602: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
    12:47:07.87 Warn: : 8602: 8605/0x123481a0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    12:47:07.88 Warn: : 8605: Stopping subdaemon Log Marker thread for /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because db is invalid.
    12:47:07.88 Warn: : 8602: 8605/0x123a47b0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    12:47:07.96 Warn: : 8602: 8605/0x1243c900: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    12:47:08.88 Warn: : 8602: 8605 ------------------: subdaemon process exited
    12:47:08.88 Warn: : 8602: 8605 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=10
    12:47:34.78 Warn: : 20263: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 11 users
    12:47:34.78 Warn: : 20263: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
    12:47:34.78 Warn: : 20263: WARNING: data store no longer considered in use
    12:47:34.78 Warn: : 20263: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    12:51:06.94 Warn: : 20263: 20266/0x14690500: Recovery started
    16:29:00.34 Warn: : 20263: 22849 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 134512646 count=1
    10:12:26.98 Warn: REP: 20784: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. TimesTen replication agent is stopping
    10:12:30.91 Warn: : 20263: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
    10:12:30.91 Warn: : 20263: 20266/0x1479ff40: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:30.91 Warn: : 20266: Stopping subdaemon Log Marker thread for /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because db is invalid.
    10:12:30.91 Warn: : 20263: 20266/0x1488b830: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:30.96 Warn: : 20263: 20266/0x1486fa40: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.03 Warn: : 20263: 20266/0x2aaac40008c0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.34 Warn: : 20263: 20266/0x2aaac401c6b0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.40 Warn: : 20263: 20266/0x2aaac00008c0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.66 Warn: : 20263: 20266/0x2aaac4078700: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.91 Warn: : 20263: 20266 ------------------: subdaemon process exited
    10:12:31.91 Warn: : 20263: 20266 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 134512646 count=10
    10:12:36.28 Warn: : 14678: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 11 users
    10:12:36.28 Warn: : 14678: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
    10:12:36.28 Warn: : 14678: WARNING: data store no longer considered in use
    10:12:36.28 Warn: : 14678: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    10:13:25.52 Warn: : 14678: 14683/0x5121500: Recovery started
    10:10:12.39 Warn: : 14678: 15486 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
    10:06:55.19 Warn: : 14678: 30796 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
    09:58:48.69 Warn: : 14678: 12930 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
    15:27:42.39 Warn: : 14678: 7811 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
    10:16:36.60 Warn: REP: 14964: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
    10:53:27.24 Warn: : 14678: 11658 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
    15:11:33.81 Warn: : 14678: got termination signal, stopping
    15:11:34.63 Err : : 14678: Could not connect to subdaemon 14686, port 41664
    15:11:34.72 Warn: : 14682: got termination signal, stopping
    15:11:35.10 Warn: : 14681: got termination signal, stopping
    15:11:35.11 Warn: : 14684: got termination signal, stopping
    15:11:35.23 Warn: : 14683: got termination signal, stopping
    15:11:35.35 Warn: : 14678: 14684 ------------------: subdaemon process exited
    15:11:35.43 Warn: REP: 14964: got termination signal, stopping
    15:11:35.53 Warn: : 14678: 14681 ------------------: subdaemon process exited
    15:11:35.55 Warn: : 14678: 14682 ------------------: subdaemon process exited
    15:11:36.29 Err : : 14678: TT14000: TimesTen daemon internal error: 14683: Error processing 'unmanage' in subdaemon rc -2
    15:11:36.29 Err : : 14678: TT14000: TimesTen daemon internal error: Unparsable reply to unmanage
    15:11:36.29 Err : : 14678: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
    15:11:36.29 Err : REP: 14964: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPLISTENER' thread
    15:11:36.29 Warn: : 14678: 14683 ------------------: subdaemon process exited
    15:11:36.29 Err : REP: 14964: TT_TT70_32:repagent.c(3338): TT798: TT0798: Daemon reports error 0 -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
    15:11:36.30 Warn: : 14678: 14683 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
    15:11:37.63 Warn: : 14678: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
    15:54:42.72 Warn: : 8962: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 1 users
    15:54:42.73 Warn: : 8962: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
    15:54:42.73 Warn: : 8962: WARNING: data store no longer considered in use
    15:54:42.73 Warn: : 8962: WARNING: PL/SQL shared segment existed at time of daemon termination
    15:54:42.73 Err : : 8962: TT14000: TimesTen daemon internal error: Could not destroy PL/SQL shared memory, error 22
    15:54:42.73 Warn: : 8962: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    15:54:48.61 Warn: : 8962: 8973/0x17292500: Recovery started
    16:15:24.25 Warn: : 8962: 5703 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 251953159 count=1
    15:32:17.57 Warn: : 8962: 8974/0xff51500: Recovery started
    15:32:55.78 Warn: REP: 28114: SIPT_TT_SUB4:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out

    1)
    TimesTen Release 11.2.1.3.0 (64 bit Linux/x86_64) (TT_tt70_32:53388) 2009-08-21T05:34:23Z
    Instance admin: timesten
    Instance home directory: /opt/timesten/tt7032/TimesTen/TT_tt70_32
    Group owner: timesten
    Daemon home directory: /opt/timesten/tt7032/TimesTen/TT_tt70_32/info
    PL/SQL enabled.
    2)
    [TT_1121]
    Driver=/opt/timesten/tt7032/TimesTen/TT_tt70_32/lib/libtten.so
    DataStore=/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_1121
    DatabaseCharacterSet=US7ASCII
    3)
    kernel.shmmax = 2147483648
    kernel.shmall = 2097152
    4)
    MemTotal: 8171576 kB
    MemFree: 3754532 kB
    Buffers: 312052 kB
    Cached: 1656640 kB
    SwapCached: 0 kB
    Active: 3924072 kB
    Inactive: 309660 kB
    HighTotal: 0 kB
    HighFree: 0 kB
    LowTotal: 8171576 kB
    LowFree: 3754532 kB
    SwapTotal: 8388600 kB
    SwapFree: 8388600 kB
    Dirty: 652 kB
    Writeback: 4 kB
    AnonPages: 2265060 kB
    Mapped: 153924 kB
    Slab: 126580 kB
    PageTables: 12320 kB
    NFS_Unstable: 0 kB
    Bounce: 0 kB
    CommitLimit: 12474388 kB
    Committed_AS: 4718116 kB
    VmallocTotal: 34359738367 kB
    VmallocUsed: 284328 kB
    VmallocChunk: 34359452663 kB
    HugePages_Total: 0
    HugePages_Free: 0
    HugePages_Rsvd: 0
    Hugepagesize: 2048 kB

  • My manager request me to compare between (Directories, initialization param

    hi,
    my manager request me to compare between (Directories, initialization parameters, roles, profiles, tablespaces, users, redo logs) different databases by using SQL command line ( built-in package) not by tool ( Toad , ... )
    regards.
    Edited by: user13364155 on Mar 7, 2011 7:37 AM

    You have plenty of answers already in Re: Comparing Two DBs

  • Management console monitor logs disapear ?

    Has anybody experimented an issue with the management console monitor logs disapearing  ?
    I believe that it might be related to the repository table containing the logs ... has anybody an other idea ?
    Thanks

    Hi Dale Mahalko,
    Please refer the following KB to adjust your desktop resolution and monitor resolution to best resolution value.
    Getting the best display on your monitor
    http://windows.microsoft.com/en-us/windows/getting-best-display-monitor#getting-best-display-monitor=windows-7
    how to make the text on your screen larger or smaller
    http://windows.microsoft.com/en-us/windows7/make-the-text-on-your-screen-larger-or-smaller?v=t
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Why are there suddenly two icons in my URL (Google Manage Requests and Facebook Manage Requests) that I cannot control?

    Hi Mozilla ~
    In the URL field of Firefox, there are two icons on the far right, just left of the pull-down arrow and refresh arrow. They appear to be for Google and Facebook, both with tooltips that say, "View and Manage Requests". The pull-down menu allows me to manage those Friend requests they link to, but "Move to Menu" and "Remove from Toolbar" are greyed out and not actionable.
    Q1 - How did they get there?
    Q2 - How can I stop them from being placed automatically in the future by these privacy-muggers?
    Q3 - What are they doing in the URL field?
    Q4 - If the right-click context/pull-down menu has greyed out the option of "Remove from Toolbar", how can I delete them?
    FWIW, I have accounts with Google and Facebook but trust neither and so have blocked them in every way possible from watching me, sending me notifications, doing anything "for" me, etc. My Add-Ons may be visible in my account, but generally they are related to organizing: "Group Tabs", "Bookmarks" or to my customized work process: "Send to Kindle", "HTTPS Everywhere" and "Disconnect Privacy". I hope that helps.
    In an online world of sharks and blood-suckers, I trust Mozilla to help me be safe. Thank you for helping me figure out what Google and Facebook are going in my URL field.
    I prepared a JPG to show what it looks like but there is no upload image function in this screen... and I cannot seem to drag-and-drop the file into this form field. Please advise.
    ''[Personal information removed by moderator. Please read [[Forum rules and guidelines]], thanks.]''

    Hi - Thanks for responding.
    I've opened the Add-ons dialog and can confirm that I have both installed and enabled. I want them to stay this way, since I do not want either of them intruding on my privacy.
    That their icons have very recently (I only noticed them today) appeared in my URL field, and that they are seeking to push notifications of friend requests to me from that location, does not seem related to my use of the add-on that prevents them from tracking what websites I go to, which is what those two Disconnect add-ons seek to provide.
    Further insight and advice appreciated. I see there is a way to add an image to my concern, so here goes.
    Thanks again
    Alison

  • Manage request atributes in xhtml

    Is there any way to manage request attributes at xhtml in jsf2???
    I mean like scriptlest in jsp...
    v.g (here im not using request attributes).:
    <%@ page import="java.util.Calendar" %>
    <% if(Calendar.getInstance().get(Calendar.AM_PM) == Calendar.AM) { %>
    Good morning
    <% } else { %>
    Good afternon
    <% } %>
    I know about
    <h:body>
         <f:view>
                   <f:subview id="myIncludedPage">
                        <jsp:include page="included.jsp" flush="true" />
                   </f:subview>
         </f:view>
    </h:body>
    but i dont know if its the best way and i couldnt make it work giving next error:
    The prefix "jsp" for element "jsp:include" is not bound.
    Edited by: user9032732 on 06-jul-2011 12:15
    Edited by: user9032732 on 06-jul-2011 12:40

    Let me translate your scriptlet into JSF:
    <h:outputText rendered="#{calendarBean.AM}">Good morning</h:outputText>
    <h:outputText rendered="#{not calendarBean.AM}">Good afternoon</h:outputText>where you have created a bean mapped to #{calendarBean} and provide a isAM() method. Note an even more terse method:
    <h:outputText value="#{calendarBean.AM ? 'Good morning' : 'Good afternoon'}" />As far as your second snippet, it sounds like you are mixing JSP and JSF2 facelets-like tags, a no-no. Try:
    <h:body>
    <ui:include src="included.xhtml" />
    </h:body>Finally, as far as your original question about request attributes, JSF exposes them via #{param}. E.g. to access the value passed in under the name 'foo' use #{param.foo}:
    <h:outputText value="#{param.foo eq 'AM' ? 'Good morning' : 'Good afternoon'}" />

  • Alert Monitoring log

    Hi,
    When I configured alert monitoring. Alert is creating when I run report SXMSALERT_PROCESS_DATA_GET. But this alert is not reflecting in the alert inbox eventhough all configuration done. Then I have gone to log then I found errors as follows.
    warning: Address receiptent of "KPRKS00" (INT) could not be determined.   ( I configured this user as single receiptent in tcode alrtcatdef).
    ERROR: send Request for INT has no receipients.
    Any help in this regard is welcome. Thanks in advance.
    Thanks,
    Mallikarjun.M

    Hi,
        I follwed according to your steps. Finally I checked in alert Monitoring log, In that I noticed error as follows.
    warning: Address receiptant of "KPSSO" (INT)could not determined.
    ERROR: BCS Exception (DNS_SREQ) occured.
    I notice this is bcoz in tcode "ALERTCATDEF" in configuraiton I selected "internal processing".
    I hope a favourable reply. Thanks in advance.
    Thnaks,
    Mallikarjun.M

  • How to data load without monitor entry?

    Hello,
    the atttibuts of a character are filled daily. There is no Request.
    Does anyone know, how I can find out from where the Data comes without monitor entrys?
    Thank you!
    SW

    Hi
    You can check whether any customised ABAP coding is used to fetch data from some data source and fill the related master data
    RSRD_ATTR_DEP - dependencies of attributes.....
    Like this, there can be some link tables which could be used in custom ABAP code to automatically fill the attribute values
    Bye
    N Ganesh
    assign points if useful**

  • [SOLVED] x11vnc without monitor connected

    How to start correctly x11vnc (or eventually vncserver) without monitor connected?
    In the wiki is written
    "Note: By default, Xorg needs to be able to detect a monitor and will not start otherwise. A workaround is to create a configuration file such as the example above and thus avoid auto-configuring. A common case where this is necessary is headless system, which boots without a monitor and starts Xorg automatically, either from virtual console and login, or using a display manager."
    However this is not working in mycase. I cannot connect to previuosly configured x11vnc if monitor is detached. X is not starting. I am sure that the driver is right.
    This is a system with LXQt desktop and sddm.
    Last edited by hifi25nl (2015-05-14 11:03:32)

    The dummy config file found in the wiki worked fine for me for the xserver itself (just make sure to pick the resolution(s) you want), but not all display managers worked correctly (GDM in particular is a problem, but I've had trouble with others).  I've been able to use x11vnc on headless systems ranging from 5th generation i7's to raspberry Pis, so it's definitely possible.
    It would help if you could provide your xorg.conf.d configuration, and your X or VNC logs so we could see what the issue is. 
    Try disabling your display manager and rebooting without a monitor attached, starting x manually via ssh, and then exporting the DISPLAY before starting x11vnc. For example try running the following lines interactively from the console via ssh.
    startx &
    export DISPLAY=:0
    xrandr --fb 1920x1080
    x11vnc --fbauth /path/to/password -display :0 -geometry 1920x1080 auth guess -forever -bg
    Make sure to pick a mode (resolution) that's supported in your configuration files, etc. Those commands should give you copious error messages if they fail, which will give us a place to start.
    As an aside, if all you want is a vncserver, tigervnc will work with much less fuss because it creates a virtual display so you don't need to mess with your xorg settings at all.  x11vnc (without addins) relies on your system's literal physical display output device, which is what necessitates all the xorg fiddling.  The only reason to use x11vnc is if you need to remote control an actual screen (which doesn't sound like your use case) or if you need the desktop you're VNCing into to have hardware acceleration for some reason.  Tigervnc will "just work" in most setups without significant additional configuration.
    Last edited by mwillems (2015-05-13 19:48:47)

  • Manage transports (without ChaRM) in Solution Manager?

    Hi,
    How do I manage transports in target systems (ECC, APO, etc.) using Solution Manager. We have the Dev systems (ECC, APO) connected using RFC to Solution Manager. Configuration (SOLAR02) will be done using Solution Manager. So the question is - how do we manage transports (without ChaRM being present) using Solution Manager?
    Any suggestions/recommendations? I would greatly appreciate any feedback.
    Edited by: GiveMeFood on Sep 22, 2011 10:05 PM

    Hi,
    One of the main features available with the Solution Manager is ChaRM. It has been introduced to basically deal with the diverse transports management and related control framework over the SAP lanscape. Having a Solution Manager and not using ChaRM defeats the purpose of installing a Solution Manager in the first place. A better approach would be to incorporate the features provided by the system.
    In my opinion - you should configure ChaRM, else it would not make sense to have the SolMan in the landscape. You would start using one of the features which you already have !
    Regards,
    Srikishan

  • Communication channel monitoring logs

    Dear all,
    on weekend we had a problem with a CC. Messages not have beend pick up from
    a FTP server. The problem was solved automatically and I was not able to see
    any error entries in the CC monitoring log files because there were to many
    entries without error.
    My question:
    Is there an option for persisting the logs into a trace file on server? I was not
    able to find the entries in defaultTrace or anywhere else.
    How to raise the time/size of the log files?
    Thanks
    Chris

    Hi,
    I think the channel was getting locked and so, it could not pick up any data.
    Refer the SAP note 849089 for this.
    -Supriya.

Maybe you are looking for