Thinking Out Loud

May 29, 2015

Warning: standby redo logs not configured for thread – BUG

Filed under: 12c,Dataguard,oracle — mdinh @ 12:12 am

Surprise to find the following error for single instance Data Guard environment:

    Warning: standby redo logs not configured for thread 3 on boston

 

This will be fixed with an upcoming patch for the existing issue in Oracle Database 12.1.0.1.0 – good reason to stay up to date on patching?

Also, the number of Standby Redo Log Groups do not match since thread = 1 is being used.

Not *ALL* SRL have thread 1 assigned – not sure if this is a bug as well.

[oracle@host01 trace]$ dgmgrl /

DGMGRL for Linux: Version 12.1.0.1.0 - 64bit Production

Copyright (c) 2000, 2012, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected as SYSDG.
DGMGRL> validate database boston

  Database Role:    Primary database

  Ready for Switchover:  Yes

  Flashback Database Status:
    boston:  Off

DGMGRL> validate database london

  Database Role:     Physical standby database
  Primary Database:  boston

  Ready for Switchover:  Yes
  Ready for Failover:    Yes (Primary Running)

  Flashback Database Status:
    boston:  Off
    london:  Off

  Current Log File Groups Configuration:
    Thread #  Online Redo Log Groups   Standby Redo Log Groups  
              (boston)                 (london)                 
    1         3                        2                        

  Future Log File Groups Configuration:
    Thread #  Online Redo Log Groups   Standby Redo Log Groups  
              (london)                 (boston)                 
    1         3                        0                        
    Warning: standby redo logs not configured for thread 3 on boston

DGMGRL> validate database london2

  Database Role:     Logical standby database
  Primary Database:  boston

  Ready for Switchover:  Yes
  Ready for Failover:    Yes (Primary Running)
    Warning: Physical and snapshot standby databases will
    be disabled if a role change is performed to this database

  Flashback Database Status:
    boston:   Off
    london2:  Off

  Current Log File Groups Configuration:
    Thread #  Online Redo Log Groups   Standby Redo Log Groups  
              (boston)                 (london2)                
    1         3                        2                        

  Future Log File Groups Configuration:
    Thread #  Online Redo Log Groups   Standby Redo Log Groups  
              (london2)                (boston)                 
    1         3                        0                        
    Warning: standby redo logs not configured for thread 3 on boston

DGMGRL> 
HOST01:(SYS@boston):PRIMARY> select group#,thread#,sequence#,bytes,used,status from v$standby_log;

    GROUP#    THREAD#  SEQUENCE#      BYTES       USED STATUS
---------- ---------- ---------- ---------- ---------- ----------
         4          0          0   52428800          0 UNASSIGNED
         5          0          0   52428800          0 UNASSIGNED
         6          0          0   52428800          0 UNASSIGNED
         7          0          0   52428800          0 UNASSIGNED

HOST01:(SYS@boston):PRIMARY> select count(*) from v$standby_log where thread#=1;

  COUNT(*)
----------
         0

HOST01:(SYS@boston):PRIMARY> 
HOST03:(SYS@london2):LOGICAL STANDBY> select group#,thread#,sequence#,bytes,used,status from v$standby_log;

    GROUP#    THREAD#  SEQUENCE#      BYTES       USED STATUS
---------- ---------- ---------- ---------- ---------- ----------
         4          1         67   52428800    4803072 ACTIVE
         5          1          0   52428800          0 UNASSIGNED
         6          0          0   52428800          0 UNASSIGNED
         7          0          0   52428800          0 UNASSIGNED

HOST03:(SYS@london2):LOGICAL STANDBY> select count(*) from v$standby_log where thread#=1;

  COUNT(*)
----------
         2

HOST03:(SYS@london2):LOGICAL STANDBY> 
HOST03:(SYS@london):PHYSICAL STANDBY> select group#,thread#,sequence#,bytes,used,status from v$standby_log;

    GROUP#    THREAD#  SEQUENCE#      BYTES       USED STATUS
---------- ---------- ---------- ---------- ---------- ----------
         4          1         67   52428800    4816896 ACTIVE
         5          1          0   52428800          0 UNASSIGNED
         6          0          0   52428800          0 UNASSIGNED
         7          0          0   52428800          0 UNASSIGNED

