0% found this document useful (0 votes)
121 views4 pages

Opatach DB

The document provides information on troubleshooting issues with browsers crashing or Oracle components crashing after upgrading a database or configuring autoconfig on a database node. It includes commands to check the PSU version installed, find potential patch conflicts, and rollback patches. It also describes how to check the ORA_NLS10 parameter value used when starting the listener and database processes to help diagnose NLS issues after an upgrade. Reloading the listener configuration can also help fix issues with the listener after an upgrade or autoconfig.

Uploaded by

Murali Bodapati
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
121 views4 pages

Opatach DB

The document provides information on troubleshooting issues with browsers crashing or Oracle components crashing after upgrading a database or configuring autoconfig on a database node. It includes commands to check the PSU version installed, find potential patch conflicts, and rollback patches. It also describes how to check the ORA_NLS10 parameter value used when starting the listener and database processes to help diagnose NLS issues after an upgrade. Reloading the listener configuration can also help fix issues with the listener after an upgrade or autoconfig.

Uploaded by

Murali Bodapati
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 4

(11:31:52 AM) murali.bodapati: Hi Team, Please review the below notes if you have issues with browser crashing.

430359.1 Internet Explorer Crashes When Forms Is Launched 286758.1 Running Different Versions of Oracle Jinitiator / Sun JRE From Same Ses sion Causes Browser Fatal Error or Crash Regards, Suraj (11:33:50 AM) murali.bodapati: 1) How to Find PSU at OS level? Use below command to find $ORACLE_HOME/OPatch/opatch lsinventory -bugs_fixed -invPtrLoc $ORACLE_HOME/oraIn st.loc | grep "DATABASE PSU" Example: ******** -bash-3.2$ $ORACLE_HOME/OPatch/opatch lsinventory -bugs_fixed -invPtrLoc $ORACLE _HOME/oraInst.loc | grep "DATABASE PSU" 12419378 12419378 Mon Sep 06 06:59:22 CDT 2011 DATABASE PSU 11.2.0.1.6 (I NCLUDES CPUJUL2011) -bash-3.2$ Note: While applying DB patch,Please use above command to find the PSU version,t hen Download the Patch and apply Example: p9217342_112016_Linux-x86-64.zip 2) How to find conflict patches list using OPatch without apply patch? Unzip the patch and go to patch directory run the below commnad $ORACLE_HOME/OPatch/opatch apply -report -invPtrLoc $ORACLE_HOME/oraInst.loc 3) Some times we are unable to rollback the patch,Due to patch directory is not found in .patch_storage. In this case use below command to roll back the patch **************************************************************** opatch rollback -id <sub-set patch#> -no_sysmod **************************************************************** Above command will simply remove patch number from the inventory. (11:37:50 AM) murali.bodapati: Hi Team, If customer facing any issue with listener after DB upgrade or Autoconfig on DB Node. In this case add necessary parameters to listener.ora and sqlnet.ora files."RELO AD" the listener will fix the issue Q: What is Listener reload Command? A: The RELOAD command to reread the listener.ora file. This command enables you to add or change statically configured services without actually stopping the li stener.

In addition, the database services, instances, service handlers, and listening e ndpoints that were dynamically registered with the listener will be unregistered and subsequently registered again. Syntax: $lsnrctl reload $ORACLE_SID Thanks, Naveen On 6/24/2012 1:31 PM, Suraj Krishna K. wrote: > Hi Team, > > Now a days, we are facing issues after Database Upgrade(issues with accessing NLS data, though correct ORA_NLS10 Parameter has been set(env)). > echo $ORA_NLS10 shows the correct value. > > Not sure if the issue is the with Automation. However there is a way to check( if the DB/Listener has been started with correct ORA_NLS10 parameter or not ) > > [orppucli@auohspucl03 ~]$ ps ux|egrep -i 'pmon|tns'|grep -v grep > orppucli 5576 0.0 0.0 83212 13464 ? Ssl 13:53 0:03 /ppucli/oracl e/product/112/bin/tnslsnr PPUCLI -inherit > orppucli 23550 0.0 0.1 234044 16852 ? Ss 13:51 0:00 ora_pmon_PPUC LI > [orppucli@auohspucl03 ~]$ > > [orppucli@auohspucl03 ~]$ cd /proc/5576 > [orppucli@auohspucl03 5576]$ ls > attr cmdline cpuset environ fd limits maps mounts oom_ad j root smaps statm task > auxv coredump_filter cwd exe io loginuid mem mountstats oom_sc ore schedstat stat status wchan > > [orppucli@auohspucl03 5576]$ strings -a environ|grep -i ora_nls ==>This will g ive the ORA_NLS10 env that was used while starting the Listener. > ORA_NLS10=/ppucli/oracle/product/112/nls/data/9idata > > [orppucli@auohspucl03 5576]$ strings environ ==>This will give the complete en vs, that were set while starting the Listener. > _=*22655*/ppucli/oracle/product/112/bin/lsnrctl > ADJREOPTS=-Xms128M -Xmx512M > ADJVAPRG=/ppucli/oracle/product/112/jdk/bin/java > ADPERLPRG=/ppucli/oracle/product/112/perl/bin/perl > APACHE_TOP=/ppucli/applmgr/product/iAS/Apache > COMMON_TOP=/ppucli/applmgr/common > CONTEXT_FILE=/ppucli/oracle/product/112/appsutil/PPUCLI_auohspucl03.xml > CONTEXT_NAME=PPUCLI_auohspucl03 > G_BROKEN_FILENAMES=1 > HISTSIZE=1000 > HOME=/ppucli/oracle > HOSTNAME=auohspucl03 > INPUTRC=/etc/inputrc > LANG=en_US.UTF-8 > LD_LIBRARY_PATH=/ppucli/oracle/product/112/lib:/usr/X11R6/lib:/usr/openwin/lib :/ppucli/oracle/product/112/ctx/lib

