Skip to Main Content

Oracle Database Discussions

Announcement

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

Database Started In Restricted Mode...

969526Apr 24 2013 — edited Apr 28 2013
Dear Exports,

We are using Oracle 10gR2 on Windows server 2008. My database size is approximately 2tb. Now we are going to setup Dataguard for our primary. We started the database with the changer parameters for dataguard and create spfile from pfile. And started the database with Spfile. But after some time i noticed that the database started automatically in Restricted mode. As in our database Previously dataguard was configured, due to the some problem that setup is not working and the logs are not applied in Standby server. I thought may be for this reason database going to restricted mode automatically so i set the log_archive_dest_state_2='DEFFER' and Now I scanned the whore alert.log file and found the same situation of restricted is happening from Jan 2010. Please Suggest some solution how i can over come the problem.

The alertlog when i started the database recently...

ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Fri Apr 12 19:12:39 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =97
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 800
sessions = 885
sga_max_size = 10737418240
__shared_pool_size = 1325400064
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 8589934592
control_files = G:\ORADATA\CONTROL01.CTL, G:\ORADATA\CONTROL02.CTL, G:\ORADATA\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 7214202880
compatible = 10.2.0.3.0
log_archive_config = DG_CONFIG=(orcl,stdby)
log_archive_dest_1 = LOCATION=I:\archive_log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl
log_archive_dest_2 = SERVICE=stdby NOAFFIRM ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stdby
log_archive_dest_state_1 = enable
log_archive_max_processes= 30
log_archive_format = ARC%D_%s_%R.%T
fal_client = orcl
fal_server = stdby
db_file_multiblock_read_count= 16
db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
standby_file_management = AUTO
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 5400
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.168.12.86)(PORT=1521))
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = orcl
open_cursors = 500
pga_aggregate_target = 10737418240
PMON started with pid=2, OS id=14328
PSP0 started with pid=3, OS id=15420
MMAN started with pid=4, OS id=9092
DBW0 started with pid=5, OS id=12360
DBW1 started with pid=6, OS id=18112
LGWR started with pid=7, OS id=18360
CKPT started with pid=8, OS id=18448
SMON started with pid=9, OS id=17160
RECO started with pid=10, OS id=18512
CJQ0 started with pid=11, OS id=19324
MMON started with pid=12, OS id=14380
Fri Apr 12 19:12:40 2013
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=13, OS id=2996
Fri Apr 12 19:12:40 2013
starting up 1 shared server(s) ...
Fri Apr 12 19:12:41 2013
ALTER DATABASE MOUNT
Fri Apr 12 19:12:45 2013
Setting recovery target incarnation to 2
Fri Apr 12 19:12:45 2013
Successful mount of redo thread 1, with mount id 1340307369
Fri Apr 12 19:12:45 2013
Allocated 15937344 bytes in shared pool for flashback generation buffer
Starting background process RVWR
RVWR started with pid=17, OS id=5524
Fri Apr 12 19:12:45 2013
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Fri Apr 12 19:12:46 2013
ALTER DATABASE OPEN
Fri Apr 12 19:12:46 2013
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=18, OS id=11964
ARC1 started with pid=19, OS id=13472
ARC2 started with pid=20, OS id=17960
ARC3 started with pid=21, OS id=18548
ARC4 started with pid=22, OS id=15660
ARC5 started with pid=23, OS id=15548
ARC6 started with pid=24, OS id=14720
ARC7 started with pid=25, OS id=15780
ARC8 started with pid=26, OS id=17992
ARC9 started with pid=27, OS id=17988
ARCa started with pid=28, OS id=19436
ARCb started with pid=29, OS id=16104
ARCc started with pid=30, OS id=6656
ARCd started with pid=31, OS id=6900
ARCe started with pid=32, OS id=10568
ARCf started with pid=33, OS id=16992
ARCg started with pid=34, OS id=14372
ARCh started with pid=35, OS id=18084
ARCi started with pid=36, OS id=5788
ARCj started with pid=37, OS id=4940
ARCk started with pid=38, OS id=18816
ARCl started with pid=39, OS id=14588
ARCm started with pid=40, OS id=16820
ARCn started with pid=41, OS id=8068
ARCo started with pid=42, OS id=18736
ARCp started with pid=43, OS id=8316
ARCq started with pid=44, OS id=5952
ARCr started with pid=45, OS id=16304
ARCs started with pid=46, OS id=14884
Fri Apr 12 19:12:46 2013
ARC0: Archival started
ARCt started with pid=47, OS id=19408
Fri Apr 12 19:12:46 2013
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 opened at log sequence 117446
Current log# 10 seq# 117446 mem# 0: G:\ORADATA\REDO10A.LOG
Current log# 10 seq# 117446 mem# 1: H:\ORADATA\REDO10B.LOG
Fri Apr 12 19:12:46 2013
ARC0: Becoming the 'no FAL' ARCH
Fri Apr 12 19:12:46 2013
ARC0: Becoming the 'no SRL' ARCH
Fri Apr 12 19:12:46 2013
ARC8: Becoming the heartbeat ARCH
Fri Apr 12 19:12:47 2013
Successful open of redo thread 1
Fri Apr 12 19:12:47 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Apr 12 19:12:47 2013
SMON: enabling cache recovery
Fri Apr 12 19:12:48 2013
Successfully onlined Undo Tablespace 1.
Fri Apr 12 19:12:48 2013
SMON: enabling tx recovery
Fri Apr 12 19:12:48 2013
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 16
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=48, OS id=10048
Fri Apr 12 19:12:51 2013
Completed: ALTER DATABASE OPEN
Fri Apr 12 19:12:51 2013
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mmon_14380.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 99.56% used, and has 9486336 remaining bytes available.

