Mon Jan 01 02:00:00 2018 Clearing Resource Manager plan via parameter Mon Jan 01 09:00:06 2018 Thread 1 advanced to log sequence 8745 (LGWR switch) Current log# 3 seq# 8745 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Mon Jan 01 19:50:08 2018 Thread 1 advanced to log sequence 8746 (LGWR switch) Current log# 1 seq# 8746 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Mon Jan 01 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3003]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Mon Jan 01 22:00:00 2018 Starting background process VKRM Mon Jan 01 22:00:00 2018 VKRM started with pid=25, OS id=1289388 Mon Jan 01 22:00:01 2018 DM00 started with pid=33, OS id=1289536, job DEV.SYS_EXPORT_SCHEMA_01 Mon Jan 01 22:00:02 2018 DW00 started with pid=34, OS id=1289576, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Mon Jan 01 22:20:53 2018 Thread 1 advanced to log sequence 8747 (LGWR switch) Current log# 2 seq# 8747 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Jan 02 02:00:00 2018 Clearing Resource Manager plan via parameter Tue Jan 02 08:00:23 2018 Thread 1 advanced to log sequence 8748 (LGWR switch) Current log# 3 seq# 8748 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Tue Jan 02 16:17:11 2018 Thread 1 advanced to log sequence 8749 (LGWR switch) Current log# 1 seq# 8749 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Tue Jan 02 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3004]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Tue Jan 02 22:00:00 2018 Starting background process VKRM Tue Jan 02 22:00:00 2018 VKRM started with pid=27, OS id=1327324 Tue Jan 02 22:00:01 2018 DM00 started with pid=34, OS id=1327356, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 02 22:00:02 2018 DW00 started with pid=35, OS id=1327664, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 02 22:00:27 2018 Thread 1 cannot allocate new log, sequence 8750 Private strand flush not complete Current log# 1 seq# 8749 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8750 (LGWR switch) Current log# 2 seq# 8750 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Jan 02 22:21:31 2018 Thread 1 advanced to log sequence 8751 (LGWR switch) Current log# 3 seq# 8751 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Jan 03 02:00:00 2018 Clearing Resource Manager plan via parameter Wed Jan 03 08:30:43 2018 Thread 1 advanced to log sequence 8752 (LGWR switch) Current log# 1 seq# 8752 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Wed Jan 03 16:00:34 2018 Thread 1 advanced to log sequence 8753 (LGWR switch) Current log# 2 seq# 8753 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Wed Jan 03 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3005]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Wed Jan 03 22:00:00 2018 Starting background process VKRM Wed Jan 03 22:00:00 2018 VKRM started with pid=19, OS id=1370892 Wed Jan 03 22:00:01 2018 DM00 started with pid=34, OS id=1373068, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 03 22:00:02 2018 DW00 started with pid=35, OS id=1372560, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 03 22:00:26 2018 Thread 1 cannot allocate new log, sequence 8754 Private strand flush not complete Current log# 2 seq# 8753 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thread 1 advanced to log sequence 8754 (LGWR switch) Current log# 3 seq# 8754 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Jan 03 22:22:09 2018 Thread 1 advanced to log sequence 8755 (LGWR switch) Current log# 1 seq# 8755 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thu Jan 04 02:00:00 2018 Clearing Resource Manager plan via parameter Thu Jan 04 08:36:53 2018 Thread 1 advanced to log sequence 8756 (LGWR switch) Current log# 2 seq# 8756 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Jan 04 16:04:03 2018 Thread 1 advanced to log sequence 8757 (LGWR switch) Current log# 3 seq# 8757 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thu Jan 04 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3006]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Thu Jan 04 22:00:00 2018 Starting background process VKRM Thu Jan 04 22:00:00 2018 VKRM started with pid=25, OS id=1417724 Thu Jan 04 22:00:01 2018 DM00 started with pid=28, OS id=1416644, job DEV.SYS_EXPORT_SCHEMA_01 Thu Jan 04 22:00:02 2018 DW00 started with pid=34, OS id=1415224, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Thu Jan 04 22:00:27 2018 Thread 1 cannot allocate new log, sequence 8758 Private strand flush not complete Current log# 3 seq# 8757 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thread 1 advanced to log sequence 8758 (LGWR switch) Current log# 1 seq# 8758 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thu Jan 04 22:22:50 2018 Thread 1 advanced to log sequence 8759 (LGWR switch) Current log# 2 seq# 8759 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Fri Jan 05 02:00:00 2018 Clearing Resource Manager plan via parameter Fri Jan 05 08:44:01 2018 Thread 1 advanced to log sequence 8760 (LGWR switch) Current log# 3 seq# 8760 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Fri Jan 05 16:03:32 2018 Thread 1 advanced to log sequence 8761 (LGWR switch) Current log# 1 seq# 8761 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Fri Jan 05 21:00:29 2018 Thread 1 advanced to log sequence 8762 (LGWR switch) Current log# 2 seq# 8762 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Fri Jan 05 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3007]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Fri Jan 05 22:00:00 2018 Starting background process VKRM Fri Jan 05 22:00:00 2018 VKRM started with pid=26, OS id=1464100 Fri Jan 05 22:00:01 2018 DM00 started with pid=29, OS id=1463316, job DEV.SYS_EXPORT_SCHEMA_01 Fri Jan 05 22:00:02 2018 DW00 started with pid=36, OS id=1461320, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Fri Jan 05 22:23:23 2018 Thread 1 advanced to log sequence 8763 (LGWR switch) Current log# 3 seq# 8763 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Sat Jan 06 02:00:00 2018 Clearing Resource Manager plan via parameter Sat Jan 06 06:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3008]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Sat Jan 06 06:00:00 2018 Starting background process VKRM Sat Jan 06 06:00:00 2018 VKRM started with pid=26, OS id=1478412 Sat Jan 06 06:00:15 2018 Thread 1 cannot allocate new log, sequence 8764 Private strand flush not complete Current log# 3 seq# 8763 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thread 1 advanced to log sequence 8764 (LGWR switch) Current log# 1 seq# 8764 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Sat Jan 06 13:26:30 2018 Thread 1 advanced to log sequence 8765 (LGWR switch) Current log# 2 seq# 8765 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Sat Jan 06 21:14:16 2018 Thread 1 advanced to log sequence 8766 (LGWR switch) Current log# 3 seq# 8766 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Sat Jan 06 22:00:01 2018 DM00 started with pid=28, OS id=1509120, job DEV.SYS_EXPORT_SCHEMA_01 Sat Jan 06 22:00:02 2018 DW00 started with pid=29, OS id=1509168, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Sat Jan 06 22:24:03 2018 Thread 1 advanced to log sequence 8767 (LGWR switch) Current log# 1 seq# 8767 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Sun Jan 07 02:00:00 2018 Clearing Resource Manager plan via parameter Sun Jan 07 06:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3009]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Sun Jan 07 06:00:00 2018 Starting background process VKRM Sun Jan 07 06:00:00 2018 VKRM started with pid=24, OS id=1523284 Sun Jan 07 06:00:18 2018 Thread 1 cannot allocate new log, sequence 8768 Private strand flush not complete Current log# 1 seq# 8767 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8768 (LGWR switch) Current log# 2 seq# 8768 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Sun Jan 07 14:10:18 2018 Thread 1 advanced to log sequence 8769 (LGWR switch) Current log# 3 seq# 8769 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Sun Jan 07 22:00:01 2018 DM00 started with pid=30, OS id=1553500, job DEV.SYS_EXPORT_SCHEMA_01 Sun Jan 07 22:00:02 2018 DW00 started with pid=32, OS id=1554276, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Sun Jan 07 22:00:41 2018 Thread 1 cannot allocate new log, sequence 8770 Private strand flush not complete Current log# 3 seq# 8769 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thread 1 advanced to log sequence 8770 (LGWR switch) Current log# 1 seq# 8770 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Sun Jan 07 22:24:52 2018 Thread 1 advanced to log sequence 8771 (LGWR switch) Current log# 2 seq# 8771 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Mon Jan 08 02:00:00 2018 Clearing Resource Manager plan via parameter Mon Jan 08 08:40:53 2018 Thread 1 advanced to log sequence 8772 (LGWR switch) Current log# 3 seq# 8772 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Mon Jan 08 16:00:50 2018 Thread 1 advanced to log sequence 8773 (LGWR switch) Current log# 1 seq# 8773 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Mon Jan 08 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3003]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Mon Jan 08 22:00:00 2018 Starting background process VKRM Mon Jan 08 22:00:00 2018 VKRM started with pid=25, OS id=1598376 Mon Jan 08 22:00:01 2018 DM00 started with pid=28, OS id=1599204, job DEV.SYS_EXPORT_SCHEMA_01 Mon Jan 08 22:00:03 2018 DW00 started with pid=36, OS id=1599112, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Mon Jan 08 22:00:23 2018 Thread 1 cannot allocate new log, sequence 8774 Private strand flush not complete Current log# 1 seq# 8773 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8774 (LGWR switch) Current log# 2 seq# 8774 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Mon Jan 08 22:41:47 2018 Thread 1 advanced to log sequence 8775 (LGWR switch) Current log# 3 seq# 8775 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Tue Jan 09 02:00:00 2018 Clearing Resource Manager plan via parameter Tue Jan 09 09:00:40 2018 Thread 1 advanced to log sequence 8776 (LGWR switch) Current log# 1 seq# 8776 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Tue Jan 09 16:58:09 2018 Thread 1 advanced to log sequence 8777 (LGWR switch) Current log# 2 seq# 8777 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Jan 09 19:26:02 2018 Thread 1 advanced to log sequence 8778 (LGWR switch) Current log# 3 seq# 8778 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Tue Jan 09 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3004]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Tue Jan 09 22:00:00 2018 Starting background process VKRM Tue Jan 09 22:00:00 2018 VKRM started with pid=25, OS id=1624916 Tue Jan 09 22:00:01 2018 DM00 started with pid=30, OS id=1622272, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 09 22:00:02 2018 DW00 started with pid=35, OS id=1605272, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 09 22:04:10 2018 Thread 1 cannot allocate new log, sequence 8779 Private strand flush not complete Current log# 3 seq# 8778 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thread 1 advanced to log sequence 8779 (LGWR switch) Current log# 1 seq# 8779 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Wed Jan 10 02:00:00 2018 Clearing Resource Manager plan via parameter Wed Jan 10 08:20:42 2018 Thread 1 advanced to log sequence 8780 (LGWR switch) Current log# 2 seq# 8780 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Wed Jan 10 16:42:46 2018 Thread 1 advanced to log sequence 8781 (LGWR switch) Current log# 3 seq# 8781 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Jan 10 19:26:41 2018 Thread 1 advanced to log sequence 8782 (LGWR switch) Current log# 1 seq# 8782 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Wed Jan 10 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3005]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Wed Jan 10 22:00:00 2018 Starting background process VKRM Wed Jan 10 22:00:00 2018 VKRM started with pid=24, OS id=1630892 Wed Jan 10 22:00:01 2018 DM00 started with pid=27, OS id=1629528, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 10 22:00:02 2018 DW00 started with pid=36, OS id=1631096, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 10 22:34:05 2018 Thread 1 advanced to log sequence 8783 (LGWR switch) Current log# 2 seq# 8783 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Jan 11 02:00:00 2018 Clearing Resource Manager plan via parameter Thu Jan 11 09:00:09 2018 Thread 1 advanced to log sequence 8784 (LGWR switch) Current log# 3 seq# 8784 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thu Jan 11 15:50:26 2018 Thread 1 advanced to log sequence 8785 (LGWR switch) Current log# 1 seq# 8785 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thu Jan 11 19:27:39 2018 Thread 1 advanced to log sequence 8786 (LGWR switch) Current log# 2 seq# 8786 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Jan 11 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3006]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Thu Jan 11 22:00:00 2018 Starting background process VKRM Thu Jan 11 22:00:00 2018 VKRM started with pid=25, OS id=1674920 Thu Jan 11 22:00:01 2018 DM00 started with pid=30, OS id=1658156, job DEV.SYS_EXPORT_SCHEMA_01 Thu Jan 11 22:00:04 2018 DW00 started with pid=35, OS id=1675284, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Thu Jan 11 22:28:43 2018 Thread 1 advanced to log sequence 8787 (LGWR switch) Current log# 3 seq# 8787 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Fri Jan 12 02:00:00 2018 Clearing Resource Manager plan via parameter Fri Jan 12 08:52:55 2018 Thread 1 advanced to log sequence 8788 (LGWR switch) Current log# 1 seq# 8788 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Fri Jan 12 17:33:50 2018 Thread 1 advanced to log sequence 8789 (LGWR switch) Current log# 2 seq# 8789 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Fri Jan 12 19:28:41 2018 Thread 1 advanced to log sequence 8790 (LGWR switch) Current log# 3 seq# 8790 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Fri Jan 12 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3007]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Fri Jan 12 22:00:00 2018 Starting background process VKRM Fri Jan 12 22:00:00 2018 VKRM started with pid=19, OS id=1712084 Fri Jan 12 22:00:01 2018 DM00 started with pid=26, OS id=1706208, job DEV.SYS_EXPORT_SCHEMA_01 Fri Jan 12 22:00:04 2018 DW00 started with pid=37, OS id=1711420, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Fri Jan 12 22:04:47 2018 Thread 1 cannot allocate new log, sequence 8791 Private strand flush not complete Current log# 3 seq# 8790 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thread 1 advanced to log sequence 8791 (LGWR switch) Current log# 1 seq# 8791 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Sat Jan 13 02:00:00 2018 Clearing Resource Manager plan via parameter Sat Jan 13 06:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3008]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Sat Jan 13 06:00:00 2018 Starting background process VKRM Sat Jan 13 06:00:00 2018 VKRM started with pid=23, OS id=1724668 Sat Jan 13 06:00:28 2018 Thread 1 advanced to log sequence 8792 (LGWR switch) Current log# 2 seq# 8792 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Sat Jan 13 14:10:10 2018 Thread 1 cannot allocate new log, sequence 8793 Private strand flush not complete Current log# 2 seq# 8792 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thread 1 advanced to log sequence 8793 (LGWR switch) Current log# 3 seq# 8793 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Sat Jan 13 19:29:36 2018 Thread 1 advanced to log sequence 8794 (LGWR switch) Current log# 1 seq# 8794 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Sat Jan 13 22:00:01 2018 DM00 started with pid=28, OS id=1756256, job DEV.SYS_EXPORT_SCHEMA_01 Sat Jan 13 22:00:02 2018 DW00 started with pid=30, OS id=1756324, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Sat Jan 13 23:23:37 2018 Thread 1 advanced to log sequence 8795 (LGWR switch) Current log# 2 seq# 8795 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Sun Jan 14 02:00:00 2018 Clearing Resource Manager plan via parameter Tue Jan 16 08:34:07 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Tue Jan 16 08:34:13 2018 PMON started with pid=2, OS id=3444 Tue Jan 16 08:34:13 2018 VKTM started with pid=3, OS id=3448 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Tue Jan 16 08:34:13 2018 GEN0 started with pid=4, OS id=3452 Tue Jan 16 08:34:13 2018 DIAG started with pid=5, OS id=3456 Tue Jan 16 08:34:13 2018 DBRM started with pid=6, OS id=3460 Tue Jan 16 08:34:13 2018 PSP0 started with pid=7, OS id=3464 Tue Jan 16 08:34:13 2018 DIA0 started with pid=8, OS id=3468 Tue Jan 16 08:34:13 2018 MMAN started with pid=9, OS id=3472 Tue Jan 16 08:34:13 2018 DBW0 started with pid=10, OS id=3476 Tue Jan 16 08:34:13 2018 LGWR started with pid=11, OS id=3480 Tue Jan 16 08:34:13 2018 CKPT started with pid=12, OS id=3484 Tue Jan 16 08:34:13 2018 SMON started with pid=13, OS id=3488 Tue Jan 16 08:34:13 2018 RECO started with pid=14, OS id=3492 Tue Jan 16 08:34:13 2018 MMON started with pid=15, OS id=3496 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Tue Jan 16 08:34:13 2018 MMNL started with pid=16, OS id=3500 Tue Jan 16 08:34:15 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2482792583 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1120 KB redo, 85 data blocks need recovery Started redo application at Thread 1: logseq 8795, block 27507 Recovery of Online Redo Log: Thread 1 Group 2 Seq 8795 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Completed redo application of 0.30MB Completed crash recovery at Thread 1: logseq 8795, block 29747, scn 237898511 85 data blocks read, 85 data blocks written, 1120 redo k-bytes read Tue Jan 16 08:34:23 2018 Thread 1 advanced to log sequence 8796 (thread open) Thread 1 opened at log sequence 8796 Current log# 3 seq# 8796 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Successful open of redo thread 1 Tue Jan 16 08:34:23 2018 SMON: enabling cache recovery Tue Jan 16 08:34:25 2018 Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Tue Jan 16 08:34:29 2018 QMNC started with pid=20, OS id=4012 Completed: alter database open Tue Jan 16 08:34:35 2018 Starting background process CJQ0 Tue Jan 16 08:34:35 2018 CJQ0 started with pid=19, OS id=3568 Tue Jan 16 08:34:36 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Tue Jan 16 08:39:35 2018 Starting background process SMCO Tue Jan 16 08:39:35 2018 SMCO started with pid=25, OS id=3248 Tue Jan 16 09:02:27 2018 Thread 1 advanced to log sequence 8797 (LGWR switch) Current log# 1 seq# 8797 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8798 (LGWR switch) Current log# 2 seq# 8798 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Jan 16 16:28:34 2018 Thread 1 advanced to log sequence 8799 (LGWR switch) Current log# 3 seq# 8799 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Tue Jan 16 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3004]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Tue Jan 16 22:00:00 2018 Starting background process VKRM Tue Jan 16 22:00:00 2018 VKRM started with pid=27, OS id=4948 Tue Jan 16 22:00:04 2018 DM00 started with pid=36, OS id=5148, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 16 22:00:07 2018 DW00 started with pid=37, OS id=5164, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 16 22:00:34 2018 Thread 1 cannot allocate new log, sequence 8800 Private strand flush not complete Current log# 3 seq# 8799 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thread 1 advanced to log sequence 8800 (LGWR switch) Current log# 1 seq# 8800 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Wed Jan 17 02:00:00 2018 Clearing Resource Manager plan via parameter Wed Jan 17 06:54:06 2018 Thread 1 advanced to log sequence 8801 (LGWR switch) Current log# 2 seq# 8801 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Wed Jan 17 14:38:49 2018 Thread 1 advanced to log sequence 8802 (LGWR switch) Current log# 3 seq# 8802 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Jan 17 19:03:11 2018 Thread 1 advanced to log sequence 8803 (LGWR switch) Current log# 1 seq# 8803 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Wed Jan 17 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3005]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Wed Jan 17 22:00:00 2018 Starting background process VKRM Wed Jan 17 22:00:00 2018 VKRM started with pid=27, OS id=15384 Wed Jan 17 22:00:00 2018 DM00 started with pid=31, OS id=15604, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 17 22:00:02 2018 DW00 started with pid=32, OS id=15052, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 17 22:00:29 2018 Thread 1 cannot allocate new log, sequence 8804 Private strand flush not complete Current log# 1 seq# 8803 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8804 (LGWR switch) Current log# 2 seq# 8804 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Jan 18 02:00:00 2018 Clearing Resource Manager plan via parameter Thu Jan 18 05:50:19 2018 Thread 1 advanced to log sequence 8805 (LGWR switch) Current log# 3 seq# 8805 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thu Jan 18 13:56:12 2018 Thread 1 advanced to log sequence 8806 (LGWR switch) Current log# 1 seq# 8806 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thu Jan 18 19:03:43 2018 Thread 1 advanced to log sequence 8807 (LGWR switch) Current log# 2 seq# 8807 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Jan 18 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3006]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Thu Jan 18 22:00:00 2018 Starting background process VKRM Thu Jan 18 22:00:00 2018 VKRM started with pid=22, OS id=61860 Thu Jan 18 22:00:01 2018 DM00 started with pid=27, OS id=61592, job DEV.SYS_EXPORT_SCHEMA_01 Thu Jan 18 22:00:02 2018 DW00 started with pid=36, OS id=61456, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Thu Jan 18 22:04:00 2018 Thread 1 cannot allocate new log, sequence 8808 Private strand flush not complete Current log# 2 seq# 8807 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thread 1 advanced to log sequence 8808 (LGWR switch) Current log# 3 seq# 8808 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Fri Jan 19 02:00:00 2018 Clearing Resource Manager plan via parameter Fri Jan 19 08:00:18 2018 Thread 1 advanced to log sequence 8809 (LGWR switch) Current log# 1 seq# 8809 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Fri Jan 19 16:20:56 2018 Thread 1 advanced to log sequence 8810 (LGWR switch) Current log# 2 seq# 8810 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Fri Jan 19 19:04:17 2018 Thread 1 advanced to log sequence 8811 (LGWR switch) Current log# 3 seq# 8811 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Fri Jan 19 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3007]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Fri Jan 19 22:00:00 2018 Starting background process VKRM Fri Jan 19 22:00:00 2018 VKRM started with pid=29, OS id=108788 Fri Jan 19 22:00:00 2018 DM00 started with pid=24, OS id=109252, job DEV.SYS_EXPORT_SCHEMA_01 Fri Jan 19 22:00:01 2018 DW00 started with pid=26, OS id=108936, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Fri Jan 19 22:04:11 2018 Thread 1 cannot allocate new log, sequence 8812 Private strand flush not complete Current log# 3 seq# 8811 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thread 1 advanced to log sequence 8812 (LGWR switch) Current log# 1 seq# 8812 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Sat Jan 20 02:00:00 2018 Clearing Resource Manager plan via parameter Mon Jan 22 08:23:45 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Mon Jan 22 08:23:52 2018 PMON started with pid=2, OS id=3432 Mon Jan 22 08:23:52 2018 VKTM started with pid=3, OS id=3436 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Mon Jan 22 08:23:52 2018 GEN0 started with pid=4, OS id=3440 Mon Jan 22 08:23:52 2018 DIAG started with pid=5, OS id=3444 Mon Jan 22 08:23:52 2018 DBRM started with pid=6, OS id=3448 Mon Jan 22 08:23:52 2018 PSP0 started with pid=7, OS id=3452 Mon Jan 22 08:23:52 2018 DIA0 started with pid=8, OS id=3456 Mon Jan 22 08:23:52 2018 MMAN started with pid=9, OS id=3460 Mon Jan 22 08:23:52 2018 DBW0 started with pid=10, OS id=3464 Mon Jan 22 08:23:52 2018 LGWR started with pid=11, OS id=3468 Mon Jan 22 08:23:52 2018 CKPT started with pid=12, OS id=3472 Mon Jan 22 08:23:52 2018 SMON started with pid=13, OS id=3476 Mon Jan 22 08:23:52 2018 RECO started with pid=14, OS id=3480 Mon Jan 22 08:23:52 2018 MMON started with pid=15, OS id=3484 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Mon Jan 22 08:23:52 2018 MMNL started with pid=16, OS id=3488 Mon Jan 22 08:23:53 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2483326490 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1113 KB redo, 98 data blocks need recovery Started redo application at Thread 1: logseq 8812, block 29500 Recovery of Online Redo Log: Thread 1 Group 1 Seq 8812 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Completed redo application of 0.41MB Completed crash recovery at Thread 1: logseq 8812, block 31726, scn 238346978 98 data blocks read, 98 data blocks written, 1113 redo k-bytes read Thread 1 advanced to log sequence 8813 (thread open) Thread 1 opened at log sequence 8813 Current log# 2 seq# 8813 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Successful open of redo thread 1 SMON: enabling cache recovery Mon Jan 22 08:24:04 2018 Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Mon Jan 22 08:24:04 2018 SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Mon Jan 22 08:24:08 2018 QMNC started with pid=20, OS id=3284 Completed: alter database open Mon Jan 22 08:24:14 2018 Starting background process CJQ0 Mon Jan 22 08:24:14 2018 CJQ0 started with pid=22, OS id=4008 Mon Jan 22 08:24:14 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Mon Jan 22 08:30:07 2018 Starting background process SMCO Mon Jan 22 08:30:07 2018 SMCO started with pid=26, OS id=4804 Mon Jan 22 08:52:13 2018 Thread 1 advanced to log sequence 8814 (LGWR switch) Current log# 3 seq# 8814 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Mon Jan 22 12:46:14 2018 Thread 1 advanced to log sequence 8815 (LGWR switch) Current log# 1 seq# 8815 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Mon Jan 22 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3003]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Mon Jan 22 22:00:00 2018 Starting background process VKRM Mon Jan 22 22:00:00 2018 VKRM started with pid=29, OS id=5248 Mon Jan 22 22:00:05 2018 DM00 started with pid=36, OS id=5712, job DEV.SYS_EXPORT_SCHEMA_01 Mon Jan 22 22:00:07 2018 Thread 1 cannot allocate new log, sequence 8816 Private strand flush not complete Current log# 1 seq# 8815 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Mon Jan 22 22:00:08 2018 DW00 started with pid=37, OS id=5072, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Thread 1 advanced to log sequence 8816 (LGWR switch) Current log# 2 seq# 8816 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Jan 23 01:24:57 2018 Thread 1 advanced to log sequence 8817 (LGWR switch) Current log# 3 seq# 8817 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Tue Jan 23 02:00:00 2018 Clearing Resource Manager plan via parameter Tue Jan 23 10:56:39 2018 Thread 1 advanced to log sequence 8818 (LGWR switch) Current log# 1 seq# 8818 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Tue Jan 23 19:21:01 2018 Thread 1 advanced to log sequence 8819 (LGWR switch) Current log# 2 seq# 8819 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Jan 23 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3004]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Tue Jan 23 22:00:00 2018 Starting background process VKRM Tue Jan 23 22:00:00 2018 VKRM started with pid=23, OS id=2500 Tue Jan 23 22:00:00 2018 DM00 started with pid=31, OS id=4776, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 23 22:00:02 2018 DW00 started with pid=32, OS id=5744, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 23 22:22:58 2018 Thread 1 advanced to log sequence 8820 (LGWR switch) Current log# 3 seq# 8820 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Jan 24 02:00:00 2018 Clearing Resource Manager plan via parameter Wed Jan 24 04:32:57 2018 Thread 1 advanced to log sequence 8821 (LGWR switch) Current log# 1 seq# 8821 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Wed Jan 24 13:00:44 2018 Thread 1 advanced to log sequence 8822 (LGWR switch) Current log# 2 seq# 8822 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Wed Jan 24 21:00:34 2018 Thread 1 advanced to log sequence 8823 (LGWR switch) Current log# 3 seq# 8823 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Jan 24 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3005]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Wed Jan 24 22:00:00 2018 Starting background process VKRM Wed Jan 24 22:00:00 2018 VKRM started with pid=25, OS id=12360 Wed Jan 24 22:00:01 2018 DM00 started with pid=29, OS id=12528, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 24 22:00:02 2018 DW00 started with pid=33, OS id=13060, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 24 22:23:33 2018 Thread 1 advanced to log sequence 8824 (LGWR switch) Current log# 1 seq# 8824 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thu Jan 25 00:57:34 2018 Thread 1 advanced to log sequence 8825 (LGWR switch) Current log# 2 seq# 8825 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Jan 25 02:00:00 2018 Clearing Resource Manager plan via parameter Thu Jan 25 10:43:04 2018 Thread 1 advanced to log sequence 8826 (LGWR switch) Current log# 3 seq# 8826 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thu Jan 25 15:36:43 2018 Thread 1 advanced to log sequence 8827 (LGWR switch) Current log# 1 seq# 8827 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thu Jan 25 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3006]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Thu Jan 25 22:00:00 2018 Starting background process VKRM Thu Jan 25 22:00:00 2018 VKRM started with pid=25, OS id=59280 Thu Jan 25 22:00:00 2018 DM00 started with pid=29, OS id=58704, job DEV.SYS_EXPORT_SCHEMA_01 Thu Jan 25 22:00:01 2018 DW00 started with pid=30, OS id=57032, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Thu Jan 25 22:00:20 2018 Thread 1 cannot allocate new log, sequence 8828 Private strand flush not complete Current log# 1 seq# 8827 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8828 (LGWR switch) Current log# 2 seq# 8828 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Jan 25 22:24:13 2018 Thread 1 advanced to log sequence 8829 (LGWR switch) Current log# 3 seq# 8829 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Fri Jan 26 02:00:00 2018 Clearing Resource Manager plan via parameter Fri Jan 26 08:24:17 2018 Thread 1 advanced to log sequence 8830 (LGWR switch) Current log# 1 seq# 8830 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Fri Jan 26 15:53:03 2018 Thread 1 advanced to log sequence 8831 (LGWR switch) Current log# 2 seq# 8831 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Fri Jan 26 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3007]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Fri Jan 26 22:00:00 2018 Starting background process VKRM Fri Jan 26 22:00:00 2018 VKRM started with pid=27, OS id=106988 Fri Jan 26 22:00:00 2018 DM00 started with pid=33, OS id=107024, job DEV.SYS_EXPORT_SCHEMA_01 Fri Jan 26 22:00:02 2018 DW00 started with pid=35, OS id=106512, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Fri Jan 26 22:00:34 2018 Thread 1 cannot allocate new log, sequence 8832 Private strand flush not complete Current log# 2 seq# 8831 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thread 1 advanced to log sequence 8832 (LGWR switch) Current log# 3 seq# 8832 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Fri Jan 26 22:24:48 2018 Thread 1 advanced to log sequence 8833 (LGWR switch) Current log# 1 seq# 8833 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Sat Jan 27 02:00:00 2018 Clearing Resource Manager plan via parameter Sat Jan 27 06:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3008]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Sat Jan 27 06:00:00 2018 Starting background process VKRM Sat Jan 27 06:00:00 2018 VKRM started with pid=28, OS id=121280 Sat Jan 27 06:00:19 2018 Thread 1 cannot allocate new log, sequence 8834 Private strand flush not complete Current log# 1 seq# 8833 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8834 (LGWR switch) Current log# 2 seq# 8834 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Mon Jan 29 08:16:09 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Mon Jan 29 08:16:15 2018 PMON started with pid=2, OS id=3468 Mon Jan 29 08:16:15 2018 VKTM started with pid=3, OS id=3472 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Mon Jan 29 08:16:15 2018 GEN0 started with pid=4, OS id=3476 Mon Jan 29 08:16:15 2018 DIAG started with pid=5, OS id=3480 Mon Jan 29 08:16:15 2018 DBRM started with pid=6, OS id=3484 Mon Jan 29 08:16:15 2018 PSP0 started with pid=7, OS id=3488 Mon Jan 29 08:16:15 2018 DIA0 started with pid=8, OS id=3492 Mon Jan 29 08:16:15 2018 MMAN started with pid=9, OS id=3496 Mon Jan 29 08:16:15 2018 DBW0 started with pid=10, OS id=3500 Mon Jan 29 08:16:15 2018 LGWR started with pid=11, OS id=3504 Mon Jan 29 08:16:15 2018 CKPT started with pid=12, OS id=3508 Mon Jan 29 08:16:15 2018 SMON started with pid=13, OS id=3512 Mon Jan 29 08:16:15 2018 RECO started with pid=14, OS id=3516 Mon Jan 29 08:16:15 2018 MMON started with pid=15, OS id=3520 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Mon Jan 29 08:16:15 2018 MMNL started with pid=16, OS id=3524 Mon Jan 29 08:16:17 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2483873489 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1147 KB redo, 82 data blocks need recovery Started redo application at Thread 1: logseq 8834, block 1055 Recovery of Online Redo Log: Thread 1 Group 2 Seq 8834 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Completed redo application of 0.20MB Completed crash recovery at Thread 1: logseq 8834, block 3349, scn 238923579 82 data blocks read, 82 data blocks written, 1147 redo k-bytes read Thread 1 advanced to log sequence 8835 (thread open) Thread 1 opened at log sequence 8835 Current log# 3 seq# 8835 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Successful open of redo thread 1 SMON: enabling cache recovery Mon Jan 29 08:16:28 2018 Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Mon Jan 29 08:16:28 2018 SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Mon Jan 29 08:16:31 2018 QMNC started with pid=20, OS id=4076 Completed: alter database open Mon Jan 29 08:16:36 2018 Starting background process CJQ0 Mon Jan 29 08:16:36 2018 CJQ0 started with pid=25, OS id=3900 Mon Jan 29 08:16:37 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Mon Jan 29 08:18:46 2018 AUD: OS Error = 1717 encountered while writing audit record opidcl aborting process unknown ospid (4124) as a result of ORA-28056 Mon Jan 29 08:18:46 2018 AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record Mon Jan 29 08:18:46 2018 AUD: OS Error = 1717 encountered while writing audit record opidcl aborting process unknown ospid (3280) as a result of ORA-28056 Mon Jan 29 08:24:06 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Mon Jan 29 08:24:10 2018 PMON started with pid=2, OS id=3896 Mon Jan 29 08:24:10 2018 PSP0 started with pid=7, OS id=3916 Mon Jan 29 08:24:10 2018 DIAG started with pid=5, OS id=3908 Mon Jan 29 08:24:10 2018 DIA0 started with pid=8, OS id=3920 Mon Jan 29 08:24:10 2018 GEN0 started with pid=4, OS id=3904 Mon Jan 29 08:24:10 2018 DBRM started with pid=6, OS id=3912 Mon Jan 29 08:24:10 2018 MMAN started with pid=9, OS id=3924 Mon Jan 29 08:24:11 2018 DBW0 started with pid=10, OS id=3956 Mon Jan 29 08:24:11 2018 LGWR started with pid=11, OS id=3960 Mon Jan 29 08:24:11 2018 CKPT started with pid=12, OS id=3964 Mon Jan 29 08:24:11 2018 SMON started with pid=13, OS id=3968 Mon Jan 29 08:24:11 2018 RECO started with pid=14, OS id=3972 Mon Jan 29 08:24:11 2018 MMON started with pid=15, OS id=3976 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Mon Jan 29 08:24:11 2018 MMNL started with pid=16, OS id=3980 starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Mon Jan 29 08:24:10 2018 VKTM started with pid=3, OS id=3900 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Mon Jan 29 08:24:12 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2483907500 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 827 KB redo, 300 data blocks need recovery Started redo application at Thread 1: logseq 8835, block 3 Recovery of Online Redo Log: Thread 1 Group 3 Seq 8835 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Completed redo application of 0.62MB Completed crash recovery at Thread 1: logseq 8835, block 1658, scn 238944396 300 data blocks read, 300 data blocks written, 827 redo k-bytes read Thread 1 advanced to log sequence 8836 (thread open) Thread 1 opened at log sequence 8836 Current log# 1 seq# 8836 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Successful open of redo thread 1 SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Mon Jan 29 08:24:22 2018 SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active Mon Jan 29 08:24:23 2018 replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Mon Jan 29 08:24:24 2018 QMNC started with pid=20, OS id=3192 Completed: alter database open Mon Jan 29 08:24:29 2018 Starting background process CJQ0 Mon Jan 29 08:24:29 2018 CJQ0 started with pid=21, OS id=3860 Mon Jan 29 08:24:29 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Mon Jan 29 08:29:49 2018 Starting background process SMCO Mon Jan 29 08:29:49 2018 SMCO started with pid=27, OS id=3876 Mon Jan 29 08:52:41 2018 Thread 1 advanced to log sequence 8837 (LGWR switch) Current log# 2 seq# 8837 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Mon Jan 29 16:27:40 2018 Thread 1 advanced to log sequence 8838 (LGWR switch) Current log# 3 seq# 8838 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Mon Jan 29 17:12:57 2018 AUD: OS Error = 1717 encountered while writing audit record opidcl aborting process unknown ospid (5404) as a result of ORA-28056 Mon Jan 29 17:12:57 2018 AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record Mon Jan 29 17:13:00 2018 AUD: OS Error = 1717 encountered while writing audit record Mon Jan 29 17:17:23 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Mon Jan 29 17:17:27 2018 PMON started with pid=2, OS id=3932 Mon Jan 29 17:17:27 2018 VKTM started with pid=3, OS id=3936 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Mon Jan 29 17:17:27 2018 GEN0 started with pid=4, OS id=3940 Mon Jan 29 17:17:27 2018 DIAG started with pid=5, OS id=3944 Mon Jan 29 17:17:27 2018 DBRM started with pid=6, OS id=3948 Mon Jan 29 17:17:27 2018 PSP0 started with pid=7, OS id=3952 Mon Jan 29 17:17:27 2018 DIA0 started with pid=8, OS id=3956 Mon Jan 29 17:17:27 2018 MMAN started with pid=9, OS id=3960 Mon Jan 29 17:17:27 2018 DBW0 started with pid=10, OS id=3964 Mon Jan 29 17:17:27 2018 LGWR started with pid=11, OS id=3968 Mon Jan 29 17:17:27 2018 CKPT started with pid=12, OS id=3972 Mon Jan 29 17:17:27 2018 SMON started with pid=13, OS id=3976 Mon Jan 29 17:17:27 2018 RECO started with pid=14, OS id=3980 Mon Jan 29 17:17:27 2018 MMON started with pid=15, OS id=3984 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Mon Jan 29 17:17:27 2018 MMNL started with pid=16, OS id=3988 starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Mon Jan 29 17:17:28 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2483889832 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1750 KB redo, 337 data blocks need recovery Started redo application at Thread 1: logseq 8838, block 1771 Recovery of Online Redo Log: Thread 1 Group 3 Seq 8838 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Completed redo application of 0.74MB Completed crash recovery at Thread 1: logseq 8838, block 5271, scn 239003863 337 data blocks read, 337 data blocks written, 1750 redo k-bytes read Thread 1 advanced to log sequence 8839 (thread open) Thread 1 opened at log sequence 8839 Current log# 1 seq# 8839 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Successful open of redo thread 1 SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Mon Jan 29 17:17:39 2018 Starting background process QMNC Mon Jan 29 17:17:39 2018 QMNC started with pid=20, OS id=3516 Completed: alter database open Mon Jan 29 17:17:43 2018 Starting background process CJQ0 Mon Jan 29 17:17:43 2018 CJQ0 started with pid=22, OS id=3912 Mon Jan 29 17:17:43 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Mon Jan 29 17:22:39 2018 Starting background process SMCO Mon Jan 29 17:22:39 2018 SMCO started with pid=19, OS id=2076 Mon Jan 29 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3003]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Mon Jan 29 22:00:00 2018 Starting background process VKRM Mon Jan 29 22:00:00 2018 VKRM started with pid=21, OS id=13164 Mon Jan 29 22:00:05 2018 DM00 started with pid=33, OS id=12380, job DEV.SYS_EXPORT_SCHEMA_01 Mon Jan 29 22:00:07 2018 DW00 started with pid=34, OS id=12772, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Mon Jan 29 22:00:57 2018 Thread 1 cannot allocate new log, sequence 8840 Private strand flush not complete Current log# 1 seq# 8839 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8840 (LGWR switch) Current log# 2 seq# 8840 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Jan 30 02:00:00 2018 Clearing Resource Manager plan via parameter Tue Jan 30 07:51:46 2018 Thread 1 advanced to log sequence 8841 (LGWR switch) Current log# 3 seq# 8841 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Tue Jan 30 15:37:05 2018 Thread 1 advanced to log sequence 8842 (LGWR switch) Current log# 1 seq# 8842 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Tue Jan 30 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3004]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Tue Jan 30 22:00:00 2018 Starting background process VKRM Tue Jan 30 22:00:00 2018 VKRM started with pid=27, OS id=60004 Tue Jan 30 22:00:00 2018 DM00 started with pid=30, OS id=59728, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 30 22:00:01 2018 DW00 started with pid=31, OS id=60192, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Tue Jan 30 22:00:21 2018 Thread 1 cannot allocate new log, sequence 8843 Private strand flush not complete Current log# 1 seq# 8842 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8843 (LGWR switch) Current log# 2 seq# 8843 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Jan 30 22:15:54 2018 Thread 1 advanced to log sequence 8844 (LGWR switch) Current log# 3 seq# 8844 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Jan 31 02:00:00 2018 Clearing Resource Manager plan via parameter Wed Jan 31 08:20:49 2018 Thread 1 advanced to log sequence 8845 (LGWR switch) Current log# 1 seq# 8845 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Wed Jan 31 17:04:32 2018 Thread 1 advanced to log sequence 8846 (LGWR switch) Current log# 2 seq# 8846 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Wed Jan 31 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3005]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Wed Jan 31 22:00:00 2018 Starting background process VKRM Wed Jan 31 22:00:00 2018 VKRM started with pid=21, OS id=105616 Wed Jan 31 22:00:00 2018 DM00 started with pid=27, OS id=105940, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 31 22:00:01 2018 DW00 started with pid=29, OS id=105964, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Wed Jan 31 22:00:25 2018 Thread 1 cannot allocate new log, sequence 8847 Private strand flush not complete Current log# 2 seq# 8846 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thread 1 advanced to log sequence 8847 (LGWR switch) Current log# 3 seq# 8847 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Jan 31 22:16:26 2018 Thread 1 advanced to log sequence 8848 (LGWR switch) Current log# 1 seq# 8848 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thu Feb 01 02:00:00 2018 Clearing Resource Manager plan via parameter Thu Feb 01 08:18:11 2018 Thread 1 advanced to log sequence 8849 (LGWR switch) Current log# 2 seq# 8849 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Feb 01 15:30:53 2018 Thread 1 advanced to log sequence 8850 (LGWR switch) Current log# 3 seq# 8850 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thu Feb 01 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3006]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Thu Feb 01 22:00:00 2018 Starting background process VKRM Thu Feb 01 22:00:00 2018 VKRM started with pid=26, OS id=152536 Thu Feb 01 22:00:00 2018 DM00 started with pid=31, OS id=152744, job DEV.SYS_EXPORT_SCHEMA_01 Thu Feb 01 22:00:02 2018 DW00 started with pid=35, OS id=152996, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Thu Feb 01 22:00:27 2018 Thread 1 cannot allocate new log, sequence 8851 Private strand flush not complete Current log# 3 seq# 8850 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Thread 1 advanced to log sequence 8851 (LGWR switch) Current log# 1 seq# 8851 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thu Feb 01 23:38:49 2018 Thread 1 advanced to log sequence 8852 (LGWR switch) Current log# 2 seq# 8852 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Fri Feb 02 02:00:00 2018 Clearing Resource Manager plan via parameter Fri Feb 02 09:30:59 2018 Thread 1 advanced to log sequence 8853 (LGWR switch) Current log# 3 seq# 8853 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Fri Feb 02 17:22:43 2018 Thread 1 advanced to log sequence 8854 (LGWR switch) Current log# 1 seq# 8854 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Fri Feb 02 21:35:52 2018 Thread 1 advanced to log sequence 8855 (LGWR switch) Current log# 2 seq# 8855 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Fri Feb 02 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3007]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Fri Feb 02 22:00:00 2018 Starting background process VKRM Fri Feb 02 22:00:00 2018 VKRM started with pid=21, OS id=198968 Fri Feb 02 22:00:00 2018 DM00 started with pid=34, OS id=200656, job DEV.SYS_EXPORT_SCHEMA_01 Fri Feb 02 22:00:01 2018 DW00 started with pid=35, OS id=200228, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Fri Feb 02 23:34:21 2018 Thread 1 advanced to log sequence 8856 (LGWR switch) Current log# 3 seq# 8856 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Sat Feb 03 02:00:00 2018 Clearing Resource Manager plan via parameter Sat Feb 03 06:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3008]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Sat Feb 03 06:00:00 2018 Starting background process VKRM Sat Feb 03 06:00:00 2018 VKRM started with pid=26, OS id=214160 Sat Feb 03 08:13:56 2018 Thread 1 advanced to log sequence 8857 (LGWR switch) Current log# 1 seq# 8857 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Mon Feb 05 08:28:07 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Mon Feb 05 08:28:13 2018 PMON started with pid=2, OS id=3956 Mon Feb 05 08:28:13 2018 VKTM started with pid=3, OS id=3960 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Mon Feb 05 08:28:13 2018 GEN0 started with pid=4, OS id=3964 Mon Feb 05 08:28:13 2018 DIAG started with pid=5, OS id=3968 Mon Feb 05 08:28:13 2018 DBRM started with pid=6, OS id=3972 Mon Feb 05 08:28:13 2018 PSP0 started with pid=7, OS id=3976 Mon Feb 05 08:28:13 2018 DIA0 started with pid=8, OS id=3980 Mon Feb 05 08:28:13 2018 MMAN started with pid=9, OS id=3988 Mon Feb 05 08:28:13 2018 DBW0 started with pid=10, OS id=3992 Mon Feb 05 08:28:13 2018 LGWR started with pid=11, OS id=3996 Mon Feb 05 08:28:13 2018 CKPT started with pid=12, OS id=4000 Mon Feb 05 08:28:13 2018 SMON started with pid=13, OS id=4004 Mon Feb 05 08:28:13 2018 RECO started with pid=14, OS id=4008 Mon Feb 05 08:28:13 2018 MMON started with pid=15, OS id=4012 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Mon Feb 05 08:28:13 2018 MMNL started with pid=16, OS id=4016 starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Mon Feb 05 08:28:15 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2484465439 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1224 KB redo, 112 data blocks need recovery Started redo application at Thread 1: logseq 8857, block 18469 Recovery of Online Redo Log: Thread 1 Group 1 Seq 8857 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Completed redo application of 0.31MB Completed crash recovery at Thread 1: logseq 8857, block 20918, scn 239557344 112 data blocks read, 112 data blocks written, 1224 redo k-bytes read Thread 1 advanced to log sequence 8858 (thread open) Thread 1 opened at log sequence 8858 Current log# 2 seq# 8858 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Successful open of redo thread 1 SMON: enabling cache recovery Mon Feb 05 08:28:25 2018 Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Mon Feb 05 08:28:25 2018 SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Mon Feb 05 08:28:28 2018 QMNC started with pid=20, OS id=4220 Completed: alter database open Mon Feb 05 08:28:34 2018 Starting background process CJQ0 Mon Feb 05 08:28:34 2018 CJQ0 started with pid=25, OS id=4464 Mon Feb 05 08:28:35 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Mon Feb 05 08:33:47 2018 Starting background process SMCO Mon Feb 05 08:33:47 2018 SMCO started with pid=22, OS id=5552 Mon Feb 05 08:56:34 2018 Thread 1 advanced to log sequence 8859 (LGWR switch) Current log# 3 seq# 8859 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Mon Feb 05 14:20:23 2018 Thread 1 advanced to log sequence 8860 (LGWR switch) Current log# 1 seq# 8860 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Mon Feb 05 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3003]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Mon Feb 05 22:00:00 2018 Starting background process VKRM Mon Feb 05 22:00:00 2018 VKRM started with pid=21, OS id=2488 Mon Feb 05 22:00:03 2018 DM00 started with pid=33, OS id=4712, job DEV.SYS_EXPORT_SCHEMA_01 Mon Feb 05 22:00:06 2018 DW00 started with pid=35, OS id=6092, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Mon Feb 05 22:00:18 2018 Thread 1 cannot allocate new log, sequence 8861 Private strand flush not complete Current log# 1 seq# 8860 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8861 (LGWR switch) Current log# 2 seq# 8861 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Feb 06 02:00:00 2018 Clearing Resource Manager plan via parameter Tue Feb 06 03:12:42 2018 Thread 1 advanced to log sequence 8862 (LGWR switch) Current log# 3 seq# 8862 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Tue Feb 06 09:17:32 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Tue Feb 06 09:17:36 2018 PMON started with pid=2, OS id=3516 Tue Feb 06 09:17:36 2018 VKTM started with pid=3, OS id=3520 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Tue Feb 06 09:17:36 2018 GEN0 started with pid=4, OS id=3524 Tue Feb 06 09:17:36 2018 DIAG started with pid=5, OS id=3528 Tue Feb 06 09:17:37 2018 DBRM started with pid=6, OS id=3532 Tue Feb 06 09:17:37 2018 PSP0 started with pid=7, OS id=3536 Tue Feb 06 09:17:37 2018 DIA0 started with pid=8, OS id=3540 Tue Feb 06 09:17:37 2018 MMAN started with pid=9, OS id=3544 Tue Feb 06 09:17:37 2018 DBW0 started with pid=10, OS id=3548 Tue Feb 06 09:17:37 2018 LGWR started with pid=11, OS id=3552 Tue Feb 06 09:17:37 2018 CKPT started with pid=12, OS id=3556 Tue Feb 06 09:17:37 2018 SMON started with pid=13, OS id=3560 Tue Feb 06 09:17:37 2018 RECO started with pid=14, OS id=3564 Tue Feb 06 09:17:37 2018 MMON started with pid=15, OS id=3568 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Tue Feb 06 09:17:37 2018 MMNL started with pid=16, OS id=3572 Tue Feb 06 09:17:38 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2484533298 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 2206 KB redo, 466 data blocks need recovery Started redo application at Thread 1: logseq 8862, block 28714 Recovery of Online Redo Log: Thread 1 Group 3 Seq 8862 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Completed redo application of 1.09MB Completed crash recovery at Thread 1: logseq 8862, block 33127, scn 239693494 466 data blocks read, 466 data blocks written, 2206 redo k-bytes read Thread 1 advanced to log sequence 8863 (thread open) Thread 1 opened at log sequence 8863 Current log# 1 seq# 8863 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Successful open of redo thread 1 SMON: enabling cache recovery Tue Feb 06 09:17:49 2018 Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Tue Feb 06 09:17:49 2018 SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Tue Feb 06 09:17:52 2018 QMNC started with pid=20, OS id=4084 Completed: alter database open Tue Feb 06 09:17:58 2018 Starting background process CJQ0 Tue Feb 06 09:17:58 2018 CJQ0 started with pid=22, OS id=3220 Tue Feb 06 09:17:59 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Tue Feb 06 09:23:00 2018 Starting background process SMCO Tue Feb 06 09:23:00 2018 SMCO started with pid=19, OS id=2272 Tue Feb 06 16:28:04 2018 Thread 1 advanced to log sequence 8864 (LGWR switch) Current log# 2 seq# 8864 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Tue Feb 06 17:01:14 2018 AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record Tue Feb 06 17:01:15 2018 AUD: OS Error = 1717 encountered while writing audit record opidcl aborting process unknown ospid (5540) as a result of ORA-28056 Tue Feb 06 17:01:15 2018 AUD: OS Error = 1717 encountered while writing audit record opidcl aborting process unknown ospid (5632) as a result of ORA-28056 Tue Feb 06 17:01:15 2018 AUD: OS Error = 1717 encountered while writing audit record opidcl aborting process unknown ospid (4192) as a result of ORA-28056 Tue Feb 06 17:01:15 2018 AUD: OS Error = 1717 encountered while writing audit record opidcl aborting process unknown ospid (384) as a result of ORA-28056 Tue Feb 06 17:01:18 2018 AUD: OS Error = 1717 encountered while writing audit record Tue Feb 06 17:05:12 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Tue Feb 06 17:05:17 2018 PMON started with pid=2, OS id=4020 Tue Feb 06 17:05:17 2018 VKTM started with pid=3, OS id=4024 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Tue Feb 06 17:05:17 2018 GEN0 started with pid=4, OS id=4028 Tue Feb 06 17:05:17 2018 DIAG started with pid=5, OS id=4032 Tue Feb 06 17:05:17 2018 DBRM started with pid=6, OS id=4036 Tue Feb 06 17:05:17 2018 PSP0 started with pid=7, OS id=4040 Tue Feb 06 17:05:17 2018 DIA0 started with pid=8, OS id=4044 Tue Feb 06 17:05:17 2018 MMAN started with pid=9, OS id=4048 Tue Feb 06 17:05:17 2018 DBW0 started with pid=10, OS id=4052 Tue Feb 06 17:05:17 2018 LGWR started with pid=11, OS id=4056 Tue Feb 06 17:05:17 2018 CKPT started with pid=12, OS id=4060 Tue Feb 06 17:05:17 2018 SMON started with pid=13, OS id=4064 Tue Feb 06 17:05:17 2018 RECO started with pid=14, OS id=4068 Tue Feb 06 17:05:17 2018 MMON started with pid=15, OS id=4072 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Tue Feb 06 17:05:17 2018 MMNL started with pid=16, OS id=4076 starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Tue Feb 06 17:05:18 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2484600270 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 2023 KB redo, 351 data blocks need recovery Started redo application at Thread 1: logseq 8864, block 500 Recovery of Online Redo Log: Thread 1 Group 2 Seq 8864 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Completed redo application of 0.91MB Completed crash recovery at Thread 1: logseq 8864, block 4547, scn 239747048 351 data blocks read, 351 data blocks written, 2023 redo k-bytes read Thread 1 advanced to log sequence 8865 (thread open) Thread 1 opened at log sequence 8865 Current log# 3 seq# 8865 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Successful open of redo thread 1 SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Tue Feb 06 17:05:27 2018 SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Tue Feb 06 17:05:29 2018 Starting background process QMNC Tue Feb 06 17:05:30 2018 QMNC started with pid=20, OS id=3928 Completed: alter database open Tue Feb 06 17:05:34 2018 Starting background process CJQ0 Tue Feb 06 17:05:34 2018 CJQ0 started with pid=22, OS id=4000 Tue Feb 06 17:05:35 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Tue Feb 06 17:12:14 2018 Starting background process SMCO Tue Feb 06 17:12:14 2018 SMCO started with pid=21, OS id=524 Tue Feb 06 19:03:44 2018 Thread 1 advanced to log sequence 8866 (LGWR switch) Current log# 1 seq# 8866 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Tue Feb 06 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3004]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Tue Feb 06 22:00:00 2018 Starting background process VKRM Tue Feb 06 22:00:00 2018 VKRM started with pid=25, OS id=1404 Tue Feb 06 22:00:03 2018 DM00 started with pid=33, OS id=6028, job DEV.SYS_EXPORT_SCHEMA_01 Tue Feb 06 22:00:06 2018 DW00 started with pid=34, OS id=4172, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Tue Feb 06 22:00:49 2018 Thread 1 cannot allocate new log, sequence 8867 Private strand flush not complete Current log# 1 seq# 8866 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8867 (LGWR switch) Current log# 2 seq# 8867 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Wed Feb 07 02:00:00 2018 Clearing Resource Manager plan via parameter Wed Feb 07 02:14:10 2018 AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record Wed Feb 07 02:19:41 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Wed Feb 07 02:19:45 2018 PMON started with pid=2, OS id=3476 Wed Feb 07 02:19:45 2018 VKTM started with pid=3, OS id=3480 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Wed Feb 07 02:19:45 2018 GEN0 started with pid=4, OS id=3484 Wed Feb 07 02:19:45 2018 DIAG started with pid=5, OS id=3488 Wed Feb 07 02:19:45 2018 DBRM started with pid=6, OS id=3492 Wed Feb 07 02:19:45 2018 PSP0 started with pid=7, OS id=3496 Wed Feb 07 02:19:46 2018 DIA0 started with pid=8, OS id=3500 Wed Feb 07 02:19:46 2018 MMAN started with pid=9, OS id=3504 Wed Feb 07 02:19:46 2018 DBW0 started with pid=10, OS id=3508 Wed Feb 07 02:19:46 2018 LGWR started with pid=11, OS id=3512 Wed Feb 07 02:19:46 2018 CKPT started with pid=12, OS id=3516 Wed Feb 07 02:19:46 2018 SMON started with pid=13, OS id=3520 Wed Feb 07 02:19:46 2018 RECO started with pid=14, OS id=3524 Wed Feb 07 02:19:46 2018 MMON started with pid=15, OS id=3528 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Wed Feb 07 02:19:46 2018 MMNL started with pid=16, OS id=3532 starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Wed Feb 07 02:19:47 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2484599747 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1728 KB redo, 239 data blocks need recovery Started redo application at Thread 1: logseq 8867, block 26016 Recovery of Online Redo Log: Thread 1 Group 2 Seq 8867 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Completed redo application of 0.58MB Completed crash recovery at Thread 1: logseq 8867, block 29472, scn 239830497 239 data blocks read, 239 data blocks written, 1728 redo k-bytes read Thread 1 advanced to log sequence 8868 (thread open) Thread 1 opened at log sequence 8868 Current log# 3 seq# 8868 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Successful open of redo thread 1 SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Wed Feb 07 02:19:56 2018 SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Wed Feb 07 02:19:58 2018 Starting background process QMNC Wed Feb 07 02:19:58 2018 QMNC started with pid=20, OS id=3880 Completed: alter database open Wed Feb 07 02:20:02 2018 Starting background process CJQ0 Wed Feb 07 02:20:02 2018 CJQ0 started with pid=21, OS id=4004 Wed Feb 07 02:20:03 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Wed Feb 07 02:24:59 2018 Starting background process SMCO Wed Feb 07 02:24:59 2018 SMCO started with pid=19, OS id=4504 Wed Feb 07 03:06:39 2018 AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record AUD: OS Error = 1717 encountered while writing audit record Wed Feb 07 03:19:22 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Wed Feb 07 03:19:28 2018 PMON started with pid=2, OS id=2912 Wed Feb 07 03:19:28 2018 VKTM started with pid=3, OS id=3056 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Wed Feb 07 03:19:28 2018 GEN0 started with pid=4, OS id=2328 Wed Feb 07 03:19:28 2018 DIAG started with pid=5, OS id=2332 Wed Feb 07 03:19:28 2018 DBRM started with pid=6, OS id=2424 Wed Feb 07 03:19:28 2018 PSP0 started with pid=7, OS id=2544 Wed Feb 07 03:19:28 2018 DIA0 started with pid=8, OS id=3076 Wed Feb 07 03:19:28 2018 MMAN started with pid=9, OS id=3080 Wed Feb 07 03:19:28 2018 DBW0 started with pid=10, OS id=3084 Wed Feb 07 03:19:28 2018 LGWR started with pid=11, OS id=3088 Wed Feb 07 03:19:28 2018 CKPT started with pid=12, OS id=3092 Wed Feb 07 03:19:28 2018 SMON started with pid=13, OS id=3096 Wed Feb 07 03:19:29 2018 RECO started with pid=14, OS id=3100 Wed Feb 07 03:19:29 2018 MMON started with pid=15, OS id=3104 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Wed Feb 07 03:19:29 2018 MMNL started with pid=16, OS id=3108 starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Wed Feb 07 03:19:30 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2484626115 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1269 KB redo, 272 data blocks need recovery Started redo application at Thread 1: logseq 8868, block 3086 Recovery of Online Redo Log: Thread 1 Group 3 Seq 8868 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Completed redo application of 0.86MB Completed crash recovery at Thread 1: logseq 8868, block 5625, scn 239853863 272 data blocks read, 272 data blocks written, 1269 redo k-bytes read Wed Feb 07 03:19:40 2018 Thread 1 advanced to log sequence 8869 (thread open) Thread 1 opened at log sequence 8869 Current log# 1 seq# 8869 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Successful open of redo thread 1 Wed Feb 07 03:19:40 2018 SMON: enabling cache recovery Wed Feb 07 03:19:43 2018 Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Wed Feb 07 03:19:45 2018 QMNC started with pid=20, OS id=3776 Completed: alter database open Wed Feb 07 03:19:50 2018 Starting background process CJQ0 Wed Feb 07 03:19:50 2018 CJQ0 started with pid=22, OS id=4004 Wed Feb 07 03:19:50 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Wed Feb 07 03:24:46 2018 Starting background process SMCO Wed Feb 07 03:24:46 2018 SMCO started with pid=19, OS id=4408 Wed Feb 07 10:02:46 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Wed Feb 07 10:02:50 2018 PMON started with pid=2, OS id=3480 Wed Feb 07 10:02:50 2018 VKTM started with pid=3, OS id=3484 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Wed Feb 07 10:02:51 2018 GEN0 started with pid=4, OS id=3488 Wed Feb 07 10:02:51 2018 DIAG started with pid=5, OS id=3492 Wed Feb 07 10:02:51 2018 DBRM started with pid=6, OS id=3496 Wed Feb 07 10:02:51 2018 PSP0 started with pid=7, OS id=3500 Wed Feb 07 10:02:51 2018 DIA0 started with pid=8, OS id=3504 Wed Feb 07 10:02:51 2018 MMAN started with pid=9, OS id=3508 Wed Feb 07 10:02:51 2018 DBW0 started with pid=10, OS id=3512 Wed Feb 07 10:02:51 2018 LGWR started with pid=11, OS id=3516 Wed Feb 07 10:02:51 2018 CKPT started with pid=12, OS id=3520 Wed Feb 07 10:02:51 2018 SMON started with pid=13, OS id=3524 Wed Feb 07 10:02:51 2018 RECO started with pid=14, OS id=3528 Wed Feb 07 10:02:51 2018 MMON started with pid=15, OS id=3532 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Wed Feb 07 10:02:51 2018 MMNL started with pid=16, OS id=3536 starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Wed Feb 07 10:02:52 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2484683852 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1440 KB redo, 275 data blocks need recovery Started redo application at Thread 1: logseq 8869, block 36197 Recovery of Online Redo Log: Thread 1 Group 1 Seq 8869 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Completed redo application of 0.63MB Completed crash recovery at Thread 1: logseq 8869, block 39077, scn 239897718 275 data blocks read, 275 data blocks written, 1440 redo k-bytes read Thread 1 advanced to log sequence 8870 (thread open) Thread 1 opened at log sequence 8870 Current log# 2 seq# 8870 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Successful open of redo thread 1 SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Wed Feb 07 10:03:01 2018 SMON: enabling tx recovery Database Characterset is WE8MSWIN1252 No Resource Manager plan active Wed Feb 07 10:03:02 2018 replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Wed Feb 07 10:03:03 2018 QMNC started with pid=20, OS id=3884 Completed: alter database open Wed Feb 07 10:03:08 2018 Starting background process CJQ0 Wed Feb 07 10:03:08 2018 CJQ0 started with pid=21, OS id=4024 Wed Feb 07 10:03:08 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Wed Feb 07 10:10:58 2018 Starting background process SMCO Wed Feb 07 10:10:58 2018 SMCO started with pid=27, OS id=2064 Wed Feb 07 17:27:00 2018 Thread 1 advanced to log sequence 8871 (LGWR switch) Current log# 3 seq# 8871 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Wed Feb 07 19:01:34 2018 Thread 1 advanced to log sequence 8872 (LGWR switch) Current log# 1 seq# 8872 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Wed Feb 07 22:00:00 2018 Setting Resource Manager plan SCHEDULER[0x3005]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Wed Feb 07 22:00:00 2018 Starting background process VKRM Wed Feb 07 22:00:00 2018 VKRM started with pid=19, OS id=5712 Wed Feb 07 22:00:04 2018 DM00 started with pid=36, OS id=5436, job DEV.SYS_EXPORT_SCHEMA_01 Wed Feb 07 22:00:07 2018 DW00 started with pid=37, OS id=5024, wid=1, job DEV.SYS_EXPORT_SCHEMA_01 Wed Feb 07 22:00:49 2018 Thread 1 cannot allocate new log, sequence 8873 Private strand flush not complete Current log# 1 seq# 8872 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO01.LOG Thread 1 advanced to log sequence 8873 (LGWR switch) Current log# 2 seq# 8873 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Thu Feb 08 02:00:00 2018 Clearing Resource Manager plan via parameter Thu Feb 08 08:29:48 2018 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production. Using parameter settings in server-side spfile C:\APP\METRO\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETMTDB.ORA System parameters with non-default values: processes = 150 memory_target = 6560M control_files = "C:\APP\METRO\ORADATA\TMTDB\CONTROL01.CTL" control_files = "C:\APP\METRO\FLASH_RECOVERY_AREA\TMTDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "C:\app\Metro\flash_recovery_area" db_recovery_file_dest_size= 3912M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=tmtdbXDB)" audit_file_dest = "C:\APP\METRO\ADMIN\TMTDB\ADUMP" audit_trail = "DB" db_name = "tmtdb" open_cursors = 300 diagnostic_dest = "C:\APP\METRO" Thu Feb 08 08:29:54 2018 PMON started with pid=2, OS id=3548 Thu Feb 08 08:29:54 2018 VKTM started with pid=3, OS id=3552 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Thu Feb 08 08:29:54 2018 GEN0 started with pid=4, OS id=3556 Thu Feb 08 08:29:54 2018 DIAG started with pid=5, OS id=3560 Thu Feb 08 08:29:54 2018 DBRM started with pid=6, OS id=3564 Thu Feb 08 08:29:54 2018 PSP0 started with pid=7, OS id=3568 Thu Feb 08 08:29:54 2018 DIA0 started with pid=8, OS id=3572 Thu Feb 08 08:29:54 2018 MMAN started with pid=9, OS id=3576 Thu Feb 08 08:29:54 2018 DBW0 started with pid=10, OS id=3580 Thu Feb 08 08:29:54 2018 LGWR started with pid=11, OS id=3584 Thu Feb 08 08:29:54 2018 CKPT started with pid=12, OS id=3588 Thu Feb 08 08:29:54 2018 SMON started with pid=13, OS id=3592 Thu Feb 08 08:29:54 2018 RECO started with pid=14, OS id=3596 Thu Feb 08 08:29:54 2018 MMON started with pid=15, OS id=3600 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Thu Feb 08 08:29:54 2018 MMNL started with pid=16, OS id=3604 starting up 1 shared server(s) ... ORACLE_BASE from environment = C:\app\Metro Thu Feb 08 08:29:56 2018 alter database mount exclusive Successful mount of redo thread 1, with mount id 2484742660 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads Started redo scan Completed redo scan read 1620 KB redo, 189 data blocks need recovery Started redo application at Thread 1: logseq 8873, block 54451 Recovery of Online Redo Log: Thread 1 Group 2 Seq 8873 Reading mem 0 Mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO02.LOG Completed redo application of 0.54MB Completed crash recovery at Thread 1: logseq 8873, block 57691, scn 240018984 189 data blocks read, 189 data blocks written, 1620 redo k-bytes read Thread 1 advanced to log sequence 8874 (thread open) Thread 1 opened at log sequence 8874 Current log# 3 seq# 8874 mem# 0: C:\APP\METRO\ORADATA\TMTDB\REDO03.LOG Successful open of redo thread 1 SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed Thu Feb 08 08:30:06 2018 SMON: enabling tx recovery Thu Feb 08 08:30:06 2018 Database Characterset is WE8MSWIN1252 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Thu Feb 08 08:30:09 2018 QMNC started with pid=20, OS id=3384 Completed: alter database open Thu Feb 08 08:30:15 2018 Starting background process CJQ0 Thu Feb 08 08:30:15 2018 CJQ0 started with pid=21, OS id=4032 Thu Feb 08 08:30:15 2018 db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Thu Feb 08 08:35:13 2018 Starting background process SMCO Thu Feb 08 08:35:13 2018 SMCO started with pid=24, OS id=3336