Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Warnings in tterrors log

2662200Sep 5 2014 — edited Sep 5 2014

Hi,

I checked TimesTen tterrors.log and I found below warnings

20:12:01.97 Warn:    :   591: 17806/100162000: Recovery started

20:46:46.68 Warn:    :   591: 17806/100162000: Recovery started

21:35:03.97 Warn:    :   591: 17806/100162000: Recovery started

22:35:02.97 Warn:    :   591: 17806/100162000: Recovery started

03:27:54.08 Warn:    :   591: 17806/100162000: Recovery started

06:10:57.99 Warn:    :   591: 17806/100162000: Recovery started

11:29:51.99 Warn:    :   591: 17806/100162000: Recovery started

15:03:13.13 Warn:    :   591: 17806/100162000: Recovery started

17:57:04.19 Warn:    :   591: 17726 exited while connected to data store '/timesten/TimesTen/tt1122_64/info/TT_1122' shm 1845502254 count=1

17:57:04.22 Warn:    :   591: 17806/ffffffff788ca408: sbOLUndoByConn: oplog stack for connid 3 (java) pid 17726: <none>

18:53:08.23 Warn:    :   591: 17806/100162000: Recovery started

19:59:11.77 Warn:    :   591: 17806/100162000: Recovery started

21:35:23.91 Warn:    :   591: 17806/100162000: Recovery started

22:40:57.57 Warn:    :   591: 17806 ------------------: subdaemon process exited

01:14:55.73 Warn:    :   591: 26108/100162000: Recovery started

02:58:53.62 Warn:    :   591: 26108/100162000: Recovery started

04:23:54.79 Warn:    :   591: 26108/100162000: Recovery started

05:12:29.02 Warn:    :   591: 26108/100162000: Recovery started

05:12:41.45 Warn:    :   591: 5158 exited while connected to data store '/timesten/TimesTen/tt1122_64/info/TT_1122' shm 419438894 count=1

05:12:41.58 Warn:    :   591: 26108/ffffffff788ca408: sbOLUndoByConn: oplog stack for connid 1 (java) pid 5158: <none>

05:18:45.03 Warn:    :   591: 26108 ------------------: subdaemon process exited

07:19:17.19 Warn:    :   591: 23012 ------------------: subdaemon process exited

09:29:55.60 Warn:    :   591: 29548/100162000: Recovery started

10:10:24.70 Warn:    :   591: 29548/100162000: Recovery started

11:09:01.10 Warn:    :   591: 29548 ------------------: subdaemon process exited

11:53:14.37 Warn:    :   591: 1842/100162000: Recovery started

13:50:16.00 Warn:    :   591: 1842 ------------------: subdaemon process exited

18:10:24.66 Warn:    :   591: 5552/100162000: Recovery started

20:49:22.37 Warn:    :   591: 5552/100162000: Recovery started

21:55:18.07 Warn:    :   591: 5552/100162000: Recovery started

22:36:29.75 Warn:    :   591: 5552 ------------------: subdaemon process exited

22:36:30.09 Warn:    :   591: 8166/100162000: Recovery started

23:22:19.79 Warn:    :   591: 8166/100162000: Recovery started

03:54:28.70 Warn:    :   595: Invalidating the data store /timesten/TimesTen/tt1122_64/info/TT_1122 because it had 17 users

03:54:28.72 Warn:    :   595: WARNING: data store /timesten/TimesTen/tt1122_64/info/TT_1122 was in use at daemon termination.

03:54:28.72 Warn:    :   595: WARNING: data store no longer considered in use

03:54:28.72 Warn:    :   595: WARNING: PL/SQL shared segment existed at time of daemon termination

03:54:28.72 Err :    :   595: TT14000: TimesTen daemon internal error: Could not destroy PL/SQL shared memory, error 22

03:54:28.73 Warn:    :   595: TimesTen Daemon Release 11.2.2.5.0.tt1122_64 started.

03:55:03.12 Warn:    :   595: 598/100162000: Recovery started

05:34:59.75 Warn:    :   595: 598/100162000: Recovery started

06:53:34.24 Warn:    :   595: 598/100162000: Recovery started

07:19:40.82 Warn:    :   595:  598 ------------------: subdaemon process exited

08:26:51.00 Warn:    :   595:  600 ------------------: subdaemon process exited

09:23:34.95 Warn:    :   595: 19079 ------------------: subdaemon process exited

10:18:05.85 Warn:    :   595: 20145 ------------------: subdaemon process exited

11:24:52.73 Warn:    :   595: 21098 ------------------: subdaemon process exited

12:47:22.81 Warn:    :   595: 21972/1001727f0: Recovery started

13:26:35.51 Warn:    :   595: 21972/1001727f0: Recovery started

14:25:46.16 Warn:    :   595: 21972/1001727f0: Recovery started