Fri Apr 12 19:12:51 2013
************************************************************************
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
Dump file d:\oracle\product\10.2.0\admin\orcl\bdump\alert_orcl.log
Fri Apr 12 19:13:26 2013
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V6.0 Service Pack 1
CPU : 16 - type 8664, 16 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:55999M/65533M, Ph+PgF:183151M/193356M
Fri Apr 12 19:13:26 2013
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =97
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 800
sessions = 885
sga_max_size = 10737418240
__shared_pool_size = 1325400064
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 8589934592
control_files = G:\ORADATA\CONTROL01.CTL, G:\ORADATA\CONTROL02.CTL, G:\ORADATA\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 7214202880
compatible = 10.2.0.3.0
log_archive_config = DG_CONFIG=(orcl,stdby)
log_archive_dest_1 = LOCATION=I:\archive_log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl
log_archive_dest_2 = SERVICE=stdby NOAFFIRM ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stdby
log_archive_dest_state_1 = enable
log_archive_max_processes= 30
log_archive_format = ARC%D_%s_%R.%T
fal_client = orcl
fal_server = stdby
db_file_multiblock_read_count= 16
db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
standby_file_management = AUTO
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 5400
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.168.12.86)(PORT=1521))
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = orcl
open_cursors = 500
pga_aggregate_target = 10737418240
PMON started with pid=2, OS id=18668
PSP0 started with pid=3, OS id=17668
MMAN started with pid=4, OS id=16896
DBW0 started with pid=5, OS id=18204
DBW1 started with pid=6, OS id=16976
LGWR started with pid=7, OS id=14552
CKPT started with pid=8, OS id=4480
SMON started with pid=9, OS id=10236
RECO started with pid=10, OS id=11832
CJQ0 started with pid=11, OS id=18844
MMON started with pid=12, OS id=15320
Fri Apr 12 19:13:27 2013
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=13, OS id=14944
Fri Apr 12 19:13:27 2013
starting up 1 shared server(s) ...
Fri Apr 12 19:13:27 2013
alter database orcl mount exclusive
Fri Apr 12 19:13:31 2013
Setting recovery target incarnation to 2
Fri Apr 12 19:13:31 2013
Successful mount of redo thread 1, with mount id 1340305111
Fri Apr 12 19:13:31 2013
Allocated 15937344 bytes in shared pool for flashback generation buffer
Starting background process RVWR
RVWR started with pid=17, OS id=12880
Fri Apr 12 19:13:31 2013
Database mounted in Exclusive Mode
Completed: alter database orcl mount exclusive
Fri Apr 12 19:13:31 2013
alter database open
Fri Apr 12 19:13:31 2013
Beginning crash recovery of 1 threads
parallel recovery started with 15 processes
Fri Apr 12 19:13:31 2013
Started redo scan
Fri Apr 12 19:13:31 2013
Completed redo scan
735 redo blocks read, 211 data blocks need recovery
Fri Apr 12 19:13:31 2013
Started redo application at
Thread 1: logseq 117446, block 97761
Fri Apr 12 19:13:31 2013
Recovery of Online Redo Log: Thread 1 Group 10 Seq 117446 Reading mem 0
Mem# 0: G:\ORADATA\REDO10A.LOG
Mem# 1: H:\ORADATA\REDO10B.LOG
Fri Apr 12 19:13:31 2013
Completed redo application
Fri Apr 12 19:13:32 2013
Completed crash recovery at
Thread 1: logseq 117446, block 98496, scn 7310601900
211 data blocks read, 211 data blocks written, 735 redo blocks read
Fri Apr 12 19:13:33 2013
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=33, OS id=18508
ARC1 started with pid=34, OS id=14692
ARC2 started with pid=35, OS id=17728
ARC3 started with pid=36, OS id=12476
ARC4 started with pid=37, OS id=19228
ARC5 started with pid=38, OS id=11552
ARC6 started with pid=39, OS id=7576
ARC7 started with pid=40, OS id=6244
ARC8 started with pid=41, OS id=18468
ARC9 started with pid=42, OS id=18492
ARCa started with pid=43, OS id=10352
ARCb started with pid=44, OS id=15516
ARCc started with pid=45, OS id=18216
ARCd started with pid=46, OS id=5660
ARCe started with pid=47, OS id=18756
ARCf started with pid=48, OS id=17828
ARCg started with pid=49, OS id=8696
ARCh started with pid=50, OS id=17736
ARCi started with pid=51, OS id=16736
ARCj started with pid=52, OS id=13208
ARCk started with pid=53, OS id=12012
ARCl started with pid=54, OS id=19180
ARCm started with pid=55, OS id=16632
ARCn started with pid=56, OS id=17588
ARCo started with pid=57, OS id=11948
ARCp started with pid=58, OS id=18416
ARCq started with pid=59, OS id=17888
ARCr started with pid=60, OS id=2144
ARCs started with pid=61, OS id=14392
Fri Apr 12 19:13:33 2013
ARC0: Archival started
ARCt started with pid=62, OS id=19264
Fri Apr 12 19:13:33 2013
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Fri Apr 12 19:13:33 2013
Thread 1 advanced to log sequence 117447 (thread open)
Thread 1 opened at log sequence 117447
Current log# 8 seq# 117447 mem# 0: G:\ORADATA\REDO08A.LOG
Current log# 8 seq# 117447 mem# 1: H:\ORADATA\REDO08B.LOG
Successful open of redo thread 1
Fri Apr 12 19:13:33 2013
ARC3: Becoming the 'no FAL' ARCH
Fri Apr 12 19:13:33 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Apr 12 19:13:33 2013
ARC3: Becoming the 'no SRL' ARCH
Fri Apr 12 19:13:33 2013
ARCr: Becoming the heartbeat ARCH
Fri Apr 12 19:13:33 2013
SMON: enabling cache recovery
Fri Apr 12 19:13:33 2013
Successfully onlined Undo Tablespace 1.
Fri Apr 12 19:13:33 2013
SMON: enabling tx recovery
Fri Apr 12 19:13:33 2013
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 16
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=63, OS id=14896
Fri Apr 12 19:13:34 2013
Completed: alter database open
Fri Apr 12 19:13:34 2013
ALTER SYSTEM disable restricted session;
Fri Apr 12 19:13:35 2013
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mmon_15320.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 99.56% used, and has 9486336 remaining bytes available.

