Mani's Blog

January 30, 2013

How to use cell phone

Filed under: Thought of the day — mani @ 5:48 pm

How to use cell phone

I was recently watching TV show, this is what I have learned Using Cell Phone may cause brain tumor or other impacts.   But there is no proof at this time; the reason being latency between exposure and impact is at least 20 years.  The cell phone is being used only 16 years.

The amount of waves goes around our brain is equal to amount of waves using on Microwave oven.

You can protect by using wired earpiece, Don’t talk when your signal is really week that is the time more amount of waves being used to get you the signal, third don’t let kids talk on the cell phone, because the skull for them is much thinner.

Advertisements

January 7, 2013

InnoDB: table %s/%s: unknown table type 33

Filed under: MySQL,Xtrabackup — mani @ 11:21 pm

Ran into issue while restoring and recovering using xtrabackup.  innobackupex-1.5.1 –apply-log ./

130107 20:32:49 InnoDB: table bac002/_user: unknown table type 33
130107 20:32:49 InnoDB: table bac002/_user: unknown table type 33
130107 20:32:49InnoDB: Assertion failure in thread 1230002496 in file ibuf0ibuf.c line 1309
InnoDB: Failing assertion: len % DATA_NEW_ORDER_NULL_TYPE_BUF_SIZE <= 1
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
innobackupex-1.5.1: Error:
innobackupex-1.5.1: ibbackup failed at /usr/bin/innobackupex-1.5.1 line 464.
root@@xnomdb912n2:/local/mysql/data#

Solution:

I was using incorrect my.cnf file,  in my case I had incorrect binlog-format, and few other parameter.  Once I fixed them then restore/recovery worked just fine.

December 14, 2012

Error: ORA-16751: failed to switchover to physical standby database. Both Oracle DB says Physical Standby

I ran the switchover to dataguard box.  I ran into issue where both database became physical standby.

Problem:

DGMGRL for Linux: Version 11.1.0.7.0 – 64bit Production

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

Welcome to DGMGRL, type “help” for information.
DGMGRL> connect sys/oracle
Connected.
DGMGRL> swtichover to xnodb01c
Unrecognized command “swtichover”, try “help”
DGMGRL> switchover to xnodb01c
Performing switchover NOW, please wait…
Error: ORA-16751: failed to switchover to physical standby database

Failed.
Unable to switchover, primary database is still “xnodb01cdg”

Solution:

Now I have to choose one database and promote as primary.   Following steps worked well for me.

SQL> select database_role from v$database;

DATABASE_ROLE
—————-
PHYSICAL STANDBY

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area 2.6724E+10 bytes
Fixed Size            2160272 bytes
Variable Size         8321501552 bytes
Database Buffers     1.8254E+10 bytes
Redo Buffers          146423808 bytes
Database mounted.
SQL> alter database recover managed standby database cancel;
alter database recover managed standby database cancel
*
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active

SQL> alter database recover managed standby database finish;

Database altered.

SQL> ALTER database commit to switchover to primary with session shutdown;

Database altered.

SQL> alter database open;

Database altered.

SQL>  select database_role from v$database;

DATABASE_ROLE
—————-
PRIMARY

SQL> alter system switch logfile;

System altered.

SQL>

Now other DB functioning as Physical Standby with no issues.

December 12, 2012

The installer has detected that you may have an Automatic Storage Management (ASM) instance improperly configured or one that was not properly cleaned up from a previous install.

Filed under: Database,Oracle — mani @ 4:58 pm

I ran in to this issue when I re-install Oracle Binaries during prerequisites checking.

Problem:

The installer has detected that you may have an Automatic Storage Management (ASM) instance improperly configured or one that was not properly cleaned up from a previous install.

Solution:

You may see the recommendation by Oracle:  You must completely remove the ASM instance by deleting the entry for it from the oratab file, or you must configure it properly by ensuring that the oratab file is updated to point to a valid Oracle Home where ASM is configured.

But sometimes you need to make sure environment variables are set and old home directory has been removed.

 

ORA-16055: FAL request rejected ARCH: FAL archive failed. Archiver continuing

Filed under: Database,Dataguard,Oracle — mani @ 5:35 am
Tags: , , ,

Problem:

We have environment with Primary and Active standby Dataguard.   For some reason storage on Dataguard is crashed and I had rebuild the Dataguard DB from backup.  Noticed Archive log is not being shipped and when I look at alert log  found following errors.

