Monitor database in restrict mode
hello everybody,
is there a way to see session activity information in Top Activity window when database is in restricted mode? Monitored database, OMS and agent are all 10.2.0.3.
So far I have tried to grant restricted session to dbsnmp but it didn't help.
thx for any suggestion
hi Alan,
I have tried to connect as sysdba to database but it shows no data. I also reconfigured the database target properties to be monitored through sys (as sysdba) but didn't work either.
Slavek
Similar Messages
-
How to put database in RESTRICTED mode ?
Hi,
in 9.2.0.6 on Windows 2003 server how to put database in RESTRICTED mode ?
Many thanks before.ERROR at line 1:
ORA-12719: operation requires database is in RESTRICTED mode
That's because 'ALTER SYSTEM QUIESCE RESTRICTED' doesn't actually put the database into restricted mode:
SQL> select logins, active_state from v$instance;
LOGINS ACTIVE_ST
ALLOWED NORMAL
SQL> alter system quiesce restricted;
System altered.
SQL> select logins, active_state from v$instance;
LOGINS ACTIVE_ST
ALLOWED QUIESCEDTry staring the database in restricted mode and then quiescing it:
SQL>
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup restrict;
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1289508 bytes
Variable Size 117441244 bytes
Database Buffers 46137344 bytes
Redo Buffers 2904064 bytes
Database mounted.
Database opened.
SQL> alter system quiesce restricted;
System altered.
SQL> select logins, active_state from v$instance;
LOGINS ACTIVE_ST
RESTRICTED QUIESCED
SQL>As you can see from V$INSTANCE, when you are running in restricted mode LOGINS will have a value of 'RESTRICTED'
However - I still think that if you are dealing with users logging in to your (RESTRICTED) database via the listener then the easiest option is to stop the listener whilst the database is down and restart it once your alter database command has completed.
PS : No any other user is connected.No, they wouldn't be this time because you had quiesced the database... but you still need to get the database into restricted mode for this alter database command. -
How to put RAC database in restricted mode?is it with srvctl?
I know for standalone database its
SQL> startup restrict --if its down
SQL> alter system enable restricted session; --if its up
Any idea for RAC ? any option with srvctl ? what are the steps .....
Thanks in advance for help
GaganHi
There is no option like that. It's as same as keeping normal database in restricted mode.
alter database enable restricted session;
and end with
alter database disable restricted session.
Regards,
Phani Kumar P
+919948677317 -
hi
I want to make an ımport like
imp sys/***@live .......
While doing this import I dont want anybody to connect database.
If I open the database ın restrict mode sınce the ımport ıs done by remote,
I cannot connect even by sys user.
I can do it by first starting the import from remote than ALTER SYSTEM enable RESTRICTED SESSION;
I wonder if there is any other way?but the version is oracle 10g
So?Its there in 10g too.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/intro.htm#sthref147
Aman.... -
AWR Snapshots Required When Database is in Restricted Mode
We are planning to run some processes, but want the database to be in restricted mode to keep "normal" users out.
But we also need to monitor performance on the system during that. Normally however, scheduled jobs such as this don't run in restricted mode.
Does anyone know of any way of still (preferably automatically) running the AWR snapshots when the database (Version 10.1.0.5) is in restrict mode.
I know this may be a little off-topic for this forum, but it was the nearest I could find.
Any information gratefully received.Hi,
Unfortunately this is not possible in version 10.1 .
In 10.2.0.4 (when it is released) and 11g it is possible to allow this using the ALLOW_RUNS_IN_RESTRICTED_MODE boolean job attribute.
In prior releases no jobs will run when the database is in restricted mode.
Thanks,
Ravi. -
Database Started In Restricted Mode...
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.LOGlike you show in the alert.log:
PROBLEM
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.
SOLUTION
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.
************************************************************************choose one and try again. Post if you have more issues. -
Hi, in our RAC environment, we are enabling egach instance in RESTRICT mode to block incoming connections. But we need specific users to login with restricted session privilege. This is okay with single instance, but with RAC, all users cannot connect. What should be the problem? Thanks
It works just fine with me in 11.2.0.4. My instances are in restricted mode and yet I can connect locally.
SQL> select instance_number,logins
2 from gv$instance;
INSTANCE_NUMBER LOGINS
1 RESTRICTED <== both instances in restricted mode.
2 RESTRICTED
SQL> exit <== exit from sqlplus
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
[oracle@nau-rac01 ~]$ sqlplus /nolog
SQL*Plus: Release 11.2.0.4.0 Production on Thu Jul 24 15:25:16 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.
SQL> connect peasland <== connect with my dba account.
Enter password:
Connected.
So it works in 11.2.0.4 just fine. I'll ask one more time.... "please post the exact steps taken and the exact error messages." Otherwise I can't be of much help.
Cheers,
Brian -
Oracle 10g in restricted mode, unable to start up
We have a 10g instance which we shut down and started in restricted mode. It is now open, restrict.
No one including SYS can connect.
ORA-12526: TNS:listener: all appropriate instances are in restricted mode
The original session which shut down the DB is logged off.
How can we start the database?
ThanksWe did it by not specifying the instance on the connection.
I.e.
sqlplus system/password@DATABASE
did not work
but
ORACLE_HOME=DATABASE
sqlplus system/password
did
Message was edited by:
cubittm -
ORA-12526: TNS:listener: all appropriate instances are in restricted mode
Hi all,
I am trying to connect to Oracle10.2.0.2 in solaris9 as
conn sys/password@dbname as sysdba
but after this attempt it showing
ORA-12526: TNS:listener: all appropriate instances are in restricted mode
but if i connect like this
conn sys/password as sysdba
it works.
Can some one give me the solution for the same?
Thanks
VipinHi,
When you want to connect to database there are majorly two kinds of protocols are involve
1. TCP and
2. IPC
when you are talking about <username>/<password>@<servername > then though you are on same server you are refering to TCP protocol and when you are talking about <username>/<password> then you are refering to IPC protocol
now here when you are going to connect to your database through
conn sys/password as sysdba
its working fine because you are using IPC and if you connect through
conn sys/password@dbname as sysdba
it will show you error because you are using Listener TCP.
So i think that you need to check your listener status and database status both and give the output.
Thanks
Pruthiv -
Created database from cold backup.The data files were moved from a previous release . I had to open the database with the upgrade option. Now can not connect to it over netwrok or using servicenames locally too
Get error
ORA-12526 :TNS LISTENER : all appropriate instances are in restricted mode
lsnrctl status shows
Instance "xxx", status RESTRICTED, has 2 handler(s) for this service..
How can I take this instance out of restricted mode. ..Which version are you on ?
SYS@db102 SQL> startup upgrade
ORACLE instance started.
Total System Global Area 121634816 bytes
Fixed Size 1218052 bytes
Variable Size 104860156 bytes
Database Buffers 12582912 bytes
Redo Buffers 2973696 bytes
Database mounted.
Database opened.
SYS@db102 SQL> select logins from v$instance;
LOGINS
RESTRICTED
SYS@db102 SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SYS@db102 SQL> -
OWB in restricted mode issues.. anyone running successfully?
We are attempting to run OWB while our database is in restricted mode to allow us to do our updates while restricting other activity but we are running into what seems to be connection issues with the design and control centers. We have added (UR=A) to the tnsnames file and can connect from sqlplus as our design center owner, but I am wondering if some similiar modification is needed within an owb configuration as I know a lot of owb connections are set up using host:port:service and am not sure if somehow that needs a change as well to allow the connection or if that will pick up the change in the tnsnames as well. Anyone have any experience or success with running owb in restricted mode.
Thanks,
Rich
Additional Info: 10.2.0.3 DB on AIX5L 5.3 running OWB 10.2.0.3 with 10.2.0.3.33 clients
Message was edited by:
BengalGuyI can't believe that no one has ever tried this before as it seems like something that would be relatively common. Anyone have any experience with this combination at all regardless of success or failure?
-
Database in noarchivelog mode, truncate command issued
Database in noarchivelog mode, truncate command has been issued how to restore the table?
FACTS:-
1. DB In noarchivelog Mode
2. Cannot enable flash back mode because of 1. above
3. No exports available
4. No backup's Available.
Any thoughts ?Oracle Support/ Professional Services has a Data Unloader (DUL) and ORA-00600 has DUDE, both of which may be able to extract information from data files that are corrupted, where the control files are lost, etc.
These are not, however, cheap utilities. Unless the data itself is really valuable, it is generally not a viable option.
Justin -
How to set the database in NOARCHIVELOG mode
hellow world,
I knewly joined this organization.
Our database is very small < 4GB data.
Database is running in ARCHIVELOG MODE.
since we are not keeping any physical backup, so I opted to run the datbase in NOARCHIVELOG mode.
For bringing the database in NOARCHIVE MODE, I simply changed the init.ora parameter LOG_ARCHIVE_START = FALSE and restart the database.
offcourse the archiving stopped, but to my strange after 30 to 40 minutes my all log files filled an error message is being displayed to the server, saying
log files are filled, waiting for the archiving, Oh my God, What has happened, All users came to my head, DATABASE HANGED, NOT RESPONSING.
SIR, MY QUESTION IS
WHAT FOR ALL LOG FILES WAITING?
when i am saying NOARCHIEVE than
please explain me, where i committed mistake. I am new to ADMINISTRATION.1. Not keeping any physical backup is all the more reason to stay in archivelog mode.
2. You need to shutdown the database, startup mount, and issue 'alter database noarchivelog', the alter database open. -
Problem running oracle 9i database in archivelog mode - database freezes
Greetings,
I recently needed to change a (test) database to archivelog mode to make online back-ups of this database. This posed no real problem although I seem to be unable to set the database to automatic archiving eventhough I edited the init.ora file (translation of the "archive log list" output between square brackets):
SQL> archive log list
Databaselogmodus Archiveermodus [Databaselogmode: Archivemode]
Automatisch archiveren Gedeactiveerd [Automatic archiving: Deactivated]
Archiveerbestemming O:\oracle\ora92\RDBMS [Archivedestionation: O:\oracle\ora92\RDBMS]
Oudste on-line logreeks 12306
Volgende logreeks voor archivering 12306
Huidige logreeks 12308
I added this to my init.ora file:
# Archvie Log Destinations
log_archive_start=TRUE
log_archive_dest_1=%ORACLE_HOME%\database\archive
log_archive_format="%%ORACLE_SID%%t_%s.arc"
However, this is not the real problem (maybe it has something to do with it, which is why I mention it aswell), the real problem is that my database freezes when the archive log file is "full". When the archive file reaches ~102.400Kb it just freezes up and I need to restart the database.
The following error is written to the alert_sid.log file:
Thu Apr 17 09:19:55 2008
Thread 1 cannot allocate new log, sequence 12309
All online logs needed archiving
Current log# 2 seq# 12308 mem# 0: O:\ORACLE\ORADATA\O\REDO02.LOG
The problem seems to be that the oracle service can't start a new logfile when the previous one is full. Does anybody know how I could fix this?
Thanks in advance,
BramHello Maran, thanks for your quick response.
I added the output of archivelog list in the original post, but it's in dutch so here's the (loose) translation of the output:
SQL> archive log list
Databaselog mode Archive mode
Automatic archiving Deactivated
Archive destionation O:\oracle\ora92\RDBMS
Oldest on-line logsequence 12307
Next logsequence for archiving 12307
Current logsequence 12309
Maybe something that can help with the troubleshooting:
The archivelog file is written to O:\oracle\ora92\RDBMS but only AFTER the reboot, I've checked SYSTEM rights to the folder and it has full control.
Babu, thanks aswell for your quick response.
The location exists and space is available but the database doesn't seem to load (that part of) the ora.init file because the output of archive log list still refers to %ORACLE_HOME%\rdbms instead of %ORACLE_HOME%\database\archive.
I've now executed alter system archive log all; and am executing the import where the database usually freezes to see if it still happens. So far I already had this written to the alert_sid.log file after executing the command:
Completed: alter database open
Thu Apr 17 10:00:11 2008
ARCH: Evaluating archive log 1 thread 1 sequence 12307
ARCH: Beginning to archive log 1 thread 1 sequence 12307
Creating archive destination LOG_ARCHIVE_DEST_1: 'O:\ORACLE\ORA92\RDBMS\ARC12307.001'
ARCH: Completed archiving log 1 thread 1 sequence 12307
ARCH: Evaluating archive log 2 thread 1 sequence 12308
ARCH: Beginning to archive log 2 thread 1 sequence 12308
Creating archive destination LOG_ARCHIVE_DEST_1: 'O:\ORACLE\ORA92\RDBMS\ARC12308.001'
ARCH: Completed archiving log 2 thread 1 sequence 12308
And new log files were written to the directory (O:\oracle\ora92\RDBMS) and this time I didn't have to reboot for it to happen. Both were 100mb files without the database actually doing all that much though.
Message was edited by:
user616266 -
Database in Suspect Mode in SQL Server 2000 Log Shipping Environment
Hi All
We have movement of SQL Server 2000 at physical level. We have disable jobs and stop Agent and SQL Server services.
After moved the server we have started the server and then start SQL Server 2000 services.
All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in AdvanceAll of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in Advance
Hello,
Did you made sure no transactions like restore logs were running when you stopped SQL server service or agent .I have seen in SQL 2000 an abrupt stop of SQL Server agent when its doing a process can sometimes force database in suspect mode.
I would like you to get your disk analyzed by vendor ASAP for any fault in disk at first go it seems to me an underlying hardware issue.
Please can you check errorlog and event viewer to find out any possible cause for database going into suspect mode
I always suggest to use Backup and restore method of recovery to get out from suspect database problem.If you dont have then you can move with DBCC Checkdb and various repair options but be sure
DATA LOSS might be possible when you use repair allow data loss and repair_rebuild removes constraints.
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
Maybe you are looking for
-
Hello All, Can we generate automatic schedule lines for a scheduling agreement from an external system. we don't use MRP in SAP but we use external planning system which generates Purchase requsisitions as of now, we want to generate schedule lines w
-
WebDynpro application no displayed on other systems
Hi All.. We have developed an WebDynpro application using webservices where in the webservice will be used in connecting to the XI server and the rest all the business logic is there is done on XI which will be connecting to the R/3 using an RFC and
-
Problem faced while installing adobe reader X.
While trying to install adobe reader X, the installation is interuppted after about 85% installation is complete and a message pops up " The instruction at "0X00000047" referenced memory at "0X00000047". The memory could not be read. Click on OK to t
-
Hi friends I have used Validation transfer object to validate the result of an inner join query before loading into the target table. I've faced a strange issue and that is, after inner join, the number of the result records(before validation) is 109
-
Is anyones app store crashing after the ios 6 update?
After installing the update I went to restore my purchases from the app store. I clicked on purchases it says loading and the circles spin and then I get the white screen and then it goes to the white screen. After calling the Apple Tech support it