DataGuard and NoLogging

Question

i would like to know pertaining to DataGuard and NoLogging.
I read that it causes block corruption if nologging is there on the primary, which can be a problem on the standby db.
but when i tried to simulate the same on my primary/standby it was not observed.
create table xyz(name varchar2(20));
insert into xyz values ('myname');
[did this by insert 10 rows]
then created index
create index ind_xyz on xyz(name) nologging; <-- this should be causing a problem
then same log is transfered on stadnby .
but when i query on standby (in read only mode)
it works fine. the select query works fine.
so wheres the problem of nologging ???

Answer 1

SQL> select tablespace_name, force_logging from dba_tablespaces;
TABLESPACE_NAME FORCE_LOGGING
SYSTEM NO
UNDOTBS NO
TEMP NO
SQL> select force_logging from v$database;
FOR
NO
???? then where is the catch ???