Skip to main content

adrci Tool

By Unknown
I found this neat little tool for digging into the alert log without having to actually open it up and start searching line by line. Produces a nice little summary and also generates a report if you need to upload something to MOS.
adrci> show problem

ADR Home = /u03/oratest/testdb/11.2.0.4/admin/TEST_oratest/diag/rdbms/test/TEST:
*************************************************************************
PROBLEM_ID           PROBLEM_KEY                                                 LAST_INCIDENT        LASTINC_TIME                             
-------------------- ----------------------------------------------------------- -------------------- ---------------------------------------- 
2                    ORA 600 [pfrdef1_get_tdo#145: pin failed]                   116801               2016-02-10 11:20:29.927000 +02:00       
4                    ORA 7445 [kgmdtim()+85]                                     118161               2016-02-10 11:22:02.762000 +02:00       
1                    ORA 7445 [peidxr_run()+85]                                  118697               2016-02-10 11:22:13.995000 +02:00       
3                    ORA 600 [pfri.c: pfri8: plio mismatch ]                     118249               2016-02-10 12:58:23.045000 +02:00       
5                    ORA 4030                                                    115658               2016-02-10 16:28:41.934000 +02:00       

adrci> show incident

ADR Home = /u03/oratest/testdb/11.2.0.4/admin/TEST_oratest/diag/rdbms/test/TEST:
*************************************************************************
INCIDENT_ID          PROBLEM_KEY                                                 CREATE_TIME                              
-------------------- ----------------------------------------------------------- ---------------------------------------- 
117345               ORA 7445 [peidxr_run()+85]                                  2016-02-08 14:45:45.287000 +02:00       
116801               ORA 600 [pfrdef1_get_tdo#145: pin failed]                   2016-02-10 11:20:29.927000 +02:00       
118161               ORA 7445 [kgmdtim()+85]                                     2016-02-10 11:22:02.762000 +02:00       
119153               ORA 600 [pfri.c: pfri8: plio mismatch ]                     2016-02-10 11:22:07.810000 +02:00       
119409               ORA 600 [pfri.c: pfri8: plio mismatch ]                     2016-02-10 11:22:08.720000 +02:00       
118697               ORA 7445 [peidxr_run()+85]                                  2016-02-10 11:22:13.995000 +02:00       
118097               ORA 600 [pfri.c: pfri8: plio mismatch ]                     2016-02-10 11:36:15.503000 +02:00       
118249               ORA 600 [pfri.c: pfri8: plio mismatch ]                     2016-02-10 12:58:23.045000 +02:00       
115497               ORA 4030                                                    2016-02-10 15:46:31.975000 +02:00       
115498               ORA 4030                                                    2016-02-10 15:46:33.287000 +02:00       
115657               ORA 4030                                                    2016-02-10 16:28:40.512000 +02:00       
115658               ORA 4030                                                    2016-02-10 16:28:41.934000 +02:00       
12 rows fetched


adrci> show incident -mode DETAIL -p "incident_id=117345"

ADR Home = /u03/oratest/testdb/11.2.0.4/admin/TEST_oratest/diag/rdbms/test/TEST:
*************************************************************************

**********************************************************
INCIDENT INFO RECORD 1
**********************************************************
   INCIDENT_ID                   117345
   STATUS                        ready
   CREATE_TIME                   2016-02-08 14:45:45.287000 +02:00
   PROBLEM_ID                    1
   CLOSE_TIME                    
   FLOOD_CONTROLLED              none
   ERROR_FACILITY                ORA
   ERROR_NUMBER                  7445
   ERROR_ARG1                    peidxr_run()+85
   ERROR_ARG2                    SIGSEGV
   ERROR_ARG3                    ADDR:0x10
   ERROR_ARG4                    PC:0x992481B
   ERROR_ARG5                    Address not mapped to object
   ERROR_ARG6                    
   ERROR_ARG7                    
   ERROR_ARG8                    
   ERROR_ARG9                    
   ERROR_ARG10                  
   ERROR_ARG11                  
   ERROR_ARG12                  
   SIGNALLING_COMPONENT          PLSQL_Code_Execution
   SIGNALLING_SUBCOMPONENT      
   SUSPECT_COMPONENT            
   SUSPECT_SUBCOMPONENT          
   ECID                          
   IMPACTS                       0
   PROBLEM_KEY                   ORA 7445 [peidxr_run()+85]
   FIRST_INCIDENT                117345
   FIRSTINC_TIME                 2016-02-08 14:45:45.287000 +02:00
   LAST_INCIDENT                 118697
   LASTINC_TIME                  2016-02-10 11:22:13.995000 +02:00
   IMPACT1                       0
   IMPACT2                       0
   IMPACT3                       0
   IMPACT4                       0
   KEY_NAME                      Client ProcId
   KEY_VALUE                     oracle@oratest.example.com (TNS V1-V3).21955_139826516727552
   KEY_NAME                      SID
   KEY_VALUE                     1851.30071
   KEY_NAME                      ProcId
   KEY_VALUE                     268.69
   KEY_NAME                      PQ
   KEY_VALUE                     (16777216, 1454935441)
   OWNER_ID                      1
   INCIDENT_FILE                 /u03/oratest/testdb/11.2.0.4/admin/TEST_oratest/diag/rdbms/test/TEST/trace/TEST_ora_21955.trc
   OWNER_ID                      1
   INCIDENT_FILE                 /u03/oratest/testdb/11.2.0.4/admin/TEST_oratest/diag/rdbms/test/TEST/incident/incdir_117345/TEST_ora_21955_i117345.trc
1 rows fetched

adrci> show incident -mode DETAIL -p "incident_id=116801"

Reference


Labels:

Comments

Post a Comment

Popular posts from this blog

Cancel or abort adop session

By Unknown
ADOP is in my opinion still pretty half baked. This is a critical tool that just isn't as intuitive as the old adpatch was. However we move with the times and get the hang of the new way of doing things. Along the way you might want to abort or cancel a patching cycling. With the two file systems and db editioning this can be a bit more to manage. I have learnt the hard way so you need to use the full cleanup after aborting a session. adop phase=abort adop phase=cleanup cleanup_mode=full
Post a Comment
Read more

Creating new WLS domain ends with exit code 255

By Unknown
Cloning the instance I ran into this weird error. Was not sure what to do but after learning my lesson I dug through the error logs after seeing this in the adcfgclone log file. START: Creating new WLS domain. Running /u03/APPLYES/YES/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /u03/APPLYES/YES/fs2/EBSapps/comn/util/jdk64 -al /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/EBSdomain.jar -tdl /u03/APPLYES/YES/fs2/FMW_Home/user_projects/domains/EBS_domain_YES -tmw /u03/APPLYES/YES/fs2/FMW_Home -mpl /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/plan/moveplan.xml -ldl /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/tempinfo.txt Script Executed in 1903 milliseconds, returning status 255 ERROR: Script failed, exit code 255 Dig a bit deeper into the log files cd /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply cat CLONE2016-01-10_04-37-...
Post a Comment
Read more

Launching a Concurrent with Form Personalization on EBS 11i

By Unknown
There are two methods when it comes to running a concurrent from a Form Personalization in Oracle. The thing you need to do in either case is create a menu option for the form in question. This is generally done on a WHEN-NEW-FORM-INSTANCE Trigger Event. If you already have an event like this then you can add it there. I personally like to group my customizations together so there is not much overlap. Whichever catches your fancy will work. Setup the menu with the name: You now have a menu item for the launching of the concurrent program. This is where the two methods separate and you may choose which ever is more appropriate to you. Launch FNDRSRUN (Submit Request) This will use the zoom feature of Oracle Form Personalization to open the Submit Request Form, and pass the parameters to it. This involves personalization in two forms. The sending form needs to call the Form Function and pass the parameters and the Submit Request form needs to receive and process those parameters....
2 comments
Read more