trc recreation

level 2ORA-04031: unable to allocate 136 bytes of shared memory ("sharedpool", "select/* + rule */Bucket_cn... "," SQLA ^ 337fc737 "," kccdef: qkxrMemAlloc ")Elapsed: 00:00:10. 99BYS @ bys3> show parameter shared_poolORA-04031: unable to allocate 16 bytes of shared memory ("sharedpool", "unknownObject "," KGLH0 ^ 92c529c4 "," kglHeapInitialize: temp ") You can also see a large number of error logs in the warning log: Mon Feb 03 20:20:44 2014Errors in file/u01/diag/rdbms/bys3/bys3/trace/bys3_mmo

= 11141424 At this point, in the database alert log log of Node 2, no other information was found, only the information that the node 1 instance was restarted. Therefore, it is not difficult to see that the node ASM instance was forced to terminate, is the key to this problem. We further analyzed the log of the Node 1 ASM instance and found the following information: Tue Sep 15 21:51:52 2015Time drift detected. Please check VKTM the trace file for more details.Thu Sep 17 11:38:06 2015Errors i

written to/u01/Oracle/10.2.0/db_1/Network/Trace/listener. TRC Trace Level is currently 0 Started with PID = 25371 Listening On: (description = (address = (Protocol = TCP) (host = felix1) (Port = 1521 ))) Listener completed notification to CRS on Start Timestamp * connect data [* protocol info] * event [* Sid] * return code 03-jun-2014 11:51:54 * (CONNECT_DATA = (cid = (program =) (host = felix1) (user = Oracle) (command = status) (arguments = 64) (

, enable the trace function, execute an SQL statement, and disable trace: 3. Browse trace files Open the trace file directory: CD/ora10g/admin/otdrdb/udump By date, the file that appears at the top is the generated trace file: Ls-T | more Let's take a look at the unprocessed trace file. The content format is not easy to read: More otdrdb_ora_30597.trc Use tkprof to handle otdrdb_ora_30597.trc:

to the problems found in the log for timely processing Problem Processing The startup parameter is incorrect. Check the initialization parameter file The redo log cannot be switched because the checkpoint operation or archive operation is not completed. If this happens frequently, you can increase the redo log file group and find a way to improve the efficiency of checkpoint or archive operations; The tablespace is deleted without authorization. C

Recently, I bought two SSD hard disks and mounted them to the database. I put the virtual memory and temp tablespace and a controlfile on them. I hope to improve the efficiency of the database by taking advantage of the fast I/O feature of the SSD hard disk. after two weeks of running in the test environment, I moved to the formal environment. At noon today (3rd days), I received a call from my colleagues while I was on the way to dinner, and the database went down. return to the data center and

\ udump \ fgisdb_ora_5600.trc 2) obtain the trace file using SQL-- SQL: view the location of the current session trace fileSelect D. Value | '\' | Lower (rtrim (I. instance_name, CHR (0) | '_ ora _' |P. spid | '. trc' trace_file_nameFrom (select P. spidFrom v $ mystat M, V $ session S, V $ PROCESS pWhere M. Statistic # = 1And S. Sid = M. SidAnd P. ADDR = S. paddr) P,(Select instance_name from V $ instance)

I,OracleTracking FileThere are three types of Oracle tracking files: One is the background alarm log file, which recordsDatabaseActivities of background processes during startup, shutdown, and running, such as creating tablespaces, creating rollback segments, some alter commands, log switching, and error messages. When the database fails, you should first check the file, but the information in the file is not necessarily related to any error status. The background alarm log file is saved in th

log_disable (log_obj * log)Disable the log function of the specified direction.(2) void log_enable (log_obj * log)Enable the log function of the specified direction(3) void log_error (string format, Arg arg0)Void log_message (string format, Arg arg0)The previous function can write an event, data, or error message to the System Log according to the specified format string. This function is not affected by the TRC tracking management module.The latter

One quiet afternoon, an AIX small machine with an ORACLE database in the test environment was shut down due to an unexpected power failure. In the test environment, an engineer was assigned to solve the problem. Specifically, the server was restarted, it is found that the/app directory of oracle is not mounted. Then we fixed it through smitty fs, mounted the app, and started oracle. The system logs of system.txt (obtained through errpt-a), alert_soa.log, and oracle trace logs

[Oracle @ localhost udump] $ pwd /Home/oracle/admin/ORCL/udump [Oracle @ localhost udump] $ ls ORCL_ora_5035.trc You can also use an SQL script to find the generated trace file: SELECT a. VALUE | B. symbol | c. instance_name | '_ ora _' | d. spid | '. trc'Trace_fileFROM (SELECT VALUEFROM v $ parameterWHERE name = 'user _ dump_dest '),(Select substr (VALUE,-6, 1) symbolFROM v $ parameterWHERE name = 'user _ dump_dest ') B,(SELECT instance_name FROM v

One ORA-600 [13011], one ora-60013011SunOS 5.10 Oracle 10.2.0.2.0 development environment a database has a ora-600 error.Alert. error message in log: Thu Nov 13 15:11:43 2014 Errors in file/oracle/admin/sun/bdump/sun_j000_29589.trc: ORA-00600: internal error code, arguments: [13011], [298314], [4277430], [0], [4277430], [17], [], [] Thu Nov 13 15:11:45 2014 Errors in file/oracle/admin/sun/bdump/sun_j000_29589.trc