How to get Windows version from command line of remote servers

How to get windows version from command line of remote server ?

For one server:

D:\> reg query "\\172.69.0.79\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ProductName

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    ProductName    REG_SZ    Windows Server 2008 R2 Enterprise

Note: Login to your client PC as domain user with local administrator privilege.




For multiple servers: (content republished, Source here)

Save the below code as a batch file:


REM Check OS Version on a remote server
@echo Off
pushd %~dp0
for /f %%a in (serverlist.txt) do (
Echo %%a is checked
reg query "\\%%a\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ProductName

) >> OS_version_query_result.txt


In the same folder location of batch file, place the serverlist.txt file.
Just type one host name per line without any trailing space.

serverlist.txt read as below:

phygrsrv01
phyaprsrv01
172.36.88.101
10.1.0.122

Now execute the batch file, it creates a output file in the same location.

Manually Move + Delete Archive log [Windows]

### Below command deletes files ARC*.* from F:\Oracle_Arc with date older than 7 days:

FORFILES /P F:\Oracle_Arc /M ARC*.* /D -7 /C "cmd /c del @path"


### Below Command moves files ARC*.* from D:\Logs to F:\Arc with date older than 2 days: 

FORFILES /P D:\Logs /M ARC*.* /D -2 /C "cmd /c move @path F:\Arc"

ORA-08181 ORA-06512: at "SYS.SCN_TO_TIMESTAMP"

Version: 11.2.0.3

SQL> select name, open_mode, database_role from v$database;

NAME OPEN_MODE DATABASE_ROLE
--------- -------------------- ----------------
HSB62 READ ONLY PHYSICAL STANDBY

SQL> select scn_to_timestamp(current_scn) scn_sync_until from v$database;
select scn_to_timestamp(current_scn) scn_sync_until from v$database
*
ERROR at line 1:
ORA-08181: specified number is not a valid system change number
ORA-06512: at "SYS.SCN_TO_TIMESTAMP", line 1


OR


SQL> select current_scn from v$database;

CURRENT_SCN
--------------------
10588754037

SQL> select scn_to_timestamp(10588754037) scn_sync_until from v$database;
select scn_to_timestamp(10588754037) scn_sync_until from v$database
*
ERROR at line 1:
ORA-08181: specified number is not a valid system change number
ORA-06512: at "SYS.SCN_TO_TIMESTAMP", line 1


