Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.2 - Release: 10.2 to 10.2

Symptoms
The following symptoms have been attributed to this issue :-

a) V10201/V10202 Client connection reports :-

SQL*Plus: Release 10.2.0.1.0 - Production on Thu Oct 23 12:47:07 2008  ---> [or 10.2.0.2.0]

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Enter password:
ERROR:
ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], []
Error accessing PRODUCT_USER_PROFILE
Warning: Product user profile information not loaded!
You may need to run PUPBLD.SQL as SYSTEM
ERROR:
ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], []

b) Queries on V$ views show the same problems :-

SQL> select * from v$database;
select * from v$database
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], []

c) Alert log reports :-

ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], []


d) ORA-600 trace file reports :-

ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], []
No current SQL statement being executed.

e) The call stack trace will be similar to :-

Function List (to Full stack) (to Summary stack)
kssadd_stage <- kqreqa <- kqrpre1 <- kqrpre <- opiosq0 <- kpooprx <- kpoal8 <- opiodr <- ttcpip 
<- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- main <- start

The key function for this article to be considered is 'kssadd_stage', if this is not seen
in the stack the note is unlikely to provide a resolution.

Cause
If facing the above symptoms there is no exact match to known issues but in 
unpublished Bug 4937225 where it is reported :-

Details: 
ORA-22 can occur on OCIStmtExecute after OCISessionBegin 
This problem can also show as ORA-600 [kssadd_stage: null parent]
errors after the ORA-22 errors to the client.
Note: The fix for this issue is a CLIENT SIDE fix.

This note is written in addition to Note 419992.1 as it might be possible not to see ORA-22

Solution
The identified bug can be resolved via :-

a) Use a V102 client >=V10203

b)  Already available oneoff fixes can be located from :
Patch 4937225


If this note does not resolve or the reader is not sure if applicable equally a new SR should
be raised to ORACLE Support.