FAL[server, ARC3]: FAL archive failed, see trace file.
Errors in file /local/opt/oracle/diag/rdbms/xnodbcor/XNODBCOR1/trace/XNODBCOR1_arc3_2216.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
ORACLE Instance XNODBCOR1 – Archival Error. Archiver continuing.

Checked parameter values on archive_dest on primary DB and noticed “RESET” value assigned to ” log_archive_dest_state_1″

log_archive_dest_state_1         string     RESET

Solution:

Enabled the dest_1 as below, that fixed the problem.   Error disappeared and logs are being shipped and applied on Standby site.

SQL> alter system set log_archive_dest_state_1=enable;

System altered.

SQL> alter system switch logfile;

System altered.

SQL>

November 30, 2012

Oracle Grid control connects to incorrect/wrong Database / Oracle Grid pulls wrong metrics

Issue:

Grid control connects to Primary DB, but thinks it connected Physical standby and pull Standby metrics instead of Primary DB. This has started happening once I ran the switchover from DG to Primary DB.

Story behind the issue:

Here is the story behind the issue.  We had Database environment with Master(Primary) RAC and Physical Standby (RAC).   We had to convert our RAC Database into Single Instance DB and use local storage.  First I have converted Dataguard into Single Instance DB.   Switched the traffic to DG and looked good.   Converted Primary from RAC to single instance and migrated to local disk while it was Dataguard(standby).   Everything looks fine until this moment.    We decided to move the traffic back to original Primary and we did.   Everything was working well.

Effort to fix the issue.

However from this point grid control started showing DG performance metrics on both Primary and standby.  It was so weird.  I did stopped the agent,  ran clearstate, started the agent,  Did agent syncronization.  Nothing worked.    Infact I uninstalled agent on both Primary and standby then Install the agent only on Primary DB box.   I am shocked to see DG metrics and the grid control thinks it is physical standby.

At this point I was looking at primary Database’s agent log.   I noticed listener services listens to remote listener service.  which is pointing to DG box.

Solution:

Ran “lsnrctl services” to find out remote registry on Dataguard box.  It is was missed out during the conversion of RAC to single instance process.

Removed/unregister remote listener as below.

alter system set remote_listener=” scope=both;

Ran “lsnrctl services” to confirm the remote registry is gone.

Now the grid talking and pulling metrics against correct DB.

October 24, 2012

ORA-32021: parameter value longer than 255 characters

Filed under: Oracle — mani @ 7:29 pm

I was trying to set service_names, which was really long due to more number of services we needed.   Used ‘,’ as concatenation between multiple values, then worked.

SQL> @enable_services
ALTER SYSTEM SET SERVICE_NAMES=’xno_db_proc.xno.ningops.net, xno_db_membership.xno.ningops.net, xno_db_core_search.xno.ningops.net, xno_db_core_cache.xno.ningops.net,    xno_db_opensocial.xno.ningops.net, xno_db_core_batch.xno.ningops.net, xno_db_core_audit.xno.ningops.net, xno_db_core.xno.ningops.net, xno_db_admin.xno.ningops.net,  xno_core.xno.ningops.net, XNODBCOR’
*
ERROR at line 1:
ORA-32021: parameter value longer than 255 characters

Fix:  Used ‘,’ as concatenation between multiple values, then worked.

[oracle@xnodb911 ~]$ cat enable_services.sql
ALTER SYSTEM SET SERVICE_NAMES=’xno_db_proc.xno.ningops.net, xno_db_membership.xno.ningops.net, xno_db_core_search.xno.ningops.net, xno_db_core_cache.xno.ningops.net,‘,’ xno_db_opensocial.xno.ningops.net, xno_db_core_batch.xno.ningops.net, xno_db_core_audit.xno.ningops.net, xno_db_core.xno.ningops.net, xno_db_admin.xno.ningops.net,‘,’xno_core.xno.ningops.net, XNODBCOR’;

SQL> @enable_services.sql

System altered.

SQL> show parameter service_names

NAME                     TYPE
———————————— ——————————–
VALUE
——————————
service_names                 string
xno_db_proc.xno.ningops.net, x
no_db_membership.xno.ningops.n
et, xno_db_core_search.xno.nin
gops.net, xno_db_core_cache.xn
o.ningops.net,,  xno_db_openso
cial.xno.ningops.net, xno_db_c
ore_batch.xno.ningops.net, xno
_db_core_audit.xno.ningops.net