Workaround: To bounce the database and flush shared pool (doesn't worked for me..!)


Conclusion / Solution:

Bug 17214565.

There is no fixes for this bug currently.

The issue seems to be resolved in 12c.

how to get ping result with timestamp ?

# ping 172.11.23.103 | while read pong; do echo "$(date): $pong"; done >> /tmp/pingtest103.log


Tue Jul 23 09:04:33 AST 2013: PING 172.11.23.103 (172.11.23.103) 56(84) bytes of data.
Tue Jul 23 09:04:33 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=21 ttl=64 time=0.137 ms
Tue Jul 23 09:04:34 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=22 ttl=64 time=0.100 ms
Tue Jul 23 09:04:35 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=23 ttl=64 time=0.144 ms
Tue Jul 23 09:04:36 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=24 ttl=64 time=0.112 ms
Tue Jul 23 09:04:37 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=25 ttl=64 time=0.122 ms
Tue Jul 23 09:04:38 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=26 ttl=64 time=0.136 ms
Tue Jul 23 09:04:39 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=27 ttl=64 time=0.097 ms
Tue Jul 23 09:04:40 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=28 ttl=64 time=0.201 ms
Tue Jul 23 09:04:41 AST 2013: 64 bytes from 172.11.23.103: icmp_seq=29 ttl=64 time=0.115 ms



After 16 hours:

# ls -lrth /tmp/pingtest103.log

-rw-r--r-- 1 root root 8.5M Jul 24 01:09 /tmp/pingtest103.log

How to take RMAN Disk backup while Tape backup is configured ? [ TESTED ]

The below script overrides the DEFAULT DEVICE TYPE for backup.



RMAN> SHOW DEFAULT DEVICE TYPE;

RMAN configuration parameters for database with db_unique_name HSBC12 are:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';

RMAN> run
{
backup AS COMPRESSED BACKUPSET device type disk database 
format '/ora/dbbkp/DB_%d_%t_%s_%p' plus archivelog format '/ora/dbbkp/Archive_%d_%U';
backup AS COMPRESSED BACKUPSET device type disk current controlfile tag =cf1 
format '/ora/dbbkp/ctrlfile_%t_%s_p%p.dbf';
backup AS COMPRESSED BACKUPSET device type disk spfile 
format '/ora/dbbkp/Manual_spfile_%t_%s_p%p.dbf';
} 

how to check data guard is in sync?

### How to check data guard is in sync?

On Standby:


SQL> col CURRENT_SCN for 9999999999999999999

SQL> SELECT SCN_TO_TIMESTAMP(CURRENT_SCN) SYNC_UNTIL FROM V$DATABASE;

SYNC_UNTIL
---------------------------------
26-MAY-13 02.00.38.000000000 PM

SQL>

Data Guard - How To Check Whether Physical Standby is in Sync with the Primary or Not?

Summary:

1. Check for GAP on standby
2. Check redo received on standby
3. Check redo applied on standby
4. Identify missing archive log files
5. Copy archive log files
6. Register archive log files with standby
7. Restart the managed recovery operations

step 1. Check for GAP on standby

-----------------------------------------------------------------------------------------------
primary + standby > select max(sequence#) from v$log_history;

primary > SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
          FROM V$ARCHIVED_LOG
          WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
          ORDER BY 1;
-----------------------------------------------------------------------------------------------

step 2 and 3. Check redo received on standby and Check redo applied on standby

-----------------------------------------------------------------------------------------------
standby > SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
          FROM
         (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
         (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
         WHERE
         ARCH.THREAD# = APPL.THREAD#
          ORDER BY 1;
-----------------------------------------------------------------------------------------------

step 4. Identify missing archive log files

-----------------------------------------------------------------------------------------------
-- if GAP
standby > SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;
-----------------------------------------------------------------------------------------------

step 5.  Copy archive log files

-----------------------------------------------------------------------------------------------
After identifying a gap (as shown above), the DBA will need to query the primary database
to locate the archived redo logs on the primary database. The following query assumes the
local archive destination on the primary database is LOG_ARCHIVE_DEST_1:

primary > SELECT name
            FROM v$archived_log
            WHERE thread# = 1
              AND dest_id = 1
              AND sequence# BETWEEN 09464 and 90468;
-----------------------------------------------------------------------------------------------

step 6. Register archive log files with standby

-----------------------------------------------------------------------------------------------
--  Copy the above redo log files to the physical standby database and register
    them using the ALTER DATABASE REGISTER LOGFILE ... SQL statement on the
    physical standby database.
 
    For example:

standby > ALTER DATABASE REGISTER LOGFILE '/u04/arch/HSBC33/arch_t1_s64.dbf';
standby > ALTER DATABASE REGISTER LOGFILE '/u04/arch/HSBC33/arch_t1_s65.dbf';
standby > ALTER DATABASE REGISTER LOGFILE '/u04/arch/HSBC33/arch_t1_s66.dbf';
standby > ALTER DATABASE REGISTER LOGFILE '/u04/arch/HSBC33/arch_t1_s67.dbf';
standby > ALTER DATABASE REGISTER LOGFILE '/u04/arch/HSBC33/arch_t1_s68.dbf';
-----------------------------------------------------------------------------------------------

step 7. Restart the managed recovery operations

-----------------------------------------------------------------------------------------------
-- After the redo logs have been registered on the physical standby database,
   the DBA can restart the managed recovery operations.

   For example, to put the physical standby database into automatic recovery managed mode:

standby > alter database recover managed standby database disconnect from session;
-----------------------------------------------------------------------------------------------

How to check RECOVER MANAGED STANDBY DATABASE real time apply?

### On Standby: Delayed apply or Real time apply?


SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DELAY 60 disconnect; -- apply delayed for 60 minutes.

Database altered.

SQL> SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS;

RECOVERY_MODE
-----------------------
MANAGED
IDLE
IDLE
IDLE
...


SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE disconnect; -- Realtime apply

Database altered.

SQL> SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS; 

RECOVERY_MODE
-----------------------
MANAGED REAL TIME APPLY
IDLE
IDLE
IDLE
...

-- no time delay
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT; 

-- no time delay
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY DISCONNECT;

-- 60 minutes delay
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DELAY 60 DISCONNECT;

-- real time apply
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;

--- Note: -----------------------------------------------------------------------------------

By default, apply services wait for the full archived redo log file to arrive on the standby database before applying it to the standby database.

If the real-time apply feature is enabled, apply services can apply redo data as it is received, without waiting for the current standby redo log file to be archived.

ORA-39083 ORA-02063 Object type VIEW failed to create with error

ORA-39083: Object type VIEW failed to create with error:
ORA-02063: preceding 5 lines from HSBC26

face above error during impdp? this means your impdp tries to import the statistics to an remote database through an dblink.


Solution:

exclude=STATISTICS while expdp or impdp

or

set HS_FDS_SUPPORT_STATISTICS=FALSE in the init.ora

Note: In my case, I hit this error, when impdp is trying to create a view, which has a base table on remote database. 


impdp log snippet:

Failing sql is:
CREATE  FORCE VIEW "PLOANS"."CLIENT_TYPE" ("ITEM_CODE") AS select "SYMBOL_CODE" from  CUST_001.CLIENT_SUMMARY@HSBC26

ORA-39083: Object type VIEW failed to create with error:
ORA-02063: preceding 5 lines from HSBC26

how to tar a directory [ tested ] Linux

### Tar and compress a directory: 

[ includes sub-directories and files ]

For example: 

[oracle@oradb1 ~]$ echo $ORACLE_HOME 
/u01/app/product/11.2.0/dbhome_1

[oracle@oradb1 ~]$ cd /u01

[oracle@oradb1 u01]$ tar -pczf OH_backup.tar.gz app/



### Untar and uncompress:

[oracle@oradb1 ~]$ cd /u01

[oracle@oradb1 u01]$ tar xvfz OH_backup.tar.gz



### Tar multiple files:

[oracle@oradb1 bkp] tar -pczf dump2012.tar.gz psm_full.dmp psm_full.log qsm_full.dmp qsm_full.log 



### How do I untar ?

[oracle@oradb1 bkp] tar xvfz dump2012.tar.gz

how to move datafiles in oracle 11g

Move or Rename datafiles: Steps same in 10g or 11g

C:\> rman target /

RMAN> REPORT SCHEMA;

using target database control file instead of recovery catalog
Report of database schema

List of Permanent Datafiles
===========================
File Size(MB) Tablespace   RB segs Datafile Name
---- -------- ------------ ------- ------------------------
1    1320     SYSTEM       ***     D:\ORADATA\HSBC\SYSTEM01.DBF
3    860      SYSAUX       ***     D:\ORADATA\HSBC\SYSAUX01.DBF
4    7681     USERS        ***     D:\ORADATA\HSBC\USERS01.DBF
5    5864     UNDOTBS01    ***     D:\ORADATA\HSBC\UNDOTBS1.DBF
6    6219     USERS        ***     C:\ORACLE\PRODUCT\10.2.0\ORADATA\HSBC\USERS02.DBF
9    2281     INDX01       ***     D:\ORADATA\HSBC\INDX01.DBF
10   2719     USER01       ***     D:\ORADATA\HSBC\USER01.DBF

List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- ---------- ----------- --------------------
1    4229      TEMP      32767       D:\ORADATA\HSBC\TEMP01.DBF

RMAN>

RMAN> SQL 'ALTER TABLESPACE USERS OFFLINE';

RMAN> COPY DATAFILE 6 TO 'D:\ORADATA\HSBC\USERS02.DBF';

RMAN> SWITCH DATAFILE 6 TO COPY;

RMAN> RECOVER TABLESPACE USERS; 

RMAN> SQL 'ALTER TABLESPACE USERS ONLINE';

RMAN> HOST 'del C:\ORACLE\PRODUCT\10.2.0\ORADATA\HSBC\USERS02.DBF';

RMAN> REPORT SCHEMA;

using target database control file instead of recovery catalog
Report of database schema

List of Permanent Datafiles
===========================
File Size(MB) Tablespace   RB segs Datafile Name
---- -------- ------------ ------- ------------------------
1    1320     SYSTEM       ***     D:\ORADATA\HSBC\SYSTEM01.DBF
3    960      SYSAUX       ***     D:\ORADATA\HSBC\SYSAUX01.DBF
4    7681     USERS        ***     D:\ORADATA\HSBC\USERS01.DBF
5    5864     UNDOTBS01    ***     D:\ORADATA\HSBC\UNDOTBS1.DBF
6    6219     USERS        ***     D:\ORADATA\HSBC\USERS02.DBF
9    2281     INDX01       ***     D:\ORADATA\HSBC\INDX01.DBF
10   2719     USER01       ***     D:\ORADATA\HSBC\USER01.DBF

List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- ---------- ----------- --------------------
1    4229      TEMP      32767       D:\ORADATA\HSBC\TEMP01.DBF

RMAN> EXIT;

find Database Character set

Database Charactersets :

SQL> SELECT parameter, value 
     FROM nls_database_parameters 
     WHERE parameter = 'NLS_CHARACTERSET' 
     OR parameter = 'NLS_NCHAR_CHARACTERSET';

PARAMETER                      VALUE
------------------------------ ---------------
NLS_CHARACTERSET               WE8MSWIN1252
NLS_NCHAR_CHARACTERSET         AL16UTF16

expdp backup script [ tested ] Linux

expdp  userid='system/REP2012@REPDB' full=Y  direct=Y

###############################################################
##    Connect to database and create directory object
###############################################################


SQL> CREATE OR REPLACE DIRECTORY DMP_FILES AS '/backup/dmp';

SQL> GRANT read, write ON DIRECTORY DMP_FILES TO system;

SQL> col DIRECTORY_PATH for a40

SQL> col OWNER for a12

SQL> SELECT * FROM DBA_DIRECTORIES;

OWNER    DIRECTORY_NAME DIRECTORY_PATH
-------- --------------- ---------------------
SYS     DMP_FILES    /backup/dmp

###############################################################
##    From Linux command prompt, create backup script
###############################################################


[oracle@oradb1 ~]# cat /backup/dmp/dmp_backup.sh

### Export Data Pump Backup

expdp  userid='system/REP2012@REPDB' full=Y  direct=Y directory=DMP_FILES 
dumpfile=REPDB_full_$(date +"%a").dmp 
logfile=REPDB_full_$(date +"%a").log


### Send status Email
cat /backup/dmp/REPDB_full_$(date +"%a").log | grep -i 'successfully completed' | mailx -s "EXPDP Backup Status" itgroup@hsbc.com

### Compressing Backup + Log

tar -zcvf /backup/dmp/REPDB_full_$(date +"%a").dmp.tar.gz /backup/dmp/REPDB_full_$(date +"%a").dmp /backup/dmp/REPDB_full_$(date +"%a").log


### Deleting Backup

rm -f /backup/dmp/REPDB_full_$(date +"%a").dmp

How to find number of pysical hard drives in windows

Windows Command for finding number of Physical Hard drive:
C:\> wmic diskdrive list brief 

Output: (two physical drive)

C:\Users\administrator> wmic diskdrive list brief
Caption                             DeviceID            Model                               Partitions  Size
HP LOGICAL VOLUME SCSI Disk Device  \\.\PHYSICALDRIVE0  HP LOGICAL VOLUME SCSI Disk Device  1           146778685440
HP LOGICAL VOLUME SCSI Disk Device  \\.\PHYSICALDRIVE1  HP LOGICAL VOLUME SCSI Disk Device  1           299966300160

alter system kill session [dynamic]

select 'ALTER SYSTEM KILL SESSION ' ||chr(39)||sid||chr(44)||serial#||chr(39)||';' QUERY 

from v$session 
where username='ADMIN';

QUERY
-----------------------------------------
ALTER SYSTEM KILL SESSION '197,4989';



----------------------------------------------------------


SET LINESIZE 100
COLUMN spid FORMAT A10
COLUMN username FORMAT A10
COLUMN program FORMAT A45

SELECT s.inst_id,
       s.sid,
       s.serial#,
       p.spid,
       s.username,
       s.program
FROM   gv$session s
       JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id
WHERE  s.type != 'BACKGROUND';
--AND    s.sid=136;

INST_ID  SID    SERIAL# SPID  USERNAME   PROGRAM
------- ---- ---------- ----- ---------- ------------------
      1   63       9889 6800             ORACLE.EXE (J000)
      1  132      12187 7828             ORACLE.EXE (J001)
      1  197       4989 4836  SYS        sqlplus.exe


C:\> set ORACLE_SID
ORACLE_SID=orcl

C:\> orakill <oracle_sid> <spid>

C:\> orakill orcl 7828

Warning: Oracle recommends killing session at database level.

----------------------------------------------------------


DECLARE
A CHAR(2);
BEGIN
FOR I IN 20..50
LOOP
--SELECT CHR(I) INTO A FROM DUAL;
DBMS_OUTPUT.PUT_LINE(I||CHR(32)|| CHR(I));
END LOOP;
END;
/

ORA-19815, ORA-16038, ORA-19809, ORA-00312

Found these above errors in alert log..?

ORA-19815, ORA-16038, ORA-19809, ORA-00312

Database hung..?

Database crashes immediately after startup..?




### Check your alert log for this parameter:


log_archive_dest_1         = "LOCATION=USE_DB_RECOVERY_FILE_DEST"
db_recovery_file_dest      = "D:\ARCHIVELOG"

db_recovery_file_dest_size = 16201108K


### pfile : Increase the value by atleast 1GB.

db_recovery_file_dest_size = 17201108K


SQL> startup

Done.

==========================================================

Further like to delete old archivelogs, proceed below

==========================================================

C:\Users\userIT>rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Sun Jan 13 12:58:17 2013

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: ROSE (DBID=575541292)

RMAN> delete archivelog all completed before "sysdate-1"; 

### decide upto which archivelog to delete.

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=13 device type=DISK
List of Archived Log Copies for database with db_unique_name ROSE
==============================================================

Key     Thrd Seq     S Low Time
------- ---- ------- - ---------
307     1    657     A 11-JAN-13
Name: D:\ARCHIVELOG\2013_01_11\O1_MF_1_657_8H0R9QG0_.ARC

308     1    658     A 11-JAN-13
Name: D:\ARCHIVELOG\2013_01_12\O1_MF_1_658_8H0ZCK66_.ARC

309     1    659     A 12-JAN-13
Name: D:\ARCHIVELOG\2013_01_12\O1_MF_1_659_8H1F745J_.ARC


Do you really want to delete the above objects (enter YES or NO)? yes
deleted archived log
archived log file name=D:\ARCHIVELOG\2013_01_11\O1_MF_1_657_8H0R9QG0_.ARC RECID=307 STAMP=804463209
deleted archived log
archived log file name=D:\ARCHIVELOG\2013_01_12\O1_MF_1_658_8H0ZCK66_.ARC RECID=308 STAMP=804470434
deleted archived log
archived log file name=D:\ARCHIVELOG\2013_01_12\O1_MF_1_659_8H1F745J_.ARC RECID=309 STAMP=804484629
Deleted 3 objects


#### If you already deleted archivelogs manually using OS command, proceed with crosscheck...


RMAN> crosscheck archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=13 device type=DISK
validation failed for archived log
archived log file name=D:\ARCHIVELOG\2013_01_12\O1_MF_1_660_8H32D135_.ARC RECID=310 STAMP=804539058
validation failed for archived log
archived log file name=D:\ARCHIVELOG\2013_01_13\O1_MF_1_661_8H50RVPF_.ARC RECID=311 STAMP=804602956
validation failed for archived log
archived log file name=D:\ARCHIVELOG\2013_01_13\O1_MF_1_662_8H50S035_.ARC RECID=312 STAMP=804602961
validation failed for archived log
archived log file name=D:\ARCHIVELOG\2013_01_13\O1_MF_1_663_8H50S2B9_.ARC RECID=313 STAMP=804602964
Crosschecked 4 objects


RMAN> delete expired archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=13 device type=DISK
List of Archived Log Copies for database with db_unique_name ROSE
==============================================================

Key     Thrd Seq     S Low Time
------- ---- ------- - ---------
310     1    660     X 12-JAN-13
Name: D:\ARCHIVELOG\2013_01_12\O1_MF_1_660_8H32D135_.ARC

311     1    661     X 12-JAN-13
Name: D:\ARCHIVELOG\2013_01_13\O1_MF_1_661_8H50RVPF_.ARC

312     1    662     X 12-JAN-13
Name: D:\ARCHIVELOG\2013_01_13\O1_MF_1_662_8H50S035_.ARC

313     1    663     X 12-JAN-13
Name: D:\ARCHIVELOG\2013_01_13\O1_MF_1_663_8H50S2B9_.ARC


Do you really want to delete the above objects (enter YES or NO)? yes
deleted archived log
archived log file name=D:\ARCHIVELOG\2013_01_12\O1_MF_1_660_8H32D135_.ARC RECID=310 STAMP=804539058
deleted archived log
archived log file name=D:\ARCHIVELOG\2013_01_13\O1_MF_1_661_8H50RVPF_.ARC RECID=311 STAMP=804602956
deleted archived log
archived log file name=D:\ARCHIVELOG\2013_01_13\O1_MF_1_662_8H50S035_.ARC RECID=312 STAMP=804602961
deleted archived log
archived log file name=D:\ARCHIVELOG\2013_01_13\O1_MF_1_663_8H50S2B9_.ARC RECID=313 STAMP=804602964
Deleted 4 EXPIRED objects



Done.

Find database name. (non-privileged users)

SQL> show user

USER is "SCOTT"

SQL> select ora_database_name from dual;

ORA_DATABASE_NAME
-------------------
NSEDB



SQL> select '&_CONNECT_IDENTIFIER' NAME from dual;
old   1: select '&_CONNECT_IDENTIFIER' NAME from dual
new   1: select 'NSEDB' NAME from dual

NAME
-----
NSEDB

how to change data guard real time apply to delayed apply

########## ON STANDBY: Real time Apply to Delayed apply ##########


SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DELAY 30 DISCONNECT FROM SESSION;




########## ON STANDBY: Revoking delayed apply to No delay apply #######

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY DISCONNECT FROM SESSION;

--