Error PCC-S-02319 managing host arrays in pro*C

Hi all,
Pro*C is retrieving the error: "PCC-S-02319, expression type does not match usage" when tries to compile this lines:
for (i= 0; i < MAX_SAIS_POR_RECINTO && DniSAIs[i] != DNI_NULO; i++)
EXEC SQL AT :NombreBD
INSERT INTO SAIS_POR_RECINTO
( TIPO_CONF, DNI_EDIFICIO, DNI, DNI_EDIFICIO_SAI, DNI_EQUIPO_SAI )
VALUES
( :TipoConf, :DniEdificio, :Dni, :DniSAIs[2*i], :DniSAIs[2*i+1] );
Semantic error at line 4583, column 56, file __EnBDmodRciI.pc:
( :TipoConf, :DniEdificio, :Dni, :DniSAIs[2*i], :DniSAIs[2*i+1] );
.......................................................1
I'm compiling a library written in pro*C. I know that the code is well written because it have been compiled before in another machine. The fact is that they pass me the code to generate another compilation environtment in a new server. I think the problem may be in any precompiling directive because the file pcscfg.cfg is empty. In the makefile are used the following directives:
MYPCCFLAGS= PARSE=FULL CODE=ANSI_C UNSAFE_NULL=YES MODE=ORACLE DBMS=V7
I have been reading tutorials about host arrays, but doesn't says anything about ay restriction in using operators with arrays (i.e arr[i+3)) when insert or update data.
Anyone could help me?
Thank you.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

What about post your question here
Oracle Discussion Forums » Oracle Database » C++ Call Interface (OCCI)
Mark this thread as answered