NAME                     TYPE
———————————— ——————————–
VALUE
——————————
, xno_db_core.xno.ningops.net,
xno_db_admin.xno.ningops.net,
, xno_core.xno.ningops.net, XN
ODBCOR
SQL>

October 10, 2012

Oracle ASM disk creation failed. Marking disk “%s” as an ASM disk: [FAILED]

Filed under: ASM,Database,Oracle — mani @ 10:21 pm

We have a RAC database, we are converting to Non-RAC (Stand-alone) DB, and also need to migrate data off SAN storage.  I ran into this error while I am creating ASM disk ( after adding 2 new local disks).

Here is the error I ran into.

# /etc/init.d/oracleasm createdisk asm_ssd1 /dev/sdz1
Marking disk “asm_ssd1” as an ASM disk:                    [FAILED]

As soon the disk has been added to system, is configured via multipath and created device under /dev/mapper.  As I don’t want to use via multipath device, so what I did was.

1. Grabbed device id by ls -lrt /dev/disk/by-id

2. Added this device id in backlist block of /etc/multipath.conf file

devnode_blacklist {
wwid 3600508e000000000d02538430ed9c60b
wwid 35000c5003192cd97
wwid 35000c500333728e3
devnode “^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*”
devnode “^hd[a-z]”
devnode “^cciss!c[0-9]d[0-9]*”
}

3. run /etc/init.d/multipathd restart

Now I am able to create ASM disk properly.

# /etc/init.d/oracleasm createdisk asm_ssd1 /dev/sdz1
Marking disk “asm_ssd1” as an ASM disk:                    [  OK  ]
# /etc/init.d/oracleasm createdisk asm_ssd2 /dev/sdaa1
Marking disk “asm_ssd2” as an ASM disk:                    [  OK  ]

Now I can see newly added disks.
# /etc/init.d/oracleasm listdisks
ASM_DATA01
ASM_DATA02
ASM_REDO01
ASM_SSD1
ASM_SSD2

October 8, 2012

ORA-16789: standby redo logs not configured

Filed under: Data Guard Broker,Database,Dataguard,Oracle — mani @ 9:42 pm
Tags: ,

In our environment, Dataguard Manager log was showing following errors.

DG 2012-10-08-21:23:11        0 2 0 RSM0: HEALTH CHECK WARNING: ORA-16789: standby redo logs not configured
DG 2012-10-08-21:23:11        0 2 760559130 Operation CTL_GET_STATUS continuing with warning, status = ORA-16789
DG 2012-10-08-21:23:11        0 2 760559130 Operation CTL_GET_STATUS continuing with warning, status = ORA-16809
DG 2012-10-08-21:24:11        0 2 0 RSM Error: LogXptMode value ‘ASYNC’ of requires this database to have status redo logs, but they are not configured.

Show Configuration reports warning “ORA-16608: one or more databases have warnings”

DGMGRL> show configuration

Configuration
Name:                aclu1c
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodb01c   – Primary database
xnodb01cdg – Physical standby database

Fast-Start Failover: DISABLED

Current status for “aclu1c”:
Warning: ORA-16608: one or more databases have warnings

show database verbose xnodb01cdg  returned success.

show database verbose xnodb01c returned errors, so I am sure the primary DB has issue.
Solution: is to add standby log files to primary DB.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 31 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 32 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 33 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 34 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 35 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

Problem solved:

After adding all above standby log files,   Dataguard log stopped reporting the error.  Also dgmgrl stopped reporting the warnings.

DGMGRL> show configuration

Configuration
Name:                aclu1c
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodb01c   – Primary database
xnodb01cdg – Physical standby database

Fast-Start Failover: DISABLED

Current status for “aclu1c”:
SUCCESS

DGMGRL>

 

September 27, 2012

Oracle Agent stopped working : ORA-12505: TNS:listener does not currently know

Filed under: Uncategorized — mani @ 11:03 pm

Oracle Agent stopped working all of sudden.

Agent stop populating to grid. Stopped, Did clearstate, restarted agent. Nothing worked.

Tried following steps too, but no help.

1 stop the agent
2 delete agntstmp.txt and lastupld.xml (under sysman/emd)
3 Delete all the files under upload and collection directories
4 start the agent
Here it is a real solution.

Go to Grid Control,
Click on Setup
Choose Agents
Choose the Problematic Agent
Click on Unlock.
Resynchronize the agent.

 

 

« Previous PageNext Page »

Create a free website or blog at WordPress.com.