HOST03:(SYS@london):PHYSICAL STANDBY> select count(*) from v$standby_log where thread#=1;

  COUNT(*)
----------
         2

HOST03:(SYS@london):PHYSICAL STANDBY> 

May 20, 2015

Part1 Configuration Evodesk

Filed under: Uncategorized — mdinh @ 10:47 pm

Installation was not bad.

Evodesk is the 2nd company I am aware of for using recesss nuts for desktop installation.

This makes much more sense than using wood screws.

However, pondering if Evodeskk will be the first company to used recess nuts for all components and get rid of wood screws.

Don’t you think the legs make  great towel rack?

install1

install2

May 19, 2015

First Impression for Evodesk Desktop Unboxing

Filed under: Uncategorized — mdinh @ 12:53 am

Disclaimer: I am not being paid by anyone to write positive or negative review.

Opinions are my own based on my limited engineering background.

First, packaging is somewhat poor and could be much better for a desk costing close to $1,000 ($886 for my configuration).

Tape coming off.

badpackaging2

I hope my desktop is okay.

badpackaging1

Taking a look inside. Is that a tiny scratch I see?

badpackaging3

After opening the desktop, this is the torn location – not enough foam.

badpackaging4

Look at how much love I give it.

Desktop should be shipped in bubble wrap to prevent damage and scratch.

Cable Pass Through is way too small for 30” x 72”.

smallpass

Most standing desks I was looking at are 1 inch thick.

By no means is this best in class as Evodesk Desktop is 3/4 inch thin.

You won’t find this information anywhere at Evodesk technical specification.

http://www.evodesk.com/media/desktop-diagrams.pdf

thin

This is the programmer controller.

Openned ziplock bag and was this a returned repackaged?

controller

My picture does not look at good as Evodesk – http://www.evodesk.com/standing-desks#posi-loc

I do like th Posi-Loc and was the final selling point.

Hope this is secure and does not spin.

posi-loc

Update:

It looks like Evodesk has updated the information for desktop. Either that or I was blind as a bat the first go round.

Renew™ Desktops

  • 100% reclaimed/recycled wood composite desktop
  • EvoGuard™ durable & stylish non-VOC seamless coating
  • Soft comfort edges eliminate nerve compression and pressure fatigue
  • Corners are slightly rounded for improved safety and style
  • Oversized 3” x 6” Cable Pass Through
  • Pre-drilled for quick and easy setup
  • Available sizes: 48″ (30” x 48″ x .75”), 60″ (30” x 60” x .75”), 72″ (30” x 72” x .75”)
  • Meets California Air Resources Board’s (CARB 2) stringent emission standard
  • Backed by a no-nonsense 2-year no-nonsense limited warranty

May 7, 2015

Find Contents of RMAN backuppiece

Filed under: RMAN — mdinh @ 12:14 am

RMAN backuppiece listings from OS