Similar Messages

  • 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

  • Errors in the metadata manager

    Hi Experts,
    Periodically we're seeing Error Event ID's 18 and 19 on our SSAS server (SQL Server 2008 R2) hosting SCSM Data Warehouse DB's.
    The cube's appear to be processing OK from what I can tell, but everything I can find online relating to these errors indicates some corruption in the Data directory.  We get these errors in two different, separate SCSM environments (SCSM 2012 SP1 UR4). 
    Has anyone ever experienced these Errors before?
    Below are the details for these Errors.
    Log Name:      Application
    Source:        MSSQLServerOLAPService
    Date:          1/9/2014 3:07:12 AM
    Event ID:      19
    Task Category: (289)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SCSMP06SQL.wcbbc.wcbmain.com
    Description:
    Errors in the metadata manager. An error occurred when loading the ReviewActivityCreatedByUser partition, from the file, '\\?\H:\OLAP\Data\DWASDataBase2.0.db\SystemCenterChangeAndActivityManagementCube.0.cub\ReviewActivityCreatedByUser.0.det\ReviewActivityCreatedByUser.223.prt.xml'.
    Log Name:      Application
    Source:        MSSQLServerOLAPService
    Date:          1/9/2014 3:33:08 AM
    Event ID:      18
    Task Category: (289)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SCSMP06SQL.wcbbc.wcbmain.com
    Description:
    Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\H:\OLAP\Data\DWASDataBase2.0.db\SystemCenterWorkItemsCube.0.cub\BillableTimeBilledByUser.1830.det.xml'.

    Hi David,
    Did you end up resolving this? I've just come across the same error this morning (different cube reference though) and am beginning to look at the issue.
    Cheers,
    Lain

  • ORA-19511: Error received from media manager layer, error text:

    Dear Concern,
    When I am restoring the oracle 9i database by brtools for SAP ECC 5.0 the following error message appeared. Mention that, this is second time restoration. First time restoration was successfull. After that one of us change some permission in differerent folders and files in the hp-ux server. Now we facing the following problem. Please help me...
    BR0449I Restore mode: ALL
    BR0419I Files will be restored from backup: bechtawc.fnr 2010-01-08 20.00.06
    BR0416I 100 files found to restore, total size 520901.781 MB
    BR0424I Files will not be decompressed
    BR0421I Restore device type: rman_util
    BR0280I BRRESTORE time stamp: 2010-01-19 16.19.21
    BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRRESTORE:
    BR0280I BRRESTORE time stamp: 2010-01-19 16.19.23
    BR0257I Your reply: 'c'
    BR0259I Program execution will be continued...
    BR0280I BRRESTORE time stamp: 2010-01-19 16.19.23
    BR0554I Starting restore from full database backup using RMAN...
    BR0278E Command output of 'SHELL=/bin/sh /oracle/PRD/920_64/bin/rman nocatalog':
    Recovery Manager: Release 9.2.0.1.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.
    RMAN>
    RMAN> connect target /;
    connected to target database: PRD (DBID=1654880374)
    using target database controlfile instead of recovery catalog
    RMAN> *end-of-file*
    RMAN>
    host command complete
    RMAN> 2> 3> 4> 5> 6> 7> 8>
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on sbt_1 channel at 01/19/2010 16:19:24
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
    HP-UX Error: 8324: Unknown system error
    Additional information: 7110
    ORA-19511: Error received from media manager layer, error text:
       SBT error = 7110, errno = 8324, sbtinit: internal error - invalid argument(s)
    RMAN>
    Recovery Manager complete.
    BR0280I BRRESTORE time stamp: 2010-01-19 16.19.24
    BR0279E Return code from 'SHELL=/bin/sh /oracle/PRD/920_64/bin/rman nocatalog': 1
    BR0536E RMAN call for database instance PRD failed
    BR0280I BRRESTORE time stamp: 2010-01-19 16.19.24
    BR0556E Restore from full database backup using RMAN failed
    Best Regards
    Wahid

    Hi,
    It is mentioned that I already have done a restoration and recovery first time. But when I tried to do the same job I mean restoration in second time for a specific requiremnt I am getting the above error.
    Our syestem info is:
    DB: Oracle 9i
    OS: HP-UX
    Storage: EMC storage
    Backup tools: Data protector 5.5
    Please help me.
    Regards
    Wahid

  • WLST - error when i start managed server using nmstart() command.

    i am receiving an error when start the managed server using nmstart(). Please advise.
    Do I have add any parameter to nodemanager.properties file?
    Thankyou
    pasted below is the error message i am receiving when i start managed server.
    Starting server hssclient ...This Exception occured at Thu Mar 19 10:30:02 EDT 2
    009.
    java.lang.IllegalArgumentException: Invalid host name: Null or empty
    at weblogic.nodemanager.client.NMClient.checkNullOrEmpty(NMClient.java:7
    2)
    at weblogic.nodemanager.client.NMClient.setHost(NMClient.java:79)
    at weblogic.nodemanager.mbean.NodeManagerRuntime.getNMClient(NodeManager
    Runtime.java:527)
    at weblogic.nodemanager.mbean.NodeManagerRuntime.getNMClient(NodeManager
    Runtime.java:565)
    at weblogic.nodemanager.mbean.NodeManagerRuntime.start(NodeManagerRuntim
    e.java:188)
    at weblogic.server.ServerLifeCycleRuntime.startServer(ServerLifeCycleRun
    time.java:439)
    at weblogic.server.ServerLifeCycleRuntime.start(ServerLifeCycleRuntime.j
    ava:124)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean
    .java:428)
    at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImp
    l.java:213)
    at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
    BeanServerInterceptor.java:815)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784
    at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBea
    nServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:248)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.
    run(WLSMBeanServerInterceptorBase.java:443)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
    oke(WLSMBeanServerInterceptorBase.java:441)
    at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterce
    ptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:63)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.
    run(WLSMBeanServerInterceptorBase.java:443)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
    oke(WLSMBeanServerInterceptorBase.java:441)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(
    SecurityInterceptor.java:426)
    at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
    ptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
    at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
    ptor$10.run(AuthenticatedSubjectInterceptor.java:580)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
    ptor.invoke(AuthenticatedSubjectInterceptor.java:573)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanSer
    ver.java:310)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnecti
    onImpl.java:1410)
    at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectio
    nImpl.java:81)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run
    (RMIConnectionImpl.java:1247)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(R
    MIConnectionImpl.java:1350)
    at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImp
    l.java:784)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown S
    ource)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:439)
    at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:6
    1)
    at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicSer
    verRef.java:983)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Hi I am getting below exception, is nmStart only start AdminServer ????
    There are 1 nested errors:
    weblogic.management.ManagementException: Booting as admin server, but servername, MS1, does not match the admin server name, AdminServer
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:803)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:493)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
    at weblogic.Server.main(Server.java:67)
    >
    <Feb 10, 2010 1:45:17 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Feb 10, 2010 1:45:17 PM UTC> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Feb 10, 2010 1:45:17 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <Feb 10, 2010 1:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 8275>
    <Feb 10, 2010 1:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Feb 10, 2010 1:45:17 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    ~

  • Routine AFPEIM encountered an error while starting concurrent manager STAND

    hi,
    Today i have done cloning and clone completed successfully. but CM is not comming up. I found the following errors in the concurrent log. Any hints on this.
    ==========================================
    Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
    Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
    Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
    Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
    Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
    Starting PODAMGR Concurrent Manager : 28-FEB-2012 13:33:48
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/POXCON.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator t : 28-FEB-2012 13:33:49
    Starting PODAMGR Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/POXCON.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator t : 28-FEB-2012 13:33:49
    Starting PODAMGR Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/POXCON.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator t : 28-FEB-2012 13:33:49
    Starting RCVOLTM Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/RCVOLTM.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
    Starting RCVOLTM Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/RCVOLTM.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
    Starting RCVOLTM Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/RCVOLTM.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
    Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
    Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
    Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
    Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
    Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:50
    Starting TDSMGR Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager TDSMGR with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:50
    Starting TDSMGR Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager TDSMGR with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:50
    Starting TDSMGR Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager TDSMGR with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:50
    Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
    Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
    Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
    Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
    Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:50
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:50
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:53
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:53
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:53
    Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:53
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:53
    Starting PASMGR Concurrent Manager : 28-FEB-2012 13:33:53
    CONC-SM TNS FAIL
    Routine AFPEIM encountered an error while starting concurrent manager PASMGR with library /eqaappl/drqaebiz/appl/pa/11.5.0/bin/PALIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system administrator to : 28-FEB-2012 13:33:53
    Process monitor session ended : 28-FEB-2012 13:33:53
    ==========================================
    i have done already steps mentioned in 1312632.1 but nor worked for me.
    also i ran below command and output is as follows.
    SQL> select CONCURRENT_QUEUE_NAME
    from FND_CONCURRENT_QUEUES
    where CONCURRENT_QUEUE_NAME like 'FNDSM%';
    2 3
    CONCURRENT_QUEUE_NAME
    FNDSM_DRQAEBS
    SQL>
    Version details are 11.5.10.2 and DB is 11g.
    Regards
    DBA.

    Hi;
    Please see:
    R12 instance Concurrent manager  and host status is showin as down
    Regard
    Helios

  • Dynamic List - Error processing insertText tag: 'loop' parameter arrays must be...

    Hi, I'm using Dreamweaver CS3 and ADDT (PHP/MySQL).
    I have many forms that I created with "Create Dynamic List Wizard", and All it's working fine until now, suddendly when I enter an any form, click Application / Server Behaviors, I saw a red symbol "!" next to Dynamic List Layout, I clicked it in order to make any changes, and then when I tried to save I got the following error message:
    "Error processing insertText tag: 'loop' parameter arrays must be the same length. The 'loop' parameter 'tableCSSWidth' does not have the same length as the previous 'loop' parameter(s)."
    This is happening with others form in my application. I can made some changes through "code", but others no...
    I would like to know what its' happening with then "dynamic List" server behavior?
    I appreciate your help. Thanks!
    Ernesto

    Hello Ernesto,
    Please follow these exact steps:
    - go to this location on your disk (enable view of hidden files):
    - "c:\Documents and Settings\XP_user\Application Data\Adobe\Dreamweaver 9\Configuration"
    ( if you are on Windows OS)
    or:
    - "Macintosh HD:Users:MAC_User:Library:Application Support:Adobe:Dreamweaver 9:Configuration"
    ( if you are on MAC OSX)
    - rename the "Configuration" folder to "Configuration_old"
    - open Extension Manager and remove all extensions
    - install Developer Toolbox extension
    - start DW and check if the problem still occurs
    regards,
    Ionut

  • Pro*C: host array insert using VARCHAR

    I followed the sample program sqlvcp.pc (explained in the ORACLE docu for Pro*C) to select severel rows from the database into an host array of varchar. This needs only one FETCH in program and works very well.
    I tried to use the same method to insert a host array of varchar into the database.
    BUT unfortunately only one row is inserted and then I get the error -01458.
    I checked data in my host array (allocated with malloc) using a debugger and I can't find an error.
    Is it possible to use this method to insert several rows out of a host array of varchar into the database using only one insert statement?
    If yes, for what do I have to take care of?
    Or do I have to use a loop with one insert for every row. This would be much slower!
    Thanks for Help.

    Hi prajithparan,
    Thanks for the response. I already looked at the link and a few other links in this forum that are related to array inserts/updates. However, I could not find answers to my specific questions. I am specifically concerned with the setup of parameters to the API calls (OCIBindByName and OCIBindArrayOfStruct) that fully reflects the two-dimensional nature of the array of structs that I am trying to insert.
    Moreover, I need to set the data type of the columns to be inserted as SQLT_STR. I think this data type requires the programmer to supply the length of the null terminated C strings as well. If we are inserting just one column, we can provide the length of each of the strings to be inserted into a VARCHAR2 column as part of a OCIBind call, for each of those columns.
    Since in an array insert, we are supplying multiple rows at the same time, how do we supply the lengths of strings to be inserted ? Should it be some form of two-dimensional array ?
    I could not get clear answers to these questions from either the Oracle documentation or the links on this forum. May be the answers are there and I am just missing them ?

  • Updating with Host Arrays

    Hello,
    I would like to query the Oracle community about an item
    that is giving me some trouble.
    I am developping a real time data base for a utility and I
    have situation where I receive messages from the SCADA of which
    not all are included in the database (for example, the firmware
    of some SCADA components has not been programmed correctly and
    gives the wrong ID number); I have to update the data base and
    then resend to other process the messages I have received.
    Naturally I do not want to resend the messages that contain the
    wrong information, and as this is a real time data base, I try
    to use the fastest techniques available (to the best of my
    knowledge), in this case, host arrays.
    The trouble is, when updating with host arrays, if no data
    is found for a particular ID ( Error ORA-1403), oracle continues
    and follows on with the next item in the host array, which is
    great, but it does warn you (as far as I know), that that
    particulat member of the host array is not included in the data
    base.
    Is there any method with which I can find out which member
    (s) failed in the update? or which members succeded?
    Thanks!!!!
    null

    I found after testing that your response is correct.
    The database does not consider '0 rows updated' a true error condition, therefore sqlerrd[2] reports the number of rows that WERE updated,NOT the array offset of the row that did not get updated.
    Furthermore, through extensive testing, I have found that the behavior I was told to expect by Oracle is NOT how Oracle behaves. Specially, if I have 5 array items, and item 3 does not result in an update, sqlerrd[2] reports 4 - meaning 4 rows updated, not 2, meaning that the third array item failed to result in an update.
    If the first item does not result in an update, the second item results in an update, and the 3rd item results in an oracle error (field too large for instance),sqlerrd[2] does not return 2 as expected (indicating the error occured in array item 3) but instead returns a 1, indicating one row was updated before the error occurred.
    Test scenario as follows:
    for some table, col1 CHAR[10], col2 CHAR[3] with the following rows:
    200010, ABC
    200020, ABC
    200030, ABC
    200040, ABC
    200050, ABC
    The statement in the ProC code:
    UPDATE tablename SET col2 = :v1 where col1 = :v2;
    col1 array holds:
    200011
    200020
    200030
    200040
    200050
    col2 array holds:
    XYZ
    XYZ
    XYZZ <<< note field too long forcing Oracle error
    XYZ
    XYZ
    I would expect based on the documentation that sqlerrd[2] returns 2 (3rd array element results in Oracle error), but what happens instead is sqlerrd[2]
    returns 1 (indicating that one row was updated, col1=200020, before an error was encountered in 3rd element of array.
    If col2 array holds:
    XYZ
    XYZ
    XYZ
    XYZ
    XYZ
    I would expect based on the feedback in the TAR that sqlerrd[2] would return 0 indicating that the first array resulted in a 1403 - what I get is 4,
    indicating 4 rows were updated as a result of this array.

  • Error while creating persistence manager

    Folks,
    I have been receiving the following error while trying to invoke a subprocess in a flowN (the subprocess wraps some logic around a stored procedure call). There error is appearing N-1 times consistently (only one of the four transactions I'm testing is going through).
    <remoteFault>
    <part name="code" >
    <code>Server.userException</code>
    </part>
    <part name="summary" >
    <summary>when invoking endpointAddress 'http://crmoasdev.XXXX.com:7778/orabpel/CDH_inbound/XXXX_CDH_in_ProcessRewards/1.0', ORABPEL-05226 Error while creating persistence manager. An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat". The exception reported was: </summary>
    </part>
    <part name="detail" >
    <detail>AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: ORABPEL-05226 Error while creating persistence manager. An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat". The exception reported was: faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:crmoasdev.XXXX.com </detail>
    </part>
    </remoteFault>The domain log information is as follows:
    <2006-05-17 15:18:24,666> <WARN> <CDH_inbound.collaxa.cube.engine.deployment> <TypeHelperLoader::getBizdocVersionUID> missing resource: java.util.MissingResourceException: Cant find resource for bundle com.oracle.bpel.client.i18n.resources_client, key LOG_W_BD_out_of_date_class
    <2006-05-17 15:18:24,675> <ERROR> <CDH_inbound.collaxa.cube.engine.deployment> <TypeHelperRegistry::generatePersistenceManager> Error while creating persistence manager.
    An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat".  The exception reported was:
    <2006-05-17 15:18:24,675> <ERROR> <CDH_inbound.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube engine": Error while creating persistence manager.
    An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat".  The exception reported was:
    ORABPEL-05226
    Error while creating persistence manager.
    An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat".  The exception reported was:
         at com.collaxa.cube.engine.deployment.TypeHelperLoader.generatePersistenceManager(TypeHelperLoader.java(Compiled Code))
         at com.collaxa.cube.engine.deployment.TypeHelperLoader.loadPersistenceManager(TypeHelperLoader.java(Compiled Code))
         at com.collaxa.cube.engine.deployment.TypePersistenceRegistry.getPersistenceManager(TypePersistenceRegistry.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.getPersistenceManager(PersistenceService.java(Inlined Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.List__CXPM.prepareToSave(List__CXPM.java(Compiled Code))
         at com.collaxa.cube.engine.persist.Vector__CXPM.prepareToSave(Vector__CXPM.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.Map__CXPM.prepareToSave(Map__CXPM.java(Compiled Code))
         at com.collaxa.cube.engine.persist.Hashtable__CXPM.prepareToSave(Hashtable__CXPM.java:41)
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.types.bpel.CXMessageVariable__CXPM.prepareToSave(CXMessageVariable__CXPM.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.persist.BaseScope__CXPM.prepareToSave(BaseScope__CXPM.java(Compiled Code))
         at com.collaxa.cube.engine.persist.Scope__CXPM.prepareToSave(Scope__CXPM.java(Compiled Code))
         at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
         at com.collaxa.cube.engine.enc.ScopeContextSerializer.serializeContext(ScopeContextSerializer.java(Compiled Code))
         at com.collaxa.cube.engine.enc.ScopeContextSerializer.toBin(ScopeContextSerializer.java(Compiled Code))
         at com.collaxa.cube.engine.adaptors.common.BaseCubeInstancePersistenceAdaptor.store(BaseCubeInstancePersistenceAdaptor.java(Compiled Code))
         at com.collaxa.cube.engine.adaptors.oracle.CubeInstancePersistenceAdaptor.store(CubeInstancePersistenceAdaptor.java(Compiled Code))
         at com.collaxa.cube.engine.data.CubeInstancePersistenceMgr.store(CubeInstancePersistenceMgr.java(Compiled Code))
         at com.collaxa.cube.engine.CubeEngine.store(CubeEngine.java(Compiled Code))
         at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java(Compiled Code))
         at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java(Compiled Code))
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java(Compiled Code))
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java(Inlined Compiled Code))
         at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java(Compiled Code))
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java(Compiled Code))
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java(Inlined Compiled Code))
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java(Compiled Code))
         at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.processBPELMessage(CXSOAPProvider.java:632)
         at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.invoke(CXSOAPProvider.java:133)
         at org.collaxa.thirdparty.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
         at org.collaxa.thirdparty.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
         at org.collaxa.thirdparty.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
         at org.collaxa.thirdparty.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:450)
         at org.collaxa.thirdparty.apache.axis.server.AxisServer.invoke(AxisServer.java:285)
         at org.collaxa.thirdparty.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java(Compiled Code))
         at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
         at org.collaxa.thirdparty.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java(Compiled Code))
         at com.collaxa.cube.fe.CollaxaServlet.service(CollaxaServlet.java(Compiled Code))
         at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java(Compiled Code))
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java(Compiled Code))
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java(Compiled Code))
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java(Compiled Code))
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
         at java.lang.Thread.run(Thread.java:568)
    <2006-05-17 15:18:24,803> <WARN> <CDH_inbound.collaxa.cube.engine.deployment> <TypeHelperLoader::getBizdocVersionUID> missing resource: java.util.MissingResourceException: Cant find resource for bundle com.oracle.bpel.client.i18n.resources_client, key LOG_W_BD_out_of_date_classThanks for your help,
    Joseph

    hmmm what was the usecase ...
    was it after deployment, or just after new installation? this looks like a defect on loading side .. other axis stuff running around?
    at least it's good to hear that you are up & running now :-)
    /clemens

  • Error while starting weblogic Managed Server

    Hi ,
    I am new to SOA 11g. I installled the latest version(11.1.1.4) of all the components.I started web logic and able to login into Admin Console but I have a problem
    while starting Managed Server.It gives me an error saying
    <Feb 2, 2011 2:01:29 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 17.0-b17
    from Sun Microsystems Inc.>
    <Feb 2, 2011 2:01:30 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: Unable to obtain lock on C:\Oracle\Middleware\user_projects\domains\fmw_domain\servers\AdminServer\tmp\AdminServer.lok.
    Server may already be running
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)
    at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
    at weblogic.Server.main(Server.java:71)>
    <Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Feb 2, 2011 2:01:30 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Can anyone help ?
    Regards,
    Vikas Manchanda
    Edited by: 829347 on Feb 2, 2011 12:48 AM

    How are you starting the managed server? Is it a new install? The error suggests that the managed server is already running. You could check the windows task manager to see if there is a Java process running (or two if managed and admin server is on the same machine)
    Damien

  • How to fetch and display arbitrary log files from a managed host?

    We are creating a small management portal for a custom application and need a way to display, in a browser, the contents of an arbitrary log file located on an EM managed host. The effect we are looking for is similar to what you get when you show the contents of a database alert log using EM.
    I want to extend the EM agent to get the log and display the contents, but see two problems: (1) it seems like we would have to schedule the fetch of the log contents to happen on a regular basis and would not be able to do it on demand and (2) storing the results in the EM repository seems like it could consume a pile of storage, even if it only stores the logs for 24 hours.
    I am pretty sure we can bypass the repository somehow because I think the "show database alert log" EM process does so. Of course, I can't really be sure how this code is getting the alert log, but it seems reasonable to assume it is using the management agent.
    Is there some API for the EM Agent that I am missing?
    Any ideas would be appreciated.

    From within OEM it doesnt look possible. User defined metrics (UDM) can only return number or a string. The alertlog fetch is done via alertlogViewer.pl while being passed a couple of parameters.
    OEM does have a preliminary/rough api available at http://www.oracle.com/technology/products/oem/emx/index.html but I havent seen anyone make use of it yet.
    If you use just a web connection then you will probably run into security issues as a web server can usually only view/access stuff under their htmldoc dir.
    Seems like some non-OEM very custom code is what you seek..

  • Error while running the Managed server

    Hi
    i am getting the below error while running the Managed server.
    java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050633> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
    ####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050711> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
    ####<Dec 6, 2011 7:47:30 PM IST> <Error> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050726> <BEA-149231> <Unable to set the activation state to true for the application 'DMS Application [Version=11.1.1.1.0]'.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "Spy" failed to preload on startup in Web application: "dms.war".
    java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    can anyone help

    Srinath is 100% correct.
    If the deployment failed, then there will very likely be some mention in the log.
    You state that you checked the log, but you didn't mention whether you found an error, no error, a successful startup, etc. you are providing painfully few details to assist.
    I would bet if you posted your .log and .out logs to Pastebin.com - #1 paste tool since 2002 and provided us links, We would be able to point out the error.
    Lacking that information, my best advice would be to re-install and double-check you're completing all steps in the correct order.
    Also, be sure to always search the product documentation first, the search this forum. For basic issues (e.g., standard installation), there is a high probability that someone else has asked that question.
    I hope that helps,
    -ryan

  • Error while Deploying Performance Management samples in XI R3.0

    Error while Deploying Performance Management samples in XI R3.0
    I get an error when deploying the PM samples. I have set the PM repository pointing to AFDEMO database
    I have used to Java of BO dir as well as the program files\Java (1.6.03)
    I run the runPublishUtil.bat  and get the below error
    Can anyone help me to publish the PM demo's
    Regards
    Ishaq
    Edited by: ishaqbaig on May 10, 2009 1:42 PM

    Error when runPublishUtil,bat
    C:\Program Files\Business Objects\Performance Management 12.0\setup>set JARLOC=..\..\common\4.0\java\lib\
    usage : runPublishUtil.bat [dbusername] [dbuserpassword]
    C:\Program Files\Business Objects\Performance Management 12.0\setup>java -classpath publishUtil.jar;..\..\common\4.0\java\lib\cecore.jar;..\..\common\4.0\java\lib\logging.jar;..\..\common\4.0\java\lib\celib.jar;..\..\common\4.0\java\lib\ceplugins.jar;..\..\common\4.0\java\lib\cesession.jar;..\..\common\4.0\java\lib\corbaidl.jar;..\..\common\4.0\java\lib\ebus405.jar;..\..\common\4.0\java\lib\external\xercesImpl.jar;..\..\common\4.0\java\lib\external\xml-apis.jar;..\..\common\4.0\java\lib\rascore.jar;..\..\common\4.0\java\lib\serialization.jar;..\..\common\4.0\java\lib\cereports.jar com.businessobjects.util.PublishUtil ".\PublishUtil.properties" sa forms45
    caught SDKException
    com.crystaldecisions.sdk.exception.SDKServerException: Enterprise authentication
    could not log you on. Please make sure your logon information is correct. (FWB
    00008)
    cause:com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2
    detail:Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)
    The server supplied the following details: OCA_Abuse exception 10498 at [.\secpluginent.cpp : 826]  42040 {}
            ...Invalid password
            at com.crystaldecisions.sdk.exception.SDKServerException.map(SDKServerException.java:107)
            at com.crystaldecisions.sdk.exception.SDKException.map(SDKException.java:193)
            at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:701)
            at com.crystaldecisions.sdk.occa.security.internal.LogonService.userLogon(LogonService.java:295)
            at com.crystaldecisions.sdk.occa.security.internal.SecurityMgr.userLogon(SecurityMgr.java:162)
            at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon(SessionMgr.java:422)
            at com.businessobjects.util.PublishUtil.logon(Unknown Source)
            at com.businessobjects.util.PublishUtil.main(Unknown Source)
    Caused by: com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2
            at com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuseHelper.read(oca_abuseHelper.java:106)
            at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAs._LogonEx4Stub.UserLogonEx4(_LogonEx4Stub.java:80)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at com.crystaldecisions.enterprise.ocaframework.ManagedService.invoke(ManagedService.java:420)
            at com.crystaldecisions.sdk.occa.security.internal._LogonEx4Proxy.UserLogonEx4(_LogonEx4Proxy.java:222)
            at com.crystaldecisions.sdk.occa.security.internal.LogonService.doLogon(LogonService.java:347)
            at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:676)
            ... 5 more
    Exception in thread "main" java.lang.NullPointerException
            at com.businessobjects.util.PublishUtil.waitForValidInputFRS(Unknown Source)
            at com.businessobjects.util.PublishUtil.main(Unknown Source)
    Edited by: ishaqbaig on May 10, 2009 12:49 PM

  • Error while starting oam managed server

    Hi Experts,
    I am facing the following errors while starting the managed oam server instance.
    I am using 11gR2.
    <Jan 8, 2013 12:13:32 PM IST> <Error> <oracle.jps.audit> <BEA-000000> <IAU:IAU-5
    048: Problem in transferring audit record to Audit Store null null. Please verif
    y your Audit Store configuration>
    <Jan 8, 2013 12:13:49 PM IST> <Error> <oracle.security.audit.logger> <BEA-000000
    <IAU:JNDI Resource does not exist JNDI Name=AuditDB><Jan 8, 2013 12:13:49 PM IST> <Error> <oracle.jps.audit> <BEA-000000> <IAU:IAU-5
    047: Problem in transferring audit record from file:C:\Oracle\MIDDLE~1\USER_P~1\
    domains\OAM_OA~3\servers\oam_server1\logs\auditlogs\OAM\audit.log position:898,9
    24 will retry in next cycle. caught exception oracle.security.audit.AuditExcepti
    on: javax.naming.NameNotFoundException: Unable to resolve 'AuditDB'. Resolved ''
    ; remaining name 'AuditDB'
    at oracle.security.audit.ajl.loader.OracleRepository.<init>(OracleReposi
    tory.java:84)
    at oracle.security.audit.ajl.loader.JDBCLogWriter.reinit(JDBCLogWriter.j
    ava:59)
    at oracle.security.audit.ajl.loader.JDBCLogWriter.write(JDBCLogWriter.ja
    va:104)
    at oracle.security.audit.ajl.loader.AuditLoader.readMessages(AuditLoader
    .java:488)
    at oracle.security.audit.service.AuditLoaderManager.readMessages(AuditLo
    aderManager.java:209)
    at oracle.security.audit.service.AuditLoaderManager$Runner.run(AuditLoad
    erManager.java:284)
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'AuditDB'. Reso
    lved ''; remaining name 'AuditDB'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
    NamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
    a:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.j
    ava:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:20
    6)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.j
    ava:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at oracle.security.audit.ajl.loader.OracleRepository.<init>(OracleReposi
    tory.java:74)
    ... 5 more
    Any pointers would be appreciated.
    Thanks,
    Subin

    Hi Subin,
    Once the server is started, is Auditing to DB successful?
    Assuming that you have auditing to DB configured and that it is generally working, I suspect that the errors messages are occurring during the time when the server is making the jndi sources available to the server. If so, the messages are harmless (although I do not think they should happen).
    Regards,
    Colin