20:53:16.41 Warn:    :   595: 21972/1001727f0: Recovery started

21:16:47.99 Warn:    :   595: 21972/1001727f0: Recovery started

22:10:55.94 Warn:    :   595: 21972/1001727f0: Recovery started

23:26:18.09 Warn:    :   595: 21972/1001727f0: Recovery started

16:29:06.41 Warn:    :   595: 26395 exited while connected to data store '/timesten/TimesTen/tt1122_64/info/TT_1122' shm 1593844014 count=1

16:29:06.51 Warn:    :   595: 21972/ffffffff795ca408: sbOLUndoByConn: oplog stack for connid 4 (java) pid 26395: <none>

06:01:48.90 Warn:    :   595: 9977 exited while connected to data store '/timesten/TimesTen/tt1122_64/info/TT_1122' shm 1593844014 count=1

06:01:49.02 Warn:    :   595: 21972/ffffffff795ca408: sbOLUndoByConn: oplog stack for connid 7 (tt_1122) pid 9977: <none>

07:08:30.01 Warn:    :   595: 21972/1001727f0: Recovery started

07:34:57.87 Warn:    :   595: 21972/1001727f0: Recovery started

11:06:36.25 Warn:    :   595: 21972/1001727f0: Recovery started

13:42:46.29 Warn:    :   595: 21972/1001727f0: Recovery started

14:56:38.35 Warn:    :   595: 21972/1001727f0: Recovery started

15:17:48.47 Warn:    :   595: 21972/1001727f0: Recovery started

16:11:23.97 Warn:    :   595: 21972/1001727f0: Recovery started

21:51:40.15 Warn:    :   595: 21972/1001727f0: Recovery started

22:25:50.42 Warn:    :   595: 21972/1001727f0: Recovery started

05:49:06.25 Warn:    :   595: 21972/1001727f0: Recovery started

10:40:36.52 Warn:    :   595: 21972/1001727f0: Recovery started

17:00:52.25 Warn:    :   595: 21972/1001727f0: Recovery started

18:57:29.47 Warn:    :   595: 21972/1001727f0: Recovery started

20:40:31.97 Warn:    :   595: 21972/1001727f0: Recovery started

22:53:38.32 Warn:    :   595: 21972/1001727f0: Recovery started

00:17:12.61 Warn:    :   595: 7626 exited while connected to data store '/timesten/TimesTen/tt1122_64/info/TT_1122' shm 738205998 count=1

00:17:12.78 Warn:    :   595: 21972/ffffffff795ca408: sbOLUndoByConn: oplog stack for connid 15 (java) pid 7626: <none>

02:17:53.00 Warn:    :   595: 21972/1001727f0: Recovery started

03:52:28.46 Warn:    :   595: 21972/1001727f0: Recovery started

04:15:32.80 Warn:    :   595: 21972 ------------------: subdaemon process exited

05:01:27.49 Warn:    :   595: 23074/100162000: Recovery started

06:16:50.30 Warn:    :   595: 23074 ------------------: subdaemon process exited

08:38:03.85 Warn:    :   595: 28857/100162000: Recovery started

09:24:09.40 Warn:    :   595: 28857/100162000: Recovery started

10:41:18.56 Warn:    :   595: 28857/100162000: Recovery started

11:03:23.74 Warn:    :   595: 28857 ------------------: subdaemon process exited

13:21:09.60 Warn:    :   595: 6388/100162000: Recovery started

14:30:55.68 Warn:    :   595: 6388/100162000: Recovery started

14:55:07.91 Warn:    :   595: 6388 ------------------: subdaemon process exited

19:31:01.10 Warn:    :   595: 1647/1001727f0: Recovery started

21:36:13.22 Warn:    :   595: 1647/1001727f0: Recovery started

22:35:17.48 Warn:    :   595: 1647 ------------------: subdaemon process exited

02:02:54.87 Warn:    :   595: 18092/100162000: Recovery started

02:39:50.55 Warn:    :   595: 18092/100162000: Recovery started

03:33:24.89 Warn:    :   595: 18092/100162000: Recovery started

05:00:33.86 Warn:    :   595: 18092/100162000: Recovery started

05:17:30.40 Warn:    :   595: 18092 ------------------: subdaemon process exited

06:45:15.71 Warn:    :   595: 10283/100162000: Recovery started

08:07:21.57 Warn:    :   595: 10283 ------------------: subdaemon process exited

08:52:04.87 Warn:    :   595: 25020/100162000: Recovery started

11:40:04.87 Warn:    :   595: 25020/100162000: Recovery started

14:14:43.03 Warn:    :   595: 25020 ------------------: subdaemon process exited

Guys, please advise me what those warnings mean ?

Thanks in advance.

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Oct 3 2014
Added on Sep 5 2014
1 comment
992 views