> LESSOPEN=|/usr/bin/lesspipe.sh %s > LIBPATH=/ppucli/oracle/product/112/lib:/usr/X11R6/lib:/usr/openwin/lib:/ppucli /oracle/product/112/ctx/lib > LINK_CNTRL= > LOGNAME=orppucli > LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33 ;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:* .btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;3 1:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31 :*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01 ;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35: > MAIL=/var/spool/mail/orppucli > NLS_DATE_FORMAT=DD-MON-RR > NLS_LANG=American_America.WE8ISO8859P1 > NLS_NUMERIC_CHARACTERS=., > NLS_SORT=binary > OOD_DMP=/autofs/upgrade/oto_dump/PUCL > OOD_LOG=/ppucli/oracle/product/112/admin/PPUCLI_auohspucl03/ood/log > OOD_OUT=/ppucli/oracle/product/112/admin/PPUCLI_auohspucl03/ood/out > OOD_TMP=/ppucli/oracle/product/112/admin/PPUCLI_auohspucl03/ood/tmp > ORACLE_HOME=/ppucli/oracle/product/112 > ORACLE_SID=PPUCLI > ORA_NLS10=/ppucli/oracle/product/112/nls/data/9idata > ORA_TZFILE= > PATH=/ppucli/oracle/product/112/perl/bin:/ppucli/oracle/product/112/perl/bin:/ ppucli/oracle/product/112/bin:/ppucli/oracle/product/112/OPatch:/usr/bin:/usr/sb in:/ppucli/oracle/product/112/jdk/bin:/usr/ccs/bin:/bin:/usr/bin/X11:/usr/local/ bin:/ppucli/oracle/product/112/perl/bin:/ppucli/oracle/product/112/bin:/ppucli/o racle/product/112/OPatch:/usr/bin:/usr/sbin:/ppucli/oracle/product/112/jdk/bin:/ usr/ccs/bin:/bin:/usr/bin/X11:/usr/local/bin:/ppucli/oracle/product/112/perl/bin :/ppucli/oracle/product/112/bin:/ppucli/oracle/product/112/OPatch:/usr/bin:/usr/ sbin:/ppucli/oracle/product/112/jdk/bin:/usr/ccs/bin:/bin:/usr/bin/X11:/usr/loca l/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/ppucli/oracle/product/112/ lib:/usr/X11R6/lib:/usr/openwin/lib:/ppucli/oracle/product/112/ctx/lib:/ppucli/a pplmgr/product/806/lib:/ppucli/oracle/product/112/admin/PPUCLI_auohspucl03/scrip ts:/ppucli/oracle/product/112/admin/PPUCLI_auohspucl03/scripts/PPUCLI_auohspucl0 3:.:. > PERL5LIB=/ppucli/oracle/product/112/perl/lib/5.10.0:/ppucli/oracle/product/112 /perl/lib/site_perl/5.10.0:/ppucli/oracle/product/112/appsutil/perl > PWD=/ppucli/oracle > SCRIPT_TOP=/ppucli/oracle/product/112/admin/PPUCLI_auohspucl03/scripts > SHELL=/bin/ksh > SHLIB_PATH=/ppucli/oracle/product/112/lib:/usr/lib:/ppucli/oracle/product/112/ ctx/lib > SHLVL=2 > TERM=vt100 > TNS_ADMIN=/ppucli/oracle/product/112/network/admin/PPUCLI_auohspucl03 > TZ=Asia/Singapore > USER=orppucli > VLM_WINDOW_SIZE=134217728 > A__z="*SHLVL > ORA_NET2_DESC=6,9 > [orppucli@auohspucl03 5576]$ > > The above steps can be repeated for the Pmon Process(when DB was started). > orppucli 23550 0.0 0.1 234044 16852 ? Ss 13:51 0:00 ora_pmon_PPUC LI > > Also, as per the DB Upgrade Work Order, please bounce the Instance after all t he activities have been completed.

> > > > > > > > > >

This will use the correct env while starting up the Database and Listener. Regards, Suraj OHSRM(Oracle OnDemand)

You might also like