Maybe you are looking for

  • Migration from 8.1.7 to 10.1.0.3.0

    hi all, i have to migrate a db from oracle 8.1.7 to 10.1.0.3.0. my source platform is a windows 2000 (32 bit) and my destination platform is Linux Suse Enterprise server 9. During the migration i'd like to convert tablespace from extent dictionary ma

  • Adding redolog group for a database which has standby

    hi friends, Database: 10.2.0.3 OS: windows 2003 server sp2 i had a database (which has a standby) with the following redolog information SQL> select group#,member from v$logfile; GROUP# MEMBER 3 I:\D001\ORACLE\ORADATA\INFA05UT\REDO03.LOG 2 I:\D001\OR

  • Trouble Exporting Images from Lightroom 3

    I am having trouble exporting images from Lightroom 3 with my User Presets. Error Message: The file could not be written. (1). It has always worked in the past but I just bought a new Mac and had everything transfered to it. Everything else seems to

  • Cant compare collections

    hi, i cant solve one problem: SELECT be.Name, cardinality(be.Project) As project_count, cardinality(be.DoneProjects) As DoneProject_count FROM bureau be Order BY be.Name; Is it possible to compare project_count with done_project, for example: project

  • Droid Razr M new problems after latest update 182.46.15.en.us

    Ever since KitKat was pushed to my droid razr m, I have not been happy.  Very decreased battery life along with the phone getting and staying quite warm.  The loss of swype that was included when I bought it (yes, I know I COULD buy the app for cheap