cancel
Showing results for 
Search instead for 
Did you mean: 

SUM Tool died unexpectedly with ERROR: No support for DB type

Former Member
0 Kudos

Hi

Im using SUM tool for release upgrade. In extration phase it gave error "Unable to execute the SDT request ABAP operation extract on hostname GILSAPED instance 00 Extraction of the ABAP upgrade request ABAP has failed Error from unit observer Tool died unexpectedly with ERROR: No support for DB type ''

My OS is AIX and DB is oracle 10.2

Kindly find log below

Apr 19, 2013 9:13:58 AM [Info]: Starting the executor UC-10 to run request type UseCaseRequest

Apr 19, 2013 9:13:58 AM [Info]: Reset is currently not possible because the status of the current operation extract is RUNNING.

Apr 19, 2013 9:13:58 AM [Info]: Request ABAP operation extract status set to RUNNING

Apr 19, 2013 9:13:58 AM [Info]: Reset is currently not possible because the status of the current operation extract is RUNNING.

Apr 19, 2013 9:13:58 AM [Info]: Request UC operation extract status set to RUNNING

Apr 19, 2013 9:13:58 AM [Info]: Releasing the executor UC-10 to run request type UseCaseRequest

Apr 19, 2013 9:13:58 AM [Info]: Request list SUM synchronization events saved to file /usr/sap/GSD/ZSUM/sdt/data/SDTRequestListEvents.xml

Apr 19, 2013 9:13:58 AM [Info]: SDT event SAPJup_extract_syncevents_registered fired

Apr 19, 2013 9:13:58 AM [Info]: Holding the executor UC-10

Apr 19, 2013 9:13:58 AM [Info]: Reset is currently not possible because the status of the current operation extract is RUNNING.

Apr 19, 2013 9:13:58 AM [Info]: Request UC operation extract status set to WAITING Waiting for synchronization event SAPup_extract_syncevents_registered

Apr 19, 2013 9:13:58 AM [Info]: Waiting for SDT event SAPup_extract_syncevents_registered

Apr 19, 2013 9:13:59 AM [Info]: Reset is currently not possible because the status of the current operation extract is RUNNING.

Apr 19, 2013 9:13:59 AM [Info]: Request ABAP operation extract status set to RUNNING Waiting for completion of the dialog

Apr 19, 2013 9:14:26 AM [Warning]: Unable to parse SL Controller manifest file /usr/sap/GSD/ZSUM/sdt/prop/sdtmanifest.mf

File /usr/sap/GSD/ZSUM/sdt/prop/sdtmanifest.mf not found.

Apr 19, 2013 9:14:26 AM [Error]: Tool died unexpectedly with ERROR: No support for DB type ''

.

Apr 19, 2013 9:14:26 AM [Error]: Error from unit observer

Apr 19, 2013 9:14:26 AM [Error]: Extraction of the ABAP upgrade request ABAP has failed

Apr 19, 2013 9:14:26 AM [Error]: Unable to execute the SDT request ABAP operation extract on hostname GILSAPED instance 00

Apr 19, 2013 9:14:26 AM [Info]: Reset is currently not possible because the status of the current operation extract is WAITING.

Apr 19, 2013 9:14:26 AM [Info]: Request ABAP operation extract status set to ABORTED Unable to execute the SDT request ABAP operation extract on hostname GILSAPED instance 00

Extraction of the ABAP upgrade request ABAP has failed

Error from unit observer

Tool died unexpectedly with ERROR: No support for DB type ''

Accepted Solutions (1)

Accepted Solutions (1)

anandkarthik_raja
Active Participant
0 Kudos

Based on this error, it seems that the "dbms_type" environment variable
may have not been defined properly.
Can you please check the user-specific environment variable DBMS_TYPE
for user <SID>adm?


Please kindly review SAP Note 128126 for more details.

Answers (4)

Answers (4)

Manas_Vincit
Active Participant
0 Kudos

Hi Kranthi,

Did you check SAP note Note 1843966 - Oracle: Add. Information - Software Update Manager 1.0 SP08

and section Support for the Oracle db client 10.x terminated - use 11.2 instead



Thanks

Manas

former_member253966
Discoverer
0 Kudos

I have the same issue what is the solution?

Former Member
0 Kudos

Hi,

This error occurs when you were not able to give a selection on the Postprocessing phase and just select the Next button.

Once your on the screen Continue Roadmap and you are prompt with "YOUR UPGRADE IS COMPLETE", please ensure to scroll down and make a selection between the two radio buttons.

Then, that's when you can click Next button.

For reference, please see that attached file.

Regards,

Val

former_member264034
Active Contributor
0 Kudos

Hi,

Could you please check the environment settings for the system as per
SAP note below?

602843: Environment settings for R/3/Oracle on UNIX

Can you please specify what is the source and target release?

Can you please check the user-specific environment variable DBMS_TYPE
for user <SID>adm?

Also, what is the kernel patch in your current source system?

Regards,

Aidan

Former Member
0 Kudos

Hi,

Could you please check the environment settings for the system as per note below?

602843: Environment settings for R/3/Oracle on UNIX

Also please check the user-specific environment variable DBMS_TYPE for user <SID>adm?

If this is not the case then you also need to crosscheck your stack xml and find out if you have selected the correct database ( sometimes multicheck options during creation of stack xml is missing). Also check SAP Note 1678024.

Regards,

Sachin