Check All Types of Materials

http://www.scribd.com/

Comments

Post a Comment

Popular posts from this blog

ORA-01565: error in identifying file '?/dbs/spfile@.ora'

QL> startup ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated SQL> create pfile from spfile; create pfile from spfile * ERROR at line 1: ORA-01565: error in identifying file '?/dbs/spfile@.ora' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3   SQL> shut abort SQL> create pfile='/home/oracle/initORA11G.ora' from spfile='+DATA/ORA11G/spfileORA11G.ora'; File created. oracle@rac1.localdomain:/home/oracle [ORA11G1] >dba SQL*Plus: Release 11.2.0.3.0 Production on Wed Apr 6 20:15:29 2016 Copyright (c) 1982, 2011, Oracle.  All rights reserved. Connected to an idle instance. SQL> startup pfile='/home/oracle/initORA11G.ora'; ORACLE instance started. Total System Global Area 1653518336 bytes Fixed Size                  2228904 by...
Read more

Reboot Exadata Machine

Image
1) Log in to the first database server as root. 2) Change to the OneCommand directory # cd /opt/oracle.SupportTools/onecommand 3) Note whether the Grid Infrastructure is currently enabled for autostart, so that this state can be restored later: # dcli -g dbs_group -l root /u01/app/11.2.0/grid/bin/crsctl config crs 4) Disable the Grid Infrastructure for autostart on the database servers if the previous step indicated it is currently enabled for autostart. # dcli -g dbs_group -l root /u01/app/11.2.0/grid/bin/crsctl disable crs Note: This is step is [Optional] and it can required during maintenance operation like “firmware patches” which requires to reboot the Compute Node several times. 5) Stop the Grid Infrastructure stack on the database servers (compute nodes): # dcli -g dbs_group -l root /u01/app/11.2.0/grid/bin/crsctl stop crs 6) Verify that the Grid Infrastructure stack has shutdown successfully on the database servers. The follow...
Read more

STEPS TO troubleshoot long running concurrent request in R12.2.x

USUALLY we are getting concurrent program running longer and concurrent request not picking jobs, etc. those are very frequent issue we expected from development team. Collect basis level of information to development team A. Oracle seeded program/Custom program? B. How much time it used earlier? C. Is there any recent code change done in concurrent program? D. Is this program fetching higher data compare to last run? E. Does this job running any specific time/ It can be run any time? F. Does this job fetching data using DB link? G. Does the problem happen on both the test and production instance? Once asked above questions to development team in meanwhile we need to start basic sanity check in our environment. A. Verify the status of the concurrent program select REQUEST_ID,phase_code,status_code,ORACLE_SESSION_ID from apps.fnd_concurrent_requests where request_id=’23432345’; B. Find which concurrent manger ran a specific concurrent request select b.USER_CONCURRENT_QUEUE_NAME from fnd...
Read more