Fri Apr 12 19:13:35 2013
************************************************************************
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
Fri Apr 12 19:13:36 2013
Error 12514 received logging on to the standby
Fri Apr 12 19:13:36 2013
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc0_18508.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

FAL[server, ARC0]: Error 12514 creating remote archivelog file 'stdby'
FAL[server, ARC0]: FAL archive failed, see trace file.
Fri Apr 12 19:13:36 2013
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc0_18508.trc:
ORA-16055: FAL request rejected

ARCH: FAL archive failed. Archiver continuing
Fri Apr 12 19:19:33 2013
Error 12514 received logging on to the standby
Fri Apr 12 19:19:33 2013
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
Fri Apr 12 19:22:52 2013
PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
Fri Apr 12 20:09:34 2013
Error 12514 received logging on to the standby
Fri Apr 12 20:09:34 2013
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
Fri Apr 12 20:13:50 2013
Sat Apr 13 01:54:52 2013
Error 12514 received logging on to the standby
Sat Apr 13 01:54:52 2013
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
Sat Apr 13 12:35:12 2013
Error 12514 received logging on to the standby
Sat Apr 13 12:35:12 2013
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
Sat Apr 13 12:37:01 2013
ALTER SYSTEM SET log_archive_dest_state_2='DEFER' SCOPE=MEMORY;
Sat Apr 13 12:38:23 2013
*************************************************************
Unable to allocate flashback log of 1946 blocks from
current recovery area of size 2147483648 bytes.
Current Flashback database retention is less than target
because of insufficient space in the flash recovery area.
Flashback will continue to use available space, but the
size of the flash recovery area must be increased to meet
the Flashback database retention target
Use ALTER SYSTEM SET db_recovery_file_dest_size command
to add space. DO NOT manually remove flashback log files
to create space.
*************************************************************
Sat Apr 13 12:38:41 2013
ALTER SYSTEM SET db_recovery_file_dest_size='5G' SCOPE=MEMORY;
Sat Apr 13 12:38:41 2013
db_recovery_file_dest_size of 5120 MB is 39.82% 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.
Sat Apr 13 15:42:21 2013
ORA-01555 caused by SQL statement below (SQL ID: 2zb70pwz9p06q, Query Duration=1365847941 sec, SCN: 0x0001.b3c0f735):
Sat Apr 13 15:42:21 2013
SELECT * FROM RELATIONAL("ORISSA_TRANSACTION"."SELLER_BIOMETRICS_TBL")
Sat Apr 13 15:48:37 2013
Thread 1 advanced to log sequence 117452 (LGWR switch)
Current log# 10 seq# 117452 mem# 0: G:\ORADATA\REDO10A.LOG
Current log# 10 seq# 117452 mem# 1: H:\ORADATA\REDO10B.LOG
Sat Apr 13 20:31:00 2013
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=31, OS id=16196
to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_30', 'ORISSA_TRANSACTION', 'KUPC$C_1_20130413203100', 'KUPC$S_1_20130413203100', 0);
kupprdp: worker process DW01 started with worker id=1, pid=66, OS id=16200
to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_30', 'ORISSA_TRANSACTION');
Sun Apr 14 00:00:11 2013
Thread 1 advanced to log sequence 117453 (LGWR switch)
Current log# 8 seq# 117453 mem# 0: G:\ORADATA\REDO08A.LOG
Current log# 8 seq# 117453 mem# 1: H:\ORADATA\REDO08B.LOG
Sun Apr 14 00:00:52 2013
Thread 1 advanced to log sequence 117454 (LGWR switch)
Current log# 9 seq# 117454 mem# 0: G:\ORADATA\REDO09A.LOG
Current log# 9 seq# 117454 mem# 1: H:\ORADATA\REDO09B.LOG
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 26 2013
Added on Apr 24 2013
38 comments
5,803 views