Format Date in Oracle Database - NLS_DATE_FORMAT

 When you connect to the Oracle database, anything that has the DATE datatype, is displayed in the default format of DD-MON-YY, and no time component.
 

There are multiple ways to see the time component of a DATE column, in sqlplus. You can either alter your session to set the date format, or you can use a function in your select statement to alter the format of the column.

alter session set nls_date_format = 'DD/MM/YYYY HH24:MI:SS';
select sysdate from dual;
 
SYSDATE
-------------------
12/01/2022 20:19:06
 
select to_char(sysdate,'DD-MON-YY HH24:MI:SS') from dual;
 
TO_CHAR(SYSDATE,'D
------------------
12-JAN-22 20:19:50
 

How about RMAN? How can you see the date and time a backup completed or started? By default you only see the same format as in sqlplus: DD-MON-YY.
This format is not always enough. You try an alter session command in RMAN (same as above), and it doesn’t work. Instead, what is the solution?

You must set the NLS_DATE_FORMAT environment variable outside of RMAN, before you connect to RMAN, to the format of the date and time you want. Then you connect to RMAN, and voila, you have the date displayed properly!

For Unix/Linux OS you have the NLS_DATE_FORMAT variable, and for Windows, you can add the same registry entry NLS_DATE_FORMAT under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEx.

$ export NLS_DATE_FORMAT='DD/MM/YYYY HH24:MI:SS'
 
$ rman target /
 
list backup of controlfile;
 
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
4867    Full    22.02M     DISK        00:00:00     12/01/2022 15:36:52
BP Key: 981   Status: AVAILABLE  Compressed: NO  Tag: TAG20220112T153654
Piece Name: /oradata/bck/HRTST/RMAN/c-2178279485-20220112-02
Control File Included: Ckp SCN: 317921665833   Ckp time: 12/01/2022 15:36:52

Look at the Completion Time column, and the Ckp time. The format of the date is the exact format you wanted.

 

 

Comments

Post a Comment

Popular posts from this blog

Cold Backup Cloning of Database .

 Cold Backup :  A cold backup is done when there is no user activity going on with the system. Also called as offline backup, is taken when the database is not running and no users are logged in. all files of the database are copied and no changes during the copy are made. Cold backup can be preformed when Database is in archive mode as well as Non archive log mode  . Backup Strategy :  Gather all the details of physical files (CRD) files in  database . redo log files are online redo log and archived redo log ones .   Select file_name,tablespace_name from dba_data_files  ; select * from v$controlfile  select member from v$logfile ; select name from v$archived_Log ;  create pfile from spfile  Backup  the contol file manually . alter database backup controlfile to trace as '/tmp/coldbackup_controlfile.sql' ;     Stop all the DB services (Database ,Listener)on source DB Server. Copy all the files(Datafiles,redologfiles,pfile,contol file backup) from source to backup location 
Read more

Find ALert log Location

 The alert log is an XML file that is a the log of messages and errors. Each alert log is specific to its component type, such as database, Oracle ASM, listener, and Oracle Clusterware. For the database, the alert log includes messages about the following:     Critical errors (incidents)     Administrative operations, such as starting up or shutting down the database,         recovering the database, creating or dropping a tablespace, and others.     Errors during automatic refresh of a materialized view     Other database events      Trace files are updated periodically over the life of the process and can contain information on the process environment,  status, activities, and errors. In addition, when a process detects a critical error,  it writes information about the error to its trace file.      Using Find Command    find $ORACLE_BASE -type f -name alert_$ORACLE_SID.log    select value from GV$DIAG_INFO WHERE name='Diag Trace';    find /opt/oracle -name alert*log
Read more

FRA Usage and Administration

Image
 In Oracle database, the Flash Recovery Area or FRA is a location on disk where the database can create and manage several kinds of backup and recovery-related files. Main file types are archivelog, flashback log, backups, as well as mirrors for your control files and redo log files. All files in the FRA are Oracle-managed files. Using a Flash Recovery Area simplifies the administration of your database by automatically retaining them for as long as they are needed for restore and recovery activities, and deleting them when they are no longer needed, because the space is needed for another backup and recovery-related purpose. Checking the current usage  You can check the configuration by looking at two parameters.The parameters are db_receovery_file_dest and second one db_recovery_file_dest_size .  db_receovery_file_dest point to location where the files will be located in Server . FOr normal single Databases this will be any directory for RAC this will be set to a Diskgroup whi
Read more