Hi Stefan
you are right. It scares me too. Guess there will be a way, can't be the first
time something like that happens.
Von meinem Samsung Gerät gesendet.
-------- Ursprüngliche Nachricht --------
Von: Stefan Koehler <contact@xxxxxxxx>
Datum: 05.07.2015 12:19 (GMT+01:00)
An: oracle-l@xxxxxxxxxxxxx, GG <grzegorzof@xxxxxxxxxx>, l.flatz@xxxxxxxxxx
Betreff: Re: AW: Re: Large index creation speed up / issues with direct path
read temp / direct path write temp
Hi GG,
i am also a performance specialist, but had to deal with such situations in my
"permanent employment" era.
@Lothar:
Unfortuanately it is not so easy in case of physical standby databases :)
In addition these databases usually run in "force logging" mode so that a
"create index .... nologging" would have no effect anyway. There are some
special cases (like BI ETLs, etc.) where nologging is also an option in case of
physical standby database, but this is not the common stuff.
However if you just run this index creation with nologging (and database is not
in force logging mode), you can use RMAN incremental backups to roll
forward a physical standby database:
http://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm#SBYDB00759
Almost anything is possible with Oracle - scary :)
Best Regards
Stefan Koehler
Freelance Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: @OracleSK
"l.flatz" <l.flatz@xxxxxxxxxx> hat am 5. Juli 2015 um 11:45 geschrieben:
Oh, I see. Thanks for letting me know. I am a performance specialist.
Therefore I am not aware how to deal with this situation. Maybe our
colleagues will give you some advice.
I would simply create the index on both sides which is probably pretty
naive. ☺
-------- Ursprüngliche Nachricht --------
Von: GG <grzegorzof@xxxxxxxxxx>
Datum: 05.07.2015 11:07 (GMT+01:00)
An: l.flatz@xxxxxxxxxx, oracle-l@xxxxxxxxxxxxx
Betreff: Re: Large index creation speed up / issues with direct path read
temp / direct path write temp
> Standby involved (production HA) no way :( .
