Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 8914

SQL0750N The source table cannot be renamed

$
0
0

Hi all,

Would greatly appreciate if anyone could give some input or recommendation.

 

The problem i faced is during SPS patching at 5.5 Execution phase using SUM tool

 

Severe error(s) occurred in phase MAIN_SWITCH/EU_SWITCH!

Last error code set: Non single errors (code &gt; 8) found in logfile 'EUSWITCH.ELG'<br/> 2 error during parallel execution of processes, check 'EUSWITCH.ELG' for details<br/> 4 processes failed, check 'SQLSTMTSTD.*' for details

 

E RROR: Detected the following errors:

# /usr/sap/XIP/SUM/abap/log/EU_SWITCH06.XUT: 3 ETQ398 SQL: RENAME "D344L" TO "D344L~~OLD" 3 ETQ398 SQL: RENAME "DBDIFF" TO "DBDIFF~~OLD" 3 ETQ398 SQL: RENAME "DD03L" TO "DD03L~~OLD" 1 ETQ000 ================================================== 4 ETQ010 Date & Time: 20141025034810 1EETQ008 Error message: DBSL error 99 (db code -750): SQL0750N The source table cannot be renamed because it is referenced in a view, materialized query table, trigger, SQL function, SQL method, check constraint, referential constraint, or XSR object. SQLSTATE=42986 1EETQ003 exit code: "12"EUSWITCH.ELG

 

 

I am aware of sap note 381518 - DB6: DB error - 750 in the upgrade during conversion

 

Regarding snote 381518  - I have performed the following SQL during the time of error ( execution phase )

 

db2 "select viewname from syscat.viewdep where viewschema ='SAPXIP' and bname ='DD03L' //  returns 0 records


However if i remove the viewschema filter, there will be 1 record,


db2 "select viewname from syscat.viewdep where viewschema ='SAPTOOLS' and bname ='DD03L' //  returns 1 record


but when i tried to delete this record, i will get SQL error SQL0607N


There are no triggers via db2lookup command. I did drop a constraint primary key from table DD03L and repeat the step but error still persist.



I believe this error DBSL error 99 (db code -750): SQL0750N  is the culprit of the SUM error

perhaps there there was other table beside DD03L were affected ?

 

Would greatly appreciate if anyone could give some inputs or recommendation.

 

Attached is the db2lookup of table DD03L DURING error phase and BEFORE error phase

Tool used - SUM SP11 PL7

DB version -DB2 v9.5.0.10

Operating SystemSunOS 5.10

 

 

 

Best regards,

Alex


Viewing all articles
Browse latest Browse all 8914

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>