Oracle Error Logs Files
Alerts Note: The easiest and best way to monitor the database for errors and alerts is with the Database Home page in Enterprise Manager. This section provides alternate methods for monitoring, using data dictionary views, PL/SQL packages, and other command-line facilities. Monitoring Errors with Trace Files and the Alert Log Each server and background process can write to an associated trace file. When an internal error is detected by a process, it dumps information about the error to its trace file. Some of the information written to a trace file is intended for the database administrator, and other information is for Oracle Support Services. Trace file information is also used to tune applications and instances. Note: Critical errors also create incidents and incident dumps in the Automatic Diagnostic Repository. See Chapter 8, "Managing Diagnostic Data" for more information. The alert log is a chronological log of messages and errors, and includes the following items: All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60) that occur Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements Messages and errors relating to the functions of shared server and dispatcher processes Errors occurring during the automatic refresh of a materialized view The values of all initialization parameters that had nondefault values at the time the database and instance start Oracle Database uses the alert log to record these operations as an alternative to displaying the information on an operator's console (although some systems also display information on the console). If an operation is successful, a "completed" message is written in the alert log, along with a timestamp. The alert log is maintained as both an XML-formatted file and a text-formatted file. You can view either format of the alert log with any text editor or you can use the ADRCI utility to view the XML-formatted version of the file with the XML tags stripped. Check the alert log and trace files of an instance periodically to learn whether the background processes have encountered er
Log of a successful installation: /var/tmp/installer.log.latest Log of an agent installation: /var/scn/install/log General Messages: /var/adm/messages* BUI: /var/opt/sun/xvm/logs/emoc.log Actions of the BUI and remote clients on the Enterprise Controller: On Oracle Solaris: /var/cacao/instances/oem-ec/audits/ On Linux: /var/opt/sun/cacao/instances/oem-ec/audits/ Events between controllers and agents: On an Oracle Solaris Enterprise Controller: /var/cacao/instances/oem-ec/logs On a Linux Enterprise Controller: /var/opt/sun/cacao/instances/oem-ec/logs On each Oracle Solaris Proxy Controller: /var/cacao/instances/scn-proxy/logs/cacao.n On http://docs.oracle.com/cd/B28359_01/server.111/b28310/monitoring001.htm each Linux Proxy Controller: /var/opt/sun/cacao/instances/scn-proxy/logs/cacao.n Software Updates The Software Update component has its own server with its own logs. The following logs provide information on the activity for this server: Audit Log On Oracle Solaris: /var/opt/SUNWuce/server/logs/audit.log On Linux: /usr/local/uce/server/logs/audit.log Errors On Oracle Solaris: /var/opt/SUNWuce/server/logs/error.log On Linux: /usr/local/uce/server/logs/error.log https://docs.oracle.com/cd/E18440_01/doc.111/e21484/logs_and_directories.htm Log of errors in download jobs: /opt/SUNWuce/server/logs/SERVICE_CHANNEL/error.log Job Log On Oracle Solaris: /var/opt/SUNWuce/server/logs/job.log On Linux: /usr/local/uce/server/logs/job.log Component -Specific Agents: /var/scn/update-agents/logs directory. Libraries: /var/opt/sun/xvm/logs/virtimagelib.log Asset Database On the Enterprise Controller: Log of interactions with the database of assets: /var/opt/sun/xvm/logs/db/mgmt/logs/db.log Log of events in collecting data for reports: /var/opt/sun/xvm/logs/db/reports/logs/db.log On the Proxy Controller: /var/opt/sun/xvm/proxydb/* On each agent: /var/opt/sun/xvm/agentdb/* Upgrade The log of upgrade actions for the Enterprise Controller and its co-located proxy controller is in the file: /var/scn/update-saved-state/update_satellite_bundle_11.1.n.xxxx/updatelog.txt The log of upgrade actions for a proxy controller that is not co-located is in the file: /var/scn/update-saved-state/update_proxy_bundle_11.1.n.xxxx/updatelog.txt Event Logs for Jobs Event logs for jobs are generated by tasks as they progress. See Viewing Job Details for instructions on viewing job event logs. To Control the Number of Common Agent Container Log Files The Common Agent Container cacao is a common Jav
here for a quick overview of the site Help Center Detailed answers to any questions you might have http://stackoverflow.com/questions/6618142/oracle-error-log-file Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, oracle error just like you, helping each other. Join them; it only takes a minute: Sign up Oracle error log file up vote 2 down vote favorite 2 I'm running following block in Oracle (what does it do is not so important) BEGIN SDO_RDF_INFERENCE.CREATE_RULES_INDEX( 'my_index', SDO_RDF_Models('my_model'), SDO_RDF_Rulebases('RDFS')); END; and getting following error: ORA-29532: Java call terminated by uncaught oracle error logs Java exception: java.lang.NullPointerException ORA-06512: at "MDSYS.RDF_APIS_USER", line 7 ORA-06512: at "MDSYS.RDF_APIS_USER", line 9 ORA-06512: at "MDSYS.RDF_APIS", line 477 ORA-06512: at line 2 29532. 00000 - "Java call terminated by uncaught Java exception: %s" *Cause: A Java exception or error was signaled and could not be resolved by the Java code. *Action: Modify Java code, if this behavior is not intended. Question: how can I access Oracle error log or something to get full stack trace or any other information about exception. java oracle plsql ora-06512 ora-29532 share|improve this question edited Jul 7 '11 at 23:06 skaffman 278k63619656 asked Jul 7 '11 at 23:00 Yury Litvinov 78811221 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote accepted Usually only DBA's have essential rights to view Oracle logs. But,If you have enough rights: select value from v$parameter t where t.NAME='background_dump_dest' This query will return the file path of the Oracle alert log and trace\dump files at Oracle Server machine. Alert log (Alert_"databasename".log) ch