oracle@arrow:hawklas:/home/oracle
$ ll /oradata/backup/
total 216088
-rw-r-----. 1 oracle oinstall  1212416 May  5 11:06 DBF_HAWK_3130551611_20150505_hjq65thu_1_1_KEEP
-rw-r-----. 1 oracle oinstall 50536448 May  5 11:07 DBF_HAWK_3130551611_20150505_hkq65thu_1_1_KEEP
-rw-r-----. 1 oracle oinstall 39059456 May  5 11:07 DBF_HAWK_3130551611_20150505_hlq65thv_1_1_KEEP
-rw-r-----. 1 oracle oinstall  5529600 May  5 11:07 DBF_HAWK_3130551611_20150505_hmq65tie_1_1_KEEP
-rw-r-----. 1 oracle oinstall  1785856 May  5 11:07 DBF_HAWK_3130551611_20150505_hnq65tit_1_1_KEEP
-rw-r-----. 1 oracle oinstall    98304 May  5 11:07 DBF_HAWK_3130551611_20150505_hoq65tjd_1_1_KEEP
-rw-r-----. 1 oracle oinstall     2560 May  5 11:07 DBF_HAWK_3130551611_20150505_hpq65tjf_1_1_KEEP
-rw-r-----. 1 oracle oinstall  1343488 May  5 11:07 DBF_HAWK_3130551611_20150505_hqq65tjh_1_1_KEEP
-rw-r-----. 1 oracle oinstall  1212416 May  4 19:43 HAWK_3130551611_20150504_h9q647ee_1_1
-rw-r-----. 1 oracle oinstall 39051264 May  4 19:43 HAWK_3130551611_20150504_haq647ee_1_1
-rw-r-----. 1 oracle oinstall 50315264 May  4 19:43 HAWK_3130551611_20150504_hbq647ef_1_1
-rw-r-----. 1 oracle oinstall  5529600 May  4 19:43 HAWK_3130551611_20150504_hcq647em_1_1
-rw-r-----. 1 oracle oinstall  1785856 May  4 19:43 HAWK_3130551611_20150504_hdq647ep_1_1
-rw-r-----. 1 oracle oinstall   285184 May  4 19:43 HAWK_3130551611_20150504_hfq647ev_1_1
-rw-r-----. 1 oracle oinstall  1088000 May  4 19:43 HAWK_3130551611_20150504_hgq647ev_1_1
-rw-r-----. 1 oracle oinstall   280064 May  4 19:43 HAWK_3130551611_20150504_hhq647f0_1_1
-rw-r-----. 1 oracle oinstall 11075584 May  4 19:43 HAWK_c-3130551611-20150504-0e
-rw-r-----. 1 oracle oinstall 11075584 May  4 19:43 HAWK_c-3130551611-20150504-0f

Let’s find the backupset and content of backupset for backuppiece.

oracle@arrow:hawklas:/home/oracle
$ rman target /

Recovery Manager: Release 11.2.0.4.0 - Production on Wed May 6 17:02:57 2015

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

connected to target database: HAWK (DBID=3130551611)

RMAN> list backuppiece '/oradata/backup/HAWK_3130551611_20150504_hbq647ef_1_1';

using target database control file instead of recovery catalog

List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
555     554     1   1   AVAILABLE   DISK        /oradata/backup/HAWK_3130551611_20150504_hbq647ef_1_1

RMAN> list backupset 554;


List of Backup Sets
===================


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ --------------------
554     Full    47.98M     DISK        00:00:09     2015-MAY-04 19:43:20
        BP Key: 555   Status: AVAILABLE  Compressed: YES  Tag: TAG20150504T194309
        Piece Name: /oradata/backup/HAWK_3130551611_20150504_hbq647ef_1_1
  List of Datafiles in backup set 554
  File LV Type Ckp SCN    Ckp Time             Name
  ---- -- ---- ---------- -------------------- ----
  2       Full 1946389    2015-MAY-04 19:43:11 /oradata/HAWKLAS/datafile/o1_mf_sysaux_bg5n9c44_.dbf

RMAN>

The backuppiece is from FULL database backup containing datafile for tablespace SYSAUX.

May 2, 2015

Backup file using copy with date append

Filed under: linux — mdinh @ 3:51 am

How many ways are there to backup a file? Copy and append .bak, .sav, .orig, etc …

I was looking for a simple, consistent, yet elegant way to do this.

Good thing for Google (disclaimer I do own the stock), I came across this blog – http://blog.justin.kelly.org.au/how-to-copy-file-and-append-current-date-in-l/

Demo:

oracle@arrow:hawklas:/home/oracle
$ ps
  PID TTY          TIME CMD
 4343 pts/1    00:00:00 bash
 6915 pts/1    00:00:00 ps

oracle@arrow:hawklas:/home/oracle
$ ls -l logdump*
-rw-r--r--. 1 oracle oinstall 2487 Apr 19 11:09 logdump.hst

oracle@arrow:hawklas:/home/oracle
$ filename=logdump.hst

oracle@arrow:hawklas:/home/oracle
$ cp $filename{,.`date +%d%b%Y-%H%M`}

oracle@arrow:hawklas:/home/oracle
$ ls -l logdump*
-rw-r--r--. 1 oracle oinstall 2487 Apr 19 11:09 logdump.hst
-rw-r--r--. 1 oracle oinstall 2487 May  1 20:31 logdump.hst.01May2015-2031

Create a free website or blog at WordPress.com.