Steps to move OMS agent to new OMS repository

Reading Time: < 1 minute

Steps below can be used to move OMS Agent from OLD to NEW OMS repository w/o un-installing and re-installing…

On Agent machine/box:

Stop agent: emctl stop agent
Modify emd.properties : Change REPOSITORY_URL and emdWallSrcUrl to new OMS repository Cleanup following files and dir: under $ORACLE_HOME/sysman/emd/upload and $ORACLE_HOME/sysman/emd/state
$ORACLE_HOME/sysman/emd/lastupld.xml
$ORACLE_HOME/sysman/emd/agntstmp.txt
$ORACLE_HOME/sysman/emd/protocol.ini

On OLD OMS database repository find agent that needs to be removed and use package below to remove/clean it up:

SQL> select target_name from mgmt_targets where target_name like
SQL> '%app%';

TARGET_NAME
--------------------------------------------------------------------------------
vwappp005.Shared
vwappp006.Shared
vwappp014.Shared
vwappt001.Shared
vxappp003
vwappp005.Shared:3872
wappp006.Shared:3872
wappp014.Shared:1830
wappp014.Shared:3872
wappt001.Shared:3872
xappp003:3872

11 rows selected.

SQL> exec mgmt_admin.cleanup_agent('vwappt001.Shared:3872');

PL/SQL procedure successfully completed.

On Agent box:

Clear state agent: emctl clearstate
agent Secure agent: emctl secure agent
Start agent: emctl start agent
Upload agent : emctl upload agent

Once, all above steps are done agent should appear on new OMS repository..

RMAN backup using TAG and copying file between ASM to ASM

Reading Time: < 1 minute

I recently wrote a complex script…script to come soon with detail..

This script will create LEVEL 0 backup and copy backup files from ASM to ASM w/o human intervention.

This script will do following tasks:

* Backup database with Level 0
* Validate database backup set
* Verify backup set files
* Build asm copy command
* Copy Backup set files from Source ASM to Destination ASM

Please ping me to get copy of script.

Exadata new bug with 11.2.0.2.x

Reading Time: < 1 minute

New bug was discovered with EXADATA 11.2.2.4.2 in regards to OFA infiniband drivers…details to come soon…

 

Trace file  contents:

System state dump requested by (instance=1, osid=31982), summary=[SYSTEMSTATE_GLOBAL: global system state dump request (kjdgdss_g)].

[ DISKMON][30223] dskm_dump_all()+281 call kgdsdst() 000000000 ? 000000000 ?
[ DISKMON][30223] dskm_async_handler( call dskm_dump_all() 000000000 ? 000000000 ?
[ DISKMON][30223] __sighandler() call dskm_async_handler( 000000000 ? 000000000 ?
[ DISKMON][30223] __poll()+102 signal __sighandler() 7FFFF0F05598 ? 000000001 ?
[ DISKMON][30223] skgznp_accept()+120 call __poll() 7FFFF0F05598 ? 000000001 ?
[ DISKMON][30223] dskm_main()+3052 call skgznp_accept() 01DDBF320 ? 2AAAAC022910 ?
[ DISKMON][30223] __do_global_ctors_a call dskm_main() 00000DDEB ? 00000001D ?
[ DISKMON][30223] __libc_start_main() call __do_global_ctors_a 00000DDEB ? 00000001D ?

Hadoop HDFS database

Reading Time: < 1 minute

I have recently start to mess with Hadoop HDFS database system.

Here is what i plan to do:

  1. Create stand alone HDFS
  2. Create 3 node HDFS cluster
  3. Load test on both single node and HDFS
  4. load test database with Oracle, MySQL and HDFS databases

I should have identical hardware to perform load test…keep checking for setup and results

Also, i am interested to know how many people are interested in Hadoop.

 

Thanks,

 

 

[polldaddy poll=5966024]

AWR automatic or manual snapshot hangs – EXADATA

Reading Time: < 1 minute

Custer database manual or auto snapshot hangs and never returns:

Bug info:

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocType=BUG&bmDocTitle=AWR%20SNAPSHOTS%20HANGING&from=BOOKMARK&bmDocDsrc=BUG&bmDocID=13372759&viewingMode=1143%29%29

Solution:

sqlplus / as sysdba

SQL> exec dbms_stats.gather_table_stats('SYS','X$KCCFN',no_invalidate=>false);

SQL> exec dbms_stats.gather_table_stats('SYS','X$KCCFE',no_invalidate=>false);

SQL> execute dbms_workload_repository.modify_snapshot_settings (interval => 15, retention => 1576800);
SQL> EXEC DBMS_WORKLOAD_REPOSITORY.create_snapshot;

Step above should fix the issue..

Exadata bug related to HAIP

Reading Time: 2 minutes

Recently i have been engaged Peoplesoft financials and HR Exadata gig.  I ran into issue related to HAIP that is used on EXADATA system.  Oracle have confirmed that it is bug and solution is to set cluster_interconnects for each node.

following error encountered when starting cluster database:

PRCR-1013 : Failed to start resource ora.orcl.db
PRCR-1064 : Failed to start resource ora.orcl.db on node nd01db1
CRS-5017: The resource action “ora.orcl.db start” encountered the following error:
ORA-03113: end-of-file on communication channel
Process ID: 0
Session ID: 0 Serial number: 0
 

Trace file:

Group reconfiguration cleanup

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

*** 2012-02-07 15:05:09.686

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

*** 2012-02-07 15:05:10.714

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

*** 2012-02-07 15:05:11.743

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

*** 2012-02-07 15:05:12.565

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).

*** 2012-02-07 15:05:16.275

kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE])

I looked up on support and they are saying it is a bug:

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocTitle=Exadata%20Rac%20Node%20Instance%20Crash%20with%20kjzdattdlm:%20Can%20not%20attach%20to%20DLM&from=BOOKMARK&bmDocType=PROBLEM&bmDocDsrc=KB&bmDocID=1386843.1&viewingMode=1143))

solution is to shutdown and recreate spfile with hard coded value for bindib0

SQL> create pfile='inittempORCL.ora' from spfile ;
SQL> !echo "ORCL1.cluster_interconnects='192.168.5.1' " >>inittempORCL.ora
SQL> !echo "ORCL2.cluster_interconnects='192.168.5.2' " >>inittempORCL.ora

SQL> create spfile='+DATA/ORCL/spfileORCL.ora' from pfile='inittempORCL.ora';

# srvctl start database -d ORCL

Repeat each steps all cluster databases.

hopefully, steps above should fix the issue with bindib0.