DDIC_ACTIVATION Error while applying SAPKH60301 & SAPKH60302

[Former Member]

Hi,

While applying the above mentioned patches, SPAM gets stuck at DDIC_ACTIVATION state.

I have upgrade my Kernel to the latest Patch 159 and Upgrade the oracle Patch as well.

SPAM Log

Error during executing the tp command 'tp ACT ALL DVM ...'

tp return code: '0012' , tp message: 'A tool used by tp aborted' , tp output:

This is tp version 372.04.29 (release 700, unicode enabled)

Warning: Parameter DBLIBPATH is no longer used.

standard output from tp and from tools called by tp:

Details of the error situation can also be found in the import logs

Abort the import due to an error situation (30.09.2008, 15:13:54)

IMPORTLOG_

DVM System DVM

Generate Transport Information File 29.09.2008 20:31:54 (0) Successfully Completed

Import Request Piece List 29.09.2008 20:33:23 (0) Successfully Completed

Test Import 29.09.2008 20:40:14 (0) Successfully Completed

Import ABAP Dictionary Objects 29.09.2008 20:46:21 (0) Successfully Completed

ABAP Dictionary Activation 30.09.2008 15:13:42 (12) Canceled

29.09.2008 21:18:52 (12) Canceled

29.09.2008 21:41:02 (12) Canceled

ST22 DUMP

Runtime Errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Date and Time 30.09.2008 15:13:29

29.09.2008 22:01:17 (12) Canceled

29.09.2008 22:51:57 (12) Canceled

30.09.2008 00:27:12 (12) Canceled

Please help! This server needs to be delivered. Please let me know if I can provide some more information.

Thanks,

Vijay Arora

[Former Member]

The problem was resolved!

[Former Member]

Pls writ the error solution step,Tks.

Edited by: Holly Yuan on Aug 17, 2010 7:53 PM

Edited by: Holly Yuan on Aug 17, 2010 7:55 PM

[former_member235680]

Vijay,

Could you pls tell me whether your system is Unicode or a Non-Unicode one?

Thanks

Abhishek

[markus_doehr2]

> Runtime Errors DBIF_RSQL_SQL_ERROR

> Exception CX_SY_OPEN_SQL_DB

> Date and Time 30.09.2008 15:13:29

> 29.09.2008 22:01:17 (12) Canceled

> 29.09.2008 22:51:57 (12) Canceled

> 30.09.2008 00:27:12 (12) Canceled

Please check the dump in ST22 and check the "analysis" section of it. There you will see the database error. (and/or you can check SM21).

Markus