Please start as follow:
AWMano.exe -SHOW(SQL_DATA)
CAST AWmano.log:
‘-LOG(…)’ will log messages/errors into file ‘c:\temp\CAST_AWmano.log’ (!IMMEDIATE, !SECURE, TRUNCATE).
SQL message: Attempting connection on server REP1 using connection layer Oracle SQL Net V8
SQL message: Connection succeeded.
Opening a new connection on working server ‘REP1’, user ‘CAST’.
[PL/SQL script Analyzer] Analysis canceled.
SQL message: Attempting connection on server REP1 using connection layer Oracle SQL Net V8
SQL message: Connection succeeded.
Opening a new connection on working server ‘REP1’, user ‘KART’.
SQL Error: ORA-00600: internal error code, arguments: [17059], [0x70000001AE60680], [], [], [], [], [], [] (Severity 1, Msg No 600).
*** Error : Query could not be executed on the server. [Method SyncIO_PreloadOracleHierarchy() at line 2837 of file ‘syncio32/syncio’]
<unknown> – ‘Warning: preload error on ‘<<ROOT>>.REP1” [ File orascp32/orabase (line 623), Stamp=(2,@3275344) ]
SQL Error: ORA-00600: internal error code, arguments: [17059], [0x70000001AE796E0], [], [], [], [], [], [] (Severity 1, Msg No 600).
*** Error : Query could not be executed on the server. [Method SyncIO_PreloadOracleHierarchy() at line 3265 of file ‘syncio32/syncio’]
<unknown> – ‘Warning: preload error on ‘<<ROOT>>.REP1” [ File orascp32/orabase (line 623), Stamp=(4,@6426594) ]
Parsing batch ‘P:\SQL\CAST_TESTSCRIPT_REP1_LOAD.SQL’…
——————————————————-
SQL Error: ORA-00600: internal error code, arguments: [17059], [0x70000001D7143F0], [], [], [], [], [], [] (Severity 1, Msg No 600).
*** Error : Query could not be executed on the server. [Method SyncIO_PreloadOracleHierarchy() at line 3265 of file ‘syncio32/syncio’]
<unknown> – ‘Warning: preload error on ‘<<ROOT>>.REP1” [ File orascp32/orabase (line 623), Stamp=(6,@9555375) ]
Performing final resolution of relations and merge of headers & bodies…
————————————————————————-
Resolving pending relations…done (in ~0 ms).
Merging headers & bodies…done (in ~15 ms).
Retrieving list of relations…done (in ~0 ms): retrieved 1013 relations.
Marking relations and up-to-date objects…done (in ~0 ms).
Marking relations issued from packages pre-parsing…
—————————————————–
Done (marked 1002 relations).
Splitting relations:
——————–
Splitting relations involving synonyms…done (splitted 0 relations in ~0 ms).
Splitting relations involving parameters…done (splitted 0 relations in ~0 ms).
Splitting relations involving exceptions…done (splitted 0 relations in ~0 ms).
Splitting relations towards columns…done (splitted 0 relations in ~0 ms).
Splitting relations towards object-type attributes…done (splitted 0 relations in ~0 ms).
Splitting relations towards scope-fields…done (splitted 0 relations in ~0 ms).
Performing final merge/cleanup of 1013 relations (including 1002 pre-parsed relations)…
—————————————————————————————–
Performed: produced 10 relations (in ~32 ms).
=> 9 standalone-relations + 1 merged-relation.
Escalating relations for the expand/collapse feature…Done (escalated 0 relations in ~0 ms).
Chaining the merged & escalated relations’ list (contains 10 relations)…done (in ~0 ms).
Unlocking objects locked in the AppWarehouse due to the synchronization process…
———————————————————————————-
Unlocking objects child of oracle-instance ‘REP1’:
Finished.
End of analysis.
====================================================
Oracle Metalink
DESCRIPTION OF ORA-00600 [17059] ERROR
====================================================
ORA-00600
Note: For additional ORA-600 related information please read [NOTE:146580.1]
PURPOSE: This article discusses the internal error “ORA-600 [17059]”, what
it means and possible actions.
The information here is only applicable to the versions listed and is provided only for guidance. </Internal_Only>
ERROR: ORA-600 [17059] [a] VERSIONS: versions 7.1 to 10.1
DESCRIPTION: While building a table to hold the list of child cursor dependencies
relating to a given parent cursor, we exceed the maximum possible size of the table.
ARGUMENTS: Arg [a] Object containing the table
FUNCTIONALITY: Kernel Generic Library cache manager
IMPACT: PROCESS FAILURE NON CORRUPTIVE – No underlying data corruption.
SUGGESTIONS: One symptom of this error is that the session will appear to hang for a
period of time prior to this error being reported.
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.