oralce patches 9.2.0.6

Hi there,

My oracle server database (Oracle ver 9.2.0.1) was filled up with some unwanted trace files daily, may i know if it can be solved by apply oralce patches 9.2.0.6.

If yes, how may i get the link to do the patches. Please provide the steps needed to do this patching. Do i have to backup or shut down the database before doing the patching or it can be done when the db is open. Hope to hear from your advice soon as am new to this kind of administration.

Thanks...SFF
foss2002Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [16515], [D], [40], [7157], [7], [0], [], []

from metalink about that problem:

Subject:       ORA-600 [16515]
        Doc ID:       Note:138523.1       Type:       REFERENCE
        Last Revision Date:       21-OCT-2005       Status:       PUBLISHED


Note: For additional ORA-600 related information please read Note 146580.1    

PURPOSE:            
  This article discusses the internal error "ORA-600 [16515]", what
  it means and possible actions. The information here is only applicable
  to the versions listed and is provided only for guidance.

ERROR:              
  ORA-600 [16515] [a] [b] [c] [d] [e]
 
VERSIONS:
  versions 7.0 to 10.1

DESCRIPTION:        

  During a delete or update operation involving column statistics, the
  statistics held in the row cache are found to be inconsistent with those
  in the dictionary tables.

  This internal error is signalled when a histogram's data is inconsistent.
 
FUNCTIONALITY:      
  Kernel Query processing layer Dictionary management
 
IMPACT:            
  PROCESS FAILURE
  NON CORRUPTIVE - No underlying data corruption.

SUGGESTIONS:

  If the Known Issues section below does not help in terms of identifying
  a solution, please submit the trace files and alert.log to Oracle
  Support Services for further analysis.

  Known Issues:
  Bug# 4244360   See Note 4244360.8
      OERI[16515] during DBMS_STATS.gather_table_stats after split partition
      Fixed: 9.2.0.8
 
  Bug# 2252824   See Note 2252824.8
      ANALYZE TABLE with COLUMN STATISTICS may OERI:16515 or not collect statistics
      Fixed: 9.0.1.4, 9.2.0.2, 10.1.0.2
 


So, as by reading the 'Fixed' section above, applying the patch you should get solved that problem

0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
>was filled up with some unwanted trace files daily
trace files are usually generated when there are problems or that some tracing is enabled.


the patching is done as by the instructions that are in the readme of the patch kit, simply follow the lines carefully.
0
 
foss2002Author Commented:
Hi Angel,
Thanks for your reply, how may i set the tracing disabled? Where can i find the patching?

Thanks..SFF
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
first you need to find out what the trace files contain (ie in which folder are they: cdump, bdump, udump, ...)
there are some options to trace, you should learn to identify the trace files and then how to configure them.
0
 
foss2002Author Commented:
Hi,
It is in the folder udump, i had deleted all but it keeps generating. How do i identify the trace files and then how to configure it, that's why i asked.

Thanks..SFF
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
you can try this command online:
ALTER SYSTEM SET SQL_TRACE=FALSE

if that helps, change it in the spfile/pfile

if that does not help, check if the user sessions start a ALTER SESSION SET SQL_TRACE=TRUE possibly.
you might post 1 (small) file or the beginning of it so we can check what the trace file is.
0
 
foss2002Author Commented:
Hi
Here is the beginning of i of the trace file.

Dump file s:\lcs\database\lcsa\udump\lcsa_j000_8144.trc
Mon Apr 10 10:33:25 2006
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 1, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Windows 2000 Version 5.2 Service Pack 1, CPU type 586
Instance name: lcsa

Redo thread mounted by this instance: 1

Oracle process number: 11

Windows thread id: 8144, image: ORACLE.EXE (J000)


*** SESSION ID:(19.17470) 2006-04-10 10:33:25.000
*** 2006-04-10 10:33:25.000
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [16515], [D], [40], [7157], [7], [0], [], []
Current SQL statement for this session:
DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate;  broken BOOLEAN := FALSE; BEGIN ANALYZE_JOB_LCSSYS; :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
675F9624       232  package body SYS.DBMS_STATS
675F9624      3092  package body SYS.DBMS_STATS
675F9624      8923  package body SYS.DBMS_STATS
675F9624      9067  package body SYS.DBMS_STATS
675F9624      9616  package body SYS.DBMS_STATS
675F9624      9800  package body SYS.DBMS_STATS
675F9624      9854  package body SYS.DBMS_STATS
675F9624      9831  package body SYS.DBMS_STATS
6761AFD0         4  procedure LCSSYS.ANALYZE_JOB_LCSSYS
65C8FDB4         1  anonymous block
----- Call Stack Trace -----
calling              call     entry                argument values in hex      
location             type     point                (? means dubious value)    
-------------------- -------- -------------------- ----------------------------
_ksedmp+147          CALLrel  _ksedst+0            
_ksfdmp.108+e        CALLrel  _ksedmp+0            3
_kgeriv+89           CALLreg  00000000             54CBB90 3
_kgesiv+4e           CALLrel  _kgeriv+0            54CBB90 42534FC 4083 5
                                                   407BFAC
_ksesic5+3b          CALLrel  _kgesiv+0            54CBB90 42534FC 4083 5
                                                   407BFAC 4083 5 407BFAC
_kqdhdu+cc           CALLrel  _ksesic5+0           4083 1 1 197D2E4 0 28 0 1BF5
                                                   0 7 0 0
_kqrpsf+1b4          CALL???  00000000            
__VInfreq__kqrcmt+1  CALLrel  _kqrpsf+0            6545EA60 697AB8A4
16                                                
..1.18_2.filter.95+  CALLrel  _kqrcmt+0            683E5374 1 0 54CBB90 54CBB90
159                                                FF 0 0 0
_kdapscs+163b        CALLrel  _ktcrcm+0            683E5374 0 0 0 0 1 0 0
_spefcmpa+75         CALLreg  00000000             407CB7C 4282CB0 0 0
_spefmccallstd+86    CALLrel  _spefcmpa+0          407C96C 4 426A908 407C520 0
_pextproc+58         CALLrel  _spefmccallstd+0     407CBAC 407CB2C 407C9F4
                                                   407C96C 426A908
0
 
foss2002Author Commented:
Hi Angel,
How do i apply the patch, do i have to goto Oralce Metallink to look for patch & download etc as i find it difficult to look for the patch no. coz too much criteria is required in the search.

BR..SFF
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
in the metalink patches & updates, simple search
click the search by "product or family"
enter "RDBMS Server" in the serach field > the list of versions will be filled
choose 9.2.0.6 (or higher)
choose the operating system
click GO

the path link should get listed
0
 
foss2002Author Commented:
Hi

I got the below 4 patches, which one shall i choose?
I am not súre which patch is suitable.

BR..SFF

   Simple Search
 
 
 Advanced Search  Quick Links  Saved Searches  

 Search By   Patch NumberProduct or FamilySaved Search          
 (ex. RDBMS Server)  
Release   Oracle 10.2.0.2Oracle 10.2.0.1Oracle 9.2.0.8Oracle 9.2.0.7Oracle 9.2.0.6Oracle 9 Patch Type   AnyPatchset/MinipackPatch  
 Platform or Language   --------------- Platforms Windows XP (64-bit)MS Windows Server 2003(
Results for Platform : Microsoft Windows Server 2003  
 
 Tip Consider Saving the search to make it easy to run again.  Save Search  
 
Patch  Description  Release  Updated  Size    
   
4996123 Oracle Database Family: Patch
PATCH FOR REVERTING THE PERMISSION OF BINARIES ON 9206 9.2.0.6 25-JAN-2006 4.1K  

3959430 RDBMS Server: Patch
SOLARIS 9.2.0.6.0 PATCHSET TC3:ORA-06550; COMPONENT 'VALIDATE_COMPONENTS' 9.2.0.6 03-JUN-2005 6.6K  

4051461 RDBMS Server: Patch
CANNOT CREATE CHANGE TABLES ON LOGICAL STANDBY SYSTEM 9.2.0.6 03-MAR-2005 31K  

2727824 RDBMS Server: Patch
SDO_WITHIN_DISTANCE FAILS WITH 2D WINDOW AGAINST 3D DATA INDEXED 2D 9.2.0.6 31-JAN-2005 49K
 
 
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:

4996123 Oracle Database Family: Patch
PATCH FOR REVERTING THE PERMISSION OF BINARIES ON 9206 9.2.0.6 25-JAN-2006 4.1K  
0
 
foss2002Author Commented:
Hi,
I tried to avoid doing the patch coz am new to this, worried it might affect the server if it is not careful, is there any other methods that can set the trace
off. I tried the below but don't seems to work

a) Issue the command (lsntctl trace off) at the server's command prompt.

b) Issue the command (ALTER SYSTEM SET SQL_TRACE=FALSE) at the sqp plus via sys or system privilege but got error :
System parameter cannot be modified.

Can you please advise if the above has been done correctly or there is other settings need to be done.

BR..SFF

0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
Unfortunately, the files generated are not normal session trace files, but problem trace files which you cannot switch off by a setting.
only applying the patch can solve the underlying problem and make those trace files go away.

the SQL_TRACE setting is to make that (every) session generates a trace files about it's activity.
0
 
foss2002Author Commented:
Hi
Please help to verify the steps below:

1. Download the above required patch from Oracle Metallink,  print & read the instructions.

2. Do a database backup.

3. Do i have to shut down db?

4. Apply the patch as per instruction.

5. If i need to shut down mean gonna restart db?

6. Any other steps required?

Better be careful than sorry!

Thanks..SFF

0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
2) usually, this should be a cold-backup, ie with the database being shut down, doing a file backup.
you could also perform a export of the database...

3) read the instructions, it is marked there

5) at the different stages, the database might change it's status (open, mounted, not mounted, closed), once all is done you should perform a clean shutdown + startup and check the alert.log file for any problems

6) not required, but ususally you take another full backup of the database after the patch.
0
 
virtual_voidCommented:
If you are planning to patch apply the 9.2.0.7 patch which is the latest for your OS, make sure you get the correct version 32bit or 64 bit depending upon what version of Oracle binaries you have installed.

Are you collecting stats in your DB, if yes how, maybe just changing the way you collect stats might resolve your trace issue.

It seems you are concerned about the amount of trace generation and not the root cause of the trace, if you just want to reduce trace generation, you can simply write a script that cleans up the (compress, archive, delete) trace files every 5 minutes or so.
In 10g the tracing is much more detailed so we have scripts that will compress the trace files older than 2 days and delete these after 30 days.

Thanks
0
All Courses

From novice to tech pro